Solution for server manager error

You might encounter a server manager error when you launch bots using the virtual window. This topic will help troubleshoot if you counter that problem.

Prerequisites

You have successfully created a bot to deploy with virtual window. See Using virtual window for picture in picture.
Note: Child sessions (picture-in-picture mode) is a Microsoft Windows feature. Virtual window is an Automation Co-Pilot feature that uses Microsoft child sessions.

When you deploy a bot with virtual window, you might encounter an error message that relates to the server manager. This does not occur for every instance but when it does occur, you can follow these steps to resolve this issue.

Example of the error message: Server manager error message.

Procedure

  1. Modify the settings for the individual server as follows:
    1. Open the server manager.
    2. Navigate to Sever Manager > Properties.
      This page allows you to modify the setting at the individual server level.
    3. Select the Do not start Server Manager automatically at logon setting.
  2. Modify the settings at the central level by using group policy as follows:
    1. Log in to domain controller.
    2. Launch Group Policy Management console.
      You can start the Group Policy Management console when you navigate to Server Manager > Tools > Group Policy Management.
      Note: If the Group Policy Management is not visible, then you can add this as a feature in Server Manager > Add Roles and Features.
    3. Create GPO in domain where all server machines belong.
    4. Navigate to Computer Configuration > Policies > Administrative Templates > System > Server Manager in the Group Policy Management editor.
    5. Right click the Do not display Server Manager automatically at logon setting.
    6. Click Edit.
    7. Select Enabled to enable the setting.
    8. Click OK to close the Group Policy Management console.
      When the policy is applied, the server manager will not launch when you run your bot with virtual window.
      Note: The policy will be applied based on the Group Policy refresh interval for your device. If the policy is not applied then run the gpupdate /force command.