[ms office - 2016] Office ProPlus 2016 Deployment

[nelliott]

Hi All,

 

I'm looking for some advice, I've created an application within SCCM to silently install Office 2016 ProPlus.

I have run the MS Office Customization Tool however, the install won't complete as part of the OS deployment sequence because it presents the license agreement screen which has already been agreed through the customization tool.

 

Any thoughts or ideas would be much appreciated?

[Norphy]

Have you put the resulting MSP file the tool generates into the Updates folder in the install media?

[nelliott]

That might be the issue, its just in the root of the Office folder...

[mullet_man]

Yes the customisation file will only be picked up when it's in the Updates folder.

[nelliott]

I've moved the file, will I need to re-add it into SCCM?

[mullet_man]

Am only a novice in SCCM but I think you'll need to refresh the package, think you right click and choose update or refresh content in deployment types.

[free780]

Yep. You need to get the MSP right. So manually test the install. You an specify the MSP in the command line. I cant remember the switch though. Then add the deployment type into SCCM. If you've got the chance to do this over the summer. It's a lot easier than in term.

[nelliott]

Hi All,

 

I've done some further testing within Windows it installs successfully from the command line, once you have allowed the UAC prompt, however, it does briefly flash up with the Office setup flash screen. I'm unsure if this can be hidden?

 

When it is included within the SCCM task sequence it still fails, could this be due to the UAC prompt?

 

Thanks,

[CAWJames]

Same for me on a windows 10 new build, works fine from command line, just hangs the task sequence when used as an app in the workflow Might just have to install it manually and capture it

[mullet_man]

I haven't tried to deploy it on any W10 devices as yet, but my W7 devices that I have pushed it out too I have UAC turned off.

 

In SCCM I think there is an option to install with the highest privileges, so that should work even with UAC on I would guess?

 

I followed this guide and everything has worked perfectly for me.

 

How to deploy office 2016 using SCCM 2012 R2

 

I have created a task sequence for my deployment as I want to run Office Scrub to remove 2013, then reboot and then install 2016. So far it's working great.

[nelliott]

Hi @mullet_man Would it be possible for you to screenshot your deployment settings for Office to see if they differ from what I am using?

[Arthur]

could this be due to the UAC prompt?

No.

 

By default task sequences always run by using the Local System account.

 

https://technet.microsoft.com/en-gb/library/gg712685.aspx

[mullet_man]

Hi @mullet_man Would it be possible for you to screenshot your deployment settings for Office to see if they differ from what I am using?

 

I've got this

 

 

 

Anything else?

[nelliott]

The only difference is i've got the run time set to 60mins instead of 120mins...

[mullet_man]

Did you copy everything from the link I posted?

[nelliott]

yeap - i followed the guide

[mullet_man]

Am not sure what is happening then, when you hit deploy in SCCM what happens on the client?

[nelliott]

when it is running windows and I install it through the software centre it works fine, it only fails when it is installed as part of the task sequence.

 

is there anyway of forcing it to install as soon as it boots into windows?

[mullet_man]

 

This is my task sequence, it works fine for me.

[nelliott]

could it be due to my task sequence is installing windows and then by using the office customization tool is removing any old versions before trying to install office 2016?

 

this is mine...

 

[mullet_man]

Am not sure what is happening to be honest I don't use SCCM to deploy out Windows I use MDT.

 

As a test add your restart computer above your Office install, I would guess the setup and configure step in your TS will require a restart if it's doing an updates or installing any features etc.

 

That's my hunch anyway.

[nelliott]

Thanks @mullet_man will give that a try and will report back

[mullet_man]

Thanks @mullet_man will give that a try and will report back

 

Fingers crossed :-)

[nelliott]

Well... after searching log files and google... i've finally got it working... it seems Office 2016 fails to install without .NET Framework v3.5 and v4...

[mullet_man]

Well... after searching log files and google... i've finally got it working... it seems Office 2016 fails to install without .NET Framework v3.5 and v4...

 

Ah oh well at least it's all sorted now. Glad you got it sorted.