Assign a Manager to a vOU
Assigning a manager to a virtual organizational unit is straight forward. This configuration policy allows administrators to automatically assign managers to particular users who may be within a certain department or geographical location. Check out this video below for a walk through.
Set a User's Usage Location and Country Details
Setting a user's location settings is a straightforward process with Nova. Setting a configuration policy allows you to instantly change a user's usage location and country settings when placed within a virtual organizational unit. See how to do that here.
In Nova DPC, you are able to add actions to Microsoft Intune configuration policies to your user's mobile devices. For DPC users, this is helpful if you need to modify devices and applications of users you are allowed to manage, directly in Nova. Actions include:
·Syncing your devices
·Automatically locking them
·Instantly begin the process of wiping your devices
·Retire your devices
·Reboot your devices
The devices screen can be found within the Nova Dashboard by clicking manage, then Devices.
To show more details for your device, click on its name. Here, you will find several more tabs, including:
Also on this Device Detail page, you have the opportunity to remove the passcode (for iOS), and reset passcode (Android 7+ versions only).
License Policies in Nova give an administrator (or delegated administrator) the ability to assign/remove licenses, as needed, all from within Nova. Plus, Nova gives visibility into exactly how many licenses are used and how many are available.
The Nova license policies and reports provide:
·The ability to apply licenses according to what has been budgeted and what is required for a specific role
·The ability to show and hide particular licenses to include (or exclude) them from the report page shown above.
·Accurate license intelligence when it comes time for budgeting and Office 365 renewal.
·Delegated license management activities
Similar to other Nova policies, with a license policy you specify who can assign what licenses within a tenant or group. For example, a license policy might enable the Director of Engineering to manage Azure DevOps licenses assigned to users within the Engineering virtual organizational unit.
You can get really granular and specify which workloads from a license you want users to get. For example, if your organization does not use Yammer, you can remove that workload, if desired, before assigning an E5 license to someone. You can also specify how many of a particular license delegated administrators can assign.
Here is what it looks like when you are setting up a license policy:
To set up a license policy:
1.In Nova, go to Manage administration > License policies.
3.Enter a Name for the policy.
4.In the Assignment section, with the Delegate to tab selected, click Add.
5.Select user(s) to whom you will delegate the ability to assign licenses according to the policy, and then click Add.
6.Select the Managed objects tab, and then click Add.
7.Use the Select type drop-down menu to choose whether the licenses can be applied to certain users, groups, and/or organizational units.
8.Locate any users/groups/organizational units containing users to which the licenses can be assigned, select them, and click Add.
9.Select the Licenses tab, and then click Add.
10.Select the tenant containing licenses you will add to the policy.
11.Select the licenses (and specify the maximum number of licenses) and workloads you want those delegated the policy to be able to assign, and then click Add.
After completing these steps, your policy is configured and the user(s) who are delegated the license policy can assign licenses to users specified in the policy.
To hide licenses:
You can hide selected licenses from the licenses report, if desired:
You can also how/hide any hidden licenses by using the toggle option located in the top left of the list.
In many organizations a structure of organizational units will be built, and configuration policies in Nova Delegation & Policy Control can be used across this structure. In this article we will see how the processing of those policies takes place.
In this example we will use this simple organizational unit structure:
If we create a new policy and apply it to the Main-OU organizational unit we have the option to apply to child OUs'. If we select that option, when the policy is applied at the top level, any child OUs will also be affected by the policy:
In this case OU1, and OU2, will also use the same policy that was applied at the Main-OU level.
If we then create a policy and apply it to OU2, we can override any of the impact from the other policy:
In this case, Main-OU and OU1 will use the original policy, and OU2 will use the new policy.