Quantcast
Channel: Setup Deployment forum
Viewing all articles
Browse latest Browse all 2818

VAMT 3.1 and child domains problems

$
0
0

Hello,

Recently I have decided to upgrade from VAMT 2.1 to 3.1. on Server 2008 R2.

Previously with VAMT 2.1 everything worked fine. I have the correct DNS SRV record on all sub-domain DC's, and on the KMS server registry I have the DnsDomainPublishList populated with the child domains I need to have the workstations activated. So again with VAMT 2.1 it worked great.

However, since I have installed VAMT 3.1, I can't "Update License Status" on machines that are on a different domain than what the KMS server is on.

The error i receive is "Unable to connect to the WMI service on the remote machine.

If I use "Discover Products" by IP address of the respective machine on a child domain everything works fine. So this proves that something is clearly wrong with how VAMT 3.1 looks at the DnsDomainPublishList registry entry, or perhaps the registry entry should be changed to something else which has not been documented by Microsoft as of yet.

Note: VAMT 3.1 "Update License Status" works fine on machines which are on the same domain as the KMS server.

So my question is - What has changed in VAMT 3.1 DNS lookup for child domains to not work anymore?


Viewing all articles
Browse latest Browse all 2818

Trending Articles