Office 2013 Deployment in a Multisite Environment

We want to upgrade our 200+ clients to Office 2013 but I have encountered 2 major issues.
The first is that we have multiple sites with slow network links (less than 512k) so I need to be able to install and update from the local file server. All our file servers have an install share mapped to I: that replicates from a central location every
day which is where the install files are located.
Problem is I seem to have to specify the server name for the configuration XML file to work. I have tried using the %LOGONSERVER% environment variable but this hasn't worked. I could create an xml file for each sit but I'd rather avoid it as sometimes we
move computers around and I don't want them trying to update from another site and flooding the WAN link.
The second is that as we have slow links and large inboxes I need to find a way to move the email from the users 2010 inbox into their 2013 inbox. When I update to 2013 it downloads them all again. I can export from 2010 then import into 2013 but this just
adds it as an additional inbox.
Any suggestions would be greatly appreciated.

1. That's ok we have already got a File server which seems to run DFS Replication in those slow bandwidth network connections sites.
But have you already move the Office installation source onto the file server which located in site 2? Why you need to configuration XML file currently? To avoid network flooding during the upgrading, please configure the DFS sync time in the off-working
times.
2. In general, Outlook would pick up the existing OST file and reload it after upgrading. Please detail what's your upgrading steps and we could further help you.
Tony Chen
TechNet Community Support

Similar Messages

Office 2013 deployment tool Invalid product ID error

Hi,
Im in the process of virtualizing apps like Office 2013 with App-V.
Downloading the binaries with the Office Deployment tool and converting to app-v package is very easy, I've followed this kb
http://support.microsoft.com/kb/2915745
But now I want to sequence add-ins for Office 2013. So I need a local install of Office 2013 click to run.
Im trying to use the command line option setup.exe /configure <path to config.xml> but everytime I try this I receive this error:
Invalid product ProPlusVolume specified. Error configuring products
I have tried several different ProductID's like ProPlusVolume and StandardVolume. None of the volume ID's seem to work. When I changed the ID to ProPlusRetail, the setup worked flawless. But I need to install the Volume version for my RDS server...
I have found other people in the comment section in this blog: http://blogs.technet.com/b/office_resource_kit/archive/2013/12/03/3615124.aspx
(read the comments in the bottom section) But no solution..?

It's my understanding that you don't use the "/configure" parameter when using the "Volume" options.
Jeremy refers to this in the comments/responses.
In the main blog article, he refers to "You can now use the Deployment Configuration file to configure...."
This does not mean that you should use the "/configure" parameter - that is only used for C2R.
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!)

Office 2013 deployment customisation

Hello,
just added O2013 to applications. Used OCT, placed msp to Updates. Run litetouch from test VM.
Installation run silently. 100% success.
Here are the points that I would like to adjust:
1. When first started Word. I got the Windows with update chooses.
The truth that I don't deploy Office updates by WSUS. But probably will do.
After OS deployment WSUS update is enabled. So no problems with OS.
Let's assume that my WSUS will deploy Office 2013 updates. So I can probably enable post Application updates.
Currently I do post OS updates.
Is there a step in OCP to skip the Updates screen on first Office start?
Can activation window be suppressed if product key is inserted in OCT? Kind of automatic activation try?
This is not difficult one click but would like to leave Office without any "welcome" screens.
Please specify the step in OCT where I can to customize that.
Also my Office 2013 contains SP1. So probably I can keep Office 2013 patches on WSUS starting January 2014 since SP1 dated
Feb 2014. Is it right assumption?
Thanks.
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

Please follow the instructions here. Open OCT. Navigate to Features-Modify User Settings.
Select Microsoft Office 2013-->Privacy--> Trust Center
Disable Opt-in Wizard on first run-> Set to ENABLED
Enable Customer Experience Improvement Program--> set to DISABLED
Automatically receive small updates to improve reliability--> DISABLED
Then under Microsoft Office 2013--> Miscellaneous
Suppress recommended settings dialog--> set to ENABLED
Activation depends on if your using KMS or MAK keys. What are you using so I can assist you further...

Office 2013 deployment

I'm in the process of building a package to deploy office 2013. Everything works as it should except uninstalling office 2010. OCT only does a partial uninstall of office 2010 but leaves evidence in Programs and features as well as the folder in Start
up. Does anyone have a solution for this?

Configure an application for Office 2010, configure Office 2013 to supersede 2010 and deploy, simple as that. What you need is uninstall command for 2010, install command for 2013 and detection method for both. There's no need for task sequence to accomplish
what you want, the trickiest part is probably getting the right detection method, you can use the product code of Office MSI package. For install/uninstall commands, follow the official documentation or try Google. Use script installation method and use the
setup.exe with .xml created with OCT.

Add Dictionary in Office 2013 Deployment

Is there a way to include a Dictionary as part of the unattended install without logging into the App Store post install?
http://office.microsoft.com/en-us/word-help/install-a-dictionary-HA102840137.aspx

Office 2013 now allows you to add a custom dictionary from Office Store, am not sure how to deploy such an dictionary APP during the Office deployment.
But I assuming you might still can deploy a Traditional dictionary. Please refer to this blog post, hope it will give you some light:
http://blogs.technet.com/b/office_resource_kit/archive/2011/12/16/deploying-a-custom-dictionary.aspx
Thanks,

Deploy Office 2013 using Group Policy

Below are a list of questions I have regarding setting up Office 2013 deployment automation. We are looking to deploy Office 2013 Business Click-to-Run using a group policy. We have already setup the deployment using the Office Deployment Tool and have
the configuration file all setup. The more automation we can provide the better to give the end users to best/fastest experience with this upgrade.
How do we automate the deployment process using a group policy?
Is there a way to have the Office 2013 deployment auto activate using the users credentials? We will be using the same password for all the user accounts for the deployment then having them change it later once everything is up and running. Would like to
avoid having to go around and help each user activate the software as well.
We would like to uninstall all previous versions of Office from the workstations that we're deploying Office 2013 to?
Thank you!

Below are a list of questions I have regarding setting up Office 2013 deployment automation. We are looking to deploy Office 2013 Business Click-to-Run using a group policy. We have already setup the deployment using the Office Deployment Tool and
have the configuration file all setup. The more automation we can provide the better to give the end users to best/fastest experience with this upgrade.
How do we automate the deployment process using a group policy?
Is there a way to have the Office 2013 deployment auto activate using the users credentials? We will be using the same password for all the user accounts for the deployment then having them change it later once everything is up and running. Would like to
avoid having to go around and help each user activate the software as well.
We would like to uninstall all previous versions of Office from the workstations that we're deploying Office 2013 to?
1. Because Office (in all forms) requires setup.exe to orchestrate the installations, classic Group Policy Software Installation (which requires an MSI file) is not suitable. This has been the case since Office2007. If you are constrained to use GP, you
will need to use GP Startup Scripts. There is guidance for this, in the Office resource kit library on TechNet.
http://technet.microsoft.com/en-us/library/ff602181(v=office.15).aspx
2. Retail editions of Office, typically require you to login to the Microsoft Account where the license is associated, to validate the Office license. If you are using a product key method instead, you can use the PIDKEY element in your configuration.xml
http://technet.microsoft.com/en-US/library/jj219426(v=office.15).aspx
3. You'll need to tackle this yourself (there is no way to do this via C2R configuration). You could include the relevant uninstall-previous-version logic within your GP Startup Script (as a step prior to installing Office C2R). You'll need to cater for
whatever previous-versions might exist in your environment, and whatever the relevant uninstallation methods are for each previous-version.
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!)

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 Std (local) in combination with Office 2013 Pro (App-V)

Hello,
I have multiple RDS servers, that have Office 2013 Std installed locally. I did this on purpose, after reading some blogs pointing out Office 2013 is a complicated applicatie to stream well. And of course Office 2013 is highly critical to my clients.
So I have a local installation of Office 2013 Std on every RDS server.
The catch is, that the client also has an open license for Office 2013 Pro. This is because some users need to work with 'Access 2013'.
So I thought it would be nice to use App-V to stream Access 2013 to the RDS servers. I have created the package for Office 2013 Pro, with Access in it. And I succesfully published Access 2013 to the group of users. So I can use Access on the RDS servers.
The problem is, that when I click on the appliation "MSACCESS.exe", the application pops up in taskmanager and is immidiatly shut down again. So it never launches. No error, no nothing.
I can't find any directions in the server, applicatie or App-V logs in the eventviewer. Does anyone have a clue where to look?
Thanks in advance

I think to be on a safe side, using a 'true' control system like AppSense or using dedicated RDS servers would be the only legally valid option.
Even when Office (or at least Access) is virtualized, the licensing part and product key handling is done natively on the RDS servers by the 'Office 2013 Deployment Kit'. Besides others this includes a locally installed 'licensing stump'. Therefor there
can be only one Office Suite product key be assigned to a RDS server machine.
In fact you could tell the Deployment Kit to use the Office Pro key (allowing a virtualized Access to run), but then also the locally installed Office Version would (attempt to ) be licensed as 'Pro'. That potentially won't work. In fact you could re-configure
the local Standard Office installation to consume Pro licenses, but that doesn't fit to your legal licenses.
As Aaron write, legally an Office license is bound to the endpoint device, so you'd have to make sure that your Access App-V package can only be access by permitted client machines. And while App-V can filter application on the accessing user and the executing
machine, it can't filter on the accessing end-point.
Though we don't like it... 3rd party or a server silo seem the way to go.
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Deploying MS Office 2013 with GPO

OK i would like to deploy office 2013 via GPO, i finally have been able to get the script to work however there is one more detail i need to get figured out.... How can i incorporate into the script so that it will only run once... my script is below
and does the following, it uninstalls office 2010 whether it be 32bit or 64bit then silently installs office 2013 as a startup GPO... how would the script look if i'd like to add so that it looks for a specific txt file that if its there it does nothing and
if it's not it runs install script and perhaps at end of install script maybe it creates that txt file... I need help on the best way to just "RUNONCE"
here is my script:
"C:\Program Files\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
"C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\Office Setup Controller\setup.exe" /uninstall ProPlus /config "\\****\Office13\Uni_Office_10\SilentUninstall.xml"
setlocal
REM ********************************************************************
REM Environment customization begins here. Modify variables below.
REM ********************************************************************
REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
set ProductName=Office15.PROPLUS
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer=\\****\Office13
REM Set ConfigFile to the configuration file to be used for deployment (required)
set ConfigFile=\\****\Office13\ProPlus.WW\config.xml
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\****\Office13\LogFiles
REM ********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM ********************************************************************
IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall%ProductName%
if NOT %errorlevel%==1 (goto End)
REM Check for 32 and 64 bit versions of Office 2010 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall%ProductName%
if %errorlevel%==1 (goto DeployOffice) else (goto End)
REM If 1 returned, the product was not found. Run setup here.
:DeployOffice
echo %date% %time% %ComputerName% "Has Run the install Process" >> %LogLocation%\HasRunInstall.txt
start /wait %DeployServer%\setup.exe /config %ConfigFile%
echo %date% %time% %computername% Setup ended with error code %errorlevel%. >> %LogLocation%\FinishedInstall.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal

The problem with Office 2010 and later is that it is not designed to be installed remotely or by a script. You need to create an install spec and set up some prerequisites fist. If you ten follow the instructions for using a GPO to deploy Office
you will not need to use a "RunOnce" key or anything else.
Note that eh RunOnce key take a command or batch and command and is deleted as soon as it is executed. The problem you have to solve is how to set the RunOnce key to begin with.
You really must use the information in the links posted for Office deployment. You cannot do an end run around this with any success. If you search for forum posts on this you will see that many have been exactly where you are. Don't wast
your time. Follow the instructions as posted in the Office forum and on the TechNet link. YOu will find it is actually quite easy and very flexible once you understand the steps.
\_(ツ)_/

Office 2010 deployment - Bypass/Skip if Office 2013 present

We have predominantly Office 2007 installed thought out environment and I now have a working Office 2010 app deployment package. Now I am finding that we have a few systems that already have Office 2013 and I'd like to bypass any system that already has
2013 installed. Currently my 2010 package is installing side by side with 2013 and has resulted in Office being corrupted. I have not been able to find a way to detect Office 2013 and bypass/skip installation. Please help. Thank you in advance.

Hi,
You could simply use a Collection query and exclude all devices from the Office 2013 collection that already has Office 2010 installed.. If you deploy it it devices and not users that is..
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

How do I activate Office 2013 that I have deployed using ODT and App-V onto a Remote Desktop Server?

I am setting up a demo Server 2012 R2 environment (1 DC server, 2 RDSH servers, 1 App-V server).
I have created an Office 2013 volume license App-V package using the latest Office Deployment Toolkit. I have deployed the App-V package to an RDS server and it all works fine. However, I am unable to activate Office 2013 using the MSDN Office 2013 retail
key because it tells me the product key is invalid for this version of Office. I've looked at the alternative of using the App-V Sequencer to create the Office 2013 package, but from what I've read this is not a Microsoft supported method.
Is there any way that I can activate Office 2013 (volume license on RDS) using the method I've outlined above, or is there any way of using the Office2013 download from MSDN such that it can be packaged by the ODT (or App-V Sequencer) for successful deployment
using App-V and activation using the retail Office 2013 product key on MSDN?

True, VL channel media can't be activated with MSDN Retail pkeys (that's what I was trying to get you to understand, I figured you would be attempting that, as so many people do :(
I've not attempted your scenario myself.
It sounds like you aren't following the supported scenarios as (poorly) described by MS;
The way I read their guide, for an RDS scenario, you must use a VL key [either MAK or KMS] (since a subscription product+key can't be used on RDS):
i.e.: <Product ID="ProPlusVolume">
http://support.microsoft.com/kb/2772509
http://support.microsoft.com/kb/2915745
http://technet.microsoft.com/library/dn481351.aspxhttp://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
So, that all means that for RDS, you can't use anything other than VL "product" (in
the form of an ODT-generated output) with a VL pkey. So, for your RDS demo setup, you need to use real product and real pkeys.
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!)

Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2. We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012. The deployment went as
expected. Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP. I am afraid to find out what time we are looking at for remote DP's.
The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3. We are using the same package source files. Previous to a successful deployment we were
seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment? Our previous deployment time for office was a little over an hour (not five hours). Any suggestions where to look to improve
the deployment time?
I am expected to deploy this in one week and have been working on these issues for weeks.

I see now that you are using a combination of scripts and ConfigMgr package/program.
The AppEnforce.log file is for use with the new ConfigMgr Application model.
Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
Office 2013.
This is how you do it
http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Deploying Office 2013 with Group Policy

I would like to deploy Office 2013 using group policy. I am new to group policy so am looking for some advice and guidance on the best way to deploy. I would like to deploy with no interaction with the user but yet display a message so that they
know not to open Office. I would also like to create a custom registry setting so that if I need to re-install, all I have to do is delete the registry setting. I have tried a group policy for installing with OCT settings (Basic, Suppress
Model checked, No Cancel checked, Completion Notice checked) and modifying the Config.xml (<Display Level="Basic" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />) but I can not get it to display
the installer screen so that users know it is installing. It does display the screen when running the setup.exe manually. I have a setting in the OCT that creates the registry setting and that is working correctly. My group policy is set to run the
below bat file at startup in the Computer Configuration.
setlocal
REM *********************************************************************
REM Environment customization begins here. Modify variables below.
REM *********************************************************************
REM Get ProductName from the Office product's core Setup.xml file, and then add "office15." as a prefix.
set ProductName=Office15.Standard
REM Set DeployServer to a network-accessible location containing the Office source files.
set DeployServer="\\xxxxxx\setup.exe"
REM Set LogLocation to a central directory to collect log files.
set LogLocation=\\xxxxx\Logfiles
REM *********************************************************************
REM Deployment code begins here. Do not modify anything below this line.
REM *********************************************************************
IF NOT "%ProgramFiles(x86)%"=="" (goto ARP64) else (goto ARP86)
REM Operating system is X64. Check for 32 bit Office in emulated Wow6432 uninstall key
:ARP64
reg query HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if NOT %errorlevel%==1 (goto End)
REM Check for 32 and 64 bit versions of Office 2013 in regular uninstall key.(Office 64bit would also appear here on a 64bit OS)
:ARP86
reg query HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%ProductName%
if %errorlevel%==1 (goto Office) else (goto End)
REM If 1 returned, the product was not found. Run setup here.
:Office
%DeployServer%
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt
REM If 0 or other was returned, the product was found or another error occurred. Do nothing.
:End
Endlocal
Any advice or guidance would be greatly appreciate on how to get a pop up message while software is installing or if there is a better way to deploy.

> but I can not get it to display the installer screen so that users know
> it is installing. It does display the screen when running the setup.exe
> manually. I have a setting in the OCT that creates the registry setting
> and that is working correctly. My group policy is set to run the
> below bat file at startup in the Computer Configuration.
Check http://gpsearch.azurewebsites.net/#2308 - if this is enabled, you
will not be able to show "anything" in startup scripts...
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Trouble with deploying Win 8.1 and Office 2013 to Surface Pro 2

Setup; Win2012R2, WDS 6.3.9600.16384, MDT 2013 (6.2.5019.0), Surface Pro 2 128GB, MS USB Ethernet adapter
Issue 1: the TFTP transfer of the PE image is Extremely slow. 10 Mbps. Have tried to adjust Maximum Block Size without any improvement.
Issue 2: When I try to deploy both Windows 8.1 and Office 2013 the TS fails. It will not (start) installing the Application - the log confirms that it starts the script, but ends up with ZTI Heartbeat forever.
If I install Windows first and after the OS installation connect to the MDT server and start a TS With just Office 2013 it works without problem.
The disturbing part here is that if I use the same TS With both OS and Office on a Hyper-V Virtual machine it works...
Have anyone seen this before?

Hi,
I test in my environment, and Windows would finish the index, the CPU usage keeps in 29%, which my RAM is 8G.
Can you tell us how you let the Windows Index run?
Alex Zhao
TechNet Community Support

Deploy custom templates in Office 2013

Hi All,
We have been using the backstage view of Office 2010 to deploy custom templates, as described in the TechNet article
http://technet.microsoft.com/en-us/library/cc178976(v=office.14).aspx
We recently upgraded to Office 2013 and have not been successful in getting our templates to show up in the backstage view. We have tried creating the spotlight registry keys under
the \Microsoft\Office\15.0\Common\Spotlight but this was also unsuccessful.
Has anyone been able to deploy custom templates using the 2007/10 spotlight approach outlined in that TechNet article?
Thanks
Dan

Thank you Max,
Can you please specify how the permissions should be set to allow Word 2013 to access SP 2013 via the XML file? Is it enough to simply be logged into SharePoint with Contribute rights to the library or is there more that needs to be done?
Hi Katie,
I believe Contribute permissions are enough for this case.
Have a look at the following solution, see if it works for your situation:
http://zasharepoint.blogspot.com/2014/04/sorry-we-couldnt-find-your-file-is-it.html
More hints to troubleshoot this issue:
Have you tested this issue on another machine?
Is proxy used?
Does the SharePoint environment has complex permission settings (e.g. the inheriting permissions are broken, or cross domain environment, etc.)?
Max Meng
TechNet Community Support

Office 2013 Deployment in a Multisite Environment

Similar Messages

Maybe you are looking for