Slow XP logon times

[Guest Aaron]

Had a Windows 2000 AD domain with 2000 pro clients using roaming profiles.

Insalled a few XP machines and they are taking up to four minutes to logon to

the network using roaming profiles. Installed a new 2003R2 server and moved

FSMO roles. Still kept the 2000 server as a domain controller with the 2003

server. I can logon with no wait at all on the XP machines if not logging in

as a roamin profile user. Only when logging in with credential of roaming

user does the XP logon times take so long. DNS is pointing to the new server

first and the profiles are kept on the new servers. What could be taking the

XP pcs so long to long in compared to the quick 2000 pro logons?

[Guest Lanwench [MVP - Exchange]]

Re: Slow XP logon times

 

Aaron <Aaron@discussions.microsoft.com> wrote:

> Had a Windows 2000 AD domain with 2000 pro clients using roaming

> profiles. Insalled a few XP machines and they are taking up to four

> minutes to logon to the network using roaming profiles. Installed a

> new 2003R2 server and moved FSMO roles. Still kept the 2000 server

> as a domain controller with the 2003 server. I can logon with no

> wait at all on the XP machines if not logging in as a roamin profile

> user. Only when logging in with credential of roaming user does the

> XP logon times take so long. DNS is pointing to the new server first

> and the profiles are kept on the new servers. What could be taking

> the XP pcs so long to long in compared to the quick 2000 pro logons?

 

If you use mixed client OSes, don't let users roam between 'em. See whether

you have this problem with a user account on XP with no existing roaming

profile.

 

Also, you might want to enable "Always wait for networkon startup/logon" via

group policy. It helps loads.

[Guest Aaron]

Re: Slow XP logon times

 

 

 

"Lanwench [MVP - Exchange]" wrote:

> Aaron <Aaron@discussions.microsoft.com> wrote:

> > Had a Windows 2000 AD domain with 2000 pro clients using roaming

> > profiles. Insalled a few XP machines and they are taking up to four

> > minutes to logon to the network using roaming profiles. Installed a

> > new 2003R2 server and moved FSMO roles. Still kept the 2000 server

> > as a domain controller with the 2003 server. I can logon with no

> > wait at all on the XP machines if not logging in as a roamin profile

> > user. Only when logging in with credential of roaming user does the

> > XP logon times take so long. DNS is pointing to the new server first

> > and the profiles are kept on the new servers. What could be taking

> > the XP pcs so long to long in compared to the quick 2000 pro logons?

>

> If you use mixed client OSes, don't let users roam between 'em. See whether

> you have this problem with a user account on XP with no existing roaming

> profile.

>

> Also, you might want to enable "Always wait for networkon startup/logon" via

> group policy. It helps loads.

>

>

> Where is that setting in group policy. No problem with someone who logs in without roaming profile.

[Guest Lanwench [MVP - Exchange]]

Re: Slow XP logon times

 

Aaron <Aaron@discussions.microsoft.com> wrote:

> "Lanwench [MVP - Exchange]" wrote:

>

>> Aaron <Aaron@discussions.microsoft.com> wrote:

>>> Had a Windows 2000 AD domain with 2000 pro clients using roaming

>>> profiles. Insalled a few XP machines and they are taking up to four

>>> minutes to logon to the network using roaming profiles. Installed a

>>> new 2003R2 server and moved FSMO roles. Still kept the 2000 server

>>> as a domain controller with the 2003 server. I can logon with no

>>> wait at all on the XP machines if not logging in as a roamin profile

>>> user. Only when logging in with credential of roaming user does the

>>> XP logon times take so long. DNS is pointing to the new server

>>> first and the profiles are kept on the new servers. What could be

>>> taking the XP pcs so long to long in compared to the quick 2000 pro

>>> logons?

>>

>> If you use mixed client OSes, don't let users roam between 'em. See

>> whether

>> you have this problem with a user account on XP with no existing

>> roaming

>> profile.

>>

>> Also, you might want to enable "Always wait for networkon

>> startup/logon" via

>> group policy. It helps loads.

>>

>>

>> Where is that setting in group policy.

 

Computer Configuration\Administrative Templates\System\Logon

(I'd create a custom GPO - link it at the appropriate custom OU)

> No problem with someone who

>> logs in without roaming profile.

 

Right - you mentioned that. But that's not what I was asking. What about a

new user who never had an *old* roaming profile? Make sure they have the

path set up in ADUC, and then let them log in once & log out to cache a

roaming profile on the server..then have them try logging in and out again.

[Guest Aaron]

Re: Slow XP logon times

 

Ok, I created a new user and put the old roaming profile path in ADUC for

that user. Still same slow logon problem. Did you want me to create a

totally new profile instead?

 

"Lanwench [MVP - Exchange]" wrote:

> Aaron <Aaron@discussions.microsoft.com> wrote:

> > "Lanwench [MVP - Exchange]" wrote:

> >

> >> Aaron <Aaron@discussions.microsoft.com> wrote:

> >>> Had a Windows 2000 AD domain with 2000 pro clients using roaming

> >>> profiles. Insalled a few XP machines and they are taking up to four

> >>> minutes to logon to the network using roaming profiles. Installed a

> >>> new 2003R2 server and moved FSMO roles. Still kept the 2000 server

> >>> as a domain controller with the 2003 server. I can logon with no

> >>> wait at all on the XP machines if not logging in as a roamin profile

> >>> user. Only when logging in with credential of roaming user does the

> >>> XP logon times take so long. DNS is pointing to the new server

> >>> first and the profiles are kept on the new servers. What could be

> >>> taking the XP pcs so long to long in compared to the quick 2000 pro

> >>> logons?

> >>

> >> If you use mixed client OSes, don't let users roam between 'em. See

> >> whether

> >> you have this problem with a user account on XP with no existing

> >> roaming

> >> profile.

> >>

> >> Also, you might want to enable "Always wait for networkon

> >> startup/logon" via

> >> group policy. It helps loads.

> >>

> >>

> >> Where is that setting in group policy.

>

> Computer Configuration\Administrative Templates\System\Logon

> (I'd create a custom GPO - link it at the appropriate custom OU)

>

> > No problem with someone who

> >> logs in without roaming profile.

>

> Right - you mentioned that. But that's not what I was asking. What about a

> new user who never had an *old* roaming profile? Make sure they have the

> path set up in ADUC, and then let them log in once & log out to cache a

> roaming profile on the server..then have them try logging in and out again.

>

>

>

[Guest MoMule]

Re: Slow XP logon times

 

On Oct 2, 1:02 pm, Aaron <Aa...@discussions.microsoft.com> wrote:

> Ok, I created a new user and put the old roaming profile path in ADUC for

> that user. Still same slow logon problem. Did you want me to create a

> totally new profile instead?

>

> "Lanwench [MVP - Exchange]" wrote:

>

>

>

> > Aaron <Aa...@discussions.microsoft.com> wrote:

> > > "Lanwench [MVP - Exchange]" wrote:

>

> > >> Aaron <Aa...@discussions.microsoft.com> wrote:

> > >>> Had a Windows 2000 AD domain with 2000 pro clients using roaming

> > >>> profiles. Insalled a few XP machines and they are taking up to four

> > >>> minutes to logon to the network using roaming profiles. Installed a

> > >>> new 2003R2 server and moved FSMO roles. Still kept the 2000 server

> > >>> as a domain controller with the 2003 server. I can logon with no

> > >>> wait at all on the XP machines if not logging in as a roamin profile

> > >>> user. Only when logging in with credential of roaming user does the

> > >>> XP logon times take so long. DNS is pointing to the new server

> > >>> first and the profiles are kept on the new servers. What could be

> > >>> taking the XP pcs so long to long in compared to the quick 2000 pro

> > >>> logons?

>

> > >> If you use mixed client OSes, don't let users roam between 'em. See

> > >> whether

> > >> you have this problem with a user account on XP with no existing

> > >> roaming

> > >> profile.

>

> > >> Also, you might want to enable "Always wait for networkon

> > >> startup/logon" via

> > >> group policy. It helps loads.

>

> > >> Where is that setting in group policy.

>

> > Computer Configuration\Administrative Templates\System\Logon

> > (I'd create a custom GPO - link it at the appropriate custom OU)

>

> > > No problem with someone who

> > >> logs in without roaming profile.

>

> > Right - you mentioned that. But that's not what I was asking. What about a

> > new user who never had an *old* roaming profile? Make sure they have the

> > path set up in ADUC, and then let them log in once & log out to cache a

> > roaming profile on the server..then have them try logging in and out again.- Hide quoted text -

>

> - Show quoted text -

 

Some questions:

1) Is the slow login happening on every reboot, or just on the initial

reboot after joining the domain?

2) What are the roaming profile sizes that you are dealing with?

3) What happens when you allow a single user that is using a roaming

profile to become a local administrator on the XP machine?

 

Some ideas:

1) Check DNS

2) Check permissions

 

Deion "Mule" Christopher

[Guest Lanwench [MVP - Exchange]]

Re: Slow XP logon times

 

Aaron <Aaron@discussions.microsoft.com> wrote:

> Ok, I created a new user and put the old roaming profile path in ADUC

> for that user. Still same slow logon problem. Did you want me to

> create a totally new profile instead?

 

Yes. As I said, this is what you should use as a test. A profile that never

touched a workstation not running the same OS.

 

I'm including my roaming profile boilerplate below....some if it is likely

old news to you, but just in case.....

 

----

General tips:

 

1. Set up a share on the server. For example - d:\profiles, shared as

profiles$ to make it hidden from browsing. Make sure this share is *not* set

to allow offline files/caching! (that's on by default - disable it)

 

2. Make sure the share permissions on profiles$ indicate everyone=full

control. Set the NTFS security to administrators, system, and users=full

control.

 

3. In the users' ADUC properties, specify \\server\profiles$\%username% in

the profiles field

 

4. Have each user log into the domain once from their usual workstation

(where their existing profile lives) and log out. The profile is now

roaming.

 

5. If you want the administrators group to automatically have permissions to

the profiles folders, you'll need to make the appropriate change in group

policy. Look in computer configuration/administrative templates/system/user

profiles - there's an option to add administrators group to the roaming

profiles permissions.

 

Notes:

 

* Make sure users understand that they should not log into multiple

computers at the same time when they have roaming profiles (unless you make

the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't

change them). Explain that the

last one out wins,

when it comes to uploading the final, changed copy of the profile.

 

* Keep your profiles TINY. Via group policy, redirect My Documents at the

very least - to a subfolder of the user's home directory or user folder.

Also consider redirecting Desktop & Application Data similarly..... so the

user will have:

 

\\server\home$\%username%\My Documents,

\\server\home$\%username%\Desktop,

\\server\home$\%username%\Application Data.

 

Alternatively, just manually re-target My Documents to

\\server\home$\%username% (this is not optimal, however!)

 

If you aren't going to also redirect the desktop using policies, tell users

that

they are not to store any files on the desktop or you will beat them with a

stick. Big profile=slow login/logout, and possible profile corruption.

 

* Note that user profiles are not compatible between different OS versions,

even between W2k/XP. Keep all your computers. Keep your workstations as

identical as possible - meaning, OS version is the same, SP level is the

same, app load is (as much as possible) the same.

 

* Do not let people store any data locally - all data belongs on the server.

 

* The User Profile Hive Cleanup Utility should be running on all your

computers. You can download it here:

http://www.microsoft.com/downloads/details.aspx?familyid=1B286E6D-8912-4E18-B570-42470E2F3582&displaylang=en

 

 

>

> "Lanwench [MVP - Exchange]" wrote:

>

>> Aaron <Aaron@discussions.microsoft.com> wrote:

>>> "Lanwench [MVP - Exchange]" wrote:

>>>

>>>> Aaron <Aaron@discussions.microsoft.com> wrote:

>>>>> Had a Windows 2000 AD domain with 2000 pro clients using roaming

>>>>> profiles. Insalled a few XP machines and they are taking up to

>>>>> four minutes to logon to the network using roaming profiles.

>>>>> Installed a new 2003R2 server and moved FSMO roles. Still kept

>>>>> the 2000 server as a domain controller with the 2003 server. I

>>>>> can logon with no wait at all on the XP machines if not logging

>>>>> in as a roamin profile user. Only when logging in with

>>>>> credential of roaming user does the XP logon times take so long.

>>>>> DNS is pointing to the new server first and the profiles are kept

>>>>> on the new servers. What could be taking the XP pcs so long to

>>>>> long in compared to the quick 2000 pro logons?

>>>>

>>>> If you use mixed client OSes, don't let users roam between 'em. See

>>>> whether

>>>> you have this problem with a user account on XP with no existing

>>>> roaming

>>>> profile.

>>>>

>>>> Also, you might want to enable "Always wait for networkon

>>>> startup/logon" via

>>>> group policy. It helps loads.

>>>>

>>>>

>>>> Where is that setting in group policy.

>>

>> Computer Configuration\Administrative Templates\System\Logon

>> (I'd create a custom GPO - link it at the appropriate custom OU)

>>

>>> No problem with someone who

>>>> logs in without roaming profile.

>>

>> Right - you mentioned that. But that's not what I was asking. What

>> about a new user who never had an *old* roaming profile? Make sure

>> they have the path set up in ADUC, and then let them log in once &

>> log out to cache a roaming profile on the server..then have them try

>> logging in and out again.