So I was given another challenge, and that is to start the rollout of upgrading our Office 2007 clients to Office 2010.
I have read that it is possible to have some issues with uninstalling 2007 so people do the OffScrub07.vbs trick, and I figured that is probably the best way to do this. I would like to make the install as clean as possible. So I have a .bat file that is in the root of my Office 2010 install. The file is to run the offscrub07.vbs script first, then run setup.exe for office 2010 after. My question is I am not sure if I need to put the full path to the server. It seems that everyone does that, but I am wondering what the point is, if the files are copied locally, why does it need to talk back to the server to run the script? This is what I have: call cscript \\server\Office2010\Offscrub07.vbs ALL /bypass 1 /q /s /NoCancel start /wait \\server\Office2010\setup.exe /adminfile \\server\Office2010\Office2010RollOut.msp Is there a way to call the script and point locally? Like: call cscript ..\Offscrub07.vbs ALL /bypass 1 /q /s /NoCancel Or something.... I am not very good with scripting :) Has anyone worked with doing it this way or maybe another way aside from the "get Office 2010 to do the uninstall" as I find it leaves left over files. Thanks, Kevin
