Options for resizing Server 2003 R2 system partition? 2

[PPettit]

I just got my hands on a new machine (Dell PowerEdge 2900) running Windows Server 2003 R2. It came pre-configured with a 12GB system partition. This seems incredibly small to me so I want to increase it's size. What's the best way to do this?

I've run across a few possible solutions so far:
1. Re-install the OS. This seems most likely because I don't have anything installed other than just the OS. However, I'm a bit concerned about getting hold of the right drivers and installing them like they were.

2. Use DISKPART.EXE from a Windows 2000 disk because the version that comes with 2003 won't extend system partitions. The downside is that this could create stability issues with the file system.

3. Use drive/partition utilities. Acronis Disk Director ($499) seems to be mentioned most often. However, Acronis True Image Echo Server ($699) looks more useful, overall. The price sucks, but I can live with it if the products are actually as useful as they appear to be.

Any other suggestions/recommendations?

 

[LawnBoy]

IMO, the Acronis products are worth their weight in helium3, top-notch stuff. Haven't tried Echo Server, though.



"We must fall back upon the old axiom that when all other contingencies fail, whatever remains, however improbable, must be the truth." - Sherlock Holmes

 

[Roadki11]

I use ghost to do this more than i would like. Ghost the c:\ off to dvd or a spare hdd. if you have nothing on the other partions delete them if you have data on other system partions ghost that also. when you restore the ghosts you can resize the partions on the fly, bigger or smaller works perfect everytime and ghost is cheap.



RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen

 

[Davetoo]

If this is a brand new system, then Dell provides server configuration CD's that you can use to just recreate the whole system from scratch.

Since you don't have any programs/hardware connected to it yet, this is the route I would take myself.

I'm Certifiable, not cert-ified.
It just means my answers are from experience, not a book.

 

[LWComputingMVP]

12 GB is not too small in my opinion and is, in fact, just about right if you manage the server appropriately, placing all the data on other partitions. I have a document that explains how to properly move various items in Windows to other partitions - some if you need to, some that should be, and some that shouldn't be but just in case you have to.

Please reference

http://www.lwcomputing.com/tips/static/bootdrivesize.asp

 

[PPettit]

Thanks for the replies, everyone.

Davetoo, I have a set of disks with one titled "Dell Systems Build and Update Utility". Is this what you're referring to?

I disregarded this 4-CD package because at first glance they seemed like they were only for the OpenManage software. Now that I've opened the package, I can see that they also include drivers and other software. I'll have to check these out.

 

[PPettit]

I ran the "Dell Systems Build and Update Utility" and re-built the server from scratch. It was simple to use. I just had to make a few configuration changes and swap out disks when needed. The automated setup/install process appears to have worked flawlessly.

Thanks for making me take a second look at those disks. Davetoo

 

[porkchopexpress]

Nice link there LWComputingMVP star for you, i would say that i'd go with 20gig just to be safe.