Problem with GPO's

[Guest]

After the migration of a customer we are having problems with GPO's on
some/most of the clients. Here some background information:

- migration from a multi-domain W2k forest to a single-domain W2k3 forest
- migration was done with ADMT v3
- the GPO's were newly created in the new domain (no migration)
- the GPO has standard permissions

This is what happends:

- when a user logs on the policy in question (linked to the AD-Site and only
has proxy configuration information in it) is not used. (Interesting enough
when looking at GP-Result in GPMC I can see that the GPO is either not shown
or is not applyed because it is supposed to be empty...)
- when a administrative user logs on the GPO is applyed... (?) (The
administrative user is NOT member of the Domain Admins and the group does not
have any permission in the GPO)

Any input would be welcome!

Gerrit Deike
MCT, MCSA, MCSE

 

[Og]

After the migration of a customer we are having problems with GPO's on
some/most of the clients. Here some background information:

- migration from a multi-domain W2k forest to a single-domain W2k3 forest
- migration was done with ADMT v3
- the GPO's were newly created in the new domain (no migration)
- the GPO has standard permissions

This is what happends:

- when a user logs on the policy in question (linked to the AD-Site and
only
has proxy configuration information in it) is not used. (Interesting
enough
when looking at GP-Result in GPMC I can see that the GPO is either not
shown
or is not applyed because it is supposed to be empty...)
- when a administrative user logs on the GPO is applyed... (?) (The
administrative user is NOT member of the Domain Admins and the group does
not
have any permission in the GPO)

Any input would be welcome!

Gerrit Deike
MCT, MCSA, MCSE

Input:
1. You have posted a _server_ issue to a _workstation_ newsgroup,
which greatly diminishes you chance of obtaining a useful response.
2. Have you considered posting your GPO problem to a newsgroup
populated with GPO gurus?
microsoft.public.windows.group_policy
Steve

 

[Guest]

Well actually it is a client problem. Since I've posted it I've been able to
locate the origin of the problem. The kerberos token size is to small. The
problem is that XP wont change the size eventhough I've changed the value of
"MaxTokenSize" in the registry...