Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

Can you save images to an ReFS (as opposed to NTFS)

$
0
0

I'm building a new WDS server and going through the documentation, i see that NTFS is specified in a variety of places.

I was going to play with Storage Pools and ReFS, and was curious if I would run into any problems.

I was thinking that I would have the OS (with WDS/MDT) on the C partition then create a second drive formatted as ReFS and using Storage Pools as my Deployment Share.

Any thoughts?

Also, any thoughts on optimal RAID types for the C drive? 


~if this were /. this sig would be funny


in-place upgrade to win10 failed Windows Setup failed with hexadecimal exit code 0xC1900208 (decimal 3247440392)

$
0
0

Hi all

I'm doing a in-place upgrade for windows 7 computer to win10. it's always failed at progress 32% with  exit code 0xC1900208.

in the setupact.log, there is a error said: AudMig: No audio endpoint migration settings found 0x2

did SFC /scannow. windows update, remove anti-virus software. still not working.

could you please advise what else I can try. below is the screen shot.

thanks a lot!

Why do all Junction Points point to D:\ and not C:\ after deployment?

$
0
0

Running MDT 8456, ADK 1903, and Windows PE Add-on 1903

Deploying Windows 10 LTSC 2019

After deploying the image all Junction Points still exist, however, they are begin with D:\

What cause this and how do I fix it?

Trouble booting To MDT, keep getting the command line

$
0
0

Hi,

When I try to boot to MDT to image a PC, it only gets as far as the MDT splash screen then goes to the command line, "X:\Windows\System32>". prompt. I think it may have to do with the LiteTouchPE_64 boot image, but I'm not entirely sure. 

Any ideas?

Thanks



Best way to upgrade BIOS and EC on Panasonic during MDT TS.

$
0
0

Since Panasonic doesn't upgrade their BIOS versions every two weeks like Dell does, I'm looking into automating the event of the BIOS upgrade and the EC Embedded Controller.

It appears that if you run the BIOS upgrade and it already is that version, then it runs fine either way. The EC needs to verify the version because if it already is that version if will fail.

What I'm needing is a version check of the BIOS for Panasonic CF33 and also the EC version check before it runs.

Thanks!

HP Elitebook 840 G6 Imaging Issue

$
0
0

I am having an issue with some Elitebook 840 G6 PCs but not all of them.  The issue is the PC gets to the MDT screen and then reboots before prompting for credentials.

I have downloaded all the drivers from HP using the SofPaq software and I have manually exported the drivers from the computers that are failing and imported them into MDT.

I have also verified the HP WinPE drivers are the latest version.

Any thoughts?

Optiplex 3070 TS fails after OS install

$
0
0

I'm using MDT  6.3.8456.1000 with the latest WinPE. I use the total control method for drivers.

We just purchased about 20 Optiplex 3070s with NVMe drives. Task sequence goes along great until the first reboot after applying the image then fails for no obvious reason that I can tell. We run MDT from WDS and have been for several years with no issues.

If I image from a USB drive everything is fine. If I swap in a SATA SSD everything is fine. If I swap the NVMe drive to an Optiplex 3060 everything is fine.

All drivers are from Dell downloaded and imported to MDT last week. Yes, PE drivers also. I've found nothing on the internet concerning this issue.

Any help would be great. I don't want to have to image these (and any future machines) one at a time from a USB drive.

After applying the unattend file the machine reboots and then the smsts log says:

Failed to run the action: Gather local only. 
Incorrect function. (Error: 00000001; Source: Windows)

WDS can't access deployroot

$
0
0



Hello,

I'm beating my head against the desk here with this problem, been working on it for a couple days now and have made no progress. I have MDT / WDS setup on server 2016. I'm able to PXE boot , I get to the MDT Screen and get the credentials popup to connect to the deployment share. No matter what I use I cannot authenticate I just get "Invalid Credentials: The network path was not found". Now as of  typing this up I don't even get a prompt I just get " can't access deployroot"

-I've dropped into the prompt and verified end to end connectivity via ping ( both by IP and hostname)-The deployment share has everyone read permissions

-I can manually access the share with "net use xxxxx" and it authenticates with the local account and my domain admin account ( in the format of "@domain" ) from win PE once pxe booted into it. Also verified access from other domain computers.

-I've verified the share is defined correctly in both the bootstrap ( on the WDS box and once it's pxe'd via cmd) and in the MDT Share -> Properties -> General

-I've defined both my domain username and the local account in the bootstrap file and tried to get it to bypass the manual authentication.

-I verified the bios time is correct on the test laptop(Found and obscure Microsoft Forum post saying this fixed this for a user)

-I've noticed that the error shows it can't connect to the FQDN even though in my bootstrap.ini and properties I have it mentioned as explicitly the hostname. I've installed DNS on the WDS server and verified it can lookup the FQDN however even when litetouch does a lookup from CMD it can't resolve the FQDN. I've manualy added the entry to the hosts file via CMD once booted and clicked retry but the error persists.

I'm a bit lost here on what to try next, I even made a completely new deployment share to test if maybe I FUBAR'd some config and didn't know.



NOTHING happened after booting into MDT PE

$
0
0

Hi all, I an a freshman of MDT and windows server.

I am trying to use MDT, so I followed this guide and get a MDT PE iso file.

The only changes I made are me using winserver 2008r2 instead and I skipped the task sequence to simplify the process.

Then I booted into this PE. At first, everything seems ok.

HOWEVER, after the initialization process finished, the deployment wizard window disappeared without any warning or message. The screen just stuck, NOTHING happened then. 

I started a cmd window and found my network setting ok, this machine has obtained an ip using DHCP. 

I have also checked the log directory on the server, only an empty directory found. 

So, how to debug this? Any idea?


^o^


MDT STUCK after initialization

$
0
0

Hi all, I an a freshman of MDT and windows server.

I am trying to use MDT, so I followed this guide and get a MDT PE iso file.

The only changes I made are me using winserver 2008r2 instead and I skipped the task sequence to simplify the process.

Then I booted into this PE. At first, everything seems ok.

HOWEVER, after the initialization process finished, the deployment wizard window disappeared without any warning or message. The screen just stuck, NOTHING happened then. 

I started a cmd window and found my network setting ok, this machine has obtained an ip using DHCP. 

I have also checked the log directory on the server, only an empty directory found. 

So, how to debug this? Any idea?


^o^



MDT Upgrade windows 7 to 10 failure.

$
0
0

Anyone know how to fix this?

Detail logs below:

smsts.log:

<![LOG[Failed to run the action: Upgrade OS en-us. 
Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="11:58:35.917-480" date="12-12-2019" component="TSManager" context="" type="3" thread="368" file="instruction.cxx:924">

<![LOG[Failed to run the last action: Upgrade OS en-us. Execution of task sequence failed.
Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="11:58:35.917-480" date="12-12-2019" component="TSManager" context="" type="3" thread="368" file="engine.cxx:249">

<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="11:58:35.917-480" date="12-12-2019" component="TSManager" context="" type="1" thread="368" file="utils.cpp:6604">

<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="11:58:35.932-480" date="12-12-2019" component="TSManager" context="" type="3" thread="368" file="tsmanager.cpp:1273">

<![LOG[Let the parent group (Upgrade the Operating System) decides whether to continue execution]LOG]!><time="13:49:44.566-480" date="12-12-2019" component="TSManager" context="" type="0" thread="6572"

file="instruction.cxx:1037">
<![LOG[The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="13:49:44.566-480" date="12-12-2019" component="TSManager" context="" type="3" thread="6572" file="instruction.cxx:221">
<![LOG[Failed to run the last action: Upgrade OS en-us. Execution of task sequence failed.

Incorrect function. (Error: 00000001; Source: Windows)]LOG]!><time="13:49:44.566-480" date="12-12-2019" component="TSManager" context="" type="3" thread="6572" file="engine.cxx:249">

<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="13:49:44.566-480" date="12-12-2019" component="TSManager" context="" type="1" thread="6572" file="utils.cpp:6604">

<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="13:49:44.566-480" date="12-12-2019" component="TSManager" context="" type="3" thread="6572" file="tsmanager.cpp:1273">

<![LOG[Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.]LOG]!><time="13:49:44.690-480" date="12-12-2019" component="TSManager" context="" type="1" thread="6572" file="CcmFile.cpp:1154">

<![LOG[Failed to delete directory 'C:\_SMSTaskSequence']LOG]!><time="13:49:44.690-480" date="12-12-2019" component="TSManager" context="" type="2" thread="6572" file="CcmFile.cpp:1318">

<![LOG[SetNamedSecurityInfo() failed.]LOG]!><time="13:49:44.690-480" date="12-12-2019" component="TSManager" context="" type="3" thread="6572" file="utils.cpp:7582">

<![LOG[SetObjectOwner() failed. 0x80070005.]LOG]!><time="13:49:44.690-480" date="12-12-2019" component="TSManager" context="" type="3" thread="6572" file="utils.cpp:7594">

<![LOG[RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.]LOG]!><time="13:49:44.690-480" date="12-12-2019" component="TSManager" context="" type="3" thread="6572" file="utils.cpp:7723">

<![LOG[RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence]LOG]!><time="13:49:44.690-480" date="12-12-2019" component="TSManager" context="" type="2" thread="6572" file="utils.cpp:7807">

Setuperr.log:

2019-12-12 13:49:24, Error                 MOUPG  CSystemHelper::CheckConnectedStandby(642): Result = 0x80070057
2019-12-12 13:49:31, Error                 MOUPG  CSetupManager::CopyUserProvidedFiles(3075): Result = 0x80070003[gle=0x00000002]
2019-12-12 13:49:31, Error                 MOUPG  CSetupManager::ExecuteInstallMode(757): Result = 0x80070003[gle=0x00000002]
2019-12-12 13:49:31, Error                 MOUPG  CSetupManager::ExecuteDownlevelMode(390): Result = 0x80070003[gle=0x00000002]
2019-12-12 13:49:31, Error                 MOUPG  CSetupManager::GetDUSetupResults(6153): Result = 0x80070490
2019-12-12 13:49:34, Error                 MOUPG  CSetupManager::Execute(282): Result = 0x80070003
2019-12-12 13:49:34, Error                 MOUPG  CSetupHost::Execute(400): Result = 0x80070003

LTIApply.log:

<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 9092)]LOG]!><time="18:34:12.000+000" date="12-12-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">

<![LOG[Return code from command = -2147024893]LOG]!><time="18:34:35.000+000" date="12-12-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Setup failed to upgrade OS from  \\SYM-SZ-MDT-01\UPEN$\Operating Systems\Windows 10 x64 en-us\setup.exe, rc = -2147024893]LOG]!><time="18:34:35.000+000" date="12-12-2019" component="LTIApply" context="" type="3" thread="" file="LTIApply">

<![LOG[Event 41022 sent: Setup failed to upgrade OS from  \\SYM-SZ-MDT-01\UPEN$\Operating Systems\Windows 10 x64 en-us\setup.exe, rc = -2147024893]LOG]!><time="18:34:35.000+000" date="12-12-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply">

<![LOG[ZTI ERROR - Non-zero return code by LTIApply, rc = 1]LOG]!><time="18:34:35.000+000" date="12-12-2019" component="LTIApply" context="" type="3" thread="" file="LTIApply">

<![LOG[Event 41002 sent: ZTI ERROR - Non-zero return code by LTIApply, rc = 1]LOG]!><time="18:34:35.000+000" date="12-12-2019" component="LTIApply" context="" type="1" thread="" file="LTIApply"

Looking for GPO or Reg edit to stop Windows Update Notifications

$
0
0

Our AD dept. has a GPO in place to prevent MS Updates except in one OU. No other OU allows Updates.

However, users still get Notifications that updates are available. Of course when they click on trying to get them, they cannot.
Is there a method to stop "Notifications" that updates are available? Even while we prevent updates from downloading, we do not want users to get a notice because all they do is call and ask questions about the notice.

Thanks!

Sysprep error

$
0
0

Hi all,

I am trying to sysprep and capture an image with MDT but Sysprep is failing all the time:

Here is the setupact.log:

SYSPRP Sysprep_Clean_Validate_Opk: Audit mode can't be turned on if there is an active scenario.; hr = 0x800F0975
2019-12-18 17:19:28, Error                 SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x975
2019-12-18 17:19:28, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x975
2019-12-18 17:19:28, Error                 SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x975
2019-12-18 17:19:28, Error      [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x975
2019-12-18 17:19:28, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep cleanup internal providers; hr = 0x80070975
2019-12-18 17:19:28, Info       [0x0f0052] SYSPRP Shutting down SysPrep log
2019-12-18 17:19:28, Info       [0x0f004d] SYSPRP The time is now 2019-12-18 17:19:28

Here is the MDT error screen:

I see a lot of posts about spopk.dll but it seems to be fixed in the latest CU 1903 update, besides I am imaging Win10 1909 with the December CU installed

upgrade task sequence with Full Backup

$
0
0

Good morning, 

I am trying to upgrade my computers from Win 10 1809 to 1909 by using an upgrade task sequence. 

Everything works fine but i want to add a second layer or backup. I am currently using an Capture User State and works great before performing the upgrade but i want to add a full backup to WIM. 

I currently have another task sequence for this but is an replace task sequence and this work in WinPE environment. Is any way i can invoke the replace TS and once finish invoke automatically the upgrade TS? or integrate both in the same sequence? i try this by modifying the ts.xml but after the backup in the WinPE environment the upgrade fail because after the restart is booting WinPE again instead to windows. Is any command to change the WinPE environment back to Windows to continue the upgrade? 

Maybe there is something already made for get done this. 

MDT Lite Touch Failed Return Code -2147467259 0x80004005

$
0
0

Hello, <o:p></o:p>

I am having some problems with my MDT deployments. Everything was working fine, then when I came back from the being off the MDT task sequences error out. I am trying to use MDT to deploy Windows 10 1903.<o:p></o:p>

I am getting one of these two errors. <o:p></o:p>

First Error: (Appears after Pre-Application Updates)

Lite Touch Failed Return Code = -2147467259 0x80004005
Execution engine result code: Reboot(2)
Execution engine result code: Reboot(2)
Execution engine result code: Reboot(2)
Failed to run the action Install Applications.
Incorrect function. (Error:00000001; Source: Windows)
The execution of the group (Custom Tasks) has failed and the execution has been aborted. action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Applications. Execution of task sequence failed.
Incorrect function. (Error:00000001; Source: Windows)
Task Sequence Engine Failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
ReqQueryValueExW is unsuccessful for Software\Microsoft\SMS\TaskSequence,SMSTSendProgram
GetTsRegValue() is unsuccessful. 0x8007002.
Error Task Sequence Manager failed to execute task sequence Code 0x80004005

I have already tried to recreate the task sequence, and adding a reboot step after the pre-application update step. The second error I get is if I disable the updates step in the task.

Lite Touch Failed Return Code = -2147467259 0x80004005
Failed to run the action Install Applications.
Incorrect function. (Error:00000001; Source: Windows)
The execution of the group (Custom Tasks) has failed and the execution has been aborted. action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Install Applications. Execution of task sequence failed.
Incorrect function. (Error:00000001; Source: Windows)
Task Sequence Engine Failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
ReqQueryValueExW is unsuccessful for Software\Microsoft\SMS\TaskSequence,SMSTSendProgram
GetTsRegValue() is unsuccessful. 0x8007002.
Error Task Sequence Manager failed to execute task sequence Code 0x80004005

Any help or insight  that could be given would very appreciated.<o:p></o:p>

<o:p></o:p>

<o:p></o:p>



MDT - UDI - “Active directory credential check” Not Working

$
0
0
Hello,

Imagining computers with MDT via USB drive.  Everything works great except the Wizard is not performing a credential check to AD.

The tech can put anything they want in the user name and password field and it will continue and then during the install will fail because it cannot join the domain.

https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/02/46/17.png

Can you think of any way to troubleshoot this issue?  

Sincerely,

John

MDT 2012: Force MININT and _SMSTaskSequence on C Drive

$
0
0
Hi,

I'm deploying Windows 7 X64 using MDT 2012, I format 3 partitions at the beginning of the task sequence and I assign them specific drive letters during the state restore phase.
I had no problem with MDT 2010 but since I'm using MDT 2012 MININT and _SMSTaskSequence folders are created on partition 2 so when I assign my drive letters deployment fails.
I tried to force SMSTSLocalDataDrive in cs.ini but it seems that MDT doesn't care, I can see in the variables.dat that the C drive is selected but folders are still in my second partition.
Any help?

My Blog: DeployXP [Under Construction]| Viadeo:Mathieu Ait Azzouzene | Linkedin:Mathieu Ait Azzouzene


Custom Task - Run Command Line: Return Code -2147467259 0x80004005

$
0
0
What I'm trying to do:  Use a custom task with a 'run command line' to copy a folder from my deployment share to the C drive of the system I am deploying software to.

What happens:  The system is a freshly deployed Vista Enterprise OS with MS Office 2007 installed from MDT 2010.  Everything works just fine but I can't get this one custom task with two run command line items to work.  I've made sure that I have admin on the system and I'm using litetouch.vbs to start the process from the system I want to install the stuff from since the full install works up to this point.  It is on the domain.  Process is to setup a share via 'net use' to access the deployment server, then run litetouch.vbs from the scripts folder.  Command to be run to copy the folder is as follows.  ( copy \\server\share$\applications\student c:\"student materials" )  Note that this command works from the command line on the system but won't work when placed in the run command line task.  

Red Deployment summary screen, "OS deployment did not complete successfuly"  -- even though there is no OS being deployed....  Error, "Litetouch deployment failed, Return Code = -2147467259 0x40004005". 

Below is the BDD log starting where it started the Custom Task.  Note, the task only has two 'run command line' entries in the task.  One to copy the folder from share to system and one to copy a shortcut from the folder to a previously restored USMT added profile during OS installation.

"<![LOG[Property TaskSequenceName is now = Deploy Student Materials]LOG]!><time="13:40:31.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property TaskSequenceVersion is now = 1.0]LOG]!><time="13:40:31.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Unable to find Task Sequence step of type //step[@type='BDD_InstallOS']]LOG]!><time="13:40:31.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[ Open Control File: Applications]LOG]!><time="13:40:31.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Unable to find Task Sequence step of type //step[@type='BDD_InstallApplication'], performing more exhaustive search...]LOG]!><time="13:40:32.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Unable to find Task Sequence step of type //step[@type='BDD_InstallApplication']]LOG]!><time="13:40:32.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Unable to find Task Sequence step of type //step[@name='Create WIM'], performing more exhaustive search...]LOG]!><time="13:40:32.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Unable to find Task Sequence step of type //step[@name='Create WIM']]LOG]!><time="13:40:32.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property UserCredentials is now = True]LOG]!><time="13:40:47.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property TSGuid is now = {e8c592ee-e00e-47a4-84dd-42bfc503c6f1}]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property OSGUID is now = ]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property DeploymentType is now = CUSTOM]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property UserID is now = bmF0ZS5mb3hf]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property UserDomain is now = YXI=]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WizardComplete is now = Y]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Validating connection to \\SERVER\Share$]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Already connected to server SERVER as that is where this script is running from.]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DestinationDisk and DestinationPartition are not set, reading from TS.XML]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDComputerName is now = ZWA073NB9458C3T]LOG]!><time="13:40:50.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\SERVER\Share$]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z:  = \\SERVER\Share$]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z:  = \\SERVER\Share$]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceRoot is now = \\SERVER\Share$]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentType = CUSTOM]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceRoot = \\SERVER\Share$]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceDrive is now = Z:]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = Z:]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property _SMSTSPackageName is now = Lite Touch Installation]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[SMS Task Sequencer found at \\SERVER\Share$\Tools\X86, copying to C:\MININT\Tools\X86]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\CcmCore.dll to C:\MININT\Tools\X86\CcmCore.dll]LOG]!><time="13:40:51.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\CcmUtilLib.dll to C:\MININT\Tools\X86\CcmUtilLib.dll]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\Smsboot.exe to C:\MININT\Tools\X86\Smsboot.exe]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\SmsCore.dll to C:\MININT\Tools\X86\SmsCore.dll]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TsCore.dll to C:\MININT\Tools\X86\TsCore.dll]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TSEnv.exe to C:\MININT\Tools\X86\TSEnv.exe]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TsManager.exe to C:\MININT\Tools\X86\TsManager.exe]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TsmBootstrap.exe to C:\MININT\Tools\X86\TsmBootstrap.exe]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TsMessaging.dll to C:\MININT\Tools\X86\TsMessaging.dll]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TsProgressUI.exe to C:\MININT\Tools\X86\TsProgressUI.exe]LOG]!><time="13:40:52.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\TSResNlc.dll to C:\MININT\Tools\X86\TSResNlc.dll]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\xprslib.dll to C:\MININT\Tools\X86\xprslib.dll]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Tools\X86\00000409\tsres.dll to C:\MININT\Tools\X86\00000409\tsres.dll]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\SERVER\Share$\Control\6\TS.XML to C:\MININT\Tools\X86]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\VARIABLES.DAT to C:\MININT\Tools\X86\VARIABLES.DAT]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI beginning deployment]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: "C:\MININT\Tools\X86\TsmBootstrap.exe" /env:SAStart]LOG]!><time="13:40:53.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="13:40:54.000+000" date="03-12-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="13:40:54.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property RetVal is now = -2147467259]LOG]!><time="13:40:54.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[CleanStartItems Complete]LOG]!><time="13:40:54.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: MSHTA.exe "\\SERVER\Share$\Scripts\Wizard.hta" /definition:Summary_Definition_ENU.xml]LOG]!><time="13:40:54.000+000" date="03-12-2010" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property definition is now = Summary_Definition_ENU.xml]LOG]!><time="13:40:55.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Microsoft Deployment Toolkit version: 5.0.1641.0]LOG]!><time="13:40:55.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Not Wizard = False]LOG]!><time="13:40:55.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WizardComplete is now = N]LOG]!><time="13:40:55.000+000" date="03-12-2010" component="Wizard" context="" type="1" thread="" file="Wizard">"


Any help in figuring this out would be great.  I think I'm going to redeploy everything but not add it to the domain and see what happens.  I know that Office installs just fine with it on the domain though and all of the permissions work so I'm not sure what the issue with the command line is.

Task Sequence: Dell Command Update 3.1.0

$
0
0

Good morning, 

I am trying to create a task sequence for Dell Command Update version 3.1.0 (the non UWP version).  I have created Dell Command Update version 2.4 with no issues.  It seems that this version of DCU doesn't install during the task sequence, even though the BDD log shows a successful installation.  

<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Language/Locale Identified (in order of precedence): 1033,0409,0x0409,9,0009,0x0009]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Mandatory Single Application install indicated. Guid: {479c77b5-9560-4db8-a872-0edef0457134}]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[################]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Entry: {479c77b5-9560-4db8-a872-0edef0457134}]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Name:  Dell Command Update 3.1.0]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[################]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Validating connection to \\deployserver\DeploymentShare$\Applications\Dell Command Update 3.1.0]LOG]!><time="08:53:52.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Mapping server share: \\deployserver\DeploymentShare$]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Already connected to server deployserver as that is where this script is running from.]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[		Change directory: \\deployserver\DeploymentShare$\Applications\Dell Command Update 3.1.0]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[		Run Command: \\deployserver\DeploymentShare$\Tools\X64\bddrun.exe DCU_Setup_3_1_0.exe /s /v"/qn"]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[ZTI installing application ]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Event 41031 sent: ZTI installing application ]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[About to run command: \\deployserver\DeploymentShare$\Tools\X64\bddrun.exe DCU_Setup_3_1_0.exe /s /v"/qn"]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Command has been started (process ID 10016)]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 10016)]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 10016)]LOG]!><time="08:53:53.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Return code from command = 0]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Application Dell Command Update 3.1.0 installed successfully]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Event 41033 sent: Application Dell Command Update 3.1.0 installed successfully]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Property InstalledApplications001 is now = {479c77b5-9560-4db8-a872-0edef0457134}]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[ZTIApplications processing completed successfully.]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Event 41001 sent: ZTIApplications processing completed successfully.]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications"><![LOG[Command completed, return code = -2147021886]LOG]!><time="08:53:54.000+000" date="12-20-2019" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">


Command Line: DCU_Setup_3_1_0.exe /s /v"/qn"

We also use BigFix in our environment and the package works in that system with no issues.  

What am I doing wrong?  


Need guidance on Adding a 1909 to MDT deployments

$
0
0

Hello,

We had a Dell Engineer implement MDT in our environment.  Currently, we use MDT made USB Drives to build all of our new computers.  The OS installed is 1809 but I need the steps to upgrade the OS deployed to be 1909.  I am a relative Nube keep in mind but I do have full access to the MDT console.  Thank you. 

Viewing all 11297 articles
Browse latest View live