Not sure, but again to harp on the login script issue, why can't all the
clients use the same script? Individual login scripts sounds like a huge
PITA to me - what happens when you need to add a drive mapping or something?
Eeeek!
Re your scheduled task, what happens in W2003 when you try to use it? I've
never tried it, so I have little experience....
Caleb wrote:
> Yes, I could but it would require me to edit all the login
> scripts, which there are a lot. Each client has their own
> unique script. I don't understand why it works in 2000 but
> not 2003.
> Caleb
>
>
>> -----Original Message-----
>> Can you not put the net use to lptx in your login script?
>>
>> Caleb wrote:
>>> In Windows 2000 Server I had a scheduled task that
>>> automatically remapped the printers using the "net use
>>> lpt?? \\server\printer" command after each reboot. Once
>>> mapped the printers were then available to all clients
>>> that logged into the network.
>>>
>>> However, now with Windows 2003 running on a IBM xSeries
>>> 345 Server it looks like I'm going to have to setup each
>>> clients' login to do the mappings so it can print. (Which
>>> I don't want to do.)
>>>
>>> Is there a reason or work around to this? The application
>>> we use references only lpt1/2/3 ports.
>>>
>>> Thanks
>>> Caleb.
>>
>>
>> .
|
Similar Threads
Linear Mode
