Schema changes to Win2k AD when indrocuding Win2k3 DC?
Posted on 2004-04-08
I currently have a Windows 2000 AD forest and a Windows 2000 native domain. I'd like to introduce a Windows Server 2003 DC to an existing domain without upgrading the functional level from Win2k native.
I've read in many places that Win2k3 can act as a DC in a 2000 native domain, but when I run dcpromo on the Win2k3 server to promote it, it requires that adprep be run on the forest and domain before it can be added.
Does anyone know what adprep is doing to "prepare" the forest and domain? My assumption is that the end result will still be a Windows 2000 forest and a Windows 2000 native AD domain, but it obviously did _something_ to the AD structure. There are services within my company that are heavily integrated with AD , so I can't modify the schema, but I can theoretically extend it so long as all the existing fields do not change.
I'm aware that the Win2k AD schema also has different "levels" within the same functional level; is this what the Win2k3 aprep is changing? Does anyone know which level it needs to be at for the Win2k3 DC to be present? Can the Win2k3 adprep only extend the schema (assuming the functional level doesn't change), or can it modify what's already existing?