This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
Hey everyone,
first and foremost: I'm fairly new to MDT but as of now I feel like I have a solid grasp on what to do or where to find out what to do.
Since our Client does not currently have a Windows Server and the Hardware would not support us setting up one, we decided to go with Local User Accounts and to deploy / configure the Laptops using a VM on our Server instead.
So far I've gotten most things to work, but I have been trying to make it, so my Custom Tasks (mostly basic CMD Commands, some reg edits and a few PS scripts) are being executed as the user "Owner" (which is part of the local Admin Group) instead of the build in Administrator account.
When i change the AutoLogon Component inside the unattended.xml of my Task Sequence I indeed get logged into the right user during deployment, but it does not continue the Task sequence from there (I assume it fails to run LTIApply.wsf)
I have also had no success setting the user in the "Run As" box of my "Run Command Line" Tasks, i assume this is because some of them require Admin privileges.
The FirstLogonCommands Component in the unattended.xml were also with little to no success.
There has to be something I'm missing here
Thank you for the help in Advance
Kind Regards
Niclas
Daily attempt of trying to answer to this thread #5
I have figured out what i did wrong:
I have imported the script as an application without source files, so instead of in the Applications folder the file was in the %SCRIPTROOT% directory.
Doing that i crippled the ability for the script to reference the VBS file.
I fixed this by editing the script
In conclusion: you were right I did miss something, thank you!
Heyy i didn't get the no access error for once!
Thank you very much for the update and we're glad the problem is solved now. We believe this will be very beneficial for other community members who have similar questions.
Try follow this and see if you may have missed anything https://www.deploymentresearch.com/running-the-mdt-2013-update-2-task-sequence-as-a-different-user/
Thank you for your response
I followed this Tutorial before with no success. I think my problem in understanding lays in the source that I do not want to use a domain user. As I've looked through the post again today to make sure I didn't make a mistake I realized the first comment by User Geoni asked what applies to me aswell:
"How do I run MDT Task Sequence under different local admin account already apart of my image?"
The Authors response was to use the Computer Name (hostname i assume) as Domain name.
Is this the correct way of doing so?
APPINSTALLDOMAIN=%_SMSTSMachineName%
Secondly i should not have to worry about the part with Administrator001=... since I'm creating my user (in my unattended.xml) as already a member of the group Administrators, correct?
Edit: The UserAccounts Component is in step 7 oobeSystems if that is of any help
As of now the Task Sequence continues to be run as Administrator after the reboot.
As a shot in the dark try APPINSTALLDOMAIN=%OSDComputername%
If this doesn't work, send through the smsts.log.