Hi all,

I have a problem with office 2013 activation through KMS in my VDI environment.

I have installed template VM with office 2013 and did office rearm before sysprep the image. After that I have created more than 5 new VM's and I saw that Office is not activated.

When I run ospp.vbs /act I've got an error 0xc004f038 means that count is insufficient. I checked 12290 events on my KMS and saw that I have identical CMID's for different VM's in that time when I tried to activate office.

I tried to rearm office again but I saw new error 0xc004d307 meaning that maximum allowed number of re-arms has been exceeded. This is very strange because I have rearmed just once before I did sysprep VM template.

How can I solve this problem with Office activation?

• Edited by Sergey Stepanov Wednesday, July 10, 2013 8:21 AM

Update:

I have also tried to use cscript ospp.vbs /rearm:{SKU ID} and got "Microsoft Office rearm successful." But still not activating and CMID's for Office are still same (now I'm using VAMT to check office license status info).

• Edited by Sergey Stepanov Wednesday, July 10, 2013 8:32 AM add more info

I know this is almost a year ago but I'm having similar issue after installing the office 2013 SP1.

Before installing the SP1, everything was working great. No duplicate CMIDs.

I'm currently have an open case with Microsoft and they realized that SP1 broke many things.

I do curious if you have solved your issue? What did you do?

My temporary fix right now is to install Office 2013 only without SP1.

I tried a fresh install of Office 2013 w/ SP1 included and it didn't work. Got duplicate CMIDs on the cloned machines. I'm using VMware View as well.

Hi,

we have the same problem: We have reached maximum rearm count for Office 2013 and I don't know to solve this.

Both "cscript ospp.vbs /rearm:{SKU ID}" and ospprearm.exe return 0xc004d307 error

we are using VDI in a BOX.

Do you have solved your issue?

Thanks

I am having the exact same issue in a VDI environment and have applied all of the steps provided here. Were you ever able to resolve this issue?

Thanks,

Chris

The best thing is to Open a Support Case with Microsoft from their support website. It's FREE.

You will need to put in the payment information and pretend that you are going to pay for it first.

It's normal. Don't bother calling in. Submitting online is the fastest way.

Make sure on the subject or description you put in KMS issue and they will refund you the money once the case is solved.

I'm sorry I don't remember what we did (we did a lot of troubleshooting) but we ended up fixing the problem.

I believe it was just something simple that we need to do prior to cloning the desktop.

Good luck.

I am having the exact same issue in a VDI environment and have applied all of the steps provided here. Were you ever able to resolve this issue?

Thanks,

Chris

An important step which is sometimes overlooked, you must *NOT* launch any Office2013 application/component after you perform rearm.

eg if you ospprearm, then immediately sysprep, shutdown, capture, that's fine.

But if you ospprearm, then switch users or logoff/logon or run any Office component, and then you sysprep, it's too late the damage is done.

This happens, because the execution of ANY Office app/component will cause the CMID to generate. If you then sysprep, you are capturing the CMID, which causes this exact problem.