Daleus Posted September 23, 2008 Posted September 23, 2008 I recently took over as the Techie for a primary school after the old guy left. Nothing in terms of imaging was kept, So I'm hoping to image one of the already working Machines in the IT Suite and just change its name and rejoin it to the domain, would that be possible? Imaging is the easy part, the part I think may cause trouble is the active directory. The reason I don't want to make up a fresh vanilla image is because there's a lot of software installed on the machines that would take ages to reinstall, some of it even has missing installation media. Does anyone have any tips or ideas for me?
tmcd35 Posted September 23, 2008 Posted September 23, 2008 I'd disconnect it from the domain, sysprep then image it. Once the image is complete it's a trivial task to re-add the machine to the domain.
tosh74 Posted September 23, 2008 Posted September 23, 2008 If you are going to image a machine that is already part of the AD domain then you will need to run newsid (NewSID v4.10) on every machine you build from that image.
tmcd35 Posted September 23, 2008 Posted September 23, 2008 Sysprep should do the SID for you, and if correctly configured automatically join any new machines based on that image to the domain. All you need to do is give the new machines a name during it initial boot.
tosh74 Posted September 23, 2008 Posted September 23, 2008 Sysprep should do the SID for you, and if correctly configured automatically join any new machines based on that image to the domain. All you need to do is give the new machines a name during it initial boot. Right enough but I read from the OP entry that they would be using Ghost (or some similar imaging software) rather than WDS (which would be my preferred solution).
tmcd35 Posted September 23, 2008 Posted September 23, 2008 Yep we do this here. Unjoin the machine from the domain. Run Sysprep. Make a ghost image of the Sysprep'd drive. And away you go.
powdarrmonkey Posted September 23, 2008 Posted September 23, 2008 Right enough but I read from the OP entry that they would be using Ghost (or some similar imaging software) rather than WDS (which would be my preferred solution). Sysprep doesn't care how you image, just that you use it. It's far preferable to newsid.
FN-GM Posted September 23, 2008 Posted September 23, 2008 If you are going to image a machine that is already part of the AD domain then you will need to run newsid (NewSID v4.10) on every machine you build from that image. we use this batch script as a start-up script net stop wuauserv REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f net start wuauserv wuauclt /resetauthorization /detectnow
DMcCoy Posted September 23, 2008 Posted September 23, 2008 we use this batch script as a start-up script net stop wuauserv REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f net start wuauserv wuauclt /resetauthorization /detectnow My syspreped machines don't have a accountdomainsid, pingid and the susclientid's are also different.
tosh74 Posted September 23, 2008 Posted September 23, 2008 (edited) Sysprep doesn't care how you image, just that you use it. It's far preferable to newsid. Pardon ? If you read my entry it explains that I thought the OP was using Ghost instead of WDS. My accent must make me sound stupid Edited September 23, 2008 by tosh74
Daleus Posted September 23, 2008 Author Posted September 23, 2008 Thanks for replies guys, and yeah We'll most likely be using ghost. I think the best option is to just d/c the machine, image it and reconnect it, I don't mind joining the new ones to the AD manually or messing with the SID. i'll start a machine imaging on friday night Thanks for all the help
powdarrmonkey Posted September 23, 2008 Posted September 23, 2008 Pardon ? If you read my entry it explains that I thought the OP was using Ghost instead of WDS. Your two posts together implied that you were choosing to use newsid over sysprep because the OP is using Ghost not WDS. My assertion is that it doesn't matter, it's advised to use sysprep whether you're then going to image with Ghost or WDS.
john Posted September 23, 2008 Posted September 23, 2008 we use this batch script as a start-up script net stop wuauserv REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f net start wuauserv wuauclt /resetauthorization /detectnow Surely thats just removing the Windows Update IDs and flags not the whole machine SID
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now