Hi All,

Really hoping I'm missing something obvious here.  I'm in a corporate environment and I've recently moved my workstation to Windows 8.1 Update x64.  I've installed Deployment Toolkit 2013 (as I had before) and used setupadk.exe to pull down the latest Windows ADK (at least, it say's everything's up-to-date when I try and upgrade it).

However inside Deployment Workbench when creating new media I cannot create any ISOs - on the 'General' tab (under Media Properties) I can choose 'Platforms Supported' and I can also tick 'Generate a Lite Touch bootable ISO image', however under the 'Windows PE' tab the options to generate any ISO are greyed out.  When I do then click 'Update Media' the source gets copied over to the target folder, but the ISO never gets generated.  I've not tried updating the WIM so I don't know if that's working or not.

The odd thing is that under 'Components' Windows ADK is listed as "Required", not "Installed", yet I have no issue interacting with the deployment shares.  I've tried going through the 'Download' process through the UI but that hasn't made any difference.

I've already tried completely removing and reinstalling ADK and MDT and I've used the latest versions of each.

If anyone has any ideas I'd be very grateful - as is generally the way I've only noticed this now that I've got a deadline to meet!

Peter

I executed the command: "Get-AppxProvisionedPackage -online | ForEach-Object {Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}" to remove provisioned apps on a VM in order to speed up initial log on time. 

Does anyone know where I can download the appx package for Microsoft Reader to add it back during deployment?

Hi,

I know this question has been posted a fair number of times on the forums but so far none of the responses have fixed my issue.

I am having trouble connecting to the deployment share receiving the error message below.

"A connection to the deployment share could not be made. The deployment will not proceed. The following networking device did not have a driver installed PCI\VEN_10EC&DEV_8168&SUBSYS_00041179&REV_10"

I have downloaded the correct network drivers and even installed Windows 7 manually and added the drivers to check they are correct drivers.

I have added them to the OOB drivers in the deployment share and then updated and also regenerated the deployment share. Then i have updated the .wim file in the boot images folder but yet i still cannot get past this stage.

Does anyone have any further ideas that i could try?

Thanks,

Adam

Hi everybody

I just set up my first MDT environment and played around with bulk adding computers to the MDT database. There I recognized something strange. The computer ID didn't start at 1, it started at 2000 and I don't know why and how I can change this. I guess it's something in the database. I deleted all computers from the database and want to start with ID 1. Does anybody know how I can achieve this?

Thanks for the help.

Hello all,

I know that MDT 2012 Update 1 has the necessary intelligence to create the GPT partition etc. when the Gather Process detects that the system is UEFI enabled. However i wanted to configure the Format and Parition task myself, so i copied the default one, disabled it and just added a new one with the following configuration.

Disk Number 0

Disk Type = GPT

i then added

EFI, Partition Type = EFI, 500 MB, file system FAT32

MSR, 128 MB,

OSDisk 40 GB, PRIMARY

i then start the Win8 x64 Task Sequence , it formats the disks, it applies the image, but then when it reboots i cannot boot.

What am i doing wrong here ?

Alsx Verboon www.verboon.info

Hello, 

I've got 20 NUC to deploy but I keep getting errors and for first time I've no clue why. 

The error is always the same "startup fails processing specialize phase."

I looked at the logs. I don't see a thing related to this kind of error. On the plus side, I have to boot a linux livecd to get the logs. I've no keyboard and mice when it's happening. 

I thought there was something wrong in my golden image. Even if I've use it like a hundred times before. 

So I tried a "from source" deployment. Genuine 7 Pro x64 MSDN, nothing in it, no touching of the default unattended file -> same error.

Then I tried another trick. I did a fresh installation from usb key and then tried to sysprep with MDT2013. -> same error.

I never had an error of this kind with sysprep. So I think there is something fishy in the basic unattended file but what ? Since I've got nothing in the logs.

Thanks

Hi guys

Can someone point me in the direction of the best way to enable TPM+PIN through an MDT deployment (not integrated with SCCM) set the PIN as a random number and where possible store the PIN to a file share.Windows 8.1 x64 for various tablets.

Thanks in advance

NN

Is it posible to make an inplace upgrade from Windows 7 to Windows 10 with MDT2013?

Chris

Ive been trying to create a reference image for an optiplex 790 with uefi turned on, everytime i go start the process after the OS install portion i get errors in the task sequence:

Failure (5615) false: boot drive was not found, required?

it fails to run the action: install operating system.

is there something im missing in the task sequence to make this work. Ive read everywhere that if i have the task sequence set to GPT or even MBR that MDT will know if its a uefi bios and should work.  I am using a hard drive that used to have an MBR not sure if that is the reason.  Any help would be appreciated. Thanks

I'm using the MDT database to consolidate five windows 7 task sequences on five SCCM2007 site servers to one task sequence on one 2012 R2 site server. I got my locations by ip subnet working and most of the settings applied successfully, Join Domain, add  a group to the local  admin group, but I can't seem to get the AdminPassword=MyPassword to work.

I've got an "apply windows settings" step in my task sequence. But the machine keeps getting what ever its password is set to.

If I leave it bland then I get a blank password etc.. If I run without the "apply windows settings" step then then the task sequence fails and finishes with a mini setup prompting for a computer name. I can see the other values that are collected in the Bdd.log:

Remapping variables.

Property OSDDomainName is now = My.Domain

<Message containing password has been suppressed>

I even tried adding the default setting directly to the customsettings.ini file: AdminPassword=MyPassword. But the workstation still takes its password from the "apply windows step". I'm going to try and enable debug logging and see if the log has anything about the local admin password. Anyone have any ideas? What am I doing wrong here?

[Settings]
Priority=LSettings, LAdmins,

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=NO
SkipProductKey=NO
SkipComputerBackup=YES
 SkipBitLocker=YES

Hi,

I used MDT 2013 to create a sysprep & capture tasksequence. I'm using this TS to sysprep & capture some disks (W7). These disks were delivered to me and belong to different clients. Now I sysprepped and captured the first disk with no errors at all. I deployed it using a new - default - tasksequence and everything worked well. Next I took the second disk and captured this as well using exactly the same TS. Again no errors in the Final Summary. I created a brand new second task sequence, again just the default TS, to deploy this image. So I deploy this image and everything seems alright, creating partitions and installing the image etc, until at some point when the pc boots: it gets "stuck" at the logon-screen. When I try to login with the local administrator I get the message that the user is disabled. What is happening here? Why does this administrator got disabled on the second disk and not on the other??? I didn't change the task sequence, I didn't change the autounattend, on both pc's I used the local administrator to launch the capture which ended with no errors. I searched Google and this forum but couldn't find an explication. I recaptured the disk and recreated the deploying TS and even tried to deploy to another pc but without success. For info : I'm not joining any domain, I'm deploying into a workgroup.

Hi all

I have an MDT 2013 installed on a Win 8.1 x64

I configure my Customsettings.ini in media

I create my offline media in Media and next time I open to check my customsettings.ini in media it is empty.

Any suggestions?

Br Chris

Best Regards Chris Steding MCTS Windows 7 Configuration www.compit.se

I had an MDT solution that was working fine, until yesterday. I started getting errors during image restore in WinPE, or sometimes it would boot normally but not resume the task sequence after the auto login, (it is able to rename the computer and join the domain). I've regenerated the boot images, re-added the drivers, and double checked the permissions on the deployment share.

Attached is the bottom of LTIApply.log

<![LOG[  Console > [  86% ] Applying progress: 1:05 mins remaining ]LOG]!><time="12:04:05.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > [ 100% ] Applying progress ]LOG]!><time="12:04:15.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Successfully applied image.]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Total elapsed time: 8 min 13 sec]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The image C:\MININT\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim was applied successfully.]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 5625 sent: The image C:\MININT\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim was applied successfully.]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Find the boot drive (if any) [True] [6.3.9600.17056] [False]]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-7LCDATU\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\MININT-7LCDATU\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDisk : \\MININT-7LCDATU\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-7LCDATU\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Ready to Prepare boot partition: V:]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property UILanguage is now = en-US]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FindFile: The file ztiRunCommandHidden.wsf could not be found in any standard locations.]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FAILURE: 1: Verify ztiRunCommandHidden.wsf is in the path]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="2" thread="" file="LTIApply">
<![LOG[Visible console fallback.]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "X:\WINDOWS\SYSTEM32\BCDBoot.exe" C:\windows /l en-US  /s V: /f UEFI]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1948)]LOG]!><time="12:04:16.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Boot files successfully created.]LOG]!><time="12:04:17.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="12:04:17.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Run Command: X:\WINDOWS\SYSTEM32\bcdedit.exe /timeout 0]LOG]!><time="12:04:17.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCD> The operation completed successfully.]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Created scratch folder.]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copied unattend.xml to C:\Windows\Panther for image apply.]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 600)]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Version: 6.3.9600.16384]LOG]!><time="12:04:18.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Image Version: 6.3.9600.17031]LOG]!><time="12:04:22.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > The operation completed successfully.]LOG]!><time="12:04:45.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="12:04:48.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FindFile: The file LTIBootstrap.vbs could not be found in any standard locations.]LOG]!><time="12:04:48.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="12:04:48.000+000" date="01-30-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Event 41002 sent: ZTI ERROR - Unhandled error returned by LTIApply: Invalid procedure call or argument (5)]LOG]!><time="12:04:48.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[TargetOS is the current SystemDrive]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[    Open Control File: OperatingSystems]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[------  Applying Windows image using ImageX.exe ------]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI applying image \\DeployShare\MDTDeploy$\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim using ImageX]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41023 sent: LTI applying image \\DeployShare\MDTDeploy$\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim using ImageX]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\DeployShare\MDTDeploy$\Operating Systems\ReferenceImage_8.1_11-12-14]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast is not possible when running in a full operating system]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\LOANER106SP3\root\cimv2:Win32_LogicalDisk.DeviceID="C:"    \\LOANER106SP3\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #2"]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\DeployShare\MDTDeploy$\Tools\X64\imagex.exe"  /apply "\\DeployShare\MDTDeploy$\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim" 1 C:]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 3252)]LOG]!><time="13:28:58.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 3252)]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 3252)]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > ImageX Tool for Windows]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Version: 6.3.9600.16411]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > [   0% ] Applying progress ]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Error restoring image.]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > A required privilege is not held by the client. ]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 2]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[FAILURE ( 5624 ): 2: Run ImageX:  /apply "\\DeployShare\MDTDeploy$\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim" 1 C:]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="3" thread="" file="LTIApply">
<![LOG[Event 41002 sent: FAILURE ( 5624 ): 2: Run ImageX:  /apply "\\DeployShare\MDTDeploy$\Operating Systems\ReferenceImage_8.1_11-12-14\ReferenceImage_8.1_11-12-14.wim" 1 C:]LOG]!><time="13:28:59.000+000" date="01-30-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">

Running MDT 2013 with ADK 8.1 on Server 2008 R2.  Have had no issues so far with all the DeploymentShares I have created.  As well all Images up until now have been fine. 

Largest Offline Media I have created thus far had a  "Content" folder which was 29.0 GB with the ISO coming out of it at 28.1 GB.

Anyhow, I am on to a new Image and everything has been fine, up until the creation of the Offline Media.  When running the "Update Media Content", it appears to run fine.  However, it basically just hangs once the "Content" folder hits 29.5 GB in size.  At this point it is copying the "%DeploymentShare%\Tools\x64\BCDBoot.exe" file (which is 177 KB).

Some other notes:

• File is not corrupt, already checked it
• Media is being created to "D" drive, not same drive as MDT Installation
• I have full Admin Rights to all Drives and MDT is running with Administrative Rights
• Have plenty of free space on the "D" drive (~1.5 TB)
• All Drives are NTFS
• I have tried shifting applications and even removing some.  So it does not always hang on the "BCDBoot.exe", but always does when the "Content" folder hits 29.5 GB...

Haven't seen anything in documentation about any size limits.. 

Anyone ever created Offline Media that had a Content folder larger than 29.5 GB or an ISO that was over 29.5 GB?

I'm trying apply offline patches to a Windows 7 WIM I created in September.  But after applying several patches and deploying to a test machine, Windows Update shows itstill needs the same set of patches I applied offline.

Ten-Thousand Foot Patching Overview:

1. Image machine
2. Determine necessary patches
3. Acquire patches from catalog.update.microsoft.com
4. Place all msu's in the same directory
5. Mount WIM & patch, pointing to the directory above
6. Commit, unmount & commit
7. Import WIM into MDT
8. Update OSD Task Sequence to use updated WIM
9. Image a test workstation using the updated Task Sequence which is laying down the updated WIM.
10. Run Windows Update
11. The unchecked & highlighted updates in the image below (also on my OneDrive here:http://1drv.ms/1Jdu6DT) are the updates I applied offline, yet are still required:
    
    

Please check my OneDrive here http://1drv.ms/1ulS2yh for just about everything you might want to review:

• Detailed patching process (in a text document): http://1drv.ms/1BFBR5i
• Logs of *every* DISM operation: http://1drv.ms/1ulS2yh
• Redirected output (stdout & stderr) of *every* DISM operation: http://1drv.ms/1ulS2yh
• CBS.LOG and WindowsUpdate.log after OSD (but before actually installing the same updates): http://1drv.ms/1ulS2yh
• Deployment logs are available upon request.
• DISM version is 6.3.9600.17031
• WIM patched on a Windows 8.1 Enterprise laptop

We are making a push to move users from Office 2010 w/ MAK licensing to the subscription based Office 2010 that comes with our O365 subscription.

The way we installed Office was with the Office Customization Tool. Since the computer had to be licensed, this wasn't an issue when deploying an image via MDT with Office already installed. Now that we are being licensed per user, is there a way to "bake in" Office 2010 subs into an image in a way that would require a sign in of each individual user that uses one machine?

The scenario would be we have a machine that is designated as a loaner. We hand it out to a user who forgot their machine. They log in, and being that it was a freshly imaged machine, they are prompted to sign in using their O365 credentials when they open Excel. They later return the machine. Then a new user forgets their machine so they come in and pick up that same loaner. When they sign in, will they be asked to sign in with their O365 credentials when trying to access WinWord or will it just open utilizing the previous user's "activation"? Or am I thinking about it all wrong?

Hi,

I created task sequence for deploying os

in this task sequence I didn't deleted the - "Apply Local GPO Package"

i deploy it on few computer and it make me problem with accessing programs

I tried set default setting to local GPO on the deploy computer

but it still blocking me some things on this machine

How can I remove this local GPO package on deploy machine after It was set

please help me

Thanks.. 

I have been trying to image a Surface Pro 3 using MDT 2013 and have been unable to get past the Format and Partition portion of the deployment.  At first I would get an error that it was unable to format or partition the drive and then after that it just reboots after trying for so long.  I am able to image any other device with the same task sequence and have no issue just having an issue with the Surface Pro 3.  Any help would be great.

Thanks in advance.

I am getting the error FAILURE (5210)

ZTI Error - Unhandled error returned by ZTIDISKPART: Object required (424)

Hi ,

I am quite new for MDT 2013. I have recently installed MDT 2013 in my Windows Server 2012.

Now , I do have about 10 physical machine with different hardware specification inside. I have installed Windows 8.1 with all required software in it and now I want to distribute the same image in all 10 another physical machine.

Can anyone provide me the steps to implement this...

Do I need to create the image using image x software and then use it as a standard image to be deploy it in rest of the systems..

Thank you...

Hello,
I have a problem in MDT 2013, I am trying to install a machine (OS 2012R2) with 2 partitions (C 100GB and D the rest of the available space). The problem is that if I specify the two partitions in the task sequence, the extra partition is never created. (even if the checkbox is checked)

If I delete the second partition from my task sequence (so keeping only the C 100GB), the extra partition is created !

I even tried to create 2 partitions c 100GB and D 100GB with 100GB remaining free, in case the problem was the free space, but no... the same problem, the extra partition is not created.

Can someone please tell me how to solve this ?

I know I can create a postinstall script to create the second partition but... why is it not working during the installation ?

Thanks in advance for your help

 Marc.