Is there a reason external site have a “Subscriptions” tab that allows for automatic site subscription based upon property and custom internal sites do not?
Do to the large environment, custom sites need to be created for organizations within the company. I’ve tackled this different ways, but would prefer just to use the computers domain or OU path to determine which site they should subscribe. It appears the best way is to use the subscription action and add the logic there.
I’m curious as to why Internal/Custom site properties do not have the filtering available like external sites?
You definitely can control the subscriptions for custom sites (but it is in a different location in the console). Right click on a computer, go to “Edit Computer Settings”, click on “More Options” and on the “Settings” tab, you will see “Custom Site Membership”, which do what you want.
As a note, site subscriptions for Custom Sites is available in BES 6.0+ and site subscriptions for external sites are only available in BES 7.0+.
If the custom site is set using “Edit Computer Settings” will that become an action policy (provided the Target & Execution times are set appropriately)?
For example, will any future computers that meet the “target” criteria be dynamically assigned to the custom site, or is this a “static” assignment (i.e. only applies to the computers selected in the Target at that time).