Quantcast
Channel: Ivanti User Community : Document List - Installation
Viewing all 272 articles
Browse latest View live

Error: "Failed to send out own cert. Cert may not exist." during Advance Agent installation

$
0
0

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: Data Analytics Install Fails With .NET 4.7

$
0
0

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.

 

The script may fail to run, saying the execution of scripts is restricted. Running either of the following commands can address this.

Set-ExecutionPolicy Unrestricted

Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted (if the above command fails)

 

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

$
0
0

Issue

Upgrading to 2016.3 SU2 failed at running run ld_setup_node.bat

 

Error

 

2017-06-07 16:12:26 INFO: Execution of AtlasCreateWindowsEnrollMentWebsite completed. Return code: 0, State: Success(SetupController.ExecuteNextCommand())
2017-06-07 16:12:26 INFO: Executing command AtlasConfigureNode(SetupController.ExecuteNextCommand())
2017-06-07 16:12:26 INFO: Executing: D:\landesk\EnrollmentServer\ld_setup_node.bat(Launcher.ExecuteXmlCommand())
2017-06-07 16:14:55 ERROR: Execution of AtlasConfigureNode completed. Return code: 1, State: Failure(SetupController.ExecuteNextCommand())

 

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/

Error: Running any scans from the console results in error: "The request failed with HTTP status 404: not found"

$
0
0

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

About the minimum version required for upgrades

$
0
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.

 

Minimum Database Version -
For upgrading an existing database
Minimum Core Version - The minimum version for an in-place upgrade
Destination Version - The target version that you'll be upgrading to.
9.59.52016.0
9.5 SP39.5 SP32016.3
9.609.602017.1
9.609.602017.3
2016.32016.32018.1

Installing and Setting Up SQL Server 2016 For Ivanti Endpoint Manager

$
0
0

 

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.
    Screenshot_10.png
  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.
  10. Screenshot_11.png
  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".

     Screenshot_12.png

       

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.

Screenshot_13.png

 

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".
  3. Screenshot_14.png
  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

Best Known Method for Reinstalling Landesk Console.

$
0
0

1) Run the EPM Tool.  EndPoint Manager (EPM) Tool

 

- Option B for Console removal.

- C to continue the un-install.

- This will also remove the agent from the machine.

- Restart the machine.

 

2) Run the install for the target version again.

 

- If the machine has .net 4.7 then you will need to run this script. (This is only for 2017.1 and earlier.  2017.3 and newer will not have this issue) Issue: Data Analytics Install Fails With .NET 4.7

- After running this script you will need to reboot the system. ( to reload the registry.)

- In some cases some of the software might be left over so you will want to run this tool to double check that there are not any entries for: Data Analytics, Landesk or Ivanti:

 

Microsoft fix it tool (This is just in case something did not get removed.) : https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed

 

Click on uninstalling then it will populate a list for you.   After each program you run,  You need to run the tool again.

 

3) Run the install software.

 

4) Then apply any SU udpates.

 

5) Re deploy the Agent for the machine.

Upgrade fails on "Removing Commands website" "Removing Mobility website"

$
0
0

Problem:

When upgrading core version 9.6 to any later install, it may fail on "Removing Commands website" or "Removing Mobility website"

Removing commands website.PNG

When looking at the install logs, it appears similar to this:

error logs.PNG

The key here is: "delete app /app.name: "Default Web Site" /landesk/commands"

 

Cause:

The current new upgrade installer is trying to delete a Commands application or Mobility application that is not found in IIS on a core with a current 9.6 install.

 

Solution:

Convert the Commands/Mobility folder in IIS to an application if the folder exists. If it doesn't exist it will need to be created

 

1) Open IIS> Expand core server > Sites> Default Web Site> landesk> Right click Commands> Convert to Application

converttoapplication.png

Simply press "OK"

add application click ok.png

 

At this point, if you have repeated this step for Commands and Mobility, the upgrade of the core console can be continued. If it is still failing because it is found that the Commands or Mobility do not exist, either of those folders will need to be created manually, by right clicking the "landesk" subpage and selecting "Add Application". Type in the respective folder like the following capture, and then continue the upgrade.

mobilty creation.png


Core Server Installation with an Upgraded Database: Supported Versions

$
0
0

Description

 

When performing core server installation, the user will be given the option to configure a new database or to upgrade an existing database. This article aims at clarifying the supported versions for core server installation with an upgraded database on LDMS 9.6, LDMS 2016.3 and EPM 2017.1.

 

LDMS 9.6

The options are:

Upgrade an existing 9.5 database

Upgrade an existing 9.0 database

9.6.png

 

LDMS 2016.3

The options are:

Upgrade an existing 2016 database

Upgrade an existing 9.5 SP3 or 9.6 database

2016.3.png

 

EPM 2017.1

The options is:

Upgrade an existing database (Once clicking on this node pop-up message will show it only supports version 9.6 and above)

2017.1.png

How to install Ivanti Endpoint Manager 2017.3

$
0
0

This document covers how to install Ivanti Endpoint Manager 2017.3.

 

Ivanti Endpoint Manager was previously known as LANDESK Management Suite.

 

Note: The documentation refers to not doing installations over a Remote Desktop Protocol (RDP) session.  However, it is acceptable to use an RDP session if using the /ADMIN switch to open a console session to start your installation to a remote server

Verifying Ivanti Endpoint Manager ( EPM ) 2017.3 file Ivanti2017-3.exe

$
0
0

Verifying Ivanti Endpoint Manager ( EPM ) 2017.3 file Ivanti2017-3.exe

 

c:\windows\system32\certutil.exe -hashfile Ivanti2017-3.exe sha256

SHA256 hash of file Ivanti2017-3.exe:
938c889272e7462460da49b03afaf3487a860b4fcf8f54cd17ae4a44bedf4dbf

 

c:\windows\system32\certutil.exe -hashfile Ivanti2017-3.exe sha1

SHA1 hash of file Ivanti2017-3.exe:
b70f8ca542c1298721e59633aaa027afcfe51ab2

 

 

REFERENCES:

 

Ivanti Endpoint Manager 2017.3 Download

 

certutil | Microsoft Docs

Prerequisites for installing the Ivanti’s Endpoint Manager ( EPM ) version 2017.3 core server

$
0
0

Prerequisites for installing the Ivanti’s Endpoint Manager ( EPM ) version 2017.3 core server

 

Internet Information Services

Internet Information Services must be installed, started and properly configured

 

Operating System

Valid operating systems include: Windows Server 2012 R2 and Windows Server 2016

 

Computer Name

A computer name with 15 characters or less is required

 

FIPS Cryptography

FIPS Compliant System Cryptography must not be enabled

 

Memory

8 GB of RAM is highly recommended

 

Reboot Pending

The operating system cannot have a reboot pending. Restart the machine before proceeding with the current install

 

Credentials

You must be logged in as an administrator on this machine

 

Domain Controller

This machine must not be a domain controller

 

Root Certificate Configuration

Only self-signed certificates should be found in “Trusted Root Certification Authorities”. For details see https://help.ivanti.com/docs/help/en_us/LDMS/10.0/default.htm#cshid=RootCertificateConfiguration

 

doc epm 2017.3 prerequisites screenshot 01.png

 

doc epm 2017.3 prerequisites screenshot 02.png

How to troubleshoot the core server installation (advanced)  - EPM 2017.1 and later

$
0
0

This document will follow in a linear format the EPM 2017.1 Core Server installation showing the steps that it takes, log snippets, and will contain markers of known issues at certain places in the installation.

 

 

Log Files, Order of Operations and Locations

 

When troubleshooting the installation it can be important to get a list of all of the logs sorted by the last modified date in order to find the proper log for that timeframe of the installation.   A list of some of the log files for installation can be found by looking for *.log under C:\ProgramData\LANDesk.

 

Additional log files will be under \Program Files\LANDESK\ManagementSuite\log.

 

LogFilesAndLocations2.png

 

Initial Setup and Prerequisite Checks

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD Time.log

 

Log Example:

 

PreReqLog.png

What can go wrong at this point

 

  1. Checking for Online Updates
  2. Selecting installation language (The options are English (United States), Chinese (Simplified),  Chinese (Traditional), French (France), German (Germany), Japanese, Korean, Portuguese (Brazil) and Spanish (International)
  3. Accepting the End User License Agreement (EULA)
  4. Selection of what you want to install.  (Core Server, Remote Console, or Rollup Core Server)
  5. The following list of needed pre requisites is displayed (If you click the checkbox for "Check all prerequisites")
    PreReqs.png

    Typically at this point, IIS Configuration and .NET Framework are the prerequisites missing.   However, heed warnings and ensure proper memory and disk space is available.

 

IIS Configuration

 

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\IIS7_Scripted_Install.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD Time.log

 

Search for String in Log File: "

 

What can go wrong at this point:

 

The IIS Configuration consists of the following:

 

- IIS Web Server role (IIS Web Server Role must be installed)
- Windows Process Activation Service (Windows Process Activation Service)- IIS 6 Management Compatability (IIS 6 Management Compatibility)

 

The IIS Installation Log file is located here: C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\IIS7_Scripted_Install.log

 

The installation logging starts in the C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD Time.log with the following DISM command:

 

 

2017-08-30 06:47:12 INFO: Executing: dism.exe /online /Quiet /NoRestart /enable-feature /ignorecheck /featurename:IIS-WebServerRole /featurename:WAS-WindowsActivationService
/featurename:WAS-ProcessModel /featurename:IIS-IIS6ManagementCompatibility /featurename:IIS-Metabase /LogPath:C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\IIS7_Scripted_Install.log (Launcher.ExecuteCommandEx())

 

From this point as specified in the /LogPath portion of the DISM command line logging of the scripted IIS installation is logged in

C:\ProgramData\LANDesk\ManagementSuite\Install10.1.10Log\IIS7_Scriped_Install.log

 

 

Database Selection and Configuration

 

At this point, the choice to either Configure a new database or Upgrade an existing database is made.

 

Either SQL Express or Microsoft SQL Server can be selected.

 

If SQL Express is entered the following the installation moves directly to the next step of selecting the install path.

 

If selecting the Microsoft SQL Server option the following screen is presented:

 

SQLFields.png

 

For the purposes of this document, we will select SQL Express.

 

Selection of installation path

 

Typically at this section, only the drive letter will be changed if necessary.  Please ensure that an ample amount of space is available, at a minimum the recommended available free space of 50gb.

 

Log files updated:

 

At this point in the process, the following useful information is written to the C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD Time.log file:

 

2017-08-30 07:51:36 INFO: Installation Information

Feature: Core Server

Language: English (United States)

Database Action: Populate New Database

Certificate: LANDesk_1504079451

Installation Folder: C:\Program Files\LANDesk\ManagementSuite

 

Database Information

Database Application: SQL Express

Server: 2017-1\LDMSDATA

Database: ulddb

Port: Auto-detect

User: sa

Selection of Security Client Management (Client Certificate-based Security)

 

For more information about Client Certificate-Based Security) see LDMS 2016 Enhanced Security Mode

 

Log files updated: C:\ProgramData\LANDesk\Install\Log\NonSelfSignedCert.log

 

Installation of Microsoft Visual C++ Runtime Engines

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD Time.log

2017-08-30 07:51:36 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\14\vc_redist.x64.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:38 INFO: Executing: C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Data\Main\bin\Resources\PreInstall\landesk.common.runmethod.exe<args> (Launcher.ExecuteCommandEx())

2017-08-30 07:51:41 INFO: Executing command VC11Command (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:41 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\11\vcredist_x86.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:43 INFO: Execution of VC11Command completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:43 INFO: Executing command VC11Commandx64 (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:43 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\11\vcredist_x64.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:44 INFO: Execution of VC11Commandx64 completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:44 INFO: Executing command VC12Command (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:44 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\12\vcredist_x86.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:46 INFO: Execution of VC12Command completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:46 INFO: Executing command VC12Commandx64 (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:46 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\12\vcredist_x64.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:48 INFO: Execution of VC12Commandx64 completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:48 INFO: Executing command VC14Command (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:48 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\14\vc_redist.x86.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:50 INFO: Execution of VC14Command completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:50 INFO: Executing command VC14Commandx64 (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:50 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Microsoft Visual C++ Redistributable\14\vc_redist.x64.exe /q (Launcher.ExecuteCommandEx())

2017-08-30 07:51:50 INFO: Execution of VC14Commandx64 completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:51 INFO: Executing command AccessDatabaseEngine (SetupController.ExecuteCurrentCommand())

Configuring the Microsoft Access Database Engine 2010 Redistributable

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD Time.log

2017-08-30 07:51:51 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Redistributables\AccessDatabaseEngine\AccessDatabaseEngine_x64.exe /q

Configuring the Web Server Role

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\IIS7_Scripted_Install.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 07:51:56 INFO: Executing command IISConfiguration2012 (SetupController.ExecuteCurrentCommand())

2017-08-30 07:51:56 INFO: Executing: dism.exe /Online /Quiet /NoRestart /enable-feature /all /featurename:IIS-WebServerRole /featurename:IIS-CommonHttpFeatures /featurename:IIS-StaticContent /featurename:IIS-DirectoryBrowsing /featurename:IIS-HttpRedirect /featurename:IIS-ApplicationDevelopment /featurename:IIS-ASP /featurename:IIS-CGI /featurename:IIS-ISAPIExtensions /featurename:IIS-ManagementConsole /featurename:IIS-ServerSideIncludes /featurename:IIS-Security /featurename:IIS-WindowsAuthentication /featurename:IIS-WebServerManagementTools /featurename:IIS-BasicAuthentication /featurename:IIS-ClientCertificateMappingAuthentication /featurename:NetFx4Extended-ASPNET45 /featurename:IIS-ApplicationInit /featurename:IIS-ISAPIFilter /featurename:IIS-ManagementService /featurename:IIS-NetFxExtensibility45 /featurename:IIS-ASPNET45 /featurename:WCF-HTTP-Activation45 /featurename:Windows-Identity-Foundation /LogPath:C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\IIS7_Scripted_Config.log

Registering .NET Framework 4 with IIS

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 07:52:45 INFO: Executing: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i -enable (Launcher.ExecuteCommandEx())

2017-08-30 07:52:45 INFO: Execution of IIS4Registration completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

Adding the SNMP feature

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\SNMP_dism.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 07:52:45 INFO: Executing: dism.exe /Quiet /NoRestart /Online /Enable-Feature /FeatureName:SNMP /LogPath:C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\SNMP_dism.log (Launcher.ExecuteCommandEx())

2017-08-30 07:52:51 INFO: Execution of SNMPFeature completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

Determining Host Settings

  • C:\ProgramData\LANDesk\log\LANDesk.LANDesk.Common.RunMethod_YYYY-MM-DD time

2017-08-30 07:52:51 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="GetFQDN" commandLine="" (Launcher.ExecuteCommandEx())

2017-08-30 07:52:51 INFO: Execution of SystemActionsGetFQDN completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

Configuring Additional Websites

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\WebSiteConfiguration.msi.log

2017-08-30 07:52:52 INFO: Executing: msiexec.exe /i "C:\Users\Administrator\Desktop\Retail\Resources\WebSiteConfiguration.msi" /lvx "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\WebSiteConfiguration.msi.log" /q REBOOT=ReallySuppress INSTALLLEVEL=90 ENABLEEXEC=1 INSTALLDIR="C:\Program Files\LANDesk\ManagementSuite" IISDIR="C:\inetpub\wwwroot" (Launcher.ExecuteCommandEx())

Installing the Core Server

  • C:\ProgramData\LANDESK\Log\apmservice.log - Installation of the Policy Server service.
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Setup.LDMS.msi - logs laying down of the main core server components and files
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\ServerConfig.msi.log - Logs additions such as the licensing executable and Configure Services.
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\ConsoleConfiguration.msi - Logs installation of the LDMS console itself
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\Framework.msi.log - Installation of the common framework files
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_YYYY-MM-DD time.log - Runs Framework.msi and addres registry keys relating to the uninstall strings for the common framework
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 07:52:56 INFO: Executing: msiexec.exe /i "C:\Users\Administrator\Desktop\Retail\LD\MS\landesk software.msi" /q /lv+ "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\LANDesk.Setup.LDMS.msi.log" SILENT_INSTALL=1 LDLANG=ENU INSTALLDIR="C:\Program Files\LANDesk\ManagementSuite" CORESERVER=2017-1 LANDESK_CORE_TYPE=1 LDINSTALLTYPE=1 ESTSIZE=1593835 ORGANIZATION="Unspecified"

Creating Com+ User

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:00:37 INFO: Executing command LDCreateComPlusUserNoMSI (SetupController.ExecuteCurrentCommand())

2017-08-30 08:00:37 INFO: Executing: rundll32.exe "C:\Users\Administrator\Desktop\Retail\Resources\ldmsinst.dll",_LDCreateComPlusUserNoMSI 0, 0, 0, 0

Configuring Scheduler COM

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:00:38 INFO: Executing command LDRegisterSchComNoMSI (SetupController.ExecuteCurrentCommand())

2017-08-30 08:00:38 INFO: Executing: rundll32.exe "C:\Users\Administrator\Desktop\Retail\Resources\ldmsinst.dll",_LDRegisterSchComNoMSI 0, 0, 0, 0

 

Creating Scheduler Service

  • C:\ProgramData\LANDesk\log\SchedSvc.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:00:40 INFO: Executing command Service_SchedSvc_Install (SetupController.ExecuteCurrentCommand())

2017-08-30 08:00:40 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\SchedSvc.exe /i

Configuring MBSDK - UplDirRC

  • C:\ProgramData\LANDesk\log\LANDesk.LANDesk.Common.RunMethod_YYYY-DD_MM Time
  • C:\Program Files\LANDesk\ManagementSuite\log\MBSDK.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:08 INFO: Executing command ConfigureUplDirAsync (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:08 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="ModifyTextFile" commandLine="C:\Program Files\LANDesk\ManagementSuite\upl\async_basepath.asp;SimpleReplace;ASYNCDIR;C:\Program Files\LANDesk\ManagementSuite\MBSDK\AsyncFiles"

Configuring Internet Settings

  • C:\ProgramData\LANDesk\log\LANDesk.LANDesk.Common.RunMethod_YYYY-DD_MM Time
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:33 INFO: Executing command ConfigCenterRemoveNegotiateProvider (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:33 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/ConfigurationCenter" /section:system.webServer/security/authentication/windowsAuthentication /-"providers.[value='Negotiate']" /commit:apphost

Registering COM Servers

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:10 INFO: Executing command RegisterCOMServersConsole (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:10 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\Install Only Files\launchapp.exe runlist=RegisterCOMConsole.txt "ldms=C:\Program Files\LANDesk\ManagementSuite" "ldmain=C:\Program Files\LANDesk\ManagementSuite\ldmain"

Installing winpcap-nmap

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:13 INFO: Executing command WinPcapCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:13 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\winpcap-nmap-4.13.exe /S

 

Setting folder permissions

  • C:\Program Files\LANDesk\ManagementSuite\log\SetNTFSPermissions.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:14 INFO: Executing command SetPermissionsOnKeysFolder (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:14 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\SetNTFSPermissions.exe /R "C:\Program Files\LANdesk\Shared Files\keys" administrators:W system:W "LANDesk Administrators:W" "network service:R" "LANDeskComPlus:R" aspnet:R wamuser:R IISAnon:R

Installing Framework

  • C:\ProgramData\LANDesk\Framework\Install\11.0\Log\Framework.msi.log
  • C:\ProgramData\LANDesk\Framework\Install\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log
  • C:\Program Files\LANDESK\ManagementSuite\log\Framework.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:16 INFO: Executing command FrameworkInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:16 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\Framework\setup.exe /s Feature=Feature1 InstallDir="C:\Program Files\LANDESK\Framework"

Installing Configuration Center

  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\ConfigCenter.msi
  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:27 INFO: Executing command ConfigCenterInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:27 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\ConfigCenter\setup.exe /s Feature=Feature1 InstallDir="C:\Program Files\LANDESK\ConfigurationCenter"

Removing the Negotiate Provider for Configuration Center

  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:33 INFO: Executing command ConfigCenterRemoveNegotiateProvider (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:33 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/ConfigurationCenter" /section:system.webServer/security/authentication/windowsAuthentication /-"providers.[value='Negotiate']" /commit:apphost

Disabling Anonymous authentication for Configuration Center

  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:34 INFO: Executing command ConfigCenterDisableAnonymousAuth (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:34 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/ConfigurationCenter" /section:system.webServer/security/authentication/anonymousAuthentication /enabled:"False" /commit:apphost

Disabling Basic Authentication for Configuration Center

  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:34 INFO: Execution of ConfigCenterDisableAnonymousAuth completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:34 INFO: Executing command ConfigCenterDisableBasicAuth (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:34 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/ConfigurationCenter" /section:system.webServer/security/authentication/basicAuthentication /enabled:"False" /commit:apphost

Disabling Forms Authentication for Configuration Center

  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:35 INFO: Executing command ConfigCenterDisableFormsAuth (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:35 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/ConfigurationCenter" /section:system.web/authentication /mode:Windows

Installing Workspaces

  • C:\ProgramData\LANDesk\BridgeIT\Install\LANDesk.Install.LDMS_YYYY_MM_DD time.log
  • C:\ProgramData\LANDesk\ConfigurationCenter\Install\11.0\Log\BridgeIT.MSI.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:35 INFO: Executing command BridgeITInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:35 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\BridgeIT\setup.exe /s Feature=Feature1 InstallDir="C:\Program Files\LANDESK\BridgeIT"

Installing Identity Server

Log Files Used or Updated:

  • C:\ProgramData\LANDesk\IdentityServer\Install\10.5\Log\IdentifyServer.msi.log
  • C:\ProgramData\LANDesk\IdentityServerInstall\11.0\Log\LANDesk.Install.LDMS_YYYY_MM_DD time.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:41 INFO: Executing command IdentityServerInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:41 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\IdentityServer\setup.exe /s Feature=Feature1 InstallDir="C:\Program Files\LANDESK\Identity Server"

Copying Mobility Files

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:49 INFO: Executing command AtlasCopyFiles (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:49 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="DirectoryCopy" commandLine="C:\Users\Administrator\Desktop\Retail\LD\Mobility\Core\LDMain;C:\Program Files\LANDesk\ManagementSuite;true"

Copying Mobility Console files

  • C:\ProgramData\Log\LANDesk.Common.RunMethod_YYYY-MM-DD time

2017-08-30 08:01:53 INFO: Execution of AtlasCopyConsoleFiles completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:53 INFO: Executing command AtlasRouterXMLRemoveLines (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:53 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="ModifyTextFile" commandLine="C:\Program Files\LANDesk\ManagementSuite\routersxml\Mobile.Router.xml;RemoveLinesWithPattern;.BES5"";"

Restoring Mobility Configuration Files

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:54 INFO: Execution of AtlasRouterXMLRemoveLines completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:54 INFO: Executing command AtlasRouterXMLAddAssemblyPath (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:54 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="ModifyTextFile" commandLine="C:\Program Files\LANDesk\ManagementSuite\routersxml\Mobile.Router.xml;SimpleReplace;AssemblyPath="""";AssemblyPath=""C:\Program Files\LANDesk\ManagementSuite\Mobile.Handlers.dll"""

 

Updating Mobility Configuration

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:54 INFO: Executing command AtlasRouterXMLAddAssemblyPath (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:54 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="ModifyTextFile" commandLine="C:\Program Files\LANDesk\ManagementSuite\routersxml\Mobile.Router.xml;SimpleReplace;AssemblyPath="""";AssemblyPath=""C:\Program Files\LANDesk\ManagementSuite\Mobile.Handlers.dll"""

Resetting IIS

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:01:55 INFO: Executing command IisReset1 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:01:55 INFO: Executing: C:\Windows\System32\iisreset.exe

Configure SmartVue Registry

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:06 INFO: Executing command SmartVueAddPointCoreRegistry (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:06 INFO: Executing: reg.exe add HKLM\SOFTWARE\Landesk\ManagementSuite\Setup /v PointCore /t REG_SZ /d "2017-1" /f

Copying SmartVue files

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:06 INFO: Executing command SmartVueCopyFiles (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:06 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="SystemActions" Method="DirectoryCopy" commandLine="C:\Users\Administrator\Desktop\Retail\LD\SmartVue\LDMain;C:\Program Files\LANDesk\ManagementSuite;true"

Creating the Installer Information File

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:17 INFO: Executing command InstallerConfigFile (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:17 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="InstallerInfoXml" Method="CreateInstallerInfoXml" commandLine="10.1.10.0;en-US;C:\Program Files\LANDesk\ManagementSuite;C:\Program Files\LANDESK;LDMSInstallerInfo.config"

Configuring IIS Settings

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:19 INFO: Executing command AddIsapiCgiRestrictions_PostCgi (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:19 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="IISActions" Method="AddIsapiAndCgiRestriction" commandLine="C:\Program Files\LANDesk\ManagementSuite\incomingdata\postcgi.exe;True;PostCgi;CBA8 Alert Receiver"

 

Configuring Server Shortcuts

 

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\ServerConfiguration.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:20 INFO: Executing command ServerConfiguration (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:20 INFO: Executing: msiexec.exe /i "C:\Users\Administrator\Desktop\Retail\Resources\ServerConfiguration.msi" TRANSFORMS="C:\Users\Administrator\Desktop\Retail\Resources\en-US\ServerConfiguration-en-US.mst" /lvx "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\ServerConfiguration.msi.log" /q REBOOT=ReallySuppress INSTALLLEVEL=90 ENABLEEXEC=1 TARGETDIR="C:\Program Files\LANDesk\ManagementSuite" ADDLOCAL=CoreServer

Configuring Console Shortcuts

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\ConsoleConfiguration.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:24 INFO: Executing command CoreConsoleConfiguration (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:24 INFO: Executing: msiexec.exe /i "C:\Users\Administrator\Desktop\Retail\Resources\ConsoleConfiguration.msi" TRANSFORMS="C:\Users\Administrator\Desktop\Retail\Resources\en-US\ConsoleConfiguration-en-US.mst" /lvx "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\ConsoleConfiguration.msi.log" /q REBOOT=ReallySuppress INSTALLLEVEL=90 ENABLEEXEC=1 TARGETDIR="C:\Program Files\LANDesk\ManagementSuite"

Configuring SSL settings for ServerAuthentication website

  • C:\ProgramData\LANDesk\ManagementSuite\log\LANDesk.WebServer.Configure.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:27 INFO: Executing command WebSiteConfig-ServerAuthentication-SSL (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:27 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "http://localhost/landesk/managementsuite/core/ServerAuthentication" /section:access /sslFlags:SslNegotiateCert /commit:apphost

Configuring SSL settings for PreferredServer website

  • C:\ProgramData\LANDesk\ManagementSuite\log\LANDesk.WebServer.Configure.exe.log

2017-08-30 08:02:28 INFO: Executing command WebSiteConfig-PreferredServer-SSL (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:28 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "http://localhost/landesk/managementsuite/core/PreferredServer" /section:access /sslFlags:SslNegotiateCert /commit:apphost

Configuring SSL settings for WSVulnerabilityCore website

  • C:\ProgramData\LANDesk\ManagementSuite\log\LANDesk.WebServer.Configure.exe.log

2017-08-30 08:02:29 INFO: Executing command WebSiteConfig-WSVulnerabilityCore-SSL (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:29 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "http://localhost/WSVulnerabilityCore" /section:access /sslFlags:SslNegotiateCert /commit:apphost

Configuring IIS Buffer Settings

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:32 INFO: Executing command IISBufferSettings1 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:32 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "http://localhost/WSVulnerabilityCore" /section:system.webServer/serverRuntime /uploadReadAheadSize:1073741824 /commit:apphost

Configuring IIS Settings

C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:33 INFO: Executing command IISRequestFilteringSettings1 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:33 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "http://localhost/ldlogon/antivirus8" /section:system.webServer/security/requestFiltering /-"hiddenSegments.[segment='bin']"

Adding the Web Server Role

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:33 INFO: Executing command IISRequestFilteringSettings1 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:33 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "http://localhost/ldlogon/antivirus8" /section:system.webServer/security/requestFiltering /-"hiddenSegments.[segment='bin']" (Launcher.ExecuteCommandEx())

2017-08-30 08:02:35 INFO: Execution of IISRequestFilteringSettings1 completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:35 INFO: Executing command SetExecutionPolicy (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:35 INFO: Executing: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe Set-ExecutionPolicy Unrestricted (Launcher.ExecuteCommandEx())

Adding Encryption

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:41 INFO: Executing command LDCryptoConfigUtilityCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:41 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LDCryptoConfigUtil.exe /symmAlgorithmId=AES /symmKeySize=256 /symmBlockMode=CBC

Installing SQL Express

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:02:43 INFO: Executing command SQLExpressInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:02:43 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="SqlExpressConfiguration" Method="SqlExpressInstall" commandLine="C:\Users\Administrator\Desktop\Retail\Resources\SQLServerExpress\en_sql_server_2016_express_with_service_pack_1_x64_9540756.exe;LDMSDATA;ENU"

Installing SQL System CLR Types

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\SQLServerSystemCLRTypes.Install.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:15:37 INFO: Executing command SQLServerSystemCLRTypesInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:15:37 INFO: Executing: msiexec.exe /i "C:\Users\Administrator\Desktop\Retail\Redistributables\SQLServer\SQLSysClrTypes.x64.msi" /lvx "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\SQLServerSystemCLRTypes.Install.msi.log" /q REBOOT=ReallySuppress

Installing SQL  Shared Management Objects

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\Log\SQLServerManagementObjects.Install.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:15:38 INFO: Executing command SQLServerSharedManagementObjectsInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:15:38 INFO: Executing: msiexec.exe /i "C:\Users\Administrator\Desktop\Retail\Redistributables\SQLServer\SharedManagementObjects.x64.msi" /lvx "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\SQLServerSharedManagementObjects.Install.msi.log" /q REBOOT=ReallySuppress

Creating database

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:15:42 INFO: Executing command MSCreateSQLExpressDatabase (SetupController.ExecuteCurrentCommand())

2017-08-30 08:15:42 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="SqlExpressConfiguration" Method="CreateSQLExpressDatabase" commandLine="2017-1\LDMSDATA;LDMSDATA"

Setting database option: Auto close to off

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:15:46 INFO: Executing command SetSQLExpressDatabaseAutoCloseToOff (SetupController.ExecuteCurrentCommand())

2017-08-30 08:15:46 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="SqlExpressConfiguration" Method="SetSQLExpressDatabaseAutoCloseToOff" commandLine="2017-1\LDMSDATA"

Configuring Datamart

  • C:\Program Files\LANDesk\ManagementSuite\log\CoreDBUtil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDESK.Install.LDMS_YYYY_MM_DD time

2017-08-30 08:15:49 INFO: Executing command CoreDBUtilDatamart (SetupController.ExecuteCurrentCommand())

2017-08-30 08:15:49 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /buildcomponents /DDON /xml="C:\Program Files\LANDesk\ManagementSuite\datamart.xml" /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Configuring Datamart PM

  • C:\Program Files\LANDesk\ManagementSuite\log\CoreDBUtil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDESK.Install.LDMS_YYYY_MM_DD time

2017-08-30 08:19:00 INFO: Executing command CoreDBUtilDatamartPM (SetupController.ExecuteCurrentCommand())

2017-08-30 08:19:00 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /buildcomponents /DDON /xml="C:\Program Files\LANDesk\ManagementSuite\datamartpm.xml" /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Configuring Datamart SAM

  • C:\Program Files\LANDesk\ManagementSuite\log\CoreDBUtil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDESK.Install.LDMS_YYYY_MM_DD time

2017-08-30 08:19:07 INFO: Executing command CoreDBUtilDatamartSAM (SetupController.ExecuteCurrentCommand())

2017-08-30 08:19:07 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /buildcomponents /DDON /xml="C:\Program Files\LANDesk\ManagementSuite\datamartsam.xml" /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Configuring Workspaces Instance

  • C:\Program Files\LANDesk\ManagementSuite\log\CoreDBUtil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDESK.Install.LDMS_YYYY_MM_DD time
  • C:\ProgramData\LANDesk\log\LANDesk.LANDesk.Common.RunMethod_YYYY-MM-DD time.log

2017-08-30 08:19:10 INFO: Executing command AtlasDatamart (SetupController.ExecuteCurrentCommand())

2017-08-30 08:19:10 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /buildcomponents /DDON /xml="C:\Program Files\LANDesk\ManagementSuite\MDM.Datamart.xml" /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Performing Additional Configurations

  • C:\Program Files\LANDesk\ManagementSuite\log\CoreDBUtil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:19:14 INFO: Executing command AtlasDatamartExchange (SetupController.ExecuteCurrentCommand())

2017-08-30 08:19:14 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /buildcomponents /DDON /xml="C:\Program Files\LANDesk\ManagementSuite\Exchange.Datamart.xml" /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Migrating tasks and policies

  • C:\Program Files\LANDesk\ManagementSuite\log\MigrateTasksAndPolicies.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:20:47 INFO: Executing command MigrateTasksAndPoliciesCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:20:47 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\MigrateTasksAndPolicies.exe -autorun

Extracting Report Files

  • C:\ProgramData\LANDesk\log\vulscan.1.logC:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:20:50 INFO: Executing command ReportsExtractCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:20:50 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\ldlogon\vulscan.exe /unzip="C:\Program Files\LANDesk\ManagementSuite\reporting\rptfiles.cab" /dest="C:\Program Files\LANDesk\ManagementSuite\reporting"

Extracting Console Report Files

  • C:\ProgramData\LANDesk\log\vulscan.2.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:21:24 INFO: Executing command ReportsConsoleExtractVDirCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:21:24 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\ldlogon\vulscan.exe /unzip="C:\inetpub\wwwroot\LANDesk\LDMS\reporting\console_rptfiles.cab" /dest="C:\inetpub\wwwroot\LANDesk\LDMS\reporting"

Installing Report Files

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:21:54 INFO: Executing command ReportsConsoleVDirCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:21:54 INFO: Executing: C:\inetpub\wwwroot\LANDesk\LDMS\LocReport.exe ENU

Importing Reports into Database

  • C:\Program Files\LANDesk\ManagementSuite\log\CoreDBUtil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:07 INFO: Executing command CoreDBUtilCannedReports (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:07 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /updatecannedreports /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Configuring Additional Shortcuts

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:27 INFO: Executing command BridgeITCreateShortcut (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:27 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="ShortcutActions" Method="CreateInternetShortcut" commandLine="C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Ivanti;Ivanti Workspaces;'https://localhost/my.bridgeit/';C:\Program Files\LANDesk\ManagementSuite\workspaces.ico"

Configuring Certificate for Workspaces Web Service

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:28 INFO: Executing command BridgeITSetCertThumbprintInWebService (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:28 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\LANDesk.Install.ConfigUtility.exe "addstsandencryptionthumbprinttowebconfig" "LANDESK Secure Token Server" "*.BridgeIT"

Configuring Certificate for Common Services Web Service

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:29 INFO: Executing command SetCertThumbprintInWebServiceDistributionApi (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:29 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\LANDesk.Install.ConfigUtility.exe "addstsandencryptionthumbprinttowebconfig" "LANDESK Secure Token Server" "DistributionApi"

Configuring Certificate for Distribution API Web Service

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:30 INFO: Executing command SetCertThumbprintInWebServiceLdApi (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:30 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\LANDesk.Install.ConfigUtility.exe "addstsandencryptionthumbprinttowebconfig" "LANDESK Secure Token Server" "LdApi"

Configuring Certificate for SmartVue Web Service

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:31 INFO: Execution of SetCertThumbprintInWebServiceSmartVue completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:31 INFO: Executing command AddNetworkServiceReadPermsToCert (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:31 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\LANDesk.Install.ConfigUtility.exe "addpermissionstocertificate" "LANDesk_1504079451" "Network Service" "read"

Configuring Permissions on Certificate

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:31 INFO: Execution of AddNetworkServiceReadPermsToCert completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:32 INFO: Executing command CBA8InstallCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:32 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\ldlogon\rainstall.exe /delayextensioninstall /dontmove /vroot=ldms.vroot /extension=lclxsvc.dll /install /cert=registry

Installing CBA8

  • C:\ProgramData\LANDesk\log\rainstall.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:32 INFO: Executing command CBA8InstallCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:32 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\ldlogon\rainstall.exe /delayextensioninstall /dontmove /vroot=ldms.vroot /extension=lclxsvc.dll /install /cert=registry

Importing Alert Names into Database

  • C:\Program Files\LANDesk\ManagementSuite\log\alertname2table.exe.information.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:22:38 INFO: Executing command AlertNamesToDatabaseCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:22:38 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\alertname2table.exe -v 0 -c -d "C:\Program Files\LANDesk\ManagementSuite\alertstrings"

Importing Alert Rules into Database

  • C:\Program Files\LANDesk\ManagementSuite\log\alertruleset2table.exe.information.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:02 INFO: Executing command AlertRuleset2tableCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:02 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\alertruleset2table.exe "C:\Program Files\LANDesk\ManagementSuite\AlertRuleSets"

Importing Software Distribution Methods into Database

  • C:\Program Files\LANDesk\ManagementSuite\log\swdCoreCustomAction.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:23 INFO: Executing command SWDMethodsToDatabaseCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:23 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\swdCoreCustomAction.exe forcepackagesupdate

Generating Root AMT Certificate

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:34 INFO: Executing command AMTProvMgr2Command (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:34 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\amtprov\AMTProvMgr2.exe -hash

Importing Remote Control Certificate

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:41 INFO: Executing command ImportRCCertificate (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:41 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="CertificateActions" Method="ImportRootCertificate" commandLine="C:\Program Files\LANDesk\ManagementSuite\rchtml5.cer";

Configuring Main Application Pool

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:41 INFO: Executing command AppPoolLdAppMainStartMode (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:41 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="IISActions" Method="SetAppPoolAttribute" commandLine="LDAppMain;StartMode;AlwaysRunning"

Configuring Web Application Pool

  • C:\ProgramData\LANDesk\log\LANDesk.Common.RunMethod_YYYY-MM-DD time.log

2017-08-30 08:23:41 INFO: Executing command AppPoolLdAppMainStartMode (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:41 INFO: Executing: C:\Users\Administrator\Desktop\Retail\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="IISActions" Method="SetAppPoolAttribute" commandLine="LDAppMain;StartMode;AlwaysRunning"

Create Monitor Root

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:44 INFO: Executing command CreateMonitorRootCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:44 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LDLogon\CreateMonitorRoot.exe "" "C:\Program Files\LANDesk\\"

Importing Roles and Rights

  • C:\Program Files\LANDesk\ManagementSuite\log\CreateLandeskRights.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:47 INFO: Executing command CreateLANDeskRightsCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:47 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CreateLANDeskRights.exe

Importing SmartVue Roles and Rights

  • C:\Program Files\LANDesk\ManagementSuite\log\CreateLandeskRights.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:23:56 INFO: Executing command SmartVueCreateLANDeskRights (SetupController.ExecuteCurrentCommand())

2017-08-30 08:23:56 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CreateLANDeskRights.exe /LOCALIZEDXML /xml "SmartVuePermissions.xml"

Installing AMS For Core

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:24:01 INFO: Executing command InstAmsCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:24:01 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\ldlogon\instams.exe Core

Providing System Settings for Agent

  • C:\ProgramData\LANDesk\log\stamper.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:24:04 INFO: Executing command StamperCommand 1 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:24:04 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\stamper.exe

Configuring Provisioning for your environment

  • C:\Program Files\LANDesk\ManagementSuite\log\osd.Upgrade.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:24:06 INFO: Executing command OSDUpgradeCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:24:06 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\OSD.Upgrade.exe

Installing Ivanti Trusted Platform Module return code template

  • C:\Program Files\LANDesk\ManagementSuite\log\HPCoreCustomAction.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:01 INFO: Executing command HPCoreCustomAction (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:01 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\HPCoreCustomAction.exe

Provisioning Configuration

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:07 INFO: Executing command ProvCreateStartnetCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:07 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\prov_createstartnet.exe

Provisioning Database - Actions and Sections

  • C:\Program Files\LANDesk\ManagementSuite\log\Prov_LoadDB.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:08 INFO: Executing command ProvLoadDBActionsAndSectionsCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:08 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe -f "C:\Program Files\LANDesk\ManagementSuite\ENUActionsAndSections.xml"

Provisioning Datababase - Initial Groups

  • C:\Program Files\LANDesk\ManagementSuite\log\Prov_LoadDB.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:11 INFO: Executing command ProvLoadDBInitialGroupsCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:11 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe -f "C:\Program Files\LANDesk\ManagementSuite\ENUInitialGroups.xml" -u 1

Provisioning Database - Public Variables

  • C:\Program Files\LANDesk\ManagementSuite\log\Prov_LoadDB.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:12 INFO: Executing command ProvLoadDBPublicVariablesCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:12 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe -f "C:\Program Files\LANDesk\ManagementSuite\PublicVariables.xml"

Provisioning Install plugin

  • C:\Program Files\LANDesk\ManagementSuite\log\Prov_InstallPlugin.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:16 INFO: Executing command ProvInstallPluginCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:16 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\prov_InstallPlugin.exe -a

OS Virtualization Provider Setup

  • C:\Program Files\LANDesk\ManagementSuite\log\Virt_Esx_Manage.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:19 INFO: Executing command VirtEsxManageCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:19 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\Virt_Esx_Manage.exe /genkey=ESX

Configuring Agent Settings

  • C:\ProgramData\LANDesk\log\stamper.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:21 INFO: Executing command StamperCommand 2 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:21 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\stamper.exe

Verifying IIS Configurations

  • C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\LANDesk.Setup.WebSiteConfiguration.Repair.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:22 INFO: Executing command RepairWebSiteConfiguration (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:22 INFO: Executing: msiexec.exe /fomus {14443C79-27E7-4CC6-AF1B-9AC3DD5C3931} /quiet /lv+ "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\LANDesk.Setup.WebSiteConfiguration.Repair.msi.log"

Resetting IIS

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:40 INFO: Executing command IisReset2 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:40 INFO: Executing: C:\Windows\System32\iisreset.exe

Configuring Firewall

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:50 INFO: Executing command FirewallConfigurationCommand (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:50 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\Install Only Files\OpenFirewallPorts.exe C:\Program Files\LANDesk\ManagementSuite\Install Only Files\OpenFirewallPortsVista.xml

Preparing Workspaces database

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:51 INFO: Executing command BridgeITCreateSQLExpressDatabase (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:51 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="SqlExpressConfiguration" Method="CreateSQLExpressDatabaseBridgeIT" commandLine="LDMSDATA;LDBridgeIT;Framework"

Copying Workspaces database file

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:29:58 INFO: Executing command BridgeITCopySqlScriptENU (SetupController.ExecuteCurrentCommand())

2017-08-30 08:29:58 INFO: Executing: cmd.exe /c xcopy /y/i "C:\Users\Administrator\Desktop\Retail\LD\Database\Workspaces\SQL Server Scripts\LDSD_OOTB_ENU.zip" "C:\ProgramData\LANDesk\ConfigurationCenter\SQLServerScripts\"

Extracting Workspaces Database script

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:30:02 INFO: Execution of BridgeITExtractSqlScriptENU completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:30:03 INFO: Executing command BridgeITConfigureDatabase (SetupController.ExecuteCurrentCommand())

2017-08-30 08:30:03 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="ConfigCenter" Method="ConfigureDatabase" commandLine="LDBridgeIT;Framework"

Configuring Workspaces Database

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:32:19 INFO: Execution of BridgeITConfigureDatabase completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:32:19 INFO: Executing command BridgeITConfigureVDirDatabase (SetupController.ExecuteCurrentCommand())

2017-08-30 08:32:19 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LANDesk.Common.RunMethod.exe assemblyFile=".\Install Only Files\LANDesk.Install.Common.Actions.dll" class="ConfigCenter" Method="ConfigureVDirDatabase" commandLine="LDBridgeIT;Framework"

Configuring Workspaces Application

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:32:30 INFO: Execution of BridgeITConfigureVDirDatabase completed. Return code: 0, State: Success (SetupController.ExecuteCurrentCommand())

2017-08-30 08:32:31 INFO: Executing command SamInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:32:31 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\SAM\setup.exe /s

Installing Software License Monitoring

C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:32:31 INFO: Executing command SamInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:32:31 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\SAM\setup.exe /s

Installing Office 365 components for Workspaces

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:44:00 INFO: Executing command ItamInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:44:00 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\ITAMData\setup.exe /s

Installing Lenovo TVT add on

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDESK.Setup.LenovoTVT.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:44:33 INFO: Executing command TVTInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 08:44:33 INFO: Executing: msiexec.exe /i "C:\Users\David Holland\Desktop\Retail\LD\TVT\LenovoTVTAddOn.msi" /q /lv+ "C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\LANDesk.Setup.LenovoTVT.msi.log" INSTALLDIR="C:\Program Files\LANDesk\ManagementSuite"

Installing Data Analytics

  • C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\DataAnalytics_Setup.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:45:50 INFO: Executing command DataAnalytics_Install (SetupController.ExecuteCurrentCommand())

2017-08-30 08:45:50 INFO: Executing: C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Data\Main\bin\Resources\DataAnalytics\setup10.exe /S /Verbose"C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log\DataAnalytics_Setup.exe.log" /v"LDDAMS=YES"

Installing Data Analytics - registering COM servers

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:57:26 INFO: Executing command DataAnalytics_Install_RegAsm_1 (SetupController.ExecuteCurrentCommand())

2017-08-30 08:57:26 INFO: Executing: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe "C:\Program Files\LANDesk\ManagementSuite\WEBPULL\Interop.ComUtilitiesLib.dll" /s

Installing Data Analytics - registering .NET assemblies

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

 

Exporting WMI Rules

  • C:\Program Files\LANDesk\ManagementSuite\log\WMIRulesExport.exe.information.log
  • C:\Program Files\LANDesk\ManagementSuite\log\WMIRulesExport.exe.licensing.log
  • C:\Program Files\LANDesk\ManagementSuite\log\WMRulesExport.exe.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 08:57:26 INFO: Executing command WMIRulesExport (SetupController.ExecuteCurrentCommand())

2017-08-30 08:57:27 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\WMIRulesExport.exe

Configuring Licensing Service Provider

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:08:13 INFO: Executing command LSP_AltHostSetting (SetupController.ExecuteCurrentCommand())

2017-08-30 09:08:13 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\LicensingServiceProvider.exe /althost=LICENSE3 /host=LICENSE /content=14 /frequency=14

Localizing Data in the Database

  • C:\Program Files\LANDesk\ManagementSuite\log\Coredbutil.exe
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:08:14 INFO: Executing command CoreDBUtilLocalize (SetupController.ExecuteCurrentCommand())

2017-08-30 09:08:14 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /localize /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1.10\Log"

Configuring Core Server to launch activation process at next login

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:14:55 INFO: Executing command ActivateCoreOnReboot (SetupController.ExecuteCurrentCommand())

2017-08-30 09:14:55 INFO: Executing: reg.exe add hkcu\Software\Microsoft\Windows\CurrentVersion\RunOnce /v ActiveCoreServer /t REG_SZ /d "C:\Program Files\LANDesk\ManagementSuite\LANDesk.Managementsuite.Licensing.ActivateCore.exe" /f

Installing Discovery Services

  • C:\ProgramData\LANDesk\Discovery\Install\1.2\log\LANDesk.Install.Discovery.msi.log
  • C:\ProgramData\LANDesk\Discovery\Install\1.2\log\LANDesk.Install.nodejs.msi.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:14:56 INFO: Executing command DiscoveryInstall (SetupController.ExecuteCurrentCommand())

2017-08-30 09:14:56 INFO: Executing: C:\Users\Administrator\Desktop\Retail\LD\Discovery\setup.exe /s Product=Feature1 InstallDir="C:\Program Files\LANDesk\Discovery"

Creating MDM application pool

C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:15 INFO: Executing command AtlasCreateAppPool (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:15 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe add apppool /name:LDAppMDM /managedRuntimeVersion:v4.0 /managedPipelineMode:Integrated /processModel.identityType:NetworkService

Creating MDM website

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:16 INFO: Executing command AtlasCreateWebsite (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:16 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe add app /site.name:"Default Web Site" /path:"/MDM" /physicalPath:"C:\Program Files\LANDesk\ManagementSuite\MDM" /applicationPool:LDAppMDM

Creating Commands Website

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:17 INFO: Executing command AtlasCreateCommandsWebsite (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:17 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe add app /site.name:"Default Web Site" /path:"/landesk/commands" /physicalPath:"C:\Program Files\LANDesk\ManagementSuite\landesk\commands" /applicationPool:LDAppMain

Configuring Node for MDM Enrollment

  • C:\ProgramData\LANDesk\log\vulscan.log
  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:17 INFO: Executing command AtlasConfigureNode (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:17 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\ldlogon\vulscan.exe /unzip="C:\Program Files\LANDesk\ManagementSuite\EnrollmentServer\node_modules.zip" /dest="C:\Program Files\LANDesk\ManagementSuite\EnrollmentServer"

Creating Windows MDM Enrollment Site

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:16 INFO: Executing command AtlasCreateWebsite (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:16 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe add app /site.name:"Default Web Site" /path:"/MDM" /physicalPath:"C:\Program Files\LANDesk\ManagementSuite\MDM" /applicationPool:LDAppMDM

Creating Mobility Website

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:47 INFO: Executing command AtlasCreateMobilityWebsite (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:47 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe add app /site.name:"Default Web Site" /path:"/landesk/mobility" /physicalPath:"C:\Program Files\LANDesk\ManagementSuite\landesk\mobility" /applicationPool:LDAppMain

Configuring authentication on Mobility Website

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:48 INFO: Executing command AtlasSetMobilityWindowsAuth (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:48 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/landesk/mobility" -section:system.webServer/security/authentication/windowsAuthentication /enabled:"True"  /commit:apphost

Configuring access on Mobility Website

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:48 INFO: Executing command AtlasSetMobilityAccess (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:48 INFO: Executing: C:\Windows\System32\inetsrv\appcmd.exe set config "Default Web Site/landesk/mobility" -section:system.webServer/security/access /sslFlags:"Ssl" /commit:apphost

Configuring Certificate for Discovery Services

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:49 INFO: Executing command SetCertThumbprintInWebServiceDiscovery (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:49 INFO: Executing: C:\Program Files\LANDesk\ManagementSuite\install only files\LANDesk.Install.ConfigUtility.exe "addstsandencryptionthumbprinttowebconfig" "LANDESK Secure Token Server" "Discovery\api\v1"

Preparing System for Reboot

  • C:\ProgramData\LANDesk\ManagementSuite\Install\10.1.10\log\LANDesk.Install.LDMS_YYYY_MM_DD time.log

2017-08-30 09:19:50 INFO: Executing command PrepareSystemForReboot (SetupController.ExecuteCurrentCommand())

2017-08-30 09:19:50 INFO: Executing: reg.exe add hklm\Software\LANDESK\LANDESKSoftware\Setup /v Status /t REG_SZ /d "OK" /f

Issue: Core upgrade fails at Stopping LANDESK Services

$
0
0

Issue

 

LANDESK upgrade fails on "Stopping LANDESK Services"

 

pastedImage_0.png

 

You may also see an error in the log similar to this:

 

2017-01-01 21:24:14 INFO: Executing command Service_CBA8_StopService  (SetupController.ExecuteNextCommand())

2017-01-01 21:24:14 INFO: Executing: C:\LANDESKSoftware2016-3\Resources\LANDesk.Common.RunMethod.exe assemblyFile="LANDesk.Install.Common.Actions.dll" class="Services" Method="StopServiceEx" commandLine="CBA8;1200;true"  (Launcher.ExecuteXmlCommand())

2017-01-01 21:24:14 ERROR: Execution of Service_CBA8_StopService completed. Return code: 1, State: Failure  (SetupController.ExecuteNextCommand())

 

Cause

This may be caused if the LANDESK Management Agent service is missing. Since the service doesn't exist, the installation is unable to stop it, and fails.

 

Solution

 

To reinstall the service you'll need to run the following command:

 

"C:\Program Files\LANDesk\Shared Files\residentagent.exe" /register

 

If the command fails, please check "C:\Program Files\LANDesk\Shared Files" for ResidentAgent.exe.

If the file is missing, you can copy it from this location in your LDMS 2016.3 installation directory:

 

C:\LANDESKSoftware2016-3\LD\MS\PF\LD\MS\_non\ldlogon\sharedtech\

 

Once the file is copied over, run the command above to reinstall the service.


Your installation should continue past this point.

Best Known Methods for installing Microsoft SQL Server 2012 for LDMS

$
0
0

Applies to LANDESK Management Suite 9.5 and 9.6

 

This document is intended to assist LANDESK® Management Suite users with the installation and configuration of Microsoft® SQL Server 2012 (MSSQL) for a LANDESK® Management Suite installation.

 

Note: When installing LANDESK software, it is recommended to not use Remote Desktop. If this is the only available method, please initiate the RDP session using "mstsc /admin". This generates a console session as opposed to a terminal session.


Issue: OSD.Upgrade.exe error during installation

$
0
0

Description

 

OSD.Upgrade.exe is run during the installation of an Ivanti EPM Service Pack or any Ivanti patch that updates the WinPE image (boot.wim). It is responsible for configuring the image to function on a specific Core Server and migrating WinPE drivers from the boot.wim.bak into the new boot.wim. If OSD.Upgrade.exe fails, one or more of these steps may not be completed. This document will walk through re-running the OSD.Upgrade.exe installation step on the core server.

 

During the Service Pack or patch installation, there may be a failure with the OSD.Upgrade.exe process. The install error may be similar to CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000.  Review the osd.upgrade.exe log file found in C:\Program Files (x86)\LANDESK\ManagementSuite\log to get more specific information about the error. If desired the osd.upgrade.exe.log file can be renamed prior to running osd.upgrade.exe again to make current errors easier to find.

 

A common cause of this issue can be that one of the .WIM files is already mounted from a prior process or through manual intervention by an administrator.

 

Common errors and description

 

  • Error: "Access Denied"

    • Errors referring to access denied indicates that a folder path in the boot.wim is too long. Often this path will be for a driver that was injected into the WinPE image. There are two option for correcting this error. The first option is to just start with a clean boot.wim and add the necessary drivers after completing the OSD.Upgrade.exe process. In LDMS 9 Service Pack 3 the WinPE boot environment requires Windows 7 32-bit drivers. Updating those drivers is a manual process so starting with a clean boot.wim may be a good option. The second option would be to mount the backup of the boot.wim (boot.wim.bak) and rename the directories in the InstalledDrivers directory to use shorter names. After completing one of these options follow the steps outlined below to re-run OSD.Upgrade.exe.

  • Error: "CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,60000"

    • This is a general error indication. Review the log for additional errors.
    • Check to make sure the boot.wim is not mounted on the Core server.
      • The way to check this is running "dism /get-MountedWiminfo" from command prompt. This will show if wim's are mounted and where.
      • Check the OSD.Upgrade.exe.log file for any missing files. Then give it those missing files in the path that it is looking for them.
        • example: "09/06/2016 10:22:53 INFO  9680:1     RollingLog : File C:\Program Files\LANDesk\ManagementSuite\\ldlogon\provisioning\windows\Microsoft.VC90.CRT.manifest does not exist"
  • Error: "DirectoryNotFoundException"

    • Errors referring to a .0 or an mpkg package indicate that a .0 file has been extracted to a sub-folder of the ldlogon folder. DO NOT delete any .0 files from the root of ldlogon. Navigate to the directory specified in the log (i.e. C:\Program Files (x86)\LANDESK\ManagementSuite\ldlogon\mac) and delete the .0 file. To prevent additional errors when re-running OSD.Upgrade.exe delete any additional .0 files that are found in sub-folders of the ldlogon folder leaving only the .0 files in the root of ldlogon. Follow the steps below to re-run OSD.Upgrade.exe.
    • Errors referring an ALL.REG file indicate that the wim file was still mounted when osd.upgrade.exe tried to execute. This is most likely due to errors in the previous attempt at running OSD.Upgrade.exe. Review the log and correct and additional errors found before following the steps below to re-run OSD.Upgrade.exe.

  • Error: "Non-fatal error: FilterUnload failed, hr=0x801f0013"

    • This is normal and does not indicate a problem. Continue reviewing the log file for additional errors.

  • Error: "System.ComponentModel.Win32Exception"

    • You are running the process as a restricted user. Either log in as an administrative user or right click OSD.Upgrade.exe and select run as administrator.
      • Make sure that you are either logged directly into the core server or using Remote Desktop with a /admin switch as a full administrator.

  • Error: "System.IO.IOException: Element not found"

    • This error indicates that there is still a wim file mounted. Review the log for additional errors prior to this error. Follow steps below to re-run the OSD.Upgrade.exe process.

  • Error: "System.UnauthorizedAccessException"

    • This error indicates either that there is still a wim file mounted, or that the bootmedia.wim.bak already exists. Bootmedia.wim.bak can be deleted as long as bootmedia.wim exists. Review the log for additional errors and then follow the step below to re-run OSD.Upgrade.exe.

  • Error: "WAIK is not installed"

    • This is normal and does not indicate a problem. WAIK should have been uninstalled prior to upgrade. If WAIK is installed, uninstall it. Continue reviewing the log file for additional errors.

  • Error: "CommonCore.inf: (0xFFFFFFFF) OSD.Upgrade.exe,90000"

    • Download Streams from Microsoft (https://technet.microsoft.com/en-us/sysinternals/bb897440.aspx). Go into properties of Streams an unblock the application. Run Streams against the folder the Ivanti EPM installer was xtraced to and run Streams against the folder LANDESK is being installed to (ie, \Program Files\LANDESK). Make sure the Ivanit EPM installer is being run locally (not networked drive), you are upgrading the machine locally (not RDP) and run the installer as Administrator.

 

  • Issue: Upgrade fails at HII step

    • Log will displayRollingLog : HII: Setting driver repository path to "\\LDCoreName\ldmain\landesk\files\drivers" 08/05/2015 12:03:10 INFO 8732:1 RollingLog : HII: Initial driver file count to process:
    • In the \\LDCoreName\ldmain\landesk\files\drivers directory will be a db3 and db3 bak file. Rename the file to db3.old and db3 bak.old. Quit out of the installer and re-open and start install again
      .

Preparing to Re-Run OSD.Upgrade.exe

After reviewing your errors and completing the steps above perform the following steps:

 

  1. Start an administrator command prompt (right click the command prompt and select run as administrator).
  2. From the command prompt navigate to C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot.
  3. Run the following command:

    DISM.EXE /Get-MountedWimInfo
    • The command should list all images that are currently mounted. There are instances however where a mounted image will not be listed. Check for the existence of the folder original_boot_wim and/or new_boot_wim in the C:\Users\logged in user \AppData\Local\Temp\imgtmp\ directory.

  4. For each image listed and all folders found in the imgtmp directory listed in step 1, run the following commands:

    • DISM.EXE /Unmount-Wim /mountdir:"c:\path to dir(s) found in previous step" /discard  Where mountdir is the mount path listed from the dism.exe /Get-MountedWimInfo command or the folders specified in step 3.
    • DISM.EXE /Cleanup-Wim
    • Ensure that each unmount command completes successfully
    • Any errors that DISM may encounter will be logged in the %windir%\Logs\DISM directory.  (For further information see Understanding Failures and Log Files)
  5. In Windows Explorer open the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory.
  6. Rename the existing boot.wim to boot.wim.bad.
  7. Copy the backup boot.wim (the one from prior to upgrading) from C:\Program Files (x86)\LANDesk\ManagementSuite\backup\PatchName\ to the C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\vboot directory.
    • If access denied errors occurred with drivers and a clean boot.wim file is desired, use the file listed in step 9 below.
  8. Rename the restored boot.wim file in the vboot directory to boot.wim.bak.
  9. Copy the boot.wim file from the installation package \image directory to the \vboot directory. You should now have a boot.wim and boot.wim.bak (either your backup or an additional copy from the patch) file in the vboot directory.
  10. Run the OSD.Upgrade.exe from C:\Program Files (x86)\LANDesk\ManagementSuite\. This should take a few minutes to complete. If it exits quickly it is likely that there are additional errors.
  11. Review the OSD.Upgrade.exe log found in C:\Program Files (x86)\LANDesk\ManagementSuite\logs to see if any additional errors were encountered. If additional errors were encountered, you must resolve each one and after resolving re-run OSD.Upgrade.exe.
  12. If this still does not resolve the issue check "HKLM\SOFTWARE\Microsoft\WIMMount\Mounted Images" and remove any values in the key.

 

After OSD.Upgrade.exe has completed successfully you need to redeploy your PXE reps. Instructions for PXE deployment can be found at How to deploy PXE Representatives(step-by-step screenshots)

 

When a client machine boots into WinPE open a console to confirm the upgrade. The version shown in the console should be 6.1.7601 or higher.

OSD.Upgrade.exe.log

How to prepare your LANDESK database for upgrade testing

$
0
0

Operation for backing up and restoring a database for testing

 

Proper testing of the database upgrade of your database a critically important step in avoiding downtime of your LANDESK environment, we have prepared this document in order to help you backup and restore an upgradable copy or your database for the purposes of this testing.

 

  1. Prepare a new core server using the same OS that the production Core Server will use.  A virtual machine would be ideal.
  2. See DOC-7285 for complete information on Core Server preparation and setup.
  3. Right click on the LANDESK Production database, and then choose “Copy Database”.
  4. Click “Next”.
  5. In the field labeled “Source server:” type “localhost”.  (Without the quotation marks.)
  6. Choose “Use SQL Server Authentication”, use the same user and credentials that is used for Core Server access to the database.
  7. Click “Next”.
  8. In the field labeled “Source server:” type “localhost”.  (Without the quotation marks.)
  9. Choose “Use SQL Server Authentication”, use the same user and credentials that is used for Core Server access to the database.
  10. Click “Next”.
  11. Choose “Use the SQL Management Object method” by placing the mark in the radial button.
  12. Click “Next”.
  13. Ensure the LANDESK Production Database is selected.
  14. Click “Next”.
  15. Choose a unique name for the new database in the “Destination database:” field.
  16. Ensure a proper destination for the database files is selected.
  17. Click “Next”.
  18. Click “Next”.
  19. Place the mark in the “Run immediately” radial button.
  20. Click “Next”.
  21. Click “Finish”.

 

Once you have backed up your database you can complete the installation and upgrade of the Database.  Proper testing if your database will help avoid unexpected downtime for your server.

 

Attached to this article is a document showing the entire operation.

Ivanti Endpoint Manager and Endpoint Security - Core Install, Console Install, and Upgrades Frequently Asked Questions

$
0
0

Ivanti Endpoint Manager - Core Server Install and Upgrade

If you want to review additional content regarding this component, please use Documents or Discussions buttons on the overview page.

 

Product Help Files

IEM2017/ LDMS 2016  | LDMS 9.6

 

TrainingCore Installation and Configuration Database Installation and Configuration

[Tech Brief Recording] Overview of LANDESK Management Suite 2016

LANDESK Management Suite 2016 Architecture - Overview | Endpoint Manager (LDMS) 2017.1 Architecture - Overview

Best Known Methods for installing Microsoft SQL Server 2012 for LDMS

Making your LDMS 9.6 upgrade installation easier

Prerequisites to Check Before Installing, Updating, or Patching the Ivanti Endpoint Manager Core Server

Recommendations for tuning EPM (LDMS) and MS SQL for large enterprise Core Servers

Momentum On-Demand Webinars

LANDESK Management Suite 2016.3 Install Guide

Reindexing LANDESK Databases

Webinar -What's New LANDESK Management Suite in 2016.3

How to use Configuration Center to set up a Workspaces Database

Overview of how the database upgrade to Unicode works.

How to install LANDESK service packs
How to activate the LANDESK Core Server
Supported Console Platforms for LANDesk Management Suite

 

Ports used by LANDesk Management Suite - Full List

 

How to use the CoreDataMigration.exe tool to migrate core settings

 

 

TroubleshootingSoftware Downloads

How to troubleshoot Core Installation

Download the Latest Service Pack for Ivanti / LANDESK Software Products

How to troubleshoot Configuration Center

How to rebuild the LANDesk COM+ Objects

About the LANDeskCOMPlus user, "What is this account" and "Why is it on my Core"?

Error: "Login failed for user 'LDMSAdmin' during service update installation

 

Notice:Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level

 

This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Core Install/Upgrade if this page hasn't helped.

 

Issue: Core Server activation failed

$
0
0

The following may be tried in the event an activation file cannot be created or the core server otherwise fails to activate:

 

  1. Make sure your console is closed
  2. Try to activate your normal way - but check the box "show content"
  3. When this fails go to your Authorization Files usually located here:
  4. sC:\Program Files\LANDesk\Authorization Files\
  5. Check to see if a .txt file NOT a .save or .txt.save but a .txt file has been created
  6. If no file has been created check to see how many .txt's and .save's are in this folder; if there are more then 15 or 20 of each delete them all and
  7. Retry normal activation process agains
  8. You should now see that a new .txt file has just been created - go ahead and send that file into licensing@landesk.com
  9. When you get the Authorization File back just drop it in the same place "C:\Program Files\LANDesk\Authorization Files\" when it disappears reopen your console and you should be good to go.

 

If this process does NOT work - please call into or log a self-service case for technical support.

How to troubleshoot kernel memory leaks

$
0
0

Issue


System runs out of resources over time and becomes unresponsive.

 

The System Event Log shows one or more of the following error:

Event ID: 2019
Source: Srv
Description: The server was unable to allocate from the system nonpaged pool because the pool was empty.

Event Type: Error

Event Source: Srv

Event ID: 2020

Description: The server was unable to allocate from the system paged pool because the pool was empty.

 

Cause

A driver installed on the system has a memory leak and is consuming all available resources.


Resolution

 

To determine the specific driver causing this memory leak the following steps can be taken:

  1. Download the Windows Driver Kit .ISO
    (http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=36a2630f-5d56-43b5-b996-7633f2ec14ff)
  2. Extract or mount the Windows Driver Kit .ISO and run “KitSetup.exe” from the root.
  3. Uncheck “Debugging Tools for Windows” and check “Tools” and click OK.
  4. Select a directory to install to and click OK.
  5. From a CMD prompt, navigate to [Directory Installed To]\Tools\Other and then to the appropriate directory for the Operating System you are trying to troubleshoot (amd64 for x64 systems, i386 for 32-bit systems) and run “poolmon /p".
  6. Press "D" to sort by "Diff".   This will display at the top of the list the process with highest differential between handles allocated, and handles freed.
  7. Under the Tag column will be a 4 digit “Pool Tag” identifier.   This can be used to find the malfunctioning driver.
  8. To find the malfunctioning driver, go to C:\Windows\System32\drivers and C:\Windows\SysWow64\drivers and run “findstr /m /l [tag] *.sys”  (Where [tag] is the 4 digit tag identifier from the log file in step 7.
  9. The malfunctioning driver (.sys file) should now be displayed.   A Google search should now help you determine who that .SYS file belongs to.

 

The registry key change is as follows:

 

HKLM\System\CurrentControlSet\Control\Session Manager\GlobalFlag

 

Change the value of Global Flags to 1024 in decimal and reboot the computer.

 

If the driver is allocating pool space rapidly and not giving it back, it will be quickly apparent which driver is the culprit.   However at times it may be necessary to wait a while before it becomes noticable.

 

Sometimes a driver may only start acting up when certain events occur.   In this instance it is necessary to have poolmon run at regular intervals and log to a file.   The following batch file (also attached) will run poolmon and write to a log file with the current time and date.  (Poolmon.exe will need to be copied to C:\ for this to work properly)

 

@echo off
SET POOLMON="C:\Poolmon.exe"
SET OUTDIR=C:\
SET YEAR=%DATE:~10,4%
SET MONTH=%DATE:~4,2%
SET DAY=%DATE:~7,2%
SET HOUR=%TIME:~0,2%
IF /I %HOUR% LEQ 9 SET HOUR=0%HOUR:~1,1%
SET MINUTE=%TIME:~3,2%
SET SECOND=%TIME:~6,2%
SET ISODATE=%YEAR%-%MONTH%-%DAY%_%HOUR%-%MINUTE%-%SECOND%
%POOLMON% -d -n %OUTDIR%\poolmon.%ISODATE%.log
This will create a log file in the root of C: called poolmon.currentdateandtime.log

 

You can then create a Windows Local Scheduler job to run the batch file regularly:

 

To schedule a task that runs every N minutes

 

Minute Schedule Syntax

schtasks /create /tn TaskName /tr TaskRun /sc minute [/mo {1 - 1439}] [/st HH:MM] [/sd StartDate] [/ed EndDate] [{/et HH:MM | /du HHHH:MM} [/k]] [/it] [/ru {[Domain\]User [/rp Password] |System}] [/s Computer [/u [Domain\]User [/p Password]]]

 

Example to have poolmon run every 30 minutes:

 

schtasks /create /sc minute /mo 30 /tn "Run Poolmon Every 30 Minutes" /tr C:\runpoolmon.bat /ru system

 

This command line is included in the attached "AddPoolmonTask.bat".   To run this command as displayed here and add a task to the task scheduler that runs Poolmon every 30 minutes, simply run this batch file.

 

Further information regarding the schtasks command: Schtasks: Management Services

 

Note: See the following articles for further information regarding this process:


How to use Memory Pool Monitor (Poolmon.exe) to troubleshoot kernel mode memory leaks
http://support.microsoft.com/default.aspx?scid=kb;EN-US;177415


How to find pool tags that are used by third-party drivers
http://support.microsoft.com/kb/298102


Understanding Pool Consumption and Event ID: 2019 or 2020
Understanding Pool Consumption and Event ID: 2020 or 2019 – Ntdebugging Blog

 

PoolMon Examples

PoolMon Examples

Viewing all 272 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>