I have upgraded from MDT 2010 to MDT 2012.  After the upgrade, the PC's continue to work fine, the tools folder exists, and the install of applications occurs without a hitch.  The Dual Boot Macs are a completley different story though.  The install goes fine, but the Tools folder does NOT get copied to the machine and the computer errors out after the install of Windows during it's first boot into Windows when it logs in.

Here are the errors in LiteTouch.Log

<![LOG[Property ResourceDrive is now = C:]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ResourceDrive = C:]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FindFile: The file TsmBootstrap.exe could not be found in any standard locations.]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FAILURE ( 5208 ): Unable to find the SMS Task Sequencer.  The deployment will not proceed.]LOG]!><time="13:19:35.000+000" date="05-30-2012" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">

Here are a few of the errors out of BDD.Log

<![LOG[FindFile: The file TsmBootstrap.exe could not be found in any standard locations.]LOG]!><time="13:19:13.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[FAILURE ( 5208 ): Unable to find the SMS Task Sequencer.  The deployment will not proceed.]LOG]!><time="13:19:35.000+000" date="05-30-2012" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.0.2223.0]LOG]!><time="13:20:06.000+000" date="05-30-2012" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">

Again, it works on our NON-MAC computers, but ONLY fails on Dual Boot Mac's.  It seems to be related to the Tools folder and it not being there, and the install of the actual OS works fine.

Matthew

I haven’t been able to find much info on this so I thought I would try here and see if anyone can help. We’ve been using MDT 2010 for the last couple of years to install Windows 7 on Macintosh’s running Bootcamp and it’s been working fine. We recently upgraded to MDT 2012 and the same process we used to use for this does not work anymore and I would like to find out how to make it work on 2012. Here’s how the process works: 

First, setup Bootcamp on the Mac.  This creates another partition on the Mac for the Windows OS (partition 3 for MAC OS 10.6 and lower, partition 4 for OS 10.7 Lion because of the recovery partition). Unfortunately Bootcamp cannot create NTFS partitions so it formats it as FAT32.

We then create a standard client task sequence using MDT and the Windows 7 source files (not a custom image) and give it a name to make it obvious it’s for Mac’s – “Windows 7 for Macintosh running Bootcamp”. We edit that task sequence and disable the built in “Format and Partition Disk” step since we don’t need to create the partition, only format it as NTFS. We then create a custom diskpart.txt file called BootCamp_Lion.txt with the following contents:

SELECT DISK 0

SELECT PARTITION 4

FORMAT FS=NTFS QUICK OVERRIDE

We place this file in the “Extra directory to add” location we’ve specified in the Win PE Customization section so it is located on the root of X:\ when it boots into Win PE. We then add a command line to the task sequence:  diskpart.exe /s x:\BootCamp_Lion.txt to format the existing bootcamp partition as NTFS.  Then in the “Install Operating System” step we set it to apply to a specific disk and partition – Disk 0, Partition 4. This installs Windows 7 on the Bootcamp partition and leaves the Mac OS intact and has been working fine in MDT 2010. Now with MDT 2012, the task sequence starts fine, formats the partition, installs Win 7, but when it comes up in the full OS for the first time I get the error “Unable to find the SMS Task Sequencer. The deployment will not proceed.”  And the task sequence stops. I know the partitioning part has changed in 2012 and have read that you can get this error if you deploy to something other than disk 0, partition 1 but I’m wondering if I can accomplish the same thing that I used to have working in 2012. Is there a different way I can do this?  Any help would be appreciated.

Thanks,

Robb

Hi,

I'm using mdt2012u1.

I've captured a windows 8 image after modifying it with the suspend task sequence.

As part of the deployment I'm copying the profile using unattend.xml.

Deploying it happily using MDT and WDS.

All good, except that as part of the deployment, it does what its told, reboots, and then sits there waiting for me to create the an account that I can login with.

From memory task monitor tells me its sitting at 49%.

After I do that, it logs in (metro displays the tiles in the position I've set), does a reboot and finishes and I can login with a domain user.

 Its joined the domain, and the computer account is in the correct OU that my rules have told it to go to.

What am I doing wrong? I really want it to be a fully automated install like my windows 7 images.

P.S. I'm deploying windows 8 enterprise.

P.P.S I've done a little more googling, possibly adding the line SkipUserOobe=TRUE to my deployment rules will work.

Alternatively, the unnattend.xml may allow that setting as well. Not sure at this stage.

Because of the release of the final version of the Windows ADK I installed a new (on Windows Server 2012) based Deployment machine yesterday. Installed MDT 2012 Update 1 and the Windows ADK to support deployments of Windows 8.

I imported my old deployment share so i would be up and running quick. After a regenerated my boot images and tried to deploy Windows 7, something strange happened. When Windows 7 was all installd...it asked my for a productkey. Something I never had on my previos MDT installations. 

To verify the deployment share isn't 'corrupted' I also created a new deployment share in which I only created a task sequence to deploy Windows, from which I also imported sources again. During this deployment i also was asked for a product key during the deployment.

Finally I started my old deployment server (running Windows Server 2008 R2 with MDT 2012 and WAIK), the deployment worked just fine (not asking me for a product key at all).

So the question is, is there still an issue deploying Windows 7 when you're using Windows ADK? The documentation doesn't tell.....

What could be the problem?

If one of these posts answered your question or issue, please click on "Mark as answer".

I roll out dozens of servers a month to VM's on SAN Storage. One big factor is aligning the partitions of the VM's with the clsters on the SAN. Server 2008 and beyond automatically offset t 1024 which will provide aligned storage. However, 2003 and 2003 R2 offset at 28k. I have tried modifying the ztidiskpart file and it seems it won't accept me adding the option: " align=1024" to the diskpart command. I am sure someone has come across this before and I honestly cannot find any information about this topic, so I would welcome some assistance. I have also tried to use the workaround in the Windows PE registry setting for the XP BIOS fix, but it does not seem to work either.

Maybe I am just doing something wrong but here is how I modified the ztidiskpart.wsf script:

DiskPartWrite oExec, "Create Partition Primary align=1024"

I simply added the align statement to to putput, but it fails every time. There are a total of 3 places where I added the align= within the script in the exact same way.

Thanks for your input,

Dan

•  "SPxxxxx.exe is the SoftPaq to unpack
• "-pdf" is a runtime switch that overrides the build parameters
• "-f" is a runtime switch that overrides the default path set at build time
• "-s" instructs the package to unpack in silent mode, skipping the Welcome, License, and Directory screens
• "-e" instructs the package to extract only, that is, do not run the component installation program.
• -s -a -silent -reboot (Good for silent installs.)

I am fairly new to MDT.. I have been running MDT 2012 for 6 months now and we are using ghost and MDT only because i cannot get MDT to capture a computer or do a prompt for computer backup. I can set the customesettings.ini file to move and restore date join a doamin and put the computer name in the correct OU however I cant get MDT to capture once I can grasp that we can finally move away from Ghost all together. I also have linked deployment shares out in some of our regional offices as test boxes.

Can someone take a look please I would greatly appriciate some assistence.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipDeploymentType=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipBDDWelcome=YES
SkipTimeZone=YES
SkipDomainMembership=YES
SkipBitLocker=YES
SkipTaskSequence=NO
SkipLocaleSelection=YES
SkipApplications=YES
SkipComputerBackup=NO
SkipCapture=NO
SkipSummary=YES
UserDatalocation=none
TimeZone=035
TimeZoneName=Eastern Standard Time
UserLocale=en-us
KeyboardLocale=en-us
JoinDomain=*******
MachineObjectOU=ou=Workstations, ou=Main Office, dc=*******, dc=*******
EventService=http://D7MOITDDPLY:9800

Using MDT2012 Update 1 we occassionally get the following message:

Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username.

It is then followed by a warning message:

<Message containing password has been suppressed>

This appears to occur on most of our faster laptops and always right after the mandatory applications are installed.  We have a restart step in our TS and then when the Windows 7 system logs back in to continue the TS we get the above messages.  The TS continues without failure and is able to connect successfully multiple times during the process.  What is annoying is that when we get the final summary screen, it shows yellow because of this one warning that is logged.

Has anyone seen this?  If so, were you able to correct the issue?

Thanks,

Martin

Everytime I look in the ISO created by running Update Media Content, the Operating System folder is empty. I believe I have set everything up correctly, but the OS isn't there. Any ideas, or something I could have missed?

Thanks

Ok - So I know in MDT 2010 if you had FinishAction=REBOOT and SkipFinalSummary=YES set in your customsettings.ini, it would NOT reboot after deployment and ignore the SkipFinalSummary setting; so you could see that there was a failure.

In MDT2012 - I have the same settings, although when there is a failure it does not ignore SkipFinalSummary, and reboots anyway.  I basically want it to NOT reboot and show me the summary if there are failures, and reboot only if everything is successful. 

Is there a way to restore this 2010 functionality in MDT 2012?

Thanks!!

Hi

Environment: Windows server 2008 R2(VM), 2GB RAM, WADK 8, MDT 2012 SP1

When I try to build a boot ISO using either MDT or ImageX, I receive an error when DISM is used to add packages.

Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~6.2.9200.16384
An error occurred - WinPE-HTA-Package Error: 0x80070005

Error: 5

Access is denied.

This repeats for all WINPE packages being added by DISM. 

I have rebuilt the server and reinstalled but the same affect. I have tried running it as admin, editing rights and making the name of the packages lower case but cannot seem to get anywhere. Any help would be great.

We have a central office where MDT2010 is working fine for LTI.  Now we want to extend it to our remote locations with linked deployment shares.  All setup, WDS is in each location for PXE boot and that works fine.  The PC gets the boot.wim from its local WDS ok, reboots and then starts the OS install.  The issue is that the OS install is coming from our central office over the WAN.

In the remote MDT bootstrap.ini file, we declare DeployRoot=\\remote-server\MDTShare$...We've updated/replicated the linked deployment share, and updated the WIM in WDS.  I can open the remote MDT bootstrap.ini and see that it is pointed correctly.  And yet the OS install still comes across the WAN from our central MDT.

So I'm stuck...where else is DeployRoot (or something similar?) defined?  It is not defined in our customsettings.ini.  Could this be hard-coded somewhere in the boot.wim or WDS?  I've looked everywhere I can think to look.

The client's BDD logs clearly show that the PC connects to the right WDS server (its local one), it clearly gets the boot.wim from its local WDS, and then for some reason determines that its DeployRoot is the central site's MDT share instead of its local one. 

Help, please.

I'm using MDT 2012 Update 1 to build, sysprep, and capture a reference image.  For some reason the sysprep is not removingall the drivers.  Specifically it is not removing the AMD 3GIO Filter driver (among others).  When the 3GIO filter driver is included in the reference image, and the image is used on another system, the Intel HD Graphics Family driver reports that it cannont find enough resources (Code 12).

I've manually removed the 3GIO Filter driver from the reference image wim using the DISM /Remove-Driver command, and the reference image will now properly deploy.

I have double checked the Unattend.XML file and the PersistAllDeviceInstalls is set to False, so my understanding is that sysprep should remove all the drivers in the generalize phase.  Is this correct?

My question is "Is there a way to have the sysprep program remove all the drivers from the image that are not "Inbox" drivers". I use the DriverGroup property based on Make and Model to include all the drivers needed to deploy each particular type of computer, so I really don't want any "left over" drivers causing problems, and I don't want to have to manually remove drivers using the DISM /Remove-Drivers command each time I build a reference image.

Hello,

I am having a problem deploying Windows 8 with language packs and adding at the same time a role/feature (netfx3).

What I have done is creating a Standard Client Task Sequence. In the task sequence I have added, in the State Restore phase, the step Install Roles and Features (where only .Net Framework 3.5 is selected). I have configured nothing else !

If I use this task sequence, everything is ok; Windows 8 is well deployed and NetFx3 feature is installed.

Now, if I add one or more language packs in the MDT console and select them when using the previously created task sequence, the deployment fails with one error : ERROR - NetFx3 role processing with DISM.exe failed, rc = -2146498529.
The language packs are well installed but as the error message says, NetFx3 is not installed.

In the ZTIOSRole.log I can find this :
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoles.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoleServices.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  NetFx3]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41003 sent: ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64]LOG]!><time="12:55:04.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Already connected to server HPZ820 as that is where this script is running from.]LOG]!><time="12:55:05.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64\sources\sxs]LOG]!><time="12:55:05.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to execute command: cmd.exe /c C:\windows\system32\DISM.exe /Online /Enable-Feature /FeatureName:"NetFx3" /Source:"C:\MININT\sources\X64" /LimitAccess /All /NoRestart /logpath:C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_Dism.log >> C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_DismConsole.log]LOG]!><time="12:55:24.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ERROR - NetFx3 role processing with DISM.exe failed, rc = -2146498529]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="3" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = NETFX3]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Role processing complete.]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="12:55:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="12:55:58.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">

If I take the same log file from a machine where I have used the same task sequence but without deploying language packs, I can find that :
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[The task sequencer log is located at C:\Users\ADMINI~1\AppData\Local\Temp\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Roles will be installed.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoles.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OSRoleServices.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Features specified in Feature:]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[  NetFx3]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoles.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSRoleServices.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[No items were specified in variable OptionalOSFeatures.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41003 sent: ZTI Heartbeat: Processing roles (0% complete]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Validating connection to \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Already connected to server HPZ820 as that is where this script is running from.]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Copying source files locally from \\HPZ820\ZENPROD01$\Operating Systems\W8ENTSP0x64\sources\sxs]LOG]!><time="13:59:57.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[About to execute command: cmd.exe /c C:\windows\system32\DISM.exe /Online /Enable-Feature /FeatureName:"NetFx3" /Source:"C:\MININT\sources\X64" /LimitAccess /All /NoRestart /logpath:C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_Dism.log >> C:\MININT\SMSOSD\OSDLOGS\ZTIOSRole_DismConsole.log]LOG]!><time="14:00:20.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[NetFx3 role processing succeeded, rc = 0]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Property InstalledRoles001 is now = NETFX3]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Role processing complete.]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[ZTIOSRole processing completed successfully.]LOG]!><time="14:03:50.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">
<![LOG[Event 41001 sent: ZTIOSRole processing completed successfully.]LOG]!><time="14:03:51.000+000" date="10-24-2012" component="ZTIOSRole" context="" type="1" thread="" file="ZTIOSRole">

As you can see, in both logfile, the source are copied from the same folder.
Does anyone have an idea ? what am I missing ?

I have easily reproduced the problem on another computer (installing ADK/MDT, installing OS and creating task sequence).

Thanks in advance for your help.

Marc.

Hi All.

I have MDT 2012 installed. I followed a guide to create a Capture Reference OS to WIM File task sequence. I want to capture a Windows 8 pc. When I however run this task sequence it just take about 10 seconds and then get to the finish screen telling me it were successful, however, nothing is captured. What can be the problem?

Thank you in advance. 

I was toying with windows 8 deployment and was busy capturing a windows 8 image but when it was taking a while i checked with trace what was going.
when imagex scans the disk to capture it seems to do a lot of ignoring extended attributes before finally starting the capture.

never had this happen with windows 7 captures so i take it windows 8 uses a lot of extended attributes on files.

i read on the imagex page that it doesn't support these extended atributes but i'm sure it isn't the intention to increase deployment times by +/- 30 minutes just because imagex has to go through your disk saying it is ignoring certain attributes.

is there anyway to stop imagex from taking it's sweet time with windows 8 captures?

i am using a standard client task sequence.

Hi,

how can i use the application deployment preflight engine from the UDI-Wizard in a zero touch computer refresh scenario?

We want a zero touch computer refresh and retain the previously installed applications. Is there a way to recycle the preflight scripts from UDI?

SCCM2012 + MDT 2012 Update 1

Regards,

Tim

Hi guys,

I'm looking to fully automate my image creation process.  I'm trying to run a Powershell task at the end of the capture TS that will perform two  things:

1. Import the new image as an OS
2. Create a TS based on a template I created

I have the logic worked out and I can run the commands manually on the server after the capture process and its successful. However I'm having a real problem getting theMicrosoftDeploymentToolkit.psd1 module loaded into the WinPE.

I've created a folder for the module, copied the module itself out of the MDT %INSTALLDIR%\bin\ folder along with Microsoft.BDD.PSSnapIn*.*and then added that to the WinPE 'Extra folder to add' section in the MDT Console.

I've added a simple pause in my TS right at the end so I can run the commands manually to test

I can load the ZTIUtility module fine and can access all the MDT variables I need,  but when I run the following I encounter an error:

1. Import-Module X:\ZTIUtility\ZTIUtility.psd1
2. Import-Module X:\MicrosoftDeploymentToolkit\MicrosoftDeploymentToolkit.psd1  (so far so good)
3. New-PSDrive -Name "DS001" -PSProvider MDTProvider -Root "\\server\Deployment$"

I end up with an error stating:

"Could not load file or assembly 'Microsoft.BDD.Core'..."

and the PSDrive is never created.

Has anyone been successful in loading the MDT module into the PE or am I going about this all wrong

Latest version of 2012 U1.

I wanted to seperate my Win7 x86 and x64 deployment shares. I created a new deployment share, imported all drivers, created all apps, changed any references over to new share, etc.

When I run that ISO, I never get prompted for installing any apps and it reboots after asking me for PC name. Nearly identical CS.ini on the x64 side doesn't have this problem.

Is there anything that would cause this pitfall? I never ran into this before.

Hello,

i have a working deployment of Windows 8.

One problem:

Windows 8 keeps on logging in with the local adminstrator-account.

I tried to disable this by registry and netplwiz (Users must enter username WAS already enabled).

After reboot of the machine, still an autologon of the local administrator.

LocalGPOPackage of MDT is also disabled.

Where does this come from and how can i disable this?