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

MDT 8456 - Windows 10 1903 + Windows Updates ~ Deployment pauses for almost an hour! HELP!

July 29, 2019, 1:03 pm
$
0
0

I am trying to deploy an updated Windows 10 1903 (Build 10.0.18362.239) image using MDT 8456 / ADK 1903 / PS Addon 1903. I am able to deploy an image without the updates and also can deploy this updated version to legacy bios (non UEFI) without any issues.

Any suggestions?

Events From BDD.log

Event 41001 sent: ZTIWinRE processing completed successfully.ZTIWinRE7/29/2019 2:05:50 PM0 (0x0000)
Property PHASE is now = STATERESTOREZTINextPhase7/29/2019 2:05:50 PM0 (0x0000)
ZTINextPhase COMPLETED.  Return Value = 0 ZTINextPhase7/29/2019 2:05:50 PM0 (0x0000)
ZTINextPhase processing completed successfully. ZTINextPhase7/29/2019 2:05:50 PM0 (0x0000)

Event 41001 sent: ZTINextPhase processing completed successfully. ZTINextPhase 7/29/2019 2:05:50 PM 0 (0x0000)

<< PAUSE FOR ABOUT AN HOUR >> Then it will carry on as if nothing is wrong.

ZTIUtility!GetAllFixedDrives (False)LiteTouch7/29/2019 2:58:41 PM0 (0x0000)
New ZTIDisk : \\WUPDATES-FTW1\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LiteTouch7/29/2019 2:58:41 PM0 (0x0000)
New ZTIDiskPartition : \\WUPDATES-FTW1\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\WUPDATES-FTW1\root\cimv2:Win32_LogicalDisk.DeviceID="C:"LiteTouch7/29/2019 2:58:41 PM0 (0x0000)
New ZTIDisk : \\WUPDATES-FTW1\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LiteTouch7/29/2019 2:58:41 PM0 (0x0000)
New ZTIDisk : \\WUPDATES-FTW1\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"LiteTouch7/29/2019 2:58:41 PM0 (0x0000)
ZTIUtility!GetAllFixedDrives =   C: LiteTouch7/29/2019 2:58:41 PM0 (0x0000)
Found existing task sequence state information in C:\_SMSTaskSequence, will continueLiteTouch7/29/2019 2:58:41 PM0 (0x0000)
Property LTIDirtyOS is now = FALSELiteTouch7/29/2019 2:58:41 PM0 (0x0000)
Creating startup folder item to run LiteTouch.wsf once the shell is loaded.LiteTouch7/29/2019 2:58:41 PM0 (0x0000)

Here is the link to the entire BDD.log if you need it.

- Bob


↧
Search

Service Pack for ProLiant

January 7, 2019, 6:43 am
$
0
0

Has anyone managed to install HP Service Pack for ProLiant with SCCM or MDT any version since 2018.06?

I am using smartupdate /s / softwareonly and getting exit code 1. 

Don't think this install can create log files. Thank you.

↧
↧

MDT 2012 - Failed to Run Action: Install Operating System Access is Denied (Error: 0000005; Source: Windows)

July 3, 2013, 11:53 am
$
0
0

Unable to deploy any image with WIM file. Vanilla or Custom Image gives the following error:

ZTI Error – Unhandled error returned by LTIApply: invalid procedure call or argument (5)

Litetouch deployment failed, Return code = -2147467259 0x80004005

Failed to run action: Install Operating System.

Access is denied (Error: 00000005; Source: Windows)

Tried Giving Everyone Full rights to the deployment share

Rebooted Server

Updated Deployment Share

Any ideas would be great!

Thanks

Rick

Richard Ray

↧

Auto approval of windows 7 asset to windows 10 by using windows 10 dashboard

August 13, 2019, 7:50 am
$
0
0

  • Hi Guys,

    Good Evening !!

    Here is the thing on which I need ideas and help from you guys.

    Presently we are in that phase where we are migrating all the machines from Windows 7 to Windows 10.

    For this we are using windows 10 dashboard to approve the assets which are ready to migrate from 7 to 10 and presently we are doing it manually by going to dashboard site and then we have few options to enter the asset tag and then edit it and check the approved option and update so that the asset will be ready for the migration.

    And now comes my requirement.

    I want to automate this process using power-shell script every time when we get some request to approve one asset i want to write a script so that it will reduce the manual intervention and also reduce the time to approve the assets.

    I already wrote two line script like example by using invoke-webrequestcommand we can access the dashboard. from their on wards i am unable to move further like how to define new objects and all. 

  • I do not no how to define new objects and all by using windows 10 dashboard.

    Please do help me in this how to proceed or any ideas how to do this to approach our  requirement.

    Thanks in Advance :) 

↧

mdt copy failed unable to copy the item name already exists

August 13, 2019, 2:30 pm
$
0
0

Multiple, iterative attempts to copy a MDT Deployment Share | Out-of-Box Drivers | Windows 10 x64 | Model folder to a different MDT Deployment Share | Out-of-Box Drivers | Windows 10 x64 folder only copies a small fraction of the drivers then the driver copies fail with a pop-up message stating:  MDT copy failed | Unable to copy the item | Name already exists.  Initially, the original driver folder was renamed (xyz Old).  Then the original folder as well as the new folder, with the fraction of drivers copied, were deleted.

Please provide any suggestions or recommendations for addressing this error.

↧
↧

MDT Restore User State error: The drive cannot find the sector requested. (Error: 0000001B; Source: Windows)

May 9, 2017, 7:24 am
$
0
0

I need to figure out what is causing the transfer of user data and settings from a Win 7 to a Win 10 machine to fail. Here are my steps/details:

1. Run the backup only task sequence on the Win 7 machine

2. Start OSD in WinPE (MDT 8443) using the our Win 10 image, elect to restore the user data and settings from the location where it was saved in step 1.

3. The OS is upgraded, but USMT fails with these errors:

ZTI ERROR - Non-zero return code from Loadstate, RC = 27

Litetouch deployment failed, Return Code = -2147467259  0x80004005

Failed to run the restore action:Restore User State

...

SetNamedSecurityInfo() failed.

SetObjectOwner() failed. 0x80070005

RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence,SMSTSEndProgram

GetTsRegValue() is unsuccessful 0x80070002

BDD.log errors:

ZTI ERROR - Non-zero return code from Loadstate, RC = 27    ZTIUserState 

Litetouch deployment failed, Return Code = -2147467259  0x80004005    LiteTouch

Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005    LiteTouch

smsts.log errors:

Failed to run the action: Restore User State.
The drive cannot find the sector requested. (Error: 0000001B; Source: Windows)    TSManager    5/8/2017 5:15:42 PM    5112 (0x13F8)

The execution of the group (State Restore) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)    TSManager        5112 (0x13F8)

Failed to run the last action: Restore User State. Execution of task sequence failed.
The drive cannot find the sector requested. (Error: 0000001B; Source: Windows)    TSManager     5112 (0x13F8)

Here's the rules file, if it helps:

[Settings]
Priority=Default

[Default]
_SMSTSORGNAME=UCO
OSInstall=Y
UserDataLocation=AUTO
TimeZoneName=Central Standard Time
JoinDomain=[domain].local
DomainAdmin=[domain]\account_JD
DomainAdminPassword=areallycomplexpassword
Administrators001=[domain]\[group]
MachineObjectOU=OU=New Builds,OU=whatever,DC=[domain],DC=local
SLShare=\\MANIA\Logs$
ScanStateArgs=/ue:*\* /ui:[XXX]\*
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
HideShell=YES
ApplyGPOPack=NO
WSUSServer=http://[server.domain.local]:8530
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=NO
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=NO
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipFinalSummary=NO
EventService=http://[server.domain.local]:9800
↧

Trouble booting To MDT, keep getting the command line

April 25, 2019, 5:25 pm
$
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



↧

USMT prevent machine going to sleep

August 14, 2019, 4:12 am
$
0
0

I'm finding that when using loadstate.exe remotely the machine it's running against is going to sleep.  When that happens you get a 4minute countdown to reconnect.  Even bringing the machine out of sleep during this time doesn't continue the loadstate process.

Is there a method to prevent the machine from going to sleep during both a scanstate and a loadstate process?

↧
Search

Could not parse or process the unattend answer file

May 29, 2019, 10:59 am
$
0
0

Hi,

This has been working perfectly since day 1, now all of a sudden not! Full message:

Windows could not parse or process the unattend answer file for pass [specialize]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Deployment]

That section of unattend.xml in Control\xxx\unattend.xml (which was last modified 04/04/2017):

<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><RunSynchronous><RunSynchronousCommand wcm:action="add"><Description>EnableAdmin</Description><Order>1</Order><Path>cmd /c net user Administrator /active:yes</Path></RunSynchronousCommand><RunSynchronousCommand wcm:action="add"><Description>UnfilterAdministratorToken</Description><Order>2</Order><Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path></RunSynchronousCommand><RunSynchronousCommand wcm:action="add"><Description>disable user account page</Description><Order>3</Order><Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path></RunSynchronousCommand><RunSynchronousCommand wcm:action="add"><Description>disable async RunOnce</Description><Order>4</Order><Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer /v AsyncRunOnce /t REG_DWORD /d 0 /f</Path></RunSynchronousCommand></RunSynchronous></component>

↧
↧

HELP - ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)

December 1, 2016, 9:16 am
$
0
0

Ok so here's the issue I am getting.

After my image is installed using LiteTouch (booted from a USB) the final step where it is trying to apply unattend.xml with DISM, I get the following error:

ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)

The system will then reboot, and it cannot find the file "LTIBootstrap.vbs" in standard locations.

Here is a portion of the code from BDD.LOG 

<![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 1300)]LOG]!><time="10:26:06.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[The image \\LIB-AU16640\Win10Deploy$\Operating Systems\Windows 10 Enterprise 2016 LTSB x64\Sources\install.wim was applied successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Find the boot drive (if any) [True] [10.0.14393.0] [False]]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDiskPartition : \\MININT-7AH5HU7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDisk : \\MININT-7AH5HU7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Ready to Prepare boot partition: V:]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property UILanguage is now = en-US]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: cscript.exe //nologo "\\LIB-AU16640\Win10Deploy$\Scripts\ztiRunCommandHidden.wsf" ""\\LIB-AU16640\Win10Deploy$\Tools\X64\BCDBoot.exe" F:\windows /l en-US  /s V: /f UEFI"]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[About to run command: \\LIB-AU16640\Win10Deploy$\Tools\X64\BCDBoot.exe F:\windows /l en-US  /s V: /f UEFI]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Command has been started (process ID 600)]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 600)]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[  Console > Boot files successfully created.]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Return code from command = 0]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden"><![LOG[Command has returned: 0]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Run Command: X:\windows\SYSTEM32\bcdedit.exe /timeout 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCD> The operation completed successfully.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Created scratch folder.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copy File: F:\MININT\unattend.xml to F:\Windows\Panther\Unattend.xml]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copied unattend.xml to F:\Windows\Panther for image apply.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: dism.exe /Image:F:\ /Apply-Unattend:F:\Windows\Panther\Unattend.xml /ScratchDir:F:\MININT\Scratch]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 1524)]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Version: 10.0.14393.0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Image Version: 10.0.14393.0]LOG]!><time="10:26:14.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply"><![LOG[Command completed, return code = -2147467259]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Property RetVal is now = -2147467259]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[CleanStartItems Complete]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[TSCore.dll not found, not unregistering.]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\LTICleanup.wsf"]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Microsoft Deployment Toolkit version: 6.3.8298.1000]LOG]!><time="10:26:42.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Re-enabling UAC for built-in Administrator account]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Logs contained 2 errors and 0 warnings.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[No Windows PE image to delete.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Checking mapped network drive.]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[testing drive Z: mapped to \\LIB-AU16640\Win10Deploy$]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Disconnecting drive Z: mapped to \\LIB-AU16640\Win10Deploy$]LOG]!><time="10:26:43.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Cleaning up F:\MININT directory.]LOG]!><time="10:26:44.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup"><![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="10:26:44.000+000" date="12-01-2016" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
and LTIApply.log
<![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 1300)]LOG]!><time="10:26:06.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[The image \\COMPUTERNAME\Win10Deploy$\Operating Systems\Windows 10 Enterprise 2016 LTSB x64\Sources\install.wim was applied successfully.]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Find the boot drive (if any) [True] [10.0.14393.0] [False]]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDiskPartition : \\MININT-7AH5HU7\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[New ZTIDisk : \\MININT-7AH5HU7\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-7AH5HU7\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Ready to Prepare boot partition: V:]LOG]!><time="10:26:07.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property UILanguage is now = en-US]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: cscript.exe //nologo "\\COMPUTERNAME\Win10Deploy$\Scripts\ztiRunCommandHidden.wsf" ""\\LIB-AU16640\Win10Deploy$\Tools\X64\BCDBoot.exe" F:\windows /l en-US  /s V: /f UEFI"]LOG]!><time="10:26:08.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has returned: 0]LOG]!><time="10:26:09.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Run Command: X:\windows\SYSTEM32\bcdedit.exe /timeout 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCD> The operation completed successfully.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Created scratch folder.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copy File: F:\MININT\unattend.xml to F:\Windows\Panther\Unattend.xml]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Copied unattend.xml to F:\Windows\Panther for image apply.]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[About to run command: dism.exe /Image:F:\ /Apply-Unattend:F:\Windows\Panther\Unattend.xml /ScratchDir:F:\MININT\Scratch]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 1524)]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Version: 10.0.14393.0]LOG]!><time="10:26:10.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Image Version: 10.0.14393.0]LOG]!><time="10:26:14.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > The operation completed successfully.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="10:26:41.000+000" date="12-01-2016" component="LTIApply" context="" type="3" thread="" file="LTIApply">

I've noticed in these logs for whatever reason its looking for "F:" locations. My drive is C:

Any suggestions??


↧

Move Data and Settings always shows up in a Task

August 14, 2019, 2:23 pm
$
0
0

We have a standard client task setup and an unneeded step in the wizard is "Move Data and Settings". I have the following customsettings.ini set:

[Settings]
Priority=WizardMode, Model, ByVMType, TaskSequenceID, Default

[IT] 
WizardSelectionProfile=ITD
AdminPassword=asdfasdf

[Dev]
WizardSelectionProfile=Development
AdminPassword=asdfasdf

[Restart] 
WizardSelectionProfile=Restart

[Surface Pro 3]
XResolution=2160
YResolution=1440

[ByVMType]
Subsection=IsVM-%ISVM%

[IsVM-True]
BitsPerPel=32
VRefresh=60
XResolution=1024
YResolution=768

[TASK-002]
DoCapture=YES
OSInstall=YES
AdminPassword=asdfasdf
JoinWorkgroup=WORKGROUP
HideShell=NO
FinishAction=SHUTDOWN
OSDComputerName=WIN10RefImage
ApplyGPOPack=NO

'Disable Move Data and Settings
SkipUserData=YES
USMTOfflineMigration=False
UserDataLocation=NONE
UDShare=NONE
UserDataLocation=NONE

ComputerBackupLocation=\\server\deployment$\Captures
BackupFile=%HostName%_Virtual_#month(date) & "-" & day(date) & "-" & year(date)#.wim

SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipLocaleSelection=YES
SkipTaskSequence=YES
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=NO
SkipFinalSummary=YES

[Default]
_SMSTSOrgName= Provisioning in progress...
OSInstall=YES

DeployRoot=\\server\Deployment$

'Default Windows logging location
SLShare=\\server\Deployment$\Logs
SLShareDynamicLogging =\\server\Deployment$\Logs\Dynamic

SkipCapture=YES
SkipAdminPassword=YES
SkipAppsOnUpgrade=YES
SkipPackageDisplay=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipDomainMembership=YES
SkipFinalSummary=NO
SkipComputerName=Yes

SkipBitLocker=YES
SkipBDDWelcome=Yes
BDEInstallSuppress=NO
BDEDriveLetter=V:
BDEInstall=TPMPin
BDEPin=network=-0
TpmOwnerPassword=asdfasdfasf

PrepareWinRE=Yes

KeyboardLocale=en-US
UILanguage=en-US
UserLocale=en-US
SkipTimeZone=Yes
TimeZoneName=Eastern Standard Time
SkipLocaleSelection=Yes

UserID=mdtuser
UserDomain=asdfasdf
UserPassword=asdfasdf

JoinDomain=asdfasf
DomainAdmin=mdtuser
DomainAdminDomain=asdfasdf
DomainAdminPassword=asfasdf

WSUSServer=http://WSUS.domain.LOCAL
EventService=http://server:9800

Reviewing the dynamic logs I see this:

WizardProperty TaskSequenceID is now = TASK-0028/14/2019 5:12:58 PM0 (0x0000)
WizardProperty TaskSequenceName is now = Update Reference Physical Image - Windows 10 v1809- Patch, Snapshot VM, Sysprep and Capture8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty TaskSequenceVersion is now = 1.08/14/2019 5:12:58 PM0 (0x0000)
WizardProperty TaskSequenceTemplate is now = Client.xml8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageIndex is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageSize is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageFlags is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageBuild is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty InstallFromPath is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageProcessor is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty OSGUID is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty IsOSUpgrade is now = 8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty DeploymentType is now = NEWCOMPUTER8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty IsOSUpgrade is now = 08/14/2019 5:12:58 PM0 (0x0000)
WizardProperty OSGUID is now = {4cf9d828-4f1c-4091-9621-5e4e291b584e}8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageIndex is now = 18/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageSize is now = 141458/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageFlags is now = Enterprise8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageBuild is now = 10.0.17763.4758/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageProcessor is now = x648/14/2019 5:12:58 PM0 (0x0000)
WizardProperty ImageLanguage001 is now = en-US8/14/2019 5:12:58 PM0 (0x0000)
WizardInstallFromPath: \\server\Deployment$\Operating Systems\Windows 10 Enterprise x64 v1809 Reference Image\Sources\install.wim8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty InstallFromPath is now = \\filesrv1\deployment$\Operating Systems\Windows 10 Enterprise x64 v1809 Reference Image\sources\install.wim8/14/2019 5:12:58 PM0 (0x0000)
WizardSourcePath: \\FILESRV1\Deployment$\Operating Systems\Windows 10 Enterprise x64 v1809 Reference Image8/14/2019 5:12:58 PM0 (0x0000)
WizardProperty SourcePath is now = \\server\Deployment$\Operating Systems\Windows 10 Enterprise x64 v1809 Reference Image8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence Item: //step[@name='Offline User State Capture']8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence step of type //step[@name='Offline User State Capture'] = True8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence Item: //step[@name='Restore User State']8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence step of type //step[@name='Restore User State'] =8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence Item: //step[@type='BDD_InstallRoles']8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence step of type //step[@type='BDD_InstallRoles'] =8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence Item: //step[@type='BDD_InstallApplication' and ./defaultVarList/variable[@name='ApplicationGUID'] and ./defaultVarList[variable='']]8/14/2019 5:12:58 PM0 (0x0000)
WizardFound Task Sequence step of type //step[@type='BDD_InstallApplication' and ./defaultVarList/variable[@name='ApplicationGUID'] and ./defaultVarList[variable='']] =8/14/2019 5:12:58 PM0 (0x0000)
WizardAdd Entry to Dialog: MBR  0  1  1  Primary  499  \\?\Volume{72251e28-0000-0000-0000-100000000000}  C:\  System Reserved  1328/14/2019 5:12:58 PM0 (0x0000)
WizardPartition too small Disk0part1 OK TO Skip! 4998/14/2019 5:12:58 PM0 (0x0000)
WizardAdd Entry to Dialog: MBR  0  2  0  Primary  60939  \\?\Volume{72251e28-0000-0000-0000-401f00000000}  D:\  C_Drive  255568/14/2019 5:12:58 PM0 (0x0000)

I haven't a clue where that Offline User State Capture is being set to true. Where else could I look?

↧

How to upgrade MDT integrated with SCCM

August 15, 2019, 5:46 am
$
0
0

Hi Team, 

My organisation wants me to upgrade SCCM from v1706 to v1802 and for imaging purpose we have MDT integrated. 

I would like to know :- 

1. How to upgrade MDT and which version is compatible with SCCM 1806

2. Would there be any impact if I upgrade MDT on boot images and existing images ?

↧

Cannot able to see lite touchx64 option in windows boot manager

August 15, 2019, 6:35 am
$
0
0

Hi folks,

I’m new to this mdt environment.we are using server2008r2 installed with MDT, windows ADK and windows PE along with WDS. I’ve configured deployment share with the help of Lynda.com .No error popped up while configuring. But when I connect client in our domain, tried network boot, I cannot able to see “lite touch x64”option, eventually unable to deploy win 10 in client pc’s. Could you guys help me out in narrowing down the issue.

thanks,

↧
↧

PowerShell MoveOU Script

August 7, 2019, 10:13 am
↧

Windows 10 1903 - KB4498523 + KB4497935 - DISM /ResetBase will fail (Meant to be fixed with SSU KB4498523)

May 31, 2019, 1:36 pm
$
0
0

This is a newly installed Windows Preinstallation Environment Windows 10 Assessment and Deployment Toolkit 18362.1

Image

Now I am quoting the following from https://support.microsoft.com/en-au/help/4498523/windows-10-update-kb4498523

Servicing stack update for Windows 10, Version 1903: May 29, 2019

 

  • Addresses an issue in which updates may fail to install after the /resetbase command in DISM is run.

PS E:\WinROG> DISM /Image:mount\OS /Cleanup-Image /StartComponentCleanup 
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.145

Error: 0x800f0806

The operation could not be completed due to pending operations.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
PS E:\WinROG> DISM /Unmount-Image /MountDir:mount\OS /DISCARD 
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Unmounting image
[==========================100.0%==========================]
The operation completed successfully.

2019-06-01 02:43:18, Warning DISM DISM Provider Store: PID=1632 TID=14016 Failed to load the provider: D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

If you look carefully, the above screenshot shows that this MetaDeployProvider.dll DOES NOT EXIST for the ADK Release 18362.1.

While this issue doesn't break the OS as much as the previous bug I posted about the ADK - https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-1903-dear-microsoft-please-remember-to/e9e9e28a-c3f6-4e24-a900-f48a85b20431?tm=1558465537818

More log about the error posted here:

https://techcommunity.microsoft.com/t5/System-Center-Configuration/Windows-10-0-18362-145-KB4498523-DISM-fails-offline-ResetBase/td-p/661335

-NeoB

↧
Search

After deployment I want the client to start with the login page for domain admin. How?

August 16, 2019, 3:19 am
$
0
0

Hi!

After checking the internet for a solution most people want the client to start with autologon for local admin, or just login page for local admin, but not me. I choose to be original....

OK, after joining the domain at the end of deployment the client autologons to the local admin's desktop. So I have to log off so it goes back to login page and I have to choose "another user" so i can log in to the domain admin's desktop. I don't want that.

I want the client to finish deployment by opening the login page for domain admin, so I can log in by myself.

I think it has something to do with unattended file, but I'm not sure of course. Anyway, here is my unattended file, that is part of it that I think might be relevant:

<settings pass="generalize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
        </component>
    </settings>
    <settings pass="specialize">
        <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Home_Page>https://xxxxxx.xx</Home_Page>
            <TabProcessGrowth>Medium</TabProcessGrowth>
        </component>
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>EnableAdmin</Description>
                    <Order>1</Order>
                    <Path>cmd /c net user Administrator /active:no</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>UnfilterAdministratorToken</Description>
                    <Order>2</Order>
                    <Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>disable user account page</Description>
                    <Order>3</Order>
                    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>disable async RunOnce</Description>
                    <Order>4</Order>
                    <Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer /v AsyncRunOnce /t REG_DWORD /d 0 /f</Path>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>

Anyone who have a clue? Thanx :)


↧

MDT Custom Task Sequence is failing with error -2147467259 0x80004005

August 16, 2019, 3:47 am
$
0
0

Hi all,

First some background, I want to deploy Windows 10 1903 with MDT and AutoPilot. This is possible with a custom task. I found this article https://osddeployment.dk/2018/12/08/how-to-deploy-autopilot-device-fast-with-mdt/.

Short version, create a new custom Task Sequence and add a few steps in the Task Sequence:

  1. Gather local (Set a new Customsettings.ini (optional))
  2. Format and Partition Disk (BIOS) (Only use this if the devices do not support UEFI)
  3. Format and Partition Disk (UEFI)
  4. Copy scripts (Step from a standard MDT Task Sequence)
  5. Configure (Step from a standard MDT Task Sequence)
  6. Install Operating System
  7. Apply the AutopilotConfigurationFile.json to the new device
  8. Delete unattend.xml
  9. Copy a SetupComplete.cmd to run some post cleanup after MDT
  10. Restart computer so that the device will end up in OOBE for the end user

The Task Sequence is failing on number 5. This task look like this:

I have checked the SMSTS log and found this part:

Set a global environment variable _SMSTSLogPath=X:\WINDOWS\TEMP\SMSTSLog	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Expand a string: cscript.exe “%SCRIPTROOT%\ZTIConfigure.wsf"	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Expand a string: 	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Start executing the command line: cscript.exe “%SCRIPTROOT%\ZTIConfigure.wsf"	TSManager	15-8-2019 17:05:15	1856 (0x0740)
!--------------------------------------------------------------------------------------------!	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Expand a string: WinPEandFullOS	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Executing command line: cscript.exe “%SCRIPTROOT%\ZTIConfigure.wsf"	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Process completed with exit code 1	TSManager	15-8-2019 17:05:15	1856 (0x0740)
!--------------------------------------------------------------------------------------------!	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Could not find CCM install folder. Don't use ccmerrors.dll	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Failed to run the action: Configure. 
Unknown error (Error: 00000001; Source: Unknown)	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Set a global environment variable _SMSTSLastActionRetCode=1	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Clear local default environment	TSManager	15-8-2019 17:05:15	1856 (0x0740)
Failed to run the action: Configure. Execution has been aborted	TSManager	15-8-2019 17:05:15	1856 (0x0740)

This part is the strange part: 

Expand a string: cscript.exe “%SCRIPTROOT%\ZTIConfigure.wsf"

It looks like the % is malformed... How can I fix that? The screenshot shows a correct %....

↧
↧

MDT 8456 disable built-in administrator

August 16, 2019, 5:20 am
$
0
0

Hi, all!

Got a problem - can't disable administrators account in the end of deployment.

I tried to rename built-in account to "admin" with no luck. 

Tried to create a new account "admin" with specified password - that worked, but in the custom task, that was made by solution from here i'm getting error.

can you help me, pls?

Maybe there ate other ways to make it work, what i need is to disable built-in local administrator, and create a new one with specified password.

↧

MDT - Enable Bitlocker - Write Recovery Key to AD Not Working - Group Policy?

August 16, 2019, 5:28 am
$
0
0

Hi

I am having an issue with Bitlocker writing the recovery key back to AD – (Being enabled from a MDT task sequence).

MDT Version: 2013 6.3.8456.1000 (January 25th 2019)

Windows Client Version (deployed too): 1903

In my task sequence – State Restore, I have a step to Enable BitLocker:

Choose the drive to encrypt: Current operating system drive

Key Management: TPM only

Choose where to create the recover key: In active directory

The drive encrypts but I get left with the recovery key written to a .txt file to the root of the C drive and nothing in AD.

I have ruled out it being AD schema related (Server 2012R2) as have existing recovery keys written to AD by manually enabling bitlocker on machines.

I have the corresponding GP’s applied (to the correct OU where the computer is) to write the recover key to AD.

So what I have noticed is that if I put a pause in the TS just before enabling bitlocker, and do a manual gpupdate /force direct from the OS, and then continue, bitlocker enables and writes the key to AD. It definitely appears to be the situation that the GP hasn’t applied during deployment and as a result, the OS hasn’t got the necessary settings to write to AD.

(There are no Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\FVE reg keys prior to gpupdating).

Has anyone else experienced this? I have read that gpupdate /force is not possible from a task sequence which has left me ‘scratching my head’ a bit………..

Thanks

Tom

↧

Offline Full MDT USB Media fails Task Sequence Help required

August 16, 2019, 7:26 am
$
0
0

Hi All,

I am currently having a lot of issues with getting an offline task sequence Windows 10 v1809 with all drivers injected to successfully complete the deployment. I have followed the document provided in a previous post by another MDT Engineer on here. I was able to successfully deploy to a vm when I used a new deployment share i built from scratch.

I need to do this for another production deployment share but the deployment fails even though I have the drivers injected for this specific model, same rules and answer file. I have the BDD log file and smsts log file when it finished the deployment attached. Is there anybody there that can assist that has created an MDT full usb offline before? Is there anything showing in the BDD log or smsts log which would identify why this deployment is failing?

BDD Log snippet with errors : 

Not running within WinPE.LiteTouch16/08/2019 19:45:290 (0x0000)
Property DeployRoot is now = D:\DeployLiteTouch16/08/2019 19:45:290 (0x0000)
Property ResourceRoot is now = D:\DeployLiteTouch16/08/2019 19:45:290 (0x0000)
Property DeploymentMethod is now = MEDIALiteTouch16/08/2019 19:45:290 (0x0000)
DeploymentMethod = MEDIALiteTouch16/08/2019 19:45:290 (0x0000)
DeployRoot = D:\DeployLiteTouch16/08/2019 19:45:290 (0x0000)
Property DeployDrive is now = D:LiteTouch16/08/2019 19:45:290 (0x0000)
DeployDrive = D:LiteTouch16/08/2019 19:45:290 (0x0000)
Phase = STATERESTORELiteTouch16/08/2019 19:45:290 (0x0000)
Using a local or mapped drive, no connection is required.LiteTouch16/08/2019 19:45:290 (0x0000)
Property DeployDrive is now = D:LiteTouch16/08/2019 19:45:290 (0x0000)
DeployDrive = D:LiteTouch16/08/2019 19:45:290 (0x0000)
Using a local or mapped drive, no connection is required.LiteTouch16/08/2019 19:45:290 (0x0000)
DeploymentType = NEWCOMPUTERLiteTouch16/08/2019 19:45:290 (0x0000)
ResourceRoot = D:\DeployLiteTouch16/08/2019 19:45:290 (0x0000)
Property ResourceDrive is now = D:LiteTouch16/08/2019 19:45:290 (0x0000)
ResourceDrive = D:LiteTouch16/08/2019 19:45:290 (0x0000)
Property _SMSTSPackageName is now = LiteTouch16/08/2019 19:45:290 (0x0000)
SMS Task Sequencer found at D:\Deploy\Tools\X64, copying to C:\MININT\Tools\X64LiteTouch16/08/2019 19:45:290 (0x0000)
Copying D:\Deploy\Tools\X64\CcmCore.dll to C:\MININT\Tools\X64\CcmCore.dllLiteTouch16/08/2019 19:45:290 (0x0000)
Copying D:\Deploy\Tools\X64\CcmUtilLib.dll to C:\MININT\Tools\X64\CcmUtilLib.dllLiteTouch16/08/2019 19:45:290 (0x0000)
Copying D:\Deploy\Tools\X64\Smsboot.exe to C:\MININT\Tools\X64\Smsboot.exeLiteTouch16/08/2019 19:45:290 (0x0000)
Copying D:\Deploy\Tools\X64\SmsCore.dll to C:\MININT\Tools\X64\SmsCore.dllLiteTouch16/08/2019 19:45:290 (0x0000)
Copying D:\Deploy\Tools\X64\TsCore.dll to C:\MININT\Tools\X64\TsCore.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\TSEnv.exe to C:\MININT\Tools\X64\TSEnv.exeLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\TsManager.exe to C:\MININT\Tools\X64\TsManager.exeLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\TsmBootstrap.exe to C:\MININT\Tools\X64\TsmBootstrap.exeLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\TsMessaging.dll to C:\MININT\Tools\X64\TsMessaging.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\TsProgressUI.exe to C:\MININT\Tools\X64\TsProgressUI.exeLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\TSResNlc.dll to C:\MININT\Tools\X64\TSResNlc.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\msvcp120.dll to C:\MININT\Tools\X64\msvcp120.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\msvcr120.dll to C:\MININT\Tools\X64\msvcr120.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\CommonUtils.dll to C:\MININT\Tools\X64\CommonUtils.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\ccmgencert.dll to C:\MININT\Tools\X64\ccmgencert.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Copying D:\Deploy\Tools\X64\00000409\tsres.dll to C:\MININT\Tools\X64\00000409\tsres.dllLiteTouch16/08/2019 19:45:300 (0x0000)
Reading D:\Deploy\Control\\TS.XMLLiteTouch16/08/2019 19:45:300 (0x0000)
File: D:\Deploy\Control\\TS.XML Line: 0 - The system cannot locate the object specified.
 - LiteTouch16/08/2019 19:45:300 (0x0000)
FAILURE ( 5495 ): -2146697210  0x800C0006: Create MSXML2.DOMDocument  .ParseErr.ErrCode.LiteTouch16/08/2019 19:45:300 (0x0000)
Event 41002 sent: FAILURE ( 5495 ): -2146697210  0x800C0006: Create MSXML2.DOMDocument  .ParseErr.ErrCode.LiteTouch16/08/2019 19:45:300 (0x0000)

SMSTS Log :

Set a local default variable OSDDiskIndexTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDDiskPartitions1TypeTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable DONotCreateExtraPartitionTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0Type TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0FileSystemTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0BootableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0QuickFormatTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0VolumeNameTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0Size TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0SizeUnitsTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions0VolumeLetterVariableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1Type TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1FileSystemTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1BootableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1QuickFormatTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1VolumeNameTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1Size TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1SizeUnitsTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions1VolumeLetterVariableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2Type TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2FileSystemTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2BootableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2QuickFormatTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2VolumeNameTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2Size TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2SizeUnitsTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions2VolumeLetterVariableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3Type TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3FileSystemTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3BootableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3QuickFormatTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3VolumeNameTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3Size TSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3SizeUnitsTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitions3VolumeLetterVariableTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitionsTSManager16/08/2019 19:32:081812 (0x0714)
Set a local default variable OSDPartitionStyle TSManager16/08/2019 19:32:081812 (0x0714)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLogTSManager16/08/2019 19:32:081812 (0x0714)
Evaluating an AND expressionTSManager16/08/2019 19:32:081812 (0x0714)
Evaluating a variable condition expressionTSManager16/08/2019 19:32:081812 (0x0714)
Expand a string: equalsTSManager16/08/2019 19:32:081812 (0x0714)
Expand a string: IsUEFITSManager16/08/2019 19:32:081812 (0x0714)
Expand a string: TrueTSManager16/08/2019 19:32:081812 (0x0714)
The condition for the action (Format and Partition Disk (UEFI)) is evaluated to be trueTSManager16/08/2019 19:32:081812 (0x0714)
Expand a string: cscript.exe "%SCRIPTROOT%\ZTIDiskpart.wsf"TSManager16/08/2019 19:32:081812 (0x0714)
Expand a string: TSManager16/08/2019 19:32:081812 (0x0714)
Start executing the command line: cscript.exe "%SCRIPTROOT%\ZTIDiskpart.wsf"TSManager16/08/2019 19:32:081812 (0x0714)
!--------------------------------------------------------------------------------------------!TSManager16/08/2019 19:32:081812 (0x0714)
Expand a string: WinPETSManager16/08/2019 19:32:081812 (0x0714)
Executing command line: cscript.exe "%SCRIPTROOT%\ZTIDiskpart.wsf"TSManager16/08/2019 19:32:081812 (0x0714)
Process completed with exit code 0TSManager16/08/2019 19:32:211812 (0x0714)
!--------------------------------------------------------------------------------------------!TSManager16/08/2019 19:32:211812 (0x0714)
Successfully completed the action (Format and Partition Disk (UEFI)) with the exit win32 code 0TSManager16/08/2019 19:32:211812 (0x0714)
Executing in non SMS standalone mode. Ignoring send a task execution status message requestTSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSLastActionRetCode=0TSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSLastActionName=Format and Partition Disk (UEFI)TSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSLastActionSucceeded=trueTSManager16/08/2019 19:32:211812 (0x0714)
Expand a string: %_SMSTSMDataPath%\LogsTSManager16/08/2019 19:32:211812 (0x0714)
Clear local default environmentTSManager16/08/2019 19:32:211812 (0x0714)
C:\_SMSTaskSequence does not existTSManager16/08/2019 19:32:211812 (0x0714)
Failed to create C:\_SMSTaskSequence (3)TSManager16/08/2019 19:32:211812 (0x0714)
Failed to create user-specified local data path C:\_SMSTaskSequence. Error 0x80070003TSManager16/08/2019 19:32:211812 (0x0714)
F:\_SMSTaskSequence does not existTSManager16/08/2019 19:32:211812 (0x0714)
Updated security on object F:\_SMSTaskSequence. TSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSNextInstructionPointer=28TSManager16/08/2019 19:32:211812 (0x0714)
Set a TS execution environment variable _SMSTSNextInstructionPointer=28TSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSInstructionStackString=22 24TSManager16/08/2019 19:32:211812 (0x0714)
Set a TS execution environment variable _SMSTSInstructionStackString=22 24TSManager16/08/2019 19:32:211812 (0x0714)
Save the current environment blockTSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSLastActionRetryCount=0TSManager16/08/2019 19:32:211812 (0x0714)
Start executing an instruction. Instruction name: Copy scripts. Instruction pointer: 28TSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSCurrentActionName=Copy scriptsTSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSNextInstructionPointer=28TSManager16/08/2019 19:32:211812 (0x0714)
Set a local default variable RunAsUserTSManager16/08/2019 19:32:211812 (0x0714)
Set a local default variable SMSTSRunCommandLineUserNameTSManager16/08/2019 19:32:211812 (0x0714)
Set a local default variable SMSTSRunCommandLineUserPasswordTSManager16/08/2019 19:32:211812 (0x0714)
Set a local default variable LoadProfileTSManager16/08/2019 19:32:211812 (0x0714)
Set a global environment variable _SMSTSLogPath=X:\windows\TEMP\SMSTSLogTSManager16/08/2019 19:32:211812 (0x0714)
Expand a string: cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf"TSManager16/08/2019 19:32:211812 (0x0714)
Expand a string: TSManager16/08/2019 19:32:211812 (0x0714)
Start executing the command line: cscript.exe "%SCRIPTROOT%\LTICopyScripts.wsf"TSManager16/08/2019 19:32:211812 (0x0714)

 

↧
Viewing all 11297 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>