WIndows Enterprise 8.1 - MDT 2013

Hi All
I'm using MDT2013 and ADK 8.1.
I am trying to create a new Windows 8.1 ent build and am having a few strange issues...
I have created a standard TS for the initial build, when I deploy the TS everything works as expected except the build doesn't seem to have all the Modern UI apps installed. At first I assumed this may be a slight change MS made and the builtin
administrator account just doesn't have them installed anymore.. But when I create a new local user account and log in I still don't have any of the apps installed. All that is present on the start screen is IE - Store - File explorer - Skydrive
and desktop, things like weather, news, sport and so on don't seem to be installed in the default user profile..
I manually built a machine from the media and the apps do seem to be installed. I know during the default install the default admin account gets disabled and a new account is created. This account does have all the apps installed, so on here
when you add a new user these apps are present..
Am I missing something here (hopefully something simple :-))? is there something specific I need to add to my unattend.xml file to allow the apps to be installed? do I need to create a new user account during the build to allow the apps to install?
I followed the same process when I created a windows 8.0 build and didn't have any of these issues.
Thanks for any advice.. Simon

I have had the same issues. We are just migrating a school to full windows enterprise 8.1 -- God Help us.
The first issues we had were related to USMT5 not beiong available. Disabling these steps from the task sequence rectified it and the build to 8.1 is now very quick. However there are no APPS such as News and many more - they're simply not present on the
machine.
We have 150 machines to automatically set running on Friday night 20th 12 -2013 .... the expectation is we can complete the whole build on Monday and Tuesday and be able to eat a Turkey the following day. I'm worried this isn't going to be the case and I'm
expecting Turkey sandwiches.
Enough laughter:
New build of MDT 2013 complete with all the latest ADKs associated with it including VAMT 3.1 (SQL) becasue that's the only quick way to licence them. (keys not compatable with older versions or even when wrapped into MDT TS).
Using a USB drive to deploy the same media results in a good install. Auto build using MDT gives you just 5 Apps.
1. IE
2. Store
3. File Explorer
4. SkyDrive
5. Desktop
That's it -- no good to me or many others on here by the looks. It would appear from reading JECOMPUTER4MEs last post that he may be onto something with the administrator accounts, however this surely can't be regarded as a good fix and it's certainly
not something my timescales allow for. In all honesty it would be quicker using USB media and then manually carrying out a domainjoin.
A few of the apps are available to pin to the start. Which is fine as we can sort this using GPO, these apps are things like Travel and Photos. However there are still a plethera of standard apps missing such as news, weather, calendar and finance to mention
a few.
Watch this space, I'm having to work for a fix as soon as possible and hope someone can post some helpful pointers into this forum soon.
Thanks
Matt

Similar Messages

Migrate from Windows XP x86 to Windows 7 x64 using MDT 2013

Hello everybody,
We are migrating our Windows XP(x86) workstations to Windows 7 (x64). We are aware of the necessary gymastics tu perform on USMT in a way to run the scanstate with an older version of USMT in Windows XP, and then run the LoadState in Windows 7 environnement
with the newest one.
The problem is that I cannot run MDT TaskSequences (referring to a X64 windows 7 Image) in Windows XP (full OS environnement). Can anyone please tell me if there is a way to get arround this ? is there any method to execute this migration ?
Thank you in advance.

Hello,
You can use usmt with mdt. It's necessary to modify the script mdt
http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx
http://www.deploiementwindows.com/migration-windows-xp-vers-windows-8-1-avec-mdt-2013/
Thank you Nicoals for your replay, but my problem is to run MDT task Sequence (including Windows 7 x64) on Windows XP.

Is it possible to apply a GPOPACK to Windows 8.1 in MDT 2013/ADK for 8.1

We are aware that SCM does not have a basline for Windows 8.1. I have seen Johan post about adding the code to the ZTIApplyGPOPack.wsf for support for Windows 8.1. Also do we need to update GPOPack.wsf located in \Templates\GPOPacks\Name of GPO
PACK.
So what is the best approach for creating and applying a GPO PACK to Win 8.1?
Thanks

If I remember correctly what I did, this is how I went about it.
1. Create the Windows 8.1 GPO Pack using LocalGPO from SCM 3.0
To use LocalGPO you have to edit "LocalGPO.wsf" to add support for 8.1.
In "Sub ChkOSVersion" just add the lines to provide support for 8.1 (and 2012 R2 while you're there)
To do this, just copy the 4 lines for 8 and 2012, paste them above the lines you just copied, and then edit them
It should look like this after the edit:
If(Left(strOpVer,3) = "6.3") and (strProductType <> "1") then
strOS = "WS12R2"
ElseIf(Left(strOpVer,3) = "6.3") and (strProductType = "1") then
strOS = "Win81"
ElseIf(Left(strOpVer,3) = "6.2") and (strProductType <> "1") then
strOS = "WS12"
ElseIf(Left(strOpVer,3) = "6.2") and (strProductType = "1") then
strOS = "Win8"
Since you are only exporting, this should be the only change that is needed. If you were doing other functions, you would need to edit those.
2. Edit "GPOPack.wsf" in your newly created GPO Pack to provide support for 8.1 (and optionally 2012 R2) in the same way you did above.
3. Copy your GPO Pack to your deployment share
4. Edit "ZTIApplyGPOPack.wsf" to provide support for 8.1 (and optionally 2012 R2) using the same copy, paste, and edit technique that was used above. The section should look similar to below:
If (Left(sOSVersion,3) = "6.3") and oEnvironment.Item("IsServerOS") then
sOS = "WS2012R2"
oLogging.CreateEntry "Using Default Windows Server 2012 R2 GPO Pack", LogTypeInfo
ElseIf (Left(sOSVersion,3) = "6.3") and Not(oEnvironment.Item("IsServerOS")) then
sOS = "Win81"
oLogging.CreateEntry "Using Default Windows 8.1 GPO Pack", LogTypeInfo
ElseIf (Left(sOSVersion,3) = "6.2") and oEnvironment.Item("IsServerOS") then
sOS = "WS2012"
oLogging.CreateEntry "Using Default Windows Server 2012 GPO Pack", LogTypeInfo
ElseIf (Left(sOSVersion,3) = "6.2") and Not(oEnvironment.Item("IsServerOS")) then
sOS = "Win8"
oLogging.CreateEntry "Using Default Windows 8 GPO Pack", LogTypeInfo
5. If you use the standard naming convention for your GPO Pack, you are done. In other words, if you name your GPO Pack "Win81-MDTGPOPack", then you don't have to worry about adding anything to your customsettings.ini. It will automatically know
to use this one for your Windows 8.1 Task Sequences.
It would be nice if Microsoft fixed all this in the next update of MDT2013 and SCM.
Hope this helps

Error While Using MDT 2013 to Refresh Windows XP to Windows 8.1 during Computer backup to network

Hi,
I am getting below error in Deployment Summary while Computer backup to network during Refresh from XP to 8.1 through MDT 2013.
1. I followed URL-
http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx to use USMT for the UserProfile through MDT 2013.
2. For User profile I am using Hardlink USMT through MDT Wizard, that is working fine.
3. My Deployment Share rule is below..
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\MDT2013\share$
BackupDir=%OSDComputerName%
BackupFile=%OSDComputerName%.wim
BackupDrive=ALL
4. ZTIBAckup Logs below..
2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context=""
type="1" thread="" file="ZTIBackup">
<![LOG[OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Search for Drive: OriginalPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Found Drive: C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDisk is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Checking to see if we can store the backup locally]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive C: 3231300]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive D: 272600]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive X: 2489]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store path = C:\StateStore]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Total used space: 3506389]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Available space at C:\StateStore: 22368244]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Backup can use local path]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property USMTLocal is now = True]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to:
\\MDT2013\DeploymentShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\MDT2013\share$\TEST8\TEST8.wim" "001CDrive" /flags EnterpriseN]LOG]!><time="13:16:21.000+000"
date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Command has been started (process ID 1248)]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1248)]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Version: 6.3.9600.16411]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Files/folders excluded from image capture by default:]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~bt]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~ls]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \winpepge.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Windows\CSC]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycled]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycler]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$Recycle.Bin\*]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \System Volume Information]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \swapfile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \pagefile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \hiberfil.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Turning on VERIFY option for network share]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Scanning files and directories...]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   0% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   1% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [   2% ] Capturing progress: 11:04 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   3% ] Capturing progress: 9:12 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   4% ] Capturing progress: 7:58 mins remaining ]LOG]!><time="13:16:50.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   5% ] Capturing progress: 7:20 mins remaining ]LOG]!><time="13:16:55.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   6% ] Capturing progress: 7:59 mins remaining ]LOG]!><time="13:17:07.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   7% ] Capturing progress: 8:23 mins remaining ]LOG]!><time="13:17:13.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   8% ] Capturing progress: 8:20 mins remaining ]LOG]!><time="13:17:17.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [   9% ] Capturing progress: 8:33 mins remaining ]LOG]!><time="13:17:26.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 11% ] Capturing progress: 8:21 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 13% ] Capturing progress: 7:37 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ RETRY ] Restoring C:\WIMA8B0.tmp again (Error = 1392)]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1"
thread="" file="ZTIBackup">
<![LOG[ Console > Error imaging drive [C:\]]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > The file exists. ]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Return code from command = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Error creating an image of drive C:, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
<![LOG[ZTIBackup COMPLETED. Return Value = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
5. Computer Backup Dir is accessbaile and permission is ok.
Any idea to resolve this issue
Shailendra Dev

After changing the BackupDrive=D: , I am able to take backup of D drive only , but I want to take all the local drives backup before installing windows 8.1
please suggest .
Shailendra Dev

Creating Windows 8.1 master image with MDT 2013,cannot capture .WIM

I am having an issue with creating a master image with Windows 8.1 and MDT 2013.
I have followed extensive tutorials on how to create a master image using Microsoft Deployment Toolkit. my goal is to have a fully configured windows 8.1 image which I can deploy through Windows Deployment Services. I have been relatively successful thus far,
except for one issue I have run into, which is successfully capturing this image as a .WIM.
I have successfully created a task sequence and the task sequence is able to run all the way through until the final step. Essentially the task sequence is supposed to install Windows and Office, then suspend the task sequence to allow me to make customisations
to the start screen and desktop background, and I simply click resume task sequence, and the task sequence should sysprep reboot and capture the machine image as a .WIM file.
the task sequence is able to sysprep the machine, but upon rebooting it boots into out of box experience, and does not create a wim file. I receive an error saying: "cannot find script file C:\ltibootstrap.Vbs" after the machine completes OOBE
I am using Windows Server 2012 r2, creating my Master machine image using hyper-v, and my master image is running Windows 8.1.
Any help would be greatly appreciated.

I'm not sure about the sequence of steps here. Try taking your captured.wim file and deploying it using MDT again, or at least to another machine. MDT sometimes leaves extra files around on the captured machine, so simply rebooting it may not get a accurate
test results.
IF you are getting the ltibootstrap.vbs it is most likely because there is a stray unattend.xml file somewhere in your image that is looking for this file. Crack open your Wim file and search for any unattend.xml files.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2013, Deploying Windows 8.1 on Surface and Dell Venue Tablets

I'm having numerous issues with Capturing Images and Deploying to Windows 8.1 Tablets. We are currently using Surface Pro 1, 2, and Dell Venue 11 Pro tablets. I am using a Windows Server 2012 computer with MDT 2013 installed. I can't get the tablets
to:
1-sysprep and capture using MDT 2013
2-Deploy a Task Sequence with a WIM and other applications attached. (I've tried using the simple standard task seq option with no luck)
3-I found another way to get a WIM (using imagex) but when i deploy task sequence it ignores my selection of applications to install outside the WIM and only installs the WIM (WIM 14gb = Win 8.1 Ent, Office 2013 x32, MS Updates)
Any help would be greatly appreciated. Everything is being performed within the LAN and with USB 2.0 thumbdrives for media.

Hi altimav8,
Are you trying to find out how to deploy Surface Pro method? Before capture the Surface pro image please download the latest drivers for the surface and made sure that they
were the only drivers that were going to be deployed. There have a specific MDT deploy support forum more about the MDT deploy related issue you can ask in MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
The related guide:
Surface Pro - Enterprise Deployment Quick Start Guide
http://download.microsoft.com/download/2/0/7/2073C22F-2F31-4F4A-8059-E54C91C564A9/Surface%20Pro%20-%20Enterprise%20Deployment%20Quick%20Start%20Guide.pdf
Thanks for your understanding and support
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows 8.1 Copyprofile Issue (SCCM 2012R2 MDT 2013)

Hi,
We're experiencing several issues during creation of our base Windows 8.1 image.
Running SCCM 2012 R2 with MDT 2013 Integration.
Admin user customizations (a couple of simple UI settings and a wallpaper) are done to the Windows 8.1 image in audit mode. The OS is then sysprepped and captured via SCCM capture media.
We are using a standard MDT integrated task sequence for a zero touch deployment.
We are adding copyprofile to unattend.xml in the relevant MDT settings package.
Sequence completes without error and customizations appear in the image.
However, desktop IE11 immediately crashes unless it's run as administrator. This can be fixed by disabling protected mode (not ideal)
All Metro/Modern apps (including IE) are also initially broken. They immediately crash and drop you back to the desktop when you run them.
After a reboot the modern/metro apps (apart from IE) seem to reinstall and function correctly.
Has anyone else got copyprofile working correctly for 8.1 in a SCCM/MDT task sequence?
thanks
James

Hi James,
We were able to work around this issue in the following way using SCCM 2012 R2. I know this is not how the process is documented or has worked previously but it is what worked for us.
1. Create an unattend.xml with the copy profile setting (and whatever other settings) enabled.
2. On the image which will be captured run all of our regular steps to customize on the administrator profile (I always set administrator pw at this point to have blank pw, don't know if still required), copy that unattend.xml locally.
3. Do not run a standard capture using SCCM capture ISO, instead manually run sysprep specifying the unattend.xml. I.e. sysprep /generalize /oobe /shutdown /unattend:C:\Unattend.xml .
4. Boot to either the SCCM PXE or some other environment on that computer that has network access, and access to imagex.
5. Run an imagex capture to a network location (in our case the C: was all that was needed).
6. Import that WIM into SCCM as part of task sequence. Also added same unattend.xml used for sysprep into the task sequence to apply settings during first boot after image.
7. Validated our start menu icons and layout are there on the image.
Until the behaviour changes in Windows 8.1 or SCCM, then this should get you by. Little bit of extra work in the capture but we had positive, consistent results using this method.
Thank you! This was driving me crazy! Now it works on the first try.
Just a side note: You should not use ImageX with Windows 8.1. Create a new WinPE Bootmedia and use DISM! ImageX is outdated.

MDT 2013 Windows 8.1 Task sequence Stops After first Reboot. login

Hi There,
The issue I am having is that After the OS gets laid down, and the Windows 8.1 computer reboots, The task sequence does not continue. It fails everytime. There are not any obvious errors that happen in the process that I can see in the logs. But I have
customized this process quite a bit and I could use some help. We are deploying potentionally to over 30,000 computers.
The test machine I have been using is the Surface pro 2.
The interesting part is after a failure is if I start the process over again , boots into PE, then run diskpart manually from command prompt to Clean Disk 0, and then reboot and start the MDT task sequence, it will deploy fine.
I also have a custom step that copies the TS media from the stick to a Recovery partition I create. The user can launch a -re-image or MDT refresh from an Icon/script, which will unhide this "recovery partition", and kick off a lite touch refresh.
This works succesfully everytime. We have remote locations with very slow links, so MDT over the network or MDT integrated with SCCM is not an option at this time. So this is the solution.
I am attempting to use MDT 2013 to deploy Windows 8.1 Offline, and using GPT partitions.
I am using a custom Format and partiition Step, that call the CustomDiskpart.txt script from %deployroot%\Scripts.
I am also using a Split image, as multi partitioned EFI/NTFS USB sticks are not a possibility for us , also, the USB sticks capable of this are seen by MDT as a "fixed drive" anyways. Which can cause issues in itself. So the LTIAPPLY.wsf has
been edited to search and apply ther split .swm files. This works well.
After the Task sequence failure I have tried launching the Litetouch scripts from the C:\MINNINT folder manually to continue the sequence, but it doesnt do anything.
I don't want to always be running Diskpart manually before imaging a new OEM computer. I needa second pair of eyes on this.
Thank You in advance!

Hi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine.

MDT 2013 Windows 8.1 application install with reboot problem

Hello!
I have a problem with an application install on Windows 8.1. I'm trying to install two applications and have activated "Reboot the computer after installting this application" for the first application. After rebooting the deployment window does
not show up agagin. BDD.log shows, that the deployment starts after the reboot but seems to hang, before the UI shows.
I tried to install this two applications under Windows 7, which works without any problems.
Here is the BDD.log for the failed deployment: http://pastebin.com/PbUH1LUq
Can anyone confirm this problem with MDT 2013 and Windows 8.1? Any ideas how to fix this?
Additional information: Further testing showed, that this problem just occurs, if the application install gets started separately after deploying the OS. If the applications are installed in one deployment together with the OS, everything works fine.

I did the same install on Windows 7, which worked without any problems. Here is the log file: http://pastebin.com/Qgn2PzyC
To make it clear:
If I run a Lite Touch Install task sequence to install Windows 8.1 and install the two applications within this LTI, everything works fine. The computer reboots after installing the first application and the deployment goes on and finishes successfully after
the reboot.
If I first install Windows 7 or Windows 8.1 via LTI and then (after LTI successfully finished) start a separate application install (using a custom task sequence with only one "Install Application" task in it), everything works fine with Windows
7 (installation continues and finishes after the reboot) but fails with Windows 8.1.
In Windows 8.1 the computer reboots after installing the first application, but after rebooting, the installation does not start again.
Keith, as you said, my environment is corrupted, I created an new fresh deployment share, just added the two test applications and the custom task sequence and tried again. Same result, Windows 7 works fine, Windows 8.1 fails by not starting the installation
after the reboot.

Since upgrade to MDT 2013, can't capture Windows 7 image.

Hi fellas,
I use Virtual Box to create a 32- and 64-bit reference Windows 7 VM, which I then capture using an MDT Sysprep & Capture TS. This worked without a hitch using MDT 2012.
I recently upgraded to MDT 2013. Since then, after the VM syspreps and reboots, I get a boot manager error saying Windows failed to start. Status: 0xc0000260.
Not sure where to look for any logs. What I've done so far:
- Upgraded to latest version of Virtual Box (4.3.18)
- Rebuilt both VMs from scratch.
- Deleted and recreated the deployment share and Sysprep & Capture task sequences.
Stumped for the time being, although I could always just boot to my Win PE disc and manually capture with imagex. But c'mon.

Thanks for your input, but this is indeed a configuration issue, and it makes sense.
Vbox VMs are configured according to the guest OS installed on them. For my Windows 7 x64 VM, it's configured of course to run as Windows 7 x64. In the MDT 2012 environment, the Windows PE version
was 3.0, which is based on Windows 7, and hence the VM could boot to it since it was configured for it.
But MDT 2013 uses PE 5.0, based on 8.1. The VM crashes or throws an error when trying to boot the PE 5.0 boot image. I went into the VM's settings and changed the Guest OS to 8.1 x64, and it booted successfully to Windows PE and captured the
image according to the Sysprep & Capture sequence.
Sorry for the wild goose chase fellas. This should've been the first thing I checked.

Deploy UDI Windows 10 with SCCM 2012 R2 and MDT 2013 Update 1

Hi,
Trying use "User-Driven Installation" with
SCCM 2012
R2 CU4 and MDT
2013 Update 1 for deploy Windows
10.
Created MDT Task Sequences with
template "Client Task sequence"
and Deployment Method "User-Driven Installation".
When I try to deploy I have error like:
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Part smsts.log
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Expand a string: WinPEandFullOS TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: smsswd.exe /run: cscript "%deployroot%\scripts\ztierrormsg.wsf" TSManager 22.04.2015 11:36:57 1160 (0x0488)
[ smsswd.exe ] InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
PackageID = '' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
BaseVar = '', ContinueOnError='' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ProgramName = 'cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf"' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
SwdAction = '0001' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Set command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Working dir 'not set' InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Executing command line: Run command line InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft (R) Windows Script Host Version 5.12 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Copyright (C) Microsoft Corporation. All rights reserved. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Microsoft Deployment Toolkit version: 6.3.8216.1000 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
ZTI deployment failed, Return Code = 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Unable to create WebService class InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Command line returned 5001 InstallSoftware 22.04.2015 11:36:57 1740 (0x06CC)
Process completed with exit code 5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
!--------------------------------------------------------------------------------------------! TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the action: Error in the task sequence.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionRetCode=5001 TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 22.04.2015 11:36:57 1160 (0x0488)
Clear local default environment TSManager 22.04.2015 11:36:57 1160 (0x0488)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 22.04.2015 11:36:57 1160 (0x0488)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
The operation cannot be completed because other resources are dependent on this resource. (Error: 00001389; Source: Windows) TSManager 22.04.2015 11:36:57 1160 (0x0488)
MP server http://sccm.domain.com. Ports 80,443. CRL=false. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting authenticator TSManager 22.04.2015 11:36:57 1160 (0x0488)
Set authenticator in transport TSManager 22.04.2015 11:36:57 1160 (0x0488)
Sending StatusMessage TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting message signatures. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Setting the authenticator. TSManager 22.04.2015 11:36:57 1160 (0x0488)
CLibSMSMessageWinHttpTransport::Send: URL: sccm.domain.com:80 CCM_POST /ccm_system/request TSManager 22.04.2015 11:36:57 1160 (0x0488)
Request was successful. TSManager 22.04.2015 11:36:57 1160 (0x0488)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
The command completed successfully. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)
Successfully launched command shell. TSBootShell 22.04.2015 11:37:31 696 (0x02B8)

MDT Updates for Windows 10 Technical Preview Build 10041
Если Вам помог чей-либо ответ, пожалуйста, не забывайте жать на кнопку "Предложить как ответ" или "Пометить как ответ".
http://zalozny.com.ua

Problem with ztisetbackground.wsf in MDT 2013 and Windows 8.1

Has anyone found a way to get ztisetbackground.wsf to work with a Windows 8.1 build after the WinPE phase? It works fine with Windows 7 builds.
Ad(Thanks)vance!
JJ

Unfortunately not. Doesn't look like it will be fixed in the upcoming release of MDT 2013 Update 1 based on the following post...
http://blogs.technet.com/b/mniehaus/archive/2015/03/03/mdt-2013-update-1-preview-what-s-changed.aspx.

Windows RE for Windows 7 in MDT 2013

Hi, I have Windows 2012 R2 installed with MDT 2013, I need to deploy some Windows 7 machines and I need the option "Run the Windows RE" at boot, I only get "Run the Deployment Wizard" and "Exit to Command Prompt", how can
I add Windows RE to the menu for Windows 7 deployments?

You don't mention what version of the WAIK/ADK you have installed with MDT 2013, this is important.
You must install the *full* OS sources for the *client* OS that corresponds with the same build number as the WAIK/ADK version you have installed.
If you installed the *latest* Windows 8.1 ADK version then you should import the Windows 8.1 *full OS* sources into your MDT environment (even though you are using Win7). Once there, rebuild the WinPE images from scratch.
-k
Keith Garner - keithga.wordpress.com

Installing Windows ADK and MDT 2013 without Internet

Hi
I have Windows 8.1 Update 64 bit
on a computer without Internet.
I would like to install Windows ADK
and MDT 2013. What's the proper procedure to
do this?
Thanks
Bye
Balubeto

You need to download the pieces from an internet-connected machine. They can they be copied (USB or whatever) to any machine, even those without an internet connection, to do an installation.
To get the necessary ADK pieces, download ADKSETUP.EXE and run it on the internet-connected machine. It will offer an option to download all the rest of the ADK pieces (make sure you select the right components) into a folder you specify.
The MDT installation is a single MSI file.
Thanks,
-Michael Niehaus
Senior Product Marketing Manager, Windows Deployment
http://blogs.technet.com/mniehaus
[email protected]

Windows ADK and MDT 2013 components

Hi
I noticed that Windows ADK is
installed in its 32 bit version even though I have
Windows 8.1 Update 64 bit.
It is correct?
Then, I installed MDT 2013
64 bit.
Now, where can I find a detailed description
about the components of this MDT?
Having to customize, deploy and create some
DVDs of Windows 8.1 Update
32/64 bit, what components
should I download?
Thanks
Bye
Balubeto

Yes, there are some weird historical reasons why the AIK goes to "\Program Files (x86)" and MDT goes to "\Program Files". Don't over think it too much, yes it's confusing.
Some recommendations (what I install on my machine):
Your deployment Server box should be running Windows Server 2008 R2 x64 or Server 2012 x64.
You should be deploying only Windows 7 or newer (Windows 8.1) or Server 2008 R2 or newer (2012)
Use the latest AIK
http://www.microsoft.com/en-us/download/details.aspx?id=39982 the ADK is platform agnostic, it will install on x86 or x64, but of course your server should only be x64
Install the latest MDT 2013
http://www.microsoft.com/en-us/download/details.aspx?id=40796 x64 version.
MDT documentation *.chm is in the MDT install directory.
AIK documentation *.chm is in the ADK install directories.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

WIndows Enterprise 8.1 - MDT 2013

Similar Messages

Maybe you are looking for