Now Available:

Featured Resource:

line

Realtime Communities

line

Newsletter

Email Address:


line

Monthly Archives

line

RSS

line

Ask the Expert

Have a question for our resident expert? Email your questions to Greg.

« Server 2008 Domain Controllers: What's Most Neat and Cool? Part #5 of 6 | Main | Sir Edmund Hillary, Accomplished Climber and First Human Atop Everest, Rest in Peace. »

Server 2008 Domain Controllers: What's Most Neat and Cool? Part #6 of 6

Installation From Media

The following is excerpted from Chapter 7 of Windows Server 2008: What’s New / What’s Changed, available now from www.sapienpress.com.

Along with the helper DC, any IFM DC promotion needs a backup set from which to get its data. In Server 2003, this was done by making a System State backup of a functioning DC and utilizing that backup with the dcpromo /adv switch when attempting the Domain Controller promotion. The problem with this process was that the System State backup includes quite a bit more information than is necessary for the DC promotion. More data == more media.

So now with Server 2008, we have a new way of collecting just the information necessary for the promotion using NTDSUTIL. The tool has been updated to handle creating the necessary data files for an IFM promotion. Four possible options for creating IFM media are available…

More after the jump.

• Creating IFM media for a full AD DC or an AD LDS instance. This is the selection you’ll want to choose for a full IFM as it includes the information within the SYSVOL.

• Creating IFM media without SYSVOL for a full AD DC or an AD LDS instance. This selection is used in situations where SYSVOL information is changing rapidly or is not wanted as part of the IFM media.

• Creating IFM media for an RODC. As is obvious, use this selection when creating an RODC.

• Creating IFM media without SYSVOL for an RODC. Same as above, but without the SYSVOL data.

The process to create a full media set for an IFM installation involves invoking NTDSUTIL, then using the command activate instance ntds to set the focus on the current full AD instance, switching to the IFM node, and finally requesting the backup. Note that the backup must be pointed to a preexisting empty folder or you will receive an error. Once completed, the backup will include a copy of AD’s main ntds.dit database file as well as the contents of the SYSVOL and the SECURITY and SYSTEM registry information.

Interested in reading the whole series? Click here for a link to every post in this series.

Tags:              
 Email This!  Digg it!  Sphere it!  Del.icio.us  Reddit!  Newsvine

Posted by Greg Shields on January 10, 2008 12:30 AM |

TrackBack

TrackBack URL for this entry:
http://www.realtime-windowsserver.com/type/mt-tb.cgi/592

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

Search

line

Most Active Posts

line

Library Resources

line
line

Recent Posts

line

Categories

line

Greg Shields' Bio:

Greg Shields, is an independent author, instructor, and IT consultant based in Denver, Colorado, and a co-founder of Concentrated Technology. With nearly 15 years of experience in information technology, Greg has developed extensive experience in systems administration, engineering, and architecture specializing in Microsoft systems management, remote application, and virtualization technologies. Greg is a Contributing Editor for Redmond Magazine, MCPmag.com, and Virtualization Review Magazine and is the author of five books, including Windows Server 2008:  What’s New / What’s Changed. Greg is also a highly sought-after instructor and speaker, speaking regularly at conferences like TechMentor Events, and producing computer-based training curriculum for CBT Nuggets.  Greg is a recipient of Microsoft "Most Valuable Professional" award with a specialization in Windows Terminal Services.