目次 x
    Ensuring Successful Cloning of a New ServiceNow Instance with ScreenMeet Settings
    • 23 Jan 2025
    • 2 読む分
    • 印刷する
    • 闇
      光
    • PDF
    目次

    Ensuring Successful Cloning of a New ServiceNow Instance with ScreenMeet Settings

    • 更新日 23 Jan 2025
    • 2 読む分
    • 印刷する
    • 闇
      光
    • PDF
    The content is currently unavailable in Ja - 日本語. You are viewing the default English version.
    記事の要約

    Overview

    In order to ensure ScreenMeet works properly in a cloned environment, please follow the steps below.

    Confirming successful cloning/transfer of ScreenMeet settings

    The steps below are to ensure the cloning process pulled in all of the required ScreenMeet options. In general, with a full cloning process, these values will likely exist though the section below serves as a way to confirm.

    • Ensure that the ScreenMeet application was included in the instance cloning process

    • Ensure that the application registry for ScreenMeet connect exists

      • Add the link below to the end of your ServiceNow URL or navigate to System oAuth → Application registries

      • now/nav/ui/classic/params/target/oauth_entity_list.do%3Fsysparm_query%3DnameSTARTSWITHScreenMeet%2520Connect%26sysparm_first_row%3D1%26sysparm_view%3D%26sysparm_choice_query_raw%3D%26sysparm_list_header_search%3Dtrue

      • The client secret/application registry entry should look identical to the screenshot below with the proper client secret.

    • Ensure that the Service account for ScreenMeet was included in the cloning process

      • Ensure that the service account exists and has the requisite ScreenMeet roles

      • IMPORTANT: Ensure that the service account password is the same or reset it / note it for the next section.

    • Ensure that the preexisting ScreenMeet role assignment is assigned to any/all users.

      • Agents, admins, Service account.

    Service Account Setup

    After confirming that the cloning process propagated all of the required settings, the organization will need to be configured.

    This is primarily due to the fact that it is treated as a new ScreenMeet organization.

    • As a user with the ScreenMeet admin role assigned to your ServiceNow profile

      • navigate to console.screenmeet.com and select ServiceNow

      • Login to the instance using the instance URL and your credentials.

      • Press “allow” on the ScreenMeet connect prompt.

    • Once logged in, navigate to Organization → Settings and Policies → ServiceNow configuration.

    • Enter the service account username and password for the given organization and press save.

    • IMPORTANT: press configure and validate ServiceNow instance.

      • a successful configuration + validation process is required in order for the integration to work successfully

      • If this process fails, generally the service account username or password is invalid

      • alternatively, the clone may have not propagated one of the required settings in the section below.

    • Once you have configured the service account successfully, the integration should work as expected at a basic level.

    Service Account Setup

    Since the ScreenMeet organization is unique, product features (such as where files are stored, feature enablement, etc) must be reconfigured for that given unique organization.

    You may go through the organization settings and policies and adjust the settings as desired, or reach out to ScreenMeet via our support desk to import your settings from a pre-existing organization.

    この記事は役に立ちましたか?
    What's Next