xnalax Posted September 7, 2010 Report post Posted September 7, 2010 hi, i have an osd task sequence, i have a "run command line" step, is it possible to make the step visible? i am calling miscsettings.cmd and inside the *.cmd i am calling a vbs script. so i want to debug the script. thanks Quote Share this post Link to post Share on other sites More sharing options...
0 Peter van der Woude Posted September 7, 2010 Report post Posted September 7, 2010 To fine-tune your script, just first try it by starting it without intervention of ConfigMgr, then try it as a Software Package and when that works put it in a Task Sequence. Quote Share this post Link to post Share on other sites More sharing options...
0 xnalax Posted September 7, 2010 Report post Posted September 7, 2010 it works when a user is logged on. but other settings from the script are applied, if fails when i am setting AutoAdminLogon=1, it runs with the system account so no security issue? or is there another way to enable AutoAdminLogon? i tried to set it also in the unattend.xml also not working it is a windows 2008 r2 osd thanks Quote Share this post Link to post Share on other sites More sharing options...
0 anyweb Posted September 7, 2010 Report post Posted September 7, 2010 as above, plus you can test it using psexec in System Context you can autologin using the method described here http://www.windows-noob.com/forums/index.php?/topic/1543-how-can-i-capture-windows-7/ Quote Share this post Link to post Share on other sites More sharing options...
0 xnalax Posted September 7, 2010 Report post Posted September 7, 2010 is there a way to make the run commandline step visible? Quote Share this post Link to post Share on other sites More sharing options...
0 xnalax Posted September 8, 2010 Report post Posted September 8, 2010 hi the problem was that the sccm agent is a 32 bit app and i deployed 64bit os, and my reg settings gone to 32bit registry path and so the auto admin logon never worked. i solved it by writing the values in the 64 bit registry Quote Share this post Link to post Share on other sites More sharing options...
0 anyweb Posted September 8, 2010 Report post Posted September 8, 2010 nice, please post the registry file here (remove password) so that others can benefit Quote Share this post Link to post Share on other sites More sharing options...
0 xnalax Posted September 8, 2010 Report post Posted September 8, 2010 nice, please post the registry file here (remove password) so that others can benefit i took this solution http://nocentdocent.wordpress.com/2010/04/11/osd-how-to-build-a-single-task-sequence-for-windows-7-x64-and-x86/ i just replaced the WshShell.RegWrite function with the PRG_RegWrite function. Quote Share this post Link to post Share on other sites More sharing options...
hi,
i have an osd task sequence, i have a "run command line" step, is it possible to make the step visible?
i am calling miscsettings.cmd and inside the *.cmd i am calling a vbs script.
so i want to debug the script.
thanks
Share this post
Link to post
Share on other sites