Quantcast
Channel: Office Deployment Support Team Blog
Viewing all 43 articles
Browse latest View live

‘Update Now’ gone from Office backstage after build 1708 when configured to update through SCCM.

$
0
0

Starting on Version 1708 the ‘Update Now’ from the Office 365 Application backstage is no longer visible if the Office installation is also configured to receive updates through SCCM.

This change was implemented so that Users cannot bypass administrative configuration settings around updating Office.

Prior to Version 1708:

At Version 1708 and greater you will see a message that Updates are managed by your admin:

The ‘Update Now’ option is also hidden:

If a user requires individually updating the Office Client outside of SCCM, they can still do this through command line with elevated privileges.

To manually trigger an Office update, run “OfficeC2RClient.exe /update user” from the cmd prompt path ‘C:\Program Files\Common Files\Microsoft Shared\ClickToRun>”

To specify a specific version run “OfficeC2RClient.exe /update user updatetoversion=16.0.xxxx.xxxx

For more information around configuring updates, please see Configure Update Settings for Office 365 ProPlus.

 

 

 


How to enable Office 365 ProPlus ULS logging

$
0
0

There are times during troubleshooting an Office issue when the traditional log settings are not gathering enough information. This could be for Sign-In issues, installation and patching issue, even App issues.

To gather more verbose logging details, set the following registry key.

[HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\Logging]
"EnableLogging"=dword:00000001

Reproduce the issue and gather the logs for review. The logs will be stored under %temp%. Note the time stamp you did the repro so you gather the correct logs.

Turn off the Office ULS verbose logging setting after you gather the logs, otherwise this will continue to gather verbose data and take up more dive space.

Reg keys to automate logging enabled/disabled: Enable-Local-Logging2016 Disable-Local-Logging2016

Lync 2013 Shortcut Icon doesn’t change to Skype for Business after updating Lync to Skype for Business.

$
0
0

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

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

Viewing all 43 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>