Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Resources for IT Professionals >
> 
> 
> 
$OEM$ different computers

Unanswered $OEM$ different computers

  • Tuesday, October 30, 2012 2:42 PM
     
     
    Sign In to Vote
    0

    hi all

    we deploy windows 7 and now we plan to deploy also server! In our test we see that server use also $OEM$.  Is it posible that the server doesn't use the $OEM$ folder because there are many win7 client tools in this folder

    Chris

     

All Replies

  • Tuesday, October 30, 2012 3:03 PM
     
     
    Sign In to Vote
    0
    I'm not 100% sure but if you use install Windows using imagex/dism $oem$ folders will not work. If you install windows using setup.exe then $oem$ folder will work (This I know since I still use MDT 2010 RTM). You can have the $oem$ folders inside the control folder to have TS specific files. In the deployment share you can have common $oem$ files. Depending on OS you can also have $oem$ folders in the operating system<OS> folder. I'm not sure when to use he <OS> folder or the <OS\i386 folder.
     
  • Tuesday, October 30, 2012 4:45 PM
     
     
    Sign In to Vote
    0

    MDT 2012u1 no longer uses setup.exe but imagex to deploy images.

    This post should help: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/59c2d2b6-b21c-4bee-bb68-00ecab7b9a69/

    Suggestion:

    1. Create 2 wim files containing the data, one for each platform
    2. Apply the data wim using a task sequence step. Each platform will have their own.

    Blog: http://scriptimus.wordpress.com

     
  • Tuesday, October 30, 2012 9:07 PM
     
     
    Sign In to Vote
    0
    I'm not 100% sure but if you use install Windows using imagex/dism $oem$ folders will not work. If you install windows using setup.exe then $oem$ folder will work (This I know since I still use MDT 2010 RTM). You can have the $oem$ folders inside the control folder to have TS specific files. In the deployment share you can have common $oem$ files. Depending on OS you can also have $oem$ folders in the operating system<OS> folder. I'm not sure when to use he <OS> folder or the <OS\i386 folder.

    I could not find the edit button. I use MDT 2012 RTM (not MDT 2010 RTM) and there the OEM folders work fine. This is one of the reason why I've not upgraded yet. When I've some more time I will look into some other solution for OEM folders with MDT 2012 Update 1.
     
  • Wednesday, October 31, 2012 8:06 AM
     
     
    Sign In to Vote
    0

    hello andrew

    is this only a feature from 2012 U1

    we use $OEM$ to create a folder c:\daten and "Program Files (x86)\company".

    how can i create a wim file that include a folder c:\daten and a folder  program files (x86)\company. And does the wmi file create this folders?

    thanks

    Chris

     
  • Thursday, November 01, 2012 8:55 PM
     
     
    Sign In to Vote
    0

    It's really simple. Think of it as zipping a bunch of files.

    1. Create a partition and customise it with files and folders. eg D:
    2. Capture the partition using imagex.exe 

    example command:

    imagex /capture D:\ Custom.wim "Custom WIM name" /compress fast /verify

    However, if it's just a couple of empty folders that you want to create then consider a custom script. Powershell etc.

    You could even use a batch file to copy the contents of %OEM%(Z:) to the system partition.

    Blog: http://scriptimus.wordpress.com