
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-09-2016 04:49 PM
I am trying to create a deployment package for Office 2016. I tried modifying the Office 2010 package listed but am still having failures. The remote PCs are Windows 7, both 32 and 64 bit.
PackageShare}\Installers\Office2016\Pro\setup.exe
/adminfile "{PackageShare}\Installers\Office2016\Pro\adminfile.msp"
"{PackageShare}\Installers\Office2016\Pro\setup.exe" /adminfile "{PackageShare}\Installers\Office2016\Pro\adminfile.msp"
When I deploy the package, I can see the install processes start on the remote PC but they never finish and keep running until I manually stop them.
Is anyone using something for Office?
PackageShare}\Installers\Office2016\Pro\setup.exe
/adminfile "{PackageShare}\Installers\Office2016\Pro\adminfile.msp"
"{PackageShare}\Installers\Office2016\Pro\setup.exe" /adminfile "{PackageShare}\Installers\Office2016\Pro\adminfile.msp"
When I deploy the package, I can see the install processes start on the remote PC but they never finish and keep running until I manually stop them.
Is anyone using something for Office?
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2016 02:36 PM
We don't currently have an installer package for Microsoft Office 2016, but we can provide some pointers:
This article we found online seems to cover the entirety of a remote silent Office 2016 installation and could be useful for you.
- Make sure your .msp file was created correctly in OCT to allow for a silent installation.
- As a test, run the command in CMD before deploying it using a deployment module, the feedback you receive in the CMD may be valuable.
This article we found online seems to cover the entirety of a remote silent Office 2016 installation and could be useful for you.
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2020 07:51 PM
Did you have any luck getting this to work for you? I am in the same situation.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-28-2016 04:23 PM
I did create the package using OCT using a silent install.
I tried running it with CMD and had the same problem, the Install never finishes and the deployment fails on a time out.
And I did select to accept the EULA.
I tried running the install manually from the location on our LanSweeper server and the install did work.
I'm going to try a couple different parameters and see if anything changes.
I tried running it with CMD and had the same problem, the Install never finishes and the deployment fails on a time out.
And I did select to accept the EULA.
I tried running the install manually from the location on our LanSweeper server and the install did work.
I'm going to try a couple different parameters and see if anything changes.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-26-2016 02:36 PM
We don't currently have an installer package for Microsoft Office 2016, but we can provide some pointers:
This article we found online seems to cover the entirety of a remote silent Office 2016 installation and could be useful for you.
- Make sure your .msp file was created correctly in OCT to allow for a silent installation.
- As a test, run the command in CMD before deploying it using a deployment module, the feedback you receive in the CMD may be valuable.
This article we found online seems to cover the entirety of a remote silent Office 2016 installation and could be useful for you.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-24-2016 02:22 AM
When a deployment never ends is more likely to be stuck. I suggest to run it without lansweeper to confirm your commands.
Did you select to accept EULA option in the admin file?
Did you select to accept EULA option in the admin file?
