How to Test a new LDMS version on a new server and later upgrade the Production Database

Version 7

    Verified Product Versions

    Endpoint Manager 2016.xEndpoint Manager 2018.x

    How To



    ATTENTION: These instructions were tested in a test environment but not in a production one. Hence this is not a supported.



    For some reasons, you want to test a new version of LDMS version in the future production infrastructure (New Core Server) but you don't want yet to upgrade the production database.


    The scenario would be;

    • You have LDMS 9.5 Core Server, named LDMS95Core, with the Windows Server 2008R2 OS
    • You have a Database Server, named LDMSDatabase, where the Production Database is which is named LDMSDBPROD
    • You have a brand new server, named LDMS96Core, with the Windows Server 2012R2 OS
    • You have a SQL Server where the Test Database is named LDMS96DBTEST
    • LDMS96Core will be the future Production Core Server with LDMS Core Server version 9.6.
    • LDMS96Core will be also the Test Core Server with LDMS Core Server version 9.6 on which you will




    ATTENTION :It is a "raw" process meaning if you need more detailed steps, you may follow the steps explained in other articles regarding upgrading (See section "Other Interesting Links"). The goal of it is just to give an idea how to proceed for an upgrade from 9.5 to 9.6;


    1. On a SQL Server, create a new database called LDMS96DBTEST
    2. Install 9.6 Core Server on the LDMS96Core server by referring to the DB LDMS96DBTEST > At this stage, you can test the new LDMS version on a Test Database.


    At a point, you may decide to make LDMS96Core server as the 9.6 Production Core Server. Here are the steps:


    1. Do an "In-place" upgrade of the LDMS95Core server > It will then upgrade the LDMSDBPROD DB to version 9.6
    2. On the LDMS96Core server, go to Start > Programs > LANDESK > Double Click on "LANDESK Configure Services" and a Window called "Configure LANDESK Software Services" will open
    3. On tab "General", change the following items to point the DB to the "Production Dabase" called LDMSDBPROD (see below - put also your own credentials of course)
    4. And restart all the LANDESK services (See article How to Stop/Start all LANDESK Services at Once? (now with PowerShell))



    Other Interesting Links: