Office 2013 GPO Silent install doesn't run consistently

client is all Dell Win 7. Servers are 2012. Project is to install Office 2013 silently with GPO at computer start. Everything is configured correctly and it works on some computers. I set it install in a larger group by linking the GPO to that group of computers. Told everyone to reboot and waited. Nothing. It didn't install. I know it works because I haven't changed it and I have seenit work multiple times. Try another reboot. Nothing. Then one of them works. Then another. Then another. Not all at once and not always at reboot. Some of them just install in the middle of the day. Is this a "load balancing" feature where all of them are not installed at once so the server isn't overwhelmed? If not, why does it work sometimes and then at random times. The actual install doesn't take very long. Maybe my server doesn't have the horsepower...
This topic first appeared in the Spiceworks Community

I've not tried the Dashboard connection yet.
I will try to connect and setup permissions using TDADM.
This is my thoughts etc. so far;
problem starts when running dpconfig.exe - therefore I can skip re-running (and 'repairing') the install using the MSI
dpconfig doesn't appear to have any command line options? (ran "dpconfig /?" from a command line and still just launched the wizard)
so far, even if permission are or get set correctly, processor hasn't been linked to the share yet - only dpconfig can do that?
had installed the Processor on Server 2012 in Core UI. Thought dpconfig might be trying to launch Explorer, which isn't available in Core, so went up to "Server with GUI" (bypassing "minimal"). However, this didn't change anything. Left at Server with GUI
for now (although would prefer to run as Core if supported - nothing says it isn't?)
by default, our server config blocks all Firewall ports incoming (the out of the box config) only opening up ports as required. I'll try turning the Processor Firewall off.
Seems like not a lot of people do this (install the 2013 Telemetry), as very little online apart from Microsoft pages. Trying to dig through the Powershell script posted (by you Jill?) here;
http://blogs.technet.com/b/office_resource_kit/archive/2012/09/25/quickly-set-up-office-telemetry-dashboard-on-a-workgroup-or-domain-joined-computer.aspx . However, looks like even in this one that for domain joined machines, dpconfig is launched interactively,
so still no cmd line options!

Similar Messages

What query should I use to find all versions of Office 2013 64-bit installed on client computers?

What query should I use to find all versions of Office 2013 64-bit installed on client computers? Could someone create a custom query? I need all of the client computers names and which ones have any Office 64-bit components. Thank you so much! I really
appreciate it!

Hi,
You could edit the following query to meet your requirement.
SELECT     dbo.v_R_System.Name0, dbo.v_GS_OPERATING_SYSTEM.Caption0 AS [Operating System],
                      dbo.v_GS_OPERATING_SYSTEM.CSDVersion0 AS [OS Service Pack], arp.DisplayName0,
                      CASE WHEN arp.version0 LIKE '11.0.6361.0' THEN 'SP1' WHEN arp.version0 LIKE '11.0.7969.0' THEN 'SP2' WHEN arp.version0 LIKE '11.0.8173.0'
THEN 'SP3' WHEN
                       arp.version0 LIKE '12.0.6215.1000' THEN 'SP1' WHEN arp.version0 LIKE '12.0.6425.1000' THEN 'SP2' WHEN arp.version0 LIKE '14.0.6029.1000'
THEN 'SP1' ELSE '' END
                       AS 'Service Pack', arp.Version0
FROM         dbo.v_Add_Remove_Programs AS arp INNER JOIN
                      dbo.v_R_System ON arp.ResourceID = dbo.v_R_System.ResourceID INNER JOIN
                      dbo.v_RA_System_SMSInstalledSites AS ASSG ON dbo.v_R_System.ResourceID = ASSG.ResourceID INNER JOIN
                      dbo.v_GS_OPERATING_SYSTEM ON dbo.v_R_System.ResourceID = dbo.v_GS_OPERATING_SYSTEM.ResourceID
WHERE     (arp.DisplayName0 LIKE '%Microsoft Office%edition%' OR
                      arp.DisplayName0 LIKE '%Microsoft Office Standard 2007%' OR
                      arp.DisplayName0 LIKE '%Microsoft Office Enterprise 2007%' OR
                      arp.DisplayName0 LIKE '%Microsoft Office Professional%2007%' OR
                      arp.DisplayName0 LIKE '%Microsoft Office Standard 2010%' OR
                      arp.DisplayName0 LIKE '%Microsoft Office Enterprise 2010%' OR
                      arp.DisplayName0 LIKE '%Microsoft Office Professional%2010%' OR
                      arp.DisplayName0 LIKE 'Microsoft Office 2000%' OR
                      arp.DisplayName0 LIKE 'Microsoft Office XP%') AND (arp.DisplayName0 NOT LIKE '%update%') AND
                      (arp.DisplayName0 NOT LIKE '%Microsoft Office XP Web Components') AND (dbo.v_R_System.Operating_System_Name_and0 NOT LIKE '%server%')
AND
                      (arp.InstallDate0 NOT LIKE 'NULL')
ORDER BY dbo.v_R_System.Name0, arp.DisplayName0, arp.Version0
Full details:http://social.technet.microsoft.com/Forums/systemcenter/en-US/7baeb348-fb63-4115-8d76-2c884d18f708/sql-query-to-check-ms-office-service-pack-level?forum=configmgrreporting
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Office 2013 Home and Business - Click to Run wipes out the Office files from the Programs folder

We are having an issue with a number of clients running Office 2013 H&B in a domain environment, after a click to run update.
It appears the update is ran in the background and after a reboot, the program files short of a few .DLL's are completely missing. Office still shows as installed through the control panel.
We have to use the office removal tool and reinstall program completely. System restore does not fix the issue.
These are Dell Latitude and the version of Office shipped with the machines as an OEM version. There was nothing pushed from the Dell update utility for Office.
They are running Avast AV and it is not affecting all users presently.
I've been on hold and getting transferred around Microsoft's support lines all day as Microsoft support can't seem to figure out which department should troubleshoot the issue.
Any assistance would be greatly appreciated.

I am doing some research. And I might involve someone who is more familiar with this kind of issue to deal with this problem.
Cheers,
Tony Chen
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 contact
[email protected]

Office 2013 Home and Business OEM First Run screen

Hi There
We are starting to roll out office 2013 oem Home and Business our users are reporting that the first run screen get coming up every time there open an office application.
In Group Policy I've disable the First Run Movie and Office First run on application boot however the users are still getting to first run screen this is every annoying.
Any help with would be great?
Cheers,
Brett

The policy setting should work: it correctly adds bootedrtm=1 value to HKCU\Software\Policies\Microsoft\office\15.0\firstrun. But for some reason Office apps ignore it. I tried disabling the entire policy, then go through the welcome screen. After finishing
with it, office created the same value, but in another place (HKCU\Software\Microsoft\Office\15.0\FirstRun), and the screen never appeared anymore.
So to make the setting work, you have to manually create registry setting (via GPO preference) with the following data:.
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\FirstRun]
"BootedRTM"=dword:00000001
P.S. this was pretty easy, but did anyone look at disabling the EULA prompt? The acceptance is marked by creating a registry key for each user, but the path contains computer name :)) Therefore if all users of the PC have accepted the agreement, and you
renamed the computer, the popup comes back again. And of course group policy is impossible with such path.

Office 2013 patches not installing

I am trying to install some updates for office 2013 through Windows update and I keep on getting the error message 80070663 when installing these (8 so far). Other windows patches
install fine. I am running Windows 7 Pro in a Domain environment and am a domain admin running these with full admin privileges.
I have tried just about every fix suggested in every other post
- Rebuilding the Windows Update environment
- Running Sfc (no errors)
- Running the relevant Fixit's (no issues or repairs found)
- Running Chkdsk Scan (no errors)
- Downloading the patches and trying to run them manually (They error out with a applicability test error)
- Running Antimalware and similar scans (nothing)
- Running a repair on Office 2013 (errors out with a 5 error towards the end of the repair - faulting module msvcrt.dll fault offset 35e1
- Downloading and reinstalling the C++ library re-distributables (i.e. msvcrt.dll)
Not this is only on the Office patches and not any other patches which suggests an office problem rather than a Windows update issue.
Anyone got any thoughts - There was a suggestion that this might be caused by missing update packages...

Hi,
Apologize for the late reply.
Regarding Office issue, have you tried Repair Office programs from control panel?
Follow this guide:
Repair Office programs
Change recommended update and diagnostic settings
Further, since this is more related with Office, it is recommended to ask inthe office forum for a better assistance:
Microsoft Office IT Pro
http://social.technet.microsoft.com/Forums/office/en-US/home?category=officeitpro
Best regards
Michael Shao
TechNet Community Support

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

Error 25004. The product key you entered cannot be used on this machine. This is most likely due to previous office 2013 trails being installed

I've spent several hours researching this issue, I've clear the registry, I've used the tool fix it program and nothing works. This all started after my computer stop functioning properly and I did a refresh, I've been able to reinstall all the programs
except office. Any help will be appreciated.

Hi,
May I know what version of Office has been installed on the machine before? What version are you trying to install now?
Please also let me know the Windows version so that I can know the scenario more clearly.
When you use Fix it tool to uninstall Office, make sure you have selected the correct Office and Windows version:
http://support.microsoft.com/kb/971179
Regards,
Melon Chen
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.

PDF created from Office 2013 with Acrobat X doesn't have correct page size

We have a process of quickly creating PDFs along with combining several Word files to PDF by utilizing the "right click" on a Word file(s) to save as a PDF within Windows. Many times, our page size in Word is 5.5 X 8.5 and it does not save actual page size once PDF is created by using the "right click" and defaults to 8 1/2 X 11. Is there a way to fix this or edit a setting? It works fine from within Word if you "Save as" or "Export" but we need the right click to save as actual page size. Please help. It worked fine in all previous versions of Word/Office. Thanks!

Hi pwhite2315,
Could you please let me know what version of Acrobat are you using.
Try using 'Create PDF' option under Acrobat ribbon in your word file and check for the same.
Also, please open 'Preferences' for Acrobat PDFMaker and check what 'Conversion Settings' have you selected.
Let me know.
Regards,
Anubha

Unable to install MS Office Proofing tools 2013 SP1 even after installing MS Office 2013

Hi All,
When I run the "proofsp1.exe" manually by double clicking on it, I get the below error message. Proofing tools has already been installed and I am trying to install Proofing tools Service Pack1.
"The expected version of the product was not found on the system."
MS Office 2013 is already installed in the machine.
Few more details about the issue:
Which language are you trying to install the proofing tools for?
I am trying to install on English for testing purpose. I am facing the same issue on other languages as well.
What is the language of office you have installed?
English
Are you working on 32 bit or 64 bit version of Office?
32-bit
At last I was able to install "proofsp1.exe" using the below command line with User Interface.
"proofsp1.exe" "PACKAGE.BYPASS.DETECTION.CHECK=1"
But not able to install it silently using the below command line
"proofsp1.exe" "PACKAGE.BYPASS.DETECTION.CHECK=1" "/quiet /norestart"
Please advice how to install "proofsp1.exe" silently or without the
"PACKAGE.BYPASS.DETECTION.CHECK=1" parameter.
Thanks in advance.

Hi George,
It does not accept "PACKAGE.BYPASS.DETECTION.CHECK=1".
It throws the help window with all the switches on using this command line
proofsp1.exe
PACKAGE.BYPASS.DETECTION.CHECK=1 /quiet /norestart
Can anyone please tell, why am I getting the below error message when MS Office 2013 and Proofing tools has already been installed.? I am trying to install MS Office proofing Tools 2013 SP1
"The expected version of the product was not found on the system."
Thanks.

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 Click-to-Run

All,
We are having issues with some customers that have the Office 2013 Home and Business Click-to-Run version of office installed. Users are randomly having their installation corrupted. This interestingly enough didn't start happening until SP1 was released
for Office 2013. I am aware that click-to-run installations of office don't update via Windows Updates direct but through another method. Is anyone else seeing this happen? Any thoughts would be appreciated.
Some of the symptoms are as follows:
1. None of the Office apps open. You double-click but nothing happens nor are there any processes running.
2. If you open an office document direct you might get a message something to the effect of There was a Problem sending the command to the program. None of the documented fixes appear to correct the issue for this type of error.
3. A system restore point fixes it but it breaks again within a day or two.
4. The only fix at this point is to uninstall (Using FixIt KB2739501) and reinstall which of course pulls down the latest build with SP1.

Hi,
You can probably fix the issue by updating the video driver to the latest.
Please refer to this thread below, many users had the same issue and solved it by updating the video driver:
http://social.technet.microsoft.com/Forums/en-US/34401d63-6c3b-47e6-ab20-9ed9b70d890b/outlook-2013-sp1-unusable-since-sp1-update-?forum=officesetupdep
Thanks,
Melon Chen
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

Error installing Office 2013 on Server 2012 R2 RDS - Error 25004: the product key you entered cannot be used on this machine

Hi there,
I really hope someone can help me as I am tearing my hair out trying to get this resolved!
I am working on a Server 2012 R2 server with RDS running. Before it was turned into a RDS server it had a copy of Office 2010 running as a trial to see would it work for the accounting package that is running for users via Remote Desktop. Trial worked ok
so it was converted into a RDS server. Now, as its a RDS it needs to run Office under a volume licence, which I have. However when trying to install I get the message: "Error 25004: the product key you entered cannot be used on this machine. this is most
likely due to previous Office 2013 trials being installed on the system."
In summary I have tried everything I can think of and find to remove all traces of the old Office from the machine but still this message persists. I have run the Fix It For Me uninstall from MS and it cannot find any Office installed. i have manually searched
through all of the Windows directories including Program Files and AppData and removed all traces of Office from there, I have searched the registry and removed all I can find from there.
Where or what file does the installer look at to see that a previous version was installed?
I cannot scrub this machine which I would have done long ago because there is another SQL Server based application running on it.
Really really appreciate anyone that can help me on this,
Thanks

Hi,
I have definitely heard your frustration, and I’ll try my best to help you.
Since Office 2010 installed on it before, you need to remove Office 2010 completely.
KB about this error:
http://support2.microsoft.com/kb/2792178
A similar issue is addressed here. Although this method is based on Office 2010, but we can have a try:
http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Q_28475448.html
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best regards,
Greta Ge
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.

How to add MS Office add-in from inside a Thinapp 5 virtual application to a MS Office 2013 suite that is installed on a base image

Hi,
We have the following solution:
VMware Horizon View 5.3.1
Non-persistent Linked-clone pool with delete VM after logoff
Windows 8.1 Update 1 Enterprise 64 bit
MS Office 2013 32-bit installed on image
Thinapps registered for each user from logonscript with thinreg.exe command. Thinapps is located on a network share
Native Windows roaming profiles with appdata/roaming, appdata/local without appdata/locallow(persona management does not support Windows 8.1 in View 5.3.1)
This is our issue:
We have a 3rd party application with a couple Thinapp entrypoints(exe files) and in the Thinapp package process we also installed Office addins. We tested that the Add-ins was opened inside Outlook, Word and Powerpoint before post installation scan.
The problem is that the add-ins is not added to Office 2013 before or after the Thinapp is started on a test client.
I have tried several changes in the package.ini and virtual filesystem attributes(no registry changes yet):
Package.ini:
ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;
ChildProcessEnvironmentDefault=External
ChildProcessEnvironmentExceptions=excel.exe;outlook.exe;powerpnt.exe;winword.exe
ChildProcessEnvironmentDefault=Virtual
VirtualizeExternalOutOfProcessCOM=0
DirectoryIsolationMode=Merged
RegistryIsolationMode=Merged
I have also read that you could make entrypoints to the locally installed Office 2013, but I get errors on the build process. ref. link: http://edwinfriesen.nl/content/?p=105#comments
The best thing would be if the add-ins were added in the logon process together with thinreg.exe, but if that is not supported, the add-ins must be added to Office either in a custom Office shortcut/entry point or after starting the Thinapp virtual application.
Remember that the application needs to registered every times the user logon, because we use a non-persistent View pool.
I would really appreciate if somebody could tell me how to add Office add-ins from inside a Thinapp virtual application/package to a locally installed MS Office 2013 suite on a Windows "base" image?
We do not want to add the whole Office suite to the Thinapp virtual package and not add the add-ins trough GPO,SCCM etc.

What about the COM object parameters in package.ini ?
We can live with scripting in logon or changed logon scripts etc.
And you don't no need to lock in the project files.
From package.ini documentation:
ObjectTypes Parameter
The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications in
the physical environment. You can use scripts, such as VBScripts, to call objects that start captured applications.
An object type is registered to only one native or virtual application at a time. If you install Office 2003 on the
native machine and want to use a virtual Office 2007 package, you must determine whether to have the virtual
or native application handle the object types.
If you want the virtual Office 2007 to handle the object types, you can leave the ObjectTypes setting in the
Package.ini file, build the package, and register it using the thinreg.exe utility. If you want the native Office
2003 to handle the object types, you must remove the ObjectTypes setting from the Package.ini file before
building and registering the package.
You cannot add random entries to the ObjectTypes parameter.
You can only remove entries that were generated by the capture process.
Example: Starting a Virtual Application When a COM Object is Created
If a script or a native application creates an Excel.Application COM object or other COM objects listed in the
ObjectTypes parameter, ThinApp starts the virtual package.
[Microsoft Office Excel 2007.exe]
ObjectTypes=Excel.Application;Excel.Application.12;Excel.Chart;
Excel.Macrosheet;Excel.Sheet; Excel.Workspace

Unable to Install Office 2013 Pro and I get returned message "Couldn't Install We're sorry, we had a problem installing your office programs"

I purchased 40 licenses of Office 2013 Pro from a vendor in the US and received 40 product keys along with the URL to download the software - 1 for each pc activation codes. I have done a few and were all successful. I am now trying
install on 2 other pcs and I am having real difficulty and getting error message each time I try to install. I am able to download the installer and copied to my desktop and when I double click to execute it, it gives me the option to run on the next
screen. I click on run then it gives me the message " do you want to allow the program to make changes to this computer". When I press YES, nothing happens and minutes later, I get the flwg message everytime, "Couldn't
install" "We're sorry, we had a problem installing your office programs. Is your internet connection working? Do you have enough free space on your main hard drive? Please try installing again after you've checked the above.
Go online for additional help.
I have lots of space and my pc is Win 7 64 bit new machine. I have connection to internet and I was able to get the others done. What is the problem here and I have been trying to work late night hours to try to install the program and I am unable
to successfully get it to work. I receive the same message every time and I followed all the recommended troubleshoot steps I found on the internet. Someone please help. I have to install all for all the PCs we have for our organization.
Please respond because I am really stuck.
Gabe

Hi Gabe,
First, please check the suggestion above is helpful. I also suggest you removing all version of Office and re-install Office 2013.
We can try to run the application as an administrator and check if it works.
1. Right click the shortcut of the application or the main application.
2. Select properties.
3. Select compatibility tab and select "Run this program as an administrator."
If there is anything I can do for you about this issue, don't hesitate to tell me.
Best regards,
Greta Ge
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.

Unable to install 32 bit version of Office 2013

We had several computers deployed with the 64 bit version of Office 2013. Due to some unforeseen compatibility issues, we needed to remove the 64 bit version and then install the 32 bit version. While we have been able to remove the 64 bit version,
we are not able to install the 32 bit version. After we click setup.exe, We simply see the Office 2013 splash page that mentions "Please wait while setup prepares the necessary files" and then it disappears. Nothing in the event log either.
Any idea what is going on and how to resolve this?

Hi,
Do you mind telling us which category of Event viewer have you checked?
Most of the setup error log may be stored in Setup category, and some in Application category.
If there are some error logs, please upload, they'll help us to troubleshoot this issue.
Then, this issue also may be due to the remain of Office 2013 64bit. I recommend we remove it manually and clean the registry key:
==========
Method 1
Open C:\Program Files\Microsoft Office 15\root\integration\
Delete all C2RManifest*.xml files in that folder.
Open an elevated command prompt. Tap on Windows, enter cmd, right-click on the result and select run as administrator from the menu.
Type cd "C:\Program files\Microsoft Office 15\root\integration".
Type integrator.exe /U.
To remove the Office 2013 preview scheduled tasks run the following commands.
Type schtasks.exe /delete /tn "FF_INTEGRATEDstreamSchedule"
Type schtasks.exe /delete /tn "FF_INTEGRATEDUPDATEDETECTION"
Type schtasks.exe /delete /tn "FF_INTEGRATEDOffice 15 Subscription Heartbeat"
Keep the command prompt open.
Open the Task Manager with Ctrl-Shift-Esc.
Click on the Process tab and kill the following processes: integratedoffice.exe,
appvshnotify.exe, firstrun.exe and setup*.exe.
Type sc delete OfficeSvc at the command prompt.
Open Windows Explorer and delete the Microsoft Office 15 folder
Open %ProgramData%\Microsoft and delete the ClickToRun folder
Open %ProgramData%\Microsoft\office and delete the
FFPackageLocker file
Press Windows, type regedit and hit enter to open the Registry editor
Delete the following Registry keys.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppVISV
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Office 15 - ProfessionalRetail - en-us
Note that the name of the last Registry key depends on the installed version of Office.
Delete Office 2013 start menu shortcuts
Open %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs and delete the Office 2013 folder
Go to the command prompt and run one of the following commands:
If you are running an x86 version of Office 2013 and an x64 operating system run the following command:
MsiExec.exe /X{50150000-008F-0000-1000-0000000FF1CE}
If you are running an x86 version of Office 2013 and an x86 operating system run the following command:
MsiExec.exe /X{50150000-007E-0000-0000-0000000FF1CE}
If you are running an x64 version of Office 2013 and and x64 operating system run the following command:
MsiExec.exe /X{50150000-008C-0000-1000-0000000FF1CE}
Run the following command afterwards: MsiExec.exe /X{00150000-008C-0000-0000-0000000FF1CE}
Method 2
Open the %windir%\Installer folder. Make sure you can view Hidden files and folders on your system
Select View, then Choose Details
Select Subject, type 340 in the width of the column and click ok. This may take several minutes before subjects appear.
Select View > Sort by > Subject
Locate all .msi files that have Microsoft Office 2013 product names and uninstall them.
Use Windows-R to open a run box
Enter services.msc and hit the enter key
Locate Office Source Engine and right-click the service and select
Stop from the context menu.
Open the %CommonProgramFiles%\Microsoft Shared folder or
%CommonProgramFiles(x86)%\Microsoft Shared on a 64-bit operating system
Delete the folders Office15 and Source Engine from the folder list.
Open the %ProgramFiles%\Microsoft Office folder or %ProgramFiles(x86)%\Microsoft Office on 64-bit systems
Delete the Office15 folder.
Open the MSOCache folder on the root of the hard drive
Open the All Users folder and delete every folder that contains 0FF1CE} in the name
Open the folder %appdata%\microsoft\templates
Delete the following files Normal.dotm and Welcome to Word.dotx
Open the folder %appdata%\microsoft\document building blocks
Delete the building blocks.dotx file
Press Windows-r, type regedit and hit enter
Open the following Registry key: HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
Delete the following Registry keys if you are running a 32-bit version of Windows.
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\*0FF1CE}-*
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Upgrade Codes\*F01FEC
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\*F01FEC
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
HKEY_CLASSES_ROOT\Installer\Win32Assemblies\*Office15*
Delete the following Registry keys if you are running a 64-bit version of Windows
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\15.0
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\Delivery\SourceEngine\Downloads\*0FF1CE}-*
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
HKEY_CLASSES_ROOT\Installer\Win32Asemblies\*Office15*
On a 32-bit version of Windows, open the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
On a 64-bit version of Windows, open the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
Select File > Export, type UninstallKey01 and select Save.
Under the uninstall key determine the subkey that has the following values:
Name: UninstallString
Data: file_name path\Office Setup Controller\Setup.exe path
Delete the keys that match the data and repeat the process until all keys have been processed.
====
On the other hand, the installation source also may be a factor, please try to change one and test.
https://products.office.com/en-us/download-back-up-restore-microsoft-office-products?legRedir=true&CorrelationId=9398947d-5b49-4e53-a203-0ef5ff858293
Hope it's helpful.
Regards,
George Zhao
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.

Office 2013 GPO Silent install doesn't run consistently

Similar Messages

Maybe you are looking for