Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2012 does not copy the folders inside $OEM$ !!!!

Discussion MDT 2012 does not copy the folders inside $OEM$ !!!!

  • Thursday, April 19, 2012 12:05 PM
     
     
    Sign In to Vote
    0

    HI,

    I have upgraded my Deplyment share from MDT 2012RC2 to MDT 2012 today.

    I am using $OEM$\$1\MYFOLDER to copy my folder into the root of the deployed image I have also kept few other files in $OEM$\$1 folder. I have kept $OEM$ in my MDT deployment root directory.

    Observation:

    The folder inside $OEM$\$1 (i.e MYFOLDER) is not getting copied to the deployed image whereas the files in $OEM$\$1 are getting copied.

    Any help?

    P.S: Before the MDT2012RC2 to MDT2012 it was working fine !

    Thanks in advance.

    Saravanan

    saravanan rajappa

     

All Replies

  • Thursday, May 10, 2012 5:52 AM
     
     
    Sign In to Vote
    0

    Same issue here.

    My folder structure that has always worked is:

    "D:\Distribution\Operating Systems\Windows Server 2003 R2 Std SP2 x86\$OEM$\$1\R2\CMPNENTS"
    "D:\Distribution\Operating Systems\Windows Server 2003 R2 Std SP2 x86\$OEM$\$1\R2\InstallR2.cmd"

    Upgrading to MDT2012 RTM appears to have broken the R2 piece.

    Help!

    Thanks :)

     
  • Thursday, May 10, 2012 2:18 PM
     
     
    Sign In to Vote
    0

    Same here.

    From the logfile it seems like it is copying the <MDTSHARE>\$OEM$

    I will try that out.

    Guess one could try to put the files in the <TSID>\$OEM$ as well.

    //Olof

     
  • Thursday, May 10, 2012 3:18 PM
     
     
    Sign In to Vote
    0

    It looks like $OEM$ folder does not get copied if image is applied using IMAGEX or it works if SETUP.EXE is used to apply the image. This command in post install phase appears to be working for me:

    xcopy "%DEPLOYROOT%\Control\%TaskSequenceID%\$OEM$\$1" "%OSDisk%\" /sevqy


    • Edited by mdtuser7 Thursday, May 10, 2012 3:20 PM typo
    •  
     
  • Thursday, May 10, 2012 4:02 PM
     
     
    Sign In to Vote
    0

    Here's my thread on the same issue (http://social.technet.microsoft.com/Forums/en/mdt/thread/786b7b3c-b6aa-4ce7-be6a-7226c296b7d1)

    What my solution was it this:

    Import the OS into the Deployment Workbench (My case - 2003 Std/Ent R2)

    Copy the CMPNENTS folder to the following path:

    d:\DEPLOYMENTSHARE\Operating Systems\Windows Server 2003 Enterprise Edition SP2\i386\$oem$\$1\R2

    This worked for me.

    Then I put this in a InstallR2.cmd file (per Johan's directions)

    reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup /v SourcePath /t REG_SZ /d C:\Windows\Source\i386 /f
    reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup /v ServicePackSourcePath /t REG_SZ /d C:\R2\CMPNENTS\R2 /f
    C:\R2\CMPNENTS\R2\setup2.exe /q /a /sr

     
  • Thursday, May 10, 2012 7:24 PM
     
     
    Sign In to Vote
    0

    Where is that location for Windows 7???

    B:\DeploymentShare\Operating Systems\Windows 7 x64.........

     
  • Thursday, May 10, 2012 11:28 PM
     
     
    Sign In to Vote
    0

    Thanks Graeme

    The fix appears to be as per your comments for Server 2003 x86 (but not x64) . This is how I fixed my builds:

    • For Server 2003 x86 - moved the OS\$OEM$ structure into OS\I386\
    • For Server 2003 x64 - moved the OS\$OEM$ structure into OS\AMD64\

    Both tested and work now!

     
  • Friday, August 24, 2012 8:09 PM
     
     
    Sign In to Vote
    0
    I ran into this as well.  Michael Niehaus has posted an explanation for why this was failing as well as a script to resolve it on his blog: http://blogs.technet.com/b/mniehaus/archive/2012/08/24/copying-oem-files-and-folders-with-mdt-2012-update-1.aspx#comments