Bit of advice needed

[ppuddick]

Hi all,

I've just setup an SBS2003 server for one of our clients. Following a tutorial on the web I partitioned the first disk (of a RAID 1 mirror) as follows;

C:\ - 10Gigs - SYSTEM Drive
D:\ - 2Gigs - SWAP
E:\ - 138Gigs - DATA

Now, I ran through the SBS wizards as I've been told that manually running dcpromo and Exchange setup can cause problems. Everything's fine and I have Active Directory setup and mail coming into Exchange no problem with an SMTP mail feed.

My only concern is that during the wizard setup it didn't ask where I wanted to put NTDS and SYSVOL. On Server 2003 installations I put these on a different partition. So then, they are in the default locations of C:\Windows\NTDS and C:\Windows\SYSVOL. It did ask me where I wanted the storage folders for Exchange and application deployment to go and I was able to set those to E:\ (extended partition)

As stated above the System drive is a 10Gigs partition. Do you think that is going to cause problems in the future. They only have 7 XP client machines authenticating to the server at the moment and that's likely to increase to 9 or 10 soon.

Any thoughts or comments would be very much appreciated. Thank you for reading.

 

[schtek]

my only thoughts would have been the exchange i would have put into another partion say f:/ 10Gigs to keep it on its own folder /section

and another 20Gigs for users folder G:/ when creating accounts if they are storing onto the server!!! leaves you with 100gigs for data. you can always add at a later stage to give more for data

It's the same each time with progress. First they ignore you, then they say you're mad, then dangerous, then there's a pause and then you can't find anyone who disagrees with you.

 

[NickFerrar]

10GB should be fine. In your case though I'm not sure you're gaining much by partitioning up everything anyway as you imply it's all on the same physical RAID-1 set. The point in partitioning everything up for performance is also to use separate RAID sets/channels/containers so the I/O hit is distributed, just logically partitioning at the OS level isn't going to help with this.