DirSync/AADSync/AADConnect

How to migrate AAD Connect database to a new SQL server

autor:

 

1/ Stop + disable „Microsoft Azure AD Sync“ (ADSync)

2/ Migrate database to new SQL server (CI collation etc, see https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-prerequisites)

3/ Restore db owner + permissions for a service account on new SQL server

4/ Backup registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync\Parameters
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion

5/ Update registry with new SQL server/instance name

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync\Parameters\SQLInstance
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ADSync\Parameters\Server
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion\SqlInstanceName
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSOLCoExistence\CurrentVersion\SqlServerName

6/ Start „Microsoft Azure AD Sync“ (ADSync)

7/ Check logs + sync manager console

8/ 🙂

Atribut “adminDescription” v AADConnectu

autor:

Tohle jsem netušil, a přitom je to prima:

Populating the “adminDescription” attribute with the value “User_NoO365Sync” or “Group_NoO365Sync” (depending on the object type) will allow you to easily filter these objects.

Office 365 – The (Previously) Undocumented AAD Connect Filter


https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnectsync-understanding-default-configuration/

Performance countery pro AADSync

autor:

Postup sice žádné performance countery neopraví, ale v logu se přestanou množit chyby. Dle MS supportu bude opraveno v dalších verzích, chyby se přelila z FIMu.

  1. Delete registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\ FIMSynchronizationService\Performance]
  2. Recreate the ‚Performance‘ registry key.
  3. unlodctr.exe FIMSynchronizationService
  4. lodctr.exe „C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Bin\mmsperf.ini“

http://blogs.technet.com/b/steady/archive/2015/01/12/aadsync-the-server-encountered-an-unexpected-error-creating-performance-counters-for.aspx

http://social.technet.microsoft.com/wiki/contents/articles/16631.troubleshooting-fim-sync-eventid-6313-unable-to-load-performance-counters-for-management-agent.aspx