Deployment Artist
   Minimize

 

The deployvista.com site is finally put to rest...

You find new content on the Deployment Research site, a site filled with articles and video-tutorials on how to deploy operating systems. If you are missing something on the new site, please let me know. You can find me on twitter on my @jarwidmark alias.

You can also search the old deployvista.com article archive below.

Regards / Johan Arwidmark


 Print   
 Blog_List Minimize

 Print   
 Blog_Archive Minimize

 Print   
 New_Blog Minimize
You must be logged in and have permission to create or edit a blog.

 Print   
 Pushing MDT 2010 Lite Touch installations to remote clients... Minimize
Location: BlogsJohan Arwidmark    
Posted by: johan 1/17/2010

To start a MDT 2010 Lite Touch installation remotely, e.g. without having to visit the machine, you can use the psexec tool (Microsoft / Sysinternals).

In my sample the remote PC is named PC0004 and my deployment server is MDT01. The deployment share is MDTProduction$ and the user account I use for my installations is TSLAB\BuildAccount. That account has administrator rights on the PC0004 machine.

  1. On MDT01, configure the rules (bootstrap.ini and customsettings.ini) on the deploymentshare so that the refresh installation process is fully automated. Below you find a fully automated sample rule set.
     
    Bootstrap.ini
     
    [Settings]
    Priority=Default
     
    [Default]
    SkipBDDWelcome=YES
    DeployRoot=\\MDT01\MDTProduction$
    TaskSequenceID=W7-X86-002
     
    UserDomain=TSLAB
    UserID=BuildAccount
    UserPassword=P@ssw0rd
     
     
    Customsettings.ini
     
    [Settings]
    Priority=Default
     
    [Default]
    _SMSTSORGNAME=TSLAB
    OSInstall=Y
    DeploymentType=REFRESH
    SkipDeploymentType=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerName=YES
    SkipDomainMembership=YES
    SkipUserData=YES
    UserDataLocation=AUTO
    SkipLocaleSelection=YES
    SkipTaskSequence=YES
    SkipTimeZone=YES
    SkipApplications=YES
    SkipBitLocker=YES
    SkipSummary=YES
    SkipBDDWelcome=YES
    SkipComputerBackup=YES
    ComputerBackupLocation=NONE
    SkipCapture=YES
    SkipFinalSummary=YES
    TimeZone=004
    TimeZoneName=Pacific Standard Time
     
    JoinDomain=TSLAB
    DomainAdmin=TSLAB\JoinAccount 
    DomainAdminPassword=P@ssw0rd
    MachineObjectOU=ou=Workstations,dc=tslab,dc=net
     
    WSUSServer=http://MDT01
     
  2. Make sure the account used has administrator rights on PC0004. Can be achieved in many ways, I normally use Group Policy and the restricted groups feature to remotely add members to the administrators group on the clients.
     
  3. If the firewall is enabled on PC0004, make sure that the File and Printer Sharing exception is allowed. I use Group Policy for that too.
     
  4. On MTD01, download the PSTools package from Microsoft, extract it, and copy psexec.exe to C:\Windows\System32.
     
  5. On MDT01, in a command prompt (or via a batchfile), execute psexec.exe \\PC0004 -u TSLAB\BuildAccount -p P@ssw0rd cscript.exe \\MDT01\MDTProduction$\Scripts\litetouch.vbs

 / Johan

 

Permalink |  Trackback

Comments (2)  
Re: Pushing MDT 2010 Lite Touch installations to remote clients...    By jhiltabidel on 10/22/2010
I've tried this several times and I suppose it's a user error on my part. I get the below error messages (last two lines). Any advice?

_________________________________________________________
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

\\mdt01.fu.campus\deploymentshare$\scripts\litetouch.vbs(78, 1) (null): This operation requires an interactive window station.

cscript.exe exited on Lab-Lib042-11.fu.campus with error code 0.
_________________________________________________________

I have turned the firewall completely off on the client machine (Lab-Lib042-11) and get the same results. I have confirmed Admin status for the username used and psexec is in the windows\system32 folder.

Thanks,

Joe

Re: Pushing MDT 2010 Lite Touch installations to remote clients...    By jhiltabidel on 10/22/2010
Resolved by adding -i after psexec.exe. So the complete command line looks like this for me:
psexec.exe -i \\Lab-Lib042-11 -u Domain\Useraccount -p P@ssw0rd cscript.exe \\MDT01\DeploymentShare$\Scripts\litetouch.vbs


  
 Search_Blog Minimize

 Print   
Copyright Deployvista.com 2006-2012 (c)   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2017 by DotNetNuke Corporation