- This topic has 5 replies, 3 voices, and was last updated 1 year, 10 months ago by .
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
- You must be logged in to reply to this topic.
I’m starting to get annoyed with Dell now. The documentation is plentiful but poor. It just lists the things that I can see in front of me, doesn’t tell me why or how I’m supposed to use anything.
I set up some groups in WMS but I can’t add anything to them. I can add devices to the default group but not my newly created sub groups. The “help” tips don’t explain anything, just some garbled message “Note: Device Exception might not work with a new group Configuration due to Policy inheritance”. What does that mean?
Is there a guide for creating and using groups anywhere or any instructions that can actually be followed?
Have you given your new groups an own group token?
CG
No we’re not using group tokens.
You cannot assign any clients to a group without a group token.
Group tokens are a must-have.
CG
Ah OK. The manual doesn’t make this clear, and WMS allows you to create the groups without tokens suggesting it is optional.
This note from the WMS Admin Guide suggests I don’t have to use tokens in a private cloud, hence the confusion.
> NOTE: For a public cloud, the group token for an unmanaged group must be enabled to register devices. For a private cloud, the group token for an unmanaged group is automatically enabled.
That note is specific to the ‘unmanaged group’, the place all your devices will go when they don’t have group tokens assigned (defa-quarantine). Interesting that you could create groups without a group token, didn’t know that was an option. I guess maybe that would be valuable if you wanted to create a custom parent group to apply policy to a set of devices but also wanted to segment that device set for more granular policy.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |