Slow Logon and Drive Mapping

  • Thread starter Thread starter dave Admin
  • Start date Start date
D

dave Admin

We have been migrating from Netware to MS Server 2003, SP1. All
workstations are XP, SP2.

With Netware, all drive mappings are completed before the user can access
any application.

With Microsoft, the user logs on and immediately attempts to open Outlook,
the .pst file being on a server. Since Microsoft takes about 30-45 seconds
to map the drives AFTER the user is logged in, Outlook can't find the mapped
drive and creates a pst file on the local c:\ drive. Of course the user has
no idea where their mail went and it takes about 5 minutes to reset the pst
file and import from the local file.

I have enabled "Always wait for the network at computer startup and logon"
policy as described in KB 305293 with no noticible affect.

How can I setup the workstation so that the user does not have access to the
desktop until all drive mappings and other GPO applied settings are
complete?? Is there a local registry setting that works.Logon scripts are
applied through a GPO.

User training is a lost cause, my users all believe WORD is a typewriter and
overwhelmingly have no computer skill whatsoever. This is very poor
behavior on the OS part.

dave Admin
 
Slow log on with AD is usually the sign of a mis configured DNS set up.

You should have a DNS server set up for the AD domain. It should point to
itself in the properties of TCP/IP for DNS. All AD clients must point to the
AD DNS server ONLY. For Internet access you should set up your AD DNS server
to forward requests to your ISP or use root hints. Your AD clients should
not have your ISP's DNS servers listed on them.

Is this how your DNS is setup?

hth
DDS W 2k MVP MCSE
 
Thanks Danny but that's not it. My DNS setup is as you described. All
clients point to the DNS server. The DNS server points to itself, and
forwarders are setup to the ISP.

Not only is logon mapping slow with a GPO but browsing is often slow, and my
MS servers are new, dual processor and dual NICs for throughput, everything
is slower than accesing a Netware server.

dave
 
Back
Top