mac_shinobi (7th May 2014)
In GParted you could move the F partition to the end of the drive and then expand the C drive, although obviously this requires rebooting the server and has an element of risk.
Last edited by Arthur; 7th May 2014 at 09:34 AM.
What I'd recommend.
1.Create a new partition at the end of the free space of 60gb and assign it g:\
2. robocopy entire contents of f:\ to g:\
3. remove any shares from f:\ folders and recreate them on g:\
4: check everything is working as expected.
5. delete the f:\ parition, reassign g:\ as F:\
6: extend c:\ into the space where f:\ was
when you recreate the shares will be your only "downtime" in this method - using gparted will require the server be booted into it.
Are you archiving storage logs? C:\Windows\system32\winevt
What about Windows Update C:\Windows\SoftwareDistribution\Download
In hindsight, easiest thing to say once done is done.
You may have to bite the bullet introduce a new DC, transfer any FSMO roles making sure it is a Global Catalog and then demoting the old one, leaving it as a file server for now.
To be honest I'd rather build a fresh server in the virtual environment where possible rather than P2V'ing
Much better to build a fresh OS in the virtual environment and transfer the services.
I have Robocopy, from Resource toolkit with GUI, which options do I need to set as when I click 'Run' I get done... but actually nothing has copied across ?
@Domino 's suggestion is the easiest with 0 downtime, or if you could wangle some downtime you can move the partitions around in something like gpartedit (warning ensure you have backups etc... as the world may end) but that way you can slide them all around and make the free space in the middle but if it goes mammaries skywards you will have to re-build it from scratch.
nephilim's suggestion on one of those posts is to make a clone of the server ( image ) and restore that onto another server with a larger drive etc or into a vm with a larger partition ?
Not sure if that is an option ?
I have a quick and dirty fix that you can use immediately
Add a new drive in VMware, then mount the drive in disk manager (on the DC) as a folder, then fill that folder up to release space on the main drive.
folder mount is cool
Silly question - but what is disk1? How about making disk1 a new drive F and robocopying the contents of the old F drive into that? Then you can delete both the F and Free Space at the end of drive0 - making it all unallocated, hopefully you should be able to extend the C: drive (although this might depend on the version of Windows - older versions don't like extending the system drive for some reason).
There are currently 1 users browsing this thread. (0 members and 1 guests)