Schema Update Page 699

[Babscoole]

You mention updating the schema from version 30 to 31. In my case I was at 30, but the ADPrep tool on my Vista disk updated all the way to 39. I hope to god this wasn't wrong!!

Also, I was using a Dell OEM DVD and the path was completely different than the one given in the book. Mine was at Sources\ADPREP\ .May want to mention in the errata that your path was an example for one specific disc and may be different.

[PreviousPoster]

I don't know what effects this really has but the adprep tool that comes with Vista is more or less only for reference since this is the new version for Windows Server 2008 Domain Controllers (that I suspect you don't have in your production environment yet). Version 31 is the one that comes with Windows Server 2003 R2 which is the one you should have installed

[PreviousPoster]

Windows Vista Bitlocker recovery keys and Active Directory schema extension

Although ADPREP executable exists on the Vista DVD (\sources\adprep\adprep.exe) with accompanying LDF files (sch14.ldf - sch39.ldf), you should NOT use it to extend the schema of Windows 2000/Server 2003/R2 Active Directory. These files are there for informational purposes only for showing what Longhorn Server will bring along when it'll arrive.
Windows Vista Bitlocker recovery keys cannot be stored in the Active Directory before extending the schema and modifying AD permissions. The information and tools to perform these preliminary tasks will become available some time in the near future - when it's ready, I guess

There is a lot of information out there stating not to upgrade the Schema using the Vista DVD - If it's a production environment - I hope you have a good backup.

[Babscoole]

After the fact I've seen that helpful tidbit of information posted about the web. Seems to be from one or two MVPs that's been copied around, but nothing I could find officially from MS.

Nothing has blown up, caught fire, stopped working, or started generating errors. Given this, a rollback of the domain from backup could potentially cause more problems than it solves. I figure that it may potentially cause an issue when it comes time to upgrade to Windows Server 2008 next spring, but until then I'll just let sleeping dogs lie.

If an issue does crop up either then or before, I'll use up a support incident credit that I have lying around. From poking through the KB, it seems that most schema oopsies that are caused by MS or major 3rd party vendors have a more granular fix available from MS once it's a known problem. I have to believe that I'm not the only one who followed the page 699 advise.

[RTHJr]

This is a 4th ed. oversight updated very well in 5th ed as asked for here.