We help IT Professionals succeed at work.

Assistance in Deploying Outlook 2010

PTR_ITDepartment
PTR_ITDepartment asked
on
Hello All,
      I am attempting to deploy Outlook 2010 to all the staff members in my company(about 75). I am having some difficulties. I have found a thread on EE about installing Office 2010 and I tried to follow that for the most part however whenever it gets to the point on the install where the client computer is rebooted and the install is supposed to take place I get an error message...
"Path or file specified with /adminfile was not found or did not contain any patches."

This error message pops up as well when the batch file itself is double clicked on the server. Any help or advice is appreciated.
Comment
Watch Question

The best resource for installing Office remotely  (upgrading or clean installing) is right on technet.microsoft.com at:

http://technet.microsoft.com/en-us/library/ee656736.aspx

There are basically a few steps I would use. First, you need a config.xml config file for each version of office (pro or standard) that you need to install. In the .xml file (located in the .ww folder for each version) you can specify some basic parameters for the install.  (See: http://technet.microsoft.com/en-us/library/cc179195.aspx)

For example, you can change install location, turn off pop-up messages and make the install silent, etc.

Once that's configured (I'd suggest the same config file for pro and standard upgrades) you then can use the OCT to fully customize everything.

The OCT tool is opened by running setup.exe /admin from the folder for each version of Office. You will then see an enourmous list of options that go into customizing office by using an .msp file.

The last step is deployment and in order to call up both the xml and msp you use the /config and /adminfile commands on a single install line.

For example, if you are installing a copy of Office 2010 standard upgrade to a machine from a network share I would create a batch file that maps the drive, then runs the install for that as so:

net use z: /d
net use z: "\\server with office shares\office share for standard" /persistent:no

"z:\office 2010 standard folder\setup.exe" /config "z:\office 2010 standard folder\config.xml" /adminfile "z:\office 2010 standard folder\standard.ww\custom.msp"

net use x: /d


Along with this you can auto activate Office by running the OSPP.VBS script from within the same batch file as so:


C:\WINDOWS\system32\cscript.exe "C:\Program Files\Microsoft Office\Office14\OSPP.VBS" /act

C:\WINDOWS\system32\cscript.exe "C:\Program Files (x86)\Microsoft Office\Office14\OSPP.VBS" /act


I put both examples for office on a 32 bit XP machine (top line) and on a 64 bit win 7 machine (second line) so you can see the folder locations differ slightly.

If you have any other questions, let me know!

Author

Commented:
I got the general jist of what you are speaking about. I have just one question. You keep refering to "Office" would this be the same for just the outlook application?
Sorry, yes. the same general principle applies to outlook itself if you are just installing outlook standalone.

The OCT should only show you Outlook options and the rest of the installation of Office will not be available.