Zero Touch/ZTI, Lite Touch/LTi Latest Questions

Prompt for IP Address or TCP/IP Settings

Wed, 13 Jun 2018 00:49:27 +0000

Good evening

I am using SCCM to leverage imaging. I have been asked to do the following

Lay down a new image

rename the computer in the pxe menu (using OSDCOMPUTERNAME Variable) for prompt

Join domain (using Task Sequence)

Allow end user to specify static IP address, gateway (prompt)

I would perferable like to have all prompts in the beginning of the wizard.

I tried a few things and i've come up with nothing. Anyone that can help would help me immensely

I have tried to set the OSDHCP variable to false and similarly to osdcomputername use

osdadapter0gateways and the similar ipaddreses one, but they dont keep the settings.

Pushing out task sequence to new machines

Mon, 04 Jun 2018 13:27:59 +0000

Hello,

I am trying to push a task sequence to approx 100 computers (Dell Precison 3620. I have create a device collection and added those systems to the device collection. I create a task sequence and deployed it as required.

It don't seem to work. However if I manually pxe boot it does come up with that task sequence.

My question i have is we have a password set for task sequences. Would this be causing the issue?

Thanks,

Craig

Pushing out task sequence to new machines

Wed, 23 May 2018 12:15:57 +0000

Hello,

I have approx 100 Dell 3620 Precision systems that I need a task sequence pushed out to. Right now I am in the testing phase.

1. I added the machine by mac address using a .csv and gave it a name which worked sucessful

2. I create a device collection and made my limiting collection to all systems

3. I added that system to that device collection

4. I made my task sequence which is tested and working and deployed it as required set the time for it to be pushed with no expiry date.

5. There has been no activity to that machine

My question is there something that I may be missing and are there any log files on the server that i can look at to find out what the issue is?

Thank you,

Craig

Domain Attach fail

Mon, 14 Aug 2017 23:36:40 +0000

SCCM 1702+hotfix with MDT Integration

I created a task sequence using the MDT integration, and while troubleshooting some of the errors I was getting (0x00000001, 0x00000032, etc...) I now have a task sequence that is working correctly, with the exception of the domain joining process. I used the UDI config wizard, and had it working, but somewhere I accidentally killed whatever was helping it attach with the credentials provided in the UDI. Unfortunately there are many, many OU's that we need to be able to attach to, so the unattend.xml and not really viable options. I would prefer to keep the UDI so we can choose the WIM for the deployment and keep the task sequence simple.

Thanks!

MDT Installation Reboot to OS

Sun, 04 Jun 2017 19:19:40 +0000

Hi Community,

I have been fighting a problem the last couple of days.

I have been trying to install HP Probook 430 G1, 650 G1 and Surface 1 and 2 generation.

When deploying MDT first time the installation goes trough correct but when reinstalling the computer apply everything to the first restart then it restart back into WinPE and say dirt envoirment. Cant understand why it's doing this, but if I run diskpart before I start task sequence it goes trough correct.

Have anyone seen this before?

Kind regards

EGGLAS

Strange Behavior on Writing Bitlocker key to AD

Mon, 29 Feb 2016 15:49:45 +0000

The writing of the Bitlocker key to AD has been working flawlessly... until we started to receiving machines with SSD drives in them. The task sequence works flawlessly with no errors. The problem is the bitocker recovery tab within AD is empty. I can run the manual way (https://blogs.technet.microsoft.com/askcore/2010/04/06/how-to-backup-recovery-information-in-ad-after-bitlocker-is-turned-on-in-windows-7/ ) and it will input the data in to ad, but I do not want to have to do this .

The real strange thing is if I remove the machine from AD, and reimage it, the key properly registers itself within AD. Only on the second pass will it work?

[refresh] Unable to restore user files with same computername

Wed, 03 Feb 2016 14:02:16 +0000

Hi,

I'm trying to make a refresh task sequence with Windows 10.

It's working fine when you make a refresh from Computer1 to the same but renamed Conputer2.

Unfortunately if i make a refresh keeping the same computername nothing is restored.

Thanks for your help

DHCP SCOPE Option 67 string value

Fri, 14 Nov 2014 20:39:04 +0000

I am completely new to OS Deployment and very less knowledge on dhcp. We are using SCCM2012 in our environment. Wanted to know what should be the string value for DHCP 67 OPTION as i am confused. does the \ back slash make any difference when setting a string value. for example- \\smsboot\x64\wdsnbp.com or \smsboot\x64\wdsnbp.com or would i need to specify the complete path where remote install folder is located for example \\server name\c$\remoteinsall\smsboot\x64\wdsnbp.com

you guys might think its a stupid question but want to understand how the path needs to be setup. i cant test myself due to restrictions in our organization as the DHCP is handled by other team.

MDT - Multicast required on additional WDS Servers

Wed, 29 Jan 2014 11:44:43 +0000

Hi All,

I have deployed MDT throughout our business using WDS as the deployment mechanism through PXE, however have noted a problem today.

Scenario:
Server A running WDS, MDT and WAIK
Server B running WDS (I have since added MDT and WAIK without success) - Info to follow.

I wish to deploy using a multicast stream. Server A works, however Server B does not.

I have DFS-R replicating the deployment share and RemoteInstall\boot folder to 'Server B' but it appears multicast transmission is not enabled.

Can you advise how I can get this working.

As it stands site B using 'Server B' is broadcasting which is not acceptable.

I have followed the link here but does not appear to work although added the multicast feature on Server B.

http://deployment.cybertechcomputers.co.nz/mdt-toolkit-reference/EnabMultDeplWithMDTInstOnADiffCo.htm

Help appreciated!

Many thanks in advance.

WinRE Deploy

Fri, 13 Dec 2013 14:39:55 +0000

Hi All,

I need some help on deploying Windows RE in 1) Fresh Install 2) Existing Install

Background: Laptop is having Single partition which is Active, Boot, System, Recovery & Healthy Primary partition. I am NOT using Bitlocker for encryption.

I Want To: Create separate partition for Windows Recovery Environment.

Conditions: 1) I will not be using Apply Windows Recovery Environment(WinRE) which is readily available in MDT Task Sequence as I may update the winre.wim file & would need to push updated image to clients.
2) I need to deploy this recovery environment to Fresh Install as well as Existing Install

Let me know how I can achieve the objective I am having MDT 2012 Update 1 & SCCM 2007.

I have done testing in MDT 2012 Update 1 for creation of Windows RE Partition which works well if I call the Task Sequence ( by going to DeploymentShare & launching LiteTouch.vbs manually). But if I select the same task sequence in the LiteTouch Deployment , it fails giving error regarding REagentC.exe as Task sequence fails to disable the existing recovery environment.

Below is in my Task Sequence in MDT.

1) Diskapart command to shrink, format & assign drive letter for Windows recovery (S:)
2) Create folder structure S:\Recovery\WindowsRE
3) Copy winre.wim from Deploymentshare\Scripts folder to S:\Recovery\WindowsRE
4) Disable Windows RE Environment ( reagentc /disable)
5) Set Recovery Environment Reagentc.exe /setreimage /path S:\Recovery\WindowsRE /target C:\Windows
6) Enable Windows RE Environment ( reagentc /Enable)

Thanks In Advance
Mandy!

USMT Failure

Mon, 11 Jul 2011 13:25:49 +0000

I am working on getting USMT to work to go from an XP machine to a Windows 7 machine. I created a "Standard Client Replace Task Sequence" and updated the deployment share. I boot to the XP machine and then browse to my deploymentshare\scripts and kick off LiteTouch.vbs. I watch where the transfer file is created and it does about 9.2GB then goes to "Capture Groups" and then to "Apply Windows PE"...and this is where I have problems. I get the error message below:

The logical drive could not be determined from the disk and partition

FAILURE (7713): 1: Could not Determine Partition to deploy to

Litetouch deployment failed, Return Code = -2147467259 0x80004005

Below this are a bunch more "Failed to run the action:" items, but I think they're probably all caused by the original failure. From the research I've done, I think it has something to do with the small diagnostic partition on this Dell D630. I went into the LTIApply.vbs and modified it by hardcoding the "DestinationLogicalDrive" to C: so hopefully it skips over the diagnostic partition. I posted on here to see if anyone else has had to deal with this and what they've done to get around it. I talked to the guy who setup our old deployment server and he recalls modifying some of the scripts, but he doesn't remember details. Any help is apprecaited.

ZTI Task Sequence.

Thu, 16 May 2013 20:55:23 +0000

Hi Guys,

Under task sequence computers join domain however, they are not shifted to the correct OU.

I am trying to do this:

LDAP://OU=Win,OU=Corporate,OU=Workstations,DC=ngco,DC=com

Any idea?

thanks.

ZTI Deployment.

Sat, 13 Apr 2013 00:17:54 +0000

Hi,

I am getting following error on one model, and it is complaining about all the errors in here and about the space while I have enough space in this computer: few are in red and some not in red collor they are below:

EncryptionKey ENV var not found. This may be because Local state Store is used. OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Building Default USMT params successful OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Adding config files to user params successful OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Additional user defined options = "/hardlink /nocompress" OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Building user defined params successful OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Building USMT command successful OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Securing store .. OSDUSMT 4/12/2013 7:23:58 PM 2032 (0x07F0)

Executing command line: "C:\_SMSTaskSequence\Packages\LCL002A3\amd64\loadstate.exe" "C:\StateStore" /c /l:"C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog\loadstate.log" /progress:"C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog\loadstateprogress.log" /i:"C:\_SMSTaskSequence\Packages\LCL002A3\amd64\MigUser.xml" /i:"C:\_SMSTaskSequence\Packages\LCL002A3\amd64\MigApp.xml" /i:"C:\_SMSTaskSequence\Packages\LCL002A3\amd64\MigL.xml" /hardlink /nocompress OSDUSMT 4/12/2013 7:24:03 PM 2032 (0x07F0)

Process completed with exit code 14 OSDUSMT 4/12/2013 7:24:08 PM 2032 (0x07F0)

USMT completed with exit code 14 OSDUSMT 4/12/2013 7:24:08 PM 2032 (0x07F0)

USMT returned exit code (0x0000000e). Look USMT log file loadstate.log for detail error message. OSDUSMT 4/12/2013 7:24:08 PM 2032 (0x07F0)

Invoking ReleaseSource on USMTPackagePath C:\_SMSTaskSequence\Packages\LCL002A3 OSDUSMT 4/12/2013 7:24:08 PM 2032 (0x07F0)

OSDMigrateUserState finished: 0x8007000e OSDUSMT 4/12/2013 7:24:09 PM 2032 (0x07F0)

Process completed with exit code 2147942414 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Failed to run the action: Restore User State.

Not enough storage is available to complete this operation. (Error: 8007000E; Source: Windows) TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_ActionFailError TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:09ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionRetCode=-2147024882 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Let the parent group (State Restore) decides whether to continue execution TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Let the parent group (Execute Task Sequence) decide whether to continue execution TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

The group (Execute Task Sequence) ignored action failure and continue execution on the next step following the group. TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Updated security on object C:\_SMSTaskSequence. TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=251 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSNextInstructionPointer=251 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSInstructionStackString= TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSInstructionStackString= TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Save the current environment block TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Cancelled Wizard Group. Instruction pointer: 251 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Cancelled Wizard Group TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=251 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Evaluating an AND expression TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Evaluating a variable condition expression TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: equals TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: OSDSetupWizCancelled TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: TRUE TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

The group (Cancelled Wizard Group) has been skipped because the condition is evaluated to be false TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_SkipGroupConditionFalseInfo TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:09ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Execution of the instruction (Cancelled Wizard Group) has been skipped TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Gather Logs and StateStore on Failure. Instruction pointer: 257 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Gather Logs and StateStore on Failure TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=257 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Evaluating an AND expression TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Evaluating a variable condition expression TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: equals TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: _SMSTSLastActionSucceeded TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: false TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

The condition for the group (Gather Logs and StateStore on Failure) is evaluated to be true TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

The group (Gather Logs and StateStore on Failure) has been successfully started TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_GroupStartInfo TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:09ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Updated security on object C:\_SMSTaskSequence. TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=258 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSNextInstructionPointer=258 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Save the current environment block TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Set Error Code. Instruction pointer: 258 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Set Error Code TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=258 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: tsenv.exe "ErrorReturnCode=%_SMSTSLastActionRetCode%" TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Start executing the command line: tsenv.exe "ErrorReturnCode=%_SMSTSLastActionRetCode%" TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Expand a string: WinPEandFullOS TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Executing command line: tsenv.exe "ErrorReturnCode=%_SMSTSLastActionRetCode%" TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Finished with error code 0 TSEnv 4/12/2013 7:24:09 PM 2448 (0x0990)

Process completed with exit code 0 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Successfully complete the action (Set Error Code) with the exit win32 code 0 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:09ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:09 PM 2164 (0x0874)

Updated security on object C:\_SMSTaskSequence. TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=259 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSNextInstructionPointer=259 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Save the current environment block TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Use Toolkit Package. Instruction pointer: 259 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Use Toolkit Package TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=259 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Evaluating an AND expression TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Evaluating a NOT expression TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Evaluating a folder condition expression TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Expand a string: %ScriptRoot% TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Expand a string: TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

The action (Use Toolkit Package) has been skipped because the condition is evaluated to be false TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_SkipActionConditionFalseInfo TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:10ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Execution of the instruction (Use Toolkit Package) has been skipped TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Gather. Instruction pointer: 260 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Gather TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=260 TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a local default variable GatherLocalOnly TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a local default variable RulesFile TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Expand a string: smsswd.exe /run:LCL00398 cscript.exe "%DeployRoot%\Scripts\ZTIGather.wsf" TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Expand a string: TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Start executing the command line: smsswd.exe /run:LCL00398 cscript.exe "%DeployRoot%\Scripts\ZTIGather.wsf" TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Expand a string: WinPEandFullOS TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

Executing command line: smsswd.exe /run:LCL00398 cscript.exe "%DeployRoot%\Scripts\ZTIGather.wsf" TSManager 4/12/2013 7:24:10 PM 2164 (0x0874)

=======================[ smsswd.exe ] ======================= InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

PackageID = 'LCL00398' InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

BaseVar = '', ContinueOnError='' InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

SwdAction = '0001' InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

WinHttp credentials set InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

List of files to be downloaded InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

Downloaded file from http://YYYYYYYYYYY.xxxx.com:80/SMS_DP_SMSPKGS%24/LCL00398/CustomSettings.ini to C:\_SMSTaskSequence\Packages\LCL00398\CustomSettings.ini InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

Downloaded file from http://YYYYYYYYYYY.xxxx.com:80/SMS_DP_SMSPKGS%24/LCL00398/Unattend.xml to C:\_SMSTaskSequence\Packages\LCL00398\Unattend.xml InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

Resolved source to 'C:\_SMSTaskSequence\Packages\LCL00398' InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

Working dir 'C:\_SMSTaskSequence\Packages\LCL00398' InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

Executing command line: Run command line InstallSoftware 4/12/2013 7:24:10 PM 584 (0x0248)

Microsoft ® Windows Script Host Version 5.8 InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Microsoft Deployment Toolkit version: 6.1.2369.0 InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

The task sequencer log is located at C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

------------------------- Object Initialization ------------------------- InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

------------------------- Initialization ------------------------- InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Synchronizing the environments. InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Finished synchronizing the environments. InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Getting OS info InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Property OSCurrentVersion is now = 6.1.7601 InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Property OSCurrentBuild is now = 7601 InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Property OSVersion is now = Win7Client InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Property IsServerOS is now = False InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Property IsServerCoreOS is now = False InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Finished getting OS info InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Getting HAL information InstallSoftware 4/12/2013 7:24:11 PM 584 (0x0248)

Property HALName is now = acpiapic InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Finished getting HAL information InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Getting network info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Checking network adapter: [00000007] Intel® 82567LM Gigabit Network Connection InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

MAC address = 00:24:E8:EC:E5:01 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

IP Address = 10.60.238.128 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

IP Address = fe80::7de7:51c0:5878:28bf InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Default Gateway = 10.60.238.99 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property IPAddress001 is now = 10.60.238.128 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property IPAddress002 is now = fe80::7de7:51c0:5878:28bf InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property MacAddress001 is now = 00:24:E8:EC:E5:01 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property DefaultGateway001 is now = 10.60.238.99 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Finished getting network info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Getting DP info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

ConfigMgr distribution point = VWBRFNPPR4.XXXX.COM InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property SMSDP is now = VWBRFNPPR4.XXXX.COM InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Finished getting DP info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Getting WDS server info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Unable to determine WDS server name, probably not booted from WDS. InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Finished getting WDS server info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property HostName is now = 6W296L1 InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Getting asset info InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Unable to determine asset tag via WMI. InstallSoftware 4/12/2013 7:24:15 PM 584 (0x0248)

Property AssetTag is now = InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property SerialNumber is now = 6W296L1 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property Make is now = Dell Inc. InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property Model is now = Latitude E6400 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property Product is now = 0U692R InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property UUID is now = 4C4C4544-0057-3210-8039-B6C04F364C31 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property Memory is now = 1999 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property Architecture is now = X64 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property ProcessorSpeed is now = 2401 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property CapableArchitecture is now = AMD64 X64 X86 InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property IsLaptop is now = True InstallSoftware 4/12/2013 7:24:16 PM 584 (0x0248)

Property IsDesktop is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property IsServer is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property IsUEFI is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property IsOnBattery is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property SupportsX86 is now = True InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property SupportsX64 is now = True InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property SupportsSLAT = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Finished getting asset info InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Getting OS SKU info InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property OSSKU is now = ENTERPRISE InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Finished getting OS info InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Determining the Disk and Partition Number from the Logical Drive C:\WINDOWS InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Getting virtualization info InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property IsHypervisorRunning is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property SupportsVT is now = True InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property SupportsNX is now = True InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property Supports64Bit is now = True InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property SupportsHyperVRole is now = True InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

This computer does not appear to be a virtual machine (BIOS is 'DELL - 27d90911'). InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property IsVM is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Finished getting virtualization info InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Connection succeeded to MicrosoftVolumeEncryption InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

There are no encrypted drives InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Property IsBDE is now = False InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Processing the phase. InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Determining the INI file to use. InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Using COMMAND LINE ARG: Ini file = CustomSettings.ini InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Finished determining the INI file to use. InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Added new custom property MYCUSTOMPROPERTY InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Added new custom property BUILDCOMPUTERNAME InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Added new custom property LOCATIONID InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

Using from [settings]: Rule Priority = MMSETTINGS, MMPACKAGES, MMAPPS, MMADMINS, MMROLES, LSETTINGS, LPACKAGES, LAPPS, LADMINS, LROLES, RSETTINGS, RPACKAGES, RAPPS, RADMINS, LOCATIONS, BUILDCOMPUTERNAME, DEFAULT InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

------ Processing the [MMSETTINGS] section ------ InstallSoftware 4/12/2013 7:24:17 PM 584 (0x0248)

------ Processing the [MMPACKAGES] section ------ InstallSoftware 4/12/2013 7:24:18 PM 584 (0x0248)

------ Processing the [MMAPPS] section ------ InstallSoftware 4/12/2013 7:24:18 PM 584 (0x0248)

------ Processing the [MMADMINS] section ------ InstallSoftware 4/12/2013 7:24:18 PM 584 (0x0248)

------ Processing the [MMROLES] section ------ InstallSoftware 4/12/2013 7:24:18 PM 584 (0x0248)

------ Processing the [LSETTINGS] section ------ InstallSoftware 4/12/2013 7:24:18 PM 584 (0x0248)

------ Processing the [LPACKAGES] section ------ InstallSoftware 4/12/2013 7:24:19 PM 584 (0x0248)

------ Processing the [LAPPS] section ------ InstallSoftware 4/12/2013 7:24:19 PM 584 (0x0248)

------ Processing the [LADMINS] section ------ InstallSoftware 4/12/2013 7:24:19 PM 584 (0x0248)

------ Processing the [LROLES] section ------ InstallSoftware 4/12/2013 7:24:19 PM 584 (0x0248)

------ Processing the [RSETTINGS] section ------ InstallSoftware 4/12/2013 7:24:20 PM 584 (0x0248)

------ Processing the [RPACKAGES] section ------ InstallSoftware 4/12/2013 7:24:20 PM 584 (0x0248)

------ Processing the [RAPPS] section ------ InstallSoftware 4/12/2013 7:24:20 PM 584 (0x0248)

------ Processing the [RADMINS] section ------ InstallSoftware 4/12/2013 7:24:20 PM 584 (0x0248)

------ Processing the [LOCATIONS] section ------ InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

------ Processing the [bUILDCOMPUTERNAME] section ------ InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

------ Processing the [DEFAULT] section ------ InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

------ Done processing CustomSettings.ini ------ InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Remapping variables. InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Process completed with exit code 0 InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Property TaskSequenceID is now = InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Property DeploymentType is now = REFRESH InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Finished remapping variables. InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

ZTIGather processing completed successfully. InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Command line returned 0 InstallSoftware 4/12/2013 7:24:21 PM 584 (0x0248)

Process completed with exit code 0 TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Successfully complete the action (Gather) with the exit win32 code 0 TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:21ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:21 PM 2164 (0x0874)

Updated security on object C:\_SMSTaskSequence. TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=261 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSNextInstructionPointer=261 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Save the current environment block TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Move State Store. Instruction pointer: 261 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Move State Store TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=261 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a local default variable SMSTSDisableWow64Redirection TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a local default variable _SMSTSRunCommandLineAsUser TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Expand a string: smsswd.exe /run: cscript.exe "%deployroot%\scripts\ztimovestatestore.wsf" TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Expand a string: TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Start executing the command line: smsswd.exe /run: cscript.exe "%deployroot%\scripts\ztimovestatestore.wsf" TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Expand a string: WinPEandFullOS TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Executing command line: smsswd.exe /run: cscript.exe "%deployroot%\scripts\ztimovestatestore.wsf" TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

=======================[ smsswd.exe ] ======================= InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

PackageID = '' InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

BaseVar = '', ContinueOnError='' InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

SwdAction = '0001' InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Working dir 'not set' InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Executing command line: Run command line InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Process completed with exit code 0 InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Microsoft ® Windows Script Host Version 5.8 InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Microsoft Deployment Toolkit version: 6.1.2369.0 InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

The task sequencer log is located at C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

ztimovestatestore processing completed successfully. InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Command line returned 0 InstallSoftware 4/12/2013 7:24:22 PM 2508 (0x09CC)

Process completed with exit code 0 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Successfully complete the action (Move State Store) with the exit win32 code 0 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:22ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Updated security on object C:\_SMSTaskSequence. TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=262 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSNextInstructionPointer=262 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Save the current environment block TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Copy Logs. Instruction pointer: 262 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Copy Logs TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=262 TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a local default variable SMSTSDisableWow64Redirection TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a local default variable _SMSTSRunCommandLineAsUser TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Expand a string: smsswd.exe /run: cscript "%deployroot%\scripts\zticopylogs.wsf" TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Expand a string: TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Start executing the command line: smsswd.exe /run: cscript "%deployroot%\scripts\zticopylogs.wsf" TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Expand a string: WinPEandFullOS TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\zticopylogs.wsf" TSManager 4/12/2013 7:24:22 PM 2164 (0x0874)

=======================[ smsswd.exe ] ======================= InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

PackageID = '' InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

BaseVar = '', ContinueOnError='' InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

SwdAction = '0001' InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

Working dir 'not set' InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

Executing command line: Run command line InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

Microsoft ® Windows Script Host Version 5.8 InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

Microsoft Deployment Toolkit version: 6.1.2369.0 InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

The task sequencer log is located at C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

Unable to copy log to the network as no SLShare value was specified. InstallSoftware 4/12/2013 7:24:22 PM 3064 (0x0BF8)

About to run command: cmd.exe /c vssadmin resize shadowstorage /For=C: /On=C: /MaxSize=5% InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Command has been started (process ID 1984) InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Process completed with exit code 0 InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Console > vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Console > Error: A Volume Shadow Copy Service component encountered an unexpected error. InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Console > Check the Application event log for more information. InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Return code from command = 2 InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Cleaning up default wallpaper registry keys InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

zticopylogs processing completed successfully. InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Command line returned 0 InstallSoftware 4/12/2013 7:24:23 PM 3064 (0x0BF8)

Process completed with exit code 0 TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Successfully complete the action (Copy Logs) with the exit win32 code 0 TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_ActionCompleteInfo TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:23ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:23 PM 2164 (0x0874)

Updated security on object C:\_SMSTaskSequence. TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=263 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSNextInstructionPointer=263 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a TS execution environment variable _SMSTSInstructionStackString=257 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Save the current environment block TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Start executing an instruciton. Instruction name: Error in the task sequence. Instruction pointer: 263 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSCurrentActionName=Error in the task sequence TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSNextInstructionPointer=263 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a local default variable SMSTSDisableWow64Redirection TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a local default variable _SMSTSRunCommandLineAsUser TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSLogPath=C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Expand a string: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Expand a string: TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Start executing the command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Expand a string: WinPEandFullOS TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

=======================[ smsswd.exe ] ======================= InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

PackageID = '' InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

BaseVar = '', ContinueOnError='' InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

SwdAction = '0001' InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Working dir 'not set' InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Executing command line: Run command line InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Process completed with exit code 2147942414 InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Microsoft ® Windows Script Host Version 5.8 InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Microsoft Deployment Toolkit version: 6.1.2369.0 InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

The task sequencer log is located at C:\WINDOWS\SysWOW64\CCM\Logs\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

ZTI deployment failed, Return Code = -2147024882 0x8007000E InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Command line returned 2147942414 InstallSoftware 4/12/2013 7:24:24 PM 1288 (0x0508)

Process completed with exit code 2147942414 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

!--------------------------------------------------------------------------------------------! TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Failed to run the action: Error in the task sequence.

Not enough storage is available to complete this operation. (Error: 8007000E; Source: Windows) TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_ActionFailError TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:24ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionRetCode=-2147024882 TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Clear local default environment TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.

Operation aborted (Error: 80004004; Source: Windows) TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Failed to run the last action: Error in the task sequence. Execution of task sequence failed.

Not enough storage is available to complete this operation. (Error: 8007000E; Source: Windows) TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Sending status message . . . TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Send a task execution status message SMS_TSExecution_TaskSequenceFailError TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:24:24ZhttpStatusReceiverSync

TSManager 4/12/2013 7:24:24 PM 2164 (0x0874)

Launching command shell. OSDSetupHook 4/12/2013 7:26:06 PM 1932 (0x078C)

Windows station: WinSta0 OSDSetupHook 4/12/2013 7:26:06 PM 1932 (0x078C)

Desktop: Default OSDSetupHook 4/12/2013 7:26:06 PM 1932 (0x078C)

executing command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 4/12/2013 7:26:06 PM 1932 (0x078C)

executed command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 4/12/2013 7:26:06 PM 1932 (0x078C)

Task Sequence Engine failed! Code: enExecutionFail TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

**************************************************************************** TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Task sequence execution failed with error code 80004005 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Cleaning Up. Removing Authenticator TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Cleaning up task sequence folder TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Successfully unregistered Task Sequencing Environment COM Interface. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Executing command line: "C:\WINDOWS\SysWOW64\CCM\TsProgressUI.exe" /Unregister TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

==========[ TsProgressUI started in process 2148 ]========== TsProgressUI 4/12/2013 7:39:37 PM 2924 (0x0B6C)

Unregistering COM classes TsProgressUI 4/12/2013 7:39:37 PM 2924 (0x0B6C)

Shutdown complete. TsProgressUI 4/12/2013 7:39:37 PM 2924 (0x0B6C)

Process completed with exit code 0 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Successfully unregistered TS Progress UI. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Package. Error code 0x80070002 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Start to cleanup TS policy TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

End TS policy cleanup TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Start to evaluate TS policy with lock TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Updating settings in \\6w296l1\root\ccm\policy\machine\actualconfig TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Machine RequestedConfig policy instance(s) : 327 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_UpdateCIAssignment.AssignmentID="{93F8A7C8-71A7-4A97-A4B9-CB4B5382DBA6}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_ClientActions.ActionID="{00000000-0000-0000-0000-000000000113}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_ClientActions.ActionID="{00000000-0000-0000-0000-000000000108}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_Scheduler_ScheduledMessage.ScheduledMessageID="{00000000-0000-0000-0000-000000000113}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_Scheduler_ScheduledMessage.ScheduledMessageID="{93F8A7C8-71A7-4A97-A4B9-CB4B5382DBA6}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_Scheduler_ScheduledMessage.ScheduledMessageID="{00000000-0000-0000-0000-000000000114}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_Scheduler_ScheduledMessage.ScheduledMessageID="{00000000-0000-0000-0000-000000000108}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_SoftwareDistribution.ADV_AdvertisementID="LCL204E6",PKG_PackageID="LCL0032B",PRG_ProgramID="Dell Touchpoint Software"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_SoftwareDistribution.ADV_AdvertisementID="LCL204E6",PKG_PackageID="LCL00328",PRG_ProgramID="Dell E6400 Wireless Driver"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_SoftwareDistribution.ADV_AdvertisementID="LCL204E6",PKG_PackageID="LCL002A0",PRG_ProgramID="ST-MICROELECTRONICS"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_UpdateSource.UniqueID="{05A375E0-EE25-4628-902E-D7A11AB18263}"'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_NetworkAccessAccount.SiteSettingsKey=1'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey=1'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey=1'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Deleted setting 'CCM_SystemHealthClientConfig.SiteSettingsKey=1'. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Raising event:

instance of CCM_PolicyAgent_SettingsEvaluationComplete

{

ClientID = "GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6A";

DateTime = "20130412233937.816000+000";

PolicyNamespace = "\\\\6w296l1\\root\\ccm\\policy\\machine\\actualconfig";

ProcessID = 2160;

ThreadID = 2164;

};

TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Successfully submitted event to the Status Agent. TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

End TS policy evaluation TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Policy evaluation initiated TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Error Task Sequence Manager failed to execute task sequence. Code 0x80004005 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Sending error status message TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Formatted header: TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

GUID:C66CAFD2-D9AE-432C-84EA-A05F0C5D0E6Amp:[http]MP_StatusManagerdirect:OSD336002013-04-12T23:39:37ZhttpStatusReceiverSync

TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Resuming SMS Components TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Waiting for CcmExec service to be fully operational TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

CcmExec service is up and fully operational TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Resume for CCM component SoftwareDistribution requested TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Resume for CCM component SoftwareUpdates requested TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Attempting to release request using {5E4992D3-66EF-4D9C-96ED-69F07E12B45B} TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

ReleaseRequest failed with error code 0x80004005 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Task Sequence Manager could not release active TS request. code 80004005 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\System Health Agent. Error code 0x80070002 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Failed to delete registry value HKLM\Software\Microsoft\SMS\Task Sequence\Active Request Handle. Error code 0x80070002 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Finalize logging request ignored from process 2160 TSManager 4/12/2013 7:39:37 PM 2164 (0x0874)

Process completed with exit code 2147500037 TSMBootstrap 4/12/2013 7:39:37 PM 1944 (0x0798)

Exiting with return code 0x80004005 TSMBootstrap 4/12/2013 7:39:37 PM 1944 (0x0798)

Process completed with exit code 2147500037 OSDSetupHook 4/12/2013 7:39:37 PM 856 (0x0358)

Task sequence completed 0x80004005 OSDSetupHook 4/12/2013 7:39:37 PM 856 (0x0358)

Waiting for command shell to complete. OSDSetupHook 4/12/2013 7:39:37 PM 1932 (0x078C)

This is my first time in this website any assistance will be appreciated.

Regards,

AY.

Lite Touch installation with SCCM possible?

Mon, 17 Oct 2011 04:57:06 +0000

I work for a large company. We'll deploy Win7 to hundreds of computers with MDT medias (install from USB because of network portion was not ready). We plan to do the subsequent installations via SCCM. But I'd like to do lite touch installation with SCCM 2007 R3; while installing, setup should ask for computer name, where it should reside in (I'm using domainou.xml file with MDT) and time zone. Is this possible?

TS fails during capture image

Fri, 07 Jan 2011 22:21:12 +0000

Using a basic setup of MDT & WDS, I've created a simple task just to deploy and capture a base Windows 7 image. It deploys just fine, but fails during the capture phase. Testing via command prompt showed that it wasn't a permission issue (no trouble at all writing to the specified capture share). I took a look through the SMSTS.log and this was the first thing to catch my attention

Executing command line: %TOOLROOT%\bddrun.exe /runas cscript.exe "%SCRIPTROOT%\ZTIBackup.wsf"	TSManager	1/7/2011 5:09:43 PM	1584 (0x0630)
Process completed with exit code 1060	TSManager	1/7/2011 5:09:43 PM	1584 (0x0630)
Failed to run the action: Create WIM. The specified service does not exist as an installed service. (Error: 00000424; Source: Windows)	TSManager	1/7/2011 5:09:43 PM	1584 (0x0630)

I happened to notice that there is no ZTIBackup script to be found. There are plenty of scripts in \MININT\Scripts and in \Deploy\Scripts, but ZTIBackup.wsf isn't one of them. Any idea why this file is missing? I have a hunch this is the source of my current headache. This task sequence is just a "Standard Client Task Sequence" that does nothing more than install the OS and Firefox. Thoughts? Ideas? This wasn't the source of my headaches. I injected the missing script into the WIM and I'm still getting the same errors. Oh, the headaches...