This message was deleted.

I think I see what's happening... The shrinking is being done on primary, however, if the customer then doesn't log in again for a while then a smaller container exists in primary compared to secondary. I may just setup the same shrinking procedure on secondary as it will likely be overwritten anyway when the customer logs in and starts using a primary mounted container. Sound about right?

You found the answer yourself 🙂 With CC you need to run the script on all shares made available for CC

Thank you @Kasper Johansen. Script has been set.