My image was working fine. I updated it and captured it then added to MDT. Updated everything and now when I image a pc i get stuck here. I have looked at the unattend and everything is fine. i did not change anything. This is the error that the setuperr.log provides me.

Hello,

We recently created new media for offline deployments and when we began testing we started to see sporadic failures. The deployment would either complete successfully with no errors, or would present an error message and no longer continue the deployment. The error message states that the Windows Scripting Host was unable to run the LTIBootstrap.vbs script with the error "Library not registered." The message would pop up immediately on first launching the newly installed OS, prior to any post-install task sequences. Navigating to the script in question and attempting to manually run, to re-kickoff the deployment, would inevitably fail with the same error.

Some reading led us to try manually registering the Windows Scripting Host libraries

%systemroot%\system32\vbscript.dll

%systemroot%\system32\jscript.dll

%systemroot%\system32\dispex.dll 

%systemroot%\system32\scrobj.dll

%systemroot%\system32\scrrun.dll

%systemroot%\system32\wshext.dll

%systemroot%\system32\wshom.ocx

We were able to manually register all but the last two, we received an error when attempting those. When we manually attempted to execute the LTIBootstrap.vbs we received almost the same error as before, with the only change being that the error in the script was a few lines further along (line 50 rather than 38 I believe).

A second bit of information that we were able to discover is that this error only occurs if we attempt to deploy a 64bit OS using 32bit WinPE media. Deploying our 32bit Windows 7 image using the 32bit media worked every time, and deploying our 64bit Windows 7 image using the 64bit media works every time. Previously, we have not had an issue deploying 64bit images using the 32bit media, and still do so when we deploy an image over the network. The other aspect of this that is so very frustrating is that it only fails about 30% of the time.

Any thoughts on what might be the issue would be appreciated, we have hit a wall here.

Just trying to determine the differences between KB2968599 and KB2978002? Is KB2978002 an updated version of KB2968599 or just a repackaging?

Brian Hoyt

I'm looking for some help here.  I'm using deployment workbench.

I have created a model custom image and created a custom wim file.  I have imported it into deployment workbench with source files in operating systems. 

I have created a task sequence pointing to that operating system.  When I do properties of the task then into the OS info then edit Unattend.xml, it gives me an error of "the specified image file did not contain a resource section". 

In addition, when I try to deploy this image to a computer, it fails.  I get the error:  Make sure the required files are available--setup failed to applying image\\server share...wim rc=31.  I'm wondering if this has to do with the issue above?  And not having an unattend.xml file.

I have deployed this image wim via Windows deployment services successfully.  Now I'm trying to integrate WDS with Deployment Workbench with this image wim and it fails. 

Any pointers would be great.

Rod

I'm doing something wrong, but I can't figure out what.

I've read some great write ups on the subject:

• USMT Custom XML the Free and Easy Way
• USMT 4.0 Custom Sample - Blocking Wallpaper and Theme Migration from Windows Vista and Windows 7
• Blocking Wallpaper Migration with USMT (or: you are a jerk)

and used part of the XML in their example, but the wallpaper, themes and other display customizations are still coming over.  Now I'm trying to use MigXmlHelper.DestinationPriority() but really its just my last ditch effort.

From an elevated command prompt in C:\USMT\amd64\, I'm executing:

scanstate.exe E:\USMTBackup /config:nothemeuiconfig.xml /i:MigApp.xml /i:MigDocs.xml /i:MigUser.xml /i:unconditionalexclusions.xml /i:blockwallpaperandthemev3.xml /i:getlocalpsts.xml /i:inclusions.xml /ui:domain1\user1 /ue:*\* /vsc /c /o /nocompress /localonly /v:13 /l:\\path\to\scanstate.log /progress:\\path\to\scanstate_progress.log /listfiles:\\path\to\scanstate_listfiles.log

The blockwallpaperandthemev3.xml contains:

<?xml version="1.0" encoding="UTF-8"?><migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/blockwallpaperandthemev3"><component type="Documents" context="User"><displayName>Block Wallpaper, Theme and Display Registry Settings</displayName><role role="Data"><rules><unconditionalExclude><objectSet><!-- Blocks wallpaper, themes (which include wallpaper) and other display/visual customizations (DPI, Screen Saver, Window Color & Appearance etc.) in the registry when migrating from Vista, 7 and beyond --><pattern type="Registry">HKCU\Control Panel\Appearance\* [*]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [Pattern]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [TileWallpaper]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [WallPaperStyle]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop\Colors [*]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop\WindowMetrics [*]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers\* [*]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\ThemeManager\* [*]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern></objectSet></unconditionalExclude><merge script="MigXmlHelper.DestinationPriority()"><objectSet><pattern type="Registry">HKCU\Control Panel\Appearance\* [*]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [Pattern]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [TileWallpaper]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [WallPaperStyle]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop\Colors [*]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop\WindowMetrics [*]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers\* [*]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\ThemeManager\* [*]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern></objectSet></merge></rules></role></component><!-- This component blocks wallpaper & screen saver files --><component type="Documents" context="User"><displayName>Block Wallpapers and Theme Files</displayName><role role="Data"><rules><unconditionalExclude><objectSet><content filter="MigXmlHelper.ExtractSingleFile(NULL, NULL)"><objectSet><pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern></objectSet></content></objectSet></unconditionalExclude><merge script="MigXmlHelper.DestinationPriority()"><objectSet><content filter="MigXmlHelper.ExtractSingleFile(NULL, NULL)"><objectSet><pattern type="Registry">HKCU\Control Panel\Desktop [SCRNSAVE.EXE]</pattern><pattern type="Registry">HKCU\Control Panel\Desktop [WallPaper]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Internet Explorer\Desktop\General [WallpaperSource]</pattern><pattern type="Registry">HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\* [*]</pattern></objectSet></content></objectSet></merge><unconditionalExclude><objectSet><pattern type="File">%CSIDL_LOCAL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern><pattern type="File">%CSIDL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern><pattern type="File">%CSIDL_WINDOWS%\Resources\Ease of Access Themes\* [*]</pattern><pattern type="File">%CSIDL_WINDOWS%\Resources\Themes\* [*]</pattern><pattern type="File">%CSIDL_WINDOWS%\Web\Wallpaper\* [*]</pattern></objectSet></unconditionalExclude><merge script="MigXmlHelper.DestinationPriority()"><objectSet><pattern type="File">%CSIDL_LOCAL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern><pattern type="File">%CSIDL_APPDATA%\Microsoft\Windows\Themes\* [*]</pattern><pattern type="File">%CSIDL_WINDOWS%\Resources\Ease of Access Themes\* [*]</pattern><pattern type="File">%CSIDL_WINDOWS%\Resources\Themes\* [*]</pattern><pattern type="File">%CSIDL_WINDOWS%\Web\Wallpaper\* [*]</pattern></objectSet></merge><unconditionalExclude><objectSet><script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Local\Microsoft\Windows\Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Roaming\Microsoft\Windows\Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Ease of Access Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Web\Wallpaper\* [*]","Fixed")</script></objectSet></unconditionalExclude><merge script="MigXmlHelper.DestinationPriority()"><objectSet><script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Local\Microsoft\Windows\Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Users\*\AppData\Roaming\Microsoft\Windows\Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Ease of Access Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Resources\Themes\* [*]","Fixed")</script><script>MigXmlHelper.GenerateDrivePatterns ("\Windows\Web\Wallpaper\* [*]","Fixed")</script></objectSet></merge></rules></role></component></migration>

I generated a config.xml called nothemeuiconfig.xml and changed this:

<component displayname="Microsoft-Windows-themeui" migrate="yes" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-themeui/microsoft-windows-themeui/settings"/>

To this:

<component displayname="Microsoft-Windows-themeui" migrate="no" ID="http://www.microsoft.com/migration/1.0/migxmlext/cmi/microsoft-windows-themeui/microsoft-windows-themeui/settings"/>

But themes, wallpapers - everything - still come over.

Opened a case with Microsoft, sent them:

• the XML's I'm using
• the command I used to generate the config.xml
• the command I used for scanstate
• the log files generated by scanstate
• the command I used for loadstate
• the log files generated by loadstate

They claim I'm doing everything right, and the logs indicate Microsoft-Windows-shmig is the one responsible for carrying this over, not Microsoft-Windows-themeui.  Their answer is to disable Microsoft-Windows-shmig, but Ned Pyle's post says NOT to do that.  Microsoft Support claims the blogs I linked them (above) cannot be relied upon as they were written for older versions of USMT.

Is this no longer possible or am I just doing it wrong?

How can we set the deployment profile to have no startup sounds?

I've tried toggling mute, but it is not reliable because we many different models and some of them install drivers or audio applications during the deployment that end up toggling the sound back on at various places during task sequence and we would have to add another toggle mute command at a different point in the TS which would then toggle unmute for other models.  That's too kludgy to manage toggling sound by model.

So, I would rather disable startup sounds rather than trying to "mute" the audio.

Hi,

I am building a task sequence that will include Office 2010 ProPlus (volume license), a bunch of other products (like SQL Server and Visual Studio) and also Visio 2013 and Project 2013.

For Visio 2013 and Project 2013, I have to use the retail media (this is for use in academic computer labs and we have a single retail key through DreamSpark Premium that allows unlimited activations - I don't know why DreamSpark doesn't just give a volume license key).

I managed to get Visio 2013 and Project 2013 to install silently by modifying the config.xml file and using the /config parameter. However, when running my install script (the usual VBScript wrapper) or just from the command line, the command returns before setup finishes (literally within less than a second). Setup continues to run and finishes successfully, but as you can imagine, MDT considers that application install finished and tries to move on to the next application which fails because another installation is still in progress.

I've included below the relevant portion of the VBScript wrapper. Any help in figuring out how to get the wrapper to wait for the installer to finish is appreciated.

sSetupFile = oUtility.ScriptDir & "\Source\setup.exe"
sArguments = "/config vispror.ww\config.xml"

oLogging.CreateEntry oUtility.ScriptName & ": Starting installation", LogTypeInfo

// Check for existence of setup file omitted
// ...

iRetVal = oUtility.RunWithHeartbeat("""" & sSetupFile & """ " & sArguments)

Coincidentally, iRetVal = 0 indicating success.

Thanks,

SA

Hi

I am using MDT 2013 to try to deploy Windows 8.1 images. I have created the Reference Build task sequence and when I run it, the TS completed successfully and a wim file is created. But the Windows Updates events in the TS, although enabled, do not install any updates into the reference build. The TS is using the cmd line csript.exe "%SCRIPTROOT%\ZTIWindowsUpdate.wsf" 

I have added a line to my cs.ini file and put in the correct path to my WSUS server, including the Port number:

WSUSServer=WSUSServer.Domain.local:8530

If I start the completed Ref Build VM, and check the registry, the HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate keys are in place and are correct. If I run Windows Update on the client, I get an 8024A008 error.

I have looked in the ZTIWindowsUpdate.log file and I can see this:

 
FAILURE (Err) -2147012890 x80072EE6 Windows Update, Search for updates
Restore NoAutoUpdateKey to <empty>
ZTI ERROR - Non-zero return code by ZTIWindowsUpdate rc = 1

If I run a cmd prompt within the reference computer, and connect to the deployroot\scripts folder, and run ZTIWindowsUpdate.wsf it does not run Windows update successfully, and the log file shows the same error as above.

This worked fine under Windows 8 and Windows 7, when I prepared the deployments of those Operating Systems. As far as I can tell, WSUS is working OK. The Updates are approved and downloaded. The SoftwareDistribution.log file on the WSUS Server looks OK.

MDT is version 6.2.5019.0 running on Windows Server 2012.Please can anyone advise on how to get updates deploying as part of the TS, so that I do not need to do anything manually within the TS.

Many Thanks

John

Regards, John

I'm trying to install MSMQ role as part of the OS deployment task sequence on windows 7. I have added a "roles and features" step in the State Restore section of the MDT/SCCM task sequence and checked the "Directory Services Integration" feature. All looks well in the logging but MSMQ is not installed during the OS deployment task sequence. Is it supported to install MSMQ on windows 7 when using MDT/SCCM task sequences?

this is from the SMSTS.log

Microsoft Deployment Toolkit version: 5.1.1642.01 InstallSoftwareThe task sequencer log is located at C:\Windows\system32\CCM\Logs\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. InstallSoftware 

No roles were requested. InstallSoftware )
No role services were requested. InstallSoftware 

Features requested for installation: InstallSoftware 
  MSMQ InstallSoftware 

  MSMQ-Services InstallSoftware 
  MSMQ-Directory InstallSoftware 
Preparing to install roles for Windows 7 client using DISM tool InstallSoftware 

Role installation complete. InstallSoftware 
ZTIOSRole processing completed successfully. InstallSoftware 

Command line returned 0 InstallSoftware

Process completed with exit code 0 TSManager

Successfully complete the action (Install Roles and Features) with the exit win32 code 0

I have had a look in the DISM.log file but there is nothing related to MSMQ, Anyone got this working? I'm using SCCM 2007 R2 MDT 2010 Update 1

Louis

I'm trying to create a Windows 7 Embedded image that can be deployed to multiple computers. I'm new to this so please be gentle. Here is the process:

• Used Image Configuration Editor to create my base image that is bootable from a USB stick.
• Installed the image on my embedded device.
• At the point where it asks me to create a user, I press Shift+Ctrl+F3 to boot in as an Admin.
• I make all my changes to the image.
• I run sysprep /generalize /oobe /shutdown
• For testing, I would then reboot the computer

My problem is that after running sysprep the computer wont boot. The error Status is 0xc000000F and Info is "Windows failed to load because the system registry file is missing, or corrupt"

At first I though it might be a driver that I was installing after booting into the Admin mode, so I didn't install anything and just ran sysprep - same error.

Does anyone have an idea what could be going wrong?

Thanks!

I'm seeing an issue where the first time a domain account logs into a system running Windows 8.1, it takes a very long time (up to 15 minutes) to go through the "Setting things up for you" and "Installing apps" screen. 

Has anyone else been having this issue?

I've tried disabling the first run animation, but it didn't make too much of a difference.

Hello,

We are using MDT 2013 to deploy Windows 7x64. We have an automated process to generate our reference images using Powershell and Hyper-V. It works great.

We generate new images once per month, and I would like to know the best way to update the .wims in the deployment share.

Can I just copy the new .wim file into the deployment share with explorer and overwrite the old one? I assume this method will retain the old GUID in the MDT console. Will new deployments just start using this new .wim as soon as it is coped? Do I need to update the deployment share?

Do I need to import a new OS through the MDT console? Doing this I assume will require me to select the new .wim in my task sequence, since the newly imported OS will have a new GUID.

Also, these .wim files are used in our test deployment share before our production share. Can I just copy/paste from one share to the other? What does this do to the OS GUID? Does it get a new one or does it retain the old GUID from the original share?

Appreciate any feedback.

i have a requirement to create a clone of an existing PC to be deployed to destination PCs of the same hardware. The downside is that it needs to be a clone as in it can't be sysprep'd. 

From what i have been reading MDT can't deploy a non-sysprep'd image so i am not going to be able to use it.

My method for doing this is as follows:

Take Clone:

1. Use the MDT boot stick to get to the command prompt

2. Use dism to take a capture to a wim file

3. Copy wim to portable hard drive/network share

Destination PC:

1. Use the MDT boot stick to get to the command prompt

2. Use diskpart to "clean disk" and create partions

3. Use dism to apply captured .wim file to hard drive

Does that sound logical? I did something similar ages ago but not quite the same so i cant remember if i need to add a bcdboot at the end.

I have seen this post: http://blogs.technet.com/b/markrussinovich/archive/2009/11/03/3291024.aspx

Not sure if people had any weird issues where a machine hasnt been sysprep'd.

Any feedback and advice would be appreciated.

I was wondering if it's possible to install MDT 2013 on a standalone Windows 8.1 workstation.

I want to do some testing on a workstation only. This workstation will not connect to a domain or any network shares.

I ran through the default install steps for MDT2013 on the Win 8.1 workstation.

I the deployment share is local. So the workstation is called Test1 and the path to the Deployment share is as follows:

\\test1\deployshare$

I add all necessary items to the containers in MDT.

I point my VM to the x64 Boot ISO. I get hung up at the Deployment Wizard. I'm prompted for UserName, Password and Domain.

The problem is that there's no Domain. I've tried entering in "." for the domain with no success.

Is what I'm trying even possible?

Dr. Chuck

Hi,

I created a winpe vhdx. I'd like to boot from it but bootbcd needs a windows folder in order to add it to the bootmenu.
F.e. bcdboot F:\windows (F: would be the mounted vhd then).

Can it be done?

Please advise.
J.

Jan Hoedt

Hi

I want to do a offline update of our Windows 7 installation image (wim).

I have installed all necessary updates on a reference computer. Afterwards I map the Windows folder of that computer on our MDT 2013 server, and then run the following:
Start /w for /R z:\SoftwareDistribution\Download\ %f in (*.cab) do DISM /image:D:\Mount /add-package /packagepath:%f

The above command seems to work, but I get the following error:
"DISM /image:D:\Mount /add-package /packagepath:z:\SoftwareDistribution\Download\b069666a9627c88af9405a0dfcf9e100\windows6.1-kb2968294-x64-express.cab

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.1.7600.16385

Processing 1 of 1 - Adding package Package_for_KB2968294~31bf3856ad364e35~amd64~~6.1.1.1
[===========================66.1%======                    ]
An error occurred - Package_for_KB2968294 Error: 0x800f0816

Error: 0x800f0816

DISM failed. No operation was performed.
For more information, review the log file.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log"

I have been searching for the solution, and the error seems to be caused by the fact that the Windows installation (the wim image) has a pending restart which is shown because the file C:\Windows\Winsxs\pending.xml is existing.

Is this a known issue?

Lasse

/Lasse

How can i stop my Domain GPO from disabling the local Administrator's login, that MDT uses to deploy Windows.

My 'Unattend.xml' settings for the auto login are correct.

I have heard that i may need to add a setting in my CS.ini file or add an item in my TS. What would be the best and simplest option.

Any help is much appreciated.

Hi, we are in the process of deploying Surface Pro 3s. We are installing our own copy of Windows 8.1 Enterprise. What we are finding is that after the final reboot (I have set the finish action as Reboot) the touchpad settings go missing, however, the mouse settings still remain. This can be found under Mouse and Touchpad options.

I have not made any drastic changes to my unattended.xml file for Windows. I have a feeling that it may be driver related, but it does not make sense that the touchpad options are there before the final reboot.

Any help is much appreciated.

Hi

I have set up DFS-r to replicate my deployment share to remote servers. I have also updated my bootstrap.ini with DefaultGateway settings for each remote server.

How do I manage the setting of the MDT Rule properties under General \ Network (UNC) path?

Typically, this is set to  \\{IP Address of local server}\DeploymentShare$.

If you replicate the deploymentshare and update the WDS boot image, the client build will attempt to use the path of the master server, rather than the local server.

I currently have to go to each remote server and amend the path to the IP address of the local server and then Update and import the boot.wim into WDS.  I'd like to automatically get the client to access the local server.

I have tried using %WDSSERVER% in the path, but this flags up an error.

Thanks for any help in advance.

Mike