Quantcast
Channel: Ivanti User Community : All Content - General
Viewing all 415 articles
Browse latest View live

How to Stop/Start all LANDesk Services at Once? (now with PowerShell)

$
0
0

Environment

 

This script works on the following versions of LANDesk Management Suite:

 

  • LDMS 9.6
  • LDMS 9.5 SP2
  • LDMS 9.0 SP4

Description

There are times when it is desired to STOP/Start all LANDesk services on the Core Server or on a LANDesk agent.  LANDesk services include some Intel services as well.

 

Windows does not provide a method to Start/Stop multiple services at once, instead they must be stopped one a time.Update: PowerShell can do it!

 

PowerShell for Stopping\Starting All LANDesk Services

 

First, it's a good idea to see what the services are doing now:

PS H:\> Get-Service -DisplayName LANDesk*,Managed* | Sort-Object Status,DisplayName | Format-Table -AutoSize

Status  Name                                            DisplayName
------  ----                                            -----------
Stopped LDGSB                                           LANDesk(R) Management Gateway Service
Running LANDesk Inventory Server                        LANDesk Inventory Server
Running ApmTcs                                          LANDesk Policy Server
Running Intel Scheduler                                 LANDesk Scheduler Service
Running LANDeskTIM                                      LANDesk Transport Initiator Module
Running LANDesk(r) Usage Service                        LANDesk Usage Service
Running Agent_Portal                                    LANDesk(R) Agent Portal Service
Running CBA8Alert                                       LANDesk(R) Alert Service
Running LANDesk(R) AMT Notification Service             LANDesk(R) AMT Notification Service
Running ASFProxyService                                 LANDesk(R) ASF Proxy Service
Running IPMI_Redirection                                LANDesk(R) Console Redirection Service
Running CoreSyncService                                 LANDesk(R) Core Sync Service
Running CBA8                                            LANDesk(R) Management Agent
Running LSM_SNMP                                        LANDesk(R) System Manager SNMP Message Relay Service
Running Managed Planet Barcode Core                     Managed Planet Barcode Core
Running MPCore                                          Managed Planet Core Scan Processor
Running Managed Planet Discovery Core                   Managed Planet Discovery Core
Running Managed Planet Rapid Deployment                 Managed Planet Rapid Deployment
Running Managed Planet Software Manager                 Managed Planet Software Manager
Running Managed Planet Software Store Auto Uninstall    Managed Planet Software Store Auto Uninstall
Running Managed Planet Software Store LDAP Cache Update Managed Planet Software Store LDAP Cache Update
Running Managed Planet Software Store Maintenance       Managed Planet Software Store Maintenance
Running Managed Planet Software Store User Cache Update Managed Planet Software Store User Cache Update
Running Managed Planet Task Listener                    Managed Planet Task Listener

This command will list all services that have a display name that starts with "landesk" & "managed" (it is NOT case sensitive).  If you leave off "Format-Table -AutoSize", the columns will be truncated.

 

Now that you know what is running, it's time to stop them.  THESE MUST BE RUN AS AN ADMINISTRATOR.

PS C:\> Stop-Service -DisplayName LANDesk*,Managed* -Verbose -Force     - OR -
PS C:\> Get-Service -DisplayName LANDesk*,Managed* | Where-Object {$_.Status -EQ "Running"} | Stop-Service -Verbose

 

The command will only display output for services that take their time to stop (unless you use -verbose).

Once you get back to the prompt, run "Get-Service... " to make see if all the services are actually shutdown.  Sometimes it takes another go around, so just repeat the "Stop-Service... " command.

 

Please note that according to TCP protocol, ports can be locked open by the operating system for a maximum of 4 minutes after the process terminate.  This *may* cause problems when restarting services.  This is one of the reasons why the "Restart-Service" command is not used in this example.

 

Now, let's start them back up:

PS C:\> Start-Service -DisplayName LANDesk*,Managed* -Verbose      - OR -
PS C:\> Get-Service -DisplayName LANDesk*,Managed* | Where-Object {$_.Status -EQ "Stopped"} | Start-Service -Verbose

 

The services should be up and running now.  Check with "Get-Service... " or refresh the services.msc and if some are still "Stopped".  Repeat the "Start-Service... " command if needed.

 

If they are any in the"Starting" state for an extened period of time (which usually presents itself as "WARNING: Waiting for service 'DisplayName (Name)' to finish starting..."), check the application event logs for errors.  Usually it has something to do with the database (connectivity, authetication, etc.).  It may be that it just needs some time and it is NOT an error condition, i.e., don't panic.  Diasabled services will always through an error.

 

Sometimes, it is helpful to change services from automatic to manual for troubleshooting pruposes, etc.

Get-Service -DisplayName landesk* | Set-Service -StartupType Manual -Verbose
Get-Service -DisplayName landesk* | Set-Service -StartupType Automatic -Verbose

 

The first command will NOT stop services BUT it WILL prevent your core services from starting.  The second command sets them to automatic again.

 

For more information about these standardPowerShell commands, please see Get-Service, Start-Service, & Stop-Service.

 

 

Batch File for Stopping\Starting All LANDesk Services

 

Attached is a batch file that will stop/start all LANDesk services, as well as one that will stop/start all LANDesk and DA (Managed Planet) services.

Just double-click on the batch file or to get the proper usage run the batch file with a -?.

c:\> LANDeskServices.bat -?
Usage:   
LANDeskServices.bat [ STOP|START ]   

START = Starts all LANDesk and Intel Services.   
STOP = Stops all LANDesk and Intel Services.

c:\>

How to support Windows XP in your environment after upgrading to LDMS 2016.3 or greater

$
0
0

LANDESK and Ivanti Support for Windows XP

 

Ivanti (LANDESK) has discontinued support Windows XP with the release of the LDMS 2016.3 milestone update (similar to a service pack).  This is in accordance to Microsoft Support ending for Windows XP.

 

It is highly encouraged where possible to upgrade the Windows XP OS to a supported version as essential security and other updates are generally not available

 

For more information see the following article about Ivanti (LANDESK)'s sustaining (ongoing development) information.

 

Endpoint Manager 2017.X (formerly LDMS)  Sustaining and Patch Information

 

Why doesn't LANDESK (Ivanti) development not create patches for my 2016 install support Windows XP?

 

Ivanti (LANDESK) has always supported development only for the latest milestone release (service pack).  This is the same as most major software vendors.  Maintaining several development branches increases the workload and potential for error.

 

An example of a milestone release or service pack is the upgrade from 2016.0 to 2016.3.  2016.3 is not a new version, it is simply an update to 2016.0.

 

What can I do to continue supporting my Windows XP clients?

 

How to Build a Legacy Agent for Windows XP and Server 2003

 

Vulscan Self-Update has been enhanced to deliver one set of self-update files to XP clients and a different set to newer clients.  The process is outlined in this document:

Enhanced Vulscan Self-Update Feature

Custom Message PopUp

$
0
0

EPM 2017.3

Is there a way to send a custom message Popup to a machine?

We are not restarting systems after updates/other but we need the machines to be restarted after certain time (once a week)

We would like to send a "A reboot is needed" popup, can EPM do this?

 

Best

How to identify the patch level on the LDMS core server?

$
0
0

Connect to your core server LDMS and open the registry and navigate to the following path of the registry:

 

Windows 2008R2 Core Server:

HKLM | Software | WOW6432Node | LANDesk | Managementsuite | Setup | Version | Patches

 

Windows 2003 Core Server:

HKLM | Software | LANDesk | Managementsuite | Setup | Version | Patches

 

mkijidj.PNG

 

Please export the following registry key from the Core Server and attach to your case.

Reindexing LANDESK Databases

$
0
0

Database Indexing

 

Performing routine database maintenance such as reindexing is important for keeping the LANDESK database running at peak performance. When information is entered or modified in the database tables, indexes can become fragmented. Re-indexing is best done during a maintenance window.

Index fragmentation can happen when the logical sequence of pages is disrupted or when an index page contains less than its maximum amount of data, creating a gap in the data page or index. As indexes become fragmented, data reads become inefficient when accessing tables and slow database performance.

For specific recommendations for tuning LDMS and MSSQL for large enterprise environments please visit DOC-39315.

Doc 39315 also references actions such as backing up and updating statistics.

 

SQL Script

For current versions of SQL (2005 and above) there is an attached script in SQL_Logic_Based_Indexing-2018.txt that allows for a logical re-organization / rebuild action. Users can use the SQL Server Maintenance Plan Wizard to create their indexing plan or can use this script can be used instead. Its common practice for DBAs to take T-SQL and create SQL Server Agent jobs using script contents and then referring to the agent job when building their maintenance plan. This script offers more scalability in reorganizing less fragmented indexes, ignoring slightly fragmented indexes and rebuilding highly fragmented indexes. This would be useful when downtime is limited and the above reindex isnt meeting those needs. The only modification required is database name on the first line. There are other variables that can be tuned based on the DBA's needs.

 

For assistance creating maintenance plans or sql agent jobs please refer to Microsoft's documentation.

 

Some DBAs prefer to set the database to SINGLE USER MODE before reindexing the DB.  This isnt required however note that SQL Standard Edition will not keep indexes online when rebuilding them; so indexes will not be used for actions performed on those tables at the time of rebuild. Also consider if there will be resource contention at the time of your database maintenance.

 

To set a database to single-user mode in SQL 2005-2014

 

  1. In Object Explorer, connect to an instance of the SQL Server Database Engine, and then expand that instance.
  2. Right-click the database to change, and then click Properties.
  3. In the Database Properties dialog box, click the Options page.
  4. From the Restrict Access option, select Single.
  5. If other users are connected to the database, an Open Connections message will appear. To change the property and close all other connections, click Yes.

 

SQL Logic Based Indexing 2018

In the SQL Logic Based Indexing 2018.txt file attached to this article is a more robust script that provides some decision making and allows the DBA to make some choices about thresholds.

 

In the script you must select your DB using the following statement, simply replace <databasename> with the name of your Ivanti Endpoint Manager Database:

USE <databasename>

 

Next, the basic threshold to reorganize or rebuild an index is 10% and can be changed in this line of the script, 10.0 being the percentage level, change it to fit your needs or leave it as is. Indices below 10% fragementation (Or whatever you choose) will not be affected:

WHERE avg_fragmentation_in_percent > 10.0 AND index_id > 0;

 

Next, Choose your threshold for deciding between reorganizing or rebuilding indices with the following line. Anything below the threshold but above the basic fragmentation threshold will be reorganized, anything above this threshold will be rebuilt in the example below 30% is the decision threshold:

-- 30 is an arbitrary decision point at which to switch between reorganizing and rebuilding.
IF @frag < 30.0
SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REORGANIZE';
IF @frag >= 30.0
SET @command = N'ALTER INDEX ' + @indexname + N' ON ' + @schemaname + N'.' + @objectname + N' REBUILD';

 

And lastly, Set your DB back to multi user, edit the following line to include your Ivanti endpoint Manager DB name where <databasename>:

ALTER DATABASE <databasename>

 

If your database is not set to single user mode this section will just complete and move on.

 

NOTE:

 

Stop LANDESK Management Suite/Ivanti Endpoint Manager Specific processes so they will not connect to the database, refer to this document: https://community.ivanti.com/docs/DOC-2465

Basic Recommendation for Database Maintenance

$
0
0

Database maintenance plans are crucial to a well performing database for both LDMS and Service Desk.  Without maintenance plans to keep the data free of fragmentation and indexing issues, always configure maintenance plans to perform the following scheduled maintenance.

***The information below is a representation of what has worked for most customer, but individual results may vary depending on the hardware, size, and utilization of your database.***

 

1.  Reindex weekly

     Regular re-indexing of tables or defragmenting of indexes helps to optimize database performance. Also,

     monitor database statistics (especially after large data imports). We recommend that DBAs review index

     fragmentation in the database and if necessary rebuild.

     Microsoft SQL Server provides a standard maintenance plan to rebuild indexes on a database. We

     recommend that you schedule this to run on a weekly basis.

 

2.  Reorganize daily

 

3.  Backup daily

     We recommend that a regular backup and maintenance plan is in operation against the Service Desk

     database.

 

NOTE: The implementation of such plans is the responsibility of the customer’s Database Administrator.

 

Useful resources: http://technet.microsoft.com/en-us/library/ms189858.aspx

                          http://community.landesk.com/support/docs/DOC-4362

                          http://community.landesk.com/support/docs/DOC-23798

 

A more detailed how-to for this can be found here:

LDMS Database tuning for Microsoft 2008 R2 and 2012

How to change the location of the SDMCACHE folder and configure the days files stay in cache.

$
0
0

Issue:

 

How can you move the location of the SDMCACHE folder on clients?

 

9.6 SP2 and newer

 

In 9.6 SP2 this functionality was moved into the Agent's Client Connectivity settings.

 

  • Open the Client Connectivity setting being used by the agent
  • Select Download
  • Check the box for Modify client cache location
  • Enter the local path that clients using this setting should use for their SDMCache directory

 

clientconnectivity.png

 

  • Save the settings, and push the change settings to the client for them to take effect

Please note - in LDMS 9.6 SP2 the max days are limited to 100.  In LDMS 2016 the max days are limited to 20,000.

 

9.5, 9.6 flat and 9.6 SP1

  • On the Client editC:\ProgramData\LANDESK\TMCDownload\downloadermulticastconf.xml
  • Change the<CacheDirectory>value to the desired path.


Example:


Original

<CacheDirectory>C:\ProgramData\LANDesk\ManagementSuite\sdmcache</CacheDirectory>

 

New

<CacheDirectory>E:\LDCache</CacheDirectory>

How to change the Core server connection for the Windows Console

$
0
0

Assumption:

  • LANDesk Management Console is already installed

 

Process:

  1. Delete the following file from any user who will be using the console:
    • C:\Users\username\AppData\Local\LANDesk\CoreConnectionMRU.xml
      • Replace username with the individuals username
  2. Create or modify the below registry key on the machine that the console is installed on:
    • Key - HKLM\SOFTWARE\LANDesk\ManagementSuite
    • String type - REG_SZ
    • String name - CoreServer
    • String value - Core server name or IP
  3. The console will pickup the changes next time it is opened.

 

Example of registry key:

Remote Console Corse Server Change.jpg


How To: Tell What Version of .NET Framework Is Installed

$
0
0

Purpose:

 

There are times where we need to verify what version of .NET is installed. This document will help you determine that.

 

Steps:

 

To find .NET Framework versions by viewing the registry (.NET Framework 4.5 and later)

  1. On the Start menu, choose Run.
  2. In the Open box, enter regedit.exe. You must have administrative credentials to run regedit.exe.
  3. In the Registry Editor, open the following subkey:

 

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

 

 

Note: The path to the Full subkey includes the subkey "Net Framework setup" rather than ".NET Framework setup". If the "Full"subkey is not present, then you do not have the .NET Framework 4.5 or later installed.

 

   4. Check for a DWORD value named Release. The existence of the Release DWORD indicates that the .NET Framework 4.5 or newer has been installed on that computer.

 

release.PNG

 

The value of the Release DWORD indicates which version of the .NET Framework is installed. Please check the below table for the release value that you have.

 

Value of the Release DWORDVersion
378389.NET Framework 4.5
378675

.NET Framework 4.5.1 installed with Windows 8.1 or Windows Server 2012 R2

378758

.NET Framework 4.5.1 installed on Windows 8, Windows 7 SP1, or Windows Vista SP2

379893

.NET Framework 4.5.2

On Windows 10 systems: 393295

On all other OS versions: 393297

.NET Framework 4.6

On Windows 10 November Update systems: 394254

On all other OS versions: 394271

.NET Framework 4.6.1

On Windows 10 Insider Preview Build 14295: 394747

On all other OS versions: 394748

.NET Framework 4.6.2 Preview

On Windows 10 Anniversary Update: 394802

On all other OS versions: 394806

.NET Framework 4.6.2

On Windows 10 Creators Update: 460798

 

 

On all other OS versions: 460805

.NET Framework 4.7

 

This information was created from Microsoft's article: https://msdn.microsoft.com/en-us/library/hh925568(v=vs.110).aspx

 

To View / Remove .Net 4.6+ from View Installed Updates, please see the bottom section of: Issue: Unexpected Behavior On Core with Incompatible .NET Versions

Certificate Manager - Non-Self-Signed Certs & Missing Certs

$
0
0

Problem

The problem can appear as a combination of the below symptoms:

  • LDMS Core server installation pre-check fails with a "Root Certificate Configuration"
  • Clients receive 403.16 error when connecting to the core server.

 

Resolution

 

Resolution will be one of two fixes, removing non-self-signed certificates from Trusted Root Certification or adding the LANDESK certificate to Trusted Root Certification:

 

Non-Self-Signed Certs in Trusted Root Certification Authorities

 

  1. On the core server, click the start button and type in certmgr.msc. This will launch the Certificate Manager.
  2. Expand Trusted Root Certification Authorities - Certificates.
  3. In the right-hand window, the core certificates will be listed. The problem being caused is a certificate in here where the name in the "Issued To" column doesn't match the name found in the "Issued By" column. Screenshot below doesn't have an example of a error causing certificate, but is included to give user an idea of what the window should like.
  4. Either move the mismatched certificate to the Personal folder or delete certificate.

***Special Note*** GPOs may add certificates to Trusted Root Certification Authorities after the install has completed. If this happens, you'll get the HTTP 403.16 error shown next in the document.

 

http://puu.sh/pTVH5/6ea4d09663.png

 

HTTP 403.16 Error

 

This is usually caused by one of two errors:

 

  • In instances of upgrades from an older version of LANDESK to LDMS 2016; the LANDESK certificates may be missing from Trusted Root Certification Authorities
  • Non-self-signed certs being found in the Trusted Root Certification Authorities

This error will appear in logs found on the client as they try to connect to the core. This error will also appear in IIS logs. This can happen during vulscan, getting credentials for preferred servers, etc.

 

LANDESK certificates may be missing from Trusted Root Certification Authorities

 

  1. On the core server, review your agent configuration's Client Connectivity settings.
    1. Typically, on a fresh core it should look something like this:
      1. However, in most upgrades you may have multiples of these. Compare this to your list of certificates in the trusted root and ensure that all of the certs listed here are shown in your trusted root. If not continue with step 2.
  2. On the core server, navigate to \Program Files\LANDESK\Shared Files\keys. In this folder, all LANDESK certificates will be shown.
  3. On the core server, run certmgr.msc and expand Trusted Root Certification Authorities - Certificates.
  4. Compare the certificates listed in the \keys folder against the certificates found in Trusted Root Certification Authorities.
  5. Right-click the LANDesk_xxxxxxx.crt file found in the folder that is missing from Trusted Root Certification Authorities and select "Install Certificate" from the menu.

http://puu.sh/pTWKR/05eab036f8.png

 

     5. In the Certificate Import Wizard, select "Local Machine" for the Store Location. Click Next.

http://puu.sh/pTWPm/ab6222cff1.png

 

     6. Select the "Place all certificates in the following store" and click Browse. Select Trusted Root Certification Authorities. Click Next.

http://puu.sh/pTWVE/6566376a7c.png

     7. Click Finish. A popup window saying the import was successful should appear. Click OK. The certificate will now be listed in Certificate Manager. Repeat the process as needed to ensure all LANDESK Certificates are present.

 

Non-self-signed certs being found in the Trusted Root Certification Authorities

 

Due to possible GPOs or other settings, non-self-signed certs may be found in the Trusted Root Certification Authorities. This can still happen after LDMS 2016 has been installed. To fix this error, the non-self-signed certificate(s) will need to be removed:

 

  1. On the core server, click the start button and type in certmgr.msc. This will launch the Certificate Manager.
  2. Expand Trusted Root Certification Authorities - Certificates.
  3. In the right-hand window, the core certificates will be listed. The problem being caused is a certificate in here where the name in the "Issued To" column doesn't match the name found in the "Issued By" column. Screenshot below doesn't have an example of a error causing certificate, but is included to give user an idea of what the window should like.
  4. Either move the mismatched certificate to the Personal folder or delete certificate.

http://puu.sh/pTVH5/6ea4d09663.png

How To: Delete multiple tasks at one time.

$
0
0

Description

This document reviews how to delete more than one task at a time. Since clean up is so important for organization and keeping track of current activities being able to delete multiple tasks at a time is very valuable.

 

Solution

In order to delete more than one task you will need to first click on the My Tasks/All Tasks/Public Tasks and in the right window use the Ctrl button and click all the tasks you would like to delete, then right click and delete or use the red X to delete them.

 

DeleteMultipleTasks.PNG

 

Additional Information

This action can also be used for Provisioning Templates, Distribution Packages, Managed scripts and most other places.

Ivanti Endpoint Manager 2017.3 Release Information and Useful Links

$
0
0

Release Information

 

Ivanti Endpoint Manager 2017.3 was released on October 5th, 2017.  It is a full release with various problem fixes and enhancements.

 

What's New?

 

About the New Patch Engine in Ivanti Endpoint Manager

About new features and changes in Software Distribution in EPM 2017.3

Ivanti InstallEase now available with version 2017.3+

About new features/changes in Endpoint Security in 2017.3

Whats new for Mac in Endpoint Manager 2017.3

CPE (Configure Profile Editor) for IOS, MacOS and TvOS

New Alerting Features in 2017.3

New Power Management Features in 2017.3

2017.3 Linux Agent 

2017.3+ Linux Agent Conf Files

About Workspaces and Ivanti EPM 2017.3

 

 

How to obtain Ivanti Endpoint Manager 2017.3

Download links are available to customers with a current maintenance agreement

Hashes:

SHA1: b70f8ca542c1298721e59633aaa027afcfe51ab2

SHA256: 938c889272e7462460da49b03afaf3487a860b4fcf8f54cd17ae4a44bedf4dbf

 

Readme:

 

 

Installation / Upgrades

 

How to install Ivanti Endpoint Manager 2017.3

 

Licensing

 

Customers who are already licensed for older versions of Ivanti Endpoint Manager or LANDesk Management Suite are entitled to a license for version 2017.3.  Your current activation credentials will activate the new version.  Please contact support if you encounter any activation or licensing issues.

 

Customers who are not yet licensed, please contact your account/sales/partner contact to purchase the product.

Support will not be able to provide you with the software or license but can assist in finding who to contact if you are unsure.

 

Considerations Before Upgrading

 

LANDESK Smart Card Driver not included in Agent by default as of EPM 2017.3

Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager

Ivanti Endpoint Manager 2017 Architecture - Overview

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

 

Useful Documents

 

About Windows PE versions used in Ivanti Endpoint Manager

Setting up Alerting in EPM 2017.3

Mobile Device Management

Linux and Unix

Endpoint Manager 2017.X (formerly LDMS)  Sustaining and Patch Information

Features and Compatibility EOL Matrix for Management and Security Suite

Download the Latest Service Pack for Ivanti / LANDESK Software Products

Best Known Methods for installing Microsoft SQL Server 2012 for LDMS

 

 

How To: Use the Chrome Developer Tools to Troubleshoot Web Pages, Web Consoles, Web Applications, and Cloud Based Products

$
0
0

 

Introduction

This document will discuss the Chrome Developer Tools, what they are, and how to use portions of them to troubleshoot web based issues. This document is only going to provide an introduction to the Chrome Developer Tools and how some of it's features can help with troubleshooting Ivanti Products but the tools have a lot more capability than what is covered here. As with any tool the more practice you get the easier and more profitable the tool becomes.

 

Note:The available options and where they are located may vary depending on the version of Chrome and the Tools in use. For the most current information please reference the additional information link at the bottom of this article.

 

Launching the Chrome Developer Tools

 

  • To launch the Chrome Developer Tools press F12 in one of the tabs in Chrome.

 

Interface Options

 

Docking

 

You can change the location of the tools. Some find it easier to read the tools at the bottom of the page. Click on the Main Menu (3 dots in the upper right corner) and you will have options on where to locate the tools.

 

DevTools1.png

 

You also have the option to undock the devtools.

 

1- Open the Main Menu (3 dots in the upper right corner)

2- Select "Undock into separate window" which is the first icon below the Main Menu in the screen shot above.

 

Console Drawer

 

There is also an option "Console Drawer" that displays the console window all the time. The console windows will always be on top allowing it to display on every tab. This can help with finding errors.

 

Changing the Theme to Dark

 

1- Open the Main Menu

2- Select Settings

3- You'll see a "Theme" option as shown in the screen shot below

DevTools2.png

 

These are just some of the options available that most users like. For many more settings explore or reference the Additional Information section at the bottom of this article.

 

Network Tab

 

What is the Network Tab used for?

Depending on the circumstances the network tab can be extremely helpful. This tab has the ability to capture web information as it's passed between the browser and the web server or application. You can see content, the type of request, errors, and much more.

 

Status Errors and Their Meaning

 

Status codes are results that are sent back with each GET, POST, etc command in the browser. These codes have different meaning and may be client or server specific. For example codes with a 200 response are normal but anything else would be an error. See the link below for a complete listing of codes. These codes will help with narrowing down the cause of any problems the browser experiences.

 

List of IIS Status Codes and their Meaning

 

Working with HAR Files

 

HAR files are the file type when you export Network information. The file itself appears to be JSON (Javascript Object Notation) in format. HAR files make it possible to move recorded Network information between browsers or other applications.

 

Exporting Network Information

 

The Network Tab information can be exported and then imported into another Chrome instance or sent to support.

 

  1. Open the Network Tab and make sure the red button is on. This indicates that it's recording.
  2. Duplicate whatever problem you are experiencing.
  3. Network information should appear in the Window below
  4. In the Network Windows press Control + A. This should highlight all of the entries in the Network View.
  5. Right-click one of the entries and select "Save as HAR with content" as shown in the screen shot below. Send this information to support.

 

DevTools3.png

 

Importing Network Information

 

Importing a Network Capture is as easy as dragging and dropping the HAR file into the Network View.

 

DevTools4.png

 

Performance Data

The Network Tab can also be helpful in analyzing performance information. The Chrome Developer Tools has a much more detailed Performance Tab however that tab can be confusing to those who are not web developers. In the image below the mouse is hovering over the bars on the "photo.jpg" line and displays performance statistics for each piece of the process.

 

DevTools5.png

 

Console Tab

 

What is the Console Tab used for?

The console is a general log of sorts for the web page. Error messages from the browser will show up here along with any other messages. Some of these errors will not display on the page of course. There are many ways to use this tab in Web Development but for general troubleshooting you'll want to reproduce the problem and then look for error in the Console. You can also (like the Network Tab) save the messages to send to support.

 

Clearing the Console History

 

There are several ways of accomplishing this:

  • Right-click in the Console and press "Clear console"
  • Type clear() in the Console
  • Type Control + L

 

Saving the Console History

 

  • Right-click in the console and select "Save As"

 

DevTools6.png

 

Filtering the Console

 

  • Use the drop down menu to filter

 

DevTools7.png

 

Additional Information and Resources

 

Chrome Developer Tools Online Reference

PowerShell Reboot if Required

$
0
0

Hi

 

I'd like to run some PowerShell scripts in a scheduled task with a "Detect whether reboot is needed" set.

 

But what would I need to put in the script so that Ivanti will pick up that the script requires a reboot. (or not)

 

So basically the script finishes in susch a way that the scheduled task know whether a reboot is required.

 

For example you may say something like:

 

Is service a started

 

If no set flag for reboot

 

If yes set flag for No reboot

 

Thanks

 

Daren

Ivanti 2018 on SQL 2016

$
0
0

This may be obvious but can Ivanti2018 run on SQL 2016 with no problems? I am going to start a side-by-side upgrade and just wanted to check.


Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager

$
0
0

This document outlines the supported platforms for Ivanti Endpoint Manager / LANDESK Management Suite, including supported clients along with server and database requirements for all supported versions.

 

SupportedSupported: Ivanti has validated the operating system (OS) version with Ivanti Software. Ivanti provides full technical support for the corresponding product components running on the OS.
SupportedSupported with a patch: Ivanti has validated the operating system (OS) version with Ivanti Software. Ivanti provides full technical support for the corresponding product components running on the OS, however an additional patch is required to enable support for the OS.
LegacyLegacy: This involves installing an agent from a previous version of LANDESK on the OS and using it with current code. New features are not available and limited support is available for this method of device management.
*Future Update: This column or row is informational and subject to change until release.

 

 

What is the End of Life for Ivanti Products

 

Please click here be referred to our main website for the most up-to-date product availability and support information for all LANDESK products.

 

Supported Ivanti Agent - Client Operating Systems

Operating Systems9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
Mac OS X 10.6.85Legacy99999999
Mac OS X 10.7.55Legacy5Legacy9999999
Mac OS X 10.8.50Supported0Supported0Supported0Supported5Legacy9999
Mac OS X 10.9.x0Supported0Supported0Supported0Supported0Supported9999
Mac OS X 10.10.x1Supported0Supported0Supported0Supported0Supported0Supported999
Mac OS X 10.11.x991Supported0Supported0Supported0Supported0Supported0Supported0Supported
MacOS 10.12.x99990Supported0Supported0Supported0Supported0Supported
MacOS 10.13.x999990Supported90Supported0Supported
Windows XP0Supported0Supported0Supported0Supported0Supported5Legacy5Legacy5Legacy9
Windows Vista5Legacy5Legacy9999999
Windows 70Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows 80Supported0Supported0Supported0Supported0Supported0Supported0Supported5Legacy9
Windows 8.10Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows 10991Supported 1,30Supported0Supported 10Supported0Supported0Supported0Supported

 

Supported LANDESK Agent - Server Operating Systems

Operating Systems9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
AIX 6.x x64 (PPC)0Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 199
AIX 7.1 x64 (PPC)0Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
CentOS 5 x320Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 199
CentOS 5 x640Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 199
CentOS 6 x320Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
CentOS 6 x640Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
CentOS 7 x6490Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
HP-UX 11.31 PA RISC x640Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
HP-UX 11.31 on Itanium x640Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 199
Red Hat Enterprise Linux Advanced Platform 50Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 199
Red Hat Enterprise Linux 60Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
Red Hat Enterprise Linux 7 x6490Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
Solaris 10 (SPARC64/x86_64) with Update 8 or later0Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
Solaris 11 (Sparcx64/x86_64)90Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
SuSE Linux Enterprise Server 10 x32/x640Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1999
SuSE Linux Enterprise Server 110Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 10Supported 1
SuSE Linux Enterprise Server 12 x6499990Supported 10Supported 10Supported 10Supported 10Supported 1
Ubuntu 14.04 LTS99999990Supported 10Supported 1
Ubuntu 16.04 LTS99999990Supported 10Supported 1
Windows Server 2003 Standard/Enterprise0Supported0Supported0Supported0Supported0Supported5Legacy999
Windows Server 2008 Standard/Enterprise0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows Server 20120Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows Server 2016 Standard999990Supported0Supported0Supported0Supported

 

Supported LANDESK Agent - Embedded Operating Systems

Operating Systems9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
Windows Embedded Standard/Enterprise 20090Supported0Supported0Supported0Supported0Supported5Legacy5Legacy5Legacy9
Windows Embedded Standard/Enterprise 70Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows Embedded POSReady 20090Supported0Supported0Supported0Supported0Supported5Legacy5Legacy5Legacy9
Windows Embedded POSReady 70Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
HP ThinPro0Supported0Supported0Supported0Supported99999
Windows Embedded 8.1990Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows 10 IoT Enterprise9999990Supported0Supported0Supported

 

Supported LANDESK Mobile Operating Systems

Operating Systems9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
Android0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
iOS0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Blackberry OS10Supported0Supported0Supported0Supported99999
Windows Mobile 6 or Higher10Supported0Supported0Supported0Supported99999
Google Chromebook299990Supported0Supported0Supported0Supported0Supported

 

Supported LANDESK Console Operating Systems

Operating Systems9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
Windows XP SP3 (SP2 for x64)0Supported0Supported 10Supported 1999999
Windows Server 2008 R2 Standard/Enterprise0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows Server 2012 R20Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows Server 2016 Standard9999990Supported0Supported0Supported
Windows 70Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows 80Supported0Supported0Supported0Supported0Supported0Supported999
Windows 8.1 Update 10Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows 10991Supported0Supported0Supported0Supported0Supported0Supported0Supported

 

Supported LANDESK Core Server Operating Systems

Operating Systems9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
Windows Server 2008 R2 Standard/Enterprise5Legacy 15Legacy 15Legacy 15Legacy 15Legacy 15Legacy 1999
Windows Server 2012 R2 Standard0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Windows Server 2016 x649999990Supported0Supported0Supported

 

Supported LANDESK Core Server Database

SQL Versions9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
MS SQL Server 20080Supported0Supported0Supported0Supported0Supported0Supported5Legacy5Legacy9
MS SQL Server 2008 R20Supported0Supported0Supported0Supported0Supported0Supported5Legacy5Legacy9
MS SQL Server 20120Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
MS SQL Server 201490Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
MS SQL Server 201690Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
MS SQL Server 201799990Supported0Supported0Supported0Supported0Supported
Oracle Database 11g Release 2 (11.2.0.2)5Legacy 15Legacy 15Legacy 15Legacy 199999

 

LANDESK Management Suite and Cloud Services Appliance Compatibility

Cloud Services Appliance Version9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
Cloud Services Appliance 4.25Legacy99999999
Cloud Services Appliance 4.30Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported
Cloud Services Appliance 4.4999990Supported0Supported0Supported0Supported
Future Update*999990Supported0Supported0Supported0Supported

 

LANDESK Management Suite and Asset Lifecycle Manager Compatibility

Asset Lifecycle Manager Version9.69.6 SP19.6 SP29.6 SP320162016.320172017.32018.1
ALM 5.060Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported9
ALM 6.010Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported9
ALM 6.020Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported9
ALM 6.190Supported0Supported0Supported0Supported0Supported0Supported0Supported0Supported

 

LANDESK Management Suite and Service Desk Compatibility

 

Please refer to the following document for the most current information for details on compatibility and integration.

 

 

Asset Lifecycle Manager and Service Desk Compatibility

Service Desk VersionALM 5.01ALM 5.06ALM 6.01
Service Desk 7.6 / 7.6.10Supported0Supported0Supported
Service Desk 7.7.x0Supported0Supported0Supported
Next Version*5Legacy0Supported0Supported

Ivanti Endpoint Manager and Windows 10 versions

$
0
0

A patch has been released to address several issues with Windows 10 Creators edition.

  • Remote control mirror driver will not load
  • LANDESK Antivirus will not load

 

For EPM 2017.1: No action is necessary.

For LDMS 2016: Please update to the latest version of LDMS 2016.  The current version is 2016.3.

For LDMS 9.6: Windows 10 Anniversary edition is the latest supported one.

Here is some further clarification on the different Windows versions.

 

To find out what version you are running go to the Windows command prompt and run "Winver".

 

 

Windows 10 VersionRelease numberBuild NumberNickname
CodenameVersion Screenshot
Initial Release150710240RTMThreshold 110240.jpg
November 2015 Release151110586TH2Threshold 21511.jpg
July 2016 Release160714393.0RS1Redstone 11607.jpg

March 2017 Release

170315063.966RS2Redstone 21703.png
September 2017  Release
170916299.371RS3Redstone 31709.jpg

 

 

How to block automatic update to Windows 10 updates

 

In order to block Windows 10 systems from automatically installing Operating System Upgrades, the following method may be used:

 

Group Policy

Computer Configuration / Administrative Templates / Windows Components / Windows Update Policy

Setting: Turn off the upgrade to the latest version of Windows through Windows Update

Installing CBA8 Failed - Try Again - In-place upgrade to Ivanti's Endpoint Manager 2017.1 from the LANDESK's Management Suite version 2016.3 Service Update 1 ( SU1 )

$
0
0

In-place upgrade to Ivanti's Endpoint Manager 2017.1 from the LANDESK's Management Suite version 2016.3 Service Update 1 ( SU1 ) is failing with

x red x.pngInstalling CBA8 Failed - Try Again

 

installing cba8 failed - try again.png

 

 

LOG file C:\ProgramData\Landesk\ManagementSuite\Install\10.1.10\Log\LANDesk.Install.LDMS_%date%%time%.log reports

INFO: C:\Program Files\LANDesk Files\LANDesk\ManagementSuite\ldlogon\rainstall.exe /delayextensioninstall /dontmove /vroot=ldms.vroot /extension=lclxsvc.dll /install /cert=registry

ERROR: Execution of CBA8InstallCommand completed. Return code: 32, State: Failure (SetupController.ExecuteNextCommand())

 

 

LOG file C:\ProgramData\Landesk\log\rainstall.log reports:

Error 32 copying/moving "C:\Program Files\LANDesk\ManagementSuite\ldlogon\lclxsvc.dll" to "C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\extensions\lclxsvc.dll"

Extension installed, restarting resident agent

RAInstall result 32

 

RESOLUTION

Renamed file "C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\extensions\lclxsvc.dll" to "C:\Program Files (x86)\LANDesk\Shared Files\cbaroot\extensions\lclxsvc___dll" and within the running installation / setup pressed button "Try Again"

 

01002725 installing cba8 ok now on an upgrade to 2017.1 from 2016.PNG

Agent side logs not logging to correct directory

$
0
0

Problem

 

Logs in C:\programdata\LANDesk\log are not updating.

No logs are found under C:\programdata\LANDesk\log.

 

Cause

 

This is caused by the OS not having the "Appdata" directory configured in the registry.

 

Solution

 

  1. Click your start menu and type in Regedit
  2. Navigate to HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders
  3. Create a new string value labeled Common AppData
  4. Give it the value: C:\ProgramData

 

registryvalue.png

 

You may have to reboot the machine for the changes to take affect.

Download the Latest Service Pack for Ivanti / LANDESK Software Products

$
0
0
The following article should be followed in order to properly install an Endpoint Manager Service Update

How to download and install Service Updates (SU) 

Generally available updates

Updates are available from the Console in the Patch and Compliance tool under LANDESK or Ivanti updates.  Please check your LANDESK or Ivanti Updates in the Patch Management tool for generally available Service Updates.

 

 

More information about fixes, known issues and changes contained in the patch can be found in the corresponding readme.

Ivanti® Endpoint Manager 2017.3

Endpoint Manager and Endpoint Security for Endpoint Manager (EPM) released 10/05/2017.   Ivanti Endpoint Manager and Ivanti Endpoint Security for Endpoint Manager are the new names for the product previously known as LANDESK Management Suite. Future product sustainment and patches for EPM 2017 will require EPM 2017.3 be installed first.

 

You can access the download links and related information about the release in the Downloads section: Product Downloads


Ivanti® Endpoint Manager 2017.1

Endpoint Manager and Endpoint Security for Endpoint Manager (EPM) released 05/03/2017.   Ivanti Endpoint Manager and Ivanti Endpoint Security for Endpoint Manager are the new names for the product previously known as LANDESK Management Suite. Future product sustainment and patches for EPM 2017 will require EPM 2017 be installed first.

 

You can access the download links and related information about the release in the Downloads section: Product Downloads

 

For information about Service Updates, please see EPM 2017 Sustaining Patch Information


LANDESK® Management Suite 2016.3

Management & Security Suite 2016.3 released 10/20/2016. LDMS 2016.3 is the latest revision of the LDMS 2016 product. This release contains both fixes and features similar to some of the SPs released previously. Future product sustainment and patches for LDMS 2016 will require LDMS 2016.3 be installed first.

You can access the download links and related information about the release in the Downloads section: Product Downloads

 

For information about Service Updates, please see LDMS 2016 Sustaining Patch Information

 


LANDESK® Management Suite 2016

Management & Security Suite 2016 released 2/5/2016. This release is superseded by LDMS 2016.3. You can access information about the release in the Downloads section: Product Downloads

 

For information about Service Updates, please see LDMS 2016 Sustaining Patch Information

 


LANDESK® Management Suite 9.6

The latest Service Pack for LANDESK Management Suite 9.6 is Service Pack 3, released August 2nd, 2016. Service Pack 3 requires Service Pack 2 to be installed already. You can access the download links and related information about the Service Pack in the Downloads section: Product Downloads

 

To download Service Pack 2 or 3, you must be logged into the LANDESK Community and be a customer with current maintenance or a LANDESK partner.

For information about Component Patches and updates, please see LDMS 9.6 Sustaining Patch Information

 


LANDesk® Management Suite 9.5

The latest Service Pack for Management Suite 9.5 is Service Pack 3, released October 6, 2014.  You can access the download links and related information about the service pack in the product downloads section:


To download Service Pack 3, you must contact Support and be a customer with current maintenance or a be partner.

For information about Component Patches and updates please see LDMS 9.5 Sustaining Patch Information

 


Stop.png

Have you added "*.landesk.com" to the Trusted Sites in Internet Explorer?

Without this action, installing service packs and/or patches may result in unexpected failures.
For detailed steps on performing this action see this article.

 


 

Note: Older builds not listed have been deprecated. Please refer to this article for information about currently supported builds: Supported Platforms and Compatibility Matrix for LANDESK Management Suite/Ivanti Endpoint Manager

Viewing all 415 articles
Browse latest View live


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