+ Post New Thread
Results 1 to 7 of 7
Wireless Networks Thread, Re naming computers in Technical; I've got some computers to move from the suite to classroooms, they are currently on wsus and ad with names ...
  1. #1
    chrbb's Avatar
    Join Date
    Oct 2005
    Location
    Midlands
    Posts
    1,506
    Thank Post
    141
    Thanked 66 Times in 61 Posts
    Rep Power
    46

    Re naming computers

    I've got some computers to move from the suite to classroooms, they are currently on wsus and ad with names - suite01 etc.

    If I rename them by leaving the domain and rejoin them with a new name, will this cause any problems with wsus, sophos and ad?

  2. #2

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,388
    Thank Post
    797
    Thanked 1,587 Times in 1,390 Posts
    Blog Entries
    10
    Rep Power
    427
    Quote Originally Posted by chrbb View Post
    I've got some computers to move from the suite to classroooms, they are currently on wsus and ad with names - suite01 etc.

    If I rename them by leaving the domain and rejoin them with a new name, will this cause any problems with wsus, sophos and ad?
    no should be fine. When we did this i reimaged the room. Took 2 clicks with ghost console. once that was done just rename with sysprep. Its easier.

  3. #3
    ricki's Avatar
    Join Date
    Jul 2005
    Location
    uk
    Posts
    1,466
    Thank Post
    20
    Thanked 164 Times in 157 Posts
    Rep Power
    51
    Why do you have to remove the machine from active directory to rename the computer?

    I would normally just rename the computer and run a "wsus change id.bat"

    with this in it

    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v AccountDomainSid /f
    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v PingID /f
    reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Win dowsUpdate /v SusClientId /f
    cls
    @echo Triggering detection after resetting WSUS client identity
    net stop wuauserv
    net start wuauserv
    wuauclt /resetauthorization /detectnow

    This will rest the wsus id.

    Now delete the old machine name from wsus and sophos and it just works.

    If you run ocs inventory you will have to get it to change its id as well but thats just a script as well.

    Lastly dont forget to move the machine in AD to the correct OU.

    Wsus will pick the machine up under the new name and so will sophos, not a problem.

    You might have to move the computer to the correct group in sophos and wsus as they will be detected in unasigned but thats a couple of clicks.

    Richard
    Last edited by ricki; 28th November 2008 at 12:44 PM.

  4. 2 Thanks to ricki:

    AngryTechnician (29th November 2008), chrbb (28th November 2008)

  5. #4

    Join Date
    Aug 2005
    Location
    London
    Posts
    3,144
    Thank Post
    113
    Thanked 518 Times in 447 Posts
    Blog Entries
    2
    Rep Power
    121
    2 separate issues - @chrbb wants to rename some PCs (so the names match physical locations) and wants to make sure there's no problem in WSUS

    if you just rename them in AD then WSUS will still work but I seem to remember that you'll get two machines appearing. You can either just delete the old name from the console or you can use the reset method you've documented.

  6. #5

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    10,686
    Thank Post
    824
    Thanked 2,570 Times in 2,187 Posts
    Blog Entries
    9
    Rep Power
    731
    No need to drop them off the network or go through AD deleting duplicates. All you need to do is go into system properties and change the machine name on each workstation, this will prompt you for an admin password then will change the existing machine account name in AD.

    It will leave the machine account exactly where it was in AD so you may not have to move it depending on the structure in your setup.

    Then just run the WSUS reset thing from above and your done. I rename machines like this all the time with no hassels. I don't use WSUS at that site though (ISA caching rule instead) so I am not 100% on that aspect but suspect that it will reregister itself to WSUS in time without needing to be reset manually.

  7. #6
    Oops_my_bad's Avatar
    Join Date
    Jan 2007
    Location
    Man chest hair
    Posts
    1,738
    Thank Post
    438
    Thanked 53 Times in 50 Posts
    Rep Power
    29
    Or just name your PC based on serial# or asset tag# (for example) - then when the inevitable room move comes round it's one less thing to do

  8. #7

    FN-GM's Avatar
    Join Date
    Jun 2007
    Location
    UK
    Posts
    15,388
    Thank Post
    797
    Thanked 1,587 Times in 1,390 Posts
    Blog Entries
    10
    Rep Power
    427
    Quote Originally Posted by Oops_my_bad View Post
    Or just name your PC based on serial# or asset tag# (for example) - then when the inevitable room move comes round it's one less thing to do
    We thought that but its a pain when using VNC. I know all the computers names and where they are at work, its easy to connect up then.

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 5
    Last Post: 18th March 2010, 10:28 AM
  2. all-in-one computers
    By Chris in forum Hardware
    Replies: 22
    Last Post: 10th April 2008, 03:40 PM
  3. Domain Naming ad.school.co.uk
    By thegrassisgreener in forum Windows
    Replies: 13
    Last Post: 6th February 2008, 09:08 PM
  4. Use of old computers
    By AJT1 in forum Hardware
    Replies: 21
    Last Post: 20th November 2007, 10:26 AM
  5. Automated PC Naming
    By Mr_M_Cox in forum Windows
    Replies: 8
    Last Post: 31st May 2007, 06:40 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •