Cloning Systems
delifeath
November 4th, 2009
Does anyone know what the current process is for cloning systems as far is SEP is concerned. I've referenced this KB article before and now I see that there is a note at the bottom which seems to indicate that something may need to be done again. Most of the clients are running MR4 or MR4 MP2 and the SEPM is now at RU5. Can anyone give me a clear answer on what needs to be done if a system is going to be cloned. Thank you.
I do both the computer ID and
I do both the computer ID and machine ID - I kill them both.
Then when the image is put on a new computer and we run NEWSID, and it connects to the net and SEP starts, that gets regenerated.
For over a year NOT A SINGLE ISSUE with ghost images and SEP! Not a one.
I delete those values and then instantly reboot into the bood CD to launch ghost to save the image.
Deleting those is the last thing I do............
For RU5, I'd also follow the rest of the document. They aren't an issue in eariler releases.......
Personal sites -> http://theamcpages.com and http://antique-engines.com
Toy:
Shadow:
If you are planning to clone
If you are planning to clone a system with the SEP client installed, you might run into issues due to the Hardware ID on the client, the best workaround is to clone a machine with an Unmanaged SEP client and then make it managed by replacing the sylink.xml
Never have had to do that
Never have had to do that with any build, any image. Simply deleting that key, or rather, those keys, has always worked. Of course, you need to shut-down the computer right away.
Having then deal with copying a file is a more complex solution - and not needed. (almost all of our clients go into the same group, so there is no reason for us to copy any files)
I'd only ever go to all that work copying the file if you needed to change groups, otherwise, the SIMPLE fix is delete the keys........ and be done.
Personal sites -> http://theamcpages.com and http://antique-engines.com
Toy:
Shadow:
OK forget the cloning...
Forget cloning for a minute...what happens/what needs to be done in this scenario?
For example: PC1 is in use and everything is %100. PC1 is in the 'Desktops' OU. At some point PC1 is re-imaged and put back on the network with the same name and it shows up in the default group and will not move back to the 'Desktops' OU because the old PC1 is still listed there.
Thanks
Sutton
Hi
You need to follow this document , so that it creates "new" object of the same name in the SEPM database
https://www-secure.symantec.com/connect/forums/move-client-group-active-directory
Rafeeq
Would you like to reply?
Login or Register to post your comment.