Could a weird network error cause this, like a part of the image doesn’t make it to the computer?maybe the ethernet cables are just that old? The first time this happened I had discovered the machine was plugging into the network with a cat 5 cable and we just upgraded the switch to a gigabit switch, so I swapped it out with a newer cat 5e so it could image faster and that’s when I discovered after reimaging the problem was fixed. So why would sometimes office work perfectly fine and other times not so much. The quickest way to fix this is to just re-image it and then it works. In the event viewer there was some error about not being able to register to proof of purchase or something like that.

I tried to look at the cmid (client machine id) and it says it doesn’t exist. Tried a MAK key too that also is claimed to be invalid, but I know that both keys are valid.

I tried adding it in the command line with and without dashes to no avail. I tried to use ossp.vbs to manually install the GVLK kms client key and it says the key is invalid. I played with the office ossp.vbs activation tool to manually add the kms host and port and attempted to activate but it keeps claiming no key is installed. If I go to the kms server and look at VAMT, I can add the host and update the license status and the kms server successfully activated windows 10 no problem but it doesn’t even see Office 14 (2010) as an activated device. It pops up and then after a second or two it pops up an error about office activation failing and a repair attempt failed (the office 2010 setup splash screen pops up and disappears right before that) But then I try to open any Microsoft Office 2010 program. I image the computer and all seems to go well. It’s only happened 3 times out of the last 13 computers imaged in the last few weeks, but 2 of those were yesterday. So I have been having a really weird problem recently. TL DR - After imaging office 2010 fails to activate and can’t be activated, is fixed by re-imaging.

Kms office