Remote users are controlled by remote access policies, not group
policies.
Making a VPN connection is not a logon operation. It simply sets up an
IP connection. The client does not even need to belong to the domain. All
that is required is that the user has dialup access rights.
The only way to force a remote user to do a domain login is to use the
"login using a dialup connection" option in the client's logon dialog box.
(E-Mail Removed) wrote:
> I was hoping somebody could help me with a Group Policy problem I am
> having. I want to publish an application in AD. For users on my LAN,
> everything works fine. But the application does not show up for my
> remote users.
>
> I have created a GPO with a Software Installation Publication under
> "User Configuration". I've linked the GPO to an OU with the users I
> want to apply this to. When a user on my LAN logs in and goes to
> Add/Remove Programs, the application (Office 2003) appears in the "Add
> Programs From Your Network" list. But it does not appear for my
> remote users.
>
> Remote users log in using cached credentials, and then connect to the
> network via VPN. I have had them run "gpupdate" to force a refresh of
> Group Policy. I then run "gpresult" to confirm that they have been
> refreshed. Under the results for "gpresult" I see the linked GPO
> under "Applied Group Policy Objects" for User Settings. I have
> waited the 90 + 30 minutes just to see if it would show up by itself
> under normal refresh intervals with no luck.
>
> The clients are both Windows 2000 and XP Professional. The domain is
> Windows 2003 running in mixed mode.
>
> Does anyone out there have any ideas of what I'm doing wrong? I
> appreciate any assitance that can be provided. Thank you.
>
> ----
Similar Threads
Linear Mode
