Windows Thread, Service Pack 3 Password Problem in Technical; I have put SP3 on this years college image, all was tested and things seem to be going well BUT, ...
21st August 2008, 03:41 PM #1
Service Pack 3 Password Problem
I have put SP3 on this years college image, all was tested and things seem to be going well BUT, i have now found that if a user is prompted to change their password when they try to logon, windows sets that user a local profile to use!
After the password has been changed a use can logon to any machine running SP3 and is given the correct profile from the server but if they logon to the same machine on which they changed their password the local profile is still used as it is not automatically deleted.
Obviously this is a big problem as we have all our new students enroling over the next few days.
Has anyone come across this before? is there a fix? A google search seems to suggest its an issue with SP3 can anyone confirm this?
Any help would be greatly appreciated.
21st August 2008, 04:24 PM #2
I've always found that if they dont choose to change their password if its required to be changed, it kicks them off again. Dont remember if it was a Group Policy that enforced it though, or whether thats a new feature [thats bound to be group policy controlable].
Good luck and let us know
21st August 2008, 04:34 PM #3
I think he means after they change the password and they continue to login they get a local profile.
21st August 2008, 07:47 PM #4
I've one network which has XP SP3 fully deployed and have not seen this behaviour at all. I presume users are supposed to have roaming profiles?
To me it sounds as though the roaming profile cannot be found, so a local one is used (which is completely normal).
Could you give us a link to what you've found on Google?
21st August 2008, 07:54 PM #5
Its wouldn't be a permission in that case.
After the password has been changed a use can logon to any machine running SP3 and is given the correct profile from the server
We have SP3 on 90% of machines, we use local profiles anyway so can't test it.
21st August 2008, 10:36 PM #6
Hmm! we have SP3 and aint come accross this either.. linky to what u found on google if u dnt mind ..
21st August 2008, 11:14 PM #7
I've been experiencing this issue too, I definitely think it is something to do with SP3 and roaming profiles as I can only recreate the problem on SP3 machines. The only thing I have managed to find on google which mentions the problem is this. I have also managed to find this in the Microsoft KB which describes the problem perfectly, but it relates to vista and not xp.
Sorry not to have been of any help, but at least you know you are not alone!
21st August 2008, 11:36 PM #8
That's a good find Iain, it looks like it was fixed in Vista SP1.
lsasrv.dll does exist in Windows XP SP3 in C:\Windows\System32\ Maybe someone could experiment and overwrite it with an XP SP2 version?
21st August 2008, 11:40 PM #9
Out of curiosity SSFC, did you install XP SP3 on top of an existing installation or did you create a new slipstreamed disc and install from new?
22nd August 2008, 09:06 AM #10
The problem we are having is exactly the same as the vista one in the KB article posted by Iain only on XP SP3.
When installing: Windows + SP2 was setup from a CD then updated by windows update to SP3.
Having trawled the net yesterday i found a couple of people having the same problem, Leicester Uni being one but no one seems to have a fix yet.
I will keep you all informed if i find a solution.
25th August 2008, 10:37 AM #11
This is interesting, because in the one network I manage they are all re-builds, so I created a slipstream XP SP3 disc and started from scratch (then re-imaged all machines). I haven't seen this problem once.
Be interesting to see if other users suffering from this problem are applying SP3 on top of an existing SP2 installation.
4th September 2008, 09:09 PM #12
Just found this thread - after I already started my own one
I've got the same issue, - my image is based on an XP Pro SP3 ISO image from MS. It also seems to happen on other machines that have been upgraded to SP3 via WSUS.
Did anyone manage to find a fix?
5th September 2008, 11:05 AM #13
Currently on hold to MS support losing the will to live from the hold music.
Right, they know it's a bug, but no idea when/if there will be a hotfix :|
5th September 2008, 11:32 AM #14
Maybe they're all hoping we'll jump onto Vista!
30th April 2009, 04:10 PM #15
2 Thanks to SSFC:
Iain (30th April 2009), ZeroHour (30th April 2009)
By andy_nic in forum Windows
Last Post: 18th July 2008, 12:33 PM
By Nij.UK in forum Windows
Last Post: 28th September 2006, 07:39 PM
By deerwood in forum Educational Software
Last Post: 20th July 2006, 02:52 PM
By zippy in forum How do you do....it?
Last Post: 13th December 2005, 10:08 AM
By Rozzer in forum Windows
Last Post: 19th August 2005, 07:49 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)