logon script on NT 4.0

B

Betsey Thurlo

Hi.
We have a NT 4.0 domain. I have begun putting Windows XP
on new computers. I have begun to notice that randomly
some XP computers will just not run the logon script OR
map their home drive. Sometimes this just starts
happening after the person has had their new computer for
3-4 weeks. Sometimes rebooting helps. Putting the logon
script in their startup folder does not help. When they
have this problem a set command shows the logon server
correctly, but their user home path is pointing to their
C: drive.
I'm starting to think it may be a CAL issue. Does
Windows XP handle CAL licensing different than previous
operating systems?
Thanks!

Betsey
 
A

allan grossman [mvp]

Hi, Betsey -

I'm pretty sure it's not a CAL issue.

Windows XP does handle network logons a bit differently -
and if all the required services haven't started on the
workstation Windows XP will still present you with a
login prompt.

Try this - let the machine sit at a login prompt for a
minute or two before logging on. If this works, set a
local or domain group policy to force the workstations to
wait for the network before displaying a login prompt.
If you set a local policy you'll find it in the Group
Policy Editor (gpedit.msc) under Computer Configuration --
Administrative Templates --> System --> Logon. Set the
policy that says 'Always wait for the network at computer
startup and logon'.

Hope this helps -
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top