That's a good question, and group policies are updated at intervals as you
say (or can be forced with gpupdate). My reasoning is that the domain
controllers recognize the computers when they start up and policies like
software installations always seem to require a reboot of the workstation to
take place - now this is in my experience and I don't claim to be any kind
of expert on this - especially when it comes to remote computers. I'm still
waiting for someone with more remote users to add their 2 cents.
....kurt
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> If that is the case, why would you ever use "gpupdate" or "gpupdate
> /force" to manually refresh policies? If they only truly get applied
> at startup (computer policies) or logon (user policies), it would seem
> that "gpupdate" is a tool that would never be used.
>
> I appreciate your assistance in helping me understand this. Thanks
> again.
>
> -george
>
>
>
> Kurt wrote:
>> You really don't need a book, it's pretty straightforward. Computer
>> policies
>> apply when the computer starts up, so I don't believe those policies can
>> be
>> applied to remotes (you might check on that or maybe someone with more
>> remote experience will weigh in). User policies apply when the user logs
>> into the domain. Logging into a RRAS server, even with domain
>> credentials,
>> is not the same as a domain logon. That's why the VPN must be up first
>> before the user logs in. Otherwise they're getting in with cached
>> credentials or logging into their local computer.
>>
>> ...kurt
>>
>> <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> > Thank you for the reply.
>> >
>> > I guess that is part of my question. Is there any documentation as to
>> > which policies get applied only on user logon and which policies can
>> > get applied after logon either through normal refresh procedures and/or
>> > "gpupdate" ?
>> >
>> > Thanks again for your input.
>> >
>> > -george
>> >
>
|