Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
| 72:autologin_system_requirements [2018/07/06 16:04] – [Autologin System Requirements] bkkr | 72:autologin_system_requirements [2018/07/06 16:05] – [Autologin System Requirements] bkkr | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| === Client PC === | === Client PC === | ||
| - | * | + | * The Client PC has to be a member of the Kerberos realm. Using Microsoft Active Directory, the name of the realm usually corresponds to the name of the Active Directory domain in capital letters. Example: if the company’s Active Directory domain name is “abc.com”, |
| - | + | * Auto-login will only be possible for users who log into the client PC using an Active Directory domain account. Local user accounts are not suitable for the autologin-feature as user authentication is handled by Kerberos only. | |
| - | The Client PC has to be a member of the Kerberos realm. Using Microsoft Active Directory, the name of the realm usually corresponds to the name of the Active Directory domain in capital letters. Example: if the company’s Active Directory domain name is “abc.com”, | + | |
| - | + | ||
| - | * | + | |
| - | + | ||
| - | Auto-login will only be possible for users who log into the client PC using an Active Directory domain account. Local user accounts are not suitable for the autologin-feature as user authentication is handled by Kerberos only. | + | |
| === Internet Browser === | === Internet Browser === | ||
| Line 19: | Line 14: | ||
| === Network Configuration === | === Network Configuration === | ||
| - | * | + | * Time has to be synchronized within the Active Directory Domain (clients and servers) as well as between the Stages server and the Active Directory domain because every Kerberos ticket has limited validity. |
| - | + | * It is also of critical importance that your name service is set up correctly. For each device the name service resolution has to work both ways, forward and backwards. Forward resolution resolves a full-qualified domain name to an IP address and backwards resolution resolves the IP address back to the full-qualified domain name. Resolving a hostname to an IP address and the address back to the hostname again, has to result in the same full qualified hostname. | |
| - | Time has to be synchronized within the Active Directory Domain (clients and servers) as well as between the Stages server and the Active Directory domain because every Kerberos ticket has limited validity. | + | |
| - | + | ||
| - | * | + | |
| - | + | ||
| - | It is also of critical importance that your name service is set up correctly. For each device the name service resolution has to work both ways, forward and backwards. Forward resolution resolves a full-qualified domain name to an IP address and backwards resolution resolves the IP address back to the full-qualified domain name. Resolving a hostname to an IP address and the address back to the hostname again, has to result in the same full qualified hostname. | + | |
| === Stages Server === | === Stages Server === | ||