copy files with MDT2013

Hi Experts,

I use MDT2013 for deployment. This works well since now.
But I need to copy a file into one application folder on the client.
Is this possible with MDT ? How ?
What kind of Task I can use ?
Eprs_AdminSystem ArchitectAsked:
Who is Participating?
 
Felix LevenSenior System and DatabaseadministratorCommented:
In the "depoyment share" in the Folder $oem" create Folders -> $1 and $$

•$1 will be copied to the root of the volume that the new OS image was applied to.
•$$ will be copied to the Windows folder on the volume that the new OS image was applied to.

Grab the copyOEM script here and make a new Task sequence under install:
http://blogs.technet.com/b/mniehaus/archive/2012/08/24/copying-oem-files-and-folders-with-mdt-2012-update-1.aspx

If the machines are joining a Domain after the deployment, better manage or add the files to the new machines by GPO's after they joined the Domain. I create a WDS OU and place important GPO's like WSUS Servers, add/remove files and registry GPO#s there.
1
 
Kent DyerIT Security Analyst SeniorCommented:
You do realize that could use a simple batch file or even a VBScript to do this task?  I will be honest, I know nothing about MDT.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
ok this sounds very good.
When I have the file i C:\ then I have to copy it to my application folder:

C:\programs\ASEV2

What can I do here ?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Felix LevenSenior System and DatabaseadministratorCommented:
if you want to copy a test.txt file to C:\Program Files\Internet Explorer

you create $OEM$\$1\Program Files\Internet Explorer\test.txt

and then add the script from the link to your Task sequence
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
ok I see,
just creating the folders in $OEM$ is not enough.
I have to put the script to my installation task Sequence right ?
0
 
Felix LevenSenior System and DatabaseadministratorCommented:
Files and Folders under $OEM$\$1 are 1:1 mirrored to the Client.

Save the script to "deployment share" scripts and add a new Task sequence under "install" add the path to your new script in "deployment share\scripts\myscript.wsf" to this new tasksequence.
0
 
Eprs_AdminSystem ArchitectAuthor Commented:
works perfect :-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.