We are running a MDT 2012 update 1 system and now, after 3 syspreps of the same image appear to have run into the sysprep limit. I know there are "better" ways to make images that don't run into this problem, but they are not an option for our setup here sadly. In my research though, I find stuff like this: http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/1a255b2f-9afa-4960-a8a4-f6b7b6b68564/
which seems to indicate if you are running a KMS setup then one should not be hitting the sysprep limit. We are running a KMS setup and are hitting this limit. So my only conclusion is that my belief it is a limit of sysprep must be wrong? What kidn of logs are info would you guys need to help figure out what is going wrong?
What is occuring is the latest build I sysprep'ed and captured went fine. When I go and deploy that image via MDT, it deploys correct in the PE but when it reaches windows, it sits at the login screen (where you press ctrl+alt+del). When you try and login manually, the administrator account has been locked out. You can re-enable it by going into safe mode, but my research indicated this was due to the sysprep limit. Even when I do unlock the account and get into windows, the PC is showing it has been activated correctly so the KMS server is still working then.
Thanks!