GPO Using Startup Script

We have several RDP servers in our environment.  Instead of using traditional log scripts or GPO drive maps for users, we wanted to apply a GPO Startup Script which points to .bat files which provide drive maps to the RDP server and allows all users to access those mapped drives.  We have applied a Startup Script, added the GPO to the OU in AD where the server account resides, and when any of the users log on, the drives do appear but with a big red X and showing disconnected.  However, double clicking on one of the drives that appear as such allows us to browse the contents of the drive. Is there any way to prevent the drives from showing as disconnected. We have granted the Domain Computers group in AD full control of the share on the drives in question but still have the same result.
swlaurieAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
NVITConnect With a Mentor Commented:
In your drive mapping .bat, have you tried to delete the drive before mapping:
net use [drive]: /delete
net use [drive]: \\server\share /user:[user] [password] /persistent:yes

Open in new window

0
 
swlaurieAuthor Commented:
We do have net use [drive]: /delete /yes set in the script.
0
 
NVITCommented:
Various reasons...
- Some network drives show with a red 'X'
- Why some mapped network drives show a red x
- Problem with a red x on mapped drives
http://www.chicagotech.net/mapping.htm
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.