Help! Cannot deploy this script with SCCM

What am I doing wrong?
It works when I deploy it manually by logging in with my domain admin account and right click run as administrator.
Here is the script, what wrong with it.
This is part of my Office 2010 deployment.
@echo off  
rem A basic script to copy .officeUI files from a network share into the user's local AppData directory, if no .officeUI file currently exists there.
rem Can easily be modified to use the roaming AppData directory (replace %localappdata% with %appdata%) or to include additional ribbon customizations.   
 
setlocal[/style]
set userdir=%localappdata%\Microsoft\Office[/style]
set remotedir=\\MyServer\LogonFiles\public\OfficeUI  [/style]
for %%r in (Word Excel PowerPoint) do if not exist %userdir%\%%r.officeUI cp %remotedir%\%%r.officeUI %userdir%\%%r.officeUI[/style]
endlocal[/style]
 
Any help you can give me would be appreciated.[/style]
[/style]

You are copying using domain admin to reach that share.  CM doesn't do that.  It can use the network access account or the machine acct of the workstation to copy.  So grant domain computers read on that share or the network access acct.  Or preferably, copy what's on that share into your package and let CM deliver it to the cache folder.

Brian Mason
MCTS\MS MVP - ECM 
http://www.mnscug.org/

To expand upon Brian’s comment, you can simulate what CM07 does on the local workstation by running a command prompt as the local system. Here is how to do it. http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/

www.Enhansoft.com

Blog:
http://smsug.ca/blogs/garth_jones/default.aspx

You can also use Pushd   instead of set remotedir=\\MyServer\LogonFiles\public\OfficeUI.   This will map the next availabe drive and automatically change you to that directory.  Useful for the times you need a drive letter vs just a path.  In this case the out come would be something like L:\public\OfficeUI.  Once you are finished, type Popd towards the end of the batch file and it unmaps the drive for you.
 
I find it useful for when you have an install that has to be run from a mapped drive or at times has to be run from a specific directory on the local machine.  Pushd to the directory/share you need to copy something from then xcopy *.* /s /y whatever localdir you need.

That and if you run it in a normal mode with echo on, you can see if there are any permissions issues when it tries to map the drive.

Nothing fancy, but you may find it useful at some point.  :)
 

I'm  new to giving advice rather than asking for it, but Id consider checking what account is being used to run your script - if its set to run with admin rights,(on the program, environment tab) then it runs under the local system account. That being the case I think your script will struggle with this bit -
 

 set userdir=%localappdata%\Microsoft\Office[/style]  

 
as it will be trying to use the localappdata path for the SYSTEM user.
 
When ive done things like this in the past I've used VB to grab a profile list from the registry and then carry out actions for each individual profile. Alternativly, you can set the job to 'run with user rights' and that will at least test the theory.
 
To help with testing, you can use psexec (free tool, just google it) to run a script as the SYSTEM user rather than as your user elevated. 
 
Sorry for any repetition - did something really odd there and didn't notice other replies. 
Regards
 
Colin
 
 

My first thought is that you have to manually kick it off as an admin locally to get it to work, so how does your package kick it off as an admin?  Is it in the package, or are your users local admins?  That might be the problem . . . just putting it out there.