General discussion

Locked

Novell to NT migration changes

By yisrael ·
We have an almost pure win95/98 desktop enviroment. A couple of months ago I migrated from Netware 3.12 to NT 4.0. The Netware server was retired. I found a few strange things with the NT changeover:

Creating a home directory: WinNT enviroment variables don't work with win9x. I had to share the users home directory and manually go to each machine to map a home directory to the users share. Is there any better way to map a users home directory with logon scripts? To create a seperate logon script for each user is as tedious as manually mapping directories with the GUI.

Visible directories: Another thing that was strange was that in Novell when a user has no rights on a certain share, they don't see it. This deters the curious pest - why show someone something they can't use? With NT any share is visible to everyone. I tried using hidden shares but it didn't seem to work properly. Please advise.

This conversation is currently closed to new comments.

14 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Novell to NT migration changes

by yisrael In reply to Novell to NT migration ch ...

Point value changed by question poster.

Collapse -

Novell to NT migration changes

by dheupel In reply to Novell to NT migration ch ...

In creating a home directory, user profiles can help you with this. You can also use the NET USE command in the login script. In your global login script, make use of the %USERNAME% environment variable, i.e.:

NET USE H: \\<servername>\USERS\%USERNAME%

Yes, when you share a folder on a server, it will be visible when user's browse the network - however, if they do not have permissions to the folders' contents, then they will not see the contents. If they try to browse the folder, they will either see Zero Objects, or get an Access Denied dialog. Remember, in Windows NT 4, security in a directory structure follows the most restrictive permissions granted within the structure.

Collapse -

Novell to NT migration changes

by yisrael In reply to Novell to NT migration ch ...

I new all of that. What I am looking for is if you know of a tool to have NT enviroment variables work with win 9x.

Secondly, I want to know of a tool to hide the shared resource from the browse list. I understand that the user who has no rightsto use it will not be able to access the resource, but why should I entice him to try to use it?

Collapse -

Novell to NT migration changes

by yisrael In reply to Novell to NT migration ch ...

Point value changed by question poster.

Collapse -

Novell to NT migration changes

by dheupel In reply to Novell to NT migration ch ...

Since an environment variable is local to a specific computer, I don't know of a way or a software tool to allow a computer to "share" an environment variable - however, I'm not sure why you would want to. If you have your logon script running on the server in \\<sn>\NETLOGON\SCRIPTS\EXPORT\LOGON.BAT for example, the %USERNAME% variable should do everything you need it to.

I understand your desire to make shares hidden from users that don't have rights to them to reduce the "temptation factor". You might be able to find what you're looking for in System/User Policies, and configure a policy for your users with Policy Editor.

You'll have to forgive me, I haven't been around an NT network that uses policies for a couple of years, so I'm a little rusty on this. You might also find some useful info in the NT Resource Kit.

Collapse -

Novell to NT migration changes

by yisrael In reply to Novell to NT migration ch ...

Firstly, thank you for trying to help me. I understand that you may be frustrated that I keep on rating these answers unacceptable.

The first issue at hand is to map a drive to the user's home directory. I have been unable to map the directory because the win 9x client doesn't know what to do - it can't recognize the enviroment variable of %username%. Here is my script in the logon.bat:

net use u:\\<servername>\users\%username%

This did not work with win 9x clients. I had to share the home directories and map through the GUI. I know that this is lousy, but I couldn't get the win 9x client to figure out what %username% means. I am sure that I am not the first one to come up with this problem.

And as far as the "temptation factor" - to the best of my knowledge (which I admit may not be the best) there is nothing in the system policy editor to remove the restricted directories from the browse list.

As far as the resource kit - if you could direct me to an exact program that deals with this, I'd be extremely appreciative.

Thank you.

P.S. Both of these problems didn't exist with our old Netware server - this is why it is important to me to try to solve these problems.

Collapse -

Novell to NT migration changes

by dheupel In reply to Novell to NT migration ch ...

Make sure there is a space between the colon of the drive letter you want to use, and the UNC name of the share on the server, like so:

net use u: \\<servername>\users\%username%

otherwise, your script will error, and the drive will not get mapped. If you still have a problem, let me know because we'll have to start looking elsewhere (like permissions). Keep in mind, that you will have to have the folder already created on the server for the user, and in User Manger, the home folder path should be set as \\<sn>\path(users)\%username% as well. Since the login script is being called from the server, Windows 98 does know what the %username% variable means. Check the syntax.

Yes, NT is much different than NetWare as far as user rights/permissions are concerned. Check this web page for some info on browsing, and hiding drives/shares in Explorer or Network Neighborhood. You can do it with user profiles and system policies.

http://msdn.microsoft.com/library/winresource/dnwin95/S6FEB.HTM

I'm goin' for the points - YEEHAA!

Good luck!

Collapse -

Novell to NT migration changes

by yisrael In reply to Novell to NT migration ch ...

Since I have my bait for the points...

As far as the syntax, I have to check it out. When I tried it earlier, it didn't work with the proper syntax (including the space). What you are saying is that it should be able to understand the NT enviroment variable on the server.

What could be the permissions problem? I think that is the problem we may be dealing with. Please advise.

Secondly, the web page you sent me to doesn't exist - or at least I couldn't get there. The page has expired.

I'm rooting for you!!!

Thanks for all the help......

Collapse -

Novell to NT migration changes

by dheupel In reply to Novell to NT migration ch ...

OK, try this link - I don't know how that space got in there. There are no spaces in the hyperlink, and watch out for it may wrap in your browser window.

http://msdn.microsoft.com/library/winresource/dnwin95/S6FEB.HTM

OK, remember that Windows NT Server is different than NetWare in the fact that in NetWare, you can share directories, but if users don't have rights to them, they will not see them when browsing. In Windows NT, everyone will see the share, but cannot see it's contents if the permissions do not exist. Also, directory security in Windows NT follows the MOST RESTRICTIVE permissions set within a directory hierarchy.

For example, you have a global group Admins, and a global group Users, and you have a share called Share. You give the Users and Admins groups full permissions to the folder Share, and then you create sub-folders underneath Share, one called Marketing, and one called Finance, for example. Then, you create two new groups called Marketing and Finance,which are also members of the global Users group. OK, now you assign permissions to Share\Marketing to the Marketing group, and assign permissions to Share\Finance to the Finance group. In this scenario, users assigned to the Marketing group should be able to access Share\Marketing, and can see Share\Finance, but cannot access the contents of Share\Finance; conversely users in the Finance group should be able to access Share\Finance, and can see, but not access the contents of Share\Marketing- not unless you give permissions to the individual user account. By using user profiles and system policies, you can "hide" the shares that users/groups don't have sufficient permissions to see.

Good luck - and feel free to e-mail me direct.

Collapse -

Novell to NT migration changes

by dheupel In reply to Novell to NT migration ch ...

I need to follow up on the above, as I thought I might be running out of room. Anyway, give the scenario above, also, the Admins group would be able to see the contents of Share\Marketing, AND Share\Finance, because the MOST RESTRICTIVE permissionsset for the Admins Global Group exist on Share. The most restrictive permissions for the group Marketing exist on Share\Marketing. I hope you see where I'm going with this...

And, now, come to think of it, I think if you assign "No access" permissions to a group on a share (or folder underneath), then users within the group, they will not be able to see the share or folder - so give that a try.

Back to Windows Forum
14 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums