End User Communication

It’s good practise to communicate with end users about the rollout and implementation of EPM. You'll want to address:

• The change in behaviour required to elevate processes
• How users request elevations not covered by a EPM policy
• The planned date of change

The Change in Behaviour Required to Elevate Processes

Users will need to follow a new pattern to run processes as administrator. It’s important to communicate this new interaction to end users before an environment has been hardened with EPM. An email or meeting to demonstrate the appropriate usage of EPM can help users welcome the change.

To run a program as administrator, users will need to right-click the application and select “Run as Administrator with EPM”.

Based on the policy set or if an end user is part of a group in Learning Mode, they will either be prompted to enter their credentials or to contact the sysadmin for assistance.

If a user is allowed to proceed, they will see a UAC prompt asking for administrator credentials. Instead of fetching a set of administrator credentials, a user will then enter their own credentials. The user will proceed running the process as administrator.

or

If a user is not allowed to elevate the process , the user will be advised to contact their System Administrator for assistance.

How Users Request Elevations Not Covered by a EPM Policy

If a user is not allowed to elevate a process, they will see a dialog box advising them to contact their system administrator. The dialog box that is presented to a user contains a configuarble contact field. You may use this field to list an email address, phone number or extension, or statement such as "Open a service ticket".

Be sure to communicate the appropriate method in your rollout communication.

The Planned Date of Change

Don't forget to to tell end users when they are to change their behaviour for elevating processes and how to request new elevations after rollout.