This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.
Windows Server 2012 R2 - disk partitioning - system disk
What are the options to extend the C:\ partition?
This is a virtual machine, and the virtual disk has been expanded by 10GB (as shown as "Unallocated" space).
The C: partition is the one that needs to be expanded, and Windows can't do it since the newly added space is added after E:
I'm assuming if this can be done, it has to be done by booting from an .ISO since this also contains the system partition. But I'm not sure what the best / safest tool to use is (diskpart from the Windows Server 2008 .iso, or some non-Microsoft tool such as GParted)
Also, in your recommendation please include any gotcha's that I would want to be very careful about during the process.
Thanks
This is a virtual machine, and the virtual disk has been expanded by 10GB (as shown as "Unallocated" space).
The C: partition is the one that needs to be expanded, and Windows can't do it since the newly added space is added after E:
I'm assuming if this can be done, it has to be done by booting from an .ISO since this also contains the system partition. But I'm not sure what the best / safest tool to use is (diskpart from the Windows Server 2008 .iso, or some non-Microsoft tool such as GParted)
Also, in your recommendation please include any gotcha's that I would want to be very careful about during the process.
Thanks
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
This is a VM... WHY would you partition the disk in the first place!?!? You should create a SECOND virtual hard disk for E:, not a partition!
At this point you have move all the data OFF of E: to a new drive and then remove the E: partition and expand the C: partition.
IDEALLY, you can just COPY your existing virtual disk, fix the disk signature (see my article on signature collisions - http://www.experts-exchange.com/articles/24139/Windows-Signature-Collisions.html) and then ON THE COPY, delete the C: partition and re-assign E: to the partition on the copy. Then you can delete the E: partition on the original and extend C:.
And NEVER, EVER, partition a virtual hard disk.
At this point you have move all the data OFF of E: to a new drive and then remove the E: partition and expand the C: partition.
IDEALLY, you can just COPY your existing virtual disk, fix the disk signature (see my article on signature collisions - http://www.experts-exchange.com/articles/24139/Windows-Signature-Collisions.html) and then ON THE COPY, delete the C: partition and re-assign E: to the partition on the copy. Then you can delete the E: partition on the original and extend C:.
And NEVER, EVER, partition a virtual hard disk.
I agree but the customer partitioned their disk.
The problem (from the client's perspective) would be that if we add a 2nd drive and they move E to that, we may not be able to shrink the current virtual disk (in Windows, and then via the Hypervisor), and if we can't shrink it we have to bill for it's size whether they are using all that space or not.
The problem (from the client's perspective) would be that if we add a 2nd drive and they move E to that, we may not be able to shrink the current virtual disk (in Windows, and then via the Hypervisor), and if we can't shrink it we have to bill for it's size whether they are using all that space or not.
Lee is spot on with this. Actions and consequences. As to the follow-up, if being able to shrink is a concern, create a new drive at the size desired and robocopy. Don't mess with partition tools. High risk, minimal reward. Get your virtual disks configured right so that change management moving forward is easier and supported.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial