Sysprep affecting i...
 
Notifications
Clear all

Sysprep affecting install dates on local machines?

2 Posts
2 Users
0 Likes
1,021 Views
Adam10541
(@adam10541)
Posts: 550
Honorable Member
Topic starter
 

I'm examining a number of laptop images and among other details I'm looking for Windows OS install date, shutdown etc and I've come across references to Sysprep which is leading me to suspect that these machines were all installed via sysprep in a domain environment.

I'm wondering if anyone has had experience with Sysprep and how it might effect the information in the registry of the local machine regarding it's date of installation.

 
Posted : 10/07/2015 8:21 am
jaclaz
(@jaclaz)
Posts: 5133
Illustrious Member
 

Windows OS? 😯

There may be differences even in the version of Sysprep used, but certainly there are between (say) XP, Vista, 7 or 8/8.1 and between the zillion SKU's (whatever is a SKU, like OEM, SLC enabled, Retail, VLK etc.) .

Assuming (as an example) Windows 7, this is a detailed enough guide to the process
http//www.symantec.com/connect/blogs/windows7-untangling-scripted-installs-sysprep-and-configuration-passes
as you can see there are a numbers of options or if you prefer possible bifurcations, so it is hard to say which particular artefacts are created during deployment with the one (or the other) method.

The good news being that the good MS guys like a lot to re-use code, so this article
https://support.microsoft.com/en-us/kb/216680
still applies (at least up to 7 or MDT2010), and the HKEY_LOCAL_MACHINE\System\Setup\CloneTag still holds the date the image was prepared, see also
http//www.thewindowsclub.com/the-system-preparation-tool-sysprep-in-microsoft-windows-7

jaclaz

 
Posted : 10/07/2015 8:14 pm
Share: