[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

office 2013 deployment

I am setting up an office 2013 deployment using the OCT. however, when I save the setup, it saves it as an MSP. as a new install, it will not run saying it is a patch. Why does this not confugure as an MSI and how can I get this to be an MSI?
0
geriatricgeek
Asked:
geriatricgeek
2 Solutions
 
ozzeczekCommented:
Everything fine;)
You can run your setup with your customization file msp
setup.exe /admifile path_to_msp

http://technet.microsoft.com/en-us/library/cc178956(v=office.15).aspx
http://technet.microsoft.com/en-us/library/cc178960(v=office.15).aspx
0
 
RobSampsonCommented:
Not sure if this still applies, but for my Office 2007 deployment, I put the custom MSP in the Updates folder of the admin share, along with Service Packs, and then running Setup.exe alone, used those MSPs and installed all of my settings automatically.

Rob.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now