Background

One of the goals of Office Click-to-Run is to continue to innovate and improve the product with each new update release.  This month is no different.

More Information

With the July 2014 update of Office 2013 for Office 365 the following improvements have been made:

1. Smaller Update Download Package:  Based on feedback from our customers, we have made improvements to the size of the update package that has to be downloaded to each machine being patched.  We now use binary delta compression, so that the amount of data downloaded across the network is reduced by up to 70%.  For example, if you have installed the June 2014 build (version 15.0.4623.1002) and now apply the July 2014 build, the total amount of data downloaded to the computer will be less than 120MB compared to over 310 MB with the traditional update method.
   Note: This holds true only if you apply updates each month.  If you skip months, then the update package size will be larger.
   
   
2. User-mode Streaming:  When installing Office 2013 for Office 365 from a network location, the requirement has been that the local computer accounts need “read” permissions to that network location.  This requirement is documented here.  With the July 2014 update, this is no longer a requirement.

Background

The June 2014 release (build 15.0.4623.1003 and later versions) of Office Click-to-Run from Office 365 allows you to automate both a quick and online repair of Office 2013.

Note - if using an Office build lower than 15.0.4569.1007 you will need to use integratedoffice.exe to perform a Quick Repair.  Further information on using integratedoffice.exe can be found here, Automating Quick Repairs in Office 365 ProPlus.


More Information

OfficeClicktoRun.exe is the executable that will allow you to automate a repair in Office 2013.  This executable will reside in one of the following locations based on the version of the Operating System:

64-bit OS:
C:\Program Files\Microsoft Office 15\ClientX64\

32-bit OS:
C:\Program Files\Microsoft Office 15\ClientX86

Here is the list of variables that can be used with OfficeClickToRun.exe:

For example, to do a silent Online Repair, run the following command from an elevated command prompt:

"C:\Program Files\Microsoft Office 15\ClientX64\OfficeClickToRun.exe" RepairType=FullRepair DisplayLevel=False

Related Information

For more information on the build versions of Office 2013 Click-to-Run, please see the following KB article
Microsoft Office 2013 Click-to-Run virtualization

Shortly after the release of the July Public Update, we received notification of a potential issue affecting a subset of Office 365 ProPlus users. In some cases, users running Office may not be able to launch Office products after the July 2014 updates are installed.

We have since corrected the issue and will be releasing an updated build 15.0.4631.1004 scheduled to go live by Thursday July 24th. Once the update is available, you can click on “Update Now” from the backstage to get the latest fix.

If you still have issues, then please reboot your computer and try “Update Now.” If you still have issues launching Office applications, as a last resort, please run the Fix It located at http://support.microsoft.com/kb/2739501 to uninstall and reinstall the latest bits.

Note: This issue doesn’t affect Volume License customers.

A few weeks ago the following update containing a great improvement to the Ospp.vbs script was released:

2883036  August 12, 2014 update for Office 2013 KMS activation component

So, the next time you are troubleshooting a KMS activation issue and run the Ospp.vbs script, please note the addition of two items to the output:

• A ‘notice’ advising you that a KB article is available for the error code generated by the script
• A URL to the section of article 2870357 that is bookmarked specifically for the error code

These items can be seen in the following figure:

In the above example, the URL takes you to the details targeting the 0xC004F038 error:

Prior to this update, you would have to manually search for content related to the 0xC004F038 error and then navigate your way through all the hits on this error to look for your solution. After this update is installed you only need to copy the URL from the Ospp.vbs output, paste it into your browser and then follow the directions provided in the article (for that error).

There are three options for upgrading to Office 2013:

•In-place upgrade - The earlier version of Office, such as Office 2010, is still installed on computers and we install Office 2013 on top of it.

•Uninstall upgrade - The earlier version of Office, such as Office 2010, is first uninstalled before we install Office 2013.

•New operating system upgrade - The computers get a new version of the operating system, such as Windows 8.1, and a copy of Office 2013.

We will be discussing the uninstall upgrade process in this blog as that is the situation most environments will be in and is the recommended way of moving from Office 2010 to Office 2013.  

First, we are going to remove Office 2010 from the user machines. We will automate the removal of Office 2010 by using either uninstall command line, the Office 2010 removal Fix It or Offscrub10.vbs. We want to remove the previous version first, then install the new version of Office 2013 for a couple of reasons. If you are going from Office 2010 MSI to Office 2013 MSI, and we simply use the "remove previous versions" feature of Office 2013 to remove Office 2010, we will still be left with Office 2010 and Office 2013 on the machine. The reason for this is SharePoint Designer is not part of the Office 2013 Pro Plus suite but rather a standalone install. Office 2013 will remove all previous versions of apps it will be installing - Word, Excel, etc. However, because there isn't a SharePoint Designer app in the Office 2013 Pro Plus suite, it will not remove the 2010 version of it and thus you will be left with 2010 and 2013 on the machine still. That is another reason we recommend uninstalling Office 2010 completely first, then installing Office 2013 cleanly on the machines. If we go from Office 2010 MSI to Office 2013 365, Office 365 will not remove the previous version and you will have multiple versions of Office on your system which is not recommended.

Here are the three methods of uninstalling Office 2010:

Using the command line to uninstall 2010:

If you are going to use the command line to remove office, it will look similar to the following example:

\\server\share\office2010\setup.exe /uninstall ProPlus /config \\server\share\office2010\proplus.ww\config.xml

If you choose to remove Office 2010 with the command line uninstall option, keep in mind that the uninstallation could fail if the health of the product is poor. IE… if the source cache directory is corrupt, or if cached patches are broken. If you are removing Office 2010 and are wanting to have the uninstallation be silent, and you want to prevent the reboot, you will need to edit the config.xml that contains those options and have it accessible on a share to call via the uninstall command line.

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="SETUP_REBOOT" Value="Never" />

Using the Office 2010 removal “Fix It” tool to uninstall Office 2010:

Obtain the Office removal “Fix It” tool here

Using Offscrub10.vbs to uninstall Office 2010:

Utilizing Offscrub is the best method of removing a previous version of Office. It will call setup.exe and MSIExec to remove the bits. It is best equipped to deal with machine or software corruption and completely removes Office app shortcuts for the previous version. We recommend using Offscrub in almost every situation of moving from
Office 2010 to Office 2013. 
 How to obtain Offscrub
 
Once you have decided what method you are going to use to remove Office 2010, we need to automate the removal of Office 2010, and then the installation of Office 2013.

Automation options:

Here are two example batch files for Volume License media and Click-to-Run that we can use to uninstall 2010, then install either of the two versions of Office 2013 Pro Plus. These examples are using Offscrub as the method of removal for Office 2010. These batch file can be pushed out with a software distribution tool like SCCM, or used as a startup script in Group Policy.
http://technet.microsoft.com/en-us/library/ff602181.aspx

Installing Office 2013 Click-to-Run:

First we need to download the Office 2013 Click-to-Run source media. We will use the Office Deployment Tool (ODT) to download a local copy of the Click-to-Run Source. To use the ODT, follow the steps outlined here:

http://blogs.technet.com/b/odsupport/archive/2014/07/11/using-the-office-deployment-tool.aspx

=====================================================
 setlocal

REM *********************************************************************

REM Environment customization begins here. Modify variables below.

REM *********************************************************************
 
REM Set DeployServer to a network-accessible location containing the Office source files.

set DeployServer=\\server\Share\

REM Set ConfigFile to the configuration file to be used for deployment (required)

set ConfigFile=\\server\share\configuration.xml
 
REM *********************************************************************

REM Deployment code begins here. Only modify Offscrub location below this line.

REM *********************************************************************

:DeployOffice

call cscript \\server\share\Offscrub10.vbs ProPlus /bypass 1 /q /s /NoCancel

start /wait %DeployServer%\setup.exe /configure %ConfigFile%

:End

Endlocal
 =====================================================
 
Installing Office 2013 Volume License:

For Office 2013 Volume License you will get your media from the Volume License Service Center. One thing to note is if you are using a KMS host for your Office 2013 activation, you will need to add the Office 2013 KMS host pack to your KMS server and activate it separately even if you have one set up for 2010 already.

=====================================================
setlocal

REM *********************************************************************

REM Environment customization begins here. Modify variables below.

REM *********************************************************************

REM Set DeployServer to a network-accessible location containing the Office source files.

set DeployServer=\\server\Office2013SourceFiles

REM Set ConfigFile to the configuration file to be used for deployment (required)

set ConfigFile=\\server\Office2013SourceFiles\ProPlus.WW\config.xml

REM *********************************************************************

REM Deployment code begins here. Do not modify anything below this line except for the Offscrub path

REM *********************************************************************

:DeployOffice

call cscript \\server\share\Offscrub10.vbs ProPlus /bypass 1 /q /s /NoCancel

start /wait %DeployServer%\setup.exe /config %ConfigFile%

:End

EndLocal

=====================================================
 
 These batch files are simply examples. There are other methods to automate this process. The biggest take away is to follow the following order:
#1. Uninstall Office 2010 using one of the available methods for automated uninstallation
#2. Wait for the uninstallation to complete.
#3. Install Office 2013 cleanly on the machine.

FAQ

Will user settings still migrate if we are removing Office 2010 prior to installing Office 2013?

A- Any user settings that would migrate during a typical upgrade would still migrate when performing an uninstall-upgrade. The user settings will migrate upon the first user of each Office 2013 application.

We are pushing the uninstall-upgrade using a deployment method that will perform the installation while a user is logged on to the machine. We have elected to use the Offscrub method and hide the CMD prompt window that Offscrub populates, but now find that there is no message to the user that the Office installation is taking place. Can we generate a notice to the users so they know that Office is being installed, and don’t try to shut down or disconnect the PC in the middle of the install?

A- It is not uncommon for folks to want to disable the command prompt window that Offscrub generates, because if that command prompt window is closed by the end user, than Offscrub will not complete. See Offscrub FAQ
http://blogs.technet.com/b/odsupport/archive/2011/04/08/how-to-obtain-and-use-offscrub-to-automate-the-uninstallation-of-office-products.aspx

You can launch a custom IE window or a CMD window to act as the user notification if you wish. As an example, you could add the following to launch a nice notice to the user:

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2013 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"

Then after the install completes, close the CMD notification with:

taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"

So the portion of the install code above would look similar to this:

:DeployOffice

start "----NOTICE----" cmd.exe /t:ec /Q /k "echo OFFICE 2013 IS BEING INSTALLED. THIS WINDOW WILL CLOSE WHEN COMPLETE&&prompt $h"
call cscript \\server\share\Offscrub10.vbs ProPlus /bypass 1 /q /s /NoCancel
start /wait %DeployServer%\setup.exe /config %ConfigFile%
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ ----NOTICE----"
taskkill /IM cmd.exe /FI "WINDOWTITLE EQ Administrator: ----NOTICE----"
echo %date% %time% Setup ended with error code %errorlevel%. >> %LogLocation%\%computername%.txt

The article link provided below, contains information about how to troubleshoot problems that affect the ability to sign in to Microsoft Office apps for Mac, iPad, iPhone, or iPod Touch by using single sign-on (SSO). This article also contains resources for IT administrators to address reports about Active Directory Federation Services (AD FS) issues that are specific to Office for Apple iOS and Mac platforms:

http://support.microsoft.com/kb/3015526

We wanted to inform our customers that we will not be releasing the Public Update (PU) for Office 365 ProPlus/Office 2013 this month.  The next PU is planned for February 2015.  For details about the release and version history of PU’s please refer to http://support.microsoft.com/gp/office-2013-365-update/

Issue
After installing Office Professional Plus 2013 with Service Pack 1 from the Volume Licensing Service Center (VLSC) with applications disabled, it has been found that adding the remaining Office applications at a later date using a customized MSP file, created using the Office Customization Tool (OCT), will prevent Microsoft Word from opening or running.

Workarounds

1. Use the config.xml file to add the remaining Office 2013 applications post initial install.  To accomplish this, edit the config.xml file to have the following:

<Configuration Product="ProPlus">

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

<OptionState Id="AccessFiles" State="local" Children="force" />
<OptionState Id="GrooveFiles2" State="local" Children="force" />
<OptionState Id="ExcelFiles" State="local" Children="force" />
<OptionState Id="OneNoteFiles" State="local" Children="force" />
<OptionState Id="OutlookFiles" State="local" Children="force" />
<OptionState Id="PPTFiles" State="local" Children="force" />
<OptionState Id="PubPrimary" State="local" Children="force" />
<OptionState Id="WordFiles" State="local" Children="force" />
<OptionState Id="XDocsFiles" State="local" Children="force" />
<OptionState Id="SharedFiles" State="local" Children="force" />
<OptionState Id="ToolsFiles" State="local" Children="force" />
<OptionState Id="XDocsFiles" State="local" Children="force" />
<OptionState Id="LyncCoreFiles" State="local" Children="force" />

</Configuration>

Once the initial install of Office 2013 with SP1 has completed, run the following command-line:
<path>\setup.exe /config <path>\config.xml

For further information on using the Config.xml file in Office 2013, refer to the following Microsoft Article: Config.xml file reference for Office 2013

2. When creating your customized MSP file for adding the remaining Office applications follow these steps:

• Open the Microsoft Office Customization Tool
• Navigate to "Set feature installation states"
• Click the drop down for the root of Microsoft Office and select the option "Run all from My Computer"
• Expand the root of Microsoft Office and individually select each of the below products and click the "Reset Branch" button
• Once you have reset each of the 13 products available in Professional Plus you can set each product's installation state to your preference
• Save and apply your MSP

The first step in configuring local Office 365 updating is to download the Office media using the Office Deployment Tool.  See the following article for more information on downloading and installing using the ODT.  Once it has been successfully downloaded, place the media in your desired network share location.  It is imperative that client machines have Read access to this folder.  One of the most common issues experienced with local updating is due to a lack of read permissions on the share.  The recommended method for directing client machines to a network location for updates is to set the UpdatePath at install.  To set the UpdatePath remove the XML comment tags <!--   --> from either side of the updates property in the configuration.xml file. Change the UpdatePath to the location where the updated versions will be stored.

<Updates Enabled="TRUE" UpdatePath=\\Server\Share\ />

This method is automatically creating the UpdateURL key in the registry (HKLM\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration) and assigning the value "\Server\Share\" to it.  Client machines will look to the location specified in the UpdateURL key at increments according to the scheduled task Office Automatic Updates.  Please note that if the UpdateURL key does not exist, client machines will download updates from the Microsoft Client Delivery Network (CDN).  If you choose to circumnavigate the scheduled task, client machines can be forced to check for updates immediately using the following command:

C:\Program Files\Microsoft Office 15\ClientX64\OfficeC2RClient.exe /Update User displaylevel=True

For more information on available Office 365 update commands see the following article.

Additional Information:

Office Deployment Tool for Click-to-Run
http://technet.microsoft.com/en-us/library/jj219422(v=office.15).aspx

Reference for Click-to-Run configuration.xml file
http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx

Managing Updates for Office 365 ProPlus
http://blogs.technet.com/b/office_resource_kit/archive/2014/01/28/managing-updates-for-office-365-proplus-part-2.aspx

It’s very common for users to switch devices or for an enterprise company to add/move Office 365 tenants. Once an Office 365 user activates a client machine there are three locations that need to be cleared to reset the activation/install to a clean state.

** If utilizing Shared Computer Activation there are two additional locations that must be cleared.

1. The Office 365 license:

1. 1. To remove the Office 365 license you must run two cscript command lines. The command lines are as follows.

C:\program files\Microsoft office\office15>cscript ospp.vbs /dstatus

The above command line will generate a report of the currently installed/activated license. (See Below)

The line you need to reference is “Last 5 characters of installed product key” Once you have the last 5 of the installed/activated product key tap the up arrow to bring back you most recently used command line. Then remove /dstatus and replace with /unpkey:(Last 5 of Product key)  NOTE: Make sure you Do Not have any spaces

(See below)

After running /unpkey: command line you will see a “Product Key successfully removed” message. You can now close the Command Prompt and move onto Step 2.

2. Remove Credentials in HKCU registry:

1. 1. Navigate to HKCU\Software\Microsoft\Office\15.0\Common\Identify\Identities and remove all of the identities under the key. Simply right click and choose delete. **

**NOTE: If using SCA on a Terminal Server/Citrix remove the above Identities from the users SID from HKU as well.

3. Remove the stored Credentials in the Credential Manager:

a. Click on Start > Click in Search and type cred > Then click on Credential Manager in the list. or go to Control Panel > Credential Manager.  Remove all credentials titled with Office15. (See Below)

To remove the Credential Click on the Drop down arrow and choose Remove from Vault.

***NOTE: In Shared Computer Activation scenarios (RDS/Terminal Server/Citrix VDI) You will need to remove the Tokens Credentials listed below.

File Location

Appdata\local\Microsoft\Office\15.0\Licensing

Registry Location

HKCU\Software\Microsoft\Office\15.0\Common\Identity

HKU\(The Users SID)\Software\Microsoft\Office\15.0\Common\Identity

After the above process is completed your Office 365 install will be reset to the initial install state for Activation. When Office is launched if SSO is enabled it will sign in. If SSO is not being used you will be prompted to login and activate Office 365.

Office 365 ProPlus User Activations Management
(Authored by Shubham Gupta, Program Manager)

User Management Admin and Global Admin roles can now view and manage users’ O365 ProPlus Desktop Installations.

When a user is unable to install office, most likely because they have exhausted their allowed installs; the user would call the IT Admins to help troubleshoot the issue. IT Admins would then help the user to get to the portal page and deactivate office from a computer that is no longer in use.

With User Activations Management feature, IT Admins can now view and manage PCs/Macs the user has Office Apps installed on.

(Please visit the site to view this video)

To manage a user’s O365 ProPlus desktop installs, go to:

1. On the O365 Admin Center and select Active Users.

2. Select the user for whom you want to manage desktop installs.

3. In the fly out page on the right you will see a new setting: Office Installations. Click on “Edit”.

4. The following page will list the devices the user has installed Office apps on.

5. Click on the “Deactivate” link to deactivate Office from the computer

6. Deactivating the install will free up the number of available installs allowing the user to activate office on a new PC/Mac.

Important Notes:

• The computer names are obfuscated to the IT Admins in order to comply with privacy requirements of certain countries.
• Once an Office install is deactivated, office apps may enter into reduced-functionality mode and function more like viewers.
• Deactivating a device doesn’t remove the app from the device. If the user wants to keep using the app on a device you have deactivated, they can reactivate it the next time they open the app.

Background

When you attempt to download the Office 365 ProPlus from the Microsoft content delivery network (CDN) using the Office Deployment Tool (ODT) you get the following message:

More Information

This occurs when you leave the SourcePath blank in the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=" " OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify a path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  This requirement is for /download only and not for /configure.

Background

When you attempt to install Office 365 ProPlus from a local folder using the Office Deployment Tool (ODT) you get the following message:

More Information

This occurs when you have a relative path specified in the SourcePath the configuration.xml.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath=".\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

Workaround

To workaround this issue, you will need to specify an absolute path (UNC or Local folder) in the SourcePath attribute of the configuration.xml file.  For example, your configuration.xml looks as follows:

<Configuration>
<Add SourcePath="c:\Office2016" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
</Configuration>

For Enterprise Customers using Office 365 ProPlus, users will be migrated to the latest version in February of 2016. If you want your users to stay on Office 2013 and continue to receive 2013 security updates, you can delay their migration to Office 2016 ProPlus. Your users will continue to receive security updates for Office 2013 ProPlus until September of 2016 through the same update method you are currently using. However after that time, no additional security updates will be made for Office 2013 ProPlus, so we strongly recommend that you migrate to the latest version before September of 2016.

There are three ways we can delay the migration to Office 2016 ProPlus, The first is to use a GPO setting that blocks the update or you can push out a registry key manually that will do the same. Those options are outlined in our KB here:

https://support.microsoft.com/en-us/kb/3097292

Thirdly, we can use the Office Deployment Tool (ODT) and the configuration.xml file to prevent the migration as well.

In the configuration.xml file we will add the AutoUpgrade attribute and set it to "FALSE" like in this example configuration.xml file here:

<Configuration> 
<Updates Enabled="TRUE" AutoUpgrade="FALSE" />
</Configuration>

The Office Deployment tool was updated in August of 2015 to accommodate this new switch. If you are using the old version of the tool you can download the newest one here.

Additional Links:

Prepare to update Office 365 ProPlus to the Office 2016 version

https://technet.microsoft.com/en-us/library/mt422981.aspx

We always recommend only having one version of Office on a machine and we recommend you use our most current versions. Having said that, there are times that due to adoption, testing, budget or migration strategies, it becomes necessary to have multiple versions of Office on a machine. There are certain combinations that are supported and others that are not.

First, there are now two architectures of Office builds. Volume Licensing (MSI) and Office click-to-run (Office 365) There are also three main Office products that we will look at here. Office Professional Plus, Visio and Project. Also, for the purpose of this article, installing one application like Skype for Business for example is the same as installing the entire Office suite. I will walk through some supported and unsupported scenarios here:

Unsupported:

Any MSI product(s) alongside the same year’s Click-to-run product(s) Example – Office ProPlus 2013 click-to-run and Visio 2013 MSI

Any Office 2013 Click-to-run product(s) alongside any 2016 click-to-run product(s).

Any Office 2016 click-to-run product alongside 2016 MSI language packs. (*note- you can have Office 2013 click-to-run and 2013 MSI language packs but they are not recommended. There are some known issues with this configuration)

Supported: (but not recommended)

Office ProPlus 2016 click-to-run and any 2013, 2010, or 2007 MSI product (ProPlus, Visio, Project)

Office ProPlus 2013 click-to-run and any 2016, 2010 or 2007 MSI product (ProPlus, Visio, Project)

Any combination of Office 2007, 2010, 2013 and 2016 MSI products (*note – you can only have one version of Outlook running at one time)

Keep in mind that there is a reason that we will say “supported but not recommended.” Issues with SharePoint Integration, Interop keys and other issues have been reported, as well as potentially new issues can occur when you use multiple versions of Office. So again, we recommend always being on the latest and greatest builds.

Additional resources:

Office installed using Click-to-Run and Window Installer on same computer isn't supported:
https://support.office.com/en-us/article/Office-installed-using-Click-to-Run-and-Window-Installer-on-same-computer-isn-t-supported-30775ef4-fa77-4f47-98fb-c5826a6926cd?ui=en-US&rs=en-US&ad=US

Install and use different versions of Office on the same PC:
https://support.office.com/en-us/article/Install-and-use-different-versions-of-Office-on-the-same-PC-6EBB44CE-18A3-43F9-A187-B78C513788BF

Issue: When customers install Office Professional Plus 2013 MSI or Lync 2013 MSI standalone and use the Office Customization Tool (OCT) to change the default Start Menu Shortcut path, after installing the April 2015 update for Office which transforms Lync 2013 to Skype for Business 2013, the shortcut for Skype for Business will remain as “Lync 2013” which can be confusing for end users.

We can work around this by using a PowerShell script like the following sample to change the Lync shortcut icons to Skype for Business icons. *Note– this script is an example script and should be tested before being used in production.

============================================
$shortcutLocation = "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Office 2013\"
$oldShortcut = "Lync 2013.lnk"
$newShortcut = "Skype for Business 2015.lnk"
$iconComment = "Connect with people everywhere through voice and video calls, Skype Meetings, and IM."

# Rename shortcut:
Rename-Item $shortcutLocation$oldShortcut $newShortcut

# Change the new shortcut settings
$shell = New-Object -COM WScript.Shell
$shortcut = $shell.CreateShortcut($shortcutLocation+$newShortcut)
$shortcut.Description = $iconcomment
$shortcut.Save()

#Get the Icon Name and Folder
$iconlocation = $shortcut.IconLocation
$tempInd = $iconlocation.indexof("Icon")

$iconName = $iconlocation.substring($tempInd,$iconlocation.indexof(".exe")-$tempInd )
$iconFolder = $iconlocation.substring(0,$tempInd)

#Change the icon:
Rename-Item $iconFolder$iconName".exe" $iconFolder$iconName"_old.exe"
Copy-Item $iconFolder"lyncicon.exe" $iconFolder$iconName".exe" -force

=====================================

This blog was submitted by Jeremy Chapman, director on the Office team

Many organizations use the Microsoft Deployment Toolkit (MDT) to deploy Windows with Office to new computers or when re-imaging computers. You can use the tools to deploy just applications, or as part of an operating system + application deployment.

If you’ve been deploying Office or using MDT for a few years, you may know that the integration for Office deployment began in 2007 when MDT was called Business Desktop Deployment 2007 and Office 2007 suites introduced the Office Customization Tool. These capabilities have remained largely unchanged for the MSI package versions of Office over the years – currently Office Professional Plus 2016 and Office Standard 2016.

Fast forward to 2016 and while the tools have been consistent for around nine years, what if you were the IT administrator tasked with building out an imaging solution for Windows 10 and Office 2016 today using MDT? Where is the process documented for installing Office 2016? It turns out the process is documented on TechNet… but labeled as the approach for Office 2010. In reality, the same approach works in Office 2013 and Office 2016 MSI packages.

Once you’ve downloaded and installed MDT, installed the Windows 10 Automated Deployment Kit, and downloaded Office installation files from the Volume Licensing Service Center, here’s what you do to add Office 2016 into your MDT deployment share.

1.  Under MDT Deployment Share, click Applications and then click New Application in the Action pane. The New Application Wizard opens to the Application Type page.

2.  On the Application Type page, make sure that Application with source files is selected, and then click Next.

3.   On the Details page:

       a.     Under Publisher, type the name of the application publisher (optional).

       b.     Under Application Name, type a descriptive name for the application (required).

       c.     Under Version, type the application version (optional).

       d.     Under Language, type the application language (optional).

       e.     Click Next.

4.   On the Source page:

       a.     Click Browse. In the Browse for Folder dialog box, locate and select the folder that contains the setup files for the particular application, and then click OK.

       Note: If you want to move the setup files instead of copying them, select the check box that is next to Move the files to the deployment share instead of copying them.

       b.    Click Next.

5.    On the Destination page, accept or change the default destination folder (the deployment share folder that will contain the application source files) that was assigned by the wizard, and then click Next.

6.    On the Command Details page:

       a. Under Command line, type the command that you want to be run at the start of the application installation. This is typically “setup.exe”, you can access the Office Customization Tool via the Application Properties > Office Products tab later.

       b. Click Next

7.    On the Summary page, click Next.

8.    The Progress page indicates that the share is being created. On the Confirmation page, click Finish. The New Application Wizard finishes, and the application name that you typed in the Application Name page appears in the Deployment Workbench details pane.

Now you can access the properties of the Office 2016 install in the Applications menu of your deployment share.

Here in the Office Products tab, you can select the Office product to install and configure Display Level, automatically accept the EULA and suppress reboots.

The majority of your granular Office customization will be done via the Office Customization Tool (OCT), which outputs an update (.MSP) file that is automatically consumed as part of the Office installation. Plus you can use MDT to deploy additional Office applications – like the legacy versions of InfoPath or SharePoint Designer – or use it to install custom Office add-ins. Once you’ve finished the above steps and anything you want to do with the OCT, you can start building Windows or custom application-only deployment task sequences with MDT. 

Issue
After installing Office Professional Plus 2013 with Service Pack 1 from the Volume Licensing Service Center (VLSC) with applications disabled, it has been found that adding the remaining Office applications at a later date using a customized MSP file, created using the Office Customization Tool (OCT), will prevent Microsoft Word from opening or running.

Workarounds

1. Use the config.xml file to add the remaining Office 2013 applications post initial install.  To accomplish this, edit the config.xml file to have the following:

<Configuration Product="ProPlus">

<Display Level="none" CompletionNotice="no" SuppressModal="yes" AcceptEula="yes" />

<OptionState Id="AccessFiles" State="local" Children="force" />
<OptionState Id="GrooveFiles2" State="local" Children="force" />
<OptionState Id="ExcelFiles" State="local" Children="force" />
<OptionState Id="OneNoteFiles" State="local" Children="force" />
<OptionState Id="OutlookFiles" State="local" Children="force" />
<OptionState Id="PPTFiles" State="local" Children="force" />
<OptionState Id="PubPrimary" State="local" Children="force" />
<OptionState Id="WordFiles" State="local" Children="force" />
<OptionState Id="XDocsFiles" State="local" Children="force" />
<OptionState Id="SharedFiles" State="local" Children="force" />
<OptionState Id="ToolsFiles" State="local" Children="force" />
<OptionState Id="XDocsFiles" State="local" Children="force" />
<OptionState Id="LyncCoreFiles" State="local" Children="force" />

</Configuration>

Once the initial install of Office 2013 with SP1 has completed, run the following command-line:
<path>\setup.exe /config <path>\config.xml

For further information on using the Config.xml file in Office 2013, refer to the following Microsoft Article: Config.xml file reference for Office 2013

2. When creating your customized MSP file for adding the remaining Office applications follow these steps:

• Open the Microsoft Office Customization Tool
• Navigate to "Set feature installation states"
• Click the drop down for the root of Microsoft Office and select the option "Run all from My Computer"
• Expand the root of Microsoft Office and individually select each of the below products and click the "Reset Branch" button
• Once you have reset each of the 13 products available in Professional Plus you can set each product's installation state to your preference
• Save and apply your MSP

The first step in configuring local Office 365 updating is to download the Office media using the Office Deployment Tool.  See the following article for more information on downloading and installing using the ODT.  Once it has been successfully downloaded, place the media in your desired network share location.  It is imperative that client machines have Read access to this folder.  One of the most common issues experienced with local updating is due to a lack of read permissions on the share.  The recommended method for directing client machines to a network location for updates is to set the UpdatePath at install.  To set the UpdatePath remove the XML comment tags <!–   –> from either side of the updates property in the configuration.xml file. Change the UpdatePath to the location where the updated versions will be stored.

<Updates Enabled="TRUE" UpdatePath=\\Server\Share\ />

This method is automatically creating the UpdateURL key in the registry (HKLM\SOFTWARE\Microsoft\Office\15.0\ClickToRun\Configuration) and assigning the value "\Server\Share\" to it.  Client machines will look to the location specified in the UpdateURL key at increments according to the scheduled task Office Automatic Updates.  Please note that if the UpdateURL key does not exist, client machines will download updates from the Microsoft Client Delivery Network (CDN).  If you choose to circumnavigate the scheduled task, client machines can be forced to check for updates immediately using the following command:

C:\Program Files\Microsoft Office 15\ClientX64\OfficeC2RClient.exe /Update User displaylevel=True

For more information on available Office 365 update commands see the following article.

Additional Information:

Office Deployment Tool for Click-to-Run
http://technet.microsoft.com/en-us/library/jj219422(v=office.15).aspx

Reference for Click-to-Run configuration.xml file
http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx

Managing Updates for Office 365 ProPlus
http://blogs.technet.com/b/office_resource_kit/archive/2014/01/28/managing-updates-for-office-365-proplus-part-2.aspx

It’s very common for users to switch devices or for an enterprise company to add/move Office 365 tenants. Once an Office 365 user activates a client machine there are three locations that need to be cleared to reset the activation/install to a clean state.

** If utilizing Shared Computer Activation there are two additional locations that must be cleared.
*** The path will change if you've installed 2013 or 2016 Office Click To Run.

1. The Office 365 license:

1. 1. To remove the Office 365 license you must run two cscript command lines. The command lines are as follows.

C:\program files\Microsoft office\office15>cscript ospp.vbs /dstatus

The above command line will generate a report of the currently installed/activated license. (See Below)

The line you need to reference is “Last 5 characters of installed product key” Once you have the last 5 of the installed/activated product key tap the up arrow to bring back you most recently used command line. Then remove /dstatus and replace with /unpkey:(Last 5 of Product key)  NOTE: Make sure you Do Not have any spaces

(See below)

After running /unpkey: command line you will see a “Product Key successfully removed” message. You can now close the Command Prompt and move onto Step 2.

*NOTE: Make sure you remove all of the licenses that show up in the /dstatus report until it states "No Installed Product Keys".

2. Remove Credentials in HKCU registry:

1. 1. Navigate to HKCU\Software\Microsoft\Office\15.0\Common\Identity\Identities and remove all of the identities under the key. Simply right click and choose delete. **

**NOTE: If using SCA on a Terminal Server/Citrix remove the above Identities from the users SID from HKEY Users as well.

3. Remove the stored Credentials in the Credential Manager:

a. Click on Start > Click in Search and type cred > Then click on Credential Manager in the list. or go to Control Panel > Credential Manager.  Remove all credentials titled with Office15. (See Below)

To remove the Credential Click on the Drop down arrow and choose Remove from Vault.

***NOTE: In Shared Computer Activation scenarios (RDS/Terminal Server/Citrix VDI) You will need to remove the Tokens Credentials listed below.

File Location

Appdata\local\Microsoft\Office\15.0\Licensing

Registry Location

HKCU\Software\Microsoft\Office\15.0\Common\Identity

HKU\(The Users SID)\Software\Microsoft\Office\15.0\Common\Identity

After the above process is completed your Office 365 install will be reset to the initial install state for Activation.