Management and Security powered by Landesk
Installing and running Workspaces without a Service Desk installation
If you are a Ivanti® Endpoint Manager powered by Landesk customer that doesn't have a Ivanti Service Desk license or installation, you can follow these steps to install and run Workspaces. These steps only apply to customers who will be running the Service Update 4 and Workspaces combo pack.
There are three main parts in this process:
- Core server preconfiguration
- Restore the Service Desk SQL database to your SQL Server
- Configure the Workspaces database connection
Part 1: Core server preconfiguration
- Download a SQL Server Service Desk database backup self-extracting file:
- Run the self-extracting executable.
- Restore the database to your SQL Server by following the steps in the next section.
- Run the Endpoint Manager 2016.2 (SU 4) with Workspaces install from the Ivanti download site.
- Once the install finishes, Configuration Center will automatically launch after the server is rebooted and the first login.
Part 2: Restore the Service Desk SQL database to your SQL Server
If you are an SQL Server customer, contact your corporate DBA in order to restore the database on the same SQL Server that the Ivanti core database is running on. The DBA will need to provide the database server name, a valid database user and password for use later in the configuration.
If you are an SQL Express customer, follow these steps:
- If you haven’t already downloaded SQL Server Management Studio for SQL Express and installed on the core, do so from Microsoft.com at
- Open SQL Server Management Studio and connect to the SQL Express instance on your core server.
- When prompted for the server name, use <CoreServer>\LDMSDATA. Use Windows Authentication.
- Expand the root node in the tree.
- Right-click on Databases and choose Restore Database…
- Click on the “Device” radio button.
- Click on the “…” button to select the backup file (*.bak) in the folder you used for the self-extracting database backup.
- Click “Add” button.
- Locate the backup file required from part 1 step 4 above and select the file making sure to choose your correct language file. Note that en_* is American English and eng_* is British English.
- Click OK from the “Locate Backup File” window.
- Click OK from the “Select backup devices” window
- Under the “Destination” section of the “Restore Database” window, you can enter a new name for the database, or just keep the default. Note the name of the database to be used later in Configuration Center.
- Click OK in the “Restore Database” window to restore the database.
- Close the “Database successfully restored” dialog and validate that the database exists in SQL.
- If they aren't there already, add Network Service and System as users in SQL Server Management Studio by following steps 16-19.
- Under the Security node, right-click Logins and click New Login.
- Click the Search button.
- Click OK in the Select User or Group dialog box and in the Login - New Window.
- Repeat steps 16-19 for the System user if necessary.
For the database you restored, add db_owner roles for both the System and Network Service by double-clicking the login for each, which opens the “Login Properties” dialog box. Select "User Mapping", select the database you restored, and select the db_owner check box.
- Follow the steps in the next section to finish configuring Workspaces.
Part 3: Configure the Workspaces database connection
- Within Configuration Center, click “Create Standard Instance” link.
- Leave the instance name set to “My”.
- Enter the database connection information for the restored workspace database. Note: SQL Express customers should use <CoreServerName>\LDMSDATA as the server name.
If you're using SQL Express locally on the core server and you've followed the steps above, select “Integrated Security”. If you're using another SQL server/database, provide the credentials to access the database. The user must have db_owner access.
- Click “Test Connection” to make sure the connection works.
- Click OK.
- You should be taken to the edit page for the “My” instance.
You can close your browser, Workspaces is now configured. If Configuration Center launched automatically after the upgrade and reboot, closing it will continue the user’s login. If you kept the default instance name, the Workspaces URL is http://<CoreServerName>/my.bridgeit.
Was this article useful?
The topic was:
Not what I expected
Copyright © 2017, Ivanti. All rights reserved.