I realize that Sysprep
is the recommended tool for preparing a computer for duplication, but I'm trying to achieve the same result without using it. I used Casper
to clone the SSD of a W7 Pro 64-bit laptop to a new SSD and then placed the new SSD into a new laptop with identical hardware. The new laptop works perfectly with the cloned drive.
I will change product/license keys on the new laptop where necessary (including the Windows product key) so that all software is legally licensed and activated. I will also change the Computer Name via Control Panel>System so that the two laptops don't have the same name. They don't use a fixed IP address, so that shouldn't be an issue.
I've read a lot on the web about the SID debate, including that Mark Russinovich has retired NewSID (NTSID)
. He ends that blog article by saying, "Note that Sysprep resets other machine-specific state that, if duplicated, can cause problems for certain applications like Windows Server Update Services (WSUS), so Microsoft’s support policy will still require cloned systems to be made unique with Sysprep". But I'm wondering how the experts here feel about it. Will the two machines (on the same workgroup, not
on a domain) have any problems being on the same network? Are there changes other than the ones I mentioned above that I should make in order to avoid conflicts? Thanks, Joe