This concerns volume activation of MS Office 2010.
We've installed MS' Volume Activation management Tool (VAMT) v220.127.116.11. on a W7 machine that also runs as a KMS host specifically for Office 2010. We have another KMS host machine in the domain on a server 2008 box that activates W7 - this is not particularly relevant to the problem at hand, just background info.
VAMT runs OK and finds all our AD machines. When I run "UpdateStatus" from VAMT it finds and reads all my servers OK and it also reads a very small number of PCs OK, the majority of PCs however generate the following error:
On a remote PC:Unable to connect to the WMI service on the remote machine
I've checked that the WMI service is running
I've enabled DCOM - "Enable Distributed COM" is checked on the Default Properties tab, Default Auth level is Connect and Default Impersonation level is Identify. Com Security Launch and Activation permissions have all four tick boxes checked for the "Everyone" user under "Edit Limits"
I've turned Windows Firewall off on the VAMT / KMS host and the remote PC
And still I get the "Unable to Connect to the WMI Service" error.
VAMT is OK, or it must be as it finds and reads the servers and a small number of PCs OK.
I have the same problem - can't for the life of me get the management console to communicate to ANY of the detected machines without this error.
There are currently 1 users browsing this thread. (0 members and 1 guests)