Background: I'm attempting to extend the boot volume (C:) on the following SDL Tridion setup:
C:\has the OS, programs, and databases
D:\has the CMS and Content Delivery (all-in-one demonstration/training setup)
- AWS EC2 instance (based on an AMI) with Windows Server 2008 RC2
I'm not able to add extend
C:\ by adding space when creating a new instance because the un-allocated space isn't contiguous. Per Microsoft Technet:
"For logical drives, boot, or system volumes, you can extend the volume only into contiguous space and only if the disk can be upgraded to a dynamic disk."
I'm able to:
%TRIDON_HOME%to a new volume
- Delete the old
- Rename new volume to
After a everything is in the right place except Window access .
Has anyone done the same and are there any "gotchas" to doing this? The paths end up being the same and folder permissions seemed to transfer over okay, but I'm not sure if there's a better way.
Recommendations on a move with path changes (i.e. moving
D:\, for example) also appreciated.
Update: Revisiting a mistake I made in delivery. The Windows CD folder permissions aren't the same (deployment fails when trying to commit with
Access is denied).
It looks like you need to cut & paste when on the same volume, otherwise you have to reset Windows permissions at least for Windows 2008. See this post that shows moves and copies are treated the same across volumes (target setting inherited regardless).