none
Software Protection Platform for Office 2010

    Question

  • HI All. I’m about to start rolling Office 2010 Pro Plus out to our European user base of around 500 machines. I’ve got the KMS key as well as the KMS host exe but being the first time using KMS I’m not sure how to set it up correctly.


    I’ve got a Server 2003 box it can sit on because it won’t work on 2008 Data Centre but when I run the exe is says Software Protection Platform is not installed. I’ve searched everywhere for information about this and I get whats it for but I can’t find anywhere to download it.


    I would appreciate some help urgently as we need to roll this out to a number of users as a matter of urgency.

     

    Thanks

    Monday, June 28, 2010 2:49 PM

Answers

  • To give you an idea of what goes on under the hood... :-)  Office installs OSPP (Office Software Protection Platform) because we support W7, Vista, and WinXP.  That means the OSPP you have on W7 is the same as on WinXP, because Office installed it.  You can run the same ospp.vbs /act and /sethst commands on whatever OS Office is installed on.

    On the other hand, there's a separate SPP service for Windows Vista, and a slightly different one on W7.  WinXP does not have SPP.  We're working to put it all together, but because of downlevel OS support requirements, Office needs to install its own OSPP.

    You may need to run rearm on your WinXP Office installations.  If you ran ream on the two PCs, then their CMIDs should be reset.


    Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office
    • Marked as answer by Sally Tang Thursday, July 01, 2010 8:23 AM
    Wednesday, June 30, 2010 7:59 PM

All replies

  • Here's a go step-by-step guide for setting up a KMS host:

    http://technet.microsoft.com/en-us/office/ee470514.aspx

    Note that this link is to set up a Beta KMS host, but you can still follow the steps.  Just use the updated KMS host exe file and your KMS host key.  The activation ID for the RTM version is:

    bfe7a195-4f8f-4f0b-a622-cf13c7d16864


    Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office
    Tuesday, June 29, 2010 12:00 AM
  • Hi Ted. Thanks for the guide, it worked a treat. I wasn’t prompted to input any activation code other than the KMS key, but it did say everything was activated. So now do I just install 2010 on 5+ PCs and they should activate automatically, is that right? As said above I’ve not used KMS before.

     

    Thanks


    Adam

    Tuesday, June 29, 2010 8:03 AM
  • Great to hear!  On your KMS host, check to see that your Office key has been activated with this command:

    cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864

    The easiest thing to do is make sure your KMS host is correctly registered on DNS:

    http://technet.microsoft.com/en-us/library/ee624357.aspx#section3

    That way when you install your Office 2010 clients, they will look to DNS to find the KMS host and activate with it.

    If you want to specify the KMS host name in your client computers, you can use ospp.vbs /sethst:

    http://technet.microsoft.com/en-us/library/ee624350.aspx


    Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office
    Tuesday, June 29, 2010 5:59 PM
  • Thanks Ted. I had to copy the slmgr.vbs to the root of C so it could be ‘found’ by the cscript. The output is below:

     

    Name: Office(TM) 14, ProPlusKMSHost edition

    Description: Office(TM) 14 KMS, VOLUME_KMS channel

    Activation ID: bfe7a195-4f8f-4f0b-a622-cf13c7d16864

    Application ID: 59a52881-a989-479d-af46-f275c6370663

    Extended PID: 55041-00096-199-140247-03-1033-3790.0000-1812010

    Installation ID: 020901550771284990104892301832775560364556748382133773

    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78937

    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78938

    Use License URL: http://go.microsoft.com/fwlink/?LinkId=78940

    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkId=78939

    Partial Product Key: 3FFR8

    License Status: Licensed

     

    Key Management Service is enabled on this machine

        Current count: 3

        Listening on Port: 1688

        DNS publishing enabled

        KMS priority: Normal

     

    I’m assuming this is all correct?

     

    There was one other thing, I have run the command cscript ospp.vbs /sethst:<KMSHostIP>

     

    I get the message saying ‘Successfully Applied Settings’ I know I can’t use the cscript ospp.vbs /act until I have a count of 5 on the KMS server. Thing is I have built 4 PCs from ghost images with Office 2010 and run the above command but the count doesn’t seem to be going up, do it take time to do this?

     

    Thanks for your help

     

    Adam

    Wednesday, June 30, 2010 3:12 PM
  • Hi Adam,

    The slmgr.vbs script is in the C:\Windows\system32 folder, so if you go there in the command prompt, you can directly run the cscript slmgr.vbs commands.

    It looks like your KMS host has been successfully activated!  The next part is to build up the count.  Your Current count is 3, but it needs to get up to 5.  If you're not seeing the count go up, you may need to run rearm first on the client machines:

    http://technet.microsoft.com/en-us/library/ee624357.aspx#section4

    Run rearm, then try ospp.vbs /act from all your client computers again.  You can run ospp.vbs /act as many times as you want... it'll just send a request to the KMS host to activate.

    Make sure you run rearm first before you capture your image if you're deploying images to your environment.  That way they all have unique CMIDs.

     


    Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office
    Wednesday, June 30, 2010 4:42 PM
  • Thanks Ted. I’ve only deployed the image to two PCs so far so if I run rearm on those two should their CMIDs be reset? At the moment I’m guessing they will be the same.

     

    We’ve installed 2010 (upgrade from 2003) on a number of XP machines to and the count again doesn’t seem to be going up, I know XP doesn’t have OSPP so is there a way of forcing it to route out the KMS server in the same way I run cscript ospp.vbs /sethst <KMSHostIP> on a Windows 7 box?

    Thanks

     

    Adam

    Wednesday, June 30, 2010 7:24 PM
  • To give you an idea of what goes on under the hood... :-)  Office installs OSPP (Office Software Protection Platform) because we support W7, Vista, and WinXP.  That means the OSPP you have on W7 is the same as on WinXP, because Office installed it.  You can run the same ospp.vbs /act and /sethst commands on whatever OS Office is installed on.

    On the other hand, there's a separate SPP service for Windows Vista, and a slightly different one on W7.  WinXP does not have SPP.  We're working to put it all together, but because of downlevel OS support requirements, Office needs to install its own OSPP.

    You may need to run rearm on your WinXP Office installations.  If you ran ream on the two PCs, then their CMIDs should be reset.


    Ted Way [MSFT], Program Manager, Microsoft Office: Enterprise Licensing, Group Policy, and 64-bit Office
    • Marked as answer by Sally Tang Thursday, July 01, 2010 8:23 AM
    Wednesday, June 30, 2010 7:59 PM
  • Thanks Ted. I’ve now successfully activated 8 clients although I have to manually force through the host IP it is working.

     

    Thanks a lot for your help

     

    Adam

    Thursday, July 01, 2010 2:36 PM