Thank you, I still seem to be having majors issues with the VAMT tool. Any advice would be of great assistance.
I did the test you suggested on a windows xp workstation I added the regkey to a machine in one of my labs and did a search on that specific workgroup the machine resides in, and it didn't find the machine.
I have a couple of questions hopefully someone can shed some light upon
1. We are on a Novell Network with no active directory to speak of, can we still setup a kms server, using the vamt tool for volume activation for Office 2010, and Windows 7?
2. We have a mixture of Windows xp and Windows 7 clients both have office 2010.If we get the ip of a station and manually type it into the vamt tool it seems the windows 7 machines are found but not the Windows XP stations, any advice as to why this is happening?
3.It seems I am still unable to search using the VAMT tool by workgroup. Does this functionality require active directory?
4. The firewall is disabled on all clients I am trying to discover using the VAMT tool.
5. Does windows xp have the network discovery feature?, if so where?, could that be the reason why I can't discovery any stations using a workgroup search with VAMT?
6. Right now I am doing my test with the VAMT tool installed on a Windows 7 workstation, do I have to use Windows server 2008 r2 for my testing?
myselfidem, on 22 September 2010 - 03:19 PM, said:
WAMT 1.2 is a part of WAIK for Windows 7. You can find some help inside "WAMT 1.2 Help" file.
Create a registry value for the VAMT to access workgroup-joined computers
Important: This section contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, refer to the following Microsoft Knowledge Base article: http://support.micro....com/kb/256986.
On the client computer, create the following registry key using regedit.exe.
Navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system
Enter the following details:
Value Name: LocalAccountTokenFilterPolicy
Value Data: 1
Note: To discover VAMT-manageable Windows computers in workgroups, you must enable network discovery on each client.
Configure Windows Firewall to allow VAMT access across multiple subnets
This post has been edited by clivebuckwheat: 22 September 2010 - 07:23 PM