Skip to content

Commit 7a64827

Browse files
authored
Update active-directory-aadconnect-troubleshoot-sso.md
1 parent 1a08fb8 commit 7a64827

File tree

1 file changed

+7
-6
lines changed

1 file changed

+7
-6
lines changed

articles/active-directory/connect/active-directory-aadconnect-troubleshoot-sso.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.assetid: 9f994aca-6088-40f5-b2cc-c753a4f41da7
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: article
12-
ms.date: 07/26/2018
12+
ms.date: 09/04/2018
1313
ms.component: hybrid
1414
ms.author: billmath
1515
---
@@ -29,7 +29,7 @@ This article helps you find troubleshooting information about common problems re
2929
- Seamless SSO doesn't work in Internet Explorer when Enhanced Protected mode is turned on.
3030
- Seamless SSO doesn't work on mobile browsers on iOS and Android.
3131
- If a user is part of too many groups in Active Directory, the user's Kerberos ticket will likely be too large to process, and this will cause Seamless SSO to fail. Azure AD HTTPS requests can have headers with a maximum size of 50 KB; Kerberos tickets need to be smaller than that limit to accommodate other Azure AD artifacts (typically, 2 - 5 KB) such as cookies. Our recommendation is to reduce user's group memberships and try again.
32-
- If you're synchronizing 30 or more Active Directory forests, you can't enable Seamless SSO through Azure AD Connect. As a workaround, you can [manually enable](#manual-reset-of-azure-ad-seamless-sso) the feature on your tenant.
32+
- If you're synchronizing 30 or more Active Directory forests, you can't enable Seamless SSO through Azure AD Connect. As a workaround, you can [manually enable](#manual-reset-of-the-feature) the feature on your tenant.
3333
- Adding the Azure AD service URL (https://autologon.microsoftazuread-sso.com) to the Trusted sites zone instead of the Local intranet zone *blocks users from signing in*.
3434
- Disabling the use of the **RC4_HMAC_MD5** encryption type for Kerberos in your Active Directory settings will break Seamless SSO. In your Group Policy Management Editor tool ensure that the policy value for **RC4_HMAC_MD5** under **Computer Configuration -> Windows Settings -> Security Settings -> Local Policies -> Security Options -> "Network Security: Configure encryption types allowed for Kerberos"** is "Enabled".
3535

@@ -101,10 +101,9 @@ If troubleshooting didn't help, you can manually reset the feature on your tenan
101101

102102
### Step 1: Import the Seamless SSO PowerShell module
103103

104-
1. Download and install the [Microsoft Online Services Sign-In Assistant](http://go.microsoft.com/fwlink/?LinkID=286152).
105-
2. Download and install the [64-bit Azure Active Directory module for Windows PowerShell](http://go.microsoft.com/fwlink/p/?linkid=236297).
106-
3. Browse to the `%programfiles%\Microsoft Azure Active Directory Connect` folder.
107-
4. Import the Seamless SSO PowerShell module by using this command: `Import-Module .\AzureADSSO.psd1`.
104+
1. First, download, and install [Azure AD PowerShell](https://docs.microsoft.com/powershell/azure/active-directory/overview).
105+
2. Browse to the `%programfiles%\Microsoft Azure Active Directory Connect` folder.
106+
3. Import the Seamless SSO PowerShell module by using this command: `Import-Module .\AzureADSSO.psd1`.
108107

109108
### Step 2: Get the list of Active Directory forests on which Seamless SSO has been enabled
110109

@@ -124,8 +123,10 @@ If troubleshooting didn't help, you can manually reset the feature on your tenan
124123
### Step 4: Enable Seamless SSO for each Active Directory forest
125124

126125
1. Call `Enable-AzureADSSOForest`. When prompted, enter the domain administrator credentials for the intended Active Directory forest.
126+
127127
>[!NOTE]
128128
>We use the Domain Administrator's username, provided in the User Principal Names (UPN) ([email protected]) format or the domain qualified sam-account name (contoso\johndoe or contoso.com\johndoe) format, to find the intended AD forest. If you use domain qualified sam-account name, we use the domain portion of the username to [locate the Domain Controller of the Domain Administrator using DNS](https://social.technet.microsoft.com/wiki/contents/articles/24457.how-domain-controllers-are-located-in-windows.aspx). If you use UPN instead, we [translate it to a domain qualified sam-account name](https://docs.microsoft.com/windows/desktop/api/ntdsapi/nf-ntdsapi-dscracknamesa) before locating the appropriate Domain Controller.
129+
129130
2. Repeat the preceding step for each Active Directory forest where you want to set up the feature.
130131

131132
### Step 5. Enable the feature on your tenant

0 commit comments

Comments
 (0)