MDT 2012 and DomainJoin

I am trying to understand when MDT 2012 joins the domain during a standard client task sequence if the settings are specified in CustomSettings.ini. In 2012 Beta 1, I had machines joining the domain during the "Recover from Domain" step. After upgrading
to 2012 RTM, machines are joining the domain well before that step (even before first logon).
Is this expected behavior and is there an easy way to change it?

By default, the domain join happens as part of the OS installation - the unattend.xml specifies to join the domain.  If you want that to happen later, e.g. using the "Recover from Domain" step, you would need to remove the join entries from the unattend.xml
associated with your task sequence.  The Lite Touch wizard will set the same task sequence variables in either case, and the "Recover from domain" step will notice that the unattend.xml didn't do the join.
Thanks, -Michael Niehaus Senior Program Manager, Microsoft Deployment Toolkit [email protected] http://blogs.technet.com/mniehaus
I have one question for you. I use a reference TS and i don't want that the reference computer joins the domain.
My CS.ini uses the joindomain and credentials (see below).
I removed the "recover from domain" from my reference TS.
But my reference computer still joins the domain !!
Do i need to modify unattend.xml on my TS ? Domain settings are empty there. I don't understand why it does not work !
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username></Username>
<Domain></Domain>
<Password></Password>
</Credentials>
<JoinDomain></JoinDomain>
<JoinWorkgroup></JoinWorkgroup>
<MachineObjectOU></MachineObjectOU>
</Identification>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>Azerty01</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>Azerty01</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
[Settings]
Priority=Default
[Default]
_SMSTSORGNAME=SHA
OSInstall=Y
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipUserData=YES
UserDataLocation=AUTO
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
SkipSummary=YES
SkipBDDWelcome=YES
SkipCapture=YES
SkipFinalSummary=NO
TimeZone=035
TimeZoneName=Eastern Standard Time
UILanguage=fr-FR
KeyboardLocale=fr-FR
UserLocale=fr-FR
JoinDomain=MDT
DomainAdmin=MDT\JoinAccount    
DomainAdminPassword=Azerty01
MachineObjectOU=ou=NewComputers,dc=MDT,dc=local
Thanks you !

Similar Messages

  • Windows 7 Image Deployment Failed in HP model D530 using MDT 2012 and ADK 8.0

    Hi,
    I need your help to sort out the following issue.
    I have installed MDT 2012 +ADK 8.0  and created Windows 7 32 bit OS from CD in the deployment share and tried deploying the raw OS from Deployment Share in to a reference machine (HP D530) ,the deployment failed also couldn't able to capture
    Image from the machine,even the sysprep failed. This is the error
    Your PC needs to restart.
    Please hold down the power button.
    Error Code:0x0000005D
    Parameters:
    0x030F0209
    0x746E6547
    0X49656E69
    0X6C65746E
    So tried the same in another HP machine ,the deployment was success and also was able to capture the refrence machine.
    Need your help to find why this error occurred in this specific HP model D530 alone. Is it the reason that ADK was not supported in that specific model.
    D530 is the maximum available HW model in client environment so your help will be much appreciated.
    Thanks in Advance!!

    I have never seen that error before (see identical post). I did a quick internet search and found the following:
    http://optimizewindows8.wordpress.com/2013/03/26/how-to-fix-error-code-0x0000005d/
    Either:
    1) Upgrade your machines with modern processors that support the ADK.
          or
    2) Downgrade to the WAIK
    http://www.microsoft.com/en-us/download/details.aspx?id=5753 and stick with Windows 7.
    Keith Garner - keithga.wordpress.com

  • SCCM 2012 R2 With MDT 2012 AND MDT 2013 Side by Side

    Currently we're running 2012 R2 CU3 with MDT 2012 integrated into it. We're looking at upgrading to MDT 2013 (whatever the latest update is). What I'm wondering, and can't seem to find any information on, is if we can continue to use our MDT 2012 boot
    .wims/OSD Task Sequences/etc  until such time as we create and test new ones or are we going to have to update everything right away?

    Are you sure you are using MDT *2013* with ConfigMgr 2012 *R2*? That's not a supported configuration and I think there are multiple technical problems with this combination.
    The task sequences themselves don't change -- because they are ConfigMgr task sequences -- but the MDT tasks must be updated to use the MDT 2013 tasks. Boot image use is partially dependent upon the OS you are deploying however only WinPE 3.1 and WinPE 5.0
    based boot images are supported in R2.
    Jason | http://blog.configmgrftw.com | @jasonsandys
    Did you mean to ask if we were running MDT 2012 with ConfigMgr 2012 R2? Then yes we are. We did the upgrade from SP1 CU2 to R2 CU3 a couple of weeks ago but haven't upgraded MDT to 2013 yet. That's our next step but we also don't want to take down/break imaging
    capability if we can help it (major college, staff/students constantly breaking stuff, etc).

  • MDT 2012 deploy OS from USB external drive failed - need to unplug and plug it once again

    We are using MDT 2012 and deploying Windows 7 using media (USB external hard drive). We can successfully deploy Windows 7 32 bit using this method but there is a problem with deploying Windows 7 64bit. This problem appears only on HP EliteBook 840. We can
    boot into WinPE 64 bit and can start proper task sequence, all image is applied then after restart, before logon screen appears there is an error saying that cannot find litetouch.vbs script. After clicking ok, I can logon to Windows and there is no usb external
    drive recognized. But when I unplug and plug usb drive once again it is recognized by Windows and can be used. I can see that Windows install some drivers just after plug it again
    I checked BIOS looking for some USB power options - there is no such settings. And 32 bit deployment works ok. So this is not a case. Looks for me like a problem with proper usb drivers for 64 bit. I download all drivers from HP website (driver pack and
    drivers only for USB 3.0). We are using make and model matching in MDT - works ok for all the rest hardware models. Any idea how to troubleshoot it?

    Not sure what's going on here. Is this a USB "Flash" drive or a USB "Hard Drive". There *Is* a distinction.
    I *thought* that MDT would copy itself to the c:\minint\scripts folder to continue installation.
    Next time, when you see this error, Press Shift-F10 to get into a cmd.exe prompt. Can you find litetouch.vbs on any of the drives? Does the USB Drive appear?
    IF in fact, the USB Drive is not appearing after the 1st reboot, then you have a problem. Why did the USB 3.0 driver not install. Check the Driver Installation Logs to verify.
    Keith Garner - keithga.wordpress.com

  • MDT 2012 upd 1 and Windows / Component updates

    I am trying to create a deployment for Win 7 x64 in MDT 2012, and it is going quite well.  My problem is with the Windows Update passes -- for some reason it misses many Office and Component updates until I go to deploy.  Then it takes another
    hour to grab and install those.  I don't understand why it does not grab them during the TS process.
    I am doing a staged capture in a VM environment, starting with a zero-touch capture that includes Office 2010 and all the updates.  This is my thin image and it takes about 5.5 hours through capture.  Then I take this thin image, add standard apps
    that cannot be silently installed, customize desktop options that cannot be easily automated (another huge pain, but another topic), and, I was hoping, install all the updates for Office 2010 and other non-OS components.
    In the first TS, I run the updates pre-installation, use the TS step to install Office, and run them again post-installation.  It does pick up a few, but then the logs say the system is fully updated and goes on to the next step.
    In the second TS, I use the post-installation update step.  One of the apps I use installs SQL components, and the TS picks up on this and installs several updates it finds.  Then it decides the machine is up to date and moves on, skipping about
    40 updates as of this writing.
    As a test, I inserted a reboot step between app installation and the post-install Update step, but it still ignored the Office updates.  Research on the issue turned up the idea that at some point ZTIWindowsUpdate turns on the extra updates, and also
    several suggestions that this is how it is supposed to work (and why the standard TS is designed this way).
    I rolled my VM back to the suspended point and I'm running WU manually at the console.  I had to enable "Microsoft Update" manually, and now it is happily pulling down the updates.  I just hope there's enough smarts left in the VM to
    run to  the task to completion.
    I'm hoping that some whiz with the process can enlighten us on how to force ZTIWindowsUpdate to search for critical updates for all Microsoft components, not just the OS ones.
    UPDATE:
    Digging into the code and logs, it seems that a certain condition is not occurring to trigger the Microsoft Update service; bFoundMU must be true for this to happen.  A ServiceID hard coded is not being matched--the reason escapes me.  Near as
    I can tell, after a magic reboot it finally finds a match for this ServiceID.  Hopefully this snippet does not get munged...
        On Error Resume Next
                Item = oFSO.GetFileVersion ( ees("%SystemRoot%\System32\WUAUENG.DLL" ) )
                oLogging.CreateEntry "Ready to Opt-In to Microsoft Update: WUA Version: " & Item , LogTypeInfo
                Set ServiceManager = nothing
                Set ServiceManager = CreateObject("Microsoft.Update.ServiceManager")
            On Error Goto 0
            If ServiceManager is nothing then
                oLogging.CreateEntry "Failed to Create Object: Microsoft.Update.ServiceManager" , LogTypeWarning
            Else
                bFoundMU = False
                For each Item in ServiceManager.Services
                    WScript.Echo "Registered Update Service: " & Item.ServiceID & "   " & Item.Name
                    If Item.ServiceID = "7971f918-a847-4430-9279-4a52d1efe18d" then
                        bFoundMU = True
                    End if
                Next
                oLogging.CreateEntry "Microsoft Update Service:  Enabled = " & bFoundMU, LogTypeInfo
                If not bFoundMU then
                    On Error Resume Next
                        Err.clear
                        ServiceManager.ClientApplicationID = "My App"
                        If Err.Number <> 0 then
                            oLogging.CreateEntry "There was an error getting Windows Update to opt into Microsoft Update. Please verify you are running the latest version
    of Windows Update Agent." , LogTypeWarning
                        End if
    The logs look virtually identical between the two runs.  This is getting way deeper than I understand the update process or about service IDs.
    UPDATE 2:
    Digging further, it seems that the the condition of bFoundMU has no bearing on whether or not MU is used, but possibly the existence of muauth.cab.  From the deploy log where it actually started, bFoundMU is still false, but at that point the Office
    updates started to come in:
    <![LOG[Property MSIT_WU_Count is now = 1]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Configuring Windows Update settings (manual update, use server)]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Archive NoAUtoUpdate State: Was [<empty>].]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Property NoAutoUpdate_Previous is now = <empty>]LOG]!><time="11:05:32.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Windows Update Agent verion 6 found, OK to continue]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Ready to Opt-In to Microsoft Update: WUA Version: 7.5.7601.17514]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Microsoft Update Service:  Enabled = False]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1"
    thread="" file="ZTIWindowsUpdate">
    <![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ Status: 3]LOG]!><time="11:05:35.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[Command Line Procesed Query=False Registered=False  UpdateCommand=[IsInstalled = 0 and IsHidden = 0]]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1"
    thread="" file="ZTIWindowsUpdate">
    <![LOG[Start Search...]LOG]!><time="11:05:36.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    __bunch of skipped updates__
    <![LOG[  SKIP  - 258b6ca1-a8ec-4dfa-b619-fb8cecac6e2e - Turkish Language Pack - Windows 7 Service Pack 1 for x64-based Systems (KB2483139) - 56 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
    context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 48f7e3b7-2c8f-4900-ae32-f3d8f29c988d - Microsoft SQL Server 2005 Express Edition Service Pack 4 (KB2463332) - 55 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - d68e0cb2-9501-405e-af9c-156f352d6735 - Security Update for Microsoft Visual C++ 2010 Redistributable Package (KB2467173) - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
    context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 719584bc-2208-4bc9-a650-d3d6347eb32e - Security Update for Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package (KB2565063) - 9 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
    context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - eb7a169f-6bca-4e00-a52a-623c063c162d - Update for Office File Validation 2010 (KB2553065), 32-bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - f51a0e5b-24a9-4be1-8b36-0f22f99949e7 - Security Update for Microsoft SharePoint Workspace 2010 (KB2566445), 32-Bit Edition - 17 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
    context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 35eb79df-cb34-491c-ab0a-34b63f32b45c - Update for Microsoft Office 2010 (KB2553092), 32-Bit Edition - 9 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - a6309b2e-7ee4-4b02-8ce9-cf39796a2411 - Update for Microsoft OneNote 2010 (KB2553290) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - f5202a56-ff34-401d-a040-f97c7f70891c - Update for Microsoft Office 2010 (KB2553310) 32-Bit Edition - 8 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 33a4aa0a-cb01-4326-85f4-4a7d33d8782b - Update for Microsoft Outlook Social Connector 2010 (KB2553406) 32-Bit Edition - 1 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate"
    context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - aae5e2c7-3498-4f43-af66-aec06a59713f - Microsoft Silverlight (KB2636927) - 12 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1"
    thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - c8077d6d-00c2-421b-89f6-30828574519a - Update for Microsoft Office 2010 (KB2767886) 32-Bit Edition - 271 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 9c5e43a3-3ae9-434d-b105-a9d7902d5f9f - Service Pack 2 for Microsoft Office 2010 (KB2687455) 32-Bit Edition - 395 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - b8fcacb4-add0-4cc9-8551-675b59965798 - Update for Microsoft Office 2010 (KB2825640) 32-Bit Edition - 18 KB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 5923c276-0628-4ba4-be3d-e56aa029a14b - Security Update for Microsoft Office 2010 (KB2687423) 32-Bit Edition - 2 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[INSTALL - 79b27019-3090-4309-bfdc-c8be9b21ab96 - Update for Microsoft Access 2010 (KB2553446) 32-Bit Edition - 7 MB]LOG]!><time="11:14:02.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context=""
    type="1" thread="" file="ZTIWindowsUpdate">
    After the subsequent reboot, bFoundMU was set to true.

    Another detail I neglected to mention is that I am using two separate deployment shares, one for building the deploy image and the other for actual deployments.  I think I found another clue in the log, muauth.cab:
    <![LOG[FindFile: The file muauth.cab could not be found in any standard locations.]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    <![LOG[ about to begin add service []]LOG]!><time="11:05:34.000+000" date="04-24-2014" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate">
    The next stanza in ZTIWindowsUpdate.wsf is this:
    If oEnvironment.Item("WsusServer") = "" then
                              iResult = oUtility.FindFile("muauth.cab", strCabPath)
                            If iResult <> Success then
                                '// "" will force a internet search for cab file
                                strCabPath = ""
                            End if
                            oLogging.CreateEntry " about to begin add service ["+ strCabPath +"]", LogTypeInfo
                            Set NewUpdateService = ServiceManager.AddService2("7971f918-a847-4430-9279-4a52d1efe18d",6,strCabPath)
                            oLogging.CreateEntry " Status: " & NewUpdateService.RegistrationState, LogTypeInfo
                        End if
    Indeed, the muauth.cab file was present in my first one, but not the deployment one.  As the log says, since there is no muauth.cab file, the code will then go download it. 
    I don't know how, when, or why this happened (why is it in my first DS and not my second?), but a simple test this evening will confirm my suspicion that if the file is not present it will update as expected.

  • MDT and Macs running Bootcamp – worked in MDT 2010, now does not in MDT 2012

    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 Guys
    I have been having the same problem.
    What I have done to get around it is
    add a custom command as we all did in MDT 2010 to format partition 3 or 4 depending on the version of OSX
    don’t disable the Format and Partition Disk task but tick in create active partition then remove the partition properties and then click on options and check
    continue on error
    then under install operating system change the partition that you want to have windows installed on
    Once the deployment has completed you will receive the message that deployment has completed but with one error
    Hope this helps
    Regards
    Matthew

  • MDT 2012 Update 1 Boot Image Creation Fails in SP1

    I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
    installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
    \\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
    a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
    Description:
      Stopped working
    Problem signature:
      Problem Event Name: CLR20r3
      Problem Signature 01: microsoft.bdd.elevatedproxy.exe
      Problem Signature 02: 3.0.0.0
      Problem Signature 03: 50400c36
      Problem Signature 04: System.ServiceModel
      Problem Signature 05: 3.0.0.0
      Problem Signature 06: 4fee6b19
      Problem Signature 07: fb9
      Problem Signature 08: a7
      Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
      OS Version: 6.2.9200.2.0.0.272.7
      Locale ID: 1033
    The error in the boot image creation wizard is:
    Started processing.
    Creating boot image.
    Error while importing Microsoft Deployment Toolkit Task Sequence.
    System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
    configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
    Server stack trace:
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
       at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
    I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
    re-installing, etc, but same problem occurs each time.

    I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 20:22:59, Info                  DISM   PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 20:22:59, Info                  DISM   API: PID=2252 TID=3088 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
    2013-03-03 22:02:50, Info                  DISM   API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-03 22:02:51, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
    2013-03-03 22:02:58, Info                  DISM   API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:57, Info                  DISM   API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-03 22:03:59, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-03 22:04:39, Info                  DISM   PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-03 22:04:39, Info                  DISM   API: PID=3544 TID=3672 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
    2013-03-04 08:41:07, Info                  DISM   API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-04 08:41:08, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
    2013-03-04 08:41:09, Info                  DISM   API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-04 08:42:25, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-04 08:42:44, Info                  DISM   PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-04 08:42:44, Info                  DISM   API: PID=1016 TID=1620 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:44:10, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll:                                           
    - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2013-03-05 08:44:12, Info                  DISM   API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
    2013-03-05 08:44:13, Info                  DISM   API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
    2013-03-05 08:44:14, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
    2013-03-05 08:44:32, Info                  DISM   API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2013-03-05 08:45:56, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-03-05 08:46:18, Info                  DISM   PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                                         
    - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2013-03-05 08:46:18, Info                  DISM   API: PID=4140 TID=1320 DismApi.dll:                       

  • MDT 2012 + WinPE 4.0 + VMWare ESXi - Hangs "Windows is loading files" booting into PE

    I'm trying out using MDT 2012 and WinPE 4.0, upgrading things. I've recreated things following templates in MDT 2012. I'm also using ADK and WinPE 4.0.
    Issue I'm seeing is upon restarting into WinPE I see the screen showing Windows is Loading Files and the progress bar. I see the first one load through and then the second slower one load through. Once progress bar fills, it just does nothing and I'm left
    looking at a complete progress bar.
    I was trying obviously first using VMWare ESX 5.0 with no success, subsequently tried a couple of physical machines and those had no problems. I still want to get working on ESX since that will help speed up development and testing of the rest of the stuff
    I need to upgrade. Tried a variety of SCSI controllers within ESX vms. I tried VMWare Workstation 9 with the mixed results as with the LSI Logic Parallel SCSI controller had success but not the others.
    I of course at first tried making sure drivers were added with no change, although that still could be an issue with drivers I found to put in being incorrect.
    More interestingly though is that I can of course install Windows 8 from install media just fine on these hardware, as well as if I create an ISO from the deployment share and boot to that it works just fine, so it seems to just be an issue when booting
    to WinPE on disk.
    Any ideas are greatly appreciated. Thanks.

    I did have the same problem with ESXI 4.1 and Windows 8.
    I found a full solution with the following:
    download the linked file at the bottom of this post and add the following options to your vmware-configuration
    file:
    bios440.filename =
    "<full path to rom image>"  --> if file in folder of vm only "bios.440.rom
    mce.enable = TRUE
    cpuid.hypervisor.v0 =
    FALSE
    vmGenCounter.enable =
    FALSE
    This worked for me for several environment with an older ESXI-invironment and Windows 8.
    http://communities.vmware.com/servlet/JiveServlet/download/2139717-98102/bios.440.rom
    I can confirm that this works also!  Many thanks!
    ESXi 4.1 with WinPE4.0

  • Mdt 2012 sp1 command line does not run from task sequence

    Hi,
    I am hoping I can explain this correctly.  I am using MDT 2012 and having an issue with running command lines, powershell and batch files that I setup.
    The task sequence is set to use an account called "MDTService".  it has rights to join the domain but is not in the local admin group of the reference image.  a domain GPO renames the local admin account CoAdmin.
    when running a command line to, for example, run xcopy a folder and subdirectories to the "program Files x86" directory, it does not copy.
    When I log on to the system and use an admin account to manually run the command I do not have an issue.  if I log onto the system with the MDTService user and run it, it fails.
    How do I get the commands to run from the MDT task sequence?  I do not want to make the MDTService user an admin.  I have tried the run as option in the task sequence but that did not work.  maybe is set it wrong.  I used a domain\Admin
    account which did not work.
    what can I clarify or logs can I post to provide more details.
    Thanks in advance.

    Any account that needs to add files under %ProgramFilesx86% must be granted administrative privileges.
    Keith Garner - keithga.wordpress.com

  • MDT 2012 Suspend Task Sequence Problem

    Hi ,
    I have been using LTISuspens.wsf without problem in my MDT 2010 and MDT 2010 U1 for a long time. Recently I have create my test MDT 2012 and I have problem with this task.
    I have created the new Run Command line cscript.exe "%SCRIPTROOT%\LTISuspend.wsf" in State Restore section. The build and capture TS is stopping correctly and I have the LTISuspend icon on the desktop. After resuming the TS, it going correctly through, running
    sysprep, pop in again Set Network Location window, I can see it is running “Apply Windows PE (BCD)” step and then stops. There is message “suspended” and “The task sequence has been suspended true Use the…..”
    Any ideas what I am doing wrong?
    My customsettings.ini is from MDT 2010 and there they are fine.
    I am capturing Windows 7.
    Thanks
    Vinnie

    Hi,
    A few suggestions below for each of your issues.
    Issue 1 is that you don't see any task sequences in the wizard
     - Have you updated your deployment point after upgrading to 2012? if not then do this now
     - Have you updated your boot media with the newly generated Litetouch_x86.wim (meaning your boot CD, boot USB or WDS)
    The thinking behind this is that if you are using MDT 2010 boot media to try and speak to an MDT 2012 DS then you will have the same problem.
    Issue 2 is that you've had the TS running in the past but it's broken for one reason or another.
     - Have you recreated your Task sequence using the MDT 2012 client template? There are (minor but critical) differences in the logic between the versions of MDT and the new task sequence template has been updated as such. Using an MDT 2010 template with
    MDT 2012 scripts can cause this.
    These are 3 things that cause similar issues to you following an upgrade.

  • MDT 2012 & Symanted Endpoint Protection & Samba

    I have had this problem through all betas of MDT 2012 and it still exists in the final release.
    Conditions:
    Windows 7 Professional wSP1 x64 installed using all default settings.
    Installing Symantec Endpoint Protection 12 R1
    Connecting to any SAMBA computer (specifically Mac OSXS.
    If I install the OS using MDT 2012 (there is no issue with MDT 2010) once I install SEP the computer can no longer connect to SAMBA computers. Specifically tested with Mac OSXS but also tested with CentOS. The OS can connect with no issues before installing
    but once SEP touches the computer (uninstalling SEP does not fix the problem) it can no longer connect to SAMBA machines. When attempting to connect I get "The specified server cannot perform the requested operation.".
    I can not find anything in the documentation or changelog for 2012 that would lead to this issue. Also this is *NOT* a problem with SEP as there are zero issues with MDT 2010.

    Spent most of the morning on this but think I have found the answer.
    New to MDT 2012 is a feature called "Apply Local GPO Pack". This feature is part of the SystemRestore section of the default Task Sequence.
    Following deployment of a computer by MDT 2012, this step is run - and it modifies Security Options in the Local Security Policy. If these same settings are not configured or not defined in your Group Policy (in an AD environment) then the Local Security
    Policy wins.
    Specifically there are some options regarding LM and NTLM that get changed and a setting for "Require Secure Communications Always". Both of these settings cause connections to SAMBA shares to be disabled - there are lots of settings that get changed, including
    the default cached credential count, which I mentioned.
    To disable this from happening when you deploy your images in MDT 2012 you can go into the Task Sequence - right click Properties. Click on the Task Sequence tab and locate the "Apply Local GPO Package" item in the "SystemRestore" section.
    Then, click on the Options tab and select "Disable this step".
    Alternatively, add ApplyGPOPack=NO to your customsettings.ini
    http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/d93ce842-184c-414c-b2c6-bc4a7272d814
    Full list of settings changed by this feature available here (see Excel attachment)
    http://blogs.technet.com/b/deploymentguys/archive/2011/12/02/mdt-2012-new-features-gpo-packs.aspx
    I don't understand why Microsoft decided to have this set by default in their task sequences. It makes more sense to deploy a default installation of Windows 7 and then have the option of enabling the additional security options.
    I hope this helps with your issue or points you in the right direction.

  • Windows Restarted Unexpectedly while applying systems settings after MDT 2012 deployment.

    Posted this in another forum, so I figured give this forum a try.
    Hello,
    I wonder if anyone can help or point me in the right direction.  I've created a couple of WIMs and deployed them out using MDT 2012 and WDS running on a Windows 2008R2 server.  The images are created and captured fine.  Sysprep runs with no issues
    and I can deploy out the images to any PC/laptop I want.
    The issue I'm running into is I can deploy out this image to 100 PC's without any issue.  Then all of a sudden, I'll get an error saying Windows restarted unexpectedly or encountered an unexpected error and can not continue.  This will then happen
    from now on with this particular image.  For instance I've imaged a particular Dell Optiplex 790 multiple times with no problem, then all of a sudden I get this error on this or any other PC i image.
    If I create a new image, the pattern just keeps happening over and over again.  I know it's not an issue with the physical computers themselves and I can imagine something is corrupting every image I have over a certain amount of time, so I'm sort of at
    a loss.  Driver issue perhaps?
    Thanks,
    Mike

    I'm having what sounds like the same problem, which is why I posted it with this thread.  I have been using MDT 2013 on various computers without any issues and now I am receiving the
    Windows restarted unexpectedly message after the image has been applied.  It will not get past the error.  We only recently began using MDT 2013 with windows 2012 R2, so I don't have much experience troubleshooting.  The only error I
    found in the smsts.log is as follows:
    User specified local data drive D: TSManager
    2/6/2015 1:20:20 PM 628 (0x0274)
    D:\_SMSTaskSequence does not exist TSManager
    2/6/2015 1:20:20 PM 628 (0x0274)
    Creating directory D:\_SMSTaskSequence TSManager
    2/6/2015 1:20:20 PM 628 (0x0274)
    uRet == ERROR_ALREADY_EXISTS, HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,916)
    TSManager 2/6/2015 1:20:20 PM
    628 (0x0274)
    Failed to create D:\_SMSTaskSequence (3) TSManager
    2/6/2015 1:20:20 PM 628 (0x0274)
    I am deploying windows 8 (x64 &x86) custom wim images created using Hyper-v.  In my custom.ini file I use an IP address for my server and I join the computer to our domain.  
    1) Could the IP address be causing the problem?  Should I use the full domain address for my server?
    2) If the WIM file is locked somehow or unavailable, what services should I turn off on the server?
    3) Any other suggestions?
    I won't have access to the server for a couple of days and I wanted to get help before I start to make changes or create another image.  Thank you!

  • MDT 2012 stuck on Processing Bootstrap Settings

    I just updated my mdt 2010 to mdt 2012 and when I go to run litetouch.wsf it starts and then it gets stuck at the screen that says "processing bootstrap settings" and it never goes past it.  it in tcommand window it says "command completed return
    code = 0"  any thoughts?

    BTW my CustomSettings.ini is as follows;
    ==============================================================================
    [Settings]
    Priority=Default
    Properties=MyCustomProperty
    [Default]
    OSInstall=Y
    ComputerName=%SerialNumber%
    _SMSTSOrgName=Name
    JoinWorkgroup=WordGroup
    KeyboardLocale=en-us
    DeploymentType=NEWCOMPUTER
    SkipFinalSummary=YES
    SkipAdminPassword=YES
    SkipAppsOnUpgrade=YES
    SkipBDDWelcome=YES
    SkipCapture=YES
    SkipComputerBackup=YES
    SkipComputerName=YES
    SkipDeploymentType=YES
    SkipDomainMembership=YES
    SkipFinalSummary=YES
    SkipLocaleSelection=Yes
    SkipPackageDisplay=YES
    SkipProductKey=YES
    SkipTaskSequence=Yes
    SkipTimeZone=Yes
    SkipUserData=Yes
    SkipWizard=YES
    TaskSequenceID=ARC32BUILD
    UILanguage=en-US
    UserDataLocation=NONE
    UserLocale=en-us
    ==============================================================================
    My Bootstrap.ini is;
    ==============================================================================
    Blank
    ==============================================================================

  • Install SQL Express With MDT 2012 now or wait for SCCM and full SQL Server?

    We are planning to get SCCM 2012 R2 in several months and it will come with SQL Server 2012 when it is installed and configured at that time.
    If we would like to start experimenting with using a database in MDT 2012 now, can we go ahead and set up a database in SQL Express and start using it  for deployments now or should we wait for SQL server?  
    Can the database created in standalone MDT 2012 with SQL Express be migrated to SQL Server 2012  and SCCM 2012R2 or would we need to start over with a new database when we get SQL Server and SCCM?

    Using SQL Express should be fine.  You can export the database from there and import it into a full SQL Server install later if you want to preserve the content.
    Thanks,
    -Michael Niehaus
    Senior Product Marketing Manager, Windows Deployment
    http://blogs.technet.com/mniehaus
    [email protected]

  • MDT 2012 measuring amount and deployment time

    I'm on beginning of MDT's Adventure. For our Client we have to prepare in a monthly basis image load reports that contain amount of images deployed in requested period of time with information how many each OS installation took time. If it's possible to
    collect those information from MDT 2012/WDS logs and if it is possible to automation of preparation image load report process.

    You could always do a .count of your logging directory on the MDT DS.  The other option would be a Powershell script that runs at the end of the deployment.  It could be something as simple as --
    #TS Variables
    $tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
    $scriptroot = $tsenv.Value("Scriptroot")
    #Machine Log Path
    $machineLog = machinelog.txt
    #WMI Variables
    $os = get-wmiobject win32_operatingsystem
    $computer = get-wmiboject win32_computersystem
    #VALIDATE MACHINE LOG EXISTS.
    if (!(test-path $scriptroot\$machinelog)){
    new-item -path $scriptroot\$machinelog}
    #ADD CONTENT TO MACHINE LOG.
    add-content -path $scriptroot\$machinelog -value "Machine built - $(Get-Date) - Machine Name : $computer.name OS : $os.version"
    #DONE
    exit 0
    This is really basic but you get the idea.  Have it shoot data to a file.  Usually you would want this into an xls file, but that takes a bit more work.  I take no responsibility for this script and it has not been tested, it's more to give
    you the idea of the construct for what you would need.  Good luck.

Maybe you are looking for

  • Qosmio X305 will only boot in safe mode or when the graphics card disabled

    Hi All I am having a very concerning issue with my laptop (Toshiba Qosmio X305). It will only boot in safe mode or if I disable the graphics card. Awhile back I upgraded the drivers for the nVidia 9800M GTX from the nVidia website, it worked fine for

  • How to make the scroll bar in flex automate to focus on the new ui component added in the canvas?

    Hi all , There is a canvas container where am adding charts in separate windows. So whenever a new chart is added the scroll bar needs to set the focus on the present chart window. For this i made the functionality for the canvas container to scroll

  • WLC 5508 preloaded software by default

    While ordering cisco part AIR-CT5508-100-K9 via multiline configurator. My question would be which software version comes whith it by default when choosing SWC5500K9-70. Is it particularly file named AIR-CT5500-K9-7-0-230-0.aes loaded onto controller

  • How to programmatically extract VL10C results into a file?

    Hi Experts, I need to extract VL10C results programmatically into a file for a downstream non-SAP application to consume. What's the best way to do it in a ABAP program? Many thanks! -Lily

  • Wall socket charging very slow

    I sleep with my ipad2 last night at 1am and today wake up at 10am, my iPad is only from 25% to 75%. I used the wall socket but also use a 3rd party USB extend cable together with the apple cable because original one is too short. Notification shows c