Office 2013 Shell UI Language

I have some issues with the Shell UI language of Office 2013 via App-V 5.0 (SP2).
The Shell UI language is German, I want it in English.
Package was created using the latest ODT version (Office Deployment Tool for Click-to-Run, 2/25/2014).
1. setup.exe /download Configuration_AllOffice2013.xml
2. setup.exe /packager Configuration_AllOffice2013.xml E:\tmp\Office\AppV
So far so good.
But after publish (manual with Powershell), all icons are using German when using mouse-over.
Office Tools: German.
The UI however is English as expected (Language in Office applications).
According to technet the first language set in configuration.xml is the default shell UI:
“The first language determines the Shell UI culture. The Shell UI is the language of shortcuts, right-click context menus, and tooltips”.
http://technet.microsoft.com/en-us/library/jj219426.aspx#BKMK_LanguageElement
My configuration.xml:
<Configuration>
<Add SourcePath="E:\tmp\Office" OfficeClientEdition="32" >
<Product ID="ProPlusVolume" >
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="de-de" />
<Language ID="fr-fr" />
</Product>
<Product ID="VisioStdVolume" >
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="de-de" />
<Language ID="fr-fr" />
</Product>
<Product ID="VisioProVolume" >
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="de-de" />
<Language ID="fr-fr" />
</Product>
<Product ID="ProjectStdVolume" >
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="de-de" />
<Language ID="fr-fr" />
</Product>
<Product ID="ProjectProVolume" >
<Language ID="en-us" />
<Language ID="nl-nl" />
<Language ID="de-de" />
<Language ID="fr-fr" />
</Product>
</Add>
<Updates Enabled="FALSE" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="AllOffice2013_Setup.txt" Path="%temp%" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
As a workaround I can modify the DeploymentConfig.XML and change all shortcut languages +
tooltips. But I don’t believe ODT cannot generate an English Shell UI.
Any suggestions please?

sorry have not played around allot yet with ODT, so did a new test with the exact same config as you posted. Guess what... same problem,
my log also says: culture="en-us" productstoadd="ProPlusVolume_en-us_nl-nl_de-de_fr-fr_x-none"
he also created the package like: VisioProVolume_ProPlusVolume_VisioStdVolume_ProjectStdVolume_ProjectProVolume_de-de_en-us_fr-fr_nl-nl_x86.appv.
I tried swapping places en-us with de-de but this did not change anything. Seems to me a bug indeed in ODT.
edit:
ok did an other test, added the cs-cz language like:
<Language ID="en-us"/>
<Language ID="nl-nl"/>
<Language ID="cs-cz"/>
<Language ID="fr-fr"/>
And again same issue, language is set to Czech instead of English. It seems ODT does some alphabetic order or something.

Similar Messages

Office 2013 - OSD - Specify different config xml

Hi Guys
I want to deploy Office 2013 in different languages to different users. It seems there are a few ways to do this. But I am thinking I want to package all languages I need into one Office install package and then in the task sequence have groups for countries.
Each country has a variable to specify which config.xml to use. Is this possible or is there a better way?
(I just need to know how to point to the correct xml in the package, kind of like the unattend file) I know the rest if this is the way.
ie.
-France
---ConfigFR.xml
-Germany
---ConfigGe.xml
Sweden
---ConfigSE.xml
Thanks
NN

Hi
I know the original question has been answered, but I have a follow up question.
I am deploying Windows 8.1 Update using custom variables to install Windows language packs and Office Language packs dynamically based on rules. Running just one language works fine. But if I have a multiple language package deployed to Windows the
Office DTs do not pick this up (each DT is currently working of one language per DT and using operating system language to install the correct xml).
See here:
These are the DTs
After doing a bit more reading. I now know I need to setup the rules differently. Can I set the rules to be English and Swedish install DT1, and English and Romanian install DT 2, English alone install DT 3 etc?
I basically need an "AND" rule.
thanks again
NN
*you may have to zoom to see the larger image.

Application cache and multiligual Office 2013

Hi Guys
I have packaged Office 2013 with all needed language packs inside to deploy through DTs based on OU.
The issue I have, is the bandwidth available over some of the lines is very bad. I have been asked that if the Office app caches the whole package, then that might be an issue.
Is there a way without creating multiple applications, still using DTs to stop SCCM caching the whole package and only the files (languages) it needs?
NN

Hi Peter
Thank you for the response. Maybe I have packaged this incorrectly then.
Here is my method:
Folder [Office 2013] has all languages one after the other inside like this:
My application points to this as the root. The DT then points to the setup.exe in the root for all, the MSP and then has a different config file for each DT based on language to be installed.
It does install as expected and picks the correct DT and just one language where needed, but I didn't expect it to drag down files not being used.
Do I need to package this differently to have it not cache all content in the root?
Thanks again
NN

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 - App-v Package setting language to English United Kingdom

I have created an app-v package for Office 2013 using the instructions following in
http://support.microsoft.com/kb/2915745
Which works great and I have an app-v package created, trouble is that the language in Office i.e. Word is set to English United States. I need to default to English United Kingdom.
I have tried using Group Policy, and the language (Eng UK) appears in "Language" in word and if selected it uses this for session, but when Word is closed and re-opened to defaults back to English US.
I've also tried setting the language in the config.xml file to EN-GB during the build process, but the process fails straight away.
Anyone know how to permanently set the language to English UK?
Thanks
Gareth

Hi,
The packager Process ends after a couple of seconds with this error in the log
03/10/2014 14:03:26.289 SETUP (0x103c)
0xfbc Click-To-Run
apx75 Monitorable
TryLaunchClient::HandleStateAction: C2R Client returned failing error code 17002
03/10/2014 14:03:26.289 SETUP (0x103c)
0xfbc Click-To-Run
aoh72 Medium
ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0
The only english language that seems to be supported is EN-US and backed up by this document
http://technet.microsoft.com/en-us/library/f5fee727-df49-4ef7-b073-dd6c08dfecfa(v=office.15)#BKMK_LanguageIdentifiers
I don't have a problem about creating the package in en-us, but need a way of changing it after it is deployed.
Thanks
Gareth

Office 2013 refuse to show rich Grammar options in just ONE language

The bottom line is that Office 2013 Professional Click to Run allows me to use full “Grammar” and “Grammar and Style” features on ALL languages but Portuguese.
I use both English and Portuguese. Word allows me to check lots of stuff in English, but it
only allows three things in Portuguese
(Capitalization, Punctuation, and Spacing) and do not display the “Grammar and Style” option.
I´ve tried to use Spanish and French and both show full options like in English.
I´ve tried almost everything I could think of, including uninstall everything, install the Office 2013 Professional in Spanish and install both Office LangPack2013_EN_x86 and OfficeLangPack2013_Brazilian_x86.
It did not work. I´ve also already upgraded to Windows 8.1.
One thing you must know is that, by mistake I´ve choose Portuguese to Windows 8 single language installation option. When I´ve realized this, I´ve reset to factory default and
choose English. I am wondering if this initial misstep did not left some language problem on the operational system level.

Hi JRBMendes.
I had the very same problem as reported by you. What I did was just place the Office 2013 CD in the DVD driver and click install. In the option field, click "Repair" or "Reparar" if you are using the Portuguese version. After finishing repairing, it will
ask you to reboot the system in order to complete the repair. Bingo. Worked just fine and you have style and grammar option back again.
Abraços,
Carlos Gagliardi

Office 365 with Office 2013 MSI Language Pack on Windows 7 machine.

Hello All,
I have Office 2013 MSI Language Pack installed on Windows 7 machine. After deploying Office 365 using ODT, Lync is crashing.
Is Office 2013 MSI Language Pack compatible with Office 365?
Thanks in Advance !!

Hi,
Have you checked the log file? Does it record the error details there?
So you only have the language pack on your computer, not the entire Office 2013 instance? Office 2013 MSI Language Pack doesn't work with Office 365. Try to remove the language pack then try again.
Also, to plan a multi-language deployment of Click-to-Run-based Office installations, please refer to this article:
http://technet.microsoft.com/en-us/library/dn186220(v=office.15).aspx
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Install the language for office 2013 for student

Hi, I have bought the LIP for chinese traditional for my office however when I install nothing happen. Even I already check the language install from microsoft office they sai not installed?

Launch Office Tools - Office 2013 Language Preferences and check whether the Chinese Traditional shows installed or not. (Tool is Located in"C:\Program Files\Microsoft Office 15\root\office15\SETLANG.EXE")
http://office.microsoft.com/en-in/word-help/enable-the-use-of-other-languages-in-your-office-programs-HA010354783.aspx
If you purchased an Office 365 subscription you can use it to install Office in different languages instead of buying a Language Pack.
More FAQ related to Office LIP, please visit here:
http://office.microsoft.com/en-us/language-packs/microsoft-office-language-packs-2013-faq-faqs-FX102897395.aspx
Tony Chen
TechNet Community Support

Office 2013 Hebrew Language pack wont install

Hi,
I installed office 2013 (English) and am trying to install the Hebrew language pack.
The first time i did it, the installer started and then crashed. Now when i try to install the language pack it says" this program requires windows
7 or newer version" while i obviously have win 7 because i installed office 2013.
I run win7 & use x32 office version. What can i do?
Thanks,
Danny

Hi,
Since your Office is 32 bits, please first check which version of language pack you are trying to install, 32 or 64 bits.
Please install all patches to make your Windows up to date, then try the installation again. You might also try to download a new language pack file and try again.
If the issue presists, I would suggest to repair Office and check behavior, the first installation of this language pack might corrupt some files. Here is the steps on how to repair Office:
http://office.microsoft.com/en-us/outlook-help/repair-office-programs-HA010357402.aspx
Hope this helps, and feel free to post back with any findings.
Thanks,
Ethan Hua CHN
TechNet Community Support

Deploy Office 2013 with language pack

Hi,
We want to deploy Office 2013, for this I followed the tutorial:
http://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
In the first step I need to make an MSP file, but this file doesn't get used in the deployment? I think this is a fault in the tutorial.
Also the uninstall string is setuP.exe /uninstall. Is this correct?
Second we want to deploy the dutch language pack with SCCM 2012, but I can't find out how. The package need to be installed but Office 2013 still need to be default language English.
Can someone help me out with this?
Thanks in advance.

Some troubleshooting tips:
Run the installation command locally using SYSTEM account (Get psexec.exe, open cmd, run "psexec.exe -s cmd", this will open a new command line window with SYSTEM privilege, try running your installation command there)
Check the Office 2013 installation logfiles to see if your configurations are correct, more info on that here:
http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx
After those two steps are ready and you're sure your installation command works, you try it with ConfigMgr
With ConfigMgr, check %windir%\ccm\logs\ -folder for AppEval.log, AppEnforce.log and AppDiscovery.log, more info on these logfiles you can find here:
http://blogs.technet.com/b/configmgrdogs/archive/2012/05/26/new-logs-in-configmgr-2012-client-logs.aspx

Office 2013 Bug - Numerals Are Displayed In The Wrong Language.

My system: Win 7-64 , Office 2013-64 - US English
In Microsoft Word 2013 and PowerPoint 2013, when the user types in Persian using the Microsoft Persian keyboard that ships with Windows, and the option
of “Context” has been selected for the display of numerals in the Office Advanced Options, the numerals display in Arabic instead of Persian. Pay close attention to numerals 4, 5, and 6. This bug did NOT exist in Microsoft Office 2010
and 2007.
English Numerals
Persian Numerals
Arabic Numerals
0
۰
٠
1
۱
١
2
۲
٢
3
۳
٣
4
۴
٤
5
۵
٥
6
۶
٦
7
۷
٧
8
۸
٨
9
۹
٩
Table
1

Hi,
Please follow the link to re-set the language and download again：
If you have Microsoft Office Professional Plus, under Install Microsoft Office Professional Plus, select your desired language option and choose either the 32-bit or 64-bit version, and then click
Install.
http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff637594.aspx?ss=0bd4602a-5ec3-4b1c-8b0e-dfadca5da0df&ss-src=featuredhelp
If you had further question about the issue, please post it to Microsoft Office 365 Community Forum:
http://community.office365.com/en-us/forums/default.aspx
Thanks,
George Zhao
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 "[email protected]"

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

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

Office 2013 partialy virtualized breaks Outlook2013

Hi,
We tryed to virtualize Access Visio and Project 2013 in one package using the Click to Run method. For this method we made a xml file with the following content:
<Configuration>
    <Add SourcePath="C:\Temp\Project\Download" OfficeClientEdition="32" >
    <Product ID="ProPlusVolume" >
      <Language ID="nl-nl" />
      
<ExcludeApp ID= "Outlook" />
      <ExcludeApp ID= "Excel" />
      <ExcludeApp ID= "Groove" />
      <ExcludeApp ID= "InfoPath" />
      <ExcludeApp ID= "Lync" />
      <ExcludeApp ID= "OneNote" />
      <ExcludeApp ID= "PowerPoint" />
      <ExcludeApp ID= "Publisher" />
      <ExcludeApp ID= "SharePointDesigner" />
      <ExcludeApp ID= "Word" />
    </Product>
    <Product ID="ProjectProVolume" >
      <Language ID="nl-nl" />
      
    </Product>
    <Product ID="VisioProVolume" >
      <Language ID="nl-nl" />
      
    </Product>
</Add>
  
<Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="Office2013Setup.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
When using this xml to download and build the appv package the ExcludeApp tags seem to be ignored. I end up with a package containing all parts. But this is only problem 1 there is a second problem: When the AppV package is deployed on a machine with Outlook
2013 and installed in the base image with the Office 2013 installer. Then each time Outlook is started it gets repaired. When the AppV is unpublished this behaviour stops.
The question i have is it supported to deploy Office 2013 half native and half as AppV on the same system. This sounds wierd but many organisations only want part of their employers to have tools like Access. In case of deploying on terminal server it is
nice to give most users the base like Outlook,Word,Excel and Accessruntime. And some privileged users the Access,Visio Project AppV package as addition.
Is this scenario possible with AppV 5 or should all parts be installed native and use a some sort of user profile control to control who gets what?
regards,
Leon.

Use a clean machine for ODT, I use a VM with snapshots.
See:
https://social.technet.microsoft.com/Forums/en-US/2bda7882-80d1-4ebc-a6e8-32d47f74aaad/office-2013-packageguid?forum=mdopappv#9c5478e8-9cac-434d-bd50-f59b0aae13f7

Cannot install PIA on Windows 8.1 64-bit with Office 2013 64-bit

I am building a clean machine after a hard drive failure. Everything is finally reinstalled WITH THE EXCEPTION of the Office Interop for Office 2010. I have a clean install of Windows 8.1 which also has Office 2013 installed.
The documentation for the 2010 library is that it only requires the framework 2.0 present (which is) so it should install. However when I run the installation program is throws up the window "determining requirements" runs for a few seconds
then disappears.
All I need is to get these things showing up in the GAC so I can get a clean build. But try as I might I don't have them showing up at all. Any help would be greatly appreciated!!!
ADDITIONAL INFO:
When I run the MSI file it brings up the window that says it is gathering information.
This run for about 1 second (if that) moves the progress bar about halfway across, then stops and closes down the installation.
We also installed Office 2010 and reran the PIA with the same results. *sigh*

Why do you need to install Office 2010 PIAs?
Consider embedding interop types into the assembly without using PIAs on the end user PCs.
Beginning with the .NET Framework 4, the common language runtime supports embedding type information for COM types directly into managed assemblies, instead of requiring the managed assemblies to obtain type information for COM types from interop assemblies.
Because the embedded type information includes only the types and members that are actually used by a managed assembly, two managed assemblies might have very different views of the same COM type. Each managed assembly has a different Type object
to represent its view of the COM type. The common language runtime supports type equivalence between these different views for interfaces, structures, enumerations, and delegates. See Type
Equivalence and Embedded Interop Types for more information.
You just need to set the Embed
Interop Types property to True.

Office 2013 Shell UI Language

Similar Messages

Maybe you are looking for