Once Policy Inheritance becomes available on your site, you will have up to 30 days to turn it on before we automatically do it for you. This allows you the time needed to prepare for it.
To migrate to the Policy Inheritance model,
- Navigate to Admin > RMM Settings - Preferences.
- Under Policy Settings, click Enable Policy Inheritance. Like the warning says, THIS CANNOT BE UNDONE.
- Take note of the ramifications and click OK.
- A note at the top will say, "Migration may take a few minutes."
- Refresh the page until you see this at the top: "Your account has successfully been migrated to use the new Policy Inheritance feature." You can click the X on its right to close the notice.
- Under Admin > RMM Settings, the Policy Settings section is no longer there.
- On all Customer pages, the Assets section has been replaced with an Assets & Policies tab at the top.
- Clicking the Assets & Policies tab will show a very different screen compared to clicking the old Assets section View All button.
- Changing an asset's policy is now done on a Customer's Assets & Policies tab.
- The Policies page UI is slightly different—the main difference being the Monitoring, Application Management, MAV and Backup columns are gone.
- When you add or edit a Policy, the screen is very different. One nice thing is you no longer have to scroll to see what is and isn't enabled. The left-hand nav will have numbers in parenthesis by a category, indicating how many sections are enabled in that category.
- An Effective Policy is an aggregate of the policy assigned to an asset or folder and all of the policies above it in parent folders.
- RMM Package support is deprecated. If you have any recurring invoices still with RMM Package line item types, they will cease to function until updated.
- Saved Asset Searches using a Policy filter have been put into read only mode until those are updated. This functionality has been replaced by a customer selection/policy folder selection control instead. This will affect any recurring invoices using these Saved Asset Searches. These recurring invoices will continue to function for another 30 days, at which time these will need to be updated or they will cease to function.
- The way to create a new RMM Agent Installer is greatly simplified.
- The "Policy" condition of Automated Remediations has been deprecated, and any remediations using this Asset Policy condition will need to be updated.
See our new Policies article for full details.
Assets & Policies tab
We endeavored to initially disrupt your policy settings as little as possible. Let's look at Assets & Policies tab in one customer to see what the migration changed.
- We start by creating a top-level folder with the same name as the customer. All of the customer's assets will be in there in one or more sub-folders.
- The migration looks at all the policies used by the customer's assets, then creates a folder for each of those policies and names them the same as the policies (look at the POLICY column). By default, these folders are collapsed, so just click the arrow to their left to expand them.
- Inside each of those policy folders are all the assets that have that specific policy. By default, the assets themselves do not have a policy because they inherit the policy of the folder they reside in, along with any applicable policies higher up in the inheritance tree.
- You can add folders inside folders, up to five levels deep, not including the top-level Customer folder.
See our Policy Inheritance article for full details.
Add or edit a policy to see the following.
- Policy Name at the top.
- On the left is a navigation panel to access specific policy categories, with a number in parenthesis indicating the number of sections enabled/disabled for that category. Click one to access it. Policy Overview is a read-only view of exactly what this policy does.
- On the right when you first access the page, you will see a read-only view of everything enabled or disabled on the policy. In the old model, you would see all possible sections listed and would need to individually select each relevant item. Now you will only see sections that have been explicitly added or disabled on the policy.
- Once you click a policy category in the left nav, there is a dropdown at the top that lets you add sections not already activated, unless they all have been activated, in which case the dropdown will not be shown.
- For those sections already activated, there is an X in the upper right of each to delete them.
- One key difference is that, in the old model, if a policy item checkbox was unchecked, Syncro simply ignored the setting as though it did not exist. In the new model, an unchecked box in the current policy is considered disabled by Syncro, effectively overriding the same policy item in any parent policy above it. A policy item is ignored only if it has not been added to a policy at all.
If a feature is enabled, same thing—it will override any parent feature above it that is disabled.
Will installers created before migrating to policy inheritance still work?
Yes, but they will install at the top folder and you will need to move them to the folder you want. We recommend re-downloading all new installers.