• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 559
  • Last Modified:

Renaming computers from image in a single domain

We have an image of a base XP pro system using Acronis. I did the following:
1. Image a computer name it BaseXP
2. Join domain with same computer name
3. Rename computername to ABC01
4. Bring image (BaseXP) to another computer
5. Rename second image to ABC02
6. Bring image on a third machine and logged on to the same domain.

Now I have 3 different computers (BaseXP, ABC01, ABC02) on the same network in the same domain. In Active Directory, even though I just renamed the computers, and not rejoined the domain with any of them, I am showing all 3 of them as a different maching in Active Directory and everything is working like a charm.
Of course, I was only experimenting and I am quite surprised with the end result.
My reason for trying this was because it is a lot quicker than sysprep and it preserve all of the permissions set on logical drives as well as folders. It also preserve domain user accounts.
I was expecting the renamed computer to replace the existing one and not add a new one to the domain.
I am quite happy with these results, but I am also skeptical.
By the way, I tried removing BaseXP from the domain and it did not affect the other 2 in any way that I can tell. As a matter of fact, both are being used right now and no one is having any issues.
What I am looking for is some inputs from experts that could tell me what could go wrong in a long run.
We are running server 2003 SP2 R2 and XP Pro workstations.
0
gablais
Asked:
gablais
  • 2
  • 2
  • 2
  • +2
1 Solution
 
ormerodrutterCommented:
As long as you remember to rename the computer after joining the domain I can't see any problem. Even if you forgotten to rename the computer, next time you join another computer with an existing name your DC will tell you so.
0
 
Alan Huseyin KayahanCommented:
      Hi gabalis
            *If you disjoin/rejoin the client or rename , a new computer object will be created with new name, while the old one is NOT! deleted. In future, if you try to join a computer to domain, which has the same name with old computer object in AD or username, a message will pop-up and ask "computer object exist, wpuld you like to use this". If you never choose yes and let it stay inactive, it will stay there untill garbage collection process.
             *If you remove the computer from domain (Change from domain to workgroup is considered removing. Renaming is not removing), computer will not be effected from GPOs, will have to log on locally not domain account, but still can acqurie IP address from DHCP and can access internet if there is no proxy like ISA. And computer account still stays and wont be deleted untill garbage collection process because of inactivity.
             This does not affect system in long run. But if you frequently image computers, that will cause junk in Computers in AD.

Regards
0
 
ajbrittonCommented:
I'm not exactly sure what problems you may encounter, but I've a feeling they would be related to security issues on individual machines. If you need a quicker/easier method of making the image unique, I would point you to NewSIS (http://www.microsoft.com/technet/sysinternals/Utilities/NewSid.mspx). This will rename a computer and give it a new SID at the same time. You would use NewSID to rename and re-SID a newly images computer prior to adding it to the domain.
0
 
oBdACommented:
What you are creating are installations that are unsupported by Microsoft. There can well be issues that you won't notice at the beginning, and to find and resolve (if possible at all) issues related to cloning machines can easily take a *lot* longer than reading through the sysprep documentation and creating a proper image.
And if something happens on your workstations, and all Microsoft tells you is to reinstall the machines and try again, do you really want to be the one explaining to TPTB that you saved about 4 hours by ignoring sysprep some time ago, and now the new software won't run, but you'll gladly spend the weekend at the office to reinstall all machines?
Oh, and note that the *image* you'll be distributing has already to be syspreped; you can *not* clone an installation, boot it up, and then run sysprep.
Check here for details:

Do not disk duplicate installed versions of Windows
http://support.microsoft.com/?kbid=162001

The Microsoft policy concerning disk duplication of Windows XP installations
http://support.microsoft.com/?kbid=314828
0
 
ormerodrutterCommented:
Question to oBdA :-

Will the SID of a machine "change" when it is joined to a domain, to reflect the change of status? IF so then there is not a problem to gablais?
0
 
ajbrittonCommented:
Machine SIDs do not change when joining a domain.
0
 
gablaisAuthor Commented:
Thanks for the quick response everyone. I have read the links from ajbritton and oBdA. In a nutshell, Microsoft claims that it will only affect the local machine if in a workgroup and not in a domain and they have provided a tool(newsid) to correct this. They also claim that they are aware that a lot of companies prefers this over sysprep when they have large amount of computers to deploy.
Am I reading this right?

0
 
oBdACommented:
We're using NewSID for test machines, but we have, for example, experienced problems trying to install a Sharepoint server on a cloned machine that was treated with NewSID.
Microsoft is very clear when it comes to cloning: "Microsoft does not provide support for computers that are set up by use of SID-duplicating tools other than the System Preparation tool. If an image was created without the use of sysprep, Microsoft does not support the running of Sysprep after the image is deployed as a way to bring the computer back into compliance."
Once the syspreped image is created, installing new machines is likely to be faster than using NewSID, especially since you can deploy several syspreped images at the same time, while with NewSID, you have to wait until the name and SID change on one machine is finished before you can boot the next one.
Using sysprep is not really that complicated that it's worth it to waive Microsoft's support; you might need it urgently at some point.
0
  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now