Error code 1603 – Skype for Business upgrade

Skype for Business server 2015 is here, and with it comes a time for “firsts”. Today, I’ve done my first In-place upgrades on servers from Lync 2013 to SfB 2015.

One thing I noted on a couple of servers was that the install failed during “Installing local management services” with this error:

Error returned while installing OcsCore.msi(Feature_LocalMgmtStore), code 1603.

I tried the “retry” option in the wizard, but it did no difference. A reboot of the server did the trick in both instances and the install continued perfectly.

I saved the logs and went through them afterwards, and found these lines

Error 0x80070430: failed to set security info for object: RTCCLSAGT error code: 1072
Error 0x80070430: failed to set security info for object: REPLICA error code: 1072

A quick google search shows that this error means “The specified service has been marked for deletion.” So for some reason the wizard hasn’t been able to completely delete the service. Seems that the easiest way to resolve this error is a quick reboot of the server, but to avoid getting it here’s a couple of checks:

  • Be sure to have closed all mmc instances on the server, including
    • Services
    • Event viewer
  • Close Task manager

I’m pretty sure there are other causes for the error as well, but again, in all cases a reboot should solve the issue.

Bug in KB 2863908

There seems to be a bug in the Lync update KB 2863908 that breaks integration between Outlook 2010 and Lync 2013.

If you search for a local outlook contact in lync, it will not display a phone number  on the contact card unless you remove the email address from the contact. If an email address is present on the contact, the lync client will not display any phone numbers for the contact.

As far as I have seen it only occurs when you have Lync 2013 and Outlook 2010.

Removing KB 2863908 resolves the issue.

There are also a couple of threads on the technet forums about this:

http://social.technet.microsoft.com/Forums/en-US/4317ec0e-3287-427d-b875-5b9c93997139/lync-client-2013-does-not-get-contact-phone-numbers-from-outlook-2010?forum=lyncprofile

http://social.technet.microsoft.com/Forums/lync/en-US/130ff6ff-54aa-42a2-86c5-69761eec446a/lync-2013-client-does-not-show-outlook-contact-numbers?forum=ocsclients

Script: Create live tiles that changes power scheme

After i got my Surface Pro, I’ve more often than before found myself needing to change between power schemes. On my laptop, I’ll usually set it to “Max performance” and just leave it there, but on the Surface it’s necessary to conserve power a bit more.

I’ve thought about making a live tile to do this, so I wrote a PowerShell script that will create one live tile for each configured powerscheme on the machine and pins it to the start screen. The code is based on a codesample for creating shutdown tiles, and this ScriptingGuy post. The script needs to be run as Administrator. Enjoy!

Download Create-PowerSchemeTiles.zip or copy the sourcecode:


#requires -Version 3.0

#####################################################################################
# Create-PowerSchemeTiles.ps1
#
# Creates live tiles for all configured power schemes on the machine and pins them to
# the start screen.
#
#
# Usage:
# .Create-PowerSchemeTiles.ps1
#
# Written by Tom-Inge Larsen (<a href="http://www.codesalot.com">http://www.codesalot.com</a>)
#
#####################################################################################

Function CreatePowerSchemeTile
{
    Param
    (
        [parameter(Mandatory=$true)][String[]]$SchemeGUID,
        [parameter(Mandatory=$true)][String[]]$SchemeName
    )
Write-Verbose "Creating Windows shutdown tile to Start menu."

#create a new shortcut
$ShortcutPath = "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\" + $SchemeName + ".lnk"
$Shortcut = $WshShell.CreateShortcut($ShortcutPath)
$Shortcut.TargetPath = "$env:SystemRoot\System32\powercfg.exe"
$arguments = "-s " + $SchemeGUID
$Shortcut.Arguments = $arguments
$Shortcut.Save()

#change the default icon of shortcut
$Lnk = $Desktop.ParseName($ShortcutPath)
$LnkPath = $Lnk.GetLink
$LnkPath.SetIconLocation("$env:SystemRoot\System32\ddores.dll",20)
$LnkPath.Save()

#pin application to windows Start menu
$Verbs = $Lnk.Verbs()
Foreach($Verb in $Verbs) {
    If($Verb.Name.Replace("&","") -match "Pin to Start") {
        $Verb.DoIt()
    }
}

If(Test-Path -Path $ShortcutPath) {
    Write-Host "Create" $SchemeName "tile successfully." -ForegroundColor Green
    } Else {
    Write-Host "Failed to create" $SchemeName "tile." -ForegroundColor Red
   }
}

$Shell = New-Object -ComObject Shell.Application
$Desktop = $Shell.NameSpace(0X0)
$WshShell = New-Object -comObject WScript.Shell
$plans = Get-WmiObject -Class win32_powerplan -Namespace root\cimv2\power
$regex = [regex]"{(.*?)}$"
foreach ($plan in $plans) {
    $planGuid = $regex.Match($plan.instanceID.Tostring()).groups[1].value
    $planName = $plan.ElementName.Tostring()
    Write-Debug $planGuid
    Write-Debug $planName
    CreatePowerSchemeTile -SchemeGUID $planGuid -SchemeName $planName
}

Lync 2010 and EWS followup

This is a followup to this post.

Turns out that Outlook doesn’t really like autodiscover through SRV records and proceeds to ask the user for authentication when this happens. This is often not a desireable situation.

The other option seemed to be to add names for autodiscover.domain.com for each of the SMTP domains to the certificate on the CAS. We tried this as well, but in this configuration the Lync client started asking about trust of the server. A bit of searching led me to this post by Jens Trier Rasmussen that explains why.

I was not able to find any place to add trusted servers to Lyncs trusted server list, but for Outlook i could, so the solution was to revert to SRV records, and add this regkey to the machines:


Office 2007:
HKCUSoftwareMicrosoftOffice12.0OutlookAutoDiscoverRedirectServers

Office 2010:
HKCUSoftwareMicrosoftOffice14.0OutlookAutoDiscoverRedirectServers

add the CAS server FQDN as the value name of a key with value type REG_SZ and empty value data.

This tells Outlook to always trust this server.

Problems running OCS2009-DBUpgrade on OCS SE/Server 2008?

Just run the msi in an elevated cmd window. UAC is the problem

Thanks to Tonino at proexchange.be!

  • http://www.proexchange.be/blogs/ocs2007r2/archive/2010/03/25/executing-the-ocs2009-dbupgrade-package-fails-on-windows-2008.aspx
  • CCNA!

    I just passed my Cisco Certified Network Associate exam that I’ve been working on the last couple of weeks! Hooray for me!