Re: Mapped drives don't connect....
From: Q-Man (anonymous_at_discussions.microsoft.com)
Date: 11/19/03
- Next message: PS: "Re: downloading security patch for Blaster"
- Previous message: jay: "I think I figured this out..."
- In reply to: Torgeir Bakken (MVP): "Re: Mapped drives don't connect...."
- Next in thread: Torgeir Bakken (MVP): "Re: Mapped drives don't connect...."
- Reply: Torgeir Bakken (MVP): "Re: Mapped drives don't connect...."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 19 Nov 2003 13:15:06 -0800
I am not sure what you mean. I have the logon script in a
file that I double clicked once and the mapped drives
always connected after that. Where can I find "Always
wait for the network at computer startup and logon" to
change it so that the Optimization feature is turned off?
>-----Original Message-----
>Q-Man wrote:
>
>> I have a problem. I have an XP client with mapped
network
>> drives to a 2000 server. It will reconnect to the drives
>> after every restart. But when I add a password to the
user
>> account. The user account won't reconnect the drives
>> automatically to the server. I take off the password
>> protection for that user, and then it will reconnect
>> automatically with a restart. I need to protect the User
>> account, but I don't want to have to reconnect each
drive
>> everytime I boot. Is the a problem with XP or is there
>> some way I can fix this? Can anyone help me?
>
>Hi
>
>This might be the cause of it:
>
>Description of the Windows XP Professional Fast Logon
Optimization Feature
>http://support.microsoft.com/default.aspx?scid=kb;EN-
US;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):
>
>By registry edit; Set the value SyncForegroundPolicy to 1
(REG_DWORD) in this
>key:
>
>HKEY_LOCAL_MACHINE\Software
>\Policies\Microsoft\Windows NT
>\CurrentVersion\Winlogon\
>
>Create the necessary keys/value, or put the vbscript
below in a .vbs file and
>double-click on it.
>
>Set oShell = CreateObject("WScript.Shell")
>sRegValue = "HKLM\Software\Policies\Microsoft\Windows
NT\" _
>
& "CurrentVersion\Winlogon\SyncForegroundPolicy"
>
>oShell.RegWrite sRegValue, 1, "REG_DWORD"
>
>MsgBox "Please reboot the computer"
>
>
>Please post back any results :-)
>
>
>--
>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
>
>
>.
>
- Next message: PS: "Re: downloading security patch for Blaster"
- Previous message: jay: "I think I figured this out..."
- In reply to: Torgeir Bakken (MVP): "Re: Mapped drives don't connect...."
- Next in thread: Torgeir Bakken (MVP): "Re: Mapped drives don't connect...."
- Reply: Torgeir Bakken (MVP): "Re: Mapped drives don't connect...."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
