MS Office 2010 Activator Archives

MS Office 2010 Activator Archives

MS Office 2010 Activator Archives

MS Office 2010 Activator Archives

Office 2010 activation - How to rearm Office 2010

Office 2010 activation is a new topic that many users and admins face. This article explains how you can activate Office 2010 and rearm Office 2010.
Michael Pietroforte is the founder and editor in chief of 4sysops. He has more than 35 years of experience in IT management and system administration.
Latest posts by Michael Pietroforte (see all)

Update: If you have to rearm Office 2013 SP1, please read my updated article. Things are quite different with Office 2013.

This article explains how you can rearm Office 2010 and for what you need this feature.

Office 2010 is certainly the best Office suite out there. However, compared to Office 2007 it has one major drawback: Like Vista and Windows 7, Office 2010 has to be activated. However, Office 2010 behaves a little different than Windows if it is not activated. Rearming Office 2010, that is resetting the grace period, works similar as rearming Windows.

Office 2010 Reduced Functionality Mode ^

Retail versions of Office 2010 will only run in Reduced Functionality Mode (RFM) after the grace period of 30 days has been exceeded. In RFM Office, documents can only be viewed but not modified.

Volume editions of Office 2010 don't have an RFM. However, Office will start nagging users with messages after 25 days. You can just imagine how many helpdesk calls it will provoke if you don't ensure that Office 2010 has been activated during this grace period.

Activating Office 2010 ^

You can use the latest version of the Key Management Host (KMS) or activate Office 2010 with VAMT. Either way shouldn't be doable within 25 days after the installation.

However, it might be difficult to activate Office 2010 during the grace period if you deploy a pre-installed Office with an OS image. The grace period begins immediately after you installed Office 2010 on your master PC. If you have to perform other configurations before you create the master image, then it is quite possible that 25 days is too short. You also have to take into account that it might take some time until Office finds a KMS host or until you activate it manually.

This is where Office 2010 rearm comes in. This features allows you reset the grace timer to 30 days grace. If you rearm Office right before you create the OS master image, you can be sure that you have the full 25 days before users will bothered with Office activation notifications or before the retail edition goes into Reduced Functionality Mode after 30 days.

How to rearm Office 2010 ^

You will find some complicated instructions on the Web of how to rearm Office 2010. Most of these articles were written before Office 2010 was released. There are also third party tools that allow you to rearm Office 2010. However, I recommend following Microsoft's instructions. This topic is too sensitive to rely on third party tools.

To rearm Office 2010, you only have to run ospprearm.exe in %installdir%\%Program Files%\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform from an elevated command prompt. "%Program Files%" has to be replaced with %Program Files (x86)% if you installed Office 2010 32-bit on Windows 64-bit.

Rearm Office 2010 - ospprearm.exe

Since you can rearm up to 5 times, you can run Office 2010 for 180 days (30 days + 5 x 30 days) without activating it, if you rearm it every time after the 30 days grace period has been reached.

Another effect of rearming Office 2010 is that the client machine ID (CMID) is reset. The KMS host uses the CMID to identify unique clients. This allows the KMS host to count Office 2010 correctly.

Rearming Office 2010 Trial ^

Office 2010 rearm could also be useful if you installed Office 2010 Trial. The Office 2010 Professional Plus Trial comes with a special activation code that will allow you to test Office 2010 for 60 days. There are reports on the web indicating that you can also rearm the trial version of Office 2010. Office 2010 Trial indeed comes with ospprearm.exe. However I doubt that rearming will work after you used the trial activation code because rearming makes only sense with an Office installation that hasn't been activated.

Office 2010 Activation Wizard

You can run Office 2010 Trial without activating it but every time you launch the Office 2010 Activation Wizard will pop up. If you cancel this dialog, you can continue using the Office application. I suppose this will only work for 30 days. If you have experience with rearming Office 2010 Trial, please let me know.

Poll: Does your organization plan to introduce Artifical Intelligence?

Read 4sysops without ads and for free by becoming a member!

Источник: [https://torrent-igruha.org/3551-portal.html]
, MS Office 2010 Activator Archives

Chris Nackers Blog

Video Walkthrough for Office 2010 KMS Activation:


http://technet.microsoft.com/en-us/windows/ff716617.aspx?ITPID=flpbook






Planned KMS Activation of Office 2010


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


Office Volume Activation Resource Center


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


How to troubleshoot the Key Management Service (KMS)

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
















  • Each Office suite or product has its own MAK key. In addition, here are separate MAK keys for Microsoft Project 2010 and Microsoft Visio. For example, with a single MAK key you can activate all applications in the Microsoft Office Professional Plus 2010 suite, but you must enter separate MAK keys for Project 2010, Visio, or any of the Office Professional Plus 2010 suite products, such as Microsoft Word 2010 or Microsoft Excel 2010.



To activate an Office KMS host on Windows Server 2003












To activate an Office KMS host on Windows 7 or Windows Server 2008 R2




















 



 




KMS hosts automatically publish their existence by creating service (SRV) resource records (RRs) on the DNS server. If there is only one KMS host and dynamic update, no action is required for the KMS host to create the SRV RR that publishes the KMS service location.


If there is more than one KMS host, only the first KMS host can create an SRV RR. Subsequent KMS hosts cannot change or update SRV RRs unless the default permissions on the DNS server are changed.


Changing the default permissions on the DNS server requires administrative rights in the domain, and the KMS hosts must all belong to the same Active Directory Domain Services (AD DS) domain. Create a global security group in AD DS for your KMS hosts. Add each KMS host to the new security group, and set the permissions on the DNS server to allow updates by members of the newly created security group.


For more information about how to configure DNS for the KMS host, see “Understanding KMS” in Customer Hosted Volume Activation Guide(http://go.microsoft.com/fwlink/?LinkId=187539).


 


Verify successful activation of the Office KMS host



To verify that the Office 2010 KMS host key is successfully installed and activated, use the slmgr.vbs script. Open an elevated command prompt on the KMS host, type the following command, and then press ENTER:


cscript slmgr.vbs /dlv all


To view information only for Office 2010, specify the Activation ID after the /dlv parameter:


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


The output should resemble the following:





Name: Microsoft Office 2010, KMSHost edition
Description: Microsoft Office 2010 KMS, VOLUME_KMS channel
Activation ID: bfe7a195-4f8f-4f0b-a622-cf13c7d16864
Application ID: 59a52881-a989-479d-af46-f275c6370663
Extended PID: 55041-00096-199-000004-03-1033-7600.0000-3632009
Installation ID: 008585014214769124199722184000850026888810090785321136
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: RP3HH
License Status: Licensed
Remaining Windows rearm count: 1
Trusted time: 12/29/2009 1:45:54 PM

Key Management Service is enabled on this computer
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal

Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0

Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0


If the output shows “License Status: Licensed,” the Office 2010 KMS host key is successfully installed and activated.


Once KMS clients send requests for activation, the current count is incremented. The current count must be 5 or greater before KMS clients activate. The maximum current count will be twice the activation threshold, or 10. Administrators can also check the KMS log that is in the Applications and Services Logs folder for event ID 12290, the ID for KMS-related activity. The KMS log records activation requests from KMS clients. Each event displays the name of the computer and the time stamp of each activation request.


 


To diagnose KMS activation errors





  1. If the computer has the KMS client key installed, check the licensing status. To do this, type the following command, and then press ENTER:


    cscript ospp.vbs /dstatusall



  2. To check the KMS activation history, type the following command, and then press ENTER:


    cscript ospp.vbs /dhistorykms



  3. To trigger activation, type the following command, and then press ENTER:


    cscript ospp.vbs /act



  4. Check the error message for error code 0xC004F042. If you see an error code in the notification dialog boxes shown to the users, you can also use that code to check the error message. To do this, type the following command, and then press ENTER:


    cscript ospp.vbs /ddescr:0xC004F042


To set test KMS host name, and then set to auto-discovery





  1. If you are testing a KMS host named kmstest.contoso.com, and you want to specify it in the KMS client, type the following command, and then press ENTER:


    cscript ospp.vbs /sethst:kmstest.contoso.com








    Note:
    If you change the default port on the KMS host, you must run ospp.vbs with the /setprt parameter.



  2. To trigger activation, type the following command, and then press ENTER:


    cscript ospp.vbs /act



  3. To check the KMS activation history to see whether the host was successfully contacted, type the following command, and then press ENTER:


    cscript ospp.vbs /dhistorykms



  4. Now you want this KMS client to use Domain Name System (DNS) for auto-discovery of the production KMS host. To remove the KMS host name, type the following command, and then press ENTER:


    cscript ospp.vbs /remhst


Generally, you do not have to configure Office KMS clients if the Office KMS host was correctly set up and configured. The KMS client automatically searches for the KMS host by using DNS and attempts activation. The KMS service uses service (SRV) resource records (RR) in DNS to store and communicate the locations of KMS hosts.


By default, KMS hosts automatically publish the information that KMS clients need to find and connect to them by using DNS dynamic update protocol. By default, KMS clients query the DNS server for KMS service information.


You can manually configure KMS hosts and clients, depending on the network configuration and security requirements. For example, if the network environment does not use SRV records, you can manually configure a KMS client to use a specific KMS host. For more information about how to configure the KMS client, see The ospp.vbs script earlier in this article and Prepare and configure the Office 2010 client inDeploy volume activation of Office 2010. For more information about how to configure the KMS host, see Prepare and configure the KMS host in Deploy volume activation of Office 2010.


 


 


 


 

Источник: [https://torrent-igruha.org/3551-portal.html]
MS Office 2010 Activator Archives

Chris Nackers Blog

Nice document from the MSSpringboard Twitter.

Download the document here.

Frequently Asked Questions

The Microsoft Office 2010 Office Deployment Kit for App-V is required for sequencing and deploying Microsoft Office 2010. It enables specific features for 32-bit versions of Microsoft Office 2010, including:

  • Extend virtual Office 2010 usage via improved SharePoint integration to Open, Save, Edit files
  • Find your email items quickly with Outlook’s Fast Search
  • Connect to your inbox using Microsoft Outlook Send To functionality
  • Print your documents directly to OneNote
  • Find contents within your documents using Office Document Indexing
  • Open Web-based calendar items and RSS Feeds in Outlook
  • Perform advanced mail configuration using the Virtual Mail Applet
What benefits does the customer receive when using Office 2010 and App-V together?
Deploying Office 2010 with App-V 4.6 solves the top problems we hear from customers: 

1. Speeds up deployment time

2. Easier migration to the latest version of Office

3. Easier application patching and management

Additional benefits include: App-V packages (including Office 2010) can be sent to client machines running 64-bit operating systems.  App-V virtualized Outlook 2010 search is fast and instantaneous, just like non-virtualized Outlook search.

Can I use Click-to-Run to deploy Office 2010 with App-V to the enterprise?

Click-to-Run is a new delivery mechanism for certain retail Office 2010 SKUs intended for end users.  Click-to-Run Office products are not customizable and cannot be deployed in the enterprise like other App-V packages.  Enterprises interested in deploying Office 2010 via App-V must sequence their own Office 2010 packages.  Sequencing Office 2010 requires use of the Microsoft Office 2010 Deployment Kit for App-V, which enables the licensing platform to work with App-V virtualized Office applications.

What OS versions does the Deployment Kit work with?

The following list outlines the supported operating systems for running the Microsoft Office 2010 Office Deployment Kit for App-V.

Operating System

Edition

Service Pack

System Architecture

Windows XP

Professional

SP2 or SP3

x86

Windows Vista

Business, Enterprise, or Ultimate

No service pack, SP1, or SP2

x86, x64

Windows 7

Professional, Enterprise, or Ultimate

NA

x86, x64

Windows Server 2003 Remote Desktop Services

Standard Edition, Enterprise Edition, or Datacenter Edition

SP1 or SP2

x86, x64

Windows Server 2008 Remote Desktop Services

Standard, Enterprise, or Datacenter

SP1 or SP2

x86, x64

Windows Server 2008 R2 Remote Desktop Services

Standard, Enterprise, or Datacenter

NA

x64

Does this solve the existing problems with Office 2007 and App-V?

No. This solution does not correct the current limitations when using Office 2007 and App-V together.

Are administrative rights required to install the Deployment Kit? 

Yes. The Deployment Kit is an MSI that must be installed with administrative rights.

Can I deliver/install the Deployment Kit via System Center Configuration Manager or other software delivery tools?

The Deployment Kit can be deployed like any other MSI.  Software delivery tools like System Center Configuration Manager can deliver and install the MSI.

Can I sequence/launch Office 2010 with App-V 4.5x/4.2?

No. Office 2010 is supported only on versions App-V 4.6 and later. We are evaluating the cost of supporting Office 2010 with App-V 4.5, but there are no current plans for support at this time.

Can I deploy Office 2010 to production using App-V?

No.  Office 2010 Deployment Kit is pre-release.  Production deployments are not supported.

Can I upgrade my existing App-V 4.6 Beta Client to the App-V 4.6 Client?
No. The App-V 4.6 Beta Client should be uninstalled before installing the App-V 4.6 Client.

What versions of Office 2010 require use of the Deployment Kit when deployed with App-V?

All. The Deployment Kit serves two purposes: to enable Office 2010 licensing to work for virtualized Office and to enable certain integration features. Please note that all versions of Office 2010 require the Deployment Kit for the licensing components, but the integration features are optional and only supported for 32-bit versions of Office.

Which Office 2010 Beta products can I sequence and deploy with App-V?

The following Office 2010 Beta products may be deployed with App-V:

· Office Professional Plus 2010 Beta

· Office Visio 2010 Beta

· Office Project 2010 Beta

Will I need to redeploy the Deployment Kit when App-V and Office final versions are released?

Yes – this is standard procedure. All beta versions should be removed before RTM version is deployed. To re-deploy, make sure to uninstall the Deployment Kit before installing the latest version.

Why does Office 2010 use the new SPP licensing platform?
The Software Protection Platform (SPP) is new for Office 2010 and leverages the same licensing functionality introduced in Windows Vista and included in all versions of Windows 7. SPP is included in, and required for, all Office 2010 client skus and is an important part of the Office anti-piracy strategy.

To learn more about volume activation of Office 2010, here are some useful links:

· Office Volume Licensing: http://blogs.technet.com/office2010/archive/2009/08/24/volume-activation.aspx

· Microsoft Office 2010 Activation Guidelines: https://partner.microsoft.com/40111510?msp_id=office2010activation

· Overview of Volume Activation for Office 2010: http://technet.microsoft.com/en-us/library/ee624349(office.14).aspx

When will Office 2010 be generally available?

Office 2010 will be available in the first half of 2010.

How does the Deployment Kit enable SPP licensing and the virtualization proxies to work?

Certain Office components like the SPP licensing platform or the Outlook Fast Search indexer cannot work when virtualized. These components integrate with local system features and will not function if they stay in the virtual environment. The Deployment Kit installs Office SPP and proxy components to the machine that facilitate communication between the native environment and the virtual environment.

You indicate the SPP Service must be installed on the Sequencer machine. So why doesn’t the Sequencer capture the SPP service so that I don’t have to install it natively?
All technologies physical or virtual require the SPP component to be installed in order to be in compliance with Office 2010 licensing. Virtualized Office 2010 will not self-install the SPP component when sequencing. Hence, the SPP must be installed in order to sequence Office 2010. The Sequencer actually does not care if the SPP service exists or not. The SPP service must also be natively installed on client machines because the licensing activates itself uniquely with the hardware (i.e., the client machine), and hence, requires a native presence on the machine.

Will Office 2010 work when deployed with App-V to both 32-bit and 64-bit Windows?
Yes. The licensing component is supported for both 32-bit and 64-bit Office on any 32-bit and 64-bit operating systems. Hence, Office 2010 will work when deployed to 32-bit or 64-bit. The caveat to remember is that the Office 2010 proxies are supported for 32-bit Office only.

Do I have to use the 4.6 Sequencer to sequence Office 2010?
Yes, Office 2010 will only work with App-V versions 4.6 and greater, including the Sequencer.

Will Office 2010 on App-V work on XP, Vista, and Windows 7?
Yes, this will work on XP, Vista, and Windows 7. We also support Windows 2003 Remote Desktop Services, Windows 2008 Remote Desktop Services, and Windows 2008 R2 Remote Desktop Services.

Will you publish an App-V recipe for how to do this once generally available?
Absolutely. We understand that virtualizing Office 2010 Beta is important so we have designed, created, and tested a recipe to sequence Office 2010 Beta to facilitate virtualizing the product. You can download the recipe from www.officeitpro.com

For normal MSI installations of Office 2010 Beta volume-license products, I need to have a Key Management Service (KMS) or Multiple Activation Key (MAK) volume activation solution. Does deploying Office 2010 Beta with App-V bypass these requirements?

No. Licensing for either MSI-deployed Office or App-V-deployed Office would require a MAK key(s) or activation against a KMS server. For more information, see http://technet.microsoft.com/en-us/office/ee691939.aspx

Is the Deployment Kit only to be used with App-V?

The Microsoft Office 2010 Deployment Kit for App-V is designed for App-V.

Источник: [https://torrent-igruha.org/3551-portal.html]
.

What’s New in the MS Office 2010 Activator Archives?

Screen Shot

System Requirements for MS Office 2010 Activator Archives

Add a Comment

Your email address will not be published. Required fields are marked *