Here is nice information for enterprise windows installation, SOP job aid. The table below is for splitting AD Database and logs with recommended way and configuring the RAID array and the hard drives for best performance. Installing 64 BIT Windows 2003 and 2008 has huge advantages; it is simply way faster than any other version of AD. Thanks a lot one more time, for Paul Yu, (Microsoft Consulting Services) for the great information.
FYI: when you split the AD files across the disks as we have done, the following are the recommended exclusions; normally you'd have to figure these locations out via registry settings. Keep in mind these ONLY apply when you've split the AD files the way we've done.
C Drive ( 64 Bit windows 2003 SP2) 8 Gig memory | OS & Logs | RAID 1 + 0 | |
D Drive ( NTDS) | SysVol & .DIT database | RAID 1 + 0 | |
H Drive CD-Room | |||
Note:
If cost is a factor in planning for disk space, you can place the operating system and Active Directory database on one RAID array (such as RAID 0+1) and the Active Directory log files on another RAID array (such as RAID 1). However, it is recommended that you store the Active Directory database and the SYSVOL shared folder on the same drive.
AD Exclusions
- C:\WINDOWS\NTDS\Edb*.log
- C:\WINDOWS\NTDS\Res1.log
- C:\WINDOWS\NTDS\Res2.log
- D:\WINDOWS\NTDS\ntds.dit
- D:\WINDOWS\NTDS\Temp.edb
- D:\WINDOWS\NTDS\Edb.chk
SYSVOL Exclusions
- C:\WINDOWS\NTFRS\jet\sys\Edb.chk
- C:\WINDOWS\NTFRS\jet\Ntfrs.jdb
- C:\WINDOWS\NTFRS\jet\log\*.log
COMBINED LIST
- C:\WINDOWS\NTDS\Edb*.log
- C:\WINDOWS\NTDS\Res1.log
- C:\WINDOWS\NTDS\Res2.log
- C:\WINDOWS\NTFRS\jet\sys\Edb.chk
- C:\WINDOWS\NTFRS\jet\Ntfrs.jdb
- C:\WINDOWS\NTFRS\jet\log\*.log
- D:\WINDOWS\NTDS\ntds.dit
- D:\WINDOWS\NTDS\Temp.edb
- D:\WINDOWS\NTDS\Edb.chk
- D:\WINDOWS\sysvol\domain\DO_NOT_REMOVE_Ntfrs_Preinstall_Directory
- D:\WINDOWS\sysvol\staging\domain
Oz ozugurlu,
Systems Engineer
MCITP (EMA), MCITP (SA),
MCSE 2003 M+ S+ MCDST
Security Project+ Server+
oz@SMTp25.org
http://smtp25.blogspot.com
7 comments:
Your "Note" section contradicts the table just above it, unless you really meant to switch the location of the logs and database around.
Also, your "Combined List" section has two extra exclusions that don't appear in the "SYSVOL Exclusions" list.
Yes the best way is to split the databases logs and the Sysvol locations. The Sysvol and the .DIT database keep together and keep the logs on the C drive and follow the table in the article is one of the best ways of doing this. (Assuming you only have 4HD with 2 RAID controllers, RAID 1+ 0 and RAID 1+ 0.
The great network scenarios, you would have better implementation and more HD, resources. The bottom line is that, whichever RAID configuration would provide the faster and redundant scenario, what would be the configuration you would want to implement, but as always best practice and budget $$$ will conflict and wont like each other, from my experince.
Thanks for the feed back
Oz
When it comes to enterprise Windows installations, Power Automate services can play a crucial role in automating various aspects of the process, thereby increasing efficiency and reducing manual effort.
Discover captivating motion graphics videos that breathe life into your content.
Content Baskit welcome writers of all backgrounds and experience levels, from established professionals to aspiring bloggers. We believe in supporting and nurturing diverse voices and perspectives, and are committed to building a community of writers who can learn from one another and grow together. how to invest in trucking without driving
Embark on your journey with ease and comfort with SkyLink Transport, your premier choice for uk airport taxi services.
Take control of your network with Enterprise Domain Controllers Implementation! Just as
saint laurent bags secure your belongings in style, our expertise secures your domain with precision. Streamline your operations and elevate your infrastructure. Implementing domain control with confidence and expertise!
Post a Comment