MDT 2012 - Deployment of Win 7 Enterprise - Sysprep hanging in capture phase

April 7, 2016, 12:26 am

≫ Next: Apply Image not showing percentage

≪ Previous: How to run a Powershell script visibly to debug

$

0

0

I deployed a new reference machine (HP Elitebook 840 G3) with a standard Task Sequence and cusomized it (Windows Update, Desktop Settings etc.). Then i created a Sysprep and Capture Task sequence and tried to capture the customized image.

I executed the LiteTouch.wsf Script directly on the reference machine.

As for now the machine is hanging for 15 hours in the Sysprep Phase, Step "Processing generalize phase Sysprep plugins".

Is there any way to debug this process? I can't find any errors in the c:\windows\temp\DeploymentLogs Files

The setuperr.log file is clear (C:\windows\system32\sysprep\panther).

---

Apply Image not showing percentage

July 28, 2016, 3:39 am

≫ Next: Select deployment server from WinPE boot image

≪ Previous: MDT 2012 - Deployment of Win 7 Enterprise - Sysprep hanging in capture phase

$

0

0

Hi All,

We have a strange problem with our MDT machine. When it gets to the "Install Operating System: Applying Image" it doesn't show the progress bar or the percent, it just shows "Applying Image" then when its done it goes straight to "Applying image with DISM".

We have x2 MDT machines and its only happening on 1, and appears to be all Task Sequences.

Any suggestions please?

Regards,

Kevin

Select deployment server from WinPE boot image

July 1, 2016, 2:39 am

≫ Next: MDT 2013 Update 1- Selection Profiles: "Folders" window doesn't show content

≪ Previous: Apply Image not showing percentage

$

0

0

We have multiple MDT servers spread across many sites around europe.

We create all MDT deployment task sequences etc at a central site in the UK, then push them out to the multiple sites who then have to put the WinPE image on their local PXE server.

We are in the process of changing how the PXE servers are managed and would like to create a WinPE image in the UK and push it out to all the PXE servers across Europe.

But when the image boots it tries to connect to the UK server and not the local one, is there a way to add an option so that they can select their local MDT server?

MDT 2013 Update 1- Selection Profiles: "Folders" window doesn't show content

July 28, 2016, 9:08 am

≫ Next: Manually select locale

≪ Previous: Select deployment server from WinPE boot image

$

0

0

I have created several OS images and task sequences in my MDT 2013 Update 1 deployment share.  I have updated the deployment share after I created each one.  My deployments work fine...

When I try to create a selection profile and I get to the "Folders" window, none of my images or task sequences are displayed.  I cannot expand the "Operating Systems" or "Task Sequences" node in the window.  If I click the little "+" sign next to them, nothing is displayed.

Any ideas what might be wrong?

Thanks! 

FP

Manually select locale

July 28, 2016, 5:18 am

≫ Next: Error while reverting back from WINPE 4 to WINPE 3

≪ Previous: MDT 2013 Update 1- Selection Profiles: "Folders" window doesn't show content

$

0

0

I'm using MDT 2013 Update 2 and ADK 10

I'm trying to get the deployment wizard to prompt the user for things like keyboard layout and timezone.

I've changed the entries in the customsettings.ini to not skip them but the options don't appear as part of the wizard.

I have searched the net for answers, can find plenty of entries on how to automate this but not how to set it up manually.

I'm missing something probably obvious, someone point it out to me :D

Error while reverting back from WINPE 4 to WINPE 3

December 31, 2012, 4:37 am

≫ Next: Disabling Windows Defender as a Task Sequence

≪ Previous: Manually select locale

$

0

0

Hello,

while having problems with WINPE4 i revert back to WINPE3.

When starting the WINPE-part of MDT i get the following error:

Could not find a part of the path 'C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs'.

How can i fix/return to a working setup using WINPE 3?

Thx

Disabling Windows Defender as a Task Sequence

May 31, 2015, 11:36 pm

≫ Next: Lenovo M73 - Deployment Failing Missing NIC

≪ Previous: Error while reverting back from WINPE 4 to WINPE 3

$

0

0

Can this be done via a Task Sequence rather from within an image?

Lenovo M73 - Deployment Failing Missing NIC

July 28, 2016, 12:02 pm

≫ Next: MDT 2013 - "Dirty Environment Found"

≪ Previous: Disabling Windows Defender as a Task Sequence

$

0

0

Hi, I am trying to image a Lenovo M73 desktop computer and the image continuously fails with the attached. I've removed all other network drivers only leaving the (1) with the correct driver from the Lenovo website and also tested on the computer after by installing manually it works fine. This specific driver ID too shows up in the .INF of the file as well. I'm completely lost with this one. 

Missing: pci\ven_10ec&dev_8168&subsys_309817aa&rev_0c

---

MDT 2013 - "Dirty Environment Found"

July 28, 2016, 12:30 pm

≫ Next: MDT Deployment Overlay

≪ Previous: Lenovo M73 - Deployment Failing Missing NIC

$

0

0

Everytime I deploy an image it gets deploy but doesn't complete all task........during the process there is one auto reboot and that's where my issue begins. After reboot tasksequence doesn't come back to write "computername" nor it install any apps that I have on my MDT server. Also it leaves a "MINIIT" and "_SMSTaskSequence" folder because of that I am getting "Dirty environment found" error...."FYI...I am using custom wim file to deploy an image.

Please help to fix this issue.

MDT Deployment Overlay

July 28, 2016, 4:19 pm

≫ Next: Can I show the location path in the MDT Wizard on the User Data section?

≪ Previous: MDT 2013 - "Dirty Environment Found"

$

0

0

MDT deployment appears to only be capable of establishing a new image.  Question is can the existing deployed image be updated without having to re-image the target box.    

Can I show the location path in the MDT Wizard on the User Data section?

March 27, 2013, 11:01 am

≫ Next: Windows 10 Enterprise (x64) freezing during sysprep

≪ Previous: MDT Deployment Overlay

$

0

0

So I'm using the following in my CustomSettings.ini to specify where SMT.MIG files are transferred during deployments:

; USMT Backup Settings:
SkipUserData=NO
UseDataLocation=NETWORK
UDShare=\\%MDTServer%\MDTUserData$
UDDir=%OSDComputerName%

It works great; with one caveat. The path specified in CS.ini does not show up in the "Location" section of the Wizard when my Helpdesk team reaches that step. Is there any way to populate that "Location" field (maybe with another CS.ini variable) so they can actually *see* the path where the USMT files will go during a deployment? The field is question is circled in red in the screenshot below:

Any help/advice would be appreciated, thanks!

Windows 10 Enterprise (x64) freezing during sysprep

January 20, 2016, 2:56 pm

≫ Next: W7 deployment to a PC with more than one HDD connected fails

≪ Previous: Can I show the location path in the MDT Wizard on the User Data section?

$

0

0

I  recently updated my MDT to Update 1 in order to start experimenting with a Windows 10 image however the following happens:

Windows 10 Enterprise base .wim installs. Goes to capture and on the 'Processing generalize phase SysPrep plugins' the capture just freezes. No idea what is happening and there is nothing in the logs. Simply frozen.

So I installed U2 to see if that fixed it. Nothing. Still freezes.

This is with my MDTBuild share. My MDTDeploy share works fine and deploys our Win7 image without issues.
I am using HyperV 2012r2 to create the image so can delete and start again, but this is the third time the crash has happened.

Has this happened to anyone else?

Gareth

W7 deployment to a PC with more than one HDD connected fails

June 14, 2012, 11:49 pm

≫ Next: MDT Error 1602 during deployment

≪ Previous: Windows 10 Enterprise (x64) freezing during sysprep

$

0

0

Hi, i'm deploying W7 witn MDT 2010 update1. All works weel if PC has only one physical drive connected. Bu if it has more, i'm getting error RC=31 - setup failed to apply image. I'm using setup.exe to install OS. It is specified to install OS to disk 0 partition 1.

setuperrt.log says

2012-06-14 18:00:36, Error      [0x0606c8] IBS    CallBack_ValidateAndPrepareInstallSystem:Action would result in UI prompt, and this is an unattended run.
2012-06-14 18:00:36, Error      [0x060549] IBS    Install drive does not meet requirements for installation[gle=0x00000057]

As i can see in setupact.log, for some reason setup.exe thinks, that disk 0 is not botable and OS can't be erinstalled in to it. Any thoughts, what i've done wrong?

2012-06-14 18:00:36, Info                  IBSLIB DiskRegionSupportsCapability:Disk [0] is WARNED against capability [CanBeSystemVolume] for the following reasons...
2012-06-14 18:00:36, Info                  IBSLIB LogReasons: [WARNING reason for disk 0: CanBeSystemVolume] This computer's hardware may not support booting to this disk. Ensure that the disk's controller is enabled in the computer's BIOS menu.
2012-06-14 18:00:36, Info                  IBSLIB CanBeSystemVolume: Volume at disk [1] offset [0x0] doesn't meet criteria for system volumes...
2012-06-14 18:00:36, Info                  IBSLIB DiskRegionSupportsCapability:Disk [1] is BLOCKED against capability [CanBeSystemVolume] for the following reasons...
2012-06-14 18:00:36, Info                  IBSLIB LogReasons: [BLOCKING reason for disk 1: CanBeSystemVolume] The selected disk is not the computer's boot disk.
2012-06-14 18:00:36, Info                  IBSLIB CanBeSystemVolume: Volume at disk [2] offset [0x0] doesn't meet criteria for system volumes...
2012-06-14 18:00:36, Info                  IBSLIB DiskRegionSupportsCapability:Disk [2] is BLOCKED against capability [CanBeSystemVolume] for the following reasons...
2012-06-14 18:00:36, Info                  IBSLIB LogReasons: [BLOCKING reason for disk 2: CanBeSystemVolume] The selected disk is not the computer's boot disk.
2012-06-14 18:00:36, Info                  IBSLIB CanBeSystemVolume gave us a boot disk,  disk number = [3]; partition offset = [0x0]
2012-06-14 18:00:36, Info                  IBSLIB Remedy was applied for said disk rule
2012-06-14 18:00:36, Info       [0x06021a] IBS    CallBack_ValidateAndPrepareInstallSystem:Could not find a system volume. RemedyPlugin returned possible options
2012-06-14 18:00:36, Info                  IBS    CallBack_ValidateAndPrepareInstallSystem:Was able to pick a suitable candidate for new system volume
2012-06-14 18:00:36, Error      [0x0606c8] IBS    CallBack_ValidateAndPrepareInstallSystem:Action would result in UI prompt, and this is an unattended run.
2012-06-14 18:00:36, Info                  IBS    InstallDestinationMeetsRequirements: Unable to find/create system volume or system volume doesn't meet criteria for installation; hr = 0x80300015
2012-06-14 18:00:36, Error      [0x060549] IBS    Install drive does not meet requirements for installation[gle=0x00000057]
2012-06-14 18:00:36, Info                  IBS    There was a failure applying the ImageInstall/OSImage/InstallTo unattend settings (or WillShowUI=Always).  Setup will display the UI to select an image install destination.
2012-06-14 18:00:36, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information.]
2012-06-14 18:00:36, Info                         This installation is blocked from completing due to compliance failures or invalid input; this is not an internal error.

MDT Error 1602 during deployment

July 29, 2016, 10:02 am

≫ Next: Error when importing Operating System into MDT 2013 Update 1

≪ Previous: W7 deployment to a PC with more than one HDD connected fails

$

0

0

Hello

I am deploying Dell control Vault driver via command line in MDT.

the driver runs fine with no error if I run it on a Laptop from command prompt, but it errors out while same command is being deployed via MDT. Here is the log that shows the error:

Error when importing Operating System into MDT 2013 Update 1

November 4, 2015, 9:44 pm

≫ Next: Whenever I edit the unattend the deployment never finishes.

≪ Previous: MDT Error 1602 during deployment

$

0

0

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!

---

Whenever I edit the unattend the deployment never finishes.

July 29, 2016, 10:55 am

≫ Next: MDT not finishing just a blank Wizard.hta screen

≪ Previous: Error when importing Operating System into MDT 2013 Update 1

$

0

0

Hi folks.  So I've been trying to remove the administrator account from being activated and have gotten great information about that but can't get the task sequence to finish after doing so.  The details of that thread are here (Link). 

Basically whenever I edit the unattend.xml from the OS tab of the task sequence, the sequence never finishes.  The OS installs fine, then reboots me to the desktop and just sits there.  No windows of any kind show any errors of that the sequence has completed.  I'm not sure what the issue is so I'm trying to figure that out.  I'm editing the Unattend as follows from the information I was given in the above link but I haven't heard back from the person that was helping me through all that so I'm creating this thread.  This is what I've done:

Edit the Unattend, look at #4, Specialize, and amd64_Microsoft-Windows-Deployment_neutral. In the sub-folder, the first one should be Order #1 - EnableAdmin. I remove that, but then I tell the unattend to sign on as my other account, 999 times, and I enter its password. I do that in #7, OOBE, Shell-Setup, AutoLogon. At the very last step, UserAccounts, you can still add the administrator password even if you never activate that account.

Not sure what to do at this point as I can't get the sequence to finish. Help very much appreciated.  Thanks.

MDT not finishing just a blank Wizard.hta screen

June 1, 2016, 3:08 pm

≫ Next: Office 365 Office Pro Plus install - Can I just use VLSC Office bits to deploy with MDT?

≪ Previous: Whenever I edit the unattend the deployment never finishes.

$

0

0

I am using MDT to deploy a Windows 10 image to a Dell latitude 5570. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty. Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta. It deletes c:\MININT folder so cannot get the BDD.log or the task sequence log.

• Deploying windows 7 works just fine.
• The version of MDT is 2013 Update 2

Office 365 Office Pro Plus install - Can I just use VLSC Office bits to deploy with MDT?

July 30, 2016, 6:14 am

≫ Next: MDT Slow Rule Processing on Win10 Client Hyper-V

≪ Previous: MDT not finishing just a blank Wizard.hta screen

$

0

0

Hi folks.  Some of the deployments I do use the Office from VLSC licensing and others use Office 365 Office suite via 365 subscription.  Do I just use the download from VLSC for Office 2013 and 2016 for this?

MDT Slow Rule Processing on Win10 Client Hyper-V

August 1, 2016, 6:14 am

≫ Next: MDT 2013 Update 2 - Very Slow

≪ Previous: Office 365 Office Pro Plus install - Can I just use VLSC Office bits to deploy with MDT?

$

0

0

I have an MDT share that I use to build up a lab of Hyper-V VMs.  Everything is contained locally on the Hyper-V server.

When I run this on a Server 2012 R2 box with Hyper-V after I enter my credentials into the MDT logon page the CustomSettings rules are immediately processed and the MDT wizard continues.

I'm trying to do the same on a laptop running Windows 10 Pro with Client Hyper-V and it just isn't working.

After I enter my credentials it's like MDT just went out to lunch.  It's been 20 minutes and the BDD log hasn't been updated.  The last entry was "About to run command: MSHTA.exe \\computername\share\scripts\Wizard.hta /definition:Deploywiz_Definition.ENU.xml"

There's nothing going on though.  No disk activity, no network activity.  It's like it just went off and gave up.

This exact same setup works flawlessly when run on a 2012 R2 server.

Anyone else see similar problems running on Client Hyper-V vs. Server Hyper-V?

MDT 2013 Update 2 - Very Slow

August 1, 2016, 9:33 am

≫ Next: Deploying 7 SP1 x64 to NVMe drives resulting in BSOD 0x7B

≪ Previous: MDT Slow Rule Processing on Win10 Client Hyper-V

$

0

0

Ok, we have been using MDT 2K13 for almost 2 years, and we decided to upgrade to update 2 in future preparation for Windows 10. However, now LTI PC's takes twice as long?  Are we the only ones experiencing this?  Is there a solution to resolve this?