I'm Upgrading. What Has Changed?
When upgrading from a version of Bomgar previous to 14.1, you will find some significant changes to the structure of the settings in the administrative interface. Be assured that your settings have been preserved. This section outlines some of the changes and the ways Bomgar has retained your setup.
Existing representative permissions have been preserved for user accounts, group policies, embassies, and embassy users. This has been effected by applying a custom session policy to each user object as appropriate.
The options Prompt customer for approval of these actions in attended sessions and Prompt customer for approval of these actions in unattended sessions have been removed. Instead, the categories of Attended Session Permissions and Unattended Session Permissions allow for greater differentiation between attended and unattended session behavior. Your existing prompting preferences have been carried over to the new categories.
The settings available in rep invite security profiles and session policies are virtually identical. Therefore, rep invite profiles are now configured as part of session policies. For a session policy to be available as a rep invite profile, the Rep Invite Availability option must be checked.
Each existing rep invite profile has been added as a new session policy and has been enabled for Rep Invite.
Because support portals can have associated session policies, the support portal used for each Jump Client has been made visible. For Jump Clients deployed from within a support session, the associated public portal is the same public portal which was used for the original session. If the Jump Client was deployed from the mass deployment wizard, the default public portal will be used. Remember that you can modify the associated public portal from the Jump Client interface of the representative console.
Additionally, the Jump Client Prompting Rule has been removed. Instead, if you had any Jump Clients with a prompting rule other than Follow Rep Permission, one or more session policies will have been pre-created.
If a Jump Client had a prompting rule of Never, it will use the session policy [Prompting Rule: Never]. This session policy sets the permission Enable Prompting to None and leaves all other permissions undefined.
If a Jump Client had a prompting rule of Always, it will use the session policy [Prompting Rule: Always]. This session policy sets the permission Enable Prompting to All. It also sets the prompting Timeout to 30 Seconds and the Default Response to Deny. All other permissions are left undefined.
If a Jump Client used Follow Rep Permission as its prompting rule, it will not have a session policy automatically applied.
While public portals may now have associated session policies, no session policies will be automatically applied.