How can I deploy Windows 10 Enterprise x64 with MDT 2013 Update 1 integrated with System Center 2012 R2 SP1 Configuration Manager ?

[ZeZe]

I had a few issues last year while testing a new image on my lab. The deployment was always installing the OS on the drive E or D and adding the OSDPreserveDriveLetter to false actually did only help once. I captured and sysprep the image with OSDPreserveDriveLetter and then the image was always good, no issues. In the task sequence where I deploy this new image I didn't add the OSDPreserveDriveLetter!

[anyweb]

A little help please!

 

I'm running SCCM2012 R2 SP1 CU2 with intergraded MDT 2013 Update 2. Following the instruction in this thread but having issues with distribute MDT toolkit package. Below is distmgr.log

 

Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 4964 (0x1364)

STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=OPS-TITANX1.staff.copa SITE=CPA PID=1408 TID=9140 GMTDATE=Thu Jan 21 21:52:37.161 2016 ISTR0="CPA0016A" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CPA0016A" SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Retrying package CPA0016A SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Start adding package CPA0016A... SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

The Package Action is 2, the Update Mask is 268435456 and UpdateMaskEx is 0. SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

CDistributionSrcSQL::UpdateAvailableVersion PackageID=CPA0016A, Version=1, Status=2300 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Taking package snapshot for package CPA0016A from source \\ops-titanx1\f$\MDT2013u2 Toolkit SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

MoveFileW failed for E:\SCCMContentLib\FileLib\E074\E0745DEE29B578FA35225A60938C5D591073FF1B806F61D3C3D652EDA1F81FCE.INI to F:\SCCMContentLib\FileLib\E074\E0745DEE29B578FA35225A60938C5D591073FF1B806F61D3C3D652EDA1F81FCE.INI SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

CFileLibrary::AddFile failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

CFileLibrary::AddFile failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

CContentDefinition::AddFile failed; 0x80070002 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Failed to add the file. Please check if this file exists. Error 0x80070002 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

SnapshotPackage() failed. Error = 0x80070002 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=OPS-TITANX1.staff.copa SITE=CPA PID=1408 TID=9140 GMTDATE=Thu Jan 21 21:52:37.206 2016 ISTR0="\\ops-titanx1\f$\MDT2013u2 Toolkit" ISTR1="Microsoft MDT Toolkit Package" ISTR2="CPA0016A" ISTR3="30" ISTR4="95" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CPA0016A" SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Failed to take snapshot of package CPA0016A SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

CDistributionSrcSQL::UpdateAvailableVersion PackageID=CPA0016A, Version=1, Status=2302 SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=OPS-TITANX1.staff.copa SITE=CPA PID=1408 TID=9140 GMTDATE=Thu Jan 21 21:52:37.218 2016 ISTR0="Microsoft MDT Toolkit Package" ISTR1="CPA0016A" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CPA0016A" SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Failed to process package CPA0016A after 5 retries, will retry 95 more times SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Exiting package processing thread for package CPA0016A. SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:37 PM 9140 (0x23B4)

Currently using 0 out of 5 allowed package processing threads. SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:42 PM 4964 (0x1364)

The last source update time for pkg CPA000B2 is 1/20/2016 4:12:39 PM Pacific Standard Time SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:42 PM 4964 (0x1364)

The next start time for pkg CPA000B2 is 1/21/2016 4:12:00 PM Pacific Standard Time SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:42 PM 4964 (0x1364)

Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 1/21/2016 1:52:42 PM 4964 (0x1364)

 

Troubleshooting steps including

 

1. delete MDT Toolkit package > Create new MDT Toolkit package using "Create MDT Task Sequence" ---- same error

2. delete MDT Toolkit package and source folder > create new folder > copy source files from "C:\Program Files\Microsoft Deployment Toolkit\Templates\Distribution" to newly create folder > Create new package with Data Source point to new folder. ----- same error

3. delete MDT Toolkit package and source folder > create new folder and copy source as above steps > reset NTFS file permission to everyone full permission ----- same error.

4. reinstall Windows 10 ADK ---- same error

5. uninstall MDT2013 update 2 > install MDT 2013 update 1 --- same error

6. update SCCM2012 R2 SP1 with CU2 ---- and go through above steps....same error

 

:unsure: !

 

Help Please

Thanks!

 

 

 

are you only having this issue with one package on one dp or not, please elaborate,

[tnoob2]

Thanks anyweb

 

I have two DPs, both having same error distribute MDT2013 Toolkit package (only). There's no distribution issue with current or new package. In fact, MDT2013 Settings package distributed with no problem.

 

Here's the message from Content Status monitoring

 

"Description: Distribution Manager failed to access source directory \\ops-titanx1\f$\MDT2013u2 Toolkit for content "Microsoft MDT Toolkit Package" (content ID=CPA0016A).

 

Possible cause: Distribution Manager does not have sufficient rights to the source directory.

Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.

 

Possible cause: There is not enough disk space available on the site server.

Solution: Verify that there is enough free disk space available on the site server.

 

Retry Interval is 30 minutes, number of retries left is 0."

 

Thanks for your help!

[anyweb]

can it access

\\ops-titanx1\f$\MDT2013u2 Toolkit

and could any AV software be blocking it ? what about that space ?

[tnoob2]

Hi anyweb,

 

1. everyone have Read/Write/Execute permission to the folder

2. I uninstalled SAV, Disabled all firewall (for testing)

 

Just did another test with no space on file name...still have the same error :-(

 

Thanks,

T.

[anyweb]

forget about 'everyone', can the ConfigMgr server computer account access \\ops-titanx1\f$\MDT2013u2 Toolkit ?

[tpe@kmc.dk]

First of all thangs for a great guide, everything works like a charm

 

I have one question though, one i have googled a lot, but i can't seem to find a solution to it..

 

The Win10 source i use is MVLS "Windows 10 ENT DK" (including danishlanguage), but when i'm done deploying windows, it starts up using en-US for keyboard and so on (despite windows being in danish) i have read about localization of the image trough either CustomSettings.ini or Unattend.xml but it seems like it completely ignores the settings (if i edit the MDT task sequence trough the sccm configuration manager, i'm able to set the local timezone, but non of the articles i've found seems to have any effect what so ever...

 

Any ideas ?

[tpe@kmc.dk]

Well i changed my search approch and found this article that helped me out https://social.technet.microsoft.com/Forums/en-US/da3dd760-1ece-4163-a791-38d087b2e63e/mdt-2012-time-and-currency-setting-inputlocale-is-not-working-in-udi-wizard-selection?forum=mdt

 

Found the following:

 

CustomSettings.ini had to have the following added:

UserLocale=da

UILanguage=da

KeyboardLocale=0406:00000406

unattend.xml needed "<component name="Microsoft-Windows-International-Core" 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">" changed to:

<component name="Microsoft-Windows-International-Core" 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">

<InputLocale>%KeyboardLocale%</InputLocale>

<SystemLocale>%InputLocale%</SystemLocale>

<UILanguage>%UILanguage%</UILanguage>

<UserLocale>%InputLocale%</UserLocale>

</component>

 

And last:

In the MDT Toolkit package you need to find the file named UDIwizard.wsf (\Toolkit\Scripts)

Then comment out the following line:

oEnvironment.Item("UserLocale") = oEnvironment.Item("InputLocale")

Update the distribution points with the new mdt settings and mdt toolkit and i works

Edited February 5, 2016 by tpe@kmc.dk

[selimatmaca]

In this article, you didn't create a reference image or you didn't capture image. You directly used DVD resource for deployment.

 

In this video, (at 4min), they are saying we have to create a reference image for windows 10 deployment.

 

Q1: Are they wrong or an update brought this feature and we don't need a reference image anymore?

Q2: Does "Using DVD resource" bring any limitation?

[anyweb]

 

Q1: Are they wrong or an update brought this feature and we don't need a reference image anymore?

Q2: Does "Using DVD resource" bring any limitation?

 

Q1. No they are not wrong, you can capture the Windows 10 image using the method they suggest or you can use the install.wim directly from the DVD if you don't want to bundle anything with the image (such as including Microsoft Office 2016 or cumulative software updates or whatever you want). I am showing you one way of deploying Windows 10, there are many, you choose what works in your environment. Or you can capture the reference image using other methods such as Build and Capture with ConfigMgr.

Q2. There are no limitations that cannot be dealt with via extra steps in the task sequence (such as applying modifications or updates or whatever)