Friday, January 09, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
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.

Forums > Deployment Solutions > MDT 2008
Subject: Copy .DLLs to C:\Windows\System32?
Prev Next
You are not authorized to post a reply.

AuthorMessages
buttsteakUser is Offline

Posts:11

Send Message
06/16/2008 3:43 PM  

Hello,

In my work environment, we have several custom applications that require additional .DLLs to run properly.

Can I use MDT 2008 task sequencer to copy those .DLLs to the system32 folder of the target machine?

If so, how would I go about doing that?

For the source path, I was thinking of placing the .DLLs in a folder inside the Distribution$ of the deployment server.

-thanks

KonradUser is Offline

Posts:67

Send Message
06/16/2008 6:23 PM  
You can use an $OEM$ structure, such as can be used with scripted XP installs. With MDT, you can place an $OEM$ folder under a task sequence folder, eg:
Distribution\Control\MYIMAGE_XP\$OEM$


Under the $OEM$ folder you can have a $$ folder and anything within it will get automatically copied into the c:\windows folder during the install of Windows. So if you wanted some dlls to copy into the system32 folder, create this structure:

Distribution\Control\MYIMAGE_XP\$OEM$\$$\System32


And put your dlls in there.

Alternatively, you can put a $OEM$ folder in a couple of other places (I believe), including:

Distribution\$OEM$ (the root of the distribution folder so that it applies to all OSs, all task sequences)


Distribution\Operating Systems\Windows XP Pro SP2\$OEM$ (the root of an OS source folder)

FarmerPeteUser is Offline

Posts:168

Send Message
06/17/2008 7:30 AM  
I had a similar situation for our deployments. I actually did it two different ways with two different applications. For one project I created an MSI installer. This has the added benefit that I can remove the program or upgrade it later very easily. The downside to this is you have a little bit less flexibility with an MSI, and you also have to have MSI authoring software. The next solution I used was to make a self-extracting package. I use a system that makes a single file executable and when it extracts, it will run whatever command-line you want. Thus I can have it run a bat file or a vbscript, or a batch file that runs a vbscript.

The main benefit to using either of these methods is that you can set them up as application installs, and then you can either slip it into your system build process or you can set it up as a dependency of the application(s) that need it.
You are not authorized to post a reply.
Forums > Deployment Solutions > MDT 2008 > Copy .DLLs to C:\Windows\System32?



ActiveForums 3.7
Forum Policies
Minimize

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
© 2007 Jerry Honeycutt