| 193 |
| Identify systems that were cloned with Sysprep |
| Systems cloned with the Sysprep cloning utility occasionally experience specific problems. Because |
| of this, it's useful to be able to recognize systems that were cloned using Sysprep. Identification |
| can be the first step in troubleshooting a particular problem. |
| If a system was cloned with Sysprep, several indicators will exist. To locate these identifiers, open |
| the Registry Editor and browse to the following registry key: |
| HKEY_LOCAL_MACHINE\System\Setup |
| Here are a few things that you'll look for: |
| A CloneTag value, which identifies the date and time Sysprep ran. |
| A cmdline value set to "Setup -newsetup -mini." This value causes Setup to use the mini-wizard |
| An OemDuplicatorString value, which contains information added by an OEM during system |
| cloning. (Since this value is optional, not all systems will include it.) |
| In addition, when you're looking for indicators that Sysprep was used to clone a system, look for |
| Setupcl.exe in the %systemroot%\System32 folder. Setupcl.exe is used to change security IDs |
| (SIDs) on the computer after cloning, which is necessary to prevent duplicate SIDs on multiple |
| Searching for these indicators will help you quickly identify cloned systems and get you on the |
| right troubleshooting path. |
| Note: Editing the registry is risky, so make sure you have a verified backup before saving any |
First Previous Next Last |