Call litetouch.vbs from PXE booted WinPE

I'm not sure if anyone has tried this, but I thought I'd ask. What I'm trying to do is call litetouch.vbs which is sitting on an MDT distribution share from WinPE. I can call litetouch.vbs and pass in my paramaters to run a task sequence, but the task sequence
stops before it runs setup to deploy the OS.
I'm guessing this has to do with some of the info that's being gathered from the scripts and task sequence variables. Has anyone tried this and/or know what would need to be changed to be able to launch MDT from the share instead of from the content on the
MDT iso?
Thanks,
Rich

litetouch.vbs is included in the Litetouch WinPE image.
When you call it, it runs the ztigather.wsf script looking at the bootstrap.ini file. THe bootstrap.ini file will point to the correct DeployShare over the network if necessary, and the rest of the scripts will run correctly over the network.
What are you trying to accomplish?
Keith Garner - keithga.wordpress.com
Sorry I haven't gotten back to this sooner, but I was out of the office yesterday.
I'm trying to boot from a generic PE image via PXE and then automate different types of server builds. Without derailing this too much, what we're doing isn't conducive to using MDT with a database so we're using a different tool manage what gets built/rebuilt.
What I was trying to do is similar to a post OS install task sequence where you'd call litetouch.vbs sitting on a deployment share. The PE image would run a command to get it's install script that gets dynamically generated for it. I was trying to then call
litetouch.vbs with parameters sitting on the deployment share. The issue is that it didn't like that very much. It behaved differently every time I ran it. Sometimes it would format the disk and then just stop. Other times it would skip the INSTALL phase and
say it was complete, even though phase got set to INSTALL. I really couldn't figure out why this was happening.
We've since moved on to using DISM to install an OS with a dynamically generated unattend.xml and then calling an MDT post os install task sequence, but it would still be good to know if it's possible to do it the other way too.
Thanks,
Rich

Similar Messages

Format and Partitoin Disk - Difference Between Running TS/LiteTouch.vbs from Desktop Vs. Bootable Flash Drive.

Hello,
I have a question about disk formatting. If run our TS from the Run box, the HD is not cleaned. The image will be applied successfully but if there were any extra partitions, HP Recovery partitions for example, they will still be present.
If run the same TS form a bootable USB drive, the HD is completely erased.
Can anyone explain the difference in running the TS from the Desktop/Run box vs. running it from a bootable drive?
Thanks.

From LiteTouch.log, the DeploymentType is NEWCOMPUTER when run off the flash drive but REFRESH when run from the desktop. LT must detect that its running in an OS and decides not to clean the drive. We do not have DeploymentType set in our
rules.
Ah, glad you found it. That's what I was going to suggest, based on what environment the TS runs from.
-Nick O.

PXE boot fails and reboots after loading PE

I have run into what I think is a unique issue and need some help determining the cause.
We are in the process of replacing and aging DP/PXE point (2003 R2 SP2) with a new server (2008 STD R2 SP1). What makes my pxe issue unique is that pxe works without issue on the existing 2003 DP/PXE server. But on the new 2008 server I run into
the following issue.
Environment: Config Manager 2007 R2, a single primary, multiple DP's and PXE points.
Issue: When I attempt to PXE boot a system, I am able to load PE, but shortly after the custom background screen is loaded, the system reboots. I've searched the internet quite a bit and found lots of potential causes including, bad/missing drivers,
certificate issues, rights issues, etc. None of these seem to be the cause.
My troubleshooting has determined that the client computers are unable to download the variables.dat file. I just don't know why.
We're using the same boot images on both servers.
I've tried using multiple computer models and VM's.
I've opened a command prompt as soon as our background image loads and have verified that the system is pulling a valid IP address. I am able to map a drive to the PXE server's REMINST share using our sccm net access account and manually copy the .var
file using xcopy to the appropriate directory on the local virtual drive. I've also attempted to manually run smstftp.exe by mimicking the command line from the smsts log file. I'll admit that I'm not sure I have the correct syntax for smstftp.
I've tried several variations and all but one result in a short pause and no file copied/created in the X:\sms\data folder. The one that does produce a result says that the file cannot be found. I checked for typos and made sure I used the name
of the newly created .var file.
I've also tried disabling anti-virus on the server, shutting off the windows firewall on the server, granting everyone read rights to the REMINST share.
Below is the smstslog file I've been using as a reference. Per corporate security policy, I have X'd out the IP address of the PXE server. The log file for the successful pxe boot from the 2003 server shows an exit code of 0 for smstftp.exe, a note
about successful download of the pxe var file and then it continues through the rest of the boot process.
-----SMSTS log file from a failed PXE boot on the new 2008 server -----
<![LOG[LOGGING: Finalize process ID set to 832]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="tslogging.cpp:1489">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836"
file="bootshell.cpp:963">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="util.cpp:869">
<![LOG[Debug shell is enabled]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:974">
<![LOG[Waiting for PNP initialization...]LOG]!><time="16:13:54.471+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:59">
<![LOG[Booted from network (PXE)]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="configpath.cpp:198">
<![LOG[Found config path X:\sms\data\]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:553">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:564">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:767">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:850">
<![LOG[Successfully launched command shell.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
<![LOG[The command completed successfully.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
<![LOG[Starting DNS client service.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:597">
<![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880"
file="bootshell.cpp:767">
<![LOG[The command completed successfully.]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932"
file="tsmbootstrap.cpp:1039">
<![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932"
file="tsmbootstrap.cpp:1040">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="util.cpp:869">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="resourceutils.cpp:152">
<![LOG[Processor Is IA64: 0]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1005">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:921">
<![LOG[Executing from PXE in WinPE]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstrap.cpp:936">
<![LOG[Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1319">
<![LOG[TsPxe.dll loaded]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1329">
<![LOG[Device has PXE booted]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
file="tspxe.cpp:134">
<![LOG[Variable Key Len: 61]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:141">
<![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:123">
<![LOG[Executing: X:\sms\bin\i386\smstftp.exe -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.004+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:14:42.067+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:229">
<![LOG[Set command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:805">
<![LOG[Process completed with exit code 1]LOG]!><time="16:15:29.179+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:1102">
<![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:146">
<![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
file="tspxe.cpp:185">
<![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tspxe.cpp:185">
<![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tsmbootstraputil.cpp:1419">
<![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context=""
type="0" thread="1932" file="tsmbootstraputil.cpp:1420">
<![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2236)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tsmediawizardcontrol.cpp:2236">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe"
context="" type="0" thread="1932" file="tsmbootstrap.cpp:937">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
component="TSPxe" context="" type="0" thread="1932" file="tsmbootstrap.cpp:1106">
<![LOG[Exiting with return code 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1118">
<![LOG[Execution complete.]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:624">
<![LOG[Finalizing logging from process 832]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1578">
<![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="16:15:29.491+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1803">
This has been an extremely frustrating issue and any assistance would be greatly appreciated!

Thanks for your quick response Jason! I didn't expect someone to reply so quickly or I would have checked back sooner.
I had found the two 'older' posts already, but had not seen the 'newer' one. Unfortunately that did not give me any new ideas. But your comment on checking for TFTP availability did. Here are things I have tried since my original
post...
I re-ran most of my tests in case I missed something. I only found one change. Even though I double-checked, I must have made a typo when I manually ran the smstftp.exe command, because when I ran it again I received a timeout message instead
of file not found.
I had a minor 'thinking outside of the box moment' and decided to PXE boot the new 2008 R2 server itself. This was successful and I interpreted the success as meaning that the hardware is ok. Thinking there may be a compatibility issue with
the hardware and the OS, I tried a few different NIC drivers, settings, registry keys, and even a completely different NIC. No luck on any of these.
I decided to build another Server on a VM tovalidate my build process and configuration. And of course clients in multiple locations were able to PXE boot off this VM. Too bad I can't use this in production.
After reading your response Jason, I began to focus on network. I moved the server to a few different locations so it was utilizing different switches. No luck. I noticed in the event viewer for WDS that the server was logging the
beginning of the boot.var file via TFTP. This of course was not very surprising. What was surprising is that the very next entry (informational) noted that the client 'COMPLETED' the download of the boot.var file via TFTP. I know that completed
does not mean successful, but it usually implies or is interpreted as successful. It should have logged a warning or error, or nothing at all because although the process completed, it was not successful. I re-verified that the file was not downloaded
to the client and the client log file still shows the same error noted in the logfile from my original post.
Finally, I installed sniffing software on the server and ran some captures while attempting to PXE boot. Even though I am not much of a network guy, I quickly discovered two things. First, I found the section where the client attempts to download
the boot.var file. Unfortunately I don't think the local security team will allow me to post the capture, so I'll do my best to describe what I found. It starts with a single entry where the client calls for the file via TFTP protocol. This
is followed by a series of alternating entries (all TFTP) where it looks like the server attempts to send a portion of the file, and the client sends an acknowledgement. The sending entries all have checksum errors. The checksum received on
all packets is 0x0000 and of course should be something else. There is also a shorter section below this with alternating entries where the server attempts to send ICMP packets and the client responds with TFTP acknowledgements.
The ICMP entries are all marked as Destination unreachable (Port Unreachable).
The second thing I noticed from the network capture is the a few 'Spanning Tree Protocol' entries. I my search for a solution, I remember reading several posts saying that Spanning Tree can cause this issue. When I asked, I was assured that
Spanning Tree was disabled in this environment. It made sense too, because the 2003 PXE server was functioning properly, and Spanning Tree should affect both 2003 and 2008 servers, right?
Either way I will bring my findings to the network team and see what they have to say.
Any additional thoughts or ideas???

How to execute LiteTouch.vbs file remotely?

Hi,
I am developing a VB script which executes another VB script (LiteTouch.vbs) from MDT Deployment Share
remotely. But I am not able to trigger it (triggering has no effect). On the other hand if I use the script to trigger some other script say for copy a file to some directory, it works perfectly. Could someone please help me in solving or atleast
figuring out the issue?
Client machine name: CLIENT4 and server machine name: SERVER
The scripts are as follows:
Script1 - Call.vbs
strComputer = "CLIENT4"
strCommand = "cscript.exe
\\SERVER\Deployment$\Scripts\LiteTouch.vbs"
Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set objProcess = objWMIService.Get("Win32_Process")
errReturn = objProcess.Create(strCommand, null, null, intProcessID)
When I run Call.vbs, it has no effect. The runtime engine cscript is also not initialized in the taskmanager. But when I replace the second line as 'strCommand = "cscript.exe
\\SERVER\C$\abc.vbs"' (abc.vbs say for example copies a file from one location to other) and run the Call.vbs it is executed successfully.
I have also taken care that the Deployment$ folder is accesible from the client machine CLIENT4. Again, I have also tried to map the entire Deployment$ folder on the CLIENT4 machine and execute LiteTouch.vbs, it still has not effect.
Any help on the same would be greatly appreciated.
Many thanks.
Regards, Sagar Palande

When I developed a similar program a few years ago I used the information in this kb article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;827227
Based on this article I decided to copy the executable from my computer to the root of C: on the remote computer (where the executable is to be run) using a mapped drive. Then I connected to the remote computer with WMI and used the Win32_Process
class to execute program. If the program was Test.bat, then the command was "c:\\Test.bat". Finally, I deleted the executable from the remote computer.
Your problem might be that "\" should be replaced by "\\" in the command you execute. Or, it might be necessary to copy the VBScript to the remote computer. The program I developed is linked here:
http://www.rlmueller.net/PatchInstall.htm
Richard Mueller
MVP ADSI

"Welcome to the Task Sequence Wizard" never shows on PXE boot, but does on Boot Media with prestart command

Hey guys, I have a fairly odd situation here. I have all OSD Task Sequence advertisements set to "PXE and Boot Media (hidden)" and all are optional
(not mandatory). I use a powershell form via prestart command to give the user a choice which limits what task sequences they choose. When everything is working, this process works. Unknown desktop-class systems see desktop task sequences,
and server-class systems see server task sequences.
Here's where it's different when I use different boot methods:
Boot Media
"Welcome to the Task Sequence Wizard" is presented. User hits or clicks Enter.
Powershell form is presented; user picks their task sequence
Confirmation screen is presented with the task sequence they selected (this is an OSD screen the same size as the "Welcome to the Task Sequence Wizard"
screen.
Dependency check screen is shown with a progress bar. If a package is missing from a DP, it will display an error here with the PackageID. This
looks the same as "Regular" OSD with standard non-hidden advertisements.
PXE Boot
"Welcome to the Task Sequence Wizard" is never displayed.
Powershell form is the first screen they see. They select it and it continues.
No confirmation screen is presented if the system is known; if it is an unknown system, a small dialog says there is a
*mandatory* task sequence about to be run and it will run in 180 seconds. Users can hit enter.
No dependency check screen is shown; and if a package was missing, instead of presenting an error, it simply reboots. However, if everything is there,
the process starts successfully.
While I have no problems with the first window never being displayed, not displaying the error dialog and simply rebooting is what is bothersome to me.
99% of our builds are from PXE boot.
Again, these task sequences are all 100% optional, NOT mandatory, and I've double checked this multiple times. Can anyone explain why we get different
behavior between boot media and PXE boot? Any way of getting PXE boot to "mimic" the Boot media behavior?
I followed the guide here:
http://www.mydreampage.net/2012/09/21/how-can-i-deploy-a-hidden-task-sequence-in-configuration-manager-2012-sp1/
If you see the image here:
http://www.windows-noob.com/forums/uploads/monthly_09_2012/post-1-0-29840100-1348236179.png
You'll see the "Retrieving policy for this computer..." dialog box - I never get that with PXE - just Boot Media.
Note that I am running 2012 R2, not 2012 SP1 - but I never got a chance to test this process with SP1.
Upon further experimentation, the "hidden" task sequence has nothing to do with this. If I change it to a normal, non-hidden advertisement, as
long as the "prestart" command in the boot image is used, we don't get those missing dialog boxes at all, with PXE.

Are both boot images the same for PXE and the boot media? Same package ID and all?
Boot media for us always shows the task sequence wizard first, while PXE always displays the pre-start command first.
Daniel Ratliff | http://www.PotentEngineer.com

MDT 2013 - Deleted Litetouch.vbs

Alright, well... stupid mistake on my part. I was trying to clear litetouch.vbs from the recent files on a Win10 technical preview, and without fully thinking about it, just selected it and hit delete. At the same point, the realization that it was a network
location and I was logged into the client with domain admin privileges hit me. I've searched recycle bin on both the client and the server (not there). I've checked for "previous versions" of the folder, but none available, and unfortunately our
deployment server is not part of the backup schedule.
What can I do to recover or recreate the litetouch.vbs? The .wsf is still present.
I appreciate any suggestions.

' // Copyright (c) Microsoft Corporation. All rights reserved.
' // Microsoft Deployment Toolkit Solution Accelerator
' // File: Litetouch.vbs
' // Version: 6.0.2149.0
' // Purpose: Start the lite touch deployment process
' // Usage: cscript LiteTouch.vbs [/debug:true]
'// Global constant and variable declarations
Option Explicit
Dim oShell
Dim oFSO
Dim iRetVal
Dim sCmd
Dim sScriptDir
Dim sArg
Dim sArgString
Dim sArchitecture
Dim oDrive
'// Initialization
Set oShell = CreateObject("WScript.Shell")
Set oFSO = CreateObject("Scripting.FileSystemObject")
sScriptDir = oFSO.GetParentFolderName(WScript.ScriptFullName)
For each sArg in WScript.Arguments
sArgString = sArgString & sArg & " "
Next
'Change the Architecture type from amd64 to X64 for consistency
sArchitecture = oShell.Environment("SYSTEM").Item("Processor_Architecture")
if lcase(sArchitecture) = "amd64" then
sArchitecture = "x64"
end if
' Clean up any existing C:\MININT directory
sArgString = " /CleanStart " & sArgString
oShell.Environment("PROCESS")("SEE_MASK_NOZONECHECKS") = 1
' Clean up any remnants of a previous task sequence
On Error Resume Next
iRetVal = oShell.Run("reg.exe delete HKCR\Microsoft.SMS.TSEnvironment /f", 0, true)
iRetVal = oShell.Run("reg.exe delete HKCR\Microsoft.SMS.TSEnvironment.1 /f", 0, true)
iRetVal = oShell.Run("reg.exe delete HKCR\Microsoft.SMS.TSProgressUI /f", 0, true)
On Error Goto 0
'// Check to see if the prereq's have been satisfied
sCmd = "cscript.exe """ & sScriptDir & "\ZTIPrereq.vbs"""
iRetVal = oShell.Run(sCmd, 0, true)
If iRetVal <> 0 then
oShell.Popup "This computer does not meet the prerequisites for deploying a new operating system. (" & CStr(iRetVal) & ")", 0, "Prerequisite Error", 16
WScript.Quit iRetVal
End if
'// Launch LiteTouch.wsf to do the heavy lifting
sCmd = """" & sScriptDir & "\..\tools\" & sArchitecture & "\bddrun.exe"" wscript.exe """ & sScriptDir & "\LiteTouch.wsf"" " & sArgString
iRetVal = oShell.Run(sCmd, 1, true)
' All done
WScript.Quit iRetVal
That's the entire contents of the litetouch.vbs on my MDT server. Just remake it. Additionally, make another share and just copy the script over?

PXE boot no longer working - blank cmd windows shown. If run Scripts/Litetouch file from target machine wizards runs as expected??

Hi, My MDT server no longer works as expected via PXE boot. After the target machine loads the .wim file an empty command windows is shown. I have returned the custom settings.ini and bootstrap files to default and ensured nothing is being skipped within
the task sequence within both files in hope of viewing the wizard.
However from the same target machine if I map drive to my Deploymentshare/Scripts directory and run LiteTouch file I am asked for domain credentials and the Deployment wizard is displayed asking for task sequence to be selected.
I believe this error is a result of two things:
1) I applied some windows updates to my mdt server (running on 2008 r2).
2) I was implementing changes to
ZTIWindowsUpdate.wsf which i have now returned to default settings.
I have also regenerated boot images and re added to WDS.
Any help much appreciated?
Regards,
Paul

Hi Paul,
This sounds familiar; I only encounter this behaviour with certain kinds of laptops (Latitude E65x0) but I usually just provide the "wpeutil reboot" command in the empty command window to keep things going. All other hardware is deployed with the
same task sequence and this behaviour does not occur anywhere else...
A bit obvious maybe, but did you check if there is still a "Next Phase" step present and enabled following directly after the "Install Operating System" step?

OSD: What is the difference booting into winpe from pxe/media and booting in winpe from OS/Vista?

Hi,
We have a task sequence issue. Please see
http://social.technet.microsoft.com/Forums/en-US/56d783e3-214d-4027-84c1-c03cdf2013f1/osd-convert-boot-to-logical-path-failed-0x80070490-retrying-after-attempt-29-it-fails-and-says?forum=configmanagersecurity
for more info. What I would like to know: what is the difference/is there a difference between:
A.booting in PXE/bootable media to WINPE
B.booting from OS (Vista) into WINPE => will this load the x86 boot image (it doesn’t look like it, I CAN see the image loaded ….wim is exactly the same when loaded from OS)
The reason why I ask this: see link above: loading TS from PXE/media works fine, when choosing the exact same TS from WITHIN OS (Vista, 32 bit) the TS fails.
Note: we set the ts step format system disk to NOT run if _SMSTSMediaType is OEMMedia (set in order to not format if prestaged media). So if for some reason this variable would be set booting TS from OS?
Please advise.
J.
Jan Hoedt

What I would like to know: what is the difference/is there a difference between:
There is none.
Starting a TS using Software Center will download the boot image that's assigned to the task sequence.
PXE (depending on how many boot images are available on the PXE-enabled DP): the TS will use the boot image that's assigned to the task sequence (it will download that one and reboot into PE for a second time if the first boot image (see smspxe.log) does not
match).
P.S. Please don't post another question for the exact same topic. Thanks.
Torsten Meringer | http://www.mssccmfaq.de

Screen resolution when PXE boot from WDS vs Install Windows 8.1 from USB

Hi all
I own a Lenovo ThinkPad T430s, X230 Tablet, and now have my hands on a T440. All three machines have UEFI Secure Boot enabled properly, i.e. Windows boot screen shows Lenovo logo instead of Windows logo.
However, if I do a PXE boot (using Windows Deployment Services from Windows Server 2012, not R2) and boot to the same boot.wim provided on a Windows 8.1 ISO image, the boot screen resolution turns crap, and the WinPE environment runs in 640x480. Also, as opposed
to the Lenovo logo showing on the boot screen, the Windows logo shows up instead, indicating it's not doing a secure boot?
When booting from a USB stick however, using the same Windows 8.1 boot.wim (copied from ISO), the screen resolution in Windows Setup is detected correctly, and the Lenovo logo shows up.
This occurs on all three machines since MDT was upgraded to MDT 2013 or when I replaced Windows 8 boot.wim with Windows 8.1 boot.wim (as the Windows ADK 8 --> ADK 8.1).
Is there a fix for this? Do others have the same problem elsewhere?
Many thanks

Hi,
When boot UEFI-based computer from PXE you should take more into consideration.
For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode.
Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode.
How to Create a PXE-Initiated Windows 8 Deployment for UEFI-Based or BIOS-Based Computers in Configuration Manager
http://technet.microsoft.com/en-us/library/jj938037.aspx
Especially for “Pre-Deployment Considerations”
If you still cannot find a way to make it boot from UEFI mode, you should contact with manufacture to confirm if PXE-initiated boot is supported.
Hope this helps.

How to chain boot WinPE from iPXE?

Hi,
We are trying to boot "WinPE" from iPXE. We have tried two methods both are not working for HP Proliant Gen8 Server.
Method1 : Using wimboot by following "http://ipxe.org/wimboot"
We are using Puppetlabs Razor iPXE scripts, so functions inside <%= %> is working as expected.
#!ipxe
echo =========
echo freeing all loaded images to ensure wimboot works
imgfree
echo ======================
set base <%= repo_url.sub(%r{/$}, '') %>
kernel <%= file_url('wimboot', true) %>
initrd ${base}/bootmgr          bootmgr
initrd ${base}/boot/bcd                 BCD
initrd ${base}/boot/fonts/segmono_boot.ttf      segmono_boot.ttf
initrd ${base}/boot/fonts/segoe_slboot.ttf      segoe_slboot.ttf
initrd ${base}/boot/fonts/wgl4_boot.ttf   wgl4_boot.ttf
initrd ${base}/boot/boot.sdi              boot.sdi
initrd ${base}/razor-winpe.wim            boot.wim
echo =====================
imgstat
echo now booting WinPE clientboot
Method2 : Using iPXE chain boot and pxeboot.n12.
chain tftp://10.0.0.5/pxeboot.n12
In both the cases iPXE downloading all the required files after that it is hanging without booting into WinPE. We are using DHCP Server(dhcpd) in Redhat linux to boot WinPE.
To confirm there is no problem with WinPE we have directly specified "pxeboot.n12" in DHCP Configuration(/etc/dhcp/dhcpd.conf) as like this --> filename "pxeboot.12". With this method WinPE successfully booting with simple PXE boot.
So we are assuming WinPE and BCD does not have any problems.
Same files we are using with iPXE then it hangs.
We have tried different "wimboot", different "undionly.kpxe" from iPXE.org. Still same problem.
Further we have compared the tcpdump logs between normal PXE boot and iPXE boot.
The different we found is with normal PXE boot client is downloading "pxeboot.12" & "bootmgr.exe" and the WinPE boot works fine.
But with iPXE its downloading "/pxeboot.n12" & "/bootmgr.exe".
Is there any problem with the preceding "/" in the filenames?

Hi,
In WDS PXE boot the boot file name should be pxeboot.n12. If you mount the boot.wim you will find the file under the path: windows\boot.
I think you need ask this question in a IPXE related forum. People there may give you more feasible solution.
Thank you for your understanding.

New Dell Lat e6440 Laptop - no IP address when PXE boot w/ WinPE

PXE booting is working fine with all other Dell models. PE environment loads, OSD password prompt is displayed. Task sequences are displayed.
With just this model, Dell Latitude e6440, it gets to the point where we should be prompted for a password, hangs and then reboots. When I hit F8 and enter ipconfig it shows no ip address If I do ipconfig /renew i get "The operation failed as no adaptor
is in the state permissible for this operation." If I boot the computer into Windows (OOBE as shipped by Dell) it gets an IP successfully. I've updated our WinPE boot image with every network driver I can find from Dell for this model. Any other suggestions?
We are booting with a x86 WinPE wim file.
I have injected the latest kernel mode driver framework into our WinPE wim used for PXE boot.

Hi,
Any useful information in smspxe.log?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Unable to launch Litetouch.vbs (LiteTouch.wsf) from UNC path - A connection to the Deploayment Share Could not be made

I am having a difficult time figuring out this issue. Here is the back story. The particular deployment share is not used in the traditional sense of deploying OS images. Instead, it is only used in deploying applications. I actually have three shares that
do this catered to three different clientele groups; IT, teachers and students.
I have these shares set up so that the Litetouch.vbs is used as a login script and tied to specific AD accounts. When launched, it goes through the normal MDT gathering process and eventually shows a list of applications to select to install.
And this has and still is working perfectly for several years with both wired and wireless computers, until recently.
My issue, I'm afraid, is with the new Intel Dual Band 7260 wireless cards/drivers (both N7260 and AC7260. The reason I suspect this is because any other desktop or laptop will launch the VBScript just fine and bring up the list of software like it has always
done. However, if I UNC to the share and try to manually run LiteTouch.vbs, I get the "A connection to the deployment share cannot be made. Connection OK. Possible cause: Invalid credentials." That's right. I can UNC to the shares all day long, but
when launching the LiteTouch.vbs or LiteTouch.wsf scripts, I always get the above error. So the wireless is working, in a way. Just not the way I need it to. I've tried different versions of drivers all with the same error. I've launched other VBScripts that
I've wrote from UNC paths and they run fine.
I am using a Domain Admin account to connect back to the deployment share through MDT. My account is a domain admin account. The share permissions are full control for Everyone and Domain Admins. The folder permissions are Read Only for Everyone and Full
Control for Domain Admins. Like I stated, this works fine on any other system.
When I look at the BDD.log file, sometimes I don't see anything, but most of the time I see the line "No physical adapters present. Cannot deploy over wireless." Which, in my case, is not true because I can use any other laptop with older
Intel wireless cards, Broadcom, Atheros or whatever and it works perfectly. And, if I hardwire the offending laptops and use Ethernet instead of wireless, I can launch the VBScript and proceed just fine.
I guess my question is, is there a way to force MDT to use any network connection, whether it's wired or wireless to deploy anything. In my case, it would be software.
We use this option as a way for students in our high schools to be able to log in with a special account and install specific software they may need for a class. It is easier to have them do it this way than to try and install different software for
different classes on a total of 4000 laptops.
I am currently running Windows Server 2012 R2 with MDT 2013. The laptops are running Windows 7 SP1 x64 Enterprise and Windows 8.1.1 Enterprise.
Any help or ideas anyone has to offer would be greatly appreciated.
~Mike

I understand that you got MDT to work on other adapters, and I understand that some people dislike the AC series.
However...
I must strongly disagree with your conclusion:
the Intel 7260 cards just will not work for this scenario. Any other wireless card works
perfectly fine...
As designed, MDT is coded to block Wireless deployment scenarios. However, the algorithm used to determine if a network adapter is wired vs wireless is highly flawed, it will check the description (caption) of the network adapter and search for the string:
"Wireless". And if I recall, it is difficult to determine Wireless vs Wired within a VBSCript.
Set colAdapters = objWMI.ExecQuery("select * from win32_NetworkAdapterconfiguration where IPEnabled = True")
For Each oAdapter in colAdapters
If Instr(UCase(oAdapter.Caption),"WIRELESS") = 0 Then
If oAdapter.IPConnectionMetric < sIPConnectionMetric Or sIPConnectionMetric = "" Then
sIPConnectionMetric = oAdapter.IPConnectionMetric
End If
End IF
If Instr(UCase(oAdapter.Caption),"WIRELESS") Then
sWirelessConnectionMetric = oAdapter.IPConnectionMetric
End If
Next
If sIPConnectionMetric = "" Then
oLogging.CreateEntry "No physical adapters present, cannot deploy over wireless", LogTypeError
ValidatenetworkConnectivity = Failure
Exit Function
End IF
On my Lenovo W530, for example, when I disable my Wired connection, my wireless adapter reports:
PS C:\> gwmi -query "select * from win32_NetworkAdapterconfiguration where IPEnabled = true" | select-object Caption
Caption
[00000002] Intel(R) Centrino(R) Ultimate-N 6300 AGN
AS you can see, no "Wireless" in the caption string. A connection to the deployment share works just fine.
Therefore...
Yes, you *may* have gotten the installation to work on the machines that *just happen* to not have "wireless" in the caption, but I would not count on this to be true on all machines in a corporate environment.
-k
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Failed OEL7 boot from PXE

Hi
I was just attempting to boot a OEL7 image from PXE (7.4. Virtual Machine Installation Media) and the installation process halts with a warning (/dev/root doesn't exist). I am using OracleVM 3.3.1 and the guest VM was set up to be Paravirtualized.
Does anybody has any idea about what it is happenning?
Cheers and Thank you

Never mind. I downloaded the templates for OEL5 and OEL6 from the Oracle Repository.
Cheers

Does SCCM 2012 R2 supports PXE boot from Unix servers.

Does SCCM 2012 R2 supports PXE boot from Unix DHCP servers.
The client has DHCP on Unix servers. There are no Windows DHCP servers in the environment. Do we need Windows DHCP server for PXE boot.

You can use any modern DHCP server in your environment. DHCP is just used to help point the BIOS/Network Card to the right server, which in this case is your ConfigMgr Distribution Point with PXE Enabled.
It is strongly recommended to use IP Helper Addresses instead of the DHCP options though.
I hope that helps,
Nash
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

Calling startrfc.exe from within a vbs script

Hello, can someone help me please
I am trying to process xml idocs into SAP on a Windows 2008 server. I have written a vbs script to process the file and am trying to call STARTRFC.EXE from within the vbs script. However I keep getting an error that it cannot open the file. The code is shown below. I have changed the server name and gateway and user/passwd for security. I'm passing the filename as a variable (str_expfile) but it does not seem to be able to extract the actual file name from the variable. I know from past experience that you can pass it variables if its running on a unix box and in a shell. But for some reason it not decipering the variable name in the vbs script
Set objShell = CreateObject("Wscript.Shell")
str_startrfc = "D:\usr\sap\SID\SYS\exe\uc\NTAMD64\startrfc.exe -d SID -3 -h hostname -s 00 -g hostname -x sapgw00 -u user -p passwd -c 100 -l EN -t -F EDI_DATA_INCOMING -E PORT=MYPORT -E PATHNAME=str_expfile"
objShell.Run str_startrfc, ,True
The error I'm getting is shown below:
ERROR file opened at 20110510 134219 GMT Daylight Time, SAP-REL 700,0,278 RFC-VER 3 1200864 MT-SL
T:2584 Error in program 'startrfc': ======> Error at OPEN 'str_expfile' (check file)
T:2584 Error in program 'startrfc': <* RfcReceive [1] : returns 3:RFC_SYS_EXCEPTION
T:2584 Error in program 'startrfc': <* RfcCallReceive [1] : returns 3:RFC_SYS_EXCEPTION
Thanks
Regards
Steve

Hi Markus
Unfortunately I can't do that because I need it to process hundreds of files one after another and I would have to hard code the file path each time. That's why I need it automated.
Can startrfc.exe not take a variable for the pathname in a vb script? It works fine in a unix shell. We are migrating from unix to windows and I need to convert all my unix scripts into vb scripts.
I notice there is a nother rfc type program available, can I use rfcexec.exe instead of startrfc.exe and would it take variables?
Thanks
Regards
Steve

Call litetouch.vbs from PXE booted WinPE

Similar Messages

Maybe you are looking for