Finish migration from SFB hybrid to online

https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid

Cloud Azure MFA Radius?

With MFA server onpremises deprecation, you need to implement NPS extension for Azure on your local NPS/Radius to connect to Cloud MFA.

https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-mfa-nps-extension

Exchange hybrid migration errors decoded

https://blogs.technet.microsoft.com/exovoice/2017/06/30/hybridmigrationerrors/

Skype for Business mobility and hair-pinning requirements

Mobility Service URL Requirement

In a default configuration, a user who is connected to the internal network via Wi-Fi will always be returned the external Mobility Service URL for his/her home pool. The user’s device must be able to query the internal DNS zone and resolve the external Lync Web Services FQDN to the IP address of the external interface of the reverse proxy. The user will then make an outbound, hair-pinned connection to the Mobility Service through the reverse proxy.

https://docs.microsoft.com/en-us/previous-versions/office/skype-server-2010/hh690030(v=ocs.14)

Add or remote server from the Lync pool

https://tomtalks.blog/2013/04/lync-2013-gotcha-when-addingremoving-fes-in-topology-publishing-topology-will-reset-the-relevant-pool/

https://docs.microsoft.com/en-us/skypeforbusiness/manage/topology/manage-front-end-servers


When you add or remove a server to the pool in your topology and then publish the updated topology, it will cause all of the servers in the pool to restart at the same time. While the servers are restarting the pool is offline, which will interrupt service for your users connected to that pool. To prevent any interruption of service to users, plan to publish the topology with the new server in the pool during non-business hours.

Windows 2019 server activation error

With a correct key, we can not activate Windows 2019 server:

"We can’t activate Windows on this device as we can’t connect to your organization’s activation server. Make sure that you’re connected to your organization’s network and try again."

The workaround is to do with command line - run as administrator:

slmgr.vbs /ipk   key-key-..

SharePoint 2013 install error 1603

if you get an error such as

Problem Event Name:                        OfficeClassicSetup

  SETUP EXE VERSION:                        15.0.4454.1000

  SETUP DLL NAME:                            SVRSETUP.DLL

  SETUP DLL VERSION:                        15.0.4709.1000

  ERROR CODE:                                   1603

  MSI HRESULT:                                   Unspecified

  ERROR DETAILS:                               FC73469E

  FIRST ERROR CODE:                         1603

  OS Version:                                       6.3.9600.2.0.0.272.7

  Locale ID:                                          1033

it may mean that you need to ad resources: check if you have 4vCPU, disk space 80GB+

Re.run setup