J
just say NO to PDF
No go - see comments below...
Hey, Thanks Torgier - it's an interesting angle...but no cigar.
I used MMC/Group Policy/Local Computer to set the local policy,
but after reading the KB article and running on my system, I think this
applies to how GP and logon scripts are processed. NOT mapped drives.
I am still not prompted for username/password for these mapped drives that
"Connect using a different user name"
I still get the idiot balloon instead.
Someone suggested that "this is probably because your mapped drives
require different user account than the one you logon with"
....that is *exactly* the reason.
Anyone else know how to change back the behaviour?
TIA
-- Maarten
Torgeir Bakken (MVP) said:Hi
This might be the cause of it:
Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?kbid=305293
<quote>
By default in Windows XP Professional, the Fast Logon Optimization feature
is set for both domain and workgroup members. As a result, Windows XP does
not wait for the network to be fully initialized at startup and logon.
</quote>
To disable this and see if it helps on your problem, try to set the
"Always wait for the network at computer startup and logon" policy
(a negative side effect is that it might make the startup/logon to
take longer time):
Test it on a couple of computers first ...
snip 8x-------------------------------------
torgeir
Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of the 1328 page
Scripting Guide: http://www.microsoft.com/technet/scriptcenter
Hey, Thanks Torgier - it's an interesting angle...but no cigar.
I used MMC/Group Policy/Local Computer to set the local policy,
but after reading the KB article and running on my system, I think this
applies to how GP and logon scripts are processed. NOT mapped drives.
I am still not prompted for username/password for these mapped drives that
"Connect using a different user name"
I still get the idiot balloon instead.
Someone suggested that "this is probably because your mapped drives
require different user account than the one you logon with"
....that is *exactly* the reason.
Anyone else know how to change back the behaviour?
TIA
-- Maarten