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

Upgrade path from MDT2013 Update2 to MDT build 8450

$
0
0

The release notes state that build 8450 supports upgrading a Deployment Share from version 8443.    Should I upgrade to MDT 8443 first before upgrading to build 8450?   I don't want to mangle my deployment share leading me to recreate TSes, and all the nightmare that entails...


MDT using UEFI generates a Failure:5615

$
0
0

Hi All,
            I'm using MDT 8450, ADK 1809, on a Windows Server 2016 and I'm getting a Failure (5615): False: Boot Drive was not found... Failed to run the action: Install Operating System.

1. This is a new Dell OptiPlex 7060 and I've tested on three of the same model
2. Using the latest WinPE10 Drivers
3. UEFI partition is set to GPT, not MBR.
4. BIOS is set to boot w/UEFI, Legacy Options ROM turned on, SecureBoot Turned Off, NIC Stack w/PXE Support enabled, AHCI instead of RAID
5.  Same image of Windows 10 Ent. build 1803 works on OptiPlex 7050 and older as well as Latitude 5480 and older booting into Legacy BIOS.
6. Operating System installs to 100% and promptly generates the error.  Immediately I run DiskPart and under drive 0 I see the following...

Volume 0, Letter D, Type DVD-ROM
Volume 1, Letter E, Label Windows, 460GB, NTFS, Partition
Volume 2, Letter F, Label Recovery, 5392MB, NTFS, Partition

For some reason I can't understand, it cannot grab drive letter C.  It appears to format successfully using UEFI and creating the necessary partitions.  According to the LTIApply log, it applies the .WIM file successfully but is unable to find the boot drive.  From the LiteTouch.log, my OS drive is E:\  thus my error.  I'm at a loss at this point as to why this is occurring.  Is something within the Dell BIOS disallowing C:\ to be used?

Problem with logs and SQL-based settings

$
0
0

Hi,

I'm trying to set up a pretty basic configuration for a MDT deployment. The main goal is to have the computer name taken from the SQL database, so that the names are reused instead of half-randomized.

Here's my configuration.ini

[Settings]
Priority=CSettings, ByLaptop, ByDesktop, Default
Properties=ComputerType, MyCustomProperty

[ByLaptop]
SubSection=Laptop-%IsLaptop%
ComputerType=NTB

[ByDesktop]
SubSection=Desktop-%IsDesktop%
ComputerType=DST

[Default]
;Set computer name
OSDComputerName=%ComputerType%-#left(replace("%Make%"," ",""),4)#-#left(replace("%SerialNumber%","-",""),6)#

OSInstall=Y
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
BDEInstallSuppress=NO
BDEWaitForEncryption=False
BDEDriveLetter=S:
BDEDriveSize=2000
BDEInstall=TPM
BDERecoveryKey=AD
BDEKeyLocation=
SkipCapture=YES
SkipComputerName=NO
SkipComputerBackup=YES
SkipDeploymentType=YES
DeploymentType=NEWCOMPUTER
SkipDomainMembership=YES
JoinDomain=ARP.LOCAL
DomainAdmin=administrator
DomainAdminDomain=ARP.LOCAL
SkipFinalSummary=YES
SkipLocaleSelection=YES
KeyboardLocale=pl-PL
UserLocale=pl-PL
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=NO
SkipTaskSequence=NO
;TaskSequenceID=WIN10ENT-001
SkipTimeZone=YES
TimeZoneName=Central European Standard Time
SkipUserData=YES
MachineObjectOU=OU=CLT,OU=Comps,OU=ARP,DC=arp,DC=local
EventService=http://SRV-SVC-P01.arp.local:9800
FinishAction=REBOOT
SLShare=\\srv-svc-p01.arp.local\DeploymentLogs$
;SLShareDynamicLogging=\\srv-svc-p01.arp.local\DeploymentLogs$\%OSDComputername%

[CSettings]
SQLServer=srv-sql-p05.arp.local
Instance=instance01
Database=MDT
Netlib=DBNMPNTW
SQLShare=\\srv-svc-p01.arp.local\SQLLogs$
Table=ComputerSettings
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR


I feel like I can share the internal DNS names without risk, so nothing in the file above has been modified. All the shares are accessible (i.e. I can type in the shares from another computer into Explorer and have the relevant folder come up). I've also set up all the log-based shares so that "Everyone" has write permissions.

However, two things are happening:

1) despite setting up the SLShare, no files are ever created in the folder

2) despite setting up and configuring the SQL connection, the WindowsPE gets slightly "stuck" on the CSettings stage and the computer name isn't downloaded from the SQL. Since I have no logs, I cannot say if there's a connection issue or if this is a configuration issue. Named Pipes are turned on and the MDT console has no problems working on the SQL database.

Finally - yes, I've commented out the SLShareDynamicLogging - I first want to get the basic logs working before I go for the more detailed.

Could someone point me in the right direction please?


modified unattend.xml file for sysprep

$
0
0

Hi There,

We have modified unattend.xml file which we want to use when running sysprep in MDT. How can we place the unattend.xml file and what is the location, so that MDT automatically picks it and apply sysprep?

Any help would be much appreciated!

Thanks,

Sourav


Born to Learn

Specify which deployment share to use

$
0
0

Hi,

 

I am hoping that someone can help with my MDT multisite issue?

 

Error: "Specify which Deployment Share to use."

 

 I have set up MDT Multisite with one central server with MDT installed and DFS R replicating Deployment Share to 2 severs with WDS configured.

 

MDT installed on central server in Data Centre

DFS - R replicating Deployment Share to WDS servers in Milan and Prague.

Milan works fine, but when deploying to Prague, Deployment Wizard asks to "Specify which Deployment Share to use." When I manually enter the path to the DS it works fine.

 

I am using Default Gateway property to specify path to Deployment Share.

 

Bootstrap.ini:

 

[Settings]

Priority=DefaultGateway, Default

 

[DefaultGateway]

xx.xx.0.1=Milan

xx.xx.0.1=Prague

 

[Milan]

DeployRoot=\\IT-SRVV-WDS\DeploymentShare$

 

[Prague]

DeployRoot=\\CZ-WDS-02\DeploymentShare$

 

 

[Default]

SkipBDDWelcome=YES

 

 

Any advise would be much appreciated.

Windows 10 1709 MDT Error

$
0
0

I am currently trying to roll out Windows 10 Enterprise 1709 to my school district.

We am running MDT 8443, along with ADK version 1709.  Previously, I was able to import the 1703 and 1607 versions of Windows 10 into MDT without an issue.  However, I am unable to import 1709 into MDT successfully. Whenever I try to use the "import operating system" option within Deployment Workbench and specify the location of the OS files, I receive the following error:

Performing the operation "import" on target "Operating system".
Unable to get information for WIM file F:\SW_DVD5_Win_Pro_Ent_Edu_N_10_1709_64BIT_English_MLF_X21-50143\Sources\Install.wim.
System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The data is invalid
   --- End of inner exception stack trace ---
   at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
   at Microsoft.BDD.PSSnapIn.ImportOperatingSystem.Import(String sourcePath, String directoryName, Boolean moveDirectory)
Import processing finished.

I have always downloaded the Windows 10 ISO from VLSC, extracted the contents of the ISO, and imported those into MDT. However this isn't working for version 1709.  I am unsure if there is something I am missing here.  I have been researching for weeks without luck, so any suggestions would be greatly appreciated.

Application Deployment Failing Multiple Error Code 1618.. MDT 2013

$
0
0
Hi Team,

I am using MDT 2013 to deploy the Windows 8.1 OS and some applications POST OSD through Install Applications ( Multiple Applications) MDT TS step. OSD is fine but after OSD I am getting errors relared to Applications deployment  ( that is located in Mutiple Install Applications Steps). i have already checked that their Installations switches are fine. error is not related about particular Applications, some times particular application are deployed without error , and some times same application not deployed and got error in deployment Summary. i am trying to deploy  Junos Pulse,Intel Hokey, Intel Wireless Pro,MABM client through Install Multiple Applications Task Sequence Steps.

can you please guide me how can we do this without any error, i am getting any error about application deployment...Error Screenshot

Task sequence execution failed with error code 80004005

$
0
0

Hi Flokes,

strange issue here, we have been using OSD for several months,but am getting error while deploying the OS

attached the SMSTS.log below.

any help would be appreciated.

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="instruction.cxx:3010">
<![LOG[Failed to run the action: Install Operating System.
Access is denied. (Error: 00000005; Source: Windows)]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="3" thread="1480" file="instruction.cxx:3101">
<![LOG[Sending status message . . .]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="utility.cxx:302">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=5]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="21:26:39.197+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="executionenv.cxx:807">
<![LOG[Let the parent group (Install) decides whether to continue execution]LOG]!><time="21:26:39.244+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="instruction.cxx:3210">
<![LOG[The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="21:26:39.244+000" date="08-03-2012" component="TSManager" context="" type="3" thread="1480" file="instruction.cxx:2424">
<![LOG[Failed to run the last action: Install Operating System. Execution of task sequence failed.
Access is denied. (Error: 00000005; Source: Windows)]LOG]!><time="21:26:39.244+000" date="08-03-2012" component="TSManager" context="" type="3" thread="1480" file="engine.cxx:214">
<![LOG[Sending status message . . .]LOG]!><time="21:26:39.244+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="utility.cxx:292">
<![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="21:26:39.244+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="utility.cxx:302">
<![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)]LOG]!><time="21:26:39.259+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="tsmanager.cpp:767">
<![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="21:26:39.259+000" date="08-03-2012" component="TSManager" context="" type="3" thread="1480" file="tsmanager.cpp:767">
<![LOG[****************************************************************************]LOG]!><time="21:26:39.259+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tsmanager.cpp:789">
<![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="21:26:39.259+000" date="08-03-2012" component="TSManager" context="" type="3" thread="1480" file="tsmanager.cpp:790">
<![LOG[Cleaning Up. Removing Authenticator]LOG]!><time="21:26:39.259+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tsmanager.cpp:578">
<![LOG[Cleaning up task sequence folder]LOG]!><time="21:26:39.259+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="utils.cpp:1404">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="resolvesource.cpp:508">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="resolvesource.cpp:508">
<![LOG[DeleteFileW(sVolumeIDFile.c_str()), HRESULT=80070002 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,508)]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="resolvesource.cpp:508">
<![LOG[Successfully unregistered Task Sequencing Environment COM Interface.]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="environmentlib.cpp:869">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="commandline.cpp:229">
<![LOG[Set command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="commandline.cpp:707">
<![LOG[Executing command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="21:26:39.415+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="commandline.cpp:805">
<![LOG[==========[ TsProgressUI started in process 296 ]==========]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TsProgressUI" context="" type="1" thread="1520" file="winmain.cpp:327">
<![LOG[Command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TsProgressUI" context="" type="0" thread="1520" file="winmain.cpp:330">
<![LOG[Unregistering COM classes]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TsProgressUI" context="" type="1" thread="1520" file="winmain.cpp:202">
<![LOG[Unregistering class objects]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TsProgressUI" context="" type="1" thread="1520" file="winmain.cpp:503">
<![LOG[Shutdown complete.]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TsProgressUI" context="" type="1" thread="1520" file="winmain.cpp:520">
<![LOG[Process completed with exit code 0]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="commandline.cpp:1102">
<![LOG[Successfully unregistered TS Progress UI.]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="utils.cpp:1963">
<![LOG[g_TSManager.Run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,657)]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="tsmanager.cpp:657">
<![LOG[Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="3" thread="1480" file="tsmanager.cpp:689">
<![LOG[Sending error status message]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tsmanager.cpp:690">
<![LOG[In non SMS staqndalone mode.Ignoring SendStatusMessage request]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tsmanager.cpp:1541">
<![LOG[Finalizing logging from process 1440]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tslogging.cpp:1736">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="21:26:39.447+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tslogging.cpp:1578">
<![LOG[Successfully finalized logs to E:\SMSTSLog]LOG]!><time="21:26:39.525+000" date="08-03-2012" component="TSManager" context="" type="1" thread="1480" file="tslogging.cpp:1635">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="21:26:39.525+000" date="08-03-2012" component="TSManager" context="" type="0" thread="1480" file="tslogging.cpp:578">



Driver Size in C:\Windows\System32\DriverStore\FileRepository

$
0
0

This folder is 32gb with what looks like a LOT of duplicate files... why is this here and how to I reduce it to just what I need?

Thanks,

nacg



can MDT preserve user profile information from an existing Win7 machine before it installs Win10?

$
0
0

Can MDT be used to upgrade computers from Win7 to Win10 while preserving the user's profile and any OS/Application history that is kept in C:\Users\Profile, or the registry?  In other words, can it 

1. take a snapshot of the user's profile/history/etc from the current Win7 machine

2. install a custom build of Windows 10 (that we create initially with our software/drivers/configs) - NOTE: I dont want to upgrade the Win7 machine. I want a fresh, clean copy of Win10.

3. restore the user's profile/history/etc so that it appears it was an upgrade (but it wasn't).

We use a combination of Ghost and Altiris to do this today and it doesnt work well.

Thanks!

Litetouch loads and then PC's reboot

$
0
0

Hi,

Suddenly our MDT 8450 server + MDT setup is not deploying our images. Basically we boot to pxe, it loads the litetouch wim to 100%, we see our litetouch background and can move cursor around and then the PC reboots. So I don't even get to pick a task to deploy. We have been building these Dell 3010/390's for ages without issue, it's rather odd.

Below are the litetouch logs from the last test deployment, don't appear to get an error but it does seem to stop abruptly.

LOG[Microsoft Deployment Toolkit version: 6.3.8450.1000]LOG]!><time="17:34:05.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="17:34:05.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-FMH62OQ\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-FMH62OQ\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="17:34:05.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-FMH62OQ\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-FMH62OQ\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-FMH62OQ\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-FMH62OQ\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-FMH62OQ\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"    \\MININT-FMH62OQ\root\cimv2:Win32_LogicalDisk.DeviceID="E:"]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-FMH62OQ\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives =  C: D: E:]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="17:34:06.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to get Current ID.]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE or WinRE.]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z:  = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = PREINSTALL]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = Z:]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = Z:]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Existing UNC Path Z: = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Successfully established connection using supplied credentials.]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentType = NEWCOMPUTER]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceRoot = \\BEX01\MDT2013Build$]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property ResourceDrive is now = Z:]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = Z:]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[SMS Task Sequencer already found on X:\Deploy\Tools\X64]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying \\BEX01\MDT2013Build$\Control\\TS.XML to X:\Deploy\Tools\X64]LOG]!><time="17:34:10.000+000" date="11-06-2018" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Any thoughts would be great!

Thanks a lot

deploying office 2019

$
0
0

Hi,

How Can I deploy office 2019 Pro  using  mdt since it is boot strapper only 

Thanks 

MDT USMT and others

$
0
0

So I need help setting up USMT.  I have looked everywhere and read dozens of articles, but none are working.  I cannot seem to get the data to be saved and carried over at all (trying to get machines from Win 7 to Win 10).

Another thing is I am also stuck with something stupid, after the OS install, it signs in automatically as admin (which I have disabled from unattended and it ignores me like wtf) and it doesnt join to the domain like I have it setup for some reason either.

AND to make things even worse, if I try to switch user, I cant, because since I am not on the domain I cannot sign in as anyone so if I did this to a user machine i would have to make extra steps.  

I have followed everything I could to the T to make it automated so that all I have to do is pxe boot a machine (which I have about +350 to do within the next few months, go me) and just let it run.

Is there anyone that can help walk me through as to what is wrong with each of these steps please?

Trying to grant permissions on a folder during TS.

$
0
0

I have a basic batch file to copy over a folder to C:\.

Then an exe within that folder is run and an INI file gets copied to another location.

That all works fine, but I'm trying to grant permissions to that folder as well.

I was given a batch file that someone runs manually from the desktop and it appears to work fine. When I run it through
MDT, everything gets done but the permissions. Here's a snippet of the batch file:

robocopy \mdtserver\share\TN3270Plus C:\TN3270Plus /e /k /I /y /r
cd C:\TN3270Plus
START C:\TN3270Plus\TN3270Setup.exe /s /v"/qn ALLUSERS=1"
icacls "C:\Program Files (x86)\SDI" /grant "Authenticated Users":(OI)(CI)F /t

The icacls is what I need. If I make just an online-line batch file on the desktop and run it, it adds authenticated users with
full control to the folder. It does not fail, but does not apply that user within the batch when MDT runs it.
I've added "runas /user:administrator" to the batch and also net use* with my elevated account.
Just not finding what I need for this to happen, if anyone knows.....


Query BIOS Version Before Running Command or Installing Application?

$
0
0

I have a task sequence that queries the computer model and then runs a BIOS update if the model matches.

If the BIOS is already up to date, the BIOS update application doesn't update the BIOS and the deployment continues. Everything is OK, but then we get a yellow summery screen at the end saying the BIOS update task had an error code.

Is there a way to filter the BIOS update task so that it only runs when the model matches AND the BIOS version is below a certain value?



MDT unable to capture image for Windows 10 Pro ver 1803

$
0
0

We are having an issue when using MST to capture an image.

expected image state is image_state_generalize_reseal_to_oobe actual image state is image_state_complete, sysprep did not succeed

Failure 6192 : Error ...........

Help with MDT and WDS with multi company and OS deployment.

$
0
0

Hello,

I work for a company that is the parent company of many small to mid size businesses.  One of the tasks I own is the imaging process.  I've recently setup 4 WDS servers for PXE boot at our 4 largest geographic locations with DFS-R.  I'm using the MDT to build the reference image the contains only apps that all of our businesses need.  From there I have a deployment share and task sequences for each company.  Most of our companies are on Windows 10 Pro, except for one.  Two of my locations are easy, I have the default gateway set in the MDT database and it knows what OS (reference image) and apps to load.  I have two locations that use different hardware models and OSs.  For those I have the model set in the MDT database to automatically install the proper OS and apps for the one type of hardware.

The problem I'm trying to solve is how to automate the process for all other hardware types at these two locations.  I can't go by default gateway because I need it to be model independent at these locations.  I also cannot use model because the other companies use the same models with their individual task sequences.  I tried to setup location and model but ended up with a hybrid of both task sequences combined.

Is there a way to say X location and Y model gets Z image, all others at location X use the company specific image?

Any help would be greatly appreciated as this is my first time working with the MDT.  I've ready many really good posts and a book from Johan Arwidmark and done a good deal of Googling but those have been my only info sources thus far as I implement this.

And before anyone suggests it, SCCM is not in my near future ;)

Thanks,

Adam

MDT Failure (5210): ValidateDeployRootWithRecovery: Cancel

$
0
0

Hello,

We are deploying Windows 7 Professional images and are using Windows Server 2003 R2 using MDT.  We have one deployment share but that is giving us some problems when we upload new images.  So we decided to just start from scratch and create a new deployment share.  While testing the new one out, we get the following error at the end of the deployment: MDT Failure (5210): ValidateDeployRootWithRecovery: Cancel.

The old deployment share deploys images without this message.  The new share is located in the same location with the same permissions so I know it is not a permissions error.  I have also copied over the same WIM files that were working in the old share to the new, and copied the TS.xml files over too to assure the task sequence is the same.  That had failed too.  I believe it is some setting when I created the new deployment share.  I have checked the bootstrap.ini file and the Network (UNC) path in the properties of the deployment, and both point to the correct location.  I can't think of anything else.  Does anyone have any insight on this?

Ohh.  Here is some lines from the BDD.log from a deployed image from C:\Windows\Temp\DeploymentLogs.  If I didnt post enough, I can add more.  It's fairly long.

<![LOG[FAILURE ( 5210 ): ValidateDeployRootWithRecovery: Cancel]LOG]!><time="09:13:26.000+000" date="02-12-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"><![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 1544)]LOG]!><time="11:42:00.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 1544)]LOG]!><time="11:47:00.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 15 minutes (process ID 1544)]LOG]!><time="11:52:00.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = 0]LOG]!><time="11:52:30.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Setup completed successfully.]LOG]!><time="11:52:30.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[LTIApply processing completed successfully.]LOG]!><time="11:52:30.000+000" date="02-22-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Microsoft Deployment Toolkit version: 6.0.2223.0]LOG]!><time="11:52:31.000+000" date="02-22-2013" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase"><![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="11:52:31.000+000" date="02-22-2013" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">

MDT/OSD Deployment Page Not showing up corrrectly -MDT 2013 Update2

$
0
0

About 95% of the time, the final MDT/OSD Deployment Complete page is only showing up after logging in as an admin.

It usually shows up after last reboot. Here is the complete error:

The task sequence execution engine failed executing the action (Scan Installed Apps) in the group (OSD Results and Branding) with the error code 1
Action output: [ smsswd.exe ]
PackageID = ''
BaseVar = '', ContinueOnError=''
ProgramName = 'cmd /c "cscript //nologo C:\WINDOWS\UDI\OSD_InstalledAppsLookUp.vbs > C:\WINDOWS\UDI\OSD_InstalledAppsLookUp.log"'
SwdAction = '0001'
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Process completed with exit code 1
Command line returned 1. The operating system reported error 1: Incorrect function. 

_____________________________________________________________

Second error:

The task sequence execution engine failed executing the action (Parse Base Variable) in the group (OSD Results and Branding) with the error code 200
Action output: [ smsswd.exe ]
PackageID = ''
BaseVar = '', ContinueOnError=''
ProgramName = 'cscript.exe //nologo "C:\_SMSTaskSequence\WDPackage\Scripts\OSD_BaseVariables.vbs"'
SwdAction = '0001'
Command line for extension .exe is "%1" %*
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Process completed with exit code 200
--------------------------------
Initializing Objects
--------------------------------

--------------------------------
Extracting TS Base Variable
--------------------------------

Reading OSD variable: [_SMSTSTaskSequence]
Loading XML from variable string content...
Using XPATH to query for [BaseVariableName]
Failed to read XPATH query value, or value is empty.
--------------------------------
 Exiting with [200]
--------------------------------
Command line returned 200. The operating system reported error 200: The code segment cannot be greater than or equal to 64K. 

The only thing I see out there is this: http://www.myitforum.com/forums/MDT-2012-UDI-OSD-Results-Window-Installed-Applications-Unknown-m235557.aspx

But there has to be a better way to make sure this works correctly all of the time.

Using SCCM 2012 R2 SP2 CU2

Thanks.

Formatting only C drive using format and partition disk task sequence

$
0
0

I have a machine with two drive C and D with windows XP and planning to install windows 7 in C: drive.

I dont want to format the holde hard disk, only C: drive and install OS.

Please let me know how it can be done.


Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>