Hi guys while doing a specific USMT capture TS that users run themselves via a shortcut (to prestage a new laptop we are building for example), is there a simple way to get the currently logged in user ID into MDT.
If possible I would like to inject it directly into the customsettings.ini from the batch/script/shortcut being used, in whch case my basic flow will be -
- If the shortcut is run, current user injected in as UDDIR=%currentuser% etc then it is a completely automated USMT TS.
- If it is run from litetouch.vbs, %currentuser% doesn't exist proceed to normal wizard etc.
I'm pretty positive I could do it with a script later on in the TS but this seems like the simplest way to do it.
I basically want to name the scanstate location as the current user (instead of the computer as it currently is).
You cannot use %currentuser% or %username% in Cs.ini
Have a look at this thread and reply from Michael which would be an easy way.
Regards, Vik Singh
For in-place deployment, create a shortcut like this:
Actually just testing now and it seems that any parameters I'm passing through the command line are getting picked up, but getting overwritten by the CS.INI.
For example my command is :
\\server\Deployment$\scripts\LiteTouch.vbs /UDDIR:%USERNAME% /SkipTaskSequence=YES /TASKSEQUENCEID=BACKUSER /SKIPWEDDERBURN:YES
And BDD.log is reporting correctly, however as part of the USMT TS all of the settings are being overwritten. Do I have to add something to the PRIORITY in the CS.INI?EDIT : As a workaround I could use a custom CS.INI file which does not include these settings I suppose?
- Edited by mhouston100 Tuesday, March 13, 2012 9:33 PM