Office 2013 Multilanguage Deployment

Hello,
I have to deploy Office 2013 to our French users, English
users and Italian users through SCCM 2012; they should have Office 2013 installed with same OS language.
I already know how to do it on SCCM 2012, but I'd like to ask for your opinion.
Solution 1
I could have one folder for each Office 2013 language/platform:
Office2013-FR-x86
Office2013-FR-x64
Office2013-EN-x86
Office2013-EN-x64
Office2013-IT-x86
Office2013-IT-x64
On SCCM 2012 I should create 6 Application Deployments.
Having six folders and six Applications will increase management, but client will download needed content only (used language).
Solution 2
I could have one folder for each Office 2013 platform:
Office2013-x86 - Contains x86 version of Office 2013 in French, English, Italian (Multilanguage)
Office2013-x64 - Contains x64 version of Office 2013 in French, English, Italian (Multilanguage)
On SCCM 2012 I should create 2 Application Deployments.
Having two folders and two Applications only will be helpful for management, but client will download unneeded content for installation (unused languages).
I hope to be clear.
So, what is your opinion ?
Thank you,
Luca
Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

Hello Peter,
thank you for your answer. Consider there is only one central support department who manages Application Deployments and SCCM in general. That said, I can imagine what you are referring to with "...depends on...if there is a local support department.":
each local support department can manage its Office 2013 App. Deployment, so it is useful to have them splitted (Solution 1); isn't it ? With "...depends on...same type of device type..." what are your referring to ? They are all Desktop
Computers with mixed OS: Windows 8, 7, XP.
Solution 1 could be useful if, for example, I need to install Office 2013 English version on Italian OS (Solution 2 is not a good choice: Office 2013 will be installed in the same OS language).
Like you, I prefer Solution 2 too, it will simplify management, helps to save disk space (applications repository); but I also need to consider: choosing it, SCCM Clients have to download much more data even if they don't need.
Bye,
Luca
Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights. Whenever you see a helpful reply, click on [Vote As Help] and click on [Mark As Answer] if a post answers your question.

Similar Messages

Patching Office 2013 multilanguage - updates to be applied

Hi,
I deployed Office 2013 Std English with a list of Language Packs (german, italian, spanish, ...). To make the deployment, I created an administrative share with the suite (english version) and added several folders extracted fron Language Pack iso (the iso
is named "Office Multilanguage Pack 2013 w Proofing Tools (All Languages)"). The deployment worked fine: now users can select English or other languages for the interface, the guide and the proofing tools.
Now, I have to update for my deployed Office 2013 suites. I configure WSUS to download updates for Office 2013, but my question is: I can download only the english version for updates, or I have to configure WSUS also to download updates for Office
in the languages I added to the suite?
Thanks in advance.
Roberto

Always include English in addition to any other languages that are required throughout your organization.
All updates are based on English language packs.
The recommended practice by Microsoft
is as below:
Plan for WSUS Update Languages
http://technet.microsoft.com/en-us/library/hh328568(v=ws.10).aspx
Choose a Type of WSUS Deployment
http://technet.microsoft.com/us-en/library/cc720448(v=ws.10).aspx
Using the WSUS 3.0 Configuration Wizard
http://technet.microsoft.com/us-en/library/cc720475(v=ws.10).aspx
Hope this helps.
Tony Chen
TechNet Community Support

Activating MS Office 2013 ProPlus via KMS running on the same server

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Patch management for Office 2013 on MDT

Hello,
on current MDT 2012, Office 2013 is added as an app. MSP was created for customization and placed in Update folder (did it a while ago)
I am preparing new MDT 2013. Deployed OS will be patched with latest updates. So Windows update will not take initially any time for applying patches after deployment from WSUS.
I would like to know best practices for Updating Office 2013 on Deployment Share.
Please provide a link or instructions: where to get latest O2013 Update Packages (at least security and critical) and how to place them properly in Update folder. Can it coexist with Customization.msp?
1. What is the right thing to manage this? No SCCM in place.
2. Does somebody includes Office 2013 in the image and then use GPO for customization?
Is it a valid scenario? I see at least 2 advantages: no additional time after deployment and full patches for the moment of image creation. Than it could be updated in the moment of image update.
Does it make sense? What are disadvantages of this approach?
thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Thanks to all!
Ty, I added a lot to my knowledgebase during bombing :) you with the questions since last week :) ... Thanks for the answers...
I purchased Johan's Fundamentals V4 (found it more applicable to my current needs).
A bit in pressure this week need to push 2 models deployment quickly and correctly as possible.
So don't have time to Deep Dive.
What I achieved Driver Group approach works find for tons of drivers. Tried just on model now...
Have to solve sudden issue with WinPE that was working fine and suddenly stopped working.
For O2013...
Just to make things fast I installed O2013 in reference image.
If I understand correctly I cannot use MSP file after the installation is made. I suppose to create it and add to Updates folder of the O2013 source.
So now my option is to work with GPO. I have a configured one for O2013 APPV deployment.
It works great.
Don't remember if I can manage by GPO applications appearance in the Office. (Example want to exclude Publisher and Access from being used on client PC).
Can somebody point where is the option in GPO for selecting individual apps within the Office.
In my MDT2012 I use O2013 deployment as App and use MSP.
For Appv Office I use apps selection from APPV manager. So not sure if it is doable from Office GPO.
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

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

Install Office 2013 in captured 'golden' image - activation?

Hi all
I created a build & Capture in mdt 2013.
Here I install office 2013 during deployment and all is well.
When i deploy the image the office package doesn't activate.. which is .. annoying...
I tried manually running ospp.vbs /act and this seems to work.
but should I really have to insert a step in my sccm TS to run the script?
Kindest regards, Martin

It doesn't matter if you activate Office before you capture the image. Sysprep will strip this out. If you are using a KMS server Office activation should then happen automatically a short period after the computer joins the network.
If not you need to see
1. are you using a MAK key? This will not work with your KMS server.
2. Have you actually configured KMS to activate Office?
http://technet.microsoft.com/en-us/library/dn385356(v=office.15).aspx
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

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

SCCM 2012: Office 2013 click to run deploy?

Hi,
We would like to run Office 2013 next to Office 2010. Therefore the click-to-run option (app-v is only possible for Office 2013 ProPlus) looks the way to go.
I found a nice guide a Office 2013 Plus “Click to run” Deploy in SCCM:
http://www.peters.com/Blogs/Lists/Posts/Post.aspx?ID=90 However (posted it also on the site), can I use the /admin to generate the configuration.xml instead and use it within SCCM 2012 deploy?
J
Jan Hoedt

No. Click-to-run does not use the traditional Office setup methodology and thus does not have the same configuration options. More info at
http://technet.microsoft.com/en-us/library/jj219420(v=office.15).aspx
Jason | http://blog.configmgrftw.com | @jasonsandys

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!)

App-V 5.0: Adding Visio 2013 and Project 2013 to a previously deployed virtual Office 2013

Good morning.
I can successfully deploy Office 2013 via PowerShell and App-V v5.0 without difficulty. I've read the document at
http://support.microsoft.com/kb/2915745/en-us and followed all instructions successfully.
My question is this: If Office 2013 without Visio 2013 or Project 2013 is virtually deployed, how can those components be added later?
For instance, we may have 100 users that acquire a virtualized Office 2013 without Project or Visio. We then may have 25 users that require a virtualized Office and Visio without Project and, perhaps, another 15 that require Office and Project without
Visio.
Currently, when I attempt a second virtual deployment of one of these components, it removes Office 2013 making it inaccessible.
How can Project and/or Visio be deployed to an already existing virtually deployed Office 2013?
Thanks very much.
John
IAmStrings

As a part of MDOP, you'll also have access to UE-V which will provide a mechanism of moving user preferences across the same applications from difference packages.
It will require planning, configuration and deployment, but will ensure you don't face the same issue in the future.
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 other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V

Deploying Custom Office 2013, Uninstalling Office 2010

We've just recently moved to SCCM for application and OS deployment, so we're setting up applications to be deployed through SCCM for the very first time. I've read a few guides to deploying Office 2013, and the majority of them follow the same procedure:
Customize Office 2013 with OCT
Create an application in SCCM by selecting proplusww.msi
Edit the deployment type and replace proplusww.msi with setup.exe
Some guides reference the .msp in the setup.exe command, some don't. e.g. "setup.exe /adminfile custom.msp"
So, a few questions:
Why should I use setup.exe vs proplusww.msi? I understood that the application model gives us more control, better autodetection, and less manual configuration. i.e. use MSI for applications
If I should use setup.exe, do I really need to reference .msp? e.g. setup.exe /adminfile custom.msp I thought that when you customize the installer, and place the msp in the \updates folder, running the setup.exe still utilizes the msp file.
Some guides say I should also used an xml file for help with uninstalling Office 2013. e.g. An xml file with Display Level, SuppressModal, and AcceptEula set, then using the command "setup.exe /uninstall proplusr /config .\proplusr.ww\unisntall.xml".
What instances would I need the xml, and which instances would I not?
Finally, I would possibly like to install Office 2013 during OSD. Would that change any recommendations on how I create the Office 2013 SCCM application?
I'd appreciate any help/advice anyone can give. I was not able to find any info directly from Microsoft on how best to deploy Office with SCCM. Nor was I able to find any info on using proplusww.msi vs setup.exe for deployment. Thanks.

If you place the .MSP file in the Updates folder, the Setup.exe program will automatically process it without the need to specify in the command line. The .XML and OCT .MSP are two different means of customizing the installation. I typically
use the OCT to create the .MSP and drop it in the Updates folder, then just call setup.exe with no switches to perform the silent install.
Make sure you set the SETUP_REBOOT property to Never in the OCT, otherwise the install may perform an unexpected reboot that could potentially cause issues with ConfigMgr (especially if it's during imaging).
Thanks for the info. What about proplusww.msi vs using setup.exe? I still haven't been able to find any documentation on using one vs the other when deploying through SCCM (as to why you should use one over the other). Almost every SCCM application deployment
guide I come across always wants you to use the MSI, sometimes going to great lengths to find one, just to avoid using an exe. So, why does almost every SCCM Office deployment guide tell me to use setup.exe? Also, is it just me, or is there really not official
best practice form Microsoft when deploying Office through SCCM?

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

Office 2013 pro plus deployment

Hi,
I am trying to deploy office 2013 to all in my organization through a group policy, the version that I have is 15.0.4569.1506. I have used oct to customize the setup and activate the product.
All works fine but after the product is installed there are 2 GB of updates that are needed. I am trying to find the best way to push out the updates along with the initial installation.
I have tried downloading a few updates and placing them in the updates folder in the package but this does not install the updates and it is not possible to download more than 100 updates and place them in the updates folder.
Is there a latest version available with all the updates included that can be deployed straight away?

Hi,
Microsoft have used some rather confusing product marketing terms, which makes it hard to get clear, and also to be clear, when it comes to this release of Office :(
Office 2013ProfessionalPlus - installation uses the classic setup.exe + MSI engine. Can be updated via WSUS.
Office365ProPlus - installation uses the new ODT, and results in C2R virtualized "installation". Can't be updated via WSUS.
So, if you're using the ODT, then you're not using Office2013ProfessionalPlus..
Reference for the Product element:
http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx#BKMK_ProductElement
Reference including Retail Product elements:
http://support.microsoft.com/kb/2842297/en-au
NB: the update process will probably be cantankerous even after you get it working ;)
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 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 Multilanguage Deployment

Similar Messages

Maybe you are looking for