The deployment of ActiveControl software has historically required the same full ‘Server’ transport to be deployed in the Domain Controller plus all Satellite Systems (ie Dev, QA, Production etc) being managed via ActiveControl. The same has generally been true for Cumulative Patches – in that all CPs needed to be deployed to all Satellite Systems as well as the Domain Controller.

This has always resulted in a slightly painful experience for customers – and so on the back of customer feedback, ActiveControl 9.00 introduces a revised software packaging structure – which ultimately aims to reduce the size of the ActiveControl software transport that needs to be deployed to most of the satellite systems – and in many cases also avoid the need for Cumulative Patches to be deployed to non-Development satellite systems.

From ActiveControl 9.00 onwards – the software will be named (and deployed) as follows:

Transport Name Where to Deploy What does this transport contain …
Full Domain Controller + Development satellite systems All of the ActiveControl objects.
Remote Non-Development satellite systems Smaller subset of objects relating to specific functionality needed in non-Development systems (eg Imports).


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment