Office 2013 - OSD - Specify different config xml

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

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

Similar Messages

  • How to specify the webLogic server startup script to use different config.xml  file ??

    Hi,
    I have 2 weblogic startup scripts (startWebLogic.sh and
    startWebLogic_recovery.sh) for the same domain.
    startWebLogic.sh uses config.xml file.
    I would like to use config_recovery.xml as the configuration file for startWebLogic_recovery.sh
    How would I do this ?
    I am using WebLogic Server 6.1 on SunOS 5.8 / HP-UX 11.0.
    Appreciate any help.
    Regards
    Gunaseelan Venkateswaran

    I guess you're using Weblogic 6.1 with WLCS 3.5. I think you're supposed to work with one config.xml for the same domain, and not have a different config.xml.
    To start up different applications or EJBs, use the "target" property to control which applications to start up for the particular instance.
    YY

  • Upgrade Office 2010 Standard to Office 2010 Pro Plus using Config.xml

    Hello,
    I am upgrading Office 2010 Standard to Office 2010 Pro Plus. But after using the below config  pro plus did get installed but both versions of Office 2010 ( Stand and Plus ) show up on the machines. I want only Office Pro plus to appear.
    The second issue is that even after uninstalling  Office 2010 Standard from the Control panel the Office shows activation of both ( Going to --File ---Help)
    How can I edit this config.xml to remove office 2010 Standard first and then upgrade to Office 2010 Pro Plus?
    <Configuration Product="ProPlus">
     <Display Level="None" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" />
     <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> -->
     <!-- <USERNAME Value="Customer" /> -->
     <PIDKEY Value="aaaa-aaa-aaa-aaa" />
     <COMPANYNAME Value="XYZ Co." />
     <Setting Id="AUTO_ACTIVATE" Value="1" />
     <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->
     <!-- <LIS CACHEACTION="CacheOnly" /> -->
     <!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> -->
     <!-- <DistributionPoint Location="\\server\share\Office" /> -->
     <!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
     <!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> -->
     <!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i
    \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> -->
    </Configuration>

    Hi,
    Here is not a Config.xml solution, but we can use it as a workaround, basically automate the uninstallation of Office 2010, reboot the computer and then deploy Office 2010. You may find the following article useful if you need more info on that.
    http://blogs.technet.com/b/odsupport/archive/2011/04/06/how-to-perform-an-uninstall-upgrade-to-office-2010.aspx
    Regards,
    George Zhao
    TechNet Community Support

  • Stream 7 - MS Office 2013 install to different drive when setting up Office 365 free subscription

    Ok - set up my free Office 365 subscription, and got Office 2013 downloaded - to my C: drive (the internal eMMC).  I want those programs installed on my microsd (drive D.  I got no option to do this when it downloaded.
    Is it possible to re-download Office 2013, and re-install it to my D: drive?

    As default, Stream 7 only have one partition installed (drive C: only).
    MS also have some answers here:
    http://answers.microsoft.com/en-us/office/forum/office_2013_release-office_install/i-want-office-201...

  • 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 with Service Pack 1 installation error about "search path"

    I have an automated installation technique that has worked fine with Office 2010 Pro Plus (32-bit), incorporating the latest Service Pack into the network administrative installation point (under \updates), adding 10 foreign languages to the network administrative
    installation point, creating a custom .msp with the OCT (that goes into \updates too), editing the config.xml files, and then running setup.exe from that network administrative installation point. This works on 32-bit Windows XP clients and on 32- and 64-bit
    Windows 7 clients.
    For Office 2013 Pro Plus, I have built the network administrative installation point exactly the same way (original DVD files + languages + SP1 updates + config.xml updates), but the installation is failing with every type of client, all with
    the same error message. The network administrative installation point is readable by the normal installing account, but I even get the same error when I login as me and initiate setup.exe manually, and I have all rights to this point.
    Here's the critical point from a log file:
    2014/03/11 11:53:49:691::[2372] DistributionPoint parsed.  The distribution point is now set to: \\archive.ads.college.edu\archive\KBOXalt\Office2013
    2014/03/11 11:53:49:691::[2372] COMPANYNAME specified in config.xml.
    2014/03/11 11:53:49:691::[2372] USERNAME specified in config.xml.
    2014/03/11 11:53:49:800::[2372] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
    2014/03/11 11:53:49:910::[2372] Searching for default versions of resource files under the folder [\\archive.ads.college.edu\archive\KBOXalt\Office2013].
    2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
    ErrorCode: 0(0x0). Failed final attempt to load a setupexe resource file.
    2014/03/11 11:53:50:019::[2372] Error: GetDirectories: search path \\archive.ads.college.edu\archive\KBOXalt\Office2013 does not exist
    Type: 34::InvalidDirectory.
    2014/03/11 11:53:50:019::[2372] WER element [SuppressModal] is set to value [true]
    2014/03/11 11:53:50:019::[2372] WER element [P4] is set to value [InvalidDirectory]
    2014/03/11 11:53:50:019::[2372] Catalyst execution finished: 03/11/2014 11:53:50.  Return code: 30034.  Exception caught: InvalidDirectory.
    2014/03/11 11:53:50:019::[2372] PERF: TickCount=894821 Name=RunSetup Description=End function
    I cannot find any references to this exact error anywhere on the Internet. Can anyone tell me what this means, and how I fix it?

    As automated, the utility that runs setup.exe maps a drive letter to
    \\archive.ads.college.edu\archive\KBOXalt using a kboxmap AD account, which has read access to the whole \KBOXalt tree. I used that same kboxmap AD account manually to simulate what the utility does, and hit the same problem. But here's what's
    odd: right next to that
    \\archive.ads.college.edu\archive\KBOXalt\Office2013 directory is an
    \\archive.ads.college.edu\archive\KBOXalt\Office2010 directory, both created the same way, and the Office 2010 installation has always worked perfectly using the kboxmap AD account. I don't understand why Office 2013 is only working for an account with
    read/write access, where Office 2010 worked fine for an account with only read access. Especially when the Office 2013 resource kit documentation clearly states that the account running the installation should only have read access, nothing more. (All this
    KBOX stuff comes from the fact that our deployment environment is a Dell KACE KBOX 1000. However, that plays no part in the problem: ignoring the KBOX 1000, I can manually recreate the problem every time.)

  • Problems creating a Office 2013 combined installation share, bug?

    I have tried to combine Office 2013 x86 (English), with Norwegian Language Pack, and the full Proofing Tools except IMEs. However, I ran in to some problems which might be bugs?
    I create a network share and copy the Office 2013 x86 files to it, the Norwegian LIP, then the Proofing Tools files (without overwrite).
    Setup.exe works fine for the initial Office 2013 installation, however it will not work for the Proofing Tools installation.
    I run the setups like this:
    Office: setup.exe /adminfile admin.msp /config proplus.ww\config.xml
    This works just fine, Office installs without any problem.
    Proofing: setup.exe /config proofkit.ww\config.xml
    This however did not work. The setup crashes with the error:
    Setup halts at the beginning of the installation bar, then breakes out with a an unexpected error, installation failed, rolling back (roughly translated)
    My current workaround is to have one folder on the share for "Office 2013" and one for the "Proofing Tools".
    The "problem" I get then, is that I need to keep both "updates" folder up to date and identical in order to get a fully updated Office installation.
    I have also tried to copy the setup.exe/dll files + catalog from both the LIP iso, and Proofing tools ISO, but non of them gives me a "one installation source to rule them all". They all brake in some way.
    Is it somehow possible to get a fully working "combined" Office installation source on a network share?
    This is the config.xml for the Office 2013 installation, I've skipped a few lines because I have only added 2 lines to the original config.xml
    <Configuration Product="ProPlus">
    <AddLanguage Id="nb-no" ShellTransform="yes"/>
    <AddLanguage Id="en-us" />
    <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> -->
    <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Professional Plus Setup(*).txt" /> -->
    </Configuration>
    This is the config.xml for the Proofing Tools:
    <Configuration Product="ProofKit">
    <Display Level="Basic" CompletionNotice="No" SuppressModal="Yes" AcceptEula="Yes" /> -->
    <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Proofing Tools Kit Setup(*).txt" /> -->
    <!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->
    <OptionState Id="IMEMain_1028" State="Absent" Children="force"/>
    <OptionState Id="IMEMain_1041" State="Absent" Children="force"/>
    <OptionState Id="IMEMain_1042" State="Absent" Children="force"/>
    <OptionState Id="IMEMain_2052" State="Absent" Children="force"/>
    <OptionState Id="ProofingTools_1025" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1026" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1027" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1028" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1029" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1030" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1031" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1032" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1033" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1035" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1036" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1037" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1038" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1040" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1041" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1042" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1043" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1044" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1045" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1046" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1048" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1049" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1050" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1051" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1053" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1054" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1055" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1056" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1058" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1060" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1061" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1062" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1063" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1069" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1081" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1087" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1094" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1095" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1097" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1099" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1102" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_1110" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_2052" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_2068" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_2070" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_2074" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_3076" State="Local" Children="force"/>
    <OptionState Id="ProofingTools_3082" State="Local" Children="force"/>
    <!-- <Setting Id="Setup_Reboot" Value="IfNeeded" /> -->
    </Configuration>
    In my admin.msp file, I have basically just added:
    Organization name
    License (KMS)
    I accept the tems in the License Agreement
    Display level: Basic
    Suppress modal
    No cancel
    Full feature installation, except Microsoft SkyDrive Pro and Microsoft InfoPath
    Anyone know how to get this to work? It worked just fine with Office 2010, how can I get it to work with Office 2013?
    Regards,
    Øistein

    Here is a copy of the SetupError log from when the Proofing Tools installation is run:
    2013/12/22 23:12:53:377::[2084] PERF: TickCount=935312265 Name=OBootStrapper::Run Description=Begin function
    2013/12/22 23:12:53:377::[2084] Terminal Server detected
    2013/12/22 23:12:53:377::[2084] Operating System version: 6.2.9200 . Platform ID: 2
    2013/12/22 23:12:53:377::[2084] Running 32-bit setup on a 64-bit operating system.
    2013/12/22 23:12:53:377::[2084] Command line: "\\server\share\Microsoft\Office 2013 x86 - Copy\setup.exe" /config "\\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\config.xml"
    2013/12/22 23:12:53:377::[2084] Parsing command line.
    2013/12/22 23:12:53:377::[2084] Config XML file specified: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\config.xml
    2013/12/22 23:12:53:377::[2084] Parsing config.xml at: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\config.xml
    2013/12/22 23:12:53:392::[2084] Preferred product specified in config.xml to be: PROOFKIT
    2013/12/22 23:12:53:392::[2084] Display level basic specified in config.xml.
    2013/12/22 23:12:53:392::[2084] Suppression of modal dialogs specified in config.xml.
    2013/12/22 23:12:53:392::[2084] Hide completion notice specified in config.xml.
    2013/12/22 23:12:53:392::[2084] Auto accept license specified in config.xml.
    2013/12/22 23:12:53:877::[2084] Verify file signature in "\\server\share\Microsoft\Office 2013 x86 - Copy\setup.exe"
    2013/12/22 23:12:53:908::[2084] \\server\share\Microsoft\Office 2013 x86 - Copy\setup.exe is trusted.
    2013/12/22 23:12:53:908::[2084] Verify file signature in "\\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\OSETUP.DLL"
    2013/12/22 23:12:54:049::[2084] \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\OSETUP.DLL is trusted.
    2013/12/22 23:12:54:174::[2084] Using setup controller dll at [\\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\OSETUP.DLL].
    2013/12/22 23:12:54:174::[2084] PERF: TickCount=935313062 Name=OBootStrapper::Run Description=Calling RunSetup
    2013/12/22 23:12:54:174::[2084] PERF: TickCount=935313062 Name=RunSetup Description=Begin function
    2013/12/22 23:12:54:174::[2084] WER element [P2] is set to value [OSETUP.DLL]
    2013/12/22 23:12:54:174::[2084] WER element [P3] is set to value [15.0.4481.1001]
    2013/12/22 23:12:54:174::[2084] Terminal Server detected
    2013/12/22 23:12:54:174::[2084] Catalyst execution began: 12/22/2013 23:12:54.
    2013/12/22 23:12:54:174::[2084] Parsing config.xml at: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\config.xml
    2013/12/22 23:12:54:174::[2084] Preferred product specified in config.xml to be: PROOFKIT
    2013/12/22 23:12:54:174::[2084] Display level basic specified in config.xml.
    2013/12/22 23:12:54:174::[2084] Suppression of modal dialogs specified in config.xml.
    2013/12/22 23:12:54:174::[2084] Hide completion notice specified in config.xml.
    2013/12/22 23:12:54:174::[2084] Auto accept license specified in config.xml.
    2013/12/22 23:12:54:174::[2084] Setupexe Resiliency Mode is set to [PerformIfApplicable]; thus Resiliency is [disabled] for the [InstallExecutionMode]
    2013/12/22 23:12:54:174::[2084] Searching for updated versions of resource files under the 'updates' folder [\\server\share\Microsoft\Office 2013 x86 - Copy\updates].
    2013/12/22 23:12:54:174::[2084] Found [0] resource files under the update folder.
    2013/12/22 23:12:54:174::[2084] Searching for default versions of resource files under the folder [\\server\share\Microsoft\Office 2013 x86 - Copy].
    2013/12/22 23:12:54:189::[2084] Found [2] resource files under the default folder.
    2013/12/22 23:12:54:189::[2084] Running in [InstallExecutionMode]. Run from TEMP folder at [C:\Users\user\AppData\Local\Temp\Setup00000260].
    2013/12/22 23:12:54:205::[2084] Loaded resource file [C:\Users\user\AppData\Local\Temp\Setup00000260\OSETUPUI.DLL] (CultureTag=nb-NO).
    2013/12/22 23:12:54:205::[2084] WER element [SuppressModal] is set to value [false]
    2013/12/22 23:12:54:205::[2084] WER element [P1] is set to value [15.0.4420.1017]
    2013/12/22 23:12:54:205::[2084] Loaded Dll : \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\OSETUP.DLL.
    2013/12/22 23:12:54:205::[2084] Catalyst version is : 15.0.4481.1001
    2013/12/22 23:12:54:205::[2084] JobExecutionMode is InstallExecutionMode.
    2013/12/22 23:12:54:252::[2084] Check if Office is supported on Windows 6.2.9200
    2013/12/22 23:12:54:502::[3524] Product: PROOFKIT
    2013/12/22 23:12:54:502::[3524] AddOnGroup Culture: en-us
    2013/12/22 23:12:54:502::[3524] AddOnId: PROOFMUI.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnGroup Culture: fr-fr
    2013/12/22 23:12:54:502::[3524] AddOnId: PROOFMUI.FR-FR
    2013/12/22 23:12:54:502::[3524] Product: PROPLUS
    2013/12/22 23:12:54:502::[3524] AddOnGroup Culture: en-us
    2013/12/22 23:12:54:502::[3524] AddOnId: WORD.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: OSMUX.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: OSM.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: PROOFING.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: ONENOTE.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: OFFICE64.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: GROOVE.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: OUTLOOK.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: DCF.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: PUBLISHER.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: POWERPOINT.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: EXCEL.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: OFFICE.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: LYNC.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: INFOPATH.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnId: ACCESS.EN-US
    2013/12/22 23:12:54:502::[3524] AddOnGroup Culture: nb-no
    2013/12/22 23:12:54:502::[3524] AddOnId: WORD.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: POWERPOINT.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: OUTLOOK.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: OSMUX.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: OSM.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: PROOFING.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: GROOVE.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: ONENOTE.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: EXCEL.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: ACCESS.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: INFOPATH.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: DCF.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: PUBLISHER.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: OFFICE64.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: OFFICE.NB-NO
    2013/12/22 23:12:54:502::[3524] AddOnId: LYNC.NB-NO
    2013/12/22 23:12:55:292::[2084] No upgradable applications found
    2013/12/22 23:12:55:292::[2084] Not parsing product config.xml file: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\config.xml because one has already been parsed.
    2013/12/22 23:12:55:292::[2084] Found AddOn Culture: CultureTag=[en-us], NativeCltureName=[English].
    2013/12/22 23:12:55:292::[2084] Found AddOn Culture: CultureTag=[fr-fr], NativeCltureName=[français].
    2013/12/22 23:12:55:292::[2084] Product Deployment Mode: PerMachineManaged
    2013/12/22 23:12:55:292::[2084] Target Deployment Account Security Identifier: S-1-5-18
    2013/12/22 23:12:55:292::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofmui.en-us\ProofMUI.xml
    2013/12/22 23:12:55:292::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\ProofKitWW.xml
    2013/12/22 23:12:55:292::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.en\Proof.xml
    2013/12/22 23:12:55:307::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.fr\Proof.xml
    2013/12/22 23:12:55:307::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.es\Proof.xml
    2013/12/22 23:12:55:323::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ar\Proof.xml
    2013/12/22 23:12:55:323::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.zh-tw\Proof.xml
    2013/12/22 23:12:55:339::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ja\Proof.xml
    2013/12/22 23:12:55:339::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ko\Proof.xml
    2013/12/22 23:12:55:339::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.th\Proof.xml
    2013/12/22 23:12:55:354::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.zh-cn\Proof.xml
    2013/12/22 23:12:55:354::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.pt-br\Proof.xml
    2013/12/22 23:12:55:370::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.de\Proof.xml
    2013/12/22 23:12:55:370::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.it\Proof.xml
    2013/12/22 23:12:55:370::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.nl\Proof.xml
    2013/12/22 23:12:55:386::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ca\Proof.xml
    2013/12/22 23:12:55:386::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.eu\Proof.xml
    2013/12/22 23:12:55:401::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.gl\Proof.xml
    2013/12/22 23:12:55:403::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.sv\Proof.xml
    2013/12/22 23:12:55:403::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.fi\Proof.xml
    2013/12/22 23:12:55:418::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.cs\Proof.xml
    2013/12/22 23:12:55:418::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.da\Proof.xml
    2013/12/22 23:12:55:418::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.he\Proof.xml
    2013/12/22 23:12:55:434::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.hi\Proof.xml
    2013/12/22 23:12:55:434::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.hu\Proof.xml
    2013/12/22 23:12:55:434::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.mr\Proof.xml
    2013/12/22 23:12:55:451::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.nb\Proof.xml
    2013/12/22 23:12:55:451::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.pa\Proof.xml
    2013/12/22 23:12:55:451::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.pl\Proof.xml
    2013/12/22 23:12:55:466::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ru\Proof.xml
    2013/12/22 23:12:55:466::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.te\Proof.xml
    2013/12/22 23:12:55:482::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.tr\Proof.xml
    2013/12/22 23:12:55:482::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.el\Proof.xml
    2013/12/22 23:12:55:482::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.sk\Proof.xml
    2013/12/22 23:12:55:498::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.uk\Proof.xml
    2013/12/22 23:12:55:498::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.nn\Proof.xml
    2013/12/22 23:12:55:513::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.pt\Proof.xml
    2013/12/22 23:12:55:513::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.bg\Proof.xml
    2013/12/22 23:12:55:513::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ro\Proof.xml
    2013/12/22 23:12:55:529::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.hr\Proof.xml
    2013/12/22 23:12:55:529::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.sl\Proof.xml
    2013/12/22 23:12:55:529::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.et\Proof.xml
    2013/12/22 23:12:55:545::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.lv\Proof.xml
    2013/12/22 23:12:55:545::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.lt\Proof.xml
    2013/12/22 23:12:55:560::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.gu\Proof.xml
    2013/12/22 23:12:55:560::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ta\Proof.xml
    2013/12/22 23:12:55:560::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.kn\Proof.xml
    2013/12/22 23:12:55:577::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.sr\Proof.xml
    2013/12/22 23:12:55:577::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ur\Proof.xml
    2013/12/22 23:12:55:577::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.kk\Proof.xml
    2013/12/22 23:12:55:592::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.sr-cyrl-cs\Proof.xml
    2013/12/22 23:12:55:592::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.id\Proof.xml
    2013/12/22 23:12:55:608::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ms\Proof.xml
    2013/12/22 23:12:55:608::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.ms-bn\Proof.xml
    2013/12/22 23:12:55:608::[2084] Loading package metadata: \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\Proof.vi\Proof.xml
    2013/12/22 23:12:55:624::[2084] Searching for patches for the current chained install in: \\server\share\Microsoft\Office 2013 x86 - Copy\updates
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-ar-sa.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-bg-bg.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-ca-es.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-cs-cz.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-da-dk.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-de-de.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-el-gr.msp
    2013/12/22 23:12:57:882::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-en-us.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-es-es.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-et-ee.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-eu-es.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-fi-fi.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-fr-fr.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-gl-es.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-he-il.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-hi-in.msp
    2013/12/22 23:12:57:897::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-hr-hr.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-hu-hu.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-it-it.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-ja-jp.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-ko-kr.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-lt-lt.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-lv-lv.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-nb-no.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-nl-nl.msp
    2013/12/22 23:12:57:913::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-nn-no.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-pl-pl.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-pt-br.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-pt-pt.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-ro-ro.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-ru-ru.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-sk-sk.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-sl-si.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-sr-cyrl-cs.msp
    2013/12/22 23:12:57:929::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-sr-latn-cs.msp
    2013/12/22 23:12:57:944::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-sv-se.msp
    2013/12/22 23:12:57:944::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-th-th.msp
    2013/12/22 23:12:57:944::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-tr-tr.msp
    2013/12/22 23:12:57:944::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-uk-ua.msp
    2013/12/22 23:12:57:944::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-zh-cn.msp
    2013/12/22 23:12:57:944::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\proof-zh-tw.msp
    2013/12/22 23:12:58:038::[2084] Applicable patch: \\server\share\Microsoft\Office 2013 x86 - Copy\updates\setupexe-x-none.msp
    2013/12/22 23:12:58:492::[2084] Error: Default ProductName not found for 00cc
    2013/12/22 23:12:58:492::[2084] No branding information found, using catalystProductId for ARP DisplayName: PROOFKIT
    2013/12/22 23:12:58:492::[2084] No Visio 15 product is detected
    2013/12/22 23:12:58:492::[2084] No Project 15 product is detected
    2013/12/22 23:12:58:570::[2084] Reading value of unintialized setting!
    2013/12/22 23:12:58:601::[2084] BRANDING: Parsing Branding Data...
    2013/12/22 23:12:58:617::[2128] Error: Unable to set a system restore point
    2013/12/22 23:12:58:617::[2128] Kicking off chained install...
    2013/12/22 23:12:58:617::[2128] Terminal Server detected
    2013/12/22 23:12:58:617::[2128] PERF: TickCount=935317500 Name=Job::DoCacheWork Description=Begin function
    2013/12/22 23:13:00:645::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:00:645::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:00:645::[2128] Running Source Engine process detected
    2013/12/22 23:13:00:645::[2128] Running version: 15.0.4454.1000
    2013/12/22 23:13:00:645::[2128] OSE is running
    2013/12/22 23:13:00:645::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:02:348::[2128] PERF: TickCount=935321234 Name=Job::DoCacheWork Description=End function
    2013/12/22 23:13:02:348::[2128] Final Option Tree:
    2013/12/22 23:13:02:348::[2128] AlwaysInstalled:local
    2013/12/22 23:13:02:348::[2128] OSpp:local
    2013/12/22 23:13:02:348::[2128] OSpp_Core:local
    2013/12/22 23:13:02:348::[2128] Gimme_OnDemandData:local
    2013/12/22 23:13:02:348::[2128] ProductFiles:local
    2013/12/22 23:13:02:348::[2128] SHAREDFiles:local
    2013/12/22 23:13:02:348::[2128] ProofingTools:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1025:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1025:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1025:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1025:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1026:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1026:local
    2013/12/22 23:13:02:348::[2128] OCR_1026:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1026:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1026:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1027:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1027:local
    2013/12/22 23:13:02:348::[2128] OCR_1027:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1027:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1027:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1028:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1028:local
    2013/12/22 23:13:02:348::[2128] OCR_1028:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1028:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1028:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1029:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1029:local
    2013/12/22 23:13:02:348::[2128] OCR_1029:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1029:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1029:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1030:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1030:local
    2013/12/22 23:13:02:348::[2128] OCR_1030:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1030:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1030:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1031:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1031:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1031:local
    2013/12/22 23:13:02:348::[2128] OCR_1031:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1031:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1031:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1031:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1032:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1032:local
    2013/12/22 23:13:02:348::[2128] OCR_1032:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1032:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1032:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1033:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1033:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1033:local
    2013/12/22 23:13:02:348::[2128] OCR_1033:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1033:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1033:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1035:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1035:local
    2013/12/22 23:13:02:348::[2128] OCR_1035:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1035:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1035:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1036:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1036:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1036:local
    2013/12/22 23:13:02:348::[2128] OCR_1036:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1036:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1036:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1036:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1037:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1037:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1037:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1037:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1037:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1038:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1038:local
    2013/12/22 23:13:02:348::[2128] OCR_1038:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1038:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1038:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1040:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1040:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1040:local
    2013/12/22 23:13:02:348::[2128] OCR_1040:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1040:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1040:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1040:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1041:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1041:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1041:local
    2013/12/22 23:13:02:348::[2128] OCR_1041:local
    2013/12/22 23:13:02:348::[2128] RRLoc_1041:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1041:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1042:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1042:local
    2013/12/22 23:13:02:348::[2128] OCR_1042:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1042:local
    2013/12/22 23:13:02:348::[2128] HangulHanjaConversion:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1042:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1043:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1043:local
    2013/12/22 23:13:02:348::[2128] OCR_1043:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1043:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1043:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1044:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1044:local
    2013/12/22 23:13:02:348::[2128] OCR_1044:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1044:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1044:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1045:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1045:local
    2013/12/22 23:13:02:348::[2128] OCR_1045:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1045:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1045:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1046:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1046:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1046:local
    2013/12/22 23:13:02:348::[2128] OCR_1046:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1046:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1046:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1048:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1048:local
    2013/12/22 23:13:02:348::[2128] OCR_1048:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1048:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1048:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1049:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1049:local
    2013/12/22 23:13:02:348::[2128] OCR_1049:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1049:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1049:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1050:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1050:local
    2013/12/22 23:13:02:348::[2128] OCR_1050:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1050:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1050:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1051:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1051:local
    2013/12/22 23:13:02:348::[2128] OCR_1051:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1051:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1051:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1053:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_1053:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1053:local
    2013/12/22 23:13:02:348::[2128] OCR_1053:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1053:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1053:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1054:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1054:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_1054:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1055:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1055:local
    2013/12/22 23:13:02:348::[2128] OCR_1055:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1055:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1055:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1056:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1056:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1057:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1057:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1058:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1058:local
    2013/12/22 23:13:02:348::[2128] OCR_1058:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1058:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1058:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1060:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1060:local
    2013/12/22 23:13:02:348::[2128] OCR_1060:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1060:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1060:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1061:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1061:local
    2013/12/22 23:13:02:348::[2128] OCR_1061:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1061:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1061:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1062:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1062:local
    2013/12/22 23:13:02:348::[2128] OCR_1062:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1062:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1062:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1063:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1063:local
    2013/12/22 23:13:02:348::[2128] OCR_1063:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1063:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1063:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1066:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1066:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1069:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1069:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1069:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1081:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1081:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_1081:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1086:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1086:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1087:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1087:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1087:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1094:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1094:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1095:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1095:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1097:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1097:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1098:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1098:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1099:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1099:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1102:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1102:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_1110:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_1110:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_1110:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_2052:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_2052:local
    2013/12/22 23:13:02:348::[2128] OCR_2052:local
    2013/12/22 23:13:02:348::[2128] RRLoc_2052:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_2052:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_2052:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_2068:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_2068:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_2068:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_2070:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_2070:local
    2013/12/22 23:13:02:348::[2128] OCR_2070:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_2070:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_2070:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_2074:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_2074:local
    2013/12/22 23:13:02:348::[2128] OCR_2074:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_2074:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_2074:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_2110:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_2110:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_3082:local
    2013/12/22 23:13:02:348::[2128] FindAllWordFormsFiles_3082:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_3082:local
    2013/12/22 23:13:02:348::[2128] OCR_3082:local
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_3082:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_3082:local
    2013/12/22 23:13:02:348::[2128] TranslationFiles_3082:local
    2013/12/22 23:13:02:348::[2128] ProofingTools_3098:local
    2013/12/22 23:13:02:348::[2128] HyphenationFiles_3098:local
    2013/12/22 23:13:02:348::[2128] OCR_3098:absent
    2013/12/22 23:13:02:348::[2128] SpellingAndGrammarFiles_3098:local
    2013/12/22 23:13:02:348::[2128] ThesaurusFiles_3098:local
    2013/12/22 23:13:02:348::[2128] "Installed" sku component file \\server\share\Microsoft\Office 2013 x86 - Copy\proofkit.ww\setup.xml to C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\PROOFKIT\setup.xml.
    2013/12/22 23:13:02:348::[2128] "Installed" sku component file \\server\share\Microsoft\Office 2013 x86 - Copy\proofmui.en-us\setup.xml to C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\ProofMUI.en-us\setup.xml.
    2013/12/22 23:13:02:348::[2128] Determining ARP entry registry values.
    2013/12/22 23:13:02:364::[2128] PERF: TickCount=935321250 Name=Verify MSI local install source Description=Begin function
    2013/12/22 23:13:02:364::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:364::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:380::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:02:395::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:395::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:411::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:02:411::[2128] LIS: wait for package "{90150000-00C2-0409-0000-0000000FF1CE}" to complete caching
    2013/12/22 23:13:02:427::[2128] LIS: package "{90150000-00C2-0409-0000-0000000FF1CE}" caching completed
    2013/12/22 23:13:02:427::[2128] PERF: TickCount=935321312 Name=Completed verify local install source Description=End function
    2013/12/22 23:13:02:473::[2128] Executing chained package: ProofMUI.en-us
    2013/12/22 23:13:02:473::[2128] Reading value of unintialized setting!
    2013/12/22 23:13:02:473::[2128] 12/22/2013 23:13:02 Installing chained package: ProofMUI.en-us
    2013/12/22 23:13:02:473::[2128] PERF: TickCount=935321359 Name=Verify MSI local install source Description=Begin function
    2013/12/22 23:13:02:473::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:473::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:505::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:02:505::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:505::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:02:536::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:02:536::[2128] LIS: wait for package "{90150000-00C2-0409-0000-0000000FF1CE}" to complete caching
    2013/12/22 23:13:02:536::[2128] LIS: package "{90150000-00C2-0409-0000-0000000FF1CE}" caching completed
    2013/12/22 23:13:02:536::[2128] PERF: TickCount=935321421 Name=Completed verify local install source Description=End function
    2013/12/22 23:13:02:536::[2128] Catalyst Package Install..
    2013/12/22 23:13:02:536::[2128] Package: ProofMUI.en-us
    2013/12/22 23:13:02:536::[2128] File: C:\MSOCache\All Users\{90150000-00C2-0409-0000-0000000FF1CE}-C\ProofMUI.msi
    2013/12/22 23:13:02:536::[2128] Command Line: ADDLOCAL=PSetupControllerIntl_1033,Gimme_OnDemandData,PSetupController,SetupXmlFiles,ProofKitFiles,SetupControllerFiles,MsoInstalledPackagesScopedIntl_1033 ARPENTRY_UNINSTALLSTRING="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\setup.exe"" /uninstall PROOFKIT /dll OSETUP.DLL" ARPENTRY_DISPLAYICON="C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\OSETUP.DLL,1" SETUPEXEINSTALLUICULTURE="nb-NO" ARPENTRY_SHELLUITRANSFORMLANGUAGE="nb-NO" ACCEPTEDEULA="1" REMOVEPREVIOUS="" BRANDING_XML="C:\Users\user\AppData\Local\Temp\Setup00000260\BRANDING.XML" ARPENTRY_MODIFYPATH="""C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\setup.exe"" /modify PROOFKIT /dll OSETUP.DLL" REMOVESAMEVERSION="" COMPANYNAME="Sveio kommune" ARPENTRY_PRODUCTCODES="[~]{90150000-00C2-0409-0000-0000000FF1CE}[~]{90150000-001F-043E-0000-0000000FF1CE}[~]{90150000-001F-0421-0000-0000000FF1CE}[~]{90150000-001F-043F-0000-0000000FF1CE}[~]{90150000-001F-0420-0000-0000000FF1CE}[~]{90150000-001F-044B-0000-0000000FF1CE}[~]{90150000-001F-0449-0000-0000000FF1CE}[~]{90150000-001F-0447-0000-0000000FF1CE}[~]{90150000-001F-0427-0000-0000000FF1CE}[~]{90150000-001F-0426-0000-0000000FF1CE}[~]{90150000-001F-0425-0000-0000000FF1CE}[~]{90150000-001F-0424-0000-0000000FF1CE}[~]{90150000-001F-041A-0000-0000000FF1CE}[~]{90150000-001F-0418-0000-0000000FF1CE}[~]{90150000-001F-0402-0000-0000000FF1CE}[~]{90150000-001F-0422-0000-0000000FF1CE}[~]{90150000-001F-041B-0000-0000000FF1CE}[~]{90150000-001F-0408-0000-0000000FF1CE}[~]{90150000-001F-041F-0000-0000000FF1CE}[~]{90150000-001F-044A-0000-0000000FF1CE}[~]{90150000-001F-0419-0000-0000000FF1CE}[~]{90150000-001F-0415-0000-0000000FF1CE}[~]{90150000-001F-0446-0000-0000000FF1CE}[~]{90150000-001F-0414-0000-0000000FF1CE}[~]{90150000-001F-044E-0000-0000000FF1CE}[~]{90150000-001F-040E-0000-0000000FF1CE}[~]{90150000-001F-0439-0000-0000000FF1CE}[~]{90150000-001F-040D-0000-0000000FF1CE}[~]{90150000-001F-0406-0000-0000000FF1CE}[~]{90150000-001F-0405-0000-0000000FF1CE}[~]{90150000-001F-040B-0000-0000000FF1CE}[~]{90150000-001F-041D-0000-0000000FF1CE}[~]{90150000-001F-0456-0000-0000000FF1CE}[~]{90150000-001F-042D-0000-0000000FF1CE}[~]{90150000-001F-0403-0000-0000000FF1CE}[~]{90150000-001F-0413-0000-0000000FF1CE}[~]{90150000-001F-0410-0000-0000000FF1CE}[~]{90150000-001F-0407-0000-0000000FF1CE}[~]{90150000-001F-0416-0000-0000000FF1CE}[~]{90150000-001F-041E-0000-0000000FF1CE}[~]{90150000-001F-042A-0000-0000000FF1CE}[~]{90150000-001F-0409-0000-0000000FF1CE}[~]{90150000-001F-040C-0000-0000000FF1CE}[~]{90150000-001F-0401-0000-0000000FF1CE}[~]{90150000-001F-0404-0000-0000000FF1CE}[~]{90150000-001F-0411-0000-0000000FF1CE}[~]{90150000-001F-0412-0000-0000000FF1CE}[~]{90150000-001F-0C1A-0000-0000000FF1CE}[~]{90150000-001F-0C0A-0000-0000000FF1CE}[~]{90150000-001F-083E-0000-0000000FF1CE}[~]{90150000-001F-081A-0000-0000000FF1CE}[~]{90150000-001F-0816-0000-0000000FF1CE}[~]{90150000-001F-0814-0000-0000000FF1CE}[~]{90150000-001F-0804-0000-0000000FF1CE}[~]{90150000-00CC-0000-0000-0000000FF1CE}[~]" INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" SLD_TRIALTYPE="0" ACIDS="86E17AEA-A932-42C4-8651-95DE6CB37A08" USERNAME="" SLD_PKU="0" SLD_PID="00216-60000-00000-AA472" SLD_DPID="#xF804000004000000380032003500300033002D00300032003100360036002D003000300030002D003000300030003000300030002D00300030002D0031003000340034002D0039003200300030002E0030003000300030002D0033003500360032003000310033000000000000000000000000000000000000000000000000000000000000000000380036006500310037006100650061002D0061003900330032002D0034003200630034002D0038003600350031002D00390035006400650036006300620033003700610030003800000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500054004B004E006F006E006500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007608000000000C660646ED6028DB0800F963228D4DF4D7E66DCE6300666E5DC7BBCA3F62F099E5D16D5D54B8B14A0D4F7E634B904BD5706748E3B01FB3C58876B96CD63C0AF6DD9263D20EF6D7FAA5335800310038002D00330033003300320034000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000520065007400610069006C0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006C00740046007200650065000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" SLD_SUPPORTSBYPASS="0" SLD_OEMPIDKEY="0" SLD_LICENSETYPE="0" SLD_ACID="86E17AEA-A932-42C4-8651-95DE6CB37A08" USERINITIALS="" NOUSERNAME="1" ARPENTRY_SPPSKUID="[~]86E17AEA-A932-42C4-8651-95DE6CB37A08[~]" ARPENTRY_URLINFOABOUT="" ARPENTRY_CONTACT="" ARPENTRY_NOREMOVE="#0" ARPENTRY_NOMODIFY="#0" ARPENTRY_NOELEVATEONMODIFY="#0" ARPENTRY_NOREPAIR="#1" ARPENTRY_URLUPDATEINFO="" ARPENTRY_HELPLINK="" ARPENTRY_INSTALLLOCATION="C:\Program Files (x86)\Microsoft Office\" ARPENTRY_HELPTELEPHONE="" ARPENTRY_DISPLAYNAME="Microsoft Office Proofing Tools Kit Compilation 2013" ARPENTRY_DISPLAYVERSION="15.0.4481.1005" ARPENTRY_VERSIONMAJOR="#15" ARPENTRY_VERSIONMINOR="#0" ARPENTRY_CACHELOCATION="C:\MSOCache\All Users" ARPENTRY_SKUCOMPONENTS="[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\PROOFKIT\setup.xml[~]C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE15\Office Setup Controller\ProofMUI.en-us\setup.xml[~]" ARPENTRY_PACKAGEREFS="[~]ProofMUI.en-us[~]Proof.ar-sa[~]Proof.et-ee[~]Proof.pt-pt[~]Proof.vi-vn[~]Proof.eu-es[~]Proof.en-us[~]Proof.es-es[~]Proof.fr-fr[~]Proof.cs-cz[~]Proof.it-it[~]Proof.ko-kr[~]Proof.zh-tw[~]Proof.ja-jp[~]Proof.th-th[~]Proof.ms-my[~]Proof.zh-cn[~]Proof.pt-br[~]Proof.id-id[~]Proof.gu-in[~]Proof.de-de[~]Proof.sv-se[~]Proof.nl-nl[~]Proof.ca-es[~]Proof.pl-pl[~]Proof.gl-es[~]Proof.el-gr[~]Proof.fi-fi[~]Proof.da-dk[~]Proof.he-il[~]Proof.hi-in[~]Proof.hu-hu[~]Proof.ms-bn[~]Proof.mr-in[~]Proof.nn-no[~]Proof.nb-no[~]Proof.pa-in[~]Proof.ru-ru[~]Proof.ur-pk[~]Proof.ta-in[~]Proof.te-in[~]Proof.tr-tr[~]Proof.uk-ua[~]Proof.sk-sk[~]Proof.bg-bg[~]Proof.kk-kz[~]Proof.ro-ro[~]Proof.lv-lv[~]Proof.hr-hr[~]Proof.sl-si[~]Proof.lt-lt[~]Proof.sr-cyrl-cs[~]Proof.kn-in[~]Proof.sr-latn-cs[~]ProofKitWW[~]" SETUPEXE_DOARPWRITE="1" REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=1044 SETUPINTLDLLDIRECTORY="C:\Users\user\AppData\Local\Temp\Setup00000260\" ARPSYSTEMCOMPONENT=1 ALLUSERS="1"
    2013/12/22 23:13:02:536::[2128] PERF: TickCount=935321421 Name=MsiPackage::Install Description=Calling OMsiInstaller::InstallProduct for package file "C:\MSOCache\All Users\{90150000-00C2-0409-0000-0000000FF1CE}-C\ProofMUI.msi"
    2013/12/22 23:13:03:583::[2128] PERF: TickCount=935322468 Name=MsiPackage::Install Description=Returned from OMsiInstaller::InstallProduct
    2013/12/22 23:13:03:583::[2128] Successfully installed package: ProofMUI.en-us path:C:\MSOCache\All Users\{90150000-00C2-0409-0000-0000000FF1CE}-C\ProofMUI.msi
    2013/12/22 23:13:03:598::[2128] Executing chained package: Proof.vi-vn
    2013/12/22 23:13:03:598::[2128] Reading value of unintialized setting!
    2013/12/22 23:13:03:598::[2128] 12/22/2013 23:13:03 Installing chained package: Proof.vi-vn
    2013/12/22 23:13:03:598::[2128] PERF: TickCount=935322484 Name=Verify MSI local install source Description=Begin function
    2013/12/22 23:13:03:598::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:03:598::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:03:645::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:03:661::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:03:661::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:03:708::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:03:724::[2128] OSE is detected as a registered service. Service binary is reported at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:03:724::[2128] OSE service binary is detected at location: C:\Program Files (x86)\Common Files\Microsoft Shared\Source Engine\OSE.EXE
    2013/12/22 23:13:03:786::[2128] Running OSE version 15.0.4454.1000
    2013/12/22 23:13:03:802::[2128] LIS: wait for package "{90150000-00CC-0000-0000-0000000FF1CE}" to complete caching
    2013/12/22 23:13:34:771::[2128] LIS failed to cache download "{90150000-00CC-0000-0000-0000000FF1CE}-C" resource "setup.dll". Cache Error 0x80070017
    2013/12/22 23:13:34:771::[2128] SupressModal flag is set. Skip showing Source Resolution Dialog
    2013/12/22 23:13:34:771::[2128] Source Resolution aborted
    2013/12/22 23:13:43:576::[2128] LIS failed to cache download "{90150000-00CC-0000-0000-0000000FF1CE}-C" resource "setup.exe". Cache Error 0x80070017
    2013/12/22 23:13:43:576::[2128] SupressModal flag is set. Skip showing Source Resolution Dialog
    2013/12/22 23:13:43:576::[2128] Source Resolution aborted
    2013/12/22 23:13:47:466::[2128] LIS failed to cache download "{90150000-00CC-0000-0000-0000000FF1CE}-C" resource "setup.dll". Cache Error 0x80070017
    2013/12/22 23:13:47:466::[2128] SupressModal flag is set. Skip showing Source Resolution Dialog
    2013/12/22 23:13:47:466::[2128] Source Resolution aborted
    2013/12/22 23:13:47:466::[2128] WER element [SuppressModal] is set to value [true]
    2013/12/22 23:13:47:466::[2128] WER element [P4] is set to value [0x80070017]
    2013/12/22 23:13:47:466::[2128] WER element [P7] is set to value [0x80070017]
    2013/12/22 23:13:47:466::[2128] WER element [P6] is set to value [LIS: Failed to cache download "%s" resource "%s".]
    2013/12/22 23:13:47:466::[2128] WER element [P6] is converted to [FB4645EA]
    2013/12/22 23:13:47:466::[2128] Error: LIS: Failed to cache download "{90150000-00CC-0000-0000-0000000FF1CE}-C" resource "setup.dll". HResult: 0x80070017.
    2013/12/22 23:13:47:466::[2128] Log level changed from: Standard to: Verbose
    2013/12/22 23:13:47:466::[2128] Rolling back chain
    2013/12/22 23:13:47:466::[2128] Error attaching to OSE, error 0x00000000
    2013/12/22 23:13:47:466::[2128] Stopping running ose
    2013/12/22 23:13:48:158::[2128] LIS: start uncaching for download "{90150000-00C2-0409-0000-0000000FF1CE}-C"
    2013/12/22 23:13:49:264::[2128] LIS: finished uncaching for download "{90150000-00C2-0409-0000-0000000FF1CE}-C"
    2013/12/22 23:13:49:264::[2128] LIS: start uncaching for download "{90150000-00CC-0000-0000-0000000FF1CE}-C"
    2013/12/22 23:13:49:420::[2128] LIS: finished uncaching for download "{90150000-00CC-0000-0000-0000000FF1CE}-C"
    2013/12/22 23:13:49:420::[2128] Error attaching to OSE, error 0x00000000
    2013/12/22 23:13:49:420::[2128] Stopping running ose
    2013/12/22 23:13:49:998::[2128] 12/22/2013 23:13:49 Rolling back MSI transaction.
    2013/12/22 23:13:49:998::[2128] MSI(INITIALIZE): '<NULL>'
    2013/12/22 23:13:49:998::[2128] MSI(COMMONDATA): '1: 2 2: 0 '
    2013/12/22 23:13:49:998::[2128] MSI(COMMONDATA): '1: 2 2: 0 '
    2013/12/22 23:13:49:998::[2128] MSI(COMMONDATA): '1: 0 2: 1033 3: 65001 '
    2013/12/22 23:13:49:998::[2128] MSI(COMMONDATA): '1: 1 2: Microsoft Office ProofMUI (English) 2013 '
    2013/12/22 23:13:50:045::[2128] MSI(COMMONDATA): '1: 2 2: 1 '
    2013/12/22 23:13:50:045::[2128] MSI(COMMONDATA): '1: 2 2: 1 '
    2013/12/22 23:13:50:061::[2128] MSI(TERMINATE): '<NULL>'
    2013/12/22 23:13:50:061::[2128] 12/22/2013 23:13:49 MSI transaction rolled back.
    2013/12/22 23:13:50:061::[2128] Unable to cancel a system restore point.
    2013/12/22 23:13:50:061::[2084] Not showing completion dialog because it was not requested.
    2013/12/22 23:13:50:061::[2084] Reboot requested if needed.
    2013/12/22 23:13:50:061::[2084] No reboot is needed.
    2013/12/22 23:13:50:061::[2084] Catalyst execution finished: 12/22/2013 23:13:50. Return code: -2147024873.
    2013/12/22 23:13:50:061::[2084] PERF: TickCount=935368953 Name=RunSetup Description=End function
    Hopefully it could help someone to detect and solve the problem.

  • Virtual Application: Activation Office 2013

    Hello All,
    We have created virtual office application as directed in Office Deployment method. In Config.xml we gave "ProPlusVolume" we got out final .appv file
    We need to deploy this virtual application to all our clients. We are having a tough time in getting this done. 
    How do we activate this virtual application?
    Some blogs say MAK and KMS cannot be used for Virtual application, it is supported only for Non-Virtual application
    is this right? or using KMS we could achieve?
    How activation for Office 2013 applications can be achieved using VLSC?
     Any help would be greatly appreciated
    Thanks!

    Hello,
    If you are using KMS / AD-based activation I would guess it would detect it automatically.
    If using MAK - see the option to use ospp.vbs
    http://technet.microsoft.com/en-us/library/dn385359(v=office.15).aspx
    I haven't tried the above options, but it would be the most obvious chocies.
    Nicke Källén | The Knack| Twitter:
    @Znackattack

  • How to install Office 365 Pro Plus Ms office 2013 Offline through MDT Task Sequence

    Hi 
    How can i deploy the Office 365 pro Plus Ms Office 2013 (that come with Office 365 E3 License) offline to Client Machines through MDT Task Sequence?
    Shailendra Dev

    There is a wealth of information on Office 365 deployments at:
    http://technet.microsoft.com/en-us/library/gg715562(v=office.15).aspx
    Overview:
    Download the office deployment tool
    configure your config.xml file
    download the bits locally to your server.
    create a package for MDT.
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Critical WebLogicServer BEA-000362 Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException

    Friends,
    Getting below error when i restart the server.
    <Dec 31, 2014 5:33:58 AM EST> <Warning> <Management> <BEA-141274> <Production mode has specified at the command line via the weblogic.ProductionModeEnabled system property. This system property overrides the development mode setting contained in config.xml. However, the console and WLST show the attribute values and defaults that correspond to the development mode specified in config.xml.>
    <Dec 31, 2014 5:34:07 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: java.lang.AssertionError: java.lang.reflect.InvocationTargetException>
    <Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Dec 31, 2014 5:34:07 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Dec 31, 2014 5:34:07 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    I have changed the jar files path in build.properties file as its required to import new jars as part of Documentum server upgradation. But getting above errors.. Do i have to update Config.xml file or any other file.. Please suggest.

    You've got a problem with a corrupted config.xml file.
    Since you did not make any changes you can copy the config.xml.booted file over the corrupted config.xml.
    The other option is to walk though the config.xml file and look for the problem...

  • How to stop WL 7.0 to modify config.xml file

    As said, weblogic has two modes, PRODUCTION and DEVELOPMENT, if set to PRODUCTION
    mode, weblogic startup will not deploy any application and you should use console
    or deployer tool to deploy them manually. But, if I start it in PRODUCTION mode,
    the first it does not deployt any application and startup very quickly, but, if
    I manually deploy any application, weblogic server will also modify config.xml
    and my next startup will deploy all the applications since they are specified
    in config.xml, and the startup time will be much longer. How could I stop weblogic
    server from doing this? I want production mode but I want to keep my original
    config.xml untouched.
    Thanks

    To change this behavior:
    In Skype go to "Tools" - "Options" - "IM Settings" -  uncheck "Automatically accept incoming files" OR under "When I receive a file...." select "choose a folder to save the file in every time.

  • Office 2013 Setup Logging Template %hostname% Config.xml

    Hello,
    we want to deploy Office 2013 through SCCM with a Log-File which should be stored on a Server. To identify from which Computer the log file is, it should be named like the hostname.
    I have specifed the followig in the config.xml
    <Logging Type="verbose" Path="\\logserver\log\" Template="%hostname%.txt" />
    instead of translating the hostname there is only a %hostname%.txt on the logserver.
    Anyone an idea to solve this?
    Thanks.

    Glad to see you have your problem resolved. And thanks for sharing the workaround here, this should be helpful to other users who encounter the same problem.
    Thanks,
    Ethan Hua CHN
    TechNet Community Support

  • The configuration file did not contain well formed AppV configuration XML - When using Office 2013 ODT package

    All,
    I'm experiencing an issue where when using the Office 2013 package pulled down from ODT, that if I try to change the locations of either InfoPath Filler 2013 or Publisher 2013 from the default of Microsoft Office 2013 then I receive the message "The
    configuration file did not contain well formed AppV configuration XML. Please check the management server event log for more information". If I check Applications and Services\Microsoft\AppV\Server-Management\Admin the error displayed there is "An
    error was encountered parsing dynamic configuration file '0'. However I am able to change the shortcut location for all other applications except the above 2. I've tried redownloading the files using the ODT and also changing the version number (so far I've
    tried both the 15.0.4631.1002 and 15.0.4659.1001 with the same result).
    As all I'm interested in so far is having a package which contains Visio and Project I've tried following the article to exclude all the other Office elements:
    http://technet.microsoft.com/library/jj219426(v=office.15).aspx#BKMK_ExcludeAppElement. However the package looks to be the same and when I load it into the management console all the options and elements to Office 2013 are available like they were before
    when I hadn't set the exclude tags so I'm not sure whether the ExcludeApp parameters actually work correctly.
    This then brings me onto the 3rd issue I've experienced. I have a group for the Visio users and I've set custom security for them to have Visio delivered to them but not Project and then a seperate group for just Project users who will have Project delivered
    to them but not have Visio. When testing this sometimes seems to work but other times it seems to trip out and a user just in the Project or Visio group will get all of the Office 2013 applications and under the default location of Microsoft Office 2013. When
    trying to spot correlation with this it appears random and can happen to any user on any device. We have sequenced a few applications ourselves where different parts are needed for different users and we have successfully managed this using different security
    groups for different applications, just as I'm trying here with Office 2013.
    Has anyone else experienced the issue with the "did not contain well formed XML" as at the start of the post and how were you able to resolve this? Also has anyone any advice on how to troubleshoot the issue with the security seeming to trip out
    and publish all applications within a package to a user regardless of whether they are in the correct group or not?
    The management / publishing servers are 5.0.1224.0 which is SP1 HF4 and the clients are on SP2 HF5.
    Thanks

    Nicke,
    The config files are UTF-8. I did find the same article as yourself, however when searching for the value ‘TakeoverExtensionPointsFrom46=’ within either of the configuration.xml files that text isn’t found.
    No sinister reason not to share the file used, just it’s the same structure as referenced in the article:
    http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx. The only difference being that I’m using ProPlusVolume and I’ve set a version number (which is the October
    2014 update). I’ve even looked to follow the above example as closely as possible in just using the ExcludeApp ID of Access and InfoPath, just to try and prove the process. However I still get the usual full package. The version of the Click-to-Run setup.exe
    I’m using is 15.0.4623.1001, so later than the version specified at the end of that article which is 15.0.4619.1000. Where can I expect to see the elements excluded? Will it be when loading the package into the management console or would it just not appear
    on the machine when delivered?
    <Configuration>
      <Add SourcePath="C:\OfficeDeploymentToolV2" Version="15.0.4659.1001" OfficeClientEdition="32">
        <Product ID="ProPlusVolume">
          <Language ID="en-us" />
    <ExcludeApp ID="Access" />
    <ExcludeApp ID="InfoPath" />
        </Product>
      </Add>
    </Configuration>
    3). We’ve not used global publishing in our environment yet so I will try that. I’ve set both GlobalRefreshEnabled and GlobalRefreshOnLogon to True and when using the command Get-AppvPublishingServer on the client I’m testing with I can see this is pulled
    through correctly. I’ve also added the client name to the AD group used to grant access to the package and it is published. However nothing is pulling through onto the Client, so are there any steps I’ve missed or misinterpreted when looking to set this up?
    I guess the global publishing is there to keep in with licensing for Office being per device? On a slight aside, as Windows licensing is being changed to allow per user licensing
    http://www.zdnet.com/microsoft-to-make-per-user-windows-licensing-available-to-enterprise-customers-7000035401/ does anyone know if there are any plans to allow for Office / Project / Visio licenses to go per user as well? We’re a volume license customer
    rather than subscription based so I think a lot of the options to selectively deploy Visio and Project are excluded for us.
    Dan,
    Ok that explains why the security could be tripping out then and leading to this result. As above I’ll try with global publishing and see how I get on.
     From what I’ve read / watched  I think only one Office 2013 package can be published to a machine, so we would be unable to have a separate package for Visio and a separate package for Project and then attempt to deliver
    them both together. If a user wanted both Project and Visio then I guess we’d need to have a combined Project and Visio package to cover than scenario, but then 2 more separate Project and Visio packages for those who would only want either Project and Visio
    (I think).
    The scenario we’re looking at is to see whether we are able to deliver Project and / or Visio to different users through an AppV package and this will then cover users on XenApp or on fat clients. Only a small proportion of our
    users will need access to Project and / or Visio so therefore we’d only have a small amount of Project and Visio licenses.
    However from what I’ve tested up to this point and from what I’ve picked up from Forum posts / watched on TechEd sessions is that as publishing is Global and is unable to use different security groups for different elements of the
    suite, then using Office through AppV is only suitable if you will be delivering the whole suite (including Project and Visio) to all of your users. So in a scenario where you’d only want certain elements to be delivered to a handful of users then you’d need
    to keep with traditional ESD methods to have this installed onto fat clients and steer clear of XenApp. If wanting to install to XenApp then a lockdown tool like AppSense or AppLocker would also need to be brought into the equation.
    Is my understanding above correct or have I missed some options / methods?
    If the full Office package is always delivered but a company only has Office licenses and no Project and Visio licenses for all its users, how do they stop Project and Visio being delivered and being available? Or again if you have
    this use case is the AppV method one which will be unsuitable?
    Thanks

  • APP-V Office 2013 configuration.xml

    Hi all, 
    I'm trying to roll out Office 2013 with APP-V, whenever I change the config.xml to accept the EULA it still pops up with the EULA.
    The documentation for APP-V differs from the normal ODT config.xml, what's the difference and am I missing out on something? 
    See the document from Microsoft on the configuration.xml within app-v: 
    https://technet.microsoft.com/en-us/library/jj219426.aspx
    The XML file states to accept the EULA. The output in there is a configuration.xml like this: 
    <Configuration>
      <Add SourcePath="C:\office2013" OfficeClientEdition="32" >
        <Product ID="O365ProPlusRetail">
          <Language ID="nl-nl" />
    <Language ID="en-us" />
        </Product>
    <Product ID="ProjectProRetail">
          <Language ID="nl-nl" />
    <Language ID="en-us" />
        </Product>
     <Product ID="VisioProRetail" >
          <Language ID="nl-nl" />
    <Language ID="en-us" />
        </Product>
      </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Property Name="SharedComputerLicensing" Value="1" />
    </Configuration>
    Kind regards, 
    Jacob van Rooijen

    You can use two registry keys to disable it, push them using a GPO:
    HKCU\Software\Policies\Microsoft\Office\15.0\Registration
    Reg_DWORD = "AcceptAllEulas"= 1
    HKCU\software\policies\microsoft\office\15.0\firstrun
    Reg_DWORD = "bootedrtm" = 1
    See this post

  • Specify Office 2013 kms host trough group policy settings

    Hello.
    Can someone please help me get the right registry key for Office 2013. I want to specify kms host for my clients in domain - trough group policy. Dont want to use dns or config.xml to specify the host.
    For Windows i use this key, activation works greate.
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform\KeyManagementServiceName (REG_SZ)
    Have found the key for Office 2010 but cant use this for 2013
    HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName (REG_SZ).
    I have searched the web but cant find the key.
    I realy need some help here.
    Best regards
    Nils S.

    Have found the key for Office 2010 but cant use this for 2013
    HKLM\Software\Microsoft\OfficeSoftwareProtectionPlatform\KeyManagementServiceName (REG_SZ).
    I have searched the web but cant find the key.
    Hi,
    according to the documentation, it is the same registry key ?
    http://technet.microsoft.com/en-us/library/ee624350(v=office.15).aspx#section1
    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!)

Maybe you are looking for