![]() ![]()
This helps you to find computers which were not yet activated. VAMT groups computers automatically according to their licensing status. However, it collects many more information which is stored in an XML file for further processing. #Volume manager vista licenseVAMT displays information like the key type, license status, grace expiration date, installation ID and pending conformation ID. Since VAMT contacts all computers of the selected group simultaneously this might not be a big problem, though. If a computer isn't online, then VAMT will wait for several seconds. The retrieval process is relatively slow. You can do this manually by enabling the corresponding exception in the Control Panel Firewall configuration tool or by using Group Policy. If you have Vista's firewall enabled, you have to allow WMI inbound connections. You can do this for each computer individually or for a computer group. Why isn't VAMT able to list AD containers?Īfter collecting all Vista machines, VAMT will retrieve their licensing status by connecting to them thru WMI (Windows Management Instrumentation). This, certainly, is a very strange way to group computers. VAMT will then only retrieve those computers from AD which contain this string. For this, you have to specify a string as filter for the computer name. #Volume manager vista windowsall other Windows versions were excluded. VAMT listed only the Vistas machines in our domain, i.e. I also was able to collect the licensing information without disabling UAC on the Vista clients.Īt least, I had my first sense of achievement. This time, I installed VAMT on a physical Windows Server 2003 SP1, et voilà, it was able to gather all Vista machines in our Windows domain thru Active Directory. In the tests, described above, I always used virtual machines under VMware Workstation. I couldn't believe that Microsoft delivered such an important tool with so many bugs. #Volume manager vista codeMaybe, Microsoft should offer yet another tool which looks up the error messages of the error code look up function? The error code tool displayed another error message: Access denied. Anyway, this error code look up didn't work either. I wonder why the error message doesn't simply deliver the explanation for the error code. VAMT has a funny feature which allows you to look up the error codes. I, then, installed VAMT on a domain controller. But whenever I added client computers using the AD option, I got an error message with the error code 0x8007003A. This way, you don't have to add all your clients, manually. In theory, VAMT should gather the computer names from Active Directory. I, then, installed VAMT on a member server of a Windows domain. It is only after I disabled UAC altogether, that VAMT was able to collect the activation status. However, in my test adding the registry key didn't solve the UAC problem. In my view, it is very strange that one has to mess with the registry on all client machines to work with VAMT if you are not using Active Directory. According to the manual, a registry key (LocalAccountTokenFilterPolicy) must be created to enable remote administrative actions under UAC. #Volume manager vista manualI followed the manual line by line, but in my test VAMT always failed to collect the status of my test computers with the error code 0x80070005.Īfter a while, I figured out that UAC (User Account Control) is the reason. ![]() With the first option, you have to specify IP addresses, manually. VAMT offers three ways of collecting Vista machines in your network: by IP address, thru search in Active Directory and thru search in a Workgroup. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |