none
Upgrade from MDT 2012 to MDT 2012 Update 1 Problem

    Question

  • I have a Windows Server 2008 WDS + MDT 2012 Deployment Server.  There are 2 deployment shares, 1 for the build and capture, and 1 for the deployment.  It worked very well.  I was able to deploy Windows 7 Pro with WSUS updates, and install applications and drivers based on make and model.  When I updated MDT 2012 to MDT 2012 Update 1 and test Windows 8 Pro, some things stopped working and now I am stuck.  First, I am no longer able to boot to MDT through my VMWare Esxi 5.1 server.  I'll create a guest, I'll get the WDS boot screen, the progress bar will continue to full and the guest will reboot.  Second, when I try to buiid, sysprep, and capture or even deploy an operating system, it will connect to the WDS server, follow the custom.ini settings, partition the hard drive, install the operating system while in WinPE then fail.  The exact phrasing is "Failure(5627):1114:Run DISM.exe".  This is what I've tried:

    1) Import a new instance of either Windows 7 or 8 into MDT and create a new task sequence-Failed

    2)Uninstall MDT 2012 Update 1, Restart the server, Reinstall MDT 2012 Update 1-Failed

    3)Uninstall WDS Role, Restart the server, Reinstall WDS Role-Failed

    4)Create new Deployment Share with number 1-Failed

    5)Uninstall MDT 2012 Update 1 ADK, install MDT 2012 WAIK-Failed

    Short of installing a new server, which would be a PITA, I'm at a loss.  I have WinPE 3.0 and 4.0 loaded on WDS and can boot to WinPE 3.0 only from my VMWare guest machine.  On a physical machine I can boot to either 3 or 4.  I'm guessing the VMware drivers are probably not injected into the WinPE 4.0 version.  Howerver, they are injected into the LiteTouchPE.wim and will not boot into MDT.  It seems to me that the new WinPE version maybe isn't injecting the drivers correctly?  As far as the DISM.exe error, I'm not sure.  I've quadruple-checked my permissions.  They were working with the old version, why would they not work with the new version?  I would appreciate suggestions.  Below I have posted part of the bdd.log file for your viewing pleasure.  I can provide the entire file, but a)very long b)they need to verify my account before I can post it, sorry.  The bold sections are mentioning DISM.exe.

    <![LOG[Return code from command = 0]LOG]!><time="12:04:32.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="12:04:32.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[The image C:\MININT\Operating Systems\Windows 8 Pro x86\Sources\install.wim was applied successfully.]LOG]!><time="12:04:32.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: "\\ITHACA-DC2\MDTBuildLab$\Tools\X86\bootsect.exe"  /nt60 C:]LOG]!><time="12:04:32.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 2024)]LOG]!><time="12:04:32.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Target volumes will be updated with BOOTMGR compatible bootcode.]LOG]!><time="12:04:33.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > C: (\\?\Volume{055f1ce4-a862-11e2-ab2e-001e4ff36fa5})]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console >     Updated NTFS filesystem bootcode.  The update may be unreliable since the]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console >     volume could not be locked during the update:]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console >         Access is denied.]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Bootcode was successfully updated on all targeted volumes.]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = 0]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Find the boot drive (if any) [True] [6.2.9200.16384] [False]]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDiskPartition : \\MININT-Q9NJC12\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"    \\MININT-Q9NJC12\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[New ZTIDisk : \\MININT-Q9NJC12\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-Q9NJC12\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Ready to Prepare boot partition: V:]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Property UILanguage is now = en-US]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: cscript.exe //nologo "\\ITHACA-DC2\MDTBuildLab$\Scripts\ztiRunCommandHidden.wsf" ""\\ITHACA-DC2\MDTBuildLab$\Tools\X86\BCDBoot.exe" C:\windows /l en-US  /s V:"]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[The task sequencer log is located at X:\Windows\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log.]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[About to run command: \\ITHACA-DC2\MDTBuildLab$\Tools\X86\BCDBoot.exe C:\windows /l en-US  /s V:]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[Command has been started (process ID 1000)]LOG]!><time="12:04:41.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1000)]LOG]!><time="12:04:42.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[  Console > Boot files successfully created.]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[Return code from command = 0]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
    <![LOG[Command has returned: 0]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Run Command: X:\Windows\SYSTEM32\bcdedit.exe /Store "V:\boot\bcd" /timeout 0]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCD> The operation completed successfully.]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Created scratch folder.]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Copied unattend.xml to C:\Windows\Panther for image apply.]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[About to run command: dism.exe /Image:C:\ /Apply-Unattend:C:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Command has been started (process ID 1960)]LOG]!><time="12:04:43.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Deployment Image Servicing and Management tool]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Version: 6.2.9200.16384]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Error: 999]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > An error occurred. DISM could not be initialized in the local folder.]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[  Console > Ensure that DISM is installed correctly and that all of the binaries are present.]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[Return code from command = 999]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="1" thread="" file="LTIApply">
    <![LOG[FAILURE ( 5627 ): 999: Run DISM.exe]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTIApply" context="" type="3" thread="" file="LTIApply">
    <![LOG[Command completed, return code = -2147467259]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Litetouch deployment failed, Return Code = -2147467259  0x80004005]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
    <![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Property RetVal is now = -2147467259]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Unable to copy log to the network as no SLShare value was specified.]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[CleanStartItems Complete]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[TSCore.dll not found, not unregistering.]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\LTICleanup.wsf"]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
    <![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="12:04:44.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Removing AutoAdminLogon registry entries]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[VSSMaxSize not specified using 5% of volume.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Logs contained 8 errors and 0 warnings.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[No Windows PE image to delete.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Stripping BDD commands from unattend.xml template.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Modified unattend.xml saved to C:\windows\panther\unattend.xml]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Checking mapped network drive.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[testing drive Z: mapped to \\ITHACA-DC2\MDTBuildLab$]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Disconnecting drive Z: mapped to \\ITHACA-DC2\MDTBuildLab$]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up C:\MININT directory.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">
    <![LOG[Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.]LOG]!><time="12:04:45.000+000" date="04-18-2013" component="LTICleanup" context="" type="1" thread="" file="LTICleanup">

    Thursday, April 18, 2013 10:00 PM

All replies

  • No one.  Bueller...Well, I've been endlessly scouring the forums and stumbled into the Troubleshooting Windows Deployment guide by Michael Niehaus.  It lists serveral of the error codes and ideas of where to look.  On page 23, It lists 5627 LTIApply.wsf, Failure:Run DISM.exe.  He rates the errors by likelyhood of the error happening and how helpful the return error can be.  This error is a 9 for likelyhood, which means it's very likely to happen and for helpfullness of the return error message, it gets a 2, which means close to being useless.  The explanation for the cause of the problem according to Michael is this:

    "When applying an image using ImageX, the LTIApply script applies the unattend.xml file using DISM.EXE so that the servicing operations (drivers, patches, language packs) and settings are processed as expected. But in this case, DISM.EXE reported a non-zero return code. Typically this means that the unattend.xml was invalid or contained invalid settings. Check the DISM.LOG to see what the actual failure was."

    I was actually working on doing something about the unattend.xml today, but here is my dilema.  Although, in my MDT 2012 deployment solution I did customize the unattend through WSIM, I did not do this when I switched to MDT 2012 Update 1.  I used the settings in the customesettings.ini to do the job, which is this:

    [Settings]
    Priority=Default
    Properties=MyCustomProperty

    [Default]
    _SMSTSORGNAME=Ithaca School District
    SLSHARE=\\"Server Name"\Logs$\%OSDComputerName%
    OSInstall=Y
    SkipAppsOnUpgtrade=NO
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipComputerName=YES
    SkipDomainMembership=YES
    SkipUserData=YES
    UserDataLocation=AUTO
    SkipLocaleSelection=YES
    SkipTaskSequence=NO
    SkipTimeZone=YES
    SkipAppliations=NO
    SkipBitLocker=YES
    SkipSummary=YES
    SkipBDDWelcome=YES
    SkipCapture=NO
    DoCapture=YES
    SkipFinalSummary=YES
    SkipComputerBackup=NO

    TimeZone=020
    TimeZoneName=Central Standard Time

    JoinWorkgroup=WORKGROUP
    WSUSServer="MyWSUSServer"

    I've tried to use WSIM to create a catalog file, but having a 32bit image running on a 64bit server, it doesn't work.  I new this quite a while ago, but I thought, just maybe, the issue would be solved by the update.  When my solution was working, I would load the image on a 32bit server, create the catalog file, and then copy it over to the 64bit server.  Windows 8 will not work on the 32bit server, I'm guessing because I did not update the tools to MDT 2012 Update 1 yet.  I am quite apprehensive about updating the 32bit server based upon the results of the current server.  So, I'm thinking maybe I should create an unattend file manually to see if that could solve the problem.  Any other suggestions?

     

    Friday, April 19, 2013 7:48 PM
  • So, the saga continues.  I did install WSIM on my Windows 7 Pro admin machine and was able to successfully load the install.wim, both Windows 7 and Windows 8, and create a new catalog file.  I transferred the catalog file to my server and it still failed, displaying a 32bit catalog file cannot be created on a 64bit server.  I also transferred a known working unattend.xml file from a distribution share and it still failed.  At this point, I am almost resigned to the fact that the upgrade somehow messed up my installation and, unless something miraculous happens, I will need to create an entirely new fresh server.  I have some space on my VMware host and am going to test it.  Again, if anyone out there in cyberspace has any ideas at all, let me know.    
    Monday, April 22, 2013 2:44 PM
  • Wow that's a lot of info. Do you have Windows AIK and Windows ADK installed together? Plus I think I saw something where you are running Server 2008 WDS with Windows 8, but that is not supported.

    http://technet.microsoft.com/en-us/library/hh974416.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”


    Monday, April 22, 2013 10:20 PM
  • I appreciate the response.  I know, it's a lot of info.  At first, I did have both AIK and ADK installed together.  Then, I uninstalled AIK, then ADK, and reinstalled just ADK.  I am running WDS, but only to PXE boot.  I am leaving the deployment and heavy lifting to MDT.  The link that you have provided states that if you are running Windows Sever 2008 or R2 you cannot deploy Windows 8 with WDS, only Windows Server 2012 can.  MDT 2012 Update 1 supports deployment of Windows 8.  I've played around with a new deployment server running 2008 R2 and I am able to boot with WinPE 3.0 on a VMware guest machine, but not WinPE 4.0, it reboots after PXE booting to the WDS part.  A physical machine can boot to either WinPE, however, I get that nasty DISM.exe error.  It seems to point to the unattend.xml file, but I rebuilt one from scratch, and I still get the error.  Currently, my only hope seems to be the new server.  I will install MDT 2012 without Update 1 tomorrow, and see how it responds.  I really only wanted to play around with Windows 8 and possible deploy it to a select few machines next year to see if there is interest in the it.  I'll try to remember not to play around so much next time!  I'm at the point where I just want to get back to my old MDT+WDS Windows 7 Pro deployment server and have it work!
    Tuesday, April 23, 2013 3:50 AM
  • I am currently testing a new vmware Windows Server R2 with MDT 2012.  Like I did in my previous server, I mostly followed the book Deployment Fundamentals Volume 1 by Johan Arwidmark and Mikael Nystrom.  The build deployment share worked perfectly.  It installed Windows 7 Pro, updated via WSUS, I have the LTI Suspend task in there just to see if it was working and it did.  I installed office and IE9 while suspended, I continued, it updated again with WSUS, and then finally sysprepped and captured to the Capture folder on the deployment share.  I am going to further test the actual deployment of the custom .wim on the other deployment share folder, but I'm guessing that's going to work just fine.  It will take a bit longer to configure that one because I had SQL working with it so I could choose application roles and install drivers based upon make and model.  I'm not looking forwared to transferring all that stuff over, but if it works, I guess that's all that matters.  My adivce to anyone thinking of installing MDT 2012 Update 1, if you have your deployment solution working with Windows 7 and that OS is the only one you're going to deploy for the forseeable future, don't upgrade.  I'm not sure what exactly happended, but something got screwed up when I updated.  I even tried to wipe all the MDT/AIK/ADK installations and start over, but it still gave me that DISM.exe error.  It was like the software could not recognize that certain tools were installed.  If you are set on upgrading, make sure that you uninstall the workbench and AIK completely first.  Perhaps then it will work, but I'm not going to gaurantee you anything.  On a slifthly different note, The only part of the deployment process that I don't have working quite right is the joining to the domain.  I can get it to join the domain by adding the appropriate lines to the customsettings.ini

    JoinDomain=mytestdomain.LOCAL
    DomainAdmin=administrator
    DomainAdminDomain=mytestdomain
    DomainAdminPassword=password

    However, when the computer has to restart because of WSUS updates, it asks me to log on with the Adminstrator password, which has to be input into the Task Sequence setup. So, I've been leaving the JoinDomain commands out of the customsettings.ini and joining the domain manually. It works ok for me now, but when I install Windows 7 to about 200 computers this summer, it might get a little inefficient.  I'm sure there is a way, but does anyone know how to join the domain as the very last command after Windows Updates and Applications have been installed?  Perhaps I'm being to much of a perfectionist.  It would be could if it could work though.   

    Tuesday, April 23, 2013 5:16 PM
  • Glad to see you got it working. Where I was going with my previous post was that it looked like you still had some of the old WAIK tools still being used while Windows ADK was installed. After you upgraded to Windows ADK, you should have removed the old boot.wim (WinPE 3) from both WDS (the wim its pointing to boot into PXE) and the boot.wim in the MDT deployment share, recreated them and pointed WDS to the new wims (WinPE 4).

    As for the auto logon breaking, do you have a GPO or script in place to change the local admin name or password that takes affect after you join the domain?


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, April 24, 2013 10:55 AM
  • Yeah, I'm guessing there was some mix up there.  I did uninstall all of the ADK/AIK/MDT software, reinstalled just the new ADK software, created a new deployment share, and it still wouldn't work.  I'm guessing that if I installed ADK on the new server it woould've worked, but I know that my old setup worked, so I went with that.  If it ain't broke, don't fix it.

    I do actually have a GPO that changes the name of the local admin.  That was in the back of my mind, but somehow, I didn't think it had an effect on this situation because it seemed that sometimes the GPO wouldn't work right away.  I've had computers that were used in our domain that would go a few days after being introduced before finally changing its' local admin name.  Thinking about it now though, that would absolutely have an effect.  Although it usually prompts me with .\Administrator and asks for the password, it still may be interferring.  I suppose I could disable that GPO to test it.  That's why I thought if I could run a script to join the domain after all of the applications and updates it would fix that issue.  I'm just not very good script man myself.  I don't know if I'm allowed to say that here, but, I said it.  I apprectiate the feedback.   

    Wednesday, April 24, 2013 2:05 PM
  • In my situation I had the company disclaimer pop up after the machines joined the domain. I too had to move the domain join until the end to avoid it. I followed the steps in this blog to delay the domain join.

    http://blogs.msdn.com/b/alex_semi/archive/2009/08/28/avoiding-legan-notice-that-breaks-mdt-autologon.aspx


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

    Wednesday, April 24, 2013 2:13 PM