?
=?iso-8859-1?Q?Michael_Sundstr=F6m?=
Hej from Sweden,
We have a Terminal Server running on Windows Server 2003. We locked it down
according to Microsoft white paper how to lock down a Terminal Server.
We configured a kerberos realm with "ksetup" and using kerberos as
authentication method for our users.
Because our user are not placed in the same OU as the Terminal Server we
have enabled "User Group Policy loopback processing mode" and it works
perfectly as long as the users logon to the normal windows domain. But when
the users logon to the kerberos-realm the GPO settings will not be applied.
It seems that the loopback processing mode does not work when logon to the
kerberos-realm.
Does anybody know why there should be such a problem when using GPO and
logon to a kerberos-realm?
Could it be possible that we have to "activate" that the GPO settings also
should work for the kerberos-realm?
Thanks in advance!
/Michael
We have a Terminal Server running on Windows Server 2003. We locked it down
according to Microsoft white paper how to lock down a Terminal Server.
We configured a kerberos realm with "ksetup" and using kerberos as
authentication method for our users.
Because our user are not placed in the same OU as the Terminal Server we
have enabled "User Group Policy loopback processing mode" and it works
perfectly as long as the users logon to the normal windows domain. But when
the users logon to the kerberos-realm the GPO settings will not be applied.
It seems that the loopback processing mode does not work when logon to the
kerberos-realm.
Does anybody know why there should be such a problem when using GPO and
logon to a kerberos-realm?
Could it be possible that we have to "activate" that the GPO settings also
should work for the kerberos-realm?
Thanks in advance!
/Michael