Sync Local AD Object Properties to Azure Manually

 

Azure AD Sync Service

Sync Local AD Object Properties to Azure Manually

Most small and large businesses have a local domain with domain controllers. When using Microsoft 365 online services, these business will commonly also have an AD Sync server. This server often just a small virtual machine running Azure AD Connect service. 

Azure AD Connect Services Sync

Azure AD connect services sync local change from the local domain to Azure on schedule. The schedule is restricted by Microsoft and the shortest time is 30 minutes. Password changes occur nearly instantly but all other AD object additions or changes to exiting objects take 30 minutes or more. 

Other factors such as local AD replication between domain controllers affects syncing as well. So with sloe local replication the time to sync changes or AD additions to Azure will take even longer depending on the speed of local replication. 

To trigger a local AD replication, logon a domain controller and open an elevated command prompt. this is the fastest way to replicate all domain controllers throughout all sites. This is faster than using the UI. 

At the command prompt enter the following command: 

  C:\>repadmin /syncall /APeD

The command will trigger AD replication though-out the entire domain on all domain controllers.  This an other command can be run remotely. Remote support and software for online Desktop support gives us the capability to access computers and servers remotely for remote control. Some are agent based and others are on-demand. In either case once connected remotely with online computer support software of your choice, you  help the user or administer the server. 

Manual adsyncsynccycle 

Manual AD Sync from local AD to Azure.

The following command I have run very often to trigger replication or syncing from the local domain to Azure. This quick option for manual replication enables faster updates to Azure. it is particularly useful when a new user has been added and you need to continue setting up the user with their desktop and applications. 

Use RDP or another method to access your Azure Sync server and run the following command as shown in the screen capture in this post. that was taken from a real server that was setup and configured to perform Azure AD sync with Microsoft Azure AD connect software.

Run the command in an elevated PoweShell Session. Include the capitalization. 

         C:\>Start-ADSyncSyncCycle -PolicyType Delta 

Be sure to include Delta at the end of the command. There is another option (actually many more) to this command but another that would sync is Initial instead of delta. Please avoid using that option unless you have good reason to because it could cause other issues. Changes are updates lowly sometimes in Azure so expect several to 20 or 30 seconds before you see the changes in Azure. 

Troubleshooting ADSyncSyncCycle AD syncing to Microsoft Entra 

Most common issue with Azure Entra Syncing is the service has stalled for whatever reason. Restart the services associated with Azure / Entra Sync . A reboot of the server is often not required. Be careful to NEVER alter the login ID used for the services. 

.

The time provider NtpClient is configured to acquire time

If your geting the following error in your system log do the following.
On your root level PDC emulator domain controller run the command at a command prompt:
net time /setsntp:ntp2.usno.navy.mil /set /y
Then restart the time service.
On all child domain controllers that are the PDC emulator for the domain run the following command:
net time \\ROOT-DC-name /set
Change ROOT-DC-name to your root level domain controller name running the PDC emulator.
Then restart the time service.
Check your system log. You will see confirmations that the local time service is now syncing with the time source.

BlackBerry Torch Doesn't Reconcile Inbox - Syncing

BlackBerry Torch Syncing Problem with BES 4.1, Exchange 2007.
This was a new BlackBerry Torch 9800 series phone. The user had problems with reconciliation from the begining although it was not noticed right away.

His outlook inbox surely did not match the phones renerding of the inbox. Messages that had been removed in Outlook were still showing on the the BlackBerry Torch 9800 phone. Not part of the problem, but this user had ATT service. The BES (BlackBerry Enterprise Server) was version 4.1. There were about another 70 users on the BES server but none of them had this issue. What was done to resolve was firstly to change the number of messages tracked on the BES server and enabled HARD delete tracking.
Those options can be found by logging into the BES 4.1 server:
- Open BlackBerry Manager.
- In the explorer view, click server.
- On the server configuration tab, click edit Properties, then click Messaging.
- For the hard deletes reconciliation option, select True from the drop-down menu
- Restart the BlackBerry enterprise Server services ( I recommend restarting the services from the services control panel applet, not from the BES manager).

To change the number of messages tracked (the default messages tracked is 100)

In the performance section change the value of the Message State database Size to 1000. 1000 is the max.

I also resent the service book for the user, resent the IT policy, resent the peer to peer key.