AD Integrity Checker??

[Patrickm]

I have a Windows 2000 AD Domian, where ALL servers are running Windows 2000
Server. We recently started rolling out Windows XP to the clients, all
previously Win2K pro. On my particular machine I have XP Pro with all the
admin tools ( Admin Pak, Exchange Admin etc etc. etc) to manage the domain.
I just put XP SP2 on MY Workstation and now I'm experiencing all sorts of
strange behaviors on the domain in regards to domain policies. People are
not getting mapped drives, Folder redirections works randomly, users are
getting "Access Denied" errors to server shares they've been using for
years, accounts are getting locked out for no apparent reason, people are
being prompted to change passwords, when they do, they continue to get
prompted at the next login to change them again, just all sorts of weird
sh*t, very sporadically. The one thing that I have noticed is that the
default.ADM files and policy.adm files on the domain controllers now have
the same date and time as the new .adm files that were installed on my XP
workstation with SP2. Is there any type of tool that I can run on the DC's
that will report/fix/repair any inconsistancies with .adm files. I have read
that the .adm are very specific to OS and SP levels and what I have appears
to be incorrect but I am not positive, nor do I know how to correct it, if
it is wrong??? Please Help

 

[Guest]

Here is a heads-up on some of the more important issues you may run into with
regards to deploying Windows XP SP2.

Changes to Functionality in Microsoft Windows XP Service Pack 2

This document focuses on the changes in Windows XP Service Pack 2 and its
implications for developers. Examples and details are provided for several of
the technologies that are experiencing the biggest changes. Future versions
of this document will cover all new and changed technologies.

http://go.microsoft.com/fwlink/?LinkId=28022

Error messages when you try to modify or to view GPOs in Windows Server
2003, Windows XP, or Windows 2000

By default, when viewing or editing a GPO in GPEdit, the timestamps of the
..adm files in the GPO (stored in Sysvol) are compared with those on the
administrative workstation (see KB 816662 for details). This means that the
mere act of viewing an existing GPO from a Windows XP SP2 machine will result
in the new .adm files being uploaded to Sysvol - eventually used by any other
administrative workstation (whether XP SP2 or not). Without fixes we are in
the process of releasing, this will produce error messages in older versions
of GPEdit. This scenario is described in full in the following KB article
which has just gone online:

http://support.microsoft.com/default.aspx?kbid=842933

This fix goes on any system where you may need to use group policy editor.
This includes all Windows 2000 servers, Windows 2003 servers, and XP SP1
systems used for domain administrative tasks. The download for Windows 2000
is at the above location.


Best regards,

John Powell