Overview

When .NET is updated to an incompatible version on a Core Server, you may have any of these issues:

• Unable to launch core server activation utility
• Queries do not expand when starting tasks that target queries or scopes
  
• Unresponsiveness on the console
• Inventory Scans not processing
  
• Other issues
  

The most efficient and accurate way to determine which version of .NET is installed Navigate to the following registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\Version

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\Version

Compatibility

This document contains compatibility information for .NET and EPM/LDMS:

.NET Considerations for EPM/LDMS on the Core and Remote Consoles

Issues

If you are experiencing the activation issue, you may see:

"Unhandled exception has occurred in your application. "

 

Click details and you see the below errors:

 

"See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.OutOfMemoryException: Array dimensions exceeded supported range.

at System.Diagnostics.TraceUtils.GetRuntimeObject(String className, Type baseType, String initializeData)

at System.Diagnostics.TypedElement.BaseGetRuntimeObject()

at System.Diagnostics.ListenerElement.GetRuntimeObject()

at System.Diagnostics.ListenerElementsCollection.GetRuntimeObject()

at System.Diagnostics.TraceInternal.get_Listeners()

at System.Diagnostics.TraceInternal.WriteLine(String message)

at LANDesk.ManagementSuite.Diagnostics.LogForNet.Init()

at LANDesk.ManagementSuite.Diagnostics.LogForNet.GetLogger(String loggerName)

at LANDesk.ManagementSuite.Licensing.ActivateCore.ActivateCoreForm.get_Log()

at LANDesk.ManagementSuite.Licensing.ActivateCore.ActivateCoreForm.ActivateCoreForm_Load(Object sender, EventArgs e)

at System.Windows.Forms.Form.OnLoad(EventArgs e)

at System.Windows.Forms.Form.OnCreateControl()

at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

at System.Windows.Forms.Control.CreateControl()

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll

----------------------------------------

LANDesk.ManagementSuite.Licensing.ActivateCore

Assembly Version: 9.60.0.0

Win32 Version: 9.60.3.64

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Licensing.ActivateCore.exe

----------------------------------------

System.Windows.Forms

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1068.2 built by: NETFXREL3STAGE

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

LANDesk.ManagementSuite.Licensing.Activation

Assembly Version: 9.60.0.0

Win32 Version: 9.60.3.71

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Licensing.Activation.DLL

----------------------------------------

LANDesk.ManagementSuite.Database

Assembly Version: 9.60.0.0

Win32 Version: 9.60.3.68

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Database.DLL

----------------------------------------

LANDesk.ManagementSuite.Diagnostics

Assembly Version: 9.60.0.0

Win32 Version: 9.60.2.105

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Diagnostics.DLL

----------------------------------------

System.Configuration

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Core

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

System.Xml

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Web

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1069.1 built by: NETFXREL3STAGE

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Web/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.dll

----------------------------------------

LANDesk.ManagementSuite.KeyValue

Assembly Version: 9.60.0.0

Win32 Version: 9.60.2.48

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.KeyValue.DLL

----------------------------------------

System.Data

Assembly Version: 4.0.0.0

Win32 Version: 4.6.1055.0 built by: NETFXREL2

CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

LANDesk.ManagementSuite.Data

Assembly Version: 9.60.0.0

Win32 Version: 9.60.3.59

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Data.DLL

----------------------------------------

LANDesk.DataServices

Assembly Version: 9.60.0.0

Win32 Version: 9.60.3.50

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.DataServices.DLL

----------------------------------------

LANDesk.ManagementSuite.Information

Assembly Version: 9.60.0.0

Win32 Version: 9.60.3.72

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/LANDesk.ManagementSuite.Information.DLL

----------------------------------------

log4net

Assembly Version: 1.2.10.0

Win32 Version: 1.2.10.0

CodeBase: file:///C:/Program%20Files/LANDesk/ManagementSuite/log4net.DLL

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box."

           

Resolution

This problem is caused by .NET  You can remove .NET:

The .NET 4.6 update can often be found as KB 3045560 - https://support.microsoft.com/en-us/kb/3045560

• On Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, or Windows Server 2008 R2 SP1, Microsoft.NET Framework 4.6 is installed under Programs and Features in Control Panel.
• On Windows 8 or Windows Server 2012, Update for Microsoft Windows (KB3045562) is displayed under Installed Updates in Control Panel. (KB is for .Net Framework 4.6)
• On Windows 8.1 or Windows Server 2012 R2, Update for Microsoft Windows (KB3045563) is displayed under Installed Updates in Control Panel. (KB is for .Net Framework 4.6)

• On Windows 8 or Windows Server 2012, Update for Microsoft Windows (KB3045562) is displayed under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.1)
• On Windows 8.1 and Windows Server 2012 R2, it's listed asUpdate for Microsoft Windows (KB3102467) Or KB4014510under theInstalled Updates in Control Panel (KB is for .Net Framework 4.6.1)
• On Windows 10 you can find this as Update for Microsoft Windows (KB3102495)under theInstalled Updates in Control Panel (KB is for .Net Framework 4.6.1)

• On Windows Server 2012 you can find this as Update for Microsoft Windows (KB3151804) under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.2)
• On Windows 8.1 / Windows Server 2012 R2 you can find this as Update for Microsoft Windows (KB3151864) under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.2)
• On Windows 10 you can find this as Update for Microsoft Windows (KB3151900) under Installed Updates in Control Panel. (KB is for .Net Framework 4.6.2)

.NET 4.7 Redistributable:

• .NET Framework 4.7 for Windows 7/Windows Server 2008 R2: KB3186497
• .NET Framework 4.7 for Windows Server 2012: KB3186505
• .NET Framework 4.7 for Windows 8.1/Windows Server 2012 R2: KB3186539
• .NET Framework 4.7 for Windows 10 Version 1607/Windows Server 2016: KB3186568
• .NET Framework 4.7 Language Packs for Windows Server 2012: KB4015882
• .NET Framework 4.7 Language Packs for Windows 8.1/Windows Server 2012 R2: KB3186606
• .NET Framework 4.7 Language Packs for Windows 10 Version 1607/Windows Server 2016: KB3186607

.NET 4.7.1

• On Windows 7 SP1 and Windows Server 2008 R2 SP1, the Microsoft.NET Framework 4.7.1 is listed as an installed product under the Programs and Features item in Control Panel.
• On Windows Server 2012, it’s listed as Update for Microsoft Windows (KB4033345) under the Installed Updates item in Control Panel.
• On Windows 8.1 or Windows Server 2012 R2, it's listed as Update for Microsoft Windows (KB4033369) under the Installed Updates item in Control Panel.
• On Windows 10 Anniversary Update, Windows 10 Creators Update and Windows Server 2016 it’s listed as Update for Microsoft Windows (KB4033393) under the Installed Updates item in Control Panel.

In addition, the removal of a .NET version may cause configuration issues for IIS, so it is recommended to check the following:

• Verify and re-enable services (run services.msc)
  • Set the World Wide Publishing Service to Automatic, then start IIS manager to verify
  • Applicable SQL services, depending on your configuration
  • Applicable LANDESK, Intel and Managed Planet services, depending on your configuration
• Verify IIS configuration affected by .NET
  • Application Pools should look like this:  (unless you have built custom app pools)

            *** If you have made any of the above adjustments, reboot your server ***

• Verify that the https binding on the Default Web Site has the appropriate certificate
• Check for ISAPI and CGI restrictions (set all to allow)

• We do not recommend the following registry tweak. This will fix the activation but doesn't fix the other issues known with .Net 4.6

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework

You'll probably find a useRyuJIT DWORD value of 1 there. Set it to 0.


Then, create a useLegacyJIT DWORD value into the same registry key and set it to 1.

Exception! ParseLocalConnectionString Parameter name: local_connection_string

stuck while checking database pre-requisites or error may occur any time the database is accessed via coredbutil.exe

This document will cover a few different things that can contribute to getting this error message. The very first step to confirm this error message is to launch coredbutil.exe located here:

"C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe"

or

%LDMS_HOME%CoreDbUtil.exe 

This communication works with SSL and Microsoft's Internet Information Services ( IIS ) to complete the connection. Here is the error message that you will most likely get while launching CoreDbUtil.exe

Now that we have identified that the utility CoreDbUtil.exe is unable to launch, let's proceed with some of the easier steps to correct this issue first.

Solution #1 Ensure IIS is running

For good measure, restart IIS using the following steps

1. Open an elevated command line
2. Type "iisreset" and hit enter

You should see IIS stop (if started) and then start back up

Solution #2 Check bindings in IIS for https / port 443

Here are the steps to check the bindings on 443.

1. On the Core Server open IIS manager
2. Right-click on a Default Web Sie
3. Select Edit Bindings...
   
4. Select the binding for https / port 443 and then go to Edit...
   
5. On the next screen, we will want to make sure that the hostname field is blank.

Solution #3   Check Configure LANDESK Software Services and the Windows registry key HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local

1. For this step, we will be checking the Windows Registry key to make sure it is not blank, and matches what is seen under “Configure LANDESK Software Services”. Let's go ahead and launch “SvcCfg.exe”. Usually you can launch this application by clicking on start then searching for Configure Services. If your system is unable to find it, here is the full path: "C:\Program Files\LANDesk\ManagementSuite\SvcCfg.exe" or %LDMS_HOME%SvcCfg.exe
   
   Take note of the Server,  Username and Database. While we have Configure Services open, we should test the login for the Database
2. Put a space after the password and then delete the space
3. Click apply.  Afterward, you should get a prompt telling you to restart the service if everything is accurate. ( You must restart the services that use the database before your changes will take effect. )
   
4. Next we need to open Regedit then browse to:  HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local
5. Make sure that the name of the Database, name of the Server, and User all match the information found in step 1
6. Check to make sure that the value of IsNTLM is set to false

Solution #4   Check to make sure TLS 1.0/1.1 is enabled

The easiest way to enable TLS 1.0/1.1 is going to be with a tool named IIScrypto. Click here to download the tool IIScrypto. When you first launch the tool IIScrypto, everything might be grayed out. Double click on TLS 1.1 to enable it.

Click apply and then restart the Windows Server / Core Server. Now follow the same steps on the SQL Server. Once both Windows Servers come back up, let's go ahead and try to launch CoreDbUtil.exe one more time.

If CoreDbUtil.exe launched successfully, you should now be able to proceed with your upgrade or login.

Solution #5 Check that IIS Application Pools are using the correct  .NET CLR Version.

On the Core Server open IIS Manager. Application Pools should look as follows:

Solution #6 Check that ISAPI and CGI Restrictions are allowed at the IIS Server level

Solution #7 Check if any proxy server is used in IE - Options - Connections

Issue

EPM 2018.1 Core Server installation is failing on the step "Configuring Identity Server"

Log file on the Core Server LANDesk.Install.LDMS_%DATE%%TIME%.log reports:

2018-05-25 09:37:54 ERROR: Error running method: ConfigureStandalone Message: Exception has been thrown by the target of an invocation.

2018-05-25 09:37:54 ERROR: Error running method: ConfigureStandalone Message: Configuration file tps.config does not have root <configuration> tag (C:\ProgramData\LANDESK\ServiceDesk\My.IdentityServer\tps.config line 2)

Solution

Modify the following file:

• C:\ProgramData\LANDESK\ServiceDesk\My.IdentityServer\tps.config

And change the <Configuration> </Configuration> tags to <configuration> </configuration>. Then click Try Again and the installation should proceed.

Contact Ivanti Support if these steps don't resolve this issue

We get the following error message when upgrading to 2018.1

2018-05-30 07:06:49 INFO: Executing: D:\LANDesk\ManagementSuite\ldlogon\rainstall.exe /delayextensioninstall /dontmove /vroot=ldms.vroot /extension=lclxsvc.dll /install /cert=registry          (Launcher.ExecuteCommandEx())

2018-05-30 07:06:53 ERROR: Execution of CBA8InstallCommand completed. Return code: 2, State: Failure                 (SetupController.ExecuteCurrentCommand())

We already tried cbacleanup.exe and iisreset - unfortunately without success.

Anyone have a solution?

Issue

Core Server Activations can fail for a number of reasons, below is a list of some of the main things to check when activation is failing. This is not an all inclusive list but should cover most known issues.

Solution(s)

1. Verify that you can ping license.landesk.com from your core server; (ip address may vary)
   Ensure the registry key for Provider is set to LEGACY on the core.HKLM\software\LANDesk\managementsuite\licensing\provider OR HKLM\software\wow6432Node\LANDesk\managementsuite\licensing\provider)
   
2. Disable any AV that you may have running when attempting to activate.
3. Delete the contents in the LANDESK\Authorization files folder.
4. Locate the current windows temp folder using the %temp% command, then delete the contents in that folder.
5. Verify the "CertName" value under [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\Setup] matches the value of the certificate file name under Landesk\Shared files\keys
   
6. Open the .0 file with notepad, verify the key=CertName
   
7. In the Shared Files\Keys folder on the core, be sure that the hash.0 file (that is bound to IIS) matches what is in the protect.ini file.
   
8. Verify that the LANDesk Management Usage Service is running on the core. Restart if you suspect an issue.
9. Check to see if you can activate the license on another core. This will prove or disprove an issue with the license itself. If an issue with the license is found then you should work with licensing.landesk.com to resolve.
   
   
   If your core activates successfully but you are still unable to login, you should check the verification date and grace period for your license to make sure it has not expired. Also verify the Product Name(s) and Product Version(s) for your license are correct.
   
10. Verify that the activating user belongs to the core's Built-in Administrators group.
11. Check the ldpgp files - Best Known Method for Troubleshooting Remote Console Activation Error
12. If these steps still don't work, reinstall the version of LANDESK that you are currently on. If on a flat of 9.5 or 9.6, just reinstall the flat version. If on a service pack, reinstall of the service pack is all that's needed.

• Description
• Renewing Subscription customers
• Activating the Core Server Online
• Manually Activating the Core Server

Description

LANDESK Management Suite and Security Suite licensing is managed using online activation.  A Core Server must be activated using this online activation before it will be functional.

Also, different features of LANDESK can be enabled or disabled with simple activation.  Installation of additional software is not usually needed.

Renewing Subscription customers

For renewing subscription Customers, simply reactivate your core.

Start | All Programs | LANDesk | Core Server Activation and clicking the Activation button.

Activating the Core Server Online

Complete an online activation of the Core Server using the following steps:

1. Run the Core Server Activation from the Start menu LANDesk Management group.
2. Enter valid credentials and click 'activate'.
3. The Licensing server will be accessed and the Core Server will be activated.

Note: Clicking on the Licenses... button will display the licenses received through the activation process.

Manually Activating the Core Server

Complete a manual core server activation by:

1. Run the Core Server Activation from the Start menu.
2. Enter valid credentials and click 'activate'.
3. The Licensing server will be accessed and the Core Server will be activated.
4. An error box will appear specifying a file has been created that must be e-mailed to licensing.
   
     A *.txt file is created in \program files\LANDesk\Authorization Files
   
   
5. Obtain the .txt file and e-mail the file to licensing@landesk.com.
6. When the new activation e-mail is returned a .AUTH file will be attached to the email. Place the attached .auth file in \Program Files (x86)\LANDesk\Authorization Files.  Ensure the file does not have a .TXT extension, it must have a .AUTH extension.

No further action is needed.  The core is activated upon placing a valid .auth file in the above folder.

Note: Clicking on the Licenses... button will display the licenses received through the activation process.

Important! If you run the core server activation and it appears to be successful, but you are unable to log into the console check to make sure that your license is valid for the product you are trying to use.  For example, if your credentials are valid for Management Suite 8.8 but you are trying to use Management Suite 9.0, the console login will fail.

Problem:

1. LDMS setup creates a SA user with a random password if you select SQL Express database during installation. The password can't be recovered. It has to be changed.

2. Unable to log into the SQL Express server because of a lost SA password.

Solution / Workaround:

Follow the steps below to reset the lost SA password. You may need domain admin access on the Core.

1. Login to the server as the default user who installed the core
2. Locate SQL Management Studio in the start menu
3. Login with Windows Authentication
4. Once you are logged into the SQL Server use the Object Explorer and locate the SA user. (Security > Logins)
5. Right-click on the SA user and select properties.
6. In the Login Properties update the "Password" and "Confirm Password" fields and click OK

If that doesn't work or if you don't have access to the account that installed LDMS on the core server, try the following steps:

1. Turn off all LANDesk Services (Here is a document that has a PS script to quickly disable all LANDesk services: How to Stop/Start all LANDesk Services at Once? (now with PowerShell)
   
2. Open an admin CMD prompt and Stop IIS (Very important step)
3. Open the Registry and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
4. Change the value of LoginMode from 2 to 1
   
5. Open the "Services" applet in the Control Panel
6. Locate the “SQL Server (LDMSDATA)” entry and open its properties
7. Enter “-m” into the “Start parameters” field
   
8. Start the service
9. Open a Command Prompt as an administrator
10. Enter the command:
    
    osql -S CORENAME\LDMSDATA -E
    
    *Note* Be sure to change CORENAME to whatever your server name is or you will get a big long message saying you messed up.
    
    
11. At the next prompts enter the following commands:
    
    1> alter login sa enable
    2> go
    1> sp_password NULL,'new_password','sa'
    2> go
    1> quit
    
    
12. Stop the “SQL Server (LDMS)” service
13. Remove the “-m” from the Start parameters field
14. Open the Registry and navigate to "HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"
    

    Depending on the SQL install version, the path may be different. You can try searching for "LoginMode" in regedit to find this key as well.

15. Change the value of LoginMode from 1 to 2
    
16. Start the service
17. At this point you should be able to login to Management Studio using the SA user account and the new password you gave it.
18. Once you confirm that you can log into SQL Server with the new SA password, launch LANDesk Configure Services and update the SA password on the General Tab

Description

EPM Tool was originally started in order to remove Landesk (LDMS) from remote consoles and cores. Since then, other features have been added.

EPMTool is capable of the following and listed in the menu structure below:

          MAIN MENU

             Uninistall/ Install Utilities

               A.) Agent Uninstall                    How To: Uninstall the LANDESK Agent

               B.) Console Uninstall                How to remove a 9.6 and 9.6 SP1 console from client machines when the uninstall or reinstall fails

               C.) Remove IIS (in progress)

             Inventory Utilities

               A.) Mini to Miniscn                    .MINI Scan Files In LDSCAN Folder

             Failed Core Install Utilities

               A.) Fix Strong Name                 Strong Name Verification Errors

               B.) Fix .Net for DA                    Issue: Data Analytics Install Fails With .NET 4.7

               C.) Run Streams                      Troubleshooting Failed installs.

             Support Utilities

               A.) Fetch Logs

               B.) Diagnostics

               C.) Network Tests

                         A.) Core to Agent

                         B.) Core to db

                         C.) Custom Host and Port

                         D.) DEP IOS Test

                         M.) MDM Check from Core

               D.) Remove Auth Files               Issue: Unable to Build Core Server Activation File

               E.) COM+ Rebuilder                   How to rebuild the LANDesk COM+ Objects

               F.) EPM Mail (in progress)

               G.)Enumerate Programs

             Service Control

               A.) Stop LANDesk Services

               B.) Start LANDesk Services

               C.) Restart Landesk Services

               D.) Delete ASP .Net Files

Note: If you have issues uninstalling.

Try Microsoft's FixIt tool https://support.microsoft.com/en-us/help/17588 "Fix problems that block programs from being installed or removed"

Current version: 11-28-2017

This batch file is known to work on:

• 9.5SP3
• 9.60 - 9.6SP3
• 2016.0 - 2016.3 Service Update 4
• 2017.1 - 2017.1 Service Update 1
• 2017.3

Note: Attached you will find a batch file and an exe. The exe is the batch file converted so it will use less space.

Description

It is advised to run these steps prior to running any Ivanti installer (Full install or Service Update). There can be instances where an Ivanti EPM installer will fail or run into issues after installation. Below are best practices to follow when installing or updating the Core Server.

Prerequisites

1. Backup or snapshot your core server and your applicable databases (including the Core Server Database and the Workspaces Database).
   • With these backups available, you can quickly restore to a functional state if you run into errors.
     
     
2. Verify that your C drive and the drive you intend to install LANDESK onto have plenty of free space. For full specs, please visit: Ivanti Endpoint Manager 2017 Architecture - Overview
   
   
3. If upgrading to a new full release, verify Licensing for that version is listed in your product license.
   • You can verify this by opening the Core Server Activation and clicking on Licenses. This will show all the version assigned to your credentials.
   • Please contact support if you are missing any versions.
     
     
4. If having to use RDP to connect to your core server when running the install, use the admin switch for the RDP session.
   • This is done by running the RDP application with the admin switch "mstsc /admin".
     
     
5. Disable UAC, anti-virus, malware, and EPS software on the machine for the install.
   
   
6. Download the installer to the computer locally. Do not run from a network drive.
   
   
7. Before extracting the installer, right-click the file and go to Properties to Unblock the installer.
   • In the bottom right-hand corner of the properties window for the installer package there may be an Unblock button or check box. If this is there, unblock the file and then click Apply and OK.
   • It is critical to have the file be unblocked prior to running the LANDesk installer.

     8. Check version of Microsoft .NET that is installed and take actions appropriate for the version of EPM/LDMS that you are installing/updating to.

• You can use this document to check the version you have installed on your core server: How To: Tell What Version of .NET Framework Is Installed
• The following document goes over version specific .NET information and considerations .NET Considerations for EPM/LDMS on the Core and Remote Consoles

     9. DO NOT install the IIS role prior to installing your core. Ivanti will do this for you as part of the installer.

• LANDESK will incur problems during install if IIS is already installed and will not be able to proceed.
  
  

     10. Once the installer has been unblocked and extracted, run Microsoft Streams against the extracted location and install destination folders using the switches -s and -d.

• See the following document for information on how to run Microsoft StreamsStreams; and why you should remove them.
• Additional information on Streams can be found here - Streams
  
  

     11. Check to make sure the boot.wim is not mounted on the Core server.

• Follow this document if it is: How To: Cleanup WIM Images Before Upgrading/Patching Core

     12. Right-click the installer and click "Run as Administrator", even if logged on as an admin on the machine.

Conclusion

Thanks for taking the time to read through these best practices steps. If you have any suggestions to add to this list, please add a comment to this document so we can internally vet those suggestions and update this document as needed.

Hi,

I have an Environment where initial configuration of Windows agent scan option was enabled with auto fix. Which normally take much more time when user run Security scan or policy run the Security scan on the Windows Machine.( Endpoint Manager 2017.x)

What is the impact if we disable auto fix on windows agent configuration settings?

1. Do I need to update all client with the latest installer or

2. I can just disable the option and create new client for new install or

3. Does it automatically detect of disable auto fix so it don't try auto fix when first time scan or consecutive scan?

Overview

This document goes over supported minimum TLS levels for currently supported versions of Endpoint Manager. Minimum assumes that any higher level versions are also enabled.

TLS 1.2 support requires that the operating system and SQL server are properly configured to use TLS 1.2. Ivanti Support will not assist with the configuration of TLS 1.2.

Due to the amount of configuration necessary for TLS 1.2 only to function correctly, restricting your environment to TLS 1.2 only is generally not recommended unless you have a specific compliance need.

Supported TLS Versions

Issue

Remote console install fails during install with error "The Strong name verification system contains exclusion entries in the registry. Blocking access."

Resolution

1. Launch regedit on the computer that the console is being installed on.
2. Navigate to these two locations and delete additional folders beneath these keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\StrongName\Verification

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\StrongName\Verification

Issue

• During the LANDESK Management Suite installation, the Core certificate install to IIS fails
• A pop up window appears, reporting that SecureWebSiteInstall.exe has stopped working
• The installation process stops

Solution

SecureWebSiteInstall.exe runs successfully when the environment variable RANDFILE is not set.

If for some reason (for example because some third party application already set the variable) the environment variable is already set, the executable fails to install the Core certificate to IIS.

• From the Start menu, right click Computer and select Properties, then click on Advanced system settings.
  
• Select Environment variables and remove the RANDFILE variable, verifying both the User and System variables sections.
• Restart the LANDESK Management Suite setup.

When the setup installs successfully the Core certificate to IIS, you will see the following entries in the installation log file names LANDesk.Install.LDMS_yyyy-mm-dd hh_mm_ss.log in the directory %ProgramData%\LANDesk\ManagementSuite\Install\Version#\Log:

INFO: Executing: C:\Program Files (x86)\LANDesk\ManagementSuite\SecureWebSiteInstall.exe "LANDesk_1391606962" landesk/managementsuite/core/ssl landesk/managementsuite/core/ssl/information     (Launcher.ExecuteXmlCommand())

INFO: Notifying ProcessBegin: C:\Program Files (x86)\LANDesk\ManagementSuite\SecureWebSiteInstall.exe     (Launcher.ExecuteXmlCommand())

INFO: Execution of SecureWebSiteInstall_Core completed. Return code: 0, State: Success     (SetupController.ExecuteNextCommand())

Questions:

• When will LANDESK Support Windows Server 2016 as a Core Server?

  • This is supported in the 2017.1 and newer releases.
    
    

• When will LANDESK Support Windows Server 2016 as a remote console?

  • This is available in the 2017.1 SU1 update
    
    

• When will LANDESK Support Windows Server 2016 as a client?

  • This is available in the 2017.1 and later releases
    

  • This is available in the 2016.3 SU3 release

For further Supported Operating System Information: Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager

Issue

Warning: The client public cert was empty! Didn't send it out.

Warning: Failed to send out own cert. Cert may not exist.

During the Advance Agent installation you will see these warnings appear repeatedly in the AdvanceAgent.log file, located in 'C:\Windows\temp\', until the agent.exe is downloaded and installed.

Resolution

This warning is typically cosmetic and can be ignored. If agent installation is unsuccessful, or you see further errors, please contact LANDESK support.

Issue

When installing the Core or Remote Console on a device with .NET 4.7 installed, the Data Analytics install fails.

Resolution

This has been fixed in installers for 2017.3 and beyond.

Workaround

A defect has been opened for this issue internally. However, as a workaround, customer can use the powershell shell script attached to this document to modify the registry keys the DA Installer checks, so the install can proceed.

This script has a few parameters:

Install - Backs up the .NET registry keys to the directory the script is launched from, then changes the Version values to 4.6.01586

Restore - Checks for regkey backups and restores them

Ivanti is not responsible for any damages caused by this script, direct or otherwise. This is NOT an official Ivanti script, and is not supported. This script is provided as-is, with no guarantee or warranty of any kind.

Instructions

1. Save the attached .zip file and extract the contents to a directory of your choice
2. Launch an elevated powershell prompt
3. Change directory to directory of ChangeNetVersion.ps1 (ex. "cd "C:\Scripts\ChangeNetVersionRelease")
4. Run the following command: ./ChangeNetVersion.ps1 + parameter

     Ex: ./ChangeNetVersion.ps1 Install

Updated versions of this script may be attached as issues are reported, if necessary

If this script does not work, perform the manual workaround below:

1. Backup the following registry keys:

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client\1033

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full

     HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full\1033

     2. Right click each key and select Permissions > Advanced then change the owner to yourself. THIS IS REQUIRED.

     3. Right click each key and select Permissions, and give yourself full control.

     4. Change the "Version" string to 4.6.01586 once the keys are backed up.

     5. Continue with the install.

After the Remote Console is installed, double click on your backed up .reg files to restore the old values.you

******* If you still get the same Error after running this script and restarting the computer.  Delete C:\programdata\landesk and then try the Installer again.*********

History

2.0:

• Script now accepts parameters rather than prompting the user, allowing for non-interactive use (deployment package, scripted use, etc)
• Output changed to write-output instead of write-host so output can be piped to a log

1.0:

• Release. Nothing special.

Issue

Upgrading to 2016.3 SU2 failed at running run ld_setup_node.bat

Error

Resolution

Add the following line to the top of the ld_setup_node.bat:

npm set registry https://registry.npmjs.org/

Here is a forum that discusses this fix.

https://github.com/npm/npm/issues/8293

Some say this also worked for them:

npm config set registry https://registry.npmjs.org/

Issue

Running any scans from the console result in The request failed with HTTP status 404: Not Found.

IIS logs shows a response of 404 2

Cause

ISAPI and CGI Restrictions are improperly configured.

Resolution

1. Open IIS Manager
2. Click on the server level
3. Double-click on ISAP and CGI Restrictions
4. Make sure all restrictions are set to allowed.
5. From an administrator command prompt, run IISreset
6. Try again

More Info:

You can view HTTP status codes at https://support.microsoft.com/en-gb/help/943891/the-http-status-code-in-iis-7.0,-iis-7.5,-and-iis-8.0

Description

This is a simple chart designed to quickly reference what the minimum required version a core needs to be on in order to upgrade.

Note: It is recommended to be on the latest service pack or service update level for each version before upgrading. Being on the latest service pack will help reduce problems during upgrade.

• Overview
• Installation
• Database Setup
  • SQL Management Studio
  • Creating The Database
• General Configuration

Overview

This document goes over how to install SQL Server 2016 for use with Ivanti Endpoint Manager(EPM). This document assumes you have downloaded SQL Server 2016 Standard or above (i.e. not SQL Express).

The examples provided are for an environment where SQL Server and EPM are on different servers. However, the steps apply to when both are on the same server as well.

This guide does not take into account requirements for large enterprises or specific SQL Server configurations such as clustering, high availability, performance tuning, replication, etc.

Installation

The steps below will guide you through installing SQL Server 2016.

1. Mount your downloaded SQL Server .iso file. This can be done by double-clicking on the file.
2. Run Setup.exe as an administrator in the mounted disc.
3. Select Installation > New SQL Server stand-alone installation or add features to an existing installation
4. On the next window, check the box to check for updates if you want, then hit next.
5. Head through the subsequent screens until you get to Feature Selection.
6. Install the Database Engine Services feature at least. You may also want to install Reporting Services - Native if you want to run reports, and SQL Server Replication if you're using a Rollup Core as well, and intend to roll up this database. Hit Next.
   
7. On the next page, you can decide on a name for your SQL instance, or leave it at the default. Unless you have a need to name the instance, it's usually easier to just leave it at the default.
8. On the Server Configuration page, you can leave the Service Accounts and Collation at their defaults. Hit Next.
9. On the Database Engine Configuration Page, enable Mixed Mode authentication and specify an SA password. Use "Add current user" to add your windows user to the SQL Server admins, and add anyone else that should have access using the "Add" button.
11. Head to the "Data Directories" tab and specify Data, log and backup directories if you desire. Refer to this document for recommendations based on your node count.
12. TempDB and FileStream tabs can be left at defaults. Hit next.
13. If you decided to install Reporting Services, you'll now have a Reporting Services configuration page. Leave it at "Install and configure" and hit next.
14. Now you're ready to install. Review this final page to see if anything is missing or incorrect. If everything looks good, hit "Install".

Database Setup

SQL Management Studio

Setting up the database will be easiest using SQL Management Studio. To acquire SQL Management studio, you can have 2 main options:

• Download it from here
• Select the "Install SQL Server Management Tools" option in SQL Server Installation Center.

Creating The Database

1. To create the EPM database, launch SQL Server Management Studio and log in.
2. Right click on "Databases" in your Object Explorer, and select "New Database".
4. Name the database, and hit "Ok". The database should then be created.

You can now specify this database during your install of Ivanti Endpoint Manager. The installation will take care of creating the schema and populating the necessary data.

General Configuration

In addition to the above, the below items should be considered regarding overall configuration.

• EPM uses a SQL account. You may want to create a separate SQL account specifically for LDMS instead of using the SA account.
• By default, when a database is created, it uses the Full recovery model. This can cause excessive transaction log growth. Switching to a Simple recovery model is recommended, as long as you create regular backups.
• Check out our database maintenance schedule recommendations here