G
Guest
It seems as though our Windows XP clients are starting to drop like flies.
On average, about 4 or 5 machines a day (and sometimes a lot more) are coming up with DC not found messages, which, in the past, I attributed to the computer account password changing.
However, this time, I have the policy in place to disable the computer account password changing (I had it in place for the Windows 2000 clients, and it worked just fine) but the same doesn't seem to apply to XP.
These are all XP clients. I've recently updated the GPO template files and ensured that the proper policy was enabled (this was done to try and fix the above problem, so it was not the pre-cursor), but it's a bit late.
Checking the computer accounts in AD, I notice that some of the accounts have been modified since the original deployment, and without that password being reset I don't see how this is possible.
Unless other attributes are modified in XP. This could result in the problems I'm seeing.
Does anyone know what else may change in AD that requires a matching client change? Something that might result in the computer account being invalidated? (Or showing similar symptoms too?)
Any help would be appreciated. At this rate, I have roughly 1500+ machines to redeploy in the next month (and every month thereafter) and that's not acceptable. Everything was working just fine with 2000 (and continues too with the few areas that still run 2k clients).
Thanks.
On average, about 4 or 5 machines a day (and sometimes a lot more) are coming up with DC not found messages, which, in the past, I attributed to the computer account password changing.
However, this time, I have the policy in place to disable the computer account password changing (I had it in place for the Windows 2000 clients, and it worked just fine) but the same doesn't seem to apply to XP.
These are all XP clients. I've recently updated the GPO template files and ensured that the proper policy was enabled (this was done to try and fix the above problem, so it was not the pre-cursor), but it's a bit late.
Checking the computer accounts in AD, I notice that some of the accounts have been modified since the original deployment, and without that password being reset I don't see how this is possible.
Unless other attributes are modified in XP. This could result in the problems I'm seeing.
Does anyone know what else may change in AD that requires a matching client change? Something that might result in the computer account being invalidated? (Or showing similar symptoms too?)
Any help would be appreciated. At this rate, I have roughly 1500+ machines to redeploy in the next month (and every month thereafter) and that's not acceptable. Everything was working just fine with 2000 (and continues too with the few areas that still run 2k clients).
Thanks.