Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

kms server woes for volume activation of Windows 7 / Office 2010. Advi


  • Please log in to reply
21 replies to this topic

#1
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Hi

In our organization we do not have active directory and we have over 1000 computers on the network. We are trying to setup a KMS server for volume activation for are Windows 7 and Office 2010 products. We have run into a snag.

The issue is as follows, when we use the vamt tool to discover new pc's it doesn't discover any pc's when we point it to the workgroup they are located in. Obviously we do not want to manually enter the ip of each pc, because all the pc's.use dhcp.

Can anyone point me into the right direction as to why the VAMT tool isn't discovering any new pc's when we point it to the workgroup all our pc's are located in?. Is there a setting on the server or client machine I need to look for to make this happen?.

Right now, we are testing the vamt tool on a windows 7 station, do we need to be using Windows 2008 server r2 for the vamt tool to work correctly?.

Edited by clivebuckwheat, 22 September 2010 - 02:38 PM.



How to remove advertisement from MSFN

#2
myselfidem

myselfidem

    Member

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,559 posts
  • Joined 06-January 10
  • OS:Windows 7 x64
  • Country: Country Flag
Hello!
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

Type: DWORD

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
KMS Activation
Regards

Edited by myselfidem, 22 September 2010 - 04:03 PM.

For Windows 7 OS: SetProductKey.rar (fr-FR/en-US. Integrate keys).

#3
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
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?


Hello!
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

Type: DWORD

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
KMS Activation
Regards


Edited by clivebuckwheat, 22 September 2010 - 07:23 PM.


#4
myselfidem

myselfidem

    Member

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,559 posts
  • Joined 06-January 10
  • OS:Windows 7 x64
  • Country: Country Flag
Hello!
I read inside VAMT 1.2 Help

Overview
The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Microsoft Windows volume activation process. The VAMT can manage volume activation using Multiple Activation Keys (MAKs) or the Windows Key Management Service (KMS). You can install this tool as a stand-alone application on any computer that has one of the following Windows operating systems: Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008R2.

Important: The VAMT is designed to manage volume activation for Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008R2. Computers installed with volume editions of Windows XP or Windows Server 2003 cannot be managed using the VAMT.


Key Management System (KMS) activation: use the VAMT to configure client computers for KMS activation. KMS client keys are the default product keys used by Volume License editions of Windows Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008R2.



What's New in Group Policy
How to configure RPC dynamic port allocation to work with firewalls
For Windows 7 OS: SetProductKey.rar (fr-FR/en-US. Integrate keys).

#5
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Thanks Myselfidem, but every time I do a search via workgroup using the VAMT TOOL. Nothing shows up, but if I manually type in the ip of a computer or the computer name into the vamt tool it will find the computer. Would you know of what I have to do to be able to use the search by workgroup feature in the VAMT?



Hello!
I read inside VAMT 1.2 Help


Overview
The Volume Activation Management Tool (VAMT) enables network administrators and other IT professionals to automate and centrally manage the Microsoft Windows volume activation process. The VAMT can manage volume activation using Multiple Activation Keys (MAKs) or the Windows Key Management Service (KMS). You can install this tool as a stand-alone application on any computer that has one of the following Windows operating systems: Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008R2.

Important: The VAMT is designed to manage volume activation for Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008R2. Computers installed with volume editions of Windows XP or Windows Server 2003 cannot be managed using the VAMT.


Key Management System (KMS) activation: use the VAMT to configure client computers for KMS activation. KMS client keys are the default product keys used by Volume License editions of Windows Windows Vista, Windows 7, Windows Server 2008 or Windows Server 2008R2.



What's New in Group Policy
How to configure RPC dynamic port allocation to work with firewalls



#6
myselfidem

myselfidem

    Member

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,559 posts
  • Joined 06-January 10
  • OS:Windows 7 x64
  • Country: Country Flag
Hello!

Note: To discover VAMT-manageable Windows computers in workgroups, you must enable network discovery on each client.


Regards
For Windows 7 OS: SetProductKey.rar (fr-FR/en-US. Integrate keys).

#7
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
how would I do this on windows 7 and xp stations?

Hello!


Note: To discover VAMT-manageable Windows computers in workgroups, you must enable network discovery on each client.


Regards



#8
myselfidem

myselfidem

    Member

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,559 posts
  • Joined 06-January 10
  • OS:Windows 7 x64
  • Country: Country Flag
Hello!
You can find some help here:
http://www.howtogeek...-windows-vista/
http://www.howtogeek...ndows-7-and-xp/
http://www.intel.com...tween-computers
For Windows 7 OS: SetProductKey.rar (fr-FR/en-US. Integrate keys).

#9
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Network discovery is file and print sharing in XP?


Hello!
You can find some help here:
http://www.howtogeek...-windows-vista/
http://www.howtogeek...ndows-7-and-xp/
http://www.intel.com...tween-computers



#10
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • Joined 09-September 01
  • OS:Windows 8.1 x64
  • Country: Country Flag
Network discovery is a firewall rule set in Vista and Win7, so if you go looking for it you won't find it. Basically, it's an amalgamation of firewall rules for allowing in (on a Vista/Win7 machine) Link-Layer Topology Discovery (LLTD), Netbios, Functional Discovery Resource Publication (FDRP), Universal Plug-and-Play (UPnP), and Web Services for Devices (WSD) requests. Windows XP obviously doesn't have FDRP or WSD at all, nor LLTD by default - but you *can* install the LLTD listener for XP by installing the update in 922120 (you should do this on any mixed networks where XP and Vista or Win7 will co-exist).

However, if VAMT isn't discovering your machines and you're *in a workgroup setting*, you need to have both netbios and LLTD working - otherwise, you won't find anything (DNS isn't a broadcast medium, so LLTD and netbios are used for discovery).
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#11
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Thank you sir i will try, and let you know.

Network discovery is a firewall rule set in Vista and Win7, so if you go looking for it you won't find it. Basically, it's an amalgamation of firewall rules for allowing in (on a Vista/Win7 machine) Link-Layer Topology Discovery (LLTD), Netbios, Functional Discovery Resource Publication (FDRP), Universal Plug-and-Play (UPnP), and Web Services for Devices (WSD) requests. Windows XP obviously doesn't have FDRP or WSD at all, nor LLTD by default - but you *can* install the LLTD listener for XP by installing the update in 922120 (you should do this on any mixed networks where XP and Vista or Win7 will co-exist).

However, if VAMT isn't discovering your machines and you're *in a workgroup setting*, you need to have both netbios and LLTD working - otherwise, you won't find anything (DNS isn't a broadcast medium, so LLTD and netbios are used for discovery).



#12
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
I got the search by workgroup working, but I am still not out of the woods yet.The machine that the VAMT tool was installed on didn't have Netbios over tcp/ip enabled. Once I enabled it the search worked by workgroup using the vamt tool.

My next issues are below,

I have a couple of issues that I am hoping will be answered here.

1. To have clients connect to my kms server and auto activate. I need to use one KMS key for Office 2010 and one KMS key for Windows 7?. is this correct?. From the research I have done Office 2010 and Windows 7 can be hosted on one kms server as long as I have the proper kms keys? which I plug into the server. Is this correct?

2. Do I still need to use an activation script in my post configurations after imaging to connect to the kms server?, or is there somewhere on the client pc's I need to point it to the kms server?

Thanks for all the great assistance and advice.

#13
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • Joined 09-September 01
  • OS:Windows 8.1 x64
  • Country: Country Flag
#1 - Auto activation should work if your KMS is discoverable. The VAMT docs should have guided you through that setup, but if not, it's always easily found on Technet.

#2 - No, KMS is auto activation (both Windows and Office) as long as you meet the minimum number of activations and the KMS server is discoverable by hosts on the network (which ties back to #1). You don't have to do anything (you can, but you don't have to).
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#14
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
I have gotten the search working via workgroup, but I have a lot of unknown fields in my machine list. When I say use current credentials within the VAMT tool . I get the following error "Unable to connect to wmi service on remote client"

Is there anything I must do on the clients to have them populate the data fields in the VAMT tool.

See attached screen shot.Attached File  VAMT Tool.jpg   196.15KB   13 downloads

#1 - Auto activation should work if your KMS is discoverable. The VAMT docs should have guided you through that setup, but if not, it's always easily found on Technet.

#2 - No, KMS is auto activation (both Windows and Office) as long as you meet the minimum number of activations and the KMS server is discoverable by hosts on the network (which ties back to #1). You don't have to do anything (you can, but you don't have to).



#15
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • Joined 09-September 01
  • OS:Windows 8.1 x64
  • Country: Country Flag
Connecting to remote WMI means you must allow remote WMI management, and the account connecting to the remote machines must have access in DCOM (dcomcnfg) and WMI (wmimgmt). Also, if the firewall is enabled, you must enable WMI traffic through the firewall as well.
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#16
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Cluberti, a couple more questions

1. When you say the account connecting to the remote machines must have access to DCOM and WMI. Do you mean the local account on the client pc's or the account on the server?

2. The dcom service is on, on my xp clients, as well as the wmi service

3. The firewall is off on the clients trying to connect to the VAMT tool

I am still getting access denied, when I say use current credentials in the VAMT tool. Can you suggest anything else. As always thanks for everything you have been a great help to me in learning all this.



Connecting to remote WMI means you must allow remote WMI management, and the account connecting to the remote machines must have access in DCOM (dcomcnfg) and WMI (wmimgmt). Also, if the firewall is enabled, you must enable WMI traffic through the firewall as well.

Attached Files


Edited by clivebuckwheat, 02 October 2010 - 10:38 AM.


#17
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
I still seem to be getting access denied it has to be a wmi problem. I have scoured the net and tried many solutions. Does anyone have any advice, to point me into the right direction.

#18
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Solved.

#19
cluberti

cluberti

    Gustatus similis pullus

  • Supervisor
  • 11,252 posts
  • Joined 09-September 01
  • OS:Windows 8.1 x64
  • Country: Country Flag
Sorry, have been out of town and haven't been back to see your responses since my last post. Mind re-posting what you did to resovle it?
MCTS Windows Internals, MCITP Server 2008 EA, MCTS MDT/BDD, MCSE/MCSA Server 2003, Server 2012, Windows 8
--------------------
Please read the rules before posting!
Please consider donating to MSFN to keep it up and running!

#20
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Thank god your back. I spoke to soon, I will post where I am in the process. Maybe you can help me shed some light on my error / lack of knowledge in this kms debacle

Sorry, have been out of town and haven't been back to see your responses since my last post. Mind re-posting what you did to resovle it?



#21
clivebuckwheat

clivebuckwheat

    Senior Member

  • Member
  • PipPipPipPip
  • 577 posts
  • Joined 07-November 05
Can we backup a moment, so you can verify my progress to make sure I haven't forgotten anything that is glaring. This server is going to have a dual role has a Windows 7 and Office 2010 kms volume activation host.

For Windows 7 activation piece of kms host

1. I got a KMS key from my supervisor for Office 2010, and Windows server r2 2008. Do I also need a kms key for the windows 7 clients I want to activate?

2. I activated the kms server with the kms key for Windows 2008 r2

For Office 2010 piece of kms host

1. I installed the office 2010 volume license pack host utility from Microsoft and entered the kms key for office when it asked

2. To activate the KMS Host type "cscript slmgr.vbs /ato bfe7a195-4f8f-4f0b-a622-cf13c7d16864" (That number is the Office 2010 activation ID and is required)

3.On the client computer open an elevated command prompt and type "cscript ospp.vbs /sethst:<Hostname or IP of your KMS Host>" This will identify the KMS host to your client.

4.To activate the client manually type "cscript ospp.vbs /act" and as long as the default KMS client key is still installed this will activate your client using your KMS host. I get the message kms server doesn't meet the minimum requirements message... This is normal I am aware.

5. After step 4, on the server I type in the following command in an elevated command prompt on the server cscript slvmgr.vbs /dlv and the client requests are still at 0?. I have learned that for Office 2010 there is a minimum of 5 clients required and a minimum of 25 Windows 7 clients required. Shouldn't have the client count at least changed from 0 to 1?.

6. The installs on my master image of Office 2010 and Windows 7 have been registered using a MAK Key, so must I entered in a kms key on the clients for Office 2010, and Windows 7 for the kms server "happy"?

Is there no commands to test out on the client pc's running windows 7, is there some commands that I can type on the client pc's to ensure they are communicating with the server correctly?

#22
tectron1

tectron1
  • Member
  • 1 posts
  • Joined 27-January 12
  • OS:none specified
  • Country: Country Flag
Hello guys,

I've now readen the whole topic and it seems very interesting what you're doing here. Especially because we have here more or less the same situation as clivebuckwheat. also novell network. no AD, KMS, Win7, Office 2010, and so on.

First of all a very good advice in the whole KMS story is to check the event log of the server (Windows logs -> applications and service logs -> Key mangement server). There you can see when machines getting registered on your KMS server.
I found out, that the KMS GUI is not as useful as it should be.
Another good thing to check your acitvation status is the command "slmgr /dlv" (run on KMServer) you'll get a popup window with some infos in it. (here also the way to understand this information:http://technet.microsoft.com/en-us/library/ee939272.aspx [take a look at the explanation of the point "current count"]


In our network, we have different networks (which are all routetd). (For the swiss people in here: I'm situated in ZH, and we have branch offices at GE, LS, SG, BE) All the machines from the branch offices do activate perfectly at the KMS server, but the VAMT doesn't discover the machine. Probably because it's searching over workgroup, and that won't work over network-boarders. The other possibilities (like LDAD, AD, or manual IP-entering) won't work for me, because we have no LDAP Directory with the machines or AD, and the IP's are from a DHCP, so they will change.
How would you guys try to discover the machines in the branch offices? Do you have any good idea?

Thanks for reading! :-)
kind regeards,
Tec

PS: If I can help, ask me ;-)

Edited by tectron1, 27 January 2012 - 03:59 AM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN