Microsoft Office 2013: License 01A - Microsoft license ledger for Microsoft License Statements

I have a client who uses these reports for their license counts etc. Recently they have deployed Office 2013 (Not through SCCM) and the reports do not reflect any Office 2013 installations although running a query for Add/Remove or looking at software
installed on a specific computer via other reports clearly shows Office 2013. Was there a specific rollup or hotfix for this? Thank you in advance for your time.

Thanks. I reviewed that in the past and did not see anything specific regarding Office 2013 nor in the R3 release notes.
@roblizz, sorry, I just noticed you commented on the TN wiki article for CM07 patches (which I help to curate).
It seems related to this question you asked, and the same sort of timeframe.
Did you get this sorted out ?
If not, this other HF for AI might be worth considering (assuming you haven't previously applied it).
Otherwise, it looks like we all missed the boat on getting a HF for this, since CM07 is now out of mainstream support.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Similar Messages

Office 2013 license pack does not allow me to activate key within configuration wizard

Hello,
I have a KMS host running Office 2010 activations for our client computers which is running fine. I installed the Office 2013 license pack on the same host. However, in the configuration wizard it doesn't allow me to activate the product key. Is there
a way around this?
My client laptop isn't activating against the KMS host, and I have Office 2013 installed on my laptop. This is what I get when I run
cscript ospp.vbs /act on my client laptop
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd c:\
c:\>cd program files
c:\Program Files>cd microsoft office
c:\Program Files\Microsoft Office>cd office 15
The system cannot find the path specified.
c:\Program Files\Microsoft Office>cd office15
c:\Program Files\Microsoft Office\Office15>ospp.vbs /act
c:\Program Files\Microsoft Office\Office15>cscript ospp.vbs /act
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
Installed product key detected - attempting to activate the following product:
SKU ID: b13afb38-cd79-4ae5-9f7f-eed058d750ca
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
Last 5 characters of installed product key: 92CD4
ERROR CODE: 0xC004F038
ERROR DESCRIPTION: The Software Licensing Service reported that the product coul
d not be activated. The count reported by your Key Management Service (KMS) is i
nsufficient. Please contact your system administrator.
---Exiting-----------------------------
c:\Program Files\Microsoft Office\Office15>

Hi,
Please check if your KMS host key for Office 2013 is valid and you can try to activate the KMS host by telephone.
To get the key for the Microsoft Office 2013 KMS, sign in to Microsoft Volume Licensing Service Center.
On this page, don’t choose the Key Management Service Host Key. Choose the Office version you are licensed for instead, and look for the KMS key for that version.
http://technet.microsoft.com/en-us/library/dn385356.aspx
To activate an Office KMS host by telephone
http://technet.microsoft.com/en-us/library/dn385356.aspx#BMK_ToactivateanOfficeKMSbytelephone
KMS activation of Office 2013
http://technet.microsoft.com/en-us/library/ee624357.aspx
If issue persists, it is recommended to post the question in Office forums for further troubleshooting.
http://social.technet.microsoft.com/Forums/office/en-US/home?category=officeitpro&filter=alltypes&sort=lastpostdesc
Hope this helps.
Jeremy Wu
TechNet Community Support

Office 2013 removed grammar & writing style options for Portuguese (Brazil) language

The pt-br (Portuguese - Brazil) proofing tools for Office 2010 included many grammar options but apparently these have been removed in Office 2013. Pt-pt (Portuguese - Portugal) still retains these options for some reason. I asked about this issue on the
Microsoft Community forum and the forum moderator confirmed that the Brazilian Portuguese Office 2013 spell checker does indeed lack these features.
I know that the pt-br proofing tools was designed by Itautec Brazil. So I contacted the project leader and she answered me as follows:
" Someone from Itautec contacted Microsoft and they answered: “Microsoft has now replaced all of the above features with our own versions - we do not intend to ship the Itautec features with any new Microsoft product.”"
I would like use Office 2013, but I cannot work without a robust Brazilian Portuguese spell checker. Is using Office 2010 my only option?

Hi,
You can go to this page and click Download button to download Microsoft Office Proofing Tools 2013 - Portuguese (Brazil):
http://www.microsoft.com/pt-BR/download/details.aspx?id=35400
The current tool might be not powerful enough for you, you can always submit your feedback/requirement by clicking the smile face at the upper right corner of Office applications. Microsoft will work hard to make sure it is reviewed:
http://blogs.office.com/2012/08/03/got-feedback-send-a-smile-or-a-frown/
Please be assured that Microsoft product team will strive to capture Microsoft users' ideas and are working hard to create a more powerful and easy-to-use product.
Thanks,
Ethan Hua CHN
TechNet Community Support

Sccm check office 2013 users license status

Hi I tried to use sccm2012 to check the license report for office 2013 users, but there are nothing for office 2013. there are for office 2010,win7,etc. I run query and confirmed some pc have office 2013 installed. any advice how to get the report for
licensed products work?thanks
Thanks and best regards, -- KF

Here's a simple query which target the "Program and Features" (Add/Remove Program) of your computers.
Do you get any results ?
select B.Name0, B.AD_Site_Name0,B.Operating_System_Name_and0, A.DisplayName0
from v_Add_Remove_Programs A inner join v_r_system B on B.ResourceID=a.ResourceID
where DisplayName0 like '%Microsoft Office 2013%'
Benoit Lecours | Blog: System Center Dudes

Installing Office 2013 on several PCs in a small company

Rather than create individual Live IDs for each of the 7 PCs in a small company, in order to install Office 2013, can we install 7 copies of Office 2013 using a single Live ID? (each copy of Office 2013 is licenced individually, not bought through
VLSC).
Or, is there a better way to install several copies of Office 2013 in an organisation (that does not want to buy Volume Licencing, they just want to buy individual copies)?

Are you talking about the local install version Office 2013, or Office 365 (2013)?
Office 365 is "easier" if you are dealing with volume licenses. Office 365 "installs" very quickly, in a matter of minutes. So if you are talking about buying individual 365 business licensees, just document a short procedure telling users how to install
Office 365 (sorry, that may not work if they don't have admin rights on the PC).
If you bought Office 365 volume license, here is a procedure I pieced together:
How does a company install and control licenses - Business
Using Click to Run virtualization, the process of getting new users running has substantially changed. Because CTR installations are so fast, you no longer have to pre-install the software for users.
A business IT Admin controls use of corporate Office 365 licenses through the Office 365 Administration Center online.
Overview:
- In the Office 365 Administration Center the designated Office Administrator sets up the new USER ID
- Setup the associated email account(s)
- Setup Office licenses allowed to the userid
- the new User logs in to their new computer
- in Internet Explorer the user goes to the “Office 365 Portal” site to get their allowed Office 365 installation
- using the Click to Run installation process, Office 365 is installed and running on a new computer is a matter of minutes.
The following links will provide you with more detailed information of where to look and what to do. You may require some additional support from an “expert” .
Free MS training for Office 365 Administration Center / Portal
http://office365support.ca/does-microsoft-have-free-training-for-the-new-office-365/
Excellent resource to get you started administering your business Office 365 licenses.
The first video,
Exploring the Office 365 Administration Center (9:32), describes
how to create new userids, and to assign Office licenses to them. It also very quickly breezes by how to install Office.
The second vidow,
Office 365 Overview for IT Administrators (14:00), quickly walks you
through setting up new company and users.
On basic setup page, step 3 “Set up User Access” provides links to instructions on how to set up new users.
In Service Settings, Downloads, you can control what Office apps the user can download.
Creating Users for the NEW Office 365
http://office365support.ca/creating-cloud-users-for-the-new-office-365/
This page provides more detailed instructions for setting up the new userids and granting them Office 365 licenses
Configuring Desktops for the NEW Office 365
http://office365support.ca/configuring-desktops-for-the-new-office-365/
The following post will document how to setup a Windows 8 desktop for a cloud user for Office 365. I have already installed Windows 8 and created
the local account for my test user. I have logged into the Office 365 portal and had the user change his password. The password for Office 365 and the password for the desktop are the same.
Office 365 for enterprises: A tour for administrators
http://office.microsoft.com/en-us/videos/office-365-for-enterprises-a-tour-for-administrators-HA102654955.aspx
Office 365 for enterprises brings together the online services your business needs. To see how to set up and manage these services, watch these four short videos.
Where did My MSI go - Deployment Video
http://www.microsoft.com/resources/technet/en-us/office/media/video/video.html?cid=otc&from=mscomoffice&VideoID=670e3969-0509-4d3a-a8a6-ffbe526d3e6f&src=v5:endslate:related^play:related_0&from=shareembed-syndication
10 minute comparison of MSI and CTR
Touches on corporate provisioning in”User Based License Model Activation”. Users activate/deactivate, but IT still has control to deprovision the license (starting at about minute 8:15).
Then in this video / article :
http://blogs.technet.com/b/office_resource_kit/archive/2013/03/20/the-new-office-garage-series-identity-activation-data-access.aspx
They again say the companies can still allow userid activation while maintaining control of the licenses through Active Directory
<snip>
Jeremy: So we showed the installation experience for a domain-joined computer where single sign on is enabled and one that is not domain-joined, but installs via the Office 365 portal. In the direct from portal case when you kick off the
installation, you will see a file that looks something like this:
Setup.X86.en-us_O365ProPlusRetail_24*****-45a2-4eeb-b06f-b14****189c8_TX_PR_.exe
In a future episode we'll talk about all of the configurations needed to suppress completely sign-in, first run experiences and user prompts. IT admins have had to deal with these in past releases of Office, but now there are ways to
automatically sign users in to Office 365 installs picking up their domain credentials. I also showed the effects of deleting the user account from the Azure AD store and how it put Yoni's Office into Reduced Functionality Mode (RFM) -
even if Yoni installs Office on his personal devices using his organization's Office software assets, once Yoni leaves the org the IT department can deprovision his personal installs. That keeps software asset management cleaner and IT is in control.
Yoni: Don't forget we also had Mark Russinovich on the show and he explained the security model for online services with Azure AD - in your car. It sounds like they are taking the defense in depth approach to harden the service. And you
made him slum it in your car, Jeremy.
</snip>
Overview of ID, Authentication and Authorization in Office 2013
<snip http://blogs.technet.com/b/office_resource_kit/archive/2013/04/16/new-poster-and-content-roadmaps-about-office-identity-authentication-authorization-and-security.aspx
>
This page has links to 3 posters. The first poster “Identity and Authentication in the Cloud: Office 2013 and Office 365” describes at a high level how to control new user setup in a corporate / small business environment.
</snip>
<snip http://technet.microsoft.com/en-us/library/jj683102.aspx
>
This page also has a link to the same poster online (http://www.microsoft.com/en-us/download/details.aspx?id=38193 has PDF and Visio versions of the chart). As well, it goes into
more detail with information like the following:
… Because Office is a tool that is used by the same individual in two different roles, the new Office offers two identities with which users can log on to Office 2013:
A Microsoft account, which most people use for personal business
An organization ID that is assigned by Microsoft, which most people use when doing work for an organization, such as a business, charity, or school.
The credentials that are used to sign in are recognized as either personal or organizational. That sign-in identity becomes the user's “home realm” and determines which documents the user has access to on SharePoint, SkyDrive, or Office 365 Services for
a specific session. Each unique sign in identity is saved in a most-recently used list so that it is easy to switch between identities without leaving the Office experience.
a personal SkyDrive can be mounted to an organization identity so that personal documents can be accessed at work or school without ever switching identities. Also, when a user authenticates by using an identity, this authentication is valid for all Office
applications, not just the application he or she signed in to.
Two logon types are supported when users sign in to Office 2013, a Microsoft account or an organization ID that is assigned by Microsoft.
Microsoft account (the user’s individual account). This account, formerly known as Windows Live ID, is the credential that users use to authenticate with the Microsoft network and is frequently used for personal or non-business work, such
as volunteer work. To create a Microsoft account, a user provides a user name and password, certain demographic information, and “account proofs,” such as an alternative email address or phone number. For more information about the new Microsoft account, see
What is a Microsoft account?.
An organization ID that is assigned by Microsoft / Office 365 account ID that is assigned by Microsoft. This account is created for business use. An Office 365 account can be one of three types: a pure Office 365 ID, an Active Directory
ID, or an Active Directory Federation Services ID. These are described below:
Office 365 ID. This ID is created when an admin sets up an Office 365 domain and takes the form <user>@<org>.onmicrosoft.com, for example:
[email protected]
Organization ID that is assigned by Microsoft that is validated against a user's Active Directory ID. An organization ID that is assigned by Microsoft and validated against Active Directory as follows:
First, a person who has an [on-premise domain]\<user> account attempts to access organization resources.
Next, the resource requests authentication from the user.
Then, the user types in their organization user name and password.
Finally, that user name and password are validated against the organization AD database, the user is authenticated, and is given access to the requested resource.
An organization ID that is assigned by Microsoft that is validated against a user’s Active Directory Federation Services ID. An organization ID that is assigned by Microsoft and validated against Active Directory Federation Services (ADFS)
as follows:
First, one person who has an org.onmicrosoft.com attempts to access
partner organization resources.
Then, the resource requests authentication from the user.
Next, the user types in their organization user name and password.
Then, that user name and password are validated against the organization AD database.
Finally, that same user name and password are passed to the partner’s federated AD database, the user is authenticated, and is given access to the requested resource.
For on-premises resources, Office 2013 uses the domain\alias user name for authentication. For federated resources, Office 2013 uses the [email protected] user name for authentication.
</snip>
Office 365 Administration / Office 365 Administration Center / Office 365 Portal
http://technet.microsoft.com/en-us/library/jj819272.aspx
This page summarized methods of administering Office 365
User Account Management
http://technet.microsoft.com/en-us/library/jj819300.aspx
Sign-in for Small Business subscriptions
Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud services.
Sign-in options for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions
Office 365 for Enterprise, Midsize Business, Kiosk, Academic, and Government subscriptions has two systems that can be used for user identities:
Organizational account (cloud identity) Users receive Windows Azure Active Directory cloud credentials—separate from other desktop or corporate credentials—for signing into Office 365 and other Microsoft cloud
services. This is the default identity, and is recommended for small and midsize businesses in order to minimize deployment complexity. Passwords for organizational accounts use the Windows Azure Active Directory
password policy.
Federated account (federated identity) For all subscriptions other than Office 365 Small Business and Office 365 Small Business Premium, in organizations with on-premises Active Directory that use single sign-on
(SSO), users can sign into Office 365 services by using their Active Directory credentials. The corporate Active Directory stores and controls the password policy. For information about SSO, see
Single sign-on roadmap.
The type of identity affects the user experience and user account management options, as well as hardware and software requirements and other deployment considerations.
Custom domains and identity options
When you create a new user, the user’s sign-in name and email address are assigned to the default domain as set in the Office 365 admin center. By default, the Office 365 subscription uses the <company name>.onmicrosoft.com
domain that was created with the Office 365 account. You can add one or more custom domains to Office 365 rather than retaining the
onmicrosoft.com domain, and can assign users to sign in with any of the validated domains. Each user’s assigned domain is the email address that will appear on sent and received email messages.
You can host up to 600 registered Internet domains in Office 365, each represented by a different namespace.
For organizations using single sign-on, all users on a domain must use the same identity system: either cloud identity or federated identity. For example, you could have one group of users that only needs a cloud identity because they don’t access on-premises
systems, and another group of users who use Office 365 and on-premises systems. You would use add two domains to Office 365, such as
contractors.contoso.com and
staff.contoso.com, and only set up SSO for one of them. An entire domain can be converted from cloud identity to federated identity, or from federated identity to cloud identity.
For more information about domains in Office 365, see the
Domains service description.
Creating user accounts
Office 365 provides five ways to create user accounts, some of which are not available for Office 365 Small Business and Office 365 Small Business Premium: Add single User, Bulk upload using *.CSV files, Active Directory Synchronization, Azure Active Directory
Module for powershell, Exchange Simple Migration
Password management
The policies and procedures for password management depend on the identity system.
Cloud identity password management:
When using cloud identities, passwords are automatically generated when the account is created.
For cloud identity password strength requirements, see
Change your password.
To increase security, users must change their passwords when they first access Office 365 services. As a result, before users can access Office 365 services, they must sign into the Office 365 portal, where they are prompted to change their passwords.
Admins can set the password expiration policy. For more information for Enterprise and Midsize subscriptions, see
Set a user’s password expiration policy. For Small Business, see
Change how often passwords expire.
License management
A subscription to Office 365 is made up of a number of licenses to a set of services. An administrator assigns a license to each user for each service that user needs access to. For more information about managing licenses, see
Assign or remove a license in Office 365 Enterprise, or
Assign or remove a license in Office 365 Small Business.
Office 365 for Business FAQ
http://office.microsoft.com/en-us/business/microsoft-office-365-for-business-faq-FX103030232.aspx
Some general questions are answered
Deployment guide for Microsoft Office 2013
http://blogs.msdn.com/b/mssmallbiz/archive/2012/10/22/free-microsoft-ebook-deployment-guide-for-microsoft-office-2013.aspx
Free Download, 147 pg
Table of Contents
Getting help
Volume activation of Office 2013
Plan volume activation of Office 2013
Volume activation methods in Office 2013
Deploy volume activation of Office 2013
Use tools to configure client computers in Office 2013
Customize installations of Office 2013
Customize Setup before installing Office 2013
Configure a silent installation of Office 2013
Create custom configurations of Office 2013
Office Customization Tool (OCT) in Office 2013
Config.xml file in Office 2013
Setup command-line options for Office 2013
Setup properties in Office 2013
Setup architecture overview for Office 2013
Customize the Accessibility Checker for Office 2013
Outlook 2013
Planning overview for Outlook 2013
Choose between Cached Exchange Mode and Online Mode for Outlook 2013
Plan a Cached Exchange Mode deployment in Outlook 2013
Plan feature customizations in Outlook 2013
Choose security and protection settings for Outlook 2013
Configure multiple Exchange accounts for Outlook 2013
Configure Cached Exchange Mode in Outlook 2013
Configure Outlook Anywhere in Outlook 2013
Configure junk e-mail settings in Outlook 2013
Roll out Office 2013
Install Office 2013 from the local installation source
Deploy Office 2013 from a network installation point
Deploy Office 2013 by using Group Policy computer startup scripts
Language in Office 2013
Plan for multi-language deployment of Office 2013
Customize language setup and settings for Office 2013
Add or remove language packs after deployment of Office 2013
Mixed language versions of Office 2013
Companion proofing languages for Office 2013
Language identifiers and OptionState Id values in Office 2013
Security in Office 2013
Security overview for Office 2013
Authentication in Office 2013
Plan for Information Rights Management in Office 2013
Group Policy for Office 2013
Planning for Group Policy in Office 2013

Office 2013 VL Local Install with Project and Visio 2013 App-V

Is it supported to have a local install of Office 2013 and deploy a virtual package for Project and Visio 2013 (created via ODT) using App-V 5.0 SP2?I cannot find any reference in the various support articles.

Hello. Did you manage to get an official statement on this?
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
answer your question). This can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or MVPs.
Twitter:
@alexverboon | Blog: Anything About IT

Is LiveCycle ES4 compatable with Office 2013?

My network was recently upgraded to Microsoft Office 2013 and I have a LiveCycle user that reports she can no longer import documents from Word. She is still able to create a document from scratch though. We have un-installed and re-installed both Office and LiveCycle on her machine. She is the only LiveCycle user I have, so I am unable to tell if it's an issue with her machine or with Office 2013. Are there any known compatablilty issue with LiveCycle ES4 and Word 2013?

Hello There,
I am sorry for that but Captivate is not compatible with Office 2013.
Please check the link for the compatibility between Captivate and Microsoft office: http://helpx.adobe.com/captivate/using/microsoft-powerpoint.html
Hope this helps !
Thanks and Regards
Himanshu Satija

Office 2013 outlook installation only

Dears,
Office 2013 installed successfully but some feature for outlook is missing for that need to run setup to select Run All from my Computer. is there any registry key i can run directly or any script of it do it? only for outlook
[email protected]

All i need a key to run setup without going to control panal and select change to add feature.
Or At least run setup like run from program feature if you select office and click option
There is no registry key to perform this task - because it's not a registry function.
When you use: Control Panel -> Programs and Features -> Uninstall or change a program -> Office -> Change
this is actually launching setup.exe, and then you make the changes to features, which then executes msiexec.exe with special logic.
To perform the equivalent task, you must:
a1) create the customization MSPfile, with OCT, which generates the special logic (to enable the desired feature state)
a2) run the necessary msiexec /p YourMSPfile.msp
or
b1) create the config.xml, which contains the special logic (to enable the desired feature state)
b2) run the necessary setup.exe /modify ProPlus /config YourCustomConfig.xml
e.g.:
http://technet.microsoft.com/en-us/library/cc178956(v=office.15).aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Is Captivate 6 compatible with Office 2013?

Is Captivate 6 compatible with Office 2013?

Hello There,
I am sorry for that but Captivate is not compatible with Office 2013.
Please check the link for the compatibility between Captivate and Microsoft office: http://helpx.adobe.com/captivate/using/microsoft-powerpoint.html
Hope this helps !
Thanks and Regards
Himanshu Satija

Deploying Normal.dotm through OCT doesn't work in Office 2013

I am trying to install a custom normal.dotm Word Template file with the initial install of Office 2013.
I am using the Office Customization Tool to create an automated install of Office 2013 in the exact same way I did in Office 2010.I am utilizing the Additional Content>Add Files & Additional Content>Remove Files sections to include a custom normal.dotm
file and place it in the [AppDataFolder]\Microsoft\Templates directory. (The remove files section runs first and removes the same file name before it installs the file I want.)
This works perfectly fine in Office 2010. After I complete the setup process using the customized Office 2013 files however, I get an error message in Microsoft Word that says "Sorry, we had trouble getting the featured templates and can't show them
right now." Also, when I look in the path on the Windows 8 machine this is being tested on, there actually is no Normal.dotm file at first launch but depending on how many times I launch Word it shows up in a few launches or there is a NormalPre.dotm
file in the directory instead. Even when the file shows up I get the same error message in
Why is this not working? How can I accomplish rolling out a custom Normal.dotm file with the install of Office 2013 using OCT?

This is what i did to get it working as i wanted it.
I stripped out configuring the Language in the OCT tool
I added my customised normal.dotm with my customisations in OCT
I added the "MigrateNormalOnFirstBoot" registry key in OCT
I currently am creating an Office 2013 script using vbscript (.vbs file) for the purpose of installing either MSOffice 2013 x86 or x64 versions - i then added the creation of the following registry entry via the vbscript after the msoffice setup command
line part.
- HKCU\Software\Microsoft\Office\15.0\Common\LanguageResources
- i created a DWORD key here called "InstallLanguage" with the value of the language i want Word to default to. In my case it was a value of "2057" for English UK.
With this combination i have a one click MSOffice 2013 script that installs MSOffice 2013 on either a 32bit or 64bit system.
I'm pretty sure you could leverage off a function in OCT to achieve the same as i have. Just a note - i did try to add the registry key first in OCT's "Add Registry entries" however this didn't work as it didn't create the registry keys before first
launching Word. Maybe you could also consider in OCT under SETUP \ Add Installations and Run Programs to run a .bat or reg to .exe file to achieve the same result.

Office Store not working in Office 2013 ProPlus

I have few policies set up for managing our network deployment of Office 2013 ProPlus. Pretty standard things like disabling the first time run movie, disabling the office start screen, and disabling OneDrive. I actually made most of these changes through
the registry as well.
Now, it seems as though the Office Store is disabled but I have no recollection of specifically disabling such a feature nor could I find a registry or GPO which does disable it. I even undid many of the registries I use on a test bench but still could not
get the Office Store functionality back. We've had Office 2013 rolled out on our network for almost a year, and it's taken this long for 1 person of 150 members of staff to notice that the Dictionaries feature is not working due to Office Store not working.
I feel a bit daft posting something seemingly so trivial on TechNet, but half an hour on Google didn't turn up anything relevant that I wasn't already aware of.
Many thanks in advance.

Hi,
Please check if you have disabled the option of "Don't allow any apps to start" and "Don't allow apps from the Office Store to start" in Office Trust Center.
Location: FILE->Options->Trust Center->Trusted App Catalogs
GPO settings for these options:
Block Apps for Office
Block the Office Store
Location: User Configuration->Administrative Templates->Microsoft Office 2013->Security Settings->Trust Center->Trusted Catalogs
Hope this helps.
Thanks,
Ethan Hua CHN
TechNet Community Support

Replace Scenario : USMT Break Office 2013

Hi guys, in the midst of a project to refresh client Operating Systems - the refresh involves using the User State Migration Tool version 5 to capture user settings/preferences and data from old devices and restore to new machines once the Operating
System and applications such as Office are deployed.
SCCM infrastructure is 2012 SP1. Source/old machines are running Windows Vista or Windows 7, Office 2007 and have the Enterprise Vault Add-In for Outlook version 9.0.2.1136. Target/new machines have Windows 7 SP1, Office 2013 and Enterprise Vault Add-In
for Outlook version 10.0.3.1090. All operating systems are 32-bit.
USMT 5 has been extended with the hotfix for Office 2013 (new MigApp.xml) - otherwise the capture is effectively vanilla.
On machines where the User State Migration Tool is used every time Outlook is opened the following error is presented:
Either there is no default mail client or the current mail client cannot fulfill the messaging request.
If Outlook is started using outlook.exe /safe it opens without issue. If I disable the Enterprise Vault Add-In within Outlook, it opens without issue.
I’ve been through the following to no avail:
http://support.microsoft.com/kb/813745
http://www.symantec.com/business/support/index?page=content&id=TECH20486&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1377114331330xz9e5SBBuT28VInhuBHCHNIlGKF39rjY1sr1c
Removing the Enterprise Vault Add-In and re-installing doesn’t resolve the issue, neither does the ResetEVClient.exe utility.
Run fixmapi.exe to no avail.
A repair of Office itself fixes the problem, however this is not feasible across the thousands of machines we're looking to migrate!
What we have noted is that the issue affects every Windows profile on the machine, those copied over by the User State Migration Tool, but also new ones - so whatever is occurring is breaking Outlook/the Enterprise Vault Add-In for the machine, not a specific
profile.
Finally, if we don't use USMT (not viable on the number of machines we have to replace!) I'm able to logon, and under a fresh user profile can open Outlook without issue.
If anyone has any ideas please let me know!
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Finally have a workaround - known error caused by USMT. Working with MS PSS modification of the following reg key will resolve the issue without an Office repair:
HKLM\SOFTWARE\Clients\Mail\Microsoft Outlook\MSIComponentID
Set this to the following value to resolve the issue: (6DB1921F-8B40-4406-A18B-E906DBEEF0C9}Initial tests excluding this from capture/restore via a custom XML but this doesn't seem to work.
We're now using the following Run Command Line step in the USMT Task Sequence to resolve the issue:
reg add "HKLM\SOFTWARE\Clients\Mail\Microsoft Outlook" /v MSIComponentID /t REG_SZ /d {6DB1921F-8B40-4406-A18B-E906DBEEF0C9} /f
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Not able to install ms-office 2013 in windows vista home basic

Hi
recently,we have purchased ms-office 2013 but we are not able to install the ms-office 2013 and it is showing not compatible.
it is an dell vostro laptop v1510.It is an 32-bit operating system .
Could you please share your ideas why i am not able to install MS-Office 2013 in windows vista Home basic.
We are using windows mail whether this windows mail will migrate all mails automatically to outlook 2013.
looking for your reply at the earliest.
Regards
Pradeep

Office 2013 does not run on Vista, it is only compatible with Windows 7 and above. You will not be able to install it.
System Requiremets for Office 2013
While the above link is for Office 365 as well as Office 2013, it shows the requirements.

Microsoft Office can't find your license for this application - multiple copies of Office 2013 x32 failing to start, Software Protection Service timing out

We're experiencing a growing problem with our users in several different domains running in to Microsoft Office 2013 x32 'activation' issues. We use KMS for licensing, which works properly, but some of the machines (~20-30 out of 1000+) sporadically
throw the following error:
'Microsoft Office can't find your license for this application. Microsoft Office will now exit.'
We know it's not an issue with the licenses per se, since they work on and off and we can force KMS activation correctly / talk to the KMS servers.
It appears to be an issue with the Software Protection service not starting properly. In Event Viewer, we see the following:
'Software protection service failed to start due to the following error- the service did not respond in a timely fashion.
Event 7000'
This is occurring on a variety of machines in a variety of environments, all fully patched with the latest Office updates. It's inconsistent, and the 'manually restart the Software Protection Service' solution is not viable as it's occurring on many
different workstations. Office repairs have also been unsuccessful.
Has anyone else come across this? Or have any idea why the Software Protection Service might be sporadically failing? Maybe an Office update in the last 2-3 months?
Thanks for any info.

We're experiencing a growing problem with our users in several different domains running in to Microsoft Office 2013 x32 'activation' issues. We use KMS for licensing, which works properly, but some of the machines (~20-30 out of 1000+) sporadically
throw the following error:
'Microsoft Office can't find your license for this application. Microsoft Office will now exit.'
We know it's not an issue with the licenses per se, since they work on and off and we can force KMS activation correctly / talk to the KMS servers.
It appears to be an issue with the Software Protection service not starting properly. In Event Viewer, we see the following:
'Software protection service failed to start due to the following error- the service did not respond in a timely fashion.
Event 7000'
This is occurring on a variety of machines in a variety of environments, all fully patched with the latest Office updates. It's inconsistent, and the 'manually restart the Software Protection Service' solution is not viable as it's occurring on many
different workstations. Office repairs have also been unsuccessful.
Has anyone else come across this? Or have any idea why the Software Protection Service might be sporadically failing? Maybe an Office update in the last 2-3 months?
Thanks for any info.

Is it time yet for Microsoft to "Recall" Office 2013 and provide anyone who has a 2013 license a replacement Office 2010 license?

The interface is terrible and can't be changed. Every application in the suite locks up/crashes nearly constantly on any machine it is used on. The activation process is terrible and wastes hours of any support/IT dept's time. From a 'privacy
standpoint', the software is seemingly criminally intrusive. It is clearly a product that should never have been released and is so far from functional that it can't be repaired by any 'service pack', 'hotfix', or 'patch'. It needs to be completely
scrapped.
The only 'redeeming quality' of this software is that the guy who was in charge of creating it is gone from Microsoft. (Unfortunately, he is now President Obama's appointee for running the attempt at repairing the 'healthcare.gov' website...
out of the frying pan... )
When the software is installed using one profile (domain or machine account) and a different profile tries to use the software, it requires 're-activation' - which often fails because the software believes it has been installed multiple times. (This is particularly
frustrating because it has to be installed by an administrative user, but most of the time, the person who 'uses' the software is not the 'administrator' - so it is almost always being 'installed' using one profile and 'used' using another profile).
The necessary intrusion into privacy created by the requirement of a "Microsoft Account" to use the software is seemingly criminal.
The tracking of, and installation of licenses is absolutely ridiculous.
An example:
Many of my clients have many users and many computers (up to 75 or so).
I could create a "Microsoft User Account" for each 'user', but these machines get moved between users, and the software license is tied to the 'machine' and not to the 'user' so as soon as that happens, the licenses and the users are no longer
in line and become impossible to track.
I could create a "Microsoft User Account" for each 'computer'... and I can't even count the ways this would be a nightmare to try to track.
I actually did that up front for one client, and created Exchange email boxes for each computer so that "prove you are really you" emails from Microsoft could be received managed, and responded to, and passed out second usernames and passwords
to all of the users so they could "log-in" to their Office 2013 software, and created a database of the 'computer usernames and passwords' so I could track this... unfortunately, this confused the users (as it rightfully should) so they would change
the passwords for their computer's 'Microsoft User Account' thus locking me out and invalidating my database, ... and... CLUSTERF#%K!!!
As a 'best - worst case', I have had to create a single 'Microsoft User Account" for each of my clients' businesses so I can install and activate Office 2013 products. This is a whole new set of "Awesome Stupidity".
Now, I can put a new computer into a client's office and install their new license key for their oem Office 2013, and it shows up in the 'business's Microsoft User Account'. Then when I give the machine to the user, I get to 're-activate' the software
(hoping that it doesn't tell me to piss-off - which happens about 40% of the time. This is a process that can only be described as a "feat of engineering created by a group of monkeys whose former jobs included 'janitor at MAD magazine headquarters'
or 'beer-pong referee').
It starts with two hours of pressing phone buttons and ultimately talking to someone who tells me "yeah, nothin' I can do about that I'm just here for product activation" (which, incidentally, is done by machine until you pass through MS's ridiculous
labyrinth of repetitious keystroking until the machine is convinced you are just too stupid to punch in the right numbers and allows you to talk to a person... who then asks you for the exact same set of numbers and repeats back the exact same responding set
of numbers and acts dumbfounded when it still doesn't work - since it didn't work the first six times you punched or said it into the phone) followed by "I need to send you to the support group... but because it's 6:30 pm (in a process you started at
3:00pm) they are gone for the day and you'll have to call back on Monday morning"
At some point in the process, you get to log into the "Microsoft user account" and 'roll the roulette wheel of stupidity' by trying to activate the right software from a list of 40 different lines that all say "Microsoft Office 2013 Home and
Business oem", but none give any indicator or differentiating factor like for instance: license key, date installed, license key last 4 digits, mother's maiden name, phase of moon when software was first activated, color or type of blood of the user's
paperboy's dog's previous owner... NOTHING... RANDOM FREAKING STAB IN THE DARK - pick one, any one, hope its the license you are trying to install onto this machine, 'cause if not, you very well may kill the product on some other machine.
So through the process, the lucky support staff person gets' to waste roughly an hour and a half on average for every Microsoft Office 2013 installation. I have actually had to start telling my clients that they are going to likely have to pay an extra
$100 or so per machine in order to get their new Microsoft Office software which comes on their new computer activated - that number tends to work out roughly accurately - except that it is a terrible way of trying to 'please a client'.
Oh,... and did I mention... "THE SOFTWARE CONSISTANTLY FAILS"!?!
A client tries to open a document that they have been using for 8 years and Excel doesn't say "Hey, I don't know how to deal with some element of the file that you put in here using Excel 2003, or Office 2010 (both products, by the way, which worked
great) - no... instead,... it crashes. Doesn't really do any damage to the file it choked on, but the work you'd been doing on three other files which you also had open,... yeah,... that work is gone.
Yeah,.... over time, I have developed a pretty consistent spiel for client's needing new computers that goes over how absolutely terrible Office 2013 is, and explains that our options are further limited by Microsoft's yanking of all Office 2010 or previous
products from market availability, and explaining the merits of both LibreOffice and OpenOffice, as well as their drawbacks. I also have a strangely static response explaining how "larger companies are not burdened by these issues because they are
able to use MOPL which allows them to downgrade their productivity software to Office 2010 so they can continue to function happily, but this is really not a cost effective solution for smaller companies who primarily buy oem Office products with their replacement
computers".
Unfortunately, many clients still decide they want to go with Office 2013 because they apparently believe "it really can't be that bad". The value in my 'presale descriptions' are only really realized when they come back to me a week, two
weeks, or up to a month after the new machine is in place and say "wow,... you were right". The place I am left open for any further problems is when I don't impress upon them beforehand just HOW BAD OFFICE 2013 REALLY IS. In that case,
they still come back to me as though I have done something wrong foe selling them this piece of $#!% software and I have to remind them of our previous discussions.
Strangely, far too few heed the warnings and buy the software anyway - but the discussion has saved many clients the costs of Microsoft Project, because the discussion of LibreOffice and OpenOffice nearly always leads to at least a small philosophical conversation
about 'Open Source Software' in general, and my absolute favorite descriptive analogy in that discussion is to compare Microsoft Project at $600 v. ProjectLibre at $0 - and then further describe the costs of licensing and implementing the associated back-end
server solutions, etc.
This is a saving grace for me, because even though the client has been saddled with Office 2013, they have also saved substantially on Project and it is a rare (but granted, not absolutely absent) occasion that ProjectLibre is lacking some feature or function
that they actually need or want to use - and on those occasions, finding out has cost them absolutely nothing in software purchases.
Its not surprising, I suppose, that clients have grown to accept Office as a required 'cost', but still choke heavily on the price-tag of Project every time they have to buy it. The interesting thing to watch over the coming couple of years will be
'how many businesses stop accepting MS Office as a 'required cost' due to the failing of the software itself and the fact that most are being burned, at least once, by purchasing the software "against technical advice" and are learning, merely by
virtue of HOW BAD Office is, that there are other options out there that both cost less and work better... I mean,... LOTS BETTER.
How many businesses that are used to accepting the cost of Microsoft Office as a cost of doing business will be moved over to open source options and satisfied by them by the time Microsoft releases its next version - which will, presumably work - such that
they will no longer justify the cost of Microsoft's offering even if it is 'superior' to the open source offerings because the open source offerings are plenty sufficient and include a price tag of $0 and an installation/implementation time that is much, much
shorter than Microsoft's offering.
If Microsoft doesn't make some dramatic reparations, and do it soon, I expect their market share will be reduced in this area by a very significant margin.
I am suggesting either a 'Complete Recall' of Office 2013 including an 'uninstall 2013/install 2010' process driven by the automatic update engine, or at the very least, a free and easy downgrade rights offering for anybody who has already purchased 2013
and anyone who purchases it between now and the time the next "functional product" is released.

I understand the inconvenience you are experiencing when working with Office 2013.
If you have any feedback about Office 2013 product, click the and submit to Microsoft.
Microsoft will decide how to fix the problem for all customers.
For the activation mechanism, it intends to protect customers of their rights and interests.
For a retail version of Office, if it was purchased with a disk, Microsoft account is not necessary during the installation.
For volume license of Office, refer to the following link to deploy Office suites can be much efficient:
http://technet.microsoft.com/en-us/library/cc178982.aspx
For the problem Office 2013 keep crashing, check the following link to check:
http://support.microsoft.com/kb/2813143/en-us
http://support.microsoft.com/kb/2758592/en-us
Thanks,
Tyor Wang
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no
help.
If you have any feedback on our support, please click
here

Microsoft Office 2013: License 01A - Microsoft license ledger for Microsoft License Statements

Similar Messages

Maybe you are looking for