Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
2851 views

Login Script Runs, No Drives Mapping

In my deployment of Windows 7 in my organization, I'm currently mostly have deployed Client 2 SP1 IR7 with a few IR9a as I'm testing to see whether it fixes the issue that I'm about to describe.

As I said Client 2 SP1 IR7 for Windows 7 seems to be doing the following things quite frequently. When a user signs in the login process goes smoothly and appears to sign you in correctly, but no drive mappings appear under Computer or Explorer. I have been able to use UNC paths and all of the correct folder rights and access are in place. After seeing the lack of drives I can successfully right click the red N, log in again and I'll see drive letters. I can then restart the system a number of times and I will see drive mappings on the initial login for random testings over the next half hour. When the user tries to log in again on the next day, they will once again have the successful login script run but again see no network drives.

I do understand that in running IR7 I may be experiencing some issues that might have been corrected by IR9a but have had a heck of a time trying to plan some time test this on systems that I know regularly experience this trouble. Does anyone know if this is an ongoing issue with the Novell Client for Windows 7 or this has a good chance of being fixed by upgrading to the newer IR release? Thanks!
Labels (1)
0 Likes
6 Replies
Micro Focus Expert
Micro Focus Expert

When the Issue happens............

Shell out to the CMD prompt and type "NET USE" to see if the drives are
mapped there.........

Also open a Program such as "Notepad" and see if you can see the Drives
there...........

I know, Sounds Weird, but there is a known issue being investigated
where the Drives actually map successfully and are available just about
everywhere EXCEPT Windows Explore.exe. Restarting Explore.exe brings
them back, but that is not ideal to say the least 😆

On 11/28/2011 3:56 PM, marklar23 wrote:
>
> In my deployment of Windows 7 in my organization, I'm currently mostly
> have deployed Client 2 SP1 IR7 with a few IR9a as I'm testing to see
> whether it fixes the issue that I'm about to describe.
>
> As I said Client 2 SP1 IR7 for Windows 7 seems to be doing the
> following things quite frequently. When a user signs in the login
> process goes smoothly and appears to sign you in correctly, but no drive
> mappings appear under Computer or Explorer. I have been able to use UNC
> paths and all of the correct folder rights and access are in place.
> After seeing the lack of drives I can successfully right click the red
> N, log in again and I'll see drive letters. I can then restart the
> system a number of times and I will see drive mappings on the initial
> login for random testings over the next half hour. When the user tries
> to log in again on the next day, they will once again have the
> successful login script run but again see no network drives.
>
> I do understand that in running IR7 I may be experiencing some issues
> that might have been corrected by IR9a but have had a heck of a time
> trying to plan some time test this on systems that I know regularly
> experience this trouble. Does anyone know if this is an ongoing issue
> with the Novell Client for Windows 7 or this has a good chance of being
> fixed by upgrading to the newer IR release? Thanks!
>
>



--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.
--
Please give a hearty thumbs up to any post you find helpful!
To find articles by Craig Wilson simply follow the link: Craig Wilson's Tips!
0 Likes
Absent Member.
Absent Member.

craig wilson wrote:

> I know, Sounds Weird, but there is a known issue being investigated
> where the Drives actually map successfully and are available just
> about everywhere EXCEPT Windows Explore.exe. Restarting Explore.exe
> brings them back, but that is not ideal to say the least 😆


I workaround now is to set the group policy option for login scripts to
run synchronously. This way explorer doesn't initialize until the
login script finishes processing. I seem to remember a certain someone
recommending this tip. 🙂

--
Novell Knowledge Partner
Enhancement Requests: http://www.novell.com/rms

Joe Marton Emeritus Knowledge Partner
0 Likes
Absent Member.
Absent Member.

There's a fix in this area in the new Client 2 SP2, released today - give it a shot, I'd say.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
Absent Member.
Absent Member.

On 28.11.2011 22:56, marklar23 wrote:
>
> In my deployment of Windows 7 in my organization, I'm currently mostly
> have deployed Client 2 SP1 IR7 with a few IR9a as I'm testing to see
> whether it fixes the issue that I'm about to describe.
>
> As I said Client 2 SP1 IR7 for Windows 7 seems to be doing the
> following things quite frequently. When a user signs in the login
> process goes smoothly and appears to sign you in correctly, but no drive
> mappings appear under Computer or Explorer.


Try different settings for Network Provider Order settings, that has
helped in our case.

and/or try latest client.

-sk

HAMK University - OES, NW, GW, NCS, eDir, Zen, IDM, NSL - www.hamk.fi
0 Likes
Absent Member.
Absent Member.

I overcame similar problems by referencing the server by IP address in the advanced settings of the client and putting the server IP address in the hosts file.
0 Likes
Absent Member.
Absent Member.

Hi, I have this problem after upgrading to SP2. I am logged in, but there are no network drives. I tried to change group policy settings, but no effect. I can run loginw32.exe and then are drives in login script mapped. But primary login after system start is not working. 😞
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.