8 minute readApplies to: v4

How to reconfigure Squared Up after moving the Data Warehouse and/or SCOM server

If the SCOM server has moved

If you are able to log in to Squared Up you can edit the SCOM server name by navigating to the right-hand menu ☰ then system and then clicking on the Connections perspective. In the Management Server section type the new SCOM server name in the box next to server-address as shown below, and click apply changes.

Settings Management Server Name

Check that you can log in to Squared Up as a SCOM admin user. Note that your user will need to be a SCOM user on the new SCOM server.

If you are unable to log in to Squared Up, because the SCOM server has already been moved, you can edit the SCOM server name by following the steps described below:

  1. Run notepad as administrator (File, Run, type notepad, and then right-click and select Run as administrator) and then open the following file:

    C:\inetpub\wwwroot\SquaredUpv4\User\Configuration\scom.json

  2. Update the value next to server-address to the new SCOM server name, for example:

    "server-address": "SCOMServer"

    Where SCOMServer should be replaced by your SCOM server name.

  3. Save the file.

  4. Recycle the SquaredUpv4 application pool in IIS.

  5. Check that you can log in to Squared Up as a SCOM admin user.

It is likely that the Data Warehouse location is different for this new SCOM server, so follow the next section to update the Data Warehouse connection for Squared Up.

If the Data Warehouse has moved

If the Data Warehouse has moved you will need to update the connection and ensure that the application pool identity has the correct permissions to the Data Warehouse database.

First, ensure that you have updated the Data Warehouse connection for SCOM by following all the steps in the Microsoft article: How to Move the Data Warehouse Database

1. Edit the Data Warehouse connection

If you are able to log in to Squared Up you can edit the Data Warehouse server name by navigating to the right-hand menu ☰ then system and then clicking on the Connections perspective. In the Other Connections section type the new Data Warehouse server name in the box next to data-warehouse as shown below, and click apply changes. Continue to the next section to Configure the Data Warehouse permissions

Settings Data Warehouse Server Name

Alternatively, you can edit the Data Warehouse connection by editing connections.json and recycling the application pool as described below:

  1. Run notepad as administrator (File, Run, type notepad, and then right-click and select Run as administrator) and then open the following file:

    C:\inetpub\wwwroot\SquaredUpv4\User\Configuration\connections.json

  2. Update the value next to Data Source to the new Data Warehouse server name, for example:

    {
    "data-warehouse": "Data Source=DataWarehouseServer;Initial Catalog=OperationsManagerDW;Integrated Security=True"
    }

    Where DataWarehouseServer should be replaced by your Data Warehouse server name.

  3. Save the file.

  4. Recycle the SquaredUpv4 application pool in IIS.

Continue to the next section to Configure the Data Warehouse permissions

2. Configure the Data Warehouse permissions

  1. On the Squared Up server log in to Squared Up as a SCOM admin user, who is also a SQL sysadmin for the Data Warehouse database. If the user you are logged in as does not have SQL sysadmin permissions then you may need to Configure the Data Warehouse permissions manually

  2. Browse to http://localhost/SquaredUpv4/setup?stage=datawarehouse

    This gives the application pool identity a SQL server login with the OpsMgrReader role for the Data Warehouse database.

    When using Windows authentication this step must be carried out on the Squared Up server.

3. Check graphs are shown

  1. Check that graphs are shown in Squared Up, for example a server page. You may need to wait a few moments and refresh the page.

    Performance graph

  2. If performance graphs, sparklines or bar charts are not shown, you may need to Configure the Data Warehouse permissions manually.

  3. If you still experience problems see the article Troubleshooting The Data Warehouse Connection.

Troubleshooting: When Squared Up doesn't pick up the correct Data Warehouse connection

This procedure can be useful if you know the SCOM server name but not the Data Warehouse server name, or if you have just installed Squared Up and completed the setup wizard but the SCOM server or Data Warehouse server names are incorrect.

1. Check Squared Up is pointing to the correct SCOM server

Open the file C:\inetpub\wwwroot\SquaredUpv4\User\Configuration\scom.jsonand check that the SCOM server name is correct. If it is not correct, edit it by running notepad as an administrator as described above.

2. Check the Data Warehouse connection for SCOM

  1. Check the SCOM Data Warehouse connection by running the following PowerShell command in the Operations Manager Shell:

    Get-SCOMDataWarehouseSetting

    If this shows the incorrect information then you need to update the Data Warehouse connection for SCOM by following all the steps in the Microsoft article: How to Move the Data Warehouse Database

  2. Run Get-SCOMDataWarehouseSetting again to check that SCOM now has the correct Data Warehouse location.

3. Pick up the new Data Warehouse location from SCOM and give the application pool identity the correct permissions

  1. Delete the following file:

    C:\inetpub\wwwroot\SquaredUpv4\User\Configuration\connections.json

  2. Recycle the SquaredUpv4 application pool in IIS.

  3. On the Squared Up server log in to Squared Up as a SCOM admin user, who is also a SQL sysadmin for the Data Warehouse database. If the user you are logged in as does not have SQL sysadmin permissions then you may need to Configure the Data Warehouse permissions manually

  4. Browse to http://localhost/SquaredUpv4/setup?stage=datawarehouse

    This gets Squared Up to pick up the Data Warehouse location from SCOM and update the file connections.json. It also gives the application pool identity permissions to the Data Warehouse database.

    When using Windows authentication this step must be carried out on the Squared Up server.

  5. Check that graphs are shown in Squared Up, for example on a server page. You may need to wait a few moments and refresh the page.

    Performance graph

  6. If you still experience problems see the article Troubleshooting The Data Warehouse Connection.

  7. Check that the C:\inetpub\wwwroot\SquaredUpv4\User\Configuration\connections.json file has been recreated and shows the new Data Warehouse server name.

    If connections.json has not been created or is blank, it could be that Squared Up is not able to write to connections.json. If Squared Up cannot write to connections.json it caches the new setting in memory, but will lose this setting when restarted. If Squared Up is unable to write to connections.json it is likely to be due to the Squared Up application pool not having the correct permissions to the Squared Up folder structure. You can reset the correct permissions by following this article: How to check and modify the application pool identity

If you have created any dashboards using the SQL tile connecting to the Data Warehouse, you may need to change the connection string in each SQL tile to reference the new Data Warehouse location (instead of "global:dw")

Troubleshooting the Data Warehouse connection

How to configure the Data Warehouse connection

How to configure the Data Warehouse permissions manually

How to check and modify the application pool identity

Squared Up Ltd. (c) 2018Report an issue with this article