ScanStateArgs=/v:5 /o /c
TimeZoneName=GMT Standard Time
Here is the link to the Logs from the machine:http://sdrv.ms/149f4Nu
- Edited by Kevin Gosney Wednesday, June 26, 2013 7:50 AM
First off, you should be running LiteTouch.vbs, not LiteTouch.wsf. LiteTouch.vbs will call LiteTouch.wsf when it is ready, so calling the VBS directly may cause things not to work fully as intended. Is the Restore the only thing not running after the WIM is layed down and the machine rebooted, or does it not run anything else after that point? Can you look at the LoadState logs directly and see if there is an issue?
Thanks for your reply, sorry for the mistake i did mean the LiteTouch.vbs and not the .wsf file. Regarding the running after the wim has been laid down it reboots the machine boots back up and finishes the setup. It even comes up in the list about restoring user data and then comes up the report screen saying that it has finished. However when you check the Users folder there is no data been restored.
Can you validate that files are showing up in your folder: \\Server.domain\usmt\Profile\User\%OSDComputerName%?
Also, I don't believe you want UserDataLocation set to a UNC when you are also specifying UDShare / UDDir. In the case of those being specified, UserDataLocation should be set to NETWORK.
Hi I can confirm that the files are there and once windows has been build I can locate the files on the network and double click the files manually to restore the user data. It then opens the Windows Easy Transfer Wizard to do so.
However this is not the automated experience that I am aiming to achieve.
I do not see a USMTrestore.log in your files, so loadstate is not running for some reason. You should add the /c flag to the LoadStateArgs line.
Do you have a standard client task sequence created with the ID of WinPE? If you are doing a RESTORE task sequence you should have a REPLACE task sequence which I do not see configured in your customsettings.ini file.
- Edited by Squeezer999 Wednesday, June 26, 2013 4:56 PM updated
I made the change but all that did was to default the option to Network selection but leave it blank. I have since moved the option back.
I believe that the issue is now laying with permissions, when the machine builds it logs in with the local admin details to finish, as a result this account doesn't have access to the share where the data is stored.
I have tried to allow the access and the only way that i can see of doing this is by having a service account to login with which has permission to the share.
The issue that I have now is having the Windows Deployment log in with this service account to finish the install, do you know what options to change for this?
http://scriptimus.wordpress.com/2011/05/25/mdt-2010-user-state-migration/ this link will provide full information.
The easiest is to make the UNC share where you are putting the data allow read/write for Everyone, not Authenticated Users. This should allow the local admin running MDT to access it, despite it not being a domain account (and hence not authenticated). These permissions need to be both on the share and the NTFS for the files themselves, of course.