Yes to both questions. About the only thing that goes wrong with this game
plan is if the KMS service on the Windows 2008R2 box doesn't create the
necessary _VLMCS DNS SRV record or another host in your site ends up owning
it for some strange reason (e.g. you activate two or more Windows 7/Windows
20008R2 boxes with a KMS key).

If you end up in the later part with two or more Windows 7/Windows 2008R2
installed/activated with a KMS key, you can disable the registering the SRV
record in DNS by using SLMGR.VBS. This way you can ensure that your VM is
the responsible KMS host for your site and not anything else accidently or
otherwise installed with a KMS key.


"IDS" wrote in message
...
I like the idea of creating a Windows 2008 R2 VM for the KMS host. Just to
make sure I understand... So, if I wanted to do this, I would just create
a
Windows 2008 R2 virtual machine and activate it using our Windows 2008 R2
KMS
key? After that I run the Office 2010 KMS license pack on the KMS
server?
Office 2010 clients will then be able to activate?

Thanks again


"neo" wrote:

You didn't specify if your domain controller is a Windows 2003 or Windows
2008R2 server. If it is a Windows 2003/2003R2 with SP2, you need to
download and install the KMS host software. You need two packages.

http://www.microsoft.com/downloads/d...displaylang=en

and

http://www.microsoft.com/downloads/d...displaylang=en

You install KMS 1.1 and then apply the update (968915)

Reboot

Then run the Office 2010 KMS license pack exe and supply your key.

Not sure how big your site is, I'm working in a site that is 4500 devices
and we find that a dedicated KMS host (it is virtualized) that activates
Windows 7, Windows 2008R2, and Office 2010 will be perfect for us.

Just so you know, we dedicated a Windows 2008 R2 server to be our KMS
host.
We activated the server with our Windows 2008 R2 KMS key. This in turn
automatically made it a KMS host that could activate Vista, Windows 7,
Windows 2008, and Windows 2008 R2. Just had to run the Office 2010 KMS
license pack on the Windows 2008 R2 host (and still waiting patiently for
our RTM KMS key for Office 2010).

Other than that, I don't see a problem running the KMS host on a domain
controller. Should work fine for smaller sites since your devices will
only
check in once every 7 days. I don't think I missed anything, but you
might
find this helpful.

http://technet.microsoft.com/en-us/l...ffice.14).aspx


"IDS" wrote in message
...
Thanks Neo.

I do not have a KMS server. I was reading that KMS can run on a domain
controller without any problems. So I was planning to use a DC as a
KMS
server. Do you see this as a problem?

Do I run KeyManagementServiceHost.exe on the server that I want to be
the
KMS server?

Thanks

"neo" wrote:

Do you already have a KMS server established for Windows 7/Windows
2008
R2?

If yes to the above, is the KMS server installed on Windows 2003,
Windows
7,
or Windows 2008R2? Reason I ask is that KMS on Vista & Windows 2008
isn't
supported.

If you do have a KMS server established for Windows 7/Windows 2008 R2,
you
can extend your KMS host using:

http://www.microsoft.com/downloads/d...5-fdc21fe8d965

As soon as you run this, you will need to supply your Office 2010 KMS
host
license key.

What else... oh, the ProPlus version that was made available on 4/22
to
MSDN/TechNet isn't a volume license edition. It is a retail copy.
Therefore you will need to get the VL edition from your SA download
area
which may go live today based on postings around the web.




"IDS" wrote in message
...
I want to start testing Office 2010 for a rollout in the upcoming
months.
What are the steps to setup a KMS server for Office 2010?

Thanks!

.


.