>
> "Dave" <junk[ at ]junkmail.com> wrote in message
> news:82810B44-B098-4F0A-A103-3B4D7A78302F[ at ]microsoft.com...
>> On our computers we have drives that are for things like looking up
>> parts, Application Updates, Public Folders, and some others. My problem
>> is that I see no reason on certain folders such as Public Folders why if
>> I only need a certain portion of the drive why I must drill down 5 lays
>> everytime to get to the portion that pertains to me,
>
> A good point. Personally, I would create shortcuts to the folders I need
> to access frequently.
>
>> Also if I don't work in a certain area of the plant why need I look at
>> the Parts directories for the other areas?
>
> Shortcuts again can help you get past the stuff you don't need. You don't
> have to look at everything that is present in the standard mapped drives
> just because it is there.
>
>> While I understand that it would be very difficult to the IT department
>> being (EDS) to keep track of the area all 1000 employees work in, why
>> can't I get rid of those and keep only the one's that pertain to me.
>
> I don't know the specific technical policies that might be in effect, and
> I do not know the reason for them in the caes of your department. But just
> because you and I don't understand why does not mean there is no valid
> reason. That's one reason why there are IT staff and contractors - to
> understand and look after the technical bits that would be even less
> important to you than the parts directories of other areas.
>
>> Probably the worst thing about it to me is that I must look at the UNC
>> rather than a name that is easy to glance and click on what I want rather
>> than look at the entire UNC. All I want to do is rename them to a
>> sensible name for my own viewing.
>
> Again I'll say it: shortcuts. Once you have opened an explorer window on a
> deeply nested folder located in an obtusely named share, is there any
> reason why a very long path in the address bar should be a problem?
>
>> I also want to create my own, but I am unable to create a share on our
>> public drive so when I create my own drive the UNC winds up being very
>> long making it even more tedious to look at instead of simpifying things.
>>
>> I figured that if I can manually rename the drives (right click ->
>> rename) I should also be able to do it programmatically, via my own login
>> script that I would put into the Startup Folder.
>>
>> Any help would be appreciated.
>
> This may indeed be doable; I have never bothered looking into this as it
> always seemed mainly an esthetic thing to me.
>
> If your IT support were actually there to assist staff with using the
> equipment effectively, they might actually have some suggestions for you
> that would meet your needs without interfering with what they do, and
> without requiring you, and end-user, to take on scripting because it seems
> the only way for you to make your desktop work effectively for you. Given
> that IT support is out-sourced to EDS, however, this may not be an option
> for you.
>
> But, if your preference is towards mapping drive letter, have you tried
> the subst command?
>
> subst Q: C:\rootfolder\folder1\folder2\folder3\folder4\folder5\folder5
>
> This creates a "virtual drive" that points to the folder specified. It
> appears that the folder can be a UNC, or a folder in a mapped drive.
>
> If there are enough unused drive letters for your purposes after the
> standard mappings are setup, you could replace your vbscript with a simple
> batch file that uses subst to make the needed connections. Give it a try
> and let us know how it goes.
>
> /Al
>
>>
>> Dave Marden
>>
>> "Al Dunbar" <AlanDrub[ at ]hotmail.com.nospaam> wrote in message
>> news:%23g%23%23a25tHHA.4612[ at ]TK2MSFTNGP04.phx.gbl...
>>>
>>> "Dana" <raff242[ at ]yahoo.com> wrote in message
>>> news:755cb$467f0327$944e306e$30852[ at ]STARBAND.NET...
>>>>
>>>> "Al Dunbar" <AlanDrub[ at ]hotmail.com.nospaam> wrote in message
>>>> news:uem4CErtHHA.4424[ at ]TK2MSFTNGP04.phx.gbl...
>>>>>
>>>>> "Dave" <junk[ at ]junkmail.com> wrote in message
>>>>> news:B34ACF35-C2AA-424A-96C2-55F08D70F8CD[ at ]microsoft.com...
>>>>>>I have created a login script to add to the existing login script our
>>>>>>system admin created at work,
>>>>>
>>>>> As a system admin that has developed company-wide logon scripts, it
>>>>> sound more as if your script subtracts from the official one... ;-)
>>>>
>>>> Ah, you sound like another windows admin Nazi :)
>>>
>>> At first I wasn't going to respond thinking you had invoked Godwin. Now
>>> I see that you didn't mention the dreaded Mr. H.
>>>
>>>>>> I have put a .bat file in my startup folder, and used the bat file
>>>>>> to delete all existing network drives, next the .bat file runs
>>>>>> "wscript rename.vbs". This file simply recreates the network drives
>>>>>> I use
>>>>>
>>>>> One day you may find that some of the underlying shares no longer
>>>>> exist. Perhaps the name has been changed, or they have moved to a new
>>>>> server. Those happy enough with the official mappings (which will have
>>>>> been adjusted) will continue to work as per usual, while you will have
>>>>> to spend time adapting your scripts to compensate for the problem.
>>>>
>>>> Mr Negativity :)
>>>
>>> Not so. Just laying out some scenarios that the OP might not have
>>> considered.
>>>
>>> <snip>
>>>
>>>>>> I thought maybe it was because of it being /persistent but if I
>>>>>> manually rename the network drives in "My Computer" at work this
>>>>>> doesn't happen. Even if they have a GPO that disallows me from doing
>>>>>> this then why would I be able to rename the drives manually at work
>>>>>> and it works?
>>>>>
>>>>> Why not ask them that very question? You might find that there are
>>>>> reasons why things are as they are. Or, perhaps, they will suggest
>>>>> alternative options for accomplishing what it is you feel you actually
>>>>> require.
>>>>
>>>> Most window admin types tend to harm productivity of the workers, as
>>>> they place unneeded restrictions on the system.
>>>
>>> We could argue about which restrictions are necessary and which are not.
>>> In the meantime our users are much happier with a somewhat locked-down
>>> Windows XP image than they were with a wide open Windows 98 that was
>>> constantly crashing on them because of the unneeded variations users
>>> tried out.
>>>
>>> /Al
>>>
>>>
>>
>
>