$OEM$ not working in MSDT > Deployment Forum Community Forums

Friday, November 21, 2008

Library

Resources

Community

About

Community » Forums

Member Login

StandardLiveID

User Name:

Password:

Remember Login

Forgot Password ?


Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Unanswered Active Topics

Forums Search

Forums > Deployment Solutions > MDT 2008

Subject: $OEM$ not working in MSDT

Prev Next

You are not authorized to post a reply.

Author

Messages

David S.

Posts:10

01/24/2008 3:19 PM
In the BDD 2007 I would have $OEM$ directories for each of my build point. D:\Distribution\Control\\$OEM$\$1\ For some reason when I upgraded to the MSDT, the contents of these no longer come over. I deleted all my old BuildID thinking something when wrong during upgrade, and created brand new ones. Put back in my $OEM$ directory structure, but it still will not copy contents of my $OEM$ to my targeted system. Does this function no longer work in MSDT? Any help would be much appreciated, David S.

David S.

Posts:10

01/24/2008 3:20 PM
Forgot to also ask... Where in the Task Sequencer is this called up? What specific script is called to start this process? Thanks, David S.

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:120

01/24/2008 4:02 PM
Hi David- This is what my path would look like: \Distribution\Control\MYBUILDIMAGE\$OEM$\$1 Can you attach your logs too? Mike Dzikowski

Mike Dzikowski, MCP

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:120

01/24/2008 4:21 PM
Hi David- To answer your second question(s): "Where in the Task Sequencer is this called up? What specific script is called to start this process?" The $OEM$ directory is actually handled by sysprep when you seal it. Then, the LTISysprep.wsf script will look for these files. There is a For loop that handles this. Search the LTISysprep.wsf script for this. ' See if the Sysprep files already exist (e.g. copied by a build or OS-specific $OEM$\$1\Sysprep directory) For each sFile in Array("sysprep.exe", "setupcl.exe", "factory.exe") Here is a good KB on this: http://support.microsoft.com/kb/314479 Mike Dzikowski

Mike Dzikowski, MCP

David S.

Posts:10

01/24/2008 4:33 PM
My Path is pretty much the same. D:\distribution\control\BuildImage\$OEM$\$1 this worked fine when I was using the BDD 2007, but since I've upgraded to MSDT, it no longer seems to copy over the contents of the $1 folder C:\. Just a bit frustrating. And thanks for telling me about the LTISysprep.wsf script. That's what I needed to know. David S.

Mike Dzikowski User is Offline

Deployment Forum MVP

Posts:120

01/25/2008 8:40 AM
Have you tried recreating your Distribution Point and updating it? Mike Dzikowski

Mike Dzikowski, MCP

FarmerPete User is Offline

Posts:158

02/08/2008 2:37 PM
I've had the same issues. I tried using the base .\$OEM$ folder (since I wanted the same file loaded on all builds in the same place), but that did not work. I tried the individual $OEM$ folders with no success either. Not sure if I am doing some thing wrong, but it seems like it should be pretty straightforward.

You are not authorized to post a reply.

Forums > Deployment Solutions > MDT 2008 > $OEM$ not working in MSDT

ActiveForums 3.7

Forum Policies

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.

Privacy Statement | Terms Of Use