none
MDT runonce RRS feed

  • Question

  • In need of help!

    I have a windows 10 image prepared and tested via MDT. Next I would like to create\execute the runonce for all new users that log on to set IE11 setting and to run Onedrivesetup (NOTE: OneDriveSetup.exe installs OneDrive only within the current user account. OneDriveSetup.exe will need to be run once per each user account on the machine).

    I have used these step within windows 10 and tested with a few new users; this process worked!

    01)  Open regedit

    02)  Go to HKEY_USERS

    03)  Load Hive

    04)  Browse to C:\Users\Default User\ntuser.dat

    05)  Give it a temporary key name, for example Test

    06)  Go to HKEY_USERS\Test\Software\Microsoft\Windows\CurrentVersion

    07)  Create a key RunOnce

    08)  Create a string value there eg: First Run, then change the value to where your script sits, eg: "C:\temp\IE_trustedsites.reg"

    09)  Create a string value there eg: Second Run, then change the value to where your script sits, eg: "C:\temp\One_Drive.bat"

    10)  Go back to HKEY_USERS\Test

    11)  Unload the hive

    12)  Log on with new user

     

    Can this be done during MDT deployment or as registry push during MDT post application? Are there other recommended suggestions?

    Thanks in advance for the assistance.

    Thursday, April 21, 2016 4:21 PM

Answers

  • Active setup is how you should handle this: http://www.itninja.com/blog/view/an-active-setup-primer

    Many questions such as where do I find logs and what logs are interesting are found in: <a href="https://social.technet.microsoft.com/Forums/en-US/ef0a9119-63b6-45ae-a871-866ea62ee3e8/mdt-technet-forum-faq-getting-started-guide?forum=mdt"> MDT TechNet Forum - FAQ & Getting Started Guide</a> Please take the time to read it.

    Thursday, April 21, 2016 4:51 PM
    Moderator
  • This is roughly what was done:
    https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-mdt-2013-update-1-and-hideshell/

    You might try removing the added registry keys.  That being said to definitively determine what is causing a long logon you would want to look at doing a xperf trace.


    Many questions such as where do I find logs and what logs are interesting are found in: <a href="https://social.technet.microsoft.com/Forums/en-US/ef0a9119-63b6-45ae-a871-866ea62ee3e8/mdt-technet-forum-faq-getting-started-guide?forum=mdt"> MDT TechNet Forum - FAQ & Getting Started Guide</a> Please take the time to read it.

    Thursday, April 21, 2016 9:10 PM
    Moderator

All replies

  • Active setup is how you should handle this: http://www.itninja.com/blog/view/an-active-setup-primer

    Many questions such as where do I find logs and what logs are interesting are found in: <a href="https://social.technet.microsoft.com/Forums/en-US/ef0a9119-63b6-45ae-a871-866ea62ee3e8/mdt-technet-forum-faq-getting-started-guide?forum=mdt"> MDT TechNet Forum - FAQ & Getting Started Guide</a> Please take the time to read it.

    Thursday, April 21, 2016 4:51 PM
    Moderator
  • Thanks for the quick response:

    I ran the example in the link you provided and it worked as it should. This was the message I get during the wait “It's taking a bit longer than usual but it should be ready soon”. It went from a quick login to about 20 minutes before seeing the executed test. 

    My questions are: Is this a problem? Can it be sped up?

    I doubt this is an issue but please note that I am testing in VM environment.

    Thursday, April 21, 2016 6:15 PM
  • What OS? There is some stuff added to Windows 10 so that HideShell works.

    Many questions such as where do I find logs and what logs are interesting are found in: <a href="https://social.technet.microsoft.com/Forums/en-US/ef0a9119-63b6-45ae-a871-866ea62ee3e8/mdt-technet-forum-faq-getting-started-guide?forum=mdt"> MDT TechNet Forum - FAQ & Getting Started Guide</a> Please take the time to read it.

    Thursday, April 21, 2016 6:21 PM
    Moderator
  • Windows 10 Ent.

    Thank you

    Thursday, April 21, 2016 6:30 PM
  • This is roughly what was done:
    https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-mdt-2013-update-1-and-hideshell/

    You might try removing the added registry keys.  That being said to definitively determine what is causing a long logon you would want to look at doing a xperf trace.


    Many questions such as where do I find logs and what logs are interesting are found in: <a href="https://social.technet.microsoft.com/Forums/en-US/ef0a9119-63b6-45ae-a871-866ea62ee3e8/mdt-technet-forum-faq-getting-started-guide?forum=mdt"> MDT TechNet Forum - FAQ & Getting Started Guide</a> Please take the time to read it.

    Thursday, April 21, 2016 9:10 PM
    Moderator
  • I figured out the problem with “It's taking a bit longer than usual but it should be ready soon”. Hopefully this will help someone in the future. It was the test with notepad.exe, job cannot complete until notepad is closed. Eventually “It's taking a bit longer than usual but it should be ready soon” time-out and notepad is sitting there. Close notepad and job is completed.  

    Tested with OneDrive setup, it working as it should because no user input was required “no Hanging”. I added a registry to active setup and it hangs just like notepad again waiting for user input. In need of a script or a registry edit that will run silently “no user input”. Any help would be appreciated?

    Friday, April 22, 2016 4:07 PM
  • There are two things here. Have you looked at both links I provided?

    Many questions such as where do I find logs and what logs are interesting are found in: <a href="https://social.technet.microsoft.com/Forums/en-US/ef0a9119-63b6-45ae-a871-866ea62ee3e8/mdt-technet-forum-faq-getting-started-guide?forum=mdt"> MDT TechNet Forum - FAQ & Getting Started Guide</a> Please take the time to read it.

    Friday, April 22, 2016 4:48 PM
    Moderator
  • I did! Let me go back and re-read, let me see what i missed.

    Thanks

    Friday, April 22, 2016 5:28 PM
  • I did miss a piece, working. Thank you


    Friday, April 22, 2016 7:20 PM