CC4 - moving shares

[synaesthesia]

I'm helping out a local school with CC4 at the moment. It's been a while since I tackled a lot of the common issues however one thing they're having an issue with is drive space.

Ideal scenario would be to relocate the RMPublic & RMShared Documents folders to another storage device, whether network based (NAS) or iscsi. Has anyone done this with CC4? The only documentation I can find from RM dates back to 2005.

I'm wary of how embedded some of RM's systems are so simply relocating shares is quite likely to break something!

Edited February 28, 2017 by synaesthesia

[supawat1]

May be you could spend sometime on looking at relevant GPO settings of RMPublic and RM Shared Documents

[foofighterjim]

RMShared is covered in TEC1554215 but apparently only supports moving to another CC4 DC.

 

I can't find any supporting documentation regarding RMPublic, something in my mind is saying that it has to be on the FRDC (although I am sure I moved it at a previous school).

[synaesthesia]

May be you could spend sometime on looking at relevant GPO settings of RMPublic and RM Shared Documents

 

CC4 is so well ingrained, it's like Japanese knotweed. You could scratch the surface but have no idea how deep those roots go - moral being, start playing with GPO for existing CC4 stuff, expect pain

[howartp]

We moved RMPublic and RMShared a couple of years ago, though only onto E: instead of D:

 

I did contact RMSupport at the time and I'm sure RMPublic can go anywhere.

 

RMShared I think has to be one of your RM DCs or Additional User servers.

 

Peter

[bossman]

@synaesthesia

 

I remember setting up a SAN as 4 iscsi targets with the volumes already configured on the SAN and then mapping those volumes as drives on the RM DC as long as you use the Microsoft iscsi protocols then thats all you should have to do, then move the existing shares from one mapped drive to another using a third party software which will take all the shares plus access rights with it.

 

Long time ago bud memory is not what it used to be, you could also ask @Sylv3r as he may also have done something similar, I have no documentation as it was many years ago.

[angrycomputingteacher]

I think your best bet would be contacting RM.

[synaesthesia]

There's a very good reason why that's out of the question, and very much related to why there are so few remaining Community Connect installs compared to 5 years ago.

[Sylv3r]

I think it wouldn't cause any issues remapping the drives to alternative locations from a shared area point of view - one issue I can think of is if you have file rules setup generally these will likely have been done with UNC paths rather than drive letters, so these may need recreating for your P:\ software.

[synaesthesia]

I might just play simple/crafty instead and manually move the files over and leave a shortcut. Just have to be careful of any of the old rubbish software that could never make up it's mind about where it should go (the old packages we all know and love, some sit in Public, some in Shared Resources, some anywhere they lay their grubby hands on!)

[AlanD]

I've ben looking into this - for the same reason - lack of space for T: and W: drives.....and yes - it would appear to be a difficult and tangled knot to move them elsewhere - and even then it would seem to be necessary to use another DC. So, I started looking into increasing the disk space. Our CC4 servers have two mirrored system drives and four RAID 5 Data drives which fill the 6 slots. But it appears to be possible to add a 5inch to 2x 2.5 convertor and add another two drives into the RAID in our rack case and use OnLineCapacityExpansion to rebuild the RAID without losing data. RM wouldn't support this - because we don't have a hardware contract....and I am not enthusiastic about mixing two new drives with old drives. So I will probably replace all the drives. Obviously - good backups required first...probably stop all RM services before making backup and restart them after data is recovered.

[ajs]

Out of interest, when was the last time any maintenance was done on the WSUS instance on the server? Unless it's a very old installation I would expect WSUS to store its updates on the D: drive and if the default product selections are still in place then WSUS could well have downloaded updates for software that was never/is no longer in use.

 

Also, are there any old packages (particularly RM system ones) that can be removed from the RMMC (assuming none of the stations need a core update of course)? While each one may not free up a lot of space, removing a large number of them can free up quite a bit of space. May be worth running TreeSizeFree or something over the drive to see exactly where the space is being taken up.