Hello,

I am trying to do make a customized start menu using the process of copying LayoutModification.xml file to the C:\Users\Default\AppData\Local\Microsoft\Windows\Shell folder. I am using a PowerShell script to do the copy xml file. The file copy is successful but when I login as a new user I do not see the customized start menu. I am doing the file copy in State Restore in the TS.

• Doing this on Win 10 Enterprise RTM joined to a domain
• Do I need to delete/rename the existing file?
• Do I need to rename my LayoutModification.xml file?
• I am doing the LayoutModification.xml file copy in the correct place in the TS

Is anyone having the same issue?
I don't skip the WinPE-Welcome dialog because there are a lot of machines with different keyboard layouts which find their way to my deployment lab.
However it will sometimes ask me for the credentials to the deployment share before showing the WinPE dialog.

I'm on the latest ADK (1511) and MDT 2013 Update 2.

This is the first I'm trying to install a deployment server. I have added a new VM Deploy server running windows server 2012 R2. I added the WDS role then installed MDT 2013 Update1 and compatible  ADK. I was able to get things working as for as PXE boot and uploading operating system from dell CD. I deployed image from the cd through the server everything works fine. Now I'm trying to capture an image of a working machine with all the updates and necessary changes I have made. I created new task sequence and updated deployment. This is the error that I'm getting any help would be greatly appreciated. Thanks 

Hi All,

I have just built a new MDT server, loaded all software drivers, created task sequences etc and everything is running fine on other computers except for one model, Dell Optiplex 780. After PXE booting the USB and mouse stop working, I have downloaded all drivers for this model, updated deployment share and regenerated images but still no result. Ive done a lot of searching online and tried various suggestions but nothing seems to help. After the Windows logo appears, the light on the mouse goes off (Numlock light stays on the k/b), if I plug the mouse into another port, the light comes on but doesnt work.

Im loading Windows 7 Pro x64 using MDT 2013 Update 1.

Any help is appreciated!

Cheers

Dave

Hi!

I am trying to figure out how to use MDT to deploy Windows 8.1 on the new trashcan Mac Pro's.

This is what I've done so far.

Disabled the default Format and partiton step with the property DONOTFORMATANDPARTITION=YES just to get rid of errors at the end, i have alos tried to remove the Volume entries in this step with out the above mentioned property.
In this step i have also set the Disk type to GPT and checked the Create Extra 'Active' Partition

Created a custom answer file to diskpart with the following command
sel dis 0
sel par 4
format fs=ntfs quick override
active
exit

Running my custom diskpart step after the default one.

Changed the default Install Operating System step to install on disk 0 partition 4.

All seems to work fine until the computer reboots and i should start windows to continue with the deploy.
Instead of booting windows it boots into OSX.
I've tried to change the start disk with the OS utility, but it gives the error "The bless tool was unable to set the current boot disk."

Ive tried the exact same thing on a older Macbook Pro, and this works flawless. It seems that Apple dropped some legacy support in the new EFI firmware on the new Mac Pro.

If i try to use bless with the --legacy parameter it tells me "Legacy mode is not supported on this system". I used legacy to boot windows on the older Macbook Pro.

Anyone got this working or have any suggestions?

Hey guys,

Does anyone know if the Bug in the ADK 10 1511 for ConfigMgr (Blog Post) also occurs with MDT 2013 Update 2 (Standalone)? According to the Blog Post, the Bug is only related to ConfigMgr, but I wanted to check first, before I upgrade my current ADK 10 (1507 / RTM)

Thank you in advance.

Simon Dettling | msitproblog.com | @SimonDettling

I am trying to incorporate Bitlocker during my Deployment. 

This is what the CS.ini looks like:

[Settings]
Priority=Default
Properties=Type,MyCustomProperty

[Default]
_SMSTSORGNAME=Corp - Build Lab
UserDataLocation=NONE
OSInstall=Y
AdminPassword=P@ssw0rd
TimeZoneName=W. Europe Standard Time

WSUSServer=http://NLWUSSV02:8530
SLSHARE=\\REMCORPMIG01\Logs$\%ComputerName%
SLShareDynamicLogging=\\REMCORPMIG01\Logs$\%ComputerName%
UDDIR=%ComputerName%

ApplyGPOPack=NO

TimeZoneName=W. Europe Standard Time

JoinDomain=corp.Corpgroup.local
DomainAdmin=JoinAccount
DomainAdminDomain=corp.Corpgroup.local
DomainAdminPassword=P@ssw0rd

BDEInstall = TPM
BDERecoveryKey = AD
BDEInstallSuppress=NO
BDEWaitForEncryption=FALSE
BDERecoveryKey=AD


SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES

SkipSummary=YES
SkipRoles=YES

The deployment start, the OS installs and after the first reboot the Task Sequence just stops, no error message.

The logs show an error but i do not even get the usual HTA page at the end of a deployment with errors

This is the last lines of the BDD.log

Validating connection to \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
SMS Task Sequencer already found on C:\MININT\Tools\X64	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
Mapping server share: \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:12 PM	0 (0x0000)
RUN: regsvr32.exe /s "C:\Users\ADMINI~1\AppData\Local\Temp\Tools\x64\Microsoft.BDD.Utility.dll"	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
Found Existing UNC Path Y: = \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
DeployRoot = \\REMCORPMIG01\MDTBuildLab$	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)
FAILURE (Err): 429: CreateObject(Microsoft.BDD.Utility) - ActiveX component can't create object	LiteTouch	2/4/2016 4:57:13 PM	0 (0x0000)

For the moment the TPM is not activated, it waits for State Restore in the Task Sequence, i have a Bitlocker group folder with Task sequence variable BDEInstallSuppress not equals YES

In this folder i have a couple of applications using cctk version 3.0 that set a BIOS password, enable TPM and activate it.

The OS drive was once encrypted so i have ran diskpart and used the clean command already

Could that be an issue with UAC? 

Afternoon

we've been using MDT for quite some time to build and deploy images without any real issues.

We are however having a load of issues with windows 10 Ent x64.

Windows 10 was deployed to a VMware VM over PXE - all fine.

All the necessary software loaded we prepared for a sysprep and capture. 

On earlier builds of windows 10 this wasn't an issue - but on the November release we are having all sorts of unexpected issues:

Firstly from the client we wanted to capture I would manually map a drive and run the liteTouch script - this works with Windows 7, 8, 8.1 and early Windows 10.

Now, in order to get the process to run at all, I had to create a bat file that runs on the client that maps the share and calls the Litetouch script - this works as I am able to rick click and select run as admin the bat file which I can't do if I manually map the share and right click directly on the Litetouch script. - ok so first obstacle out of the way on to the next....

The process runs right up to the point of sysprep. It does sysprep but for some reason now it removes the NIC driver, so kjust as sysprep is getting to the end of it's process before a reboot it removes the driver which kills access to the deployment share - how on earth do I get around this? and why is it happening with this particular build of Windows 10?

cheers

Ok, so a little bit about my setup. I'm using MDT 2013 U1. I have a wim of Windows 7 Pro 64 SP1.

I am attempting to deploy to a Dell Precision 7710. This device uses 2 M.2 PCIe SSD's in RAID1 (using Intel RST).

I have added Hotfix 3366972 by injecting it into the wim using dism (using this https://support.microsoft.com/en-us/kb/2990941 method). I did NOT inject the hotfix into the boot wim, because it is WinPE 10, so should be supported natively (my Windows 10 installation disk can install to the drives without issue). I have also injected the Intel RST f6flpy-x86 (downloaded from https://downloadcenter.intel.com/download/25165/Intel-Rapid-Storage-Technology-Intel-RST-RAID-Driver ) drivers into the boot wim, and have the f6flpy-x64 drivers injected into the installation.

I can boot into the MDT boot wim just fine. I select my task sequence, it deploys, and reboots. Upon booting Windows, the PC has a BSOD. When attempting to boot into safe mode, it halts at DISK.SYS before BSOD'ing. Obviously it doesn't like that.

I have attempted booting into an installation disk and removing DISK.SYS from C:\Windows\Drivers or C:\Windows\System32\Drivers, I cannot remember which at the moment. I didn't expect that to work because it was specifically disk.sys, and it didn't, but I figured I'd tried because I've had success removing other faulty drivers before. I have also tried reinstalling the RST drivers by booting into an installation disk and using dism to inject the drivers directly, with no effect. As a last ditch effort, I even tried running a chkdsk /f, which didn't work.

I have never had to deploy to NVMe disks before, and I am truly stumped. I know my org's switching to Windows 10 come March / April, but we haven't converted yet, and our images aren't "Golden" yet, so my manager isn't allowing us to just image this one with 10 early.

Anybody with any ideas?

Hi all. We are running MDT 2013 U1. We recently converted from an all-in-one .wim solution to utilizing task sequences for application deployment.

I am having issues with two specific applications. One is an email archive plugin for Outlook (.msi) and the other is Citrix Receiver 4.3 (.exe). The problem I am having is when these applications deploy the task sequence hangs. The applications fully install but what happens is someone has to come over to the machine and move the mouse for it to proceed to the next task sequence. Power Settings by this time are configured for the system to not go to sleep because it was sitting there so long before the computer would do just that. If someone sits there moving the mouse the whole time from the point the application begins to install it takes about 2 minutes. If no one moves the mouse it can sit there for days if we let it. No idea what the deal is with these two specific applications. It doesn't depend on which order I put them in my application bundle or if I set them up to install as separate applications and not part of our bundle.

Has anyone seen this before? I don't see anything out of the ordinary in our logs.

Hi Guys,

I am getting an error when importing an operating system into my deployment share.

Performing the operation “import” on target “Operating system”.
Creating new item named REFW81X64CDrive in Windows 8.1×64 REFW81X64.wim at DS002:\Operating Systems.
Creating new item named REFW81X64CDrive in Windows 8.1×64 REFW81X64.wim at DS002:\Operating Systems.
Item already exists: ‘E:\MDT\DEPLOYMENT\Operating Systems\REFW81X64CDrive in Windows 8.1×64.wim’ specified.
Import processing finished.

It says item already exists ” specified. Can you please tell me what is happening??

I have done abit of research and some people are saying to remove the tag of the operating system from the Operatingsystems.xml in the control folder in your deployment share. I have tried this buyt it still is failing.

Some please help!

I tried to enable Bitlocker (manually) after a deploy, even though it gives me the option to save the recovery-key, but after I restart the laptop, the bitlocker screen comes up (after POST) and asks me to put the recovery key. Strange part is, it doesn't recognize the key at all. 

Any help is appreciated. 

Thank you!

I'm working to create a usb bootable flash drive with the contents of our MDT deployment share so my guys can upgrade some remote users to Win 7. I created a profile that contains all the  apps, drivers and Win 7 image then created the media and updated the media. Using a 64 gig flash drive I diskpart and all that stuff then loaded the required files to the flash drive. When I try to deploy using the flash drive I get the following error..

Status 0xc0000017

Info Ramdisk device creation failed due to insufficient memory

Anyone have any ideas what is causing this??

I have been working on updating the deployment shares in our environment to MDT 2013 Update 2. I have successfully performed this operation on 4 deployment shares. However, I have 2 that are giving me the same problem after having updated the deployment share I went to modify the WinPE settings in the properties of those deployment shares. When I click on the WinPE tab the MMC crashes. The following is displayed.

Unhandled Exception in Managed Code Snap In

FX:{ffb8695a-66b4-4929-abb6-15cb8bd2ae3d}

Object reference not set to an instance of an object.

Looking for additional options other than what I have seen in various searches.

MDT 2013 Update 2 console from any system gets same error on these deployment shares. I can access other deployment shares using the same MDT 2013 Update 2 console and perform these functions without issue.

Windows Assessment and Deployment Kit 10 has been reinstalled.

Attempted to create a new deployment share from MDT 2013 Update 2 and get the same results.

Server where deployment share is located has been restarted.

Database entries in settings.xml file are there and have no values

Powershell is installed on the system where MDT 2013 Update 2 is installed.

Share perms are at "Full Control" for Everyone.

Other than opening a case with Microsoft are there any ideas?

Hi All 

Recently, I have installed MDT 2013 Update 1 on a Windows 2012 R2 WDS Server. 

I have edited my bootstap.ini file and boot sequence is working fine without any issues. the only problem that I have is, always it prompts me to enter the deployment share manually. Once I enter it manually it continues the rest of the tasks without an issue.

I can confirm that \\<Server>\DeploymentShare$ has "Everyone" full control permissions. Also I have added the DeployRoot=\\<Servername>\DeploymentShare$ in to my bootstrap.ini file.

Is there anyway to fix this issue? 

Two questions, hope that is ok.

One, anytime I deploy a machine using UEFI the Wizard windows sizes are all messed up, is there a property I can set to force the windows to a standard size.  Happens in WinPE and inside Windows.

Two, MDT 2013 Update 1 and Update 2 does not see the Surface Pro 4 as any type of machine, desktop, laptop, server or vm, I use the is functions to name my machines and that fails because all property are false.  the chassis type returns 1 from a WMI query.

Hey all. Ive been following this guide here to create a WinPE boot usb since we don't use PXE at my place of work:

https://msdn.microsoft.com/library/windows/hardware/dn938386(v=vs.85).aspx

I am trying to stand up Win10 in our environment with MDT. How can I create a bootable WinPE USB if the server we use for MDT is virtualized? All of our client computers do not have optical drives and USB is locked down tight unless we use your network admin accounts. I tried converting the contents to an iso and then burning the iso to usb locally using the usb/dvd download tool but it always fails at about 98%. 

Upgrading Windows 7 Enterprise x64 to Windows 10 Enterprise x64. The upgrade task sequence appears to work fine with no errors, but the Post-Processing group does not run. Looking at the smsts.log file, it is because "Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows\Win10UpgradeStatusCode does not exist".

What puts that registry value there, and why would it NOT put it there? The upgrade itself seemed to go well.

We're using MDT 2013 Update 2 with WDS on a Windows Server 2012 R2. We have a mixed enviroment with Windows 7 and just started moving over to Windows 10. Over all everything works more or less as it should. But specifically with Dell Latitude E5450 we have massive problems. Deployment constantly fails at some (random) point in about 65-75% of all computers we have tried to install windows 10 on (about 200 E5450's so far). And this is bare-metal installations. Not upgrades.

The most common error is "bddrun has stopped working". This occurs on random applications when ever the computer feels like it. Also every now and then application installations fails with an error message claiming that another installations is already running or that reboot is needed. And as I said; It varies exactly where the errors occurs. It's not always on the same application/step.

And sometimes the computer tries to swith to wireless network mid-deployment, so it stops. Sometimes it installs 2 or 3 applications and then suddenly it fails with error message "unable to set working directory".

All computers get the same Win10 REF-image and is deployed with the exact same Win10 task sequence. We have about 40 different computer models in our enviroment. Mixed with Dell, HP, Lenovo, Microsoft Surface etc. But Dell Latitude E5450 is the only model that acts this way with Windows 10.

I've managed to fix some hiccups by completely removing all Windows 10 E5450 drivers from the MDT (we're using total control driver assignment btw) and letting Windows 10 install it's own drivers instead.
If I imported Dell's driver CAB for the E5450 to the MDT I got some weird errors when Windows 10 decided to start updating all drivers mid-deployment.

So... I've been rambling on for a while now and I'm sorry for that. I guess my question is this: Is there anyone else out there that has any experience in deploying Windows 10 to the Dell Latitude E5450 using MDT 2013 Update 2? I'm at a loss here.

//Andreas