Re: Standardize drive assignments

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Everybody,



First of all I want to thank to all of you for this support....especially
Al.
I've got my script working and it is like Al said...every time a user is
part of more than one group...he mapped those map drives but ...not all the
time he has the same G:
My next "project" will be to change the script to map G: drive all the time
as a particular net folder and to define a tempgroup and map next available
letter ....
Thanks for ideas folks,

Gabriel





"Al Dunbar" <AlanNOSPAmDrub@xxxxxxxxxxx> wrote in message
news:eGHy15xGGHA.216@xxxxxxxxxxxxxxxxxxxxxxx
>
> "Gabriel Sirbu" <gabonescu@xxxxxxxxxxx> wrote in message
> news:evMfiUhGGHA.208@xxxxxxxxxxxxxxxxxxxxxxx
>> Hello Al,
>>
>>
>> Thanks for your detailed answer.
>>
>> To be honest I've tried to explained what I had on my previous job. An
>> exact script like I've said with this conditional "question" about which
>> drive G: that user should have.
>>
>> Because, at that time, I had a Windows 4.0 environment, and this script
>> was written in Kixstart. What a now is exactly what I said to you...so I
>> think the nesting group condition worked just fine.
>> My struggling is to understand the idea behind this problem in order to
>> replicate the idea again in a different environment.
>> And in my case, we have here 44 teams (each team with 5-7 users) and
>> another 10-12 teams (like Accounting, HR, IT,etc.).
>>
>> I'll attach those files and, please, if you can decipher the functions
>> inside....I'll be the happiest man alive today.
>> I think this nesting group is called LOOPG function inside.
>
> First, I must apologize that I have had some difficulty in understanding
> exactly what you mean by what you have said. Having re-read your second
> last post, I now realize that you intend to map a user's "second" "G:"
> drive share to some available drive letter, presumably "H:". That is
> certainly one way to get around the impossibility of mapping two shares to
> the same drive letter - use a different one.
>
> Forgetting the detailed script you supplied for a moment, answer this
> question: if a person is "in" two different teams for the purposes of
> mapping to the team share, how is it determined which team he actually
> belongs to and which team he is just a "guest" member of? Or does it
> actually matter? In other words, if a person needs to map to more than one
> share normally mapped to "G:", does it matter which one uses drive "G:"?
>
> Now back to the kix script: does this script implement the exact logic
> that you require here? If so, do you plan to implement it in kixtart,
> vbscript, or something else?
>
> You are asking us to first deduce the underlying logic of someone's code,
> however, your status as the happiest man alive would probably also require
> us to pass this understanding along to you as well.
>
> IMHO, it would be better to start with a requirement statement, develop
> the logic, and then do the code. In my experience, trying to adapt code
> one does not fully understand makes the job harder. And if you are
> considering a change to vbscript, the job is even harder because of the
> significant differences in the languages.
>
> As to me understanding the code, I can kind of get an idea by reading it
> quickly, but, not being familiar with that version of kixtart, I feel a
> bit lost. Is enumgroup a supplied function, or is it implemented elsewhere
> in kixtart?
>
> /Al
>
>>
>>
>> Thanks,
>> Gabriel
>>
>>
>>
>>
>>
>> "Al Dunbar" <AlanNOSPAmDrub@xxxxxxxxxxx> wrote in message
>> news:evsd$ufGGHA.1100@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> "Gabriel Sirbu" <gabonescu@xxxxxxxxxxx> wrote in message
>>> news:uMCnxgWGGHA.3056@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Hello everybody,
>>>>
>>>>
>>>>
>>>> Just because Jerold was kind enough to answer to your question, I would
>>>> try to "raise" the complexity of your initial question:
>>>>
>>>> -let's suppose user1 is part of Team1 and he takes G drive (Team 1
>>>> common
>>>> drive) and another 3 other drives ( let's say P: Q: and T:)
>>>> -the same for a second user, named user2: the same letter (for
>>>> uniformity)
>>>> G Drive (Team 2 common drive which is, of course, different form Team
>>>> 1's
>>>> G drive) and the same 3 common drives.
>>>> -so far, so good; but.....user 2 has to cover user 1 for 3 weeks and I
>>>> want this following drives to be mapped: the same 4 drive he always
>>>> have
>>>> (G: for Team 2, P: Q: T:) and "G" drive from Team 1
>>>> which now has to be next available letter after G;
>>>>
>>>> To be more clear it will look like this :
>>>> G drive (Team 2)
>>>> H drive (Team 1) - because covering user 1 makes him part of group Team
>>>> 2
>>>> and Team 1
>>>> P drive
>>>> Q drive
>>>> T drive
>>>>
>>>> My question is how I can write a script/function who can decide to map
>>>> Team drives, based upon group membership
>>>
>>> Before you write the script, you must first decide how it should deal
>>> with
>>> conflicts such as the one you have suggested might happen. I would go
>>> you
>>> one further and suggest that, the more complex set of conditional drive
>>> mappings you happen to have, the more likely this will happen. So, as
>>> you
>>> are considering now, the best thing is to deal with the issue head-on
>>> and up
>>> front.
>>>
>>> IMHO, to have the script decide *which* share to map to G: in this case
>>> should the user happen to be in each "team" means you need to make this
>>> decision first, and then script it. If the "teams" are represented by
>>> security groups, the only way to determine which group the user is only
>>> "acting" in will require additional settings. One way I do this is with
>>> group nesting, i.e.:
>>>
>>> team1 - contains all permanent members of team number one. It also
>>> contains
>>> a group called team1guests.
>>> team1guests - contains anyone being given temporary access to team1
>>> resources.
>>>
>>> So, if a user is a direct member of team1, but only indirect in team2
>>> because he is a member of team2guests, which mapping should he get? Here
>>> you
>>> are stuck, because it must always be one or the other, and cannot be
>>> changed
>>> dynamically depending on the work he is going to be doing once logged
>>> in.
>>> Unless, of course, he uses a team2 computer for team2 work and a team1
>>> computer for team1 work.
>>>
>>> Yes, you could build up this complex (to my way of thinking, too
>>> complex)
>>> hierarchy. But would that serve your users in all cases? Perhaps you can
>>> answer that question but I cannot.
>>>
>>> The way we handle this situation is to avoid conditional drive mappings
>>> like
>>> the plague. One of our standard mapped drives contains workgroup-related
>>> folders that are permitted as appropriate to each group having one. So,
>>> as a
>>> member of team1, I would be able to access whatever was stored in
>>> "G:\team1"
>>> because I am a member of the team1 security group. I'd have no access to
>>> files in "G:\team2" because I am a *not* a member of the team2 security
>>> group, or of team2guests. When a team2 member is away and I am to act in
>>> his
>>> place, I am added to the team2guests group. Now I will see the contents
>>> of
>>> both workgroup folders.
>>>
>>> This can get as complicated as you want, while having absolutely no
>>> impact
>>> on your logon scripting.
>>>
>>> /Al
>>>
>>>> Thanks in advance,
>>>> Gabriel
>>>>
>>>>
>>>>
>>>> "Jerold Schulman" <Jerry@xxxxxxxxxx> wrote in message
>>>> news:6esfs1top7629jbs7hh63rjc8evgkg5aqs@xxxxxxxxxx
>>>>> On Fri, 13 Jan 2006 11:34:45 -0600, "Craig" <msnews@xxxxxx> wrote:
>>>>>
>>>>>>I would like to force all users to a standard drive mapping scheme,
>>>>>>currently there are many varaitions and I would like to force these to
>>>>>>disconnect and assign 6 drive mappings. I am very new this and would
>>>>>>like
>>>>>>if someone could set me in the proper direction. I have basic
>>>>>>programming
>>>>>>and networking skilss in a windows 2003 AD environment.
>>>>>>
>>>>>>Thnk you
>>>>>>
>>>>>>Ciara
>>>>>>
>>>>> In your logon script:
>>>>>
>>>>> net use * /D /Y
>>>>> net use J: \\ServerName\ShareName1 /Persistent:Yes
>>>>> net use K: \\ServerName\ShareName2 /Persistent:Yes
>>>>> net use L: \\ServerName\ShareName3 /Persistent:Yes
>>>>> net use M: \\ServerName\ShareName4 /Persistent:Yes
>>>>> net use N: \\ServerName\ShareName5 /Persistent:Yes
>>>>> net use O: \\ServerName\ShareName6 /Persistent:Yes
>>>>>
>>>>> Jerold Schulman
>>>>> Windows Server MVP
>>>>> JSI, Inc.
>>>>> http://www.jsiinc.com
>>>>> http://www.jsifaq.com
>>>>
>>>>
>>>
>>>
>>
>>
>>
>
>


.

Relevant Pages

  • Re: Script Mapping all Drives
    ... I put the script together quickly, ... trap the error and then remove the existing mapping. ... Should code be added to remove all drives, ... Dim intIndex, objList, objGroup ...
    (microsoft.public.scripting.vbscript)
  • Re: Really stupid mapped drive question
    ... Using the /persistent switch at the same time as mapping drives ... weren't able to map the drive off of the startup script I was using. ... the machines with the problem and machines without the problem is the ...
    (microsoft.public.windowsxp.general)
  • Re: Logon script: Group membership not recognized?
    ... When you run GPResults against these users, does it show them as being a member of this group? ... Speed Group Policy Troubleshooting with the NEW GPHealth Reporter tool at http://www.sdmsoftware.com/products.php ... The script works just ... P drives like it should. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Logon script: Group membership not recognized?
    ... whoami.exe has an option for showing all groups you're a member of. ... The script works just ... P drives like it should. ... Select Case strGroupName ...
    (microsoft.public.windows.server.active_directory)
  • Re: Standardize drive assignments
    ... script like I've said with this conditional "question" about which drive G: ... >> G drive) and the same 3 common drives. ... > team1 - contains all permanent members of team number one. ... > So, if a user is a direct member of team1, but only indirect in team2 ...
    (microsoft.public.windows.server.scripting)