kdadoc.blogg.se - Office 365 terminal server

Timothy also holds many advanced certifications, including Microsoft 365 Enterprise Administrator Expert (M365 EA), CompTIA A+, CompTIA Network+, Certified SonicWALL Security Administrator (CSSA) Microsoft Certified Solutions Expert (MCSE) and Microsoft Certified Solutions Associate (MCSA). Timothy Longueil is a Senior Network Consultant and Project Engineer at Sikich that works closely with organizations to improve productivity and increase overall profit. This was highly successful and made for an extremely smooth migration for all parties involved.ĭo you have a Remote Desktop Services environment in which you’ve been struggling, or have a lack of confidence to move to Office 365 because of the amount of manual effort needed? Contact the Sikich team to start your migration to Office 365 today and rest easy tomorrow! All they need to do is click Next and the profile is configured to connect to Office 365. Now, the next time a user logs into an RDS server, they get presented with a new profile window when launching Outlook.Reboot the RDS servers to apply the policies.

Finally, create a new GPO with the following settings and apply this to the RDS organizational unit inside Active Directory that contains the RDS servers.DNS management is next - verify that the internal Autodiscover A and SRV records are removed, and create a CNAME record to point to Offce365 at.

CN=Autodiscover,CN=Protocols,CN=ServerName,CN=Servers,CN=Exchange Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services

Next, log into Active Directory Sites and Services, navigate to the Services node, and remove the SCP entry for the Exchange Autodiscover record.

Reg add HKCU\Software\Microsoft\Office\16.0\Outlook /v DefaultProfile /t REG_SZ /d “Office365” /F Note the section in red, this is the expected Outlook “profile name.” reg add HKCU\Software\Microsoft\Office\16.0\Outlook\Profiles\Office365 reg file in notepad that contains the follow registry keys associated with the Outlook profile. The steps to accomplish this task are explained in detail below:

Create Group Policy Object with new organizational unit and move RDS servers there.

Update DNS Autodiscover entries to point to Office 365 via CNAME.

Remove SCP Autodiscover service entry for local on-premises Exchange within Active Directory.

Create registry key for Outlook profile to install on user login registry file placed in NETLOGON share.

This environment included Windows Server 2012 R2, Microsoft Office 2016, and an Active Directory Domain. Recently, I was tasked with an Office 365 migration for over 150 users, where an RDS environment was in use for email and collaboration. One challenge I encounter more frequently when I perform an email migration is having to recreate users’ Outlook profile in a Remote Desktop Service (RDS) environment.