Recently I have been seeing this issue with MDT and deploying my image.

It all looks fine, then when it restarts I get a nice black screen  \

Status: 0xc0000428 Windows cannot verify the digital signature of this file

This appears to be happening on all of the images. Nothing was changed on them.

Hello everyone,
I want to create a Windows 7 installation disc that will allow me to have, immediately after installation, a system updated with the latest hotfixes, installed programs and all the settings I want already selected in the system.
Now, I used MDT 2013 on x64 Windows 8.1 Pro to create a DeploymentShare Windows 7 Pro x86, including drivers, applications and various hotfixes, once I create the image of Windows PE, through which I install the above system from DeploymentShare, all row smoothly, but I have any dubious:

1) Once the system is installed, they log me in as Administrator, why?

2) If I log in as Administrator, then I have to run the sysprep.exe / generalize / oobe before delivering the computer to an imaginary customer?

3) If I want to make changes to the settings of the user (for example to make sure that hidden folders see by default after installation or arrange the icons on the desktop as I will ensure that the end user see it exactly so) I have to use the CopyProfile?

4) If yes, at what stage should I use the CopyProfile? Specifying an unattend.xml during sysprep.exe on point 2? Or maybe I recapture system image after install it and use the file *.wim with a different unattend.xml, that is, in practice doing two laps of installation?

5) Once I captured the system image, when I try to install it, the system logs me in again with Administrator account instead of OOBE, why?

I want to do this final procedure on the end user PC:
1) Put the DVD (or USB) of this modified Windows
2) Install Windows automatically with all applications, hotfixes and settings
3) Once Windows is installed, I install in audit mode all drivers for that PC and sysprep /oobe it
4) Give the PC to the client

Thank you in advance!

P.S: sorry for my bad english

Hey can someone give me some insight here?  I have a Dell Latitude 7350-being imaged with Windows 8.1 from MDT.  The problem is that the Audio driver will not install.  I can manually install it but MDT wont do it. 

Thoughts?

As the title says, I upgraded MDT component for Windows 8.1 (ADK for 8.1), regenerated boot images, did a brand new plain task sequence for Windows 8.1 and I got a red screen right after the installation on the .win image.

Failure 5627, -1073741515 0xC0000135

Anyone has an idea about the error? A bunch or error number doesn't give much.

Thanks!

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 updating an already existing Golden Image today. Some M$ updates, a few up upgrades and software changes etc. BUT, the bigger issue is the ADMIN ACCOUNT issue I've run into. (I think, anyway)

Old admin account = Administrator, which recently got a NEW password- but my MDT image is still using the old, now extinct password

New account username = ADM-MM and using a new password.   <--- This is what I need to use going forward.

Should I:  Recreate the image from scratch with new ADM-MM account, or can I alter my image to useONLY this new account, and forget the ADMINISTRATOR account (or simply, not use it).

My confusion is: When I build a new machine, I'm using my new ADM-MM credentials to connect to the share etc, and while it works just fine, once the machine is "ready", it has the local "administrator" account, where I need to log in with the old PW.  

Suggestions?

Thanks gang,

Mark M aka Rob Base

Hi,

I'm trying to capture an image from a Windows 7 computer. The computer is not a member of the domain, as it is recommended per sysprep, but the MDT server is a member. I am asked several times for credentials in connecting to the deployment share. Once I run LiteTouch.vbs from the share and the PC reboots, I am asked again for credentials, and I provide the correct ones, yet the process cannot connect to the deployment share. My bootstrap.ini file is default with no user credentials saved (I can't save a domain account password in plain text on a server, house rules). The network is good. Where else can I troubleshoot?

Thanks

Jason Watkins MCSE, MCSA, MCDBA, CCNA

Hi, My MDT server no longer works as expected via PXE boot. After the target machine loads the .wim file an empty command windows is shown. I have returned the custom settings.ini and bootstrap files to default and ensured nothing is being skipped within the task sequence within both files in hope of viewing the wizard.

However from the same target machine if I map drive to my Deploymentshare/Scripts directory and run LiteTouch file I am asked for domain credentials and the Deployment wizard is displayed asking for task sequence to be selected.

I believe this error is a result of two things:

1) I applied some windows updates to my mdt server (running on 2008 r2).

2) I was implementing changes to ZTIWindowsUpdate.wsf   which i have now returned to default settings. 

I have also regenerated boot images and re added to WDS.

Any help much appreciated?

Regards,

Paul 

Hi all,

Trying to fully automate the desktop image for my colleagues, but it is having issues after it joins the domain, as it is trying to find the litetouch.wsf file.

• The machine is a Dell OptiPlex 3020
• UEFI bios
• SSD drive
• USB drive plugged in throughout process.
• USB drive is a WD My Passport Ultra 1TB drive.  It was prepped by diskpart (clean, create primary partition, format ntfs, active, assign).
• Patching Machine with WSUS

After it joins the domain (machine is placed in specific OU).  It reboots and once it comes backup it cannot find litetouch.wsf

It appears that the USB drive doesn't appear for 5-10 seconds after logon, and since the machine has solid state drive it may be trying to kick it off too quickly.

The litetouch.wsf shortcut is in the Windows startup, which runs fine after the USB decides to show up.

Is there anyway to fix this?

Thanks,

Chris

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

On the MDT2013 deployment everything is working fine. But after a change lets say a new image to import and after the import make a task sequence. Then thru properties try to edit the unattend there it goes wrong several times now.

When choose edit unattend a error appears after a while:

Non-zero return code from catalog utility, rc = 2002

Cannot create catalog.

I must edit the unattend.xml because there must be the option copyprofile=true in the TS.

The question is where does it goes wrong?
Delete the excisting (Image) operating system in MDT2013 (name.wim)
Import a (Image) operating system in MDT2013
Delete the excisting TS
Create a new TS to deploy the imported image
Try to edit unattend.

If i go to the original image folder there is no .clg file. So have read on the internet to copy the original .clg from the Windows 7 SP1 DVD to the image folder which i want to deploy and naming it the same as the image.wim file but with the extension.clg

After this i open the system image editor and try to open the .clg file but this also reproduce the error...

freddie

On the MDT2013 deployment everything is working fine. But after a change lets say a new image to import and after the import make a task sequence. Then thru properties try to edit the unattend there it goes wrong several times now.

When choose edit unattend a error appears after a while:

Non-zero return code from catalog utility, rc = 2002

Cannot create catalog.

I must edit the unattend.xml because there must be the option copyprofile=true in the TS.

The question is where does it goes wrong?
Delete the excisting (Image) operating system in MDT2013 (name.wim)
Import a (Image) operating system in MDT2013
Delete the excisting TS
Create a new TS to deploy the imported image
Try to edit unattend.

If i go to the original image folder there is no .clg file. So have read on the internet to copy the original .clg from the Windows 7 SP1 DVD to the image folder which i want to deploy and naming it the same as the image.wim file but with the extension.clg

After this i open the system image editor and try to open the .clg file but this also reproduce the error... So deleting the clg and open system image editor and let it create a new catalog works, but every time i import a new task sequence and do above again i must create that catalog file again.

I have made a new deploymentshare and copied all to that new deployment share. However when doiing above again the error by edite unattend.xml creating the catalog is the same.

What can be the cause of this?

freddie

Hi all,

Strange issue. I have created a Windows 7 x64 gold image to be deployed. When creating the image, I allowed Sysprep to rearm Windows. I've deployed about 10 computers in the past week and everything has worked fine.

Yesterday, I deployed another two computers. One works fine, but when I logged into the second one, I was greeted with the you need to activate Windows now screen. I was confused so I ran slmgr /dlv and sure enough my license status was not "Initial Grace Period" but instead "Notification." (by the way, it did show remaining rearms as 2, which is expected since it was rearmed with sysprep when capturing the image, so we know it was in fact rearmed).

So my question is how and why did this happen? I was in a hurry so I just ran slmgr /rearm to burn off another rearm. I plan on putting in a KMS server at the end of the week, but I'm worried if I should redeploy the image to this machine since something appears to be wacky.

Anyone seen this before or have any thoughts on the matter?

I am using the logic to capture the domain address and apply the address in the last task step and I have removed the domain join from the answer file.  The 64-bit task/image works fine, but the 32-bit task/image fails to join the domain.  The task structures are the same and I have followed the instructions to avoid legal notices here. (http://blogs.msdn.com/b/alex_semi/archive/2009/08/28/avoiding-legan-notice-that-breaks-mdt-autologon.aspx)

Here is the error on the netsetup log for the x86:

When I compare the two netsetup logs, it looks like the ServicePrincialName for the x86 task does not return a full RestrictedKrbHost.  

x86 Results:

03/04/2015 14:24:11:055 ServicePrincipalName = HOST/xx-x-xxxx HOST/ xx-x-xxxx.xxx.lan | | |

03/04/2015 14:24:11:055 unicodePwd = Account exists, resetting password: <SomePassword> | | |

03/04/2015 14:24:11:055 NetpModifyComputerObjectInDs: Attribute values to set: | | |

03/04/2015 14:24:11:055 ServicePrincipalName = RestrictedKrbHost/ xx-x-xxxx.xxx.lan RestrictedKrbHost/xx-x-xxxx | | |

03/04/2015 14:24:11:055 unicodePwd = <SomePassword> | | |

03/04/2015 14:24:11:055 NetpMapGetLdapExtendedError: Parsed [0x2098] from server extended error string: 00002098: SecErr: DSID-03150BB9, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 | | |

03/04/2015 14:24:11:055 NetpModifyComputerObjectInDs: ldap_modify_s failed: 0x32 0x5 | | |

03/04/2015 14:24:11:055 NetpCreateComputerObjectInDs: NetpModifyComputerObjectInDs failed: 0x5 | | | 03/04/2015 14:24:11:055 NetpProvisionComputerAccount: LDAP creation failed: 0x5 | | |

03/04/2015 14:24:11:055 NetpProvisionComputerAccount: Retrying downlevel per options | |

x64 results - this successfully joins the domain

03/04/2015 14:07:47:102 ServicePrincipalName = HOST/xx-x-LAB-30.xxx.lan RestrictedKrbHost/ xx-x-LAB-30.xxx.lan HOST/xx-x-LAB-30 RestrictedKrbHost/xx-x-LAB-30 | | |

03/04/2015 14:07:47:102 unicodePwd = <SomePassword> | | |

03/04/2015 14:07:47:102 NetpModifyComputerObjectInDs: Computer Object already exists in OU: | | | 03/04/2015 14:07:47:102 objectClass = top person organizationalPerson user computer | | |

03/04/2015 14:07:47:102 SamAccountName = xx-x-LAB-30$ | | |

03/04/2015 14:07:47:102 userAccountControl = 0x1000 | | |

03/04/2015 14:07:47:102 DnsHostName = xx-x-LAB-30.xxx.lan | | |

03/04/2015 14:07:47:102 ServicePrincipalName = RestrictedKrbHost/xx-x-LAB-30 HOST/xx-x-LAB-30 RestrictedKrbHost/ xx-x-LAB-30.xxx.lan HOST/ xx-x-LAB-30.xxx.lan | | |

03/04/2015 14:07:47:102 unicodePwd = Account exists, resetting password: <SomePassword> | | |

03/04/2015 14:07:47:102 NetpModifyComputerObjectInDs: Attribute values to set: | | |

03/04/2015 14:07:47:102 unicodePwd = <SomePassword> | | |

03/04/2015 14:07:47:180 NetpModifyComputerObjectInDs: Toggled UserAccountControl successfully | | |

Thanks!

Hello,

when i try to deploy a VM using WDS/MDT the startup for contacting the WDS-server is very slow :

The WDS-server is a Server2012R2 (not preview)-server. 

I have reinstalled WDS already but nothing will help.

Anybody with a solution?

Thx

Hi. WDS role and my deployment share are on my Windows server 2012. MDT is installed on my Windows 7 32 bit technician computer since i have to deploy Windows XP 32 bit. To enable multicast i typed the command :"wdsutil.exe /new-namespace /friendlyname:"BDD Share Deploy$" /server:remote_server /namespace:"Deploy$" /contentprovider:WDS /configstring:"deploy_share_path" /namespacetype:AutoCast" on my server (with of course the correct modifications). In WDS i can see that the "BDD Share Deploys" has been created. But multicast is not working... so i did open a command prompt in Winpe and tried to download manually a wim file from my deployment share and it is working, the client appeared on my server with downloading speed and everything. So i don't know how to solve my problem. Here is my LTIApply.log                  <![LOG[------  Applying Windows image using ImageX.exe ------]LOG]!><time="10:28:15.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI applying image \\srv-wds\mdt$\deployment\Operating Systems\W7X64\W7X64.wim using ImageX]LOG]!><time="10:28:15.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\srv-wds\mdt$\deployment\Operating Systems\W7X64]LOG]!><time="10:28:15.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer to directory: W:\MININT\deployment\Operating Systems\W7X64]LOG]!><time="10:28:15.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="10:28:15.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1932)]LOG]!><time="10:28:15.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console >
]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Transfer Started.
]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console >
]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Transfer Complete [0xC1210105].
]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[  Console > Transfer Failed. [0xC1210105].]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = -1054801659]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer could not be completed, rc = -1054801659, falling back to using \\srv-wds\mdt$\deployment\Operating Systems\W7X64\W7X64.wim]LOG]!><time="10:28:16.000+000" date="03-08-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">

hi. i am running the deployment workbench on a windows 7 32 bit operating system. i need to deploy windows xp 32 bit. my deployment share is on my windows server 2012 with wds enable. on my windows 7 computer i checked the box for enabling multicast and write the local path d:\mdt\deployment. question is : do i have to install the deployment workbench 64 bit and aik 64 bit on the windows server or not ?. thanx

We have a new laptop model E5550. Downloaded the driver cabinet with all the model drivers from Dell.

First problem was that the WDS boot did not recognized the network driver, so after searching i came to a link to the Intel website and downloaded a new driver from the Intel site. At last the driver was exepted on the client with Windows 7 Pro.

Then when i deployed a client with MDT2013 and restarted Windows a lot of drivers from the Dell cabinet did not recognize with the client a lot of yellow excimation marks in Windows.

So i downloaded a new cabinet from another Dell website still the same.

Can it be that there are a lot of wrong drivers in the cabinet or is this due to MDT2013? 

When i select the problem devices on the client and point out to the drivers in the cabinet Windows excepts it and the driver is installed....

freddie

Hi,

We've been using MDT 2010, 2011 and 2013 deploying a couple of masters on 700 computers for 3 years.

Up to now we used to deploy 32 bits masters as our computers were only used with business softwares and were a little bit old (5 or 6 years old, but enough for Windows 7, with a Core 2 Duo and 3 Gb of RAM).

We've installed MDT using applications, operating systems (Windows 7 SP 1 Ent 32 bits), Dell packaged drivers cabs (Dell models : OptiPlex 330, 380, 745, 755, 760, 9010, 9020, 3010, 3020, and HP4540 laptops), 15 tasks sequences and all is based on our DATABASE deployment to automate the operations.

We're also using WDS with a couple of Lite Touch Windows PE x86 images.

As said above everyhthing is working nice.

But lately, we've been asked to master more and more 64 bits computers for some dedicated users, and this will probably increase !

Obviously, we want to anticipate and we set about to generate a 64 bit master !

To do so, as usual, the Windows 7 64 bits Wim image was imported, we have created a dedicated capture task sequence, we have checked the option to generate x86 AND x64 Win PE boot images, ticked the options to generate LiteTouch Windows PE x64 images, selected the "Drivers WinPE" selection profile in drivers and patches tab, we have updated MDT to generate it, we've imported the WinPE image in WDS, we've disabled the x86 image, we have manually installed a computer (OptiPlex 3020), applied all the Microsoft Windows Updates, removed our second partitions so that only one was left, we have removed the additional profile to leave Adminstrator only with no password, and obviously, the computer has not been added to our domain !.

When the capture process is starting to connect to our deploymentshare with the same account as the one used to log on to our MDT server, everything is fine till the end of the sysprep process (we start as usual the Litetouch.vbs script), but when the computer reboots, the MDT blue screen is displayed, a few seconds later the DOS window pop-up and nothing else happens !

No error, no message, no possibility to get any log apparently.

I did the same thing with an older computer, an Opitplex 745 but with the same issue !

I tested again with a new 32 bits capture, it's working fine...

We searched Internet but didn't find anything relevant up to now.

However I was thinking about something and I'm not quite sure : taking a look at MDT components, only the WAIK x86 is installed.
Is the 64 bits which is diownloadable through the interface, necessary when MDT is broadcasting 32 AND 64 bits masters, or not ?

I feel lost !

Thanks in advance for your help or suggestions !

Philippe.