Purpose
The purpose of this document is to provide a scenario that help you moving a LANDesk Management Suite Core server to a new domain or forest. This scenario is not a step by step but an example to give you a good idea on how you could proceed if you have face that situation.
The following list is not necessarily exhaustive, so you will want to go through each and check that it is suitable for your environment and of course if you wish to add anything else.
Scenario
- create a backup of the current DB (old domain).
- create a new DB on a SQL Server in the new domain and restore the DB from the old domain.
- create a new temp DB on the same SQL Server in the new domain.
- install a new LDMS Core Server in the new domain and point it at the temp DB previously created.
- after the installation of the new Core and before the activation - run the LANDesk Services configuration and point the DB connection string to the backedup DB from the old domain but on the SQL Server on the new domain.
- restart the LANDesk inventory service and activate the new Core - Server in the new domain.
- configure the COM+ components and the Scheduler Service on the new Core in the new domain.
- on the old Core in the old domain, configure the Inventory Service option "Store scans" and create a Windows scheduled task (repeats every hour) that copies the stored scan files to the new Core in the new domain.
- copy the existing agent configuration on the new Core in the new Domain, check the certificate is correct and only the new certificate is selected and check the core name.
- create and advance agent and deploy to the estate using the new core.
Additional information
Moving a Core server to another Domain/Forest - Checklist
http://community.landesk.com/support/docs/DOC-29190
Checklist before moving a LDMS core 9.0 server to a different subnet or site