Hi,

I am in the final stages of testing our new Win 7 x64 SOE.

Office 2013 has been preinstall onto the WIM. 

It is pushed out via SCCM 2012 R2.

Our issue is it appears to take office a while to active against KMS. The issue arises, as the first thing people do once logging into their new machine is open Outlook which then prompts them to activate. If they ignore it and move on Office activates itself without issue.

I have tried forcing the activation of windows embedding the command into a windows startup script (below) however that doesn't appear to work.

if exist C:\Windows\OfficeActivated.txt goto _OfficeActivated
cscript "C:\Program Files (x86)\Microsoft Office\Office15\ospp.vbs" /act
copy NUL C:\Windows\OfficeActivated.txt
:_OfficeActivated

I am either looking to force an activate that works or simply finding a while to hide the not activated message as I know it will later in its own time.

Any ideas would be great.

C

Hi,

Based on the description, there seems to be something that stops Office from being activated at the very beginning, but later Office will be activated fine.

The first thing that may interfere with the activation is some background programs, please perform a clean boot to check if the issue persists.

In addition, there may be something that takes a lot of network traffic, causing the client not able to respond to the KMS host temporarily. We can try to monitor the network traffic with some tools, such as Network Monitor to verify this.

Regards,

Melon Chen
TechNet Community Su

Hey Melon,

This is the first boot after being imaged so performing a clean boot isn't an option for me as I cant let that be the solution.

Ideally just being able to hide the activation message would solve my issue.

There was a Event Viewer message showing an error but cant find it at the moment. Will post once I can get it.

Cheers,

Zac

Hi,

Any update upon this issue? If you have the error message, please feel free to post it here.

Regards,

Melon Chen
TechNet Community Su

Hi,

I could never get it working so gave up.

At the end of the SCCM Task Sequence I did have the machine turning off. Now I just leave it on and it activates by itself as it has more time sitting there doing nothing.

Cheers,