I am using MDT 2010 to deploy Windows 7 image. The image deployed fine and before I capture the image, I renamed local administrator account but the captured image reverse back to default administrator account?

Thanks for any help!

Ying

My deployment share is working fine, but when I view my share in an explorer windows, I see about a dozen files that I do not recognize. The files are in the 8.3 format, but there is no rhyme or reason to their names.  A series of 8 random letters/numbers with an extension of 3 more random letters/numbers.  Anyone else see this? Anything I should be concerned about? Ok to delete? Thanks!

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

Summary result of the MS case:

• After much review & scrutiny, the command line and XML files are syntactically correct and rules are sound.
• The articles I referenced in the ticket are indeed old and speak of an older version of USMT, so I can accept the possibility that something may have changed between USMT versions that render those suggested rules & instructions invalid.
• Despite using unconditionalExclude to unconditionally globally exclude objects, something else is trumping that rule, and there’s no way around that.
• Even using MigXmlHelper.DestinationPrioity() won’t help us here because, like above, something else trumps that rule, and there’s no way around that.
• The last proposed suggestion is to disable the shmig component, which may or may not break or otherwise adversely affect the backup/restore of other things.  (This may be too difficult to detect easily or in initial testing and the uncertainty doesn’t give us confidence problems won’t arise as a result of this change.  Also, Ned Pyle's post post says NOT to, but then again that's an old post.)

Hi,

I'm trying to deploy a task sequence from a share which is hosted on a nas (not in a domain).
When it tries to connect to the share it says it needs a domain name but there is none. If I fill in a dummy name the connection fails.

Pls advise.

J.

Jan Hoedt

I want to create a 'portable', offline version of our entire MDT 2013 DeploymentShare and put it on a USB drive that is bootable. Searching the web offers all sorts of options on how to do this. My usb drive is 300 GB and is an actual drive, not a flash drive. It

Most of the web articles suggest to run diskpart and make the USB active. Then copy over everything media generated by MDT 2013. That's where I get stumped.

Do I need everything or can I just copy the LiteTouchMedia.iso over and boot to that?

Can I copy over the Deploy folder and boot to that without LiteTouchMedia.iso?

Is there a difference between a USB stick booting and a USB drive booting?

Thanks much for any help on this.

Orange County District Attorney

After a month of perfect deploying images deployment isnt working anymore. 

when I want to start a deployment via PXEboot it loads Litetouch_x86. when i get at 

this screen processing bootstrap settings

It gets stuck, it just says processing rules. It just stays there.

I looked at the BDD.log and this is what I found:

my bootstrap.ini is like this:

hello, i have two custom pages, one allows the user to pick the site location and the other allows the user to pick the computer model. when i launch the udi preview only the choices from one page are shown on the summary page? how can i fix this

thank you.

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

Summary result of the MS case:

• After much review & scrutiny, the command line and XML files are syntactically correct and rules are sound.
• The articles I referenced in the ticket are indeed old and speak of an older version of USMT, so I can accept the possibility that something may have changed between USMT versions that render those suggested rules & instructions invalid.
• Despite using unconditionalExclude to unconditionally globally exclude objects, something else is trumping that rule, and there’s no way around that.
• Even using MigXmlHelper.DestinationPrioity() won’t help us here because, like above, something else trumps that rule, and there’s no way around that.
• The last proposed suggestion is to disable the shmig component, which may or may not break or otherwise adversely affect the backup/restore of other things.  (This may be too difficult to detect easily or in initial testing and the uncertainty doesn’t give us confidence problems won’t arise as a result of this change.  Also, Ned Pyle's post post says NOT to, but then again that's an old post.)

Hi all,

I have MDT 2013 installed & configured in prod, we are currently using it for the deployment of our prod machines using an USB drive. The USB holds the media file which is created using MDT & then the deployment is done globally. We upload the media to One drive & then our technicians download it. Our problem is, suppose we have build V1 & then we updated the build to V2 in this case currently our technician have to download the entire build which we don't want.

What we are trying to do is the technician only download the changes & then merge the changes with previous build.

Can we achieve this with MDT 2013. Experts please suggest.

Thanks,

Pranay.

Capture process progresses to point of WIM Capture. First time through at 2% (watching this via BDD.log via Trace32) the server being captured randomly rebooted itself. Nothing logged, last entry just saying at 2% captured.

Second attempt was at "Console > Scanning files and directories" and just reboot. I had cmd window open in attempt to stop it rebooting but did anyway. I have configured to copy logs to the deployment server but there is nothing other than what was logged in BDD.log. SMSTS shows nothing at the time, ZTIBackup is just what's in BDD.log (obviously).

So why would it reboot itself randomly during WIM capture?

The server I am capturing is around 60GB HDD, 30GB used. Few applications installed. Am I doing something wrong? Should I not capture a server with various things installed?

Hello All,

I am at present working on developing a Windows ISO using MDT 2013 for Dell Servers. The Image that we use for HP (already working fine) calls for HP SPP (setup file) in a task sequence as an application. And from there SPP itself is smart enough to install necessary drivers, softwares, firmware,etc onto target hardware model from the SPP bundle. 

however in Dell, I dont know if they have something similar to HP SPP. I heard of Dell driver pack and checked that and found that it is for Lifecycle management. and then, i learnt about Dell repository management tool and Dell update package (DUP).

Could anyone please tell me what is best to use in MDT as an application so that it just picks up drivers, firmware, software, etc from the bundle and install it on dell model.

otherwise, i think only option left for me to manually download drivers (as an INF) and make structure folders (total control method) and integrate them in MDT in out of box folder...I know that process...

i am asking if that can be avoided and we have something similary to HP SPP for dell as well which i can run on hardware model....

any information would be really helpful and much appreciated!

Hi all! I recently imaged a server with MDT 2013 and after it booted into Windows one of the applications I configured to install crashed and we ended up with an incomplete deployment. In this case this was fine and we moved on, but now every time a user logs in something is attempting to launch the Litetouch.wsf script. I ran LTICleanup manually and removed the MININT folder, but I continue to get a pop-up at login that Litetouch cannot be found.

I have tried every registry key I am aware of HKCU and HKLM Run and Runonce keys and also checked the startup folders for every user. What is calling Litetouch? How can I stop this from happening? Thanks!

I have two unique Deployment shares as I have separated my Deployment shares by OS, as such I have a Windows 7 DS, and a Windows 8.1 DS. The reason behind this is shear size for the number of models I have to support, it would bloat the image over the 15GB mark it sits today.

That all being said what I am attempting to do is utilize a single database as it all houses the proper site information (all 500+ locations), however the issue I am running into is with the fact that if I have an Application bundle in my Windows 7 DS with dependencies, and I go add the Bundle for the machine to the database in my Windows 8 DS then it overwrites the database information completely and I lose the capability to install the app bundle in my Win7 deployment.

I do understand that if I had both OS within a single DS and had multiple TS for the OS deployment and all the bundles created by OS version and utilized the logic to only install on specific OS version I could get this to work rather easily but as stated above I support over 40 Models of PC in my windows 7 image and cannot add to its size as it is already a hassle to distribute.

Any help or suggestions would be appreciated.

I am trying to get WDT 2013 setup and running. I followed the Lite Touch Deployment steps in the help file, but it never asks about capturing the reference image. I have replicated the steps as closely as I could, following what the help file lays out for the Lite Touch Deployment option. I am able to import the OS, (Windows 7 Pro SP1 x64 in my case), Setup the Task Sequence, update the deployment and boot from the ISO that is created. However the Task sequence never asks if I want to capture the image after the deployment is finished.

I am not sure what I am doing wrong or how to enable the capture portion of the Task Sequence. Any ideas? -Dave

Hello Guys,

First of I want to say that i am not an expert in this and merely taking over for someone who left the company.

I am moving the image deployment from network to USB.

I was able to create a bootable USB, and migrate the settings as well.
However a few of the steps which run after the WIM install call for batch files to run.

One calls for a Proxy activation, and a few call for .exe to install because it was too complicated to have those apps as actual steps.

Inititally the batch files were just called from the \\ XXXMDT\deploymentshare$\ folder, but now i need to have them run directly from the USB, and cant figure out how to do it.

For example,

I have changed the entry in the control\ts.xml file to  <action>cmd.exe /f %systemroot%\proxy.bat</action>

F is because the USB maps as the F:\ and the proxy.bat now resides in the root of the USB stick, but the deployment process just ends up sitting at that step.

Any help would be appreciated.

Thanks, Paul

Hello,

I have a problem with my deployment tasks. All of them are stopping at 58%, and when i look at the computer, i have to log on which is not normal, the deployment have to logon automatically and finish itself.

I already search for a similar problem and i found something that says that it's probably a connectivity problem. I double checked this but to no avail.

Someone got an idea ?

Thanks for your help!

Chiddy

In our environment Linux PXE is being used to deploy Linux as well as Windows Servers. I have recently evaluated & demonstrated the power of WDS & MDT to my superiors. They have asked me to go ahead & implement in the production network but it should not break the existing deployment method.

The WDS is only being used for Network Boot (PXE). I have configured the options 66 & 67 appropriately for Windows Servers in DHCP. For Linux clients the default options for 66 & 67 point to Linux PXE & pxelinux.0

But when a linux client needs to be deployed it always boots from WDS (I believe WDS broadcasts itself) & downloads WDSNBP

Is there a way to disable the WDS broadcast itself.

Sid.

does MDT Team plan a update for Windows 10?

Error's durring Setup - (Import Windows 10 from ISO, Standard tasksequence)

Chris