Windows cannot complete the password change for USERNAME because:

I'm getting this error in the Active Directory Users and Groups snap-
in when trying to reset a password or add a users (set password). This
is after demoting one of my two AD servers.
(Windows 2003 R2 standard on both).

The demotion seemed to complete ok, but ever since I've been getting
the error.

I have checked the FSMO settings and used the DCdiag and NETDiag tools
to check for errors and warnings. I have not seen anything to be
alarmed. I have run adsiedit.msc and checked settings for trust and
site info. I have run the AD Sites and Services and verified there was
no old server info in the NTDS settings, etc.

I am at a loss for what to check next.

It is an error found on all accounts. I don't see anything under a
user's attributes in the schema to raise alarms in my head.

I would greatly appreciate anyone's thoughts. I have already run
through Paul Bergson's post on a quite similar post. Though if someone
could share specific things to watch for that would be great.

Bryan

Hello bntidd,

Have you moved the FSMO roles to the running DC before demoting the old one?
And have you made it a Global catalog?

Best regards

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

> I'm getting this error in the Active Directory Users and Groups snap-
> in when trying to reset a password or add a users (set password). This
> is after demoting one of my two AD servers.
> (Windows 2003 R2 standard on both).
> The demotion seemed to complete ok, but ever since I've been getting
> the error.
>
> I have checked the FSMO settings and used the DCdiag and NETDiag tools
> to check for errors and warnings. I have not seen anything to be
> alarmed. I have run adsiedit.msc and checked settings for trust and
> site info. I have run the AD Sites and Services and verified there was
> no old server info in the NTDS settings, etc.
>
> I am at a loss for what to check next.
>
> It is an error found on all accounts. I don't see anything under a
> user's attributes in the schema to raise alarms in my head.
>
> I would greatly appreciate anyone's thoughts. I have already run
> through Paul Bergson's post on a quite similar post. Though if someone
> could share specific things to watch for that would be great.
>
> Bryan
>