This is great, but you guys REALLY need to fix it so policies can be rebased to new parents. There is too much of a reliance on "do it right from the start" but that's just not a reality in IT. There is no way to predict forward that far. Changing the hierarchical order needs to be added.
The fact that I can't assign a policy based on roles (Hyper-v Guest, Laptop, domain controller, etc.) has kept us from signing up. I don't want my Hyper-V Guest servers patching at the same time as my Hyper-V hosts. I also don't want to have to MANUALLY apply policies to devices. That's a recipe for disaster. When
@@pilotgav3975 can't tell if your trying to be funny. You literally have your master policy, then create a policy based off that which inherits rules you specify. Then apply that globally or to the tenant. It takes all of 5 mins to setup a single time...
This is great, but you guys REALLY need to fix it so policies can be rebased to new parents. There is too much of a reliance on "do it right from the start" but that's just not a reality in IT. There is no way to predict forward that far. Changing the hierarchical order needs to be added.
The fact that I can't assign a policy based on roles (Hyper-v Guest, Laptop, domain controller, etc.) has kept us from signing up. I don't want my Hyper-V Guest servers patching at the same time as my Hyper-V hosts. I also don't want to have to MANUALLY apply policies to devices. That's a recipe for disaster.
When
you can just create a policy for your VM's etc, and then just apply it once when on boarding... simple
Yeah, because driving efficiency is based on having to manually manage every one of your machines to update or apply policies.
@@pilotgav3975 can't tell if your trying to be funny. You literally have your master policy, then create a policy based off that which inherits rules you specify. Then apply that globally or to the tenant. It takes all of 5 mins to setup a single time...