Link to home
Start Free TrialLog in
Avatar of ip_challenge
ip_challenge

asked on

Mapping Drives in Active Directory

I recently made some network changes.  I use Server 2003 with Active Directory. I use a script to map printers and drives.

For some reason members of my administrative group are no longer being mapped.  I have checked there local user profile with the SET command and no longer see the homedrive, home share being mapped.

The strange thing is that if this user logs in to another computer  (roaming profile) the drives and printers are mapped correctly.

Any idea?
Avatar of Point-In-Cyberspace
Point-In-Cyberspace
Flag of Italy image

Try to run the script manually by a command prompt from on one of those computer with the user logged that have troubles.

So you will check if it return errors
Avatar of ip_challenge
ip_challenge

ASKER

I ran the script manually and received a "network path not found".  

It seems that this group has some settings cached on the computer they use daily. The can login any other computer and it will map just fine.

THanks
 
Maybe your script have references to another script or command. Attach your script so we can view it.

If this script is not too long you can try to execute manually one single line at time to locate the issue.


Here is the script

REGEDIT /S \\mv-admin\netlogon\Delete-NetPrinters.REG
wscript.exe \\mv-admin\netlogon\adminprinters.vbs

rem modifies the registry to set the default printer to the the workstation over roaming profiles
rem not using delete statement, office workers are not transient beyond office workstations

net use G: /delete
net use G: \\mv-admin\administration
net use H: /delete
net use H: \\mv-admin\administration\%username%
exit


ASKER CERTIFIED SOLUTION
Avatar of Point-In-Cyberspace
Point-In-Cyberspace
Flag of Italy image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Thanks for the help. The script worked but the DNS record for the domain was missed up. Once the DNS started passing correct information the login worked.