So I had chance to spin UR1 and I want to share with you some tips that may help you during your deployment.
SCVMM
- When you install the SCVMM Server UR1 you may need to stop your SCOM and SCVMM agents. This happened to me when I was updating passive nodes of HA VMM Cluster. On one of the nodes WinRM service was even needed.
- Updating the console on Service Provider Foundation (SPF) servers required stopping IIS service and SCOM agent.
- If you had VMs with Shared VHDX created outside of VMM like for example the VMM servers itself and their SQL cluster and refresh these VM’s as before UR1 was not possible you still might get error on refresh. The refresh finds the configuration of the VMs but still some exception is thrown. To get rid of this error stop the passive node and refresh it while it is stopped. Start it. Failover the role. Stop the other node and refresh it while it is stopped.
SCOM
- When executing the SQL script against the OperationsManager DB I’ve received the following error:
(34 row(s) affected)
(1 row(s) affected)
(1 row(s) affected)
Msg 1205, Level 13, State 56, Line 1
Transaction (Process ID 107) was deadlocked on lock resources with another process and has been chosen as the
deadlock victim. Rerun the transaction.
Msg 3727, Level 16, State 0, Line 1
Could not drop constraint. See previous errors.
Tip from Daniele Grandini : shutdown all SCOM services on the management server/s. Execute the script again.
- There is no need to update SCOM windows agents as there is no new version. You can just reject them in the SCOM console