W2003 profiles broken after password change

[Guest tomservo]

I hope I'm posting to the right group, if not please let me know...

 

Running Windows 2003 server, clients are all XP Pro SP2 and 3 mixed. Long

story short:

 

As far as I can tell the following holds true:

 

User's account is set to require a change of password at the next login.

User logs on to workstation, and is prompted to change password.

User successfully changes password, and logs in.

User's Lotus Note's icon points to C: drive, My Documents does not appear to

remap to server.

User logs out, logs into different machine, Lotus Note icon correctly points

to H: drive, My Documents appear to map correctly.

User logs out, logs back into machine where password change was performed.

User desktop is still default, Lotus Notes icon points to C:.

 

Log into any workstation other than the one where the password was changed

and the user login works fine.

 

A couple of things I have noticed:

On machines where the user password was changed, a local profile is created

for the user. User profiles on the local workstation have two options, local

or roaming. Profiles on the workstation other than the user with the password

change are set to roaming. You can check user profiles by going to My

Computer -> Properties -> Advanced -> User Profiles -> Settings. The profile

for the user whose password was changed is set to local, with roaming grayed

out. Neither logging in as the Domain Administrator or the local

administrator account will allow the profile to be changed to roaming or, for

that matter, deleted. Only once the user has logged into another workstation

can you then delete the local profile on the original machine (logged in as

an admin).

 

I downloaded a hot fix from MS (KB Article Number(s): 821425) but can't get

it to install on the server, unable to locate update.inf.

 

Any thoughts?

[Guest Meinolf Weber]

Re: W2003 profiles broken after password change

 

Hello tomservo,

 

Profiles will not "break" after a password change. If you use roaming profiles

and they work on all machines except one, it can be that the machine is not

correctly running in the domain, maybe belonging to DNS problems or accessing

the share where the profiles are located. Also the hotfix where youare talking

about will only change the information text for user, which is not using

the correct characters for the password complexity policy.

So you have mixed here for my opinion 2 different problems, PROFILES and

PASSWORDS. Just changing a password will not interfere with other configurations.

 

Describe your setup for user configuration to access the profiles and where

they are stored.

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> 821425

>

[Guest tomservo]

Re: W2003 profiles broken after password change

 

 

 

"Meinolf Weber" wrote:

> Hello tomservo,

>

> Profiles will not "break" after a password change. If you use roaming profiles

> and they work on all machines except one, it can be that the machine is not

> correctly running in the domain, maybe belonging to DNS problems or accessing

> the share where the profiles are located. Also the hotfix where youare talking

> about will only change the information text for user, which is not using

> the correct characters for the password complexity policy.

> So you have mixed here for my opinion 2 different problems, PROFILES and

> PASSWORDS. Just changing a password will not interfere with other configurations.

>

> Describe your setup for user configuration to access the profiles and where

> they are stored.

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > 821425

> >

>

>

There are 50 machines in the domain, and I can recreate this problem on any

of them, with all 150+ users. I wish that it were limited to one or two

machines but it's not (or one or two or even a dozen users, but it's not that

either).

 

As far as the password change goes,not sure how it works, I know that the

passwords I am selecting for testing more than meet the complexity rules, in

fact when I simplify the rules via GP it still does not work.

 

Granted, I do need to provide more info re: setup. Basically I have 50

workstations running XP Pro, sp2 and 3, Windows 2003 server fully patched.

150 users all in the domain, all with roaming profiles. I think if I can

figure out why the act of forcing a password change results in the creation

of a local profile, I'd have my answer. By the way, if there is no password

change, all users work 100% correctly.

 

Thanks!

[Guest Meinolf Weber]

Re: W2003 profiles broken after password change

 

Hello tomservo,

 

Your password policy is set on domain level?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> "Meinolf Weber" wrote:

>

>> Hello tomservo,

>>

>> Profiles will not "break" after a password change. If you use roaming

>> profiles

>> and they work on all machines except one, it can be that the machine

>> is not

>> correctly running in the domain, maybe belonging to DNS problems or

>> accessing

>> the share where the profiles are located. Also the hotfix where

>> youare talking

>> about will only change the information text for user, which is not

>> using

>> the correct characters for the password complexity policy.

>> So you have mixed here for my opinion 2 different problems, PROFILES

>> and

>> PASSWORDS. Just changing a password will not interfere with other

>> configurations.

>> Describe your setup for user configuration to access the profiles and

>> where they are stored.

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> 821425

>>>

> There are 50 machines in the domain, and I can recreate this problem

> on any of them, with all 150+ users. I wish that it were limited to

> one or two machines but it's not (or one or two or even a dozen users,

> but it's not that either).

>

> As far as the password change goes,not sure how it works, I know that

> the passwords I am selecting for testing more than meet the complexity

> rules, in fact when I simplify the rules via GP it still does not

> work.

>

> Granted, I do need to provide more info re: setup. Basically I have 50

> workstations running XP Pro, sp2 and 3, Windows 2003 server fully

> patched. 150 users all in the domain, all with roaming profiles. I

> think if I can figure out why the act of forcing a password change

> results in the creation of a local profile, I'd have my answer. By the

> way, if there is no password change, all users work 100% correctly.

>

> Thanks!

>

[Guest tomservo]

Re: W2003 profiles broken after password change

 

Yes, default domain policy,

 

Thanks for responding by the way, I appreciate your help.

 

"Meinolf Weber" wrote:

> Hello tomservo,

>

> Your password policy is set on domain level?

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>

> > "Meinolf Weber" wrote:

> >

> >> Hello tomservo,

> >>

> >> Profiles will not "break" after a password change. If you use roaming

> >> profiles

> >> and they work on all machines except one, it can be that the machine

> >> is not

> >> correctly running in the domain, maybe belonging to DNS problems or

> >> accessing

> >> the share where the profiles are located. Also the hotfix where

> >> youare talking

> >> about will only change the information text for user, which is not

> >> using

> >> the correct characters for the password complexity policy.

> >> So you have mixed here for my opinion 2 different problems, PROFILES

> >> and

> >> PASSWORDS. Just changing a password will not interfere with other

> >> configurations.

> >> Describe your setup for user configuration to access the profiles and

> >> where they are stored.

> >>

> >> Best regards

> >>

> >> Meinolf Weber

> >> Disclaimer: This posting is provided "AS IS" with no warranties, and

> >> confers

> >> no rights.

> >> ** Please do NOT email, only reply to Newsgroups

> >> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> >>> 821425

> >>>

> > There are 50 machines in the domain, and I can recreate this problem

> > on any of them, with all 150+ users. I wish that it were limited to

> > one or two machines but it's not (or one or two or even a dozen users,

> > but it's not that either).

> >

> > As far as the password change goes,not sure how it works, I know that

> > the passwords I am selecting for testing more than meet the complexity

> > rules, in fact when I simplify the rules via GP it still does not

> > work.

> >

> > Granted, I do need to provide more info re: setup. Basically I have 50

> > workstations running XP Pro, sp2 and 3, Windows 2003 server fully

> > patched. 150 users all in the domain, all with roaming profiles. I

> > think if I can figure out why the act of forcing a password change

> > results in the creation of a local profile, I'd have my answer. By the

> > way, if there is no password change, all users work 100% correctly.

> >

> > Thanks!

> >

>

>

>

[Guest Meinolf Weber]

Re: W2003 profiles broken after password change

 

Hello tomservo,

 

Please post an unedited ipconifg /all from the server and one problem client.

Did you check with gpresult /v on the client that all policy settings are

applied correct?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Yes, default domain policy,

>

> Thanks for responding by the way, I appreciate your help.

>

> "Meinolf Weber" wrote:

>

>> Hello tomservo,

>>

>> Your password policy is set on domain level?

>>

>> Best regards

>>

>> Meinolf Weber

>> Disclaimer: This posting is provided "AS IS" with no warranties, and

>> confers

>> no rights.

>> ** Please do NOT email, only reply to Newsgroups

>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>> "Meinolf Weber" wrote:

>>>

>>>> Hello tomservo,

>>>>

>>>> Profiles will not "break" after a password change. If you use

>>>> roaming

>>>> profiles

>>>> and they work on all machines except one, it can be that the

>>>> machine

>>>> is not

>>>> correctly running in the domain, maybe belonging to DNS problems or

>>>> accessing

>>>> the share where the profiles are located. Also the hotfix where

>>>> youare talking

>>>> about will only change the information text for user, which is not

>>>> using

>>>> the correct characters for the password complexity policy.

>>>> So you have mixed here for my opinion 2 different problems,

>>>> PROFILES

>>>> and

>>>> PASSWORDS. Just changing a password will not interfere with other

>>>> configurations.

>>>> Describe your setup for user configuration to access the profiles

>>>> and

>>>> where they are stored.

>>>> Best regards

>>>>

>>>> Meinolf Weber

>>>> Disclaimer: This posting is provided "AS IS" with no warranties,

>>>> and

>>>> confers

>>>> no rights.

>>>> ** Please do NOT email, only reply to Newsgroups

>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

>>>>> 821425

>>>>>

>>> There are 50 machines in the domain, and I can recreate this problem

>>> on any of them, with all 150+ users. I wish that it were limited to

>>> one or two machines but it's not (or one or two or even a dozen

>>> users, but it's not that either).

>>>

>>> As far as the password change goes,not sure how it works, I know

>>> that the passwords I am selecting for testing more than meet the

>>> complexity rules, in fact when I simplify the rules via GP it still

>>> does not work.

>>>

>>> Granted, I do need to provide more info re: setup. Basically I have

>>> 50 workstations running XP Pro, sp2 and 3, Windows 2003 server fully

>>> patched. 150 users all in the domain, all with roaming profiles. I

>>> think if I can figure out why the act of forcing a password change

>>> results in the creation of a local profile, I'd have my answer. By

>>> the way, if there is no password change, all users work 100%

>>> correctly.

>>>

>>> Thanks!

>>>

[Guest krzych]

Re: W2003 profiles broken after password change

 

I have the same problem - after user changes the password during logon

instead of roaming Windows is creating local profile ( in userenv.log you can

see that ). And I think it happens after I deployed Win XP SP3. But after

rebooting that PC roaming profile is loaded OK, perhaps simple logoff/logon

would be enough. I looks like some SMB sessions are not correctly updated ??

[Guest Landair]

Re: W2003 profiles broken after password change

 

anything on this lately

 

we too are experiencing some issue and apparently its a known problem ??? wtf

http://www.le.ac.uk/its/problems/systems/xpsp3pw.html

 

 

 

 

 

 

"krzych" wrote:

> I have the same problem - after user changes the password during logon

> instead of roaming Windows is creating local profile ( in userenv.log you can

> see that ). And I think it happens after I deployed Win XP SP3. But after

> rebooting that PC roaming profile is loaded OK, perhaps simple logoff/logon

> would be enough. I looks like some SMB sessions are not correctly updated ??