K
Kerry TenHuisen
I have defined a computer GPO with security filtering and it works fine with
systems (XP and W2K) once they reboot. My issue is this ...
If a W2K computer does not reboot, it does not update it's AD group
membership/security group and therefore GPOs using this filter are not
updated.
Is a computer reboot necessary to update it's acknowledgement of its
membership to an AD Security group (Global)? Are there any tools to force
this without a reboot? Neither SECEDIT, nor WINPOLICIES work. They'll
force the GPO, but not update the Security Group membership (from the
client's perspective).
Any Ideas?
Once the GPO is applied, refreshes and updates seem to work fine.
systems (XP and W2K) once they reboot. My issue is this ...
If a W2K computer does not reboot, it does not update it's AD group
membership/security group and therefore GPOs using this filter are not
updated.
Is a computer reboot necessary to update it's acknowledgement of its
membership to an AD Security group (Global)? Are there any tools to force
this without a reboot? Neither SECEDIT, nor WINPOLICIES work. They'll
force the GPO, but not update the Security Group membership (from the
client's perspective).
Any Ideas?
Once the GPO is applied, refreshes and updates seem to work fine.