![]() Under the "Default Properties" tab, ensure that "Enable Distributed COM on this computer" is checked. In the tree navigate to "Component Services" -> "Computers" and right click "My Computer" and choose properties. You'll need to log in to one of the machines that is giving you access denied, from there run "dcomcnfg" We should also confirm that DCOM is enabled and that the Remote Activation permissions are set. Is your domain administrator also a memeber of the local administrators group on the remote machines? Ok so since you are unable to connect using slmgr.vbs and wbemtest, this indicates there is a DCOM permissions issue in the environment rather than a problem with VAMT itself. VAMT Update Status for the functional machine returns "Windows(R) 7, Enterprise edition - Successfully updated the product info" All rights reserved.Ĭ:\Windows\System32>cscript slmgr.vbs /dlv machinename Microsoft (R) Windows Script Host Version 5.8Ĭopyright (C) Microsoft Corporation. Slmgr.vbs gives slightly different resultsĬ:\Windows\System32> cscript slmgr.vbs /dlv machinename Unfortunately that machine is not a producton deployment, so we still need figure out why. I and others are able to query license status using our current credentials. VAMT installed on another Windows 2008 R2 server works just fine. Sorry to take so long getting back to you, but my notifications for updates to my threads are no longer reaching me. ![]() Update: Enabling the Administrator account on the remote client and using "alternate credentials" to connect works around the problem (along with enabling the firewall exception previously referred to). When I get more time I am going to enable the remote and local Administrator account and try connecting with those credentials again.Īny other ideas apart from the ones covered? Using the slmgr check returns the same licencing server error message about the product code being missing whether to a real remote client or a made up one.Īt least VAMT gives a few signs of partially working, if I try to connect with the disabled administrator account I get a message about not being able to connect to the WMI service rather than the "Access Denied" message I get with other admin equivalent If there is an "E" in the Attributes column for that file, the file is encrypted.I am experiencing the same issue with Windows 7 Enterprise clients, I have tried all of the suggestions here and on other postings yet the remote clients refuse to have their status updated.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |