I am hoping someone can help me out with the task sequence I have been working on to do in-place upgrades from Windows 7 x64 Enterprise to Windows 10 x64 Enterprise using MDT 2013 update 2.There are two problems that I am running into after the upgrade (which shows that it was successful).The first is after the upgrade I log-in to my user account I will get a few MDT wizards that pop up momentarily and then go away, if I don't have the windows MAK being set during the upgrade.
The final line in the says FAILURE (Err): -2147024770 0x8007007E: Create Object(Microsoft. Utility) Now this wouldn't be that big of an issue since the upgrade seems to have completed successfully otherwise.But then after every reboot it tries to continue the task sequence and pops up with the error about a dirty environment.To remedy that I can run the cleanup script or delete those files and then the script in the startup folder.But this seems like a poor fix, when I think there may only need to be a little tweak to my task sequence to get it to run successfully.The second issue is that if I do have the MAK being set during the upgrade, I get a pop-up saying that the current user doesn't have admin rights (which it does).
Now I have looked around and seen that if I run the litetouch script from the .\Administrator account with UAC turned off this isn't an issue, but the local admin account is disabled on all of our computers and UAC is turned on.
The fix that they talk about on MDT page says to add the Skip Final Wizard=YES variable, which I have but it seems to be getting ignored and the upgrade is not completing. Ideally I would like to know for the second case why the Skip Final Wizard=YES variable isn't applying.
I have tried adding that in both the task sequence and custom settings with no luck.
Or maybe it is and I'm missing something else entirely.
There are numerous tools provided by Microsoft to deploy Windows; however, I see a lot of confusion and questions about which of these tools to use, when to use it, and what the roles of each of them are.
This is the baseline set of tools provided by Microsoft to perform the atomic operations involved with deploying Windows: things like creating and modifying a Windows image, creating and updating a Windows PE boot image, and creating answer files.