[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 207
  • Last Modified:

Windows 7 45 users 1 machine different drive mappings

I have a client where they have  about 45 users that at any point can log in from a shared conf room pc to execute a login script

I am not sure if there is any limitation to the # of local profiles, but not all drive mappings from the prior user are always deleted/disconnected cleanly.

Anyone have any suggestions as to how they handled something like this? RDP would be troublesome.

I could just make one user for each department so we have only a handful of profiles?
Is there a limit to the # of profiles on a Win 7 machine? I just dont think it would be a great idea to have 45+ local profiles on a win 7 machine.

Thanks!
0
LICOMPGUY
Asked:
LICOMPGUY
2 Solutions
 
Cliff GaliherCommented:
I've done a few large scale point-of-sale systems that have many more users than what you are dealing with. Honestly 45 is a relatively small user count and windows can easily handle that (not concurrently, of course.)

 As far as drive mappings, you must have something else going on. In a normal setup, drive maps are stored as a user setting in the user's registry. Which means another user does not have those same mappings (even if they didn't unmap cleanly at log-off.)  Like many other user settings, my default printer can be different than another user's, whether I set my mouse up to be left-handed while another user's is right handed, desktop wallpapers, etc. When one user changes their wallpaper, it doesn't change it for other users. Well, drive mappings work the same way. They are intrinsically per-user by default. There are ways around that, but that would then be an issue with the login script, not with Windows or the number of local profiles.
0
 
John HurstBusiness Consultant (Owner)Commented:
The way I would manage this is by a connection script. Set one up and delete the map before creating it.

NET USE Z: /Delete
NET USE Z: \\server\share

This permits always being able to map a folder.

Set up a script for each user.

I would expect a computer to drag with 45 profiles because of temp files and indexing. Also OST files if an Exchange setup.
0
 
LICOMPGUYAuthor Commented:
Guys

Thanks for the responses. So are you saying directly before the net use to map, the line prior should just be a net use z: /delete and that will always clear it out for the net use map to the share?

Thanks!
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 
John HurstBusiness Consultant (Owner)Commented:
the line prior should just be a net use z: /delete and that will always clear it out for the net use map to the share?   <--- Yes
0
 
LICOMPGUYAuthor Commented:
Ok - so every line for a net use to execute a drive mapping, immediately before should use the /delete - correct?

You have done this before and don't see any problem with 45 or so users having a local profile?

I thought I tried this once before and felt it executed so fast that it didn't do the delete consistently.
Have you seen this occur?
Thanks so much
0
 
John HurstBusiness Consultant (Owner)Commented:
so every line for a net use to execute a drive mapping, immediately before should use the /delete - correct?  <-- I would. The purpose is to prevent persistent drives using the drive letter you are trying to map.

I see a dozen users on a computer. I have not had 45 users.
0
 
LICOMPGUYAuthor Commented:
Hey John

What seemed to work and the DC is Win2k12, was using the net use * /delete /yes.

The only issue(which I have to test again, is it seemed to delete their home dir mappings which is obtained thru their profile,
so I commented it out until later when I can go back on site.
Would that make sense that it would remove that? If so  - any thoughts on how I could prevent that?
I am guessing that the login script executes after the profile maps the user home dir.
Thanks again!
0
 
John HurstBusiness Consultant (Owner)Commented:
I am guessing that the login script executes after the profile maps the user home dir

I would consolidate the mappings so that you can delete by folder mapped before mapping. The only reason for doing this is to prevent persistent mappings from preventing a new map.

Consolidating mappings into one script will solve the problem.

Otherwise, limit the delete statements to the folders in the script and do not delete other mappings.
0
 
LICOMPGUYAuthor Commented:
Hey there

THanks for your help
Can you see any issue if I were to just list out the "NET USE Z: /Delete,  at the beginning of the loginscript, replacing z with all possible drive mapping letters and have the net use delete run for each letter whether or not the user has that drive mapping or not?  Do you think that would slow down the execution of the loginscript or cause it to hang?

Thanks
0
 
John HurstBusiness Consultant (Owner)Commented:
Deleting a mapped drive before mapping again does not slow anything down. Has not for me in years of use.
0
 
LeeTutorretiredCommented:
I've requested that this question be deleted for the following reason:

Not enough information to confirm an answer.
0
 
John HurstBusiness Consultant (Owner)Commented:
I think we answered this question very well.

I suggest split:   http:#a40617655  and http:#a40617654
0
 
LICOMPGUYAuthor Commented:
All worked out perfectly!

I did a NET USE "n": /Delete at beginning of the scripts so it cleared all - it looks like we are good, Thank you - you were a huge help!!
0
 
John HurstBusiness Consultant (Owner)Commented:
@LICOMPGUY - If we helped you out and solved your issue, then you should close the question properly instead of abandoning the question.
0

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now