I am enabling 'Notify Sponsor' on a device profile rules and the
administrator profile I built does get the email notification when a
device meets the rule. Also any user with the system admin profile are
also getting a email notification. Is there a...
Looking to create a Device Profile Rule to use HTTP/HTTPs Methods and
having issues with the path requirement. Im wanting to do this for
printers with a gui.Here are some examples of what I have tried for
paths:/wcd/spa_main.htmlx.x.x.x/wcd/spa_main....
We have a Device Profile rule acting as our catch all for rogue devices.
We have enabled 'Notify Sponsor'. This rule works and sends emails to a
shared email account. I need to change this email to something else and
I can not seem to find this setti...
What is the best procedure for OOBE Autopilot devices and NAC
integration? We have MDM Connector configured. When ever a new device is
connected it is moved to isolation and cannot continue with OOBE.
Currently our windows devices registered as a hos...
Thank you for you help, I narrowed it down to the Root admin(which has
this disturbed group email assigned to it), I changed that to my email
and it sent to me only when a rogue connected. That being said I cant do
the above changes you mentioned sin...
I thought this would be the case but we have not active mappings that I
can tell tie into 'Notify Sponsor', granted I may be missing it. Here is
the current mappings tied to a notification
None of those options are checked for any of the profiles. We do have a
generic user with the 'help desk' profile in the NAC, this user does
have the disturbed group email added to it (this the email getting the
alerts),I just cant see how this ties ...
Its is Registration but we currently do not allow users to actually
Registration/authentication via Captive Portal. Here is an example of
where we get stuck at in the OOBE process.
