Cireson Self Service Portal Database Migration

If you are planning to move the Service Manager database, you should also need to move the Cireson Service Desk Portal to the same instance.

  1. Stop the Cache Builder service and Platform Cache service.
  2. Stop the IIS application pool and website hosting the Cireson portal.
  3. Back up the ServiceManagement database.
  4. Restore it in the new SQL instance of Service Manager.
  5. Run the installer for the Cireson Portal again pointing to the new SQL server\instance when prompted.
  6. Verify the connection strings have been updated appropriately in theĀ Cireson.CacheBuilder.WindowsService.exe.configĀ file.
  7. Ensure the cache builder service, application pool, and website have successfully started.

Related Posts

Service Manager Reporting Server Database Migration

In the previous post, I explained the steps of moving the Service Manager Data Warehouse databases to another SQL instance. In this post, I will share the…

Service Manager Data Warehouse Database Migration

Microsoft has documented in details how to move Service Manager Data Warehouse databases to another SQL instance. Do not attempt to move the Reporting Services database in…

In-place OS Upgrade of Service Manager Data Warehouse

In this post, I will show the steps for in-place upgrade of Service Manager Data Warehouse management server (2019) OS from Microsoft Server 2016 to 2019. The…

Installing Zebra printer driver with SCCM

In order to install Zebra printer driver to the computers with SCCM, you will first need to extract the driver content from the exe file. Deselect all…

In-place OS Upgrade of Service Manager Data Warehouse Server

In this post, I will show the steps for in-place upgrade of Service Manager Data Warehouse management server (1801) OS from Microsoft Server 2012 R2 to 2016….

In-place OS Upgrade of Service Manager

In this post, I will show the steps for in-place upgrade of Service Manager management server (1801) OS from Microsoft Server 2012 R2 to 2016. The OS…