In almost all the cases, the organization is not in a position to get away from the local domain as its tightly connected with other services that are running on-premises and maintaining the on-premises identity is vital.
Further, you have the on-premises domain and the workstations are joined to it, GPOs being pushed across and everything is being managed centrally with the ACLs/ security groups and etc.
Continue reading “Preparing workstations for the Cloud Journey with Hybrid Azure AD Join”
Enter Azure AD Connect Sync that combines the on-premises with the Cloud world.
In most cases, the journey to cloud will start by migrating the Exchange workloads to Exchange Online and by installing Office 365 suite and consuming the benefits that comes with the cloud license, and with this way the hybrid identity is made and will be a part of a much bigger universe.
Almost everyone is familiar with the traditional Windows file servers/ shared drives concepts and its a heavily used Windows Service. Users are very familiar with how to access those directories, request access to certain files and folders and request for file recovery if it’s deleted.
Continue reading “Azure Files – Create File Shares in Azure and Authenticate via Azure AD Domain Services”
So far this mechanism has been used/ still using with on-premises files servers. 1 or 2 if not many file servers.
Continue reading “Windows Server 2019 Time zone issues with Daylight Savings option on/off?”
Domain Controller A is sitting in a different time zone and Domain Controller B that holds the PDC Emulator FSMO role is sitting in another time-zone.
DC A is on WS2019 – does not use Daylight saving settings
DC B is on WS2012R2 – uses Daylight saving
Ideally DC A should run 1 hour behind as they are not using the daylight saving option, but DC A’s time is the same as DC B’s time.