Login Scripts with workstations at a remote site

We have a remote location that is connected to our home location via a VPN tunnel.  The remote computers can ping the servers on the other end and can manually map network drives.  We changed to login script because we moved a server and the login script for the remote computers is not updating.  It still points to the old server.  All of the login scripts for the users at our home location work perfect.

Any suggestions?
jrhundsrAsked:
Who is Participating?
 
Ben Personick (Previously QCubed)Connect With a Mentor Lead Network EngineerCommented:
Is the server you moved a Domain controller?

Can you put a DC at the remote site (This is best practice, and highly advisable for any site with more than a hand-full of employees)?

Can you see which Domain Controller is listed as their logon Domain controller?

What is the latency and bandwidth of this wan link?
0
 
Gianpiero RossiSystem AdministratorCommented:
hello,
if you try to access from the remote client to \\server\netlogon do you see the script?
so, try to put in the user configuration script the complete path of the scrpt \\server\netlogon\script
0
 
Will SzymkowskiSenior Solution ArchitectCommented:
How are you deploying this script, GPO, home folder (ADUC)? If you are using GPO to push this logon script make sure that it is applying to the machines correctly. You can use rsop.msc to see if they policy is applying correctly to the machines.
0
 
Ben Personick (Previously QCubed)Lead Network EngineerCommented:
Where is the DC which is servicing this remote site? (I'm hoping you'll say it's on-site)

  Have you checked to ensure it has properly replicated the changed script and any other changed settings?  It sounds liek the issue may be that the files and settings are not properly replicating between domain controllers or just taking a long time to get there.

If your users are authenticating through the VPN that may itself be your problem, try sticking a Domain controller at the remote site. ^^

~Q
0
 
jrhundsrAuthor Commented:
The DC is not at the remote site, it is at the home site.  In each users' AD account, under profile settings, the login script is defined.  The scripts are in the default location.  The home users are pointed to the updated server, but the remote users still have not received these changes.  
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.