Anonymous_User Absent Member.
Absent Member.
1956 views

login script: F:\ & G:\ Drive Mappings


Howdy,

i have a question about some unwanted Drive mappings.
Client is running 1 Netware 6.5.3 server.

They are in the process of moving their workstations from Windows2000 to
WindowsXP.

Here is the Situtaion:
Currently, When a user logs in on their Windows2000 workstations, they get
a H:\ drive, S:\ drive, and a W:\ drive.
This is how its been for 4+ years now.
Works great.

But, when that same user logs in from a WinXP workstation, they get the 3
drives (H:, S:, W:) but they Also get a F:\ & G:\ drive.
F:\ maps to the TRYFS01:\SYS (volume)
and
G:\ maps to the TRYFS01:\VOL1 (volume).

Where is this F: & G: drivemapping coming from?
(I get these mappings as an Admin, but i do not want the regular users
having these mappings.)

No settings were changed on the server. The Context is the same on the XP
workstations,etc.
So i really dont know why this is happening.
I was thinking about adding that "NO_DEFAULT" setting into the container
where the users are....

But before i do anything crazy, i figured i better ask for some help! = ]

So, does this problem sound familar with anyone else?

Thank you again!

>^^<

Labels (2)
0 Likes
7 Replies
Anonymous_User Absent Member.
Absent Member.

Re: login script: F:\ & G:\ Drive Mappings

Bruce,

> I was thinking about adding that "NO_DEFAULT" setting into the container
> where the users are....


The default logi n script could be causing the mping to the sys volume,
but definitely not to the VOL1. Can you post the login script?

--
Hamish Speirs
Novell Support Forums Volunteer Sysop.

http://haitch.net

(Please, no email unless requested. Unsolicited support emails will
probably be ignored)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: login script: F:\ & G:\ Drive Mappings

Bruce,

> The default logi n script could be causing the mping to the sys volume,
> but definitely not to the VOL1. Can you post the login script?


Just a thought - could there be a login script assigned to an OU
further up the tree ? - We used to update Sophos AV (Win98 days) in a
script assigned to a top level OU.

Maybe its getting from there.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: login script: F:\ & G:\ Drive Mappings

Login scripts are not "cumlitative", if that's what you're suggesting?

--


Peter
eDirectory Rules!
(Site P is here!! http://www.DreamLAN.com/site_p.htm)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: login script: F:\ & G:\ Drive Mappings

Peter,

> Login scripts are not "cumlitative", if that's what you're suggesting?


Hummm. Mine seem to be.

I've certain drive mappings set on some of my user accounts, then a
script assigned to the OU (that the users are in) and finally one
assigned to the top level OU.
They all work fine......



Dave


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: login script: F:\ & G:\ Drive Mappings

You probably have 'include' line in the lower level scripts

Cheers Dave


--
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: login script: F:\ & G:\ Drive Mappings

What the other Dave said ...

--


Peter
eDirectory Rules!
(ssAegis is coming ...)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: login script


Well,
Upon further review.

i discovered that the login script was about 20 lines long!!
It had all kinds of IF's and THEN's (i was quite impressed).

in there, i found that the F:\ & G:\ drive were both explicitly mapped
depending on which group the user belongs to.

So, i modified teh logic, and now it behaves nicely on the XP workstations.

Of course, it doesnt explain why it maps diffreently depending if its
Windows2000 or WinXP...

but we'll deal with it!!

thank you all
>^^<


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.