A
auxvivrespos@gmail.com
Guest
I'm currently administering a touchscreen workstation running win2k,
that operates without a keyboard and operates on a win2k-based
domain. Since there is no keyboard, the workstation is configured to
log on to the network domain automatically.
This particular workstation is using a usb-based network interface
card. The network adapter is a Linksys USB200M. Because this adapter
is usb-based its drivers seem to either take longer to load or are
loaded later in the bootup process. This creates a problem whereby
the Winlogon process attempts to automatically log on to the domain
controller, and retrieve its roaming user profile BEFORE the network
adapter has finished loading. Consequently, windows reports that it
cannot retrieve the roaming user profile from the network share and
reverts to a locally cached copy.
I would like to ensure that the network adapter's drivers have
finished loading before WinLogon initiates the logon process. I have
come across two links which seem to suggest this is possible:
http://support.microsoft.com/default.aspx?scid=kb;[LN];193888
http://support.microsoft.com/default.aspx?scid=kb;[LN];115486
The first link in particular describes what I think is the the best
solution: Making the WinLogon service dependent on the network
adapter's device driver. In this case the logon would begin only
after the device driver has loaded.
I would like to try to create such a dependency by modifying the
appropriate registry keys but I need to know what system service is in
charge of WinLogon? I have found a "Netlogon" service but nothing
which is explicitly labelled as "WinLogon"
that operates without a keyboard and operates on a win2k-based
domain. Since there is no keyboard, the workstation is configured to
log on to the network domain automatically.
This particular workstation is using a usb-based network interface
card. The network adapter is a Linksys USB200M. Because this adapter
is usb-based its drivers seem to either take longer to load or are
loaded later in the bootup process. This creates a problem whereby
the Winlogon process attempts to automatically log on to the domain
controller, and retrieve its roaming user profile BEFORE the network
adapter has finished loading. Consequently, windows reports that it
cannot retrieve the roaming user profile from the network share and
reverts to a locally cached copy.
I would like to ensure that the network adapter's drivers have
finished loading before WinLogon initiates the logon process. I have
come across two links which seem to suggest this is possible:
http://support.microsoft.com/default.aspx?scid=kb;[LN];193888
http://support.microsoft.com/default.aspx?scid=kb;[LN];115486
The first link in particular describes what I think is the the best
solution: Making the WinLogon service dependent on the network
adapter's device driver. In this case the logon would begin only
after the device driver has loaded.
I would like to try to create such a dependency by modifying the
appropriate registry keys but I need to know what system service is in
charge of WinLogon? I have found a "Netlogon" service but nothing
which is explicitly labelled as "WinLogon"