Date: Fri, 29 Mar 2024 01:20:30 -0400 (EDT) Message-ID: <1896281989.773.1711689630979@confluence0.its.appstate.edu> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_772_1344547249.1711689630978" ------=_Part_772_1344547249.1711689630978 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In the case where standard device management policies inte= rfere with the University academic and/or business processes and an alterna= tive solution cannot be reached, a user may request an exclusion from a spe= cific management policy. An example of this would be a computer used in a r= ecital hall needing to be excluded from the traditional forced reboot sched= ule to prevent reboots during a recital.
In those cases, a user that is responsible for the device may submit a s= upport request for a Management Policy Exclusion, along wi= th a justification, and the IT Consultant will begin the Mana= gement Policy Exclusion process. The = workflow will be reviewed by a representative from IT Support Se= rvices, IT Infrastructure and Systems, and the Office of Information Securi= ty for approval before excluding the device from a management policy.
The end-user that is the responsible party for the device that nee=
ds the exclusion, can request the exclusion through a Computer Assistance Request. &=
nbsp;The IT agent will then start the internal process by submitting the Management Policy Exclusion request in Jira under IT Agents.=
An exclusion will last 365 days from the final approval date. Afte= r 365 days, the user will get a notification prompting them to review the m= anagement exclusion and they can send it through the approval process again= to continue the exclusion for another 365 days.
There is no limit to the number of exclusions re= quested per computer, but a consultant should only submit one request per computer. Additional exclusions requested should go on the = original Jira ticket. This is to ensure we track one Jira ticket per c= omputer.
Risk/Responsibility Acceptance
You, the responsible party, will be responsible for maintaining the = device in a secure, patched, and supportable state once a management policy= exclusion has been applied.