I'm currently using 2017.1 version, I have tried to scan my VM host via Unmanaged device discovery -> Discover virtual host and the device is not detected. After I switched to Standard scan, the device is detected but the result is in Others and when I right click on the device, Move to inventory database option is grayed out. I have added VM host admin access in Services -> OS virtualization. How to resolve this?
↧
Discover virtual host
↧
Supported Languages for Ivanti Endpoint Manager
Supported languages for Ivanti Endpoint Manager
| Supported Client Languages | Client | Console | Patch Content |
|---|---|---|---|
| Chinese (Simplified) | x | x | x |
| Chinese (Traditional) | x | x | x |
| Czech | x | ||
| Danish | x | ||
| Dutch | x | ||
| English | x | x | x |
Finnish | x | ||
| French | x | x | x |
| German | x | x | x |
| Hungarian | x | ||
| Italian | x | x | |
| Japanese | x | x | x |
| Korean | x | x | x |
| Norwegian | x | ||
| Polish | x | ||
| Portuguese | x | ||
| Portuguese (Brazilian) | x | x | x |
| Russian | x | x | |
| Spanish | x | x | x |
| Swedish | x |
↧
↧
How To: Reset a Lost SA Password in SQL Express
Problem:
1. LDMS setup creates a SA user with a random password if you select SQL Express database during installation. The password can't be recovered. It has to be changed.
2. Unable to log into the SQL Express server because of a lost SA password.
Solution / Workaround:
Follow the steps below to reset the lost SA password. You may need domain admin access on the Core.
- Login to the server as the default user who installed the core
- Locate SQL Management Studio in the start menu
- Login with Windows Authentication
- Once you are logged into the SQL Server use the Object Explorer and locate the SA user. (Security > Logins)
- Right-click on the SA user and select properties.
- In the Login Properties update the "Password" and "Confirm Password" fields and click OK
If that doesn't work or if you don't have access to the account that installed LDMS on the core server, try the following steps:
- Turn off all LANDesk Services (Here is a document that has a PS script to quickly disable all LANDesk services: How to Stop/Start all LANDesk Services at Once? (now with PowerShell)
- Open an admin CMD prompt and Stop IIS (Very important step)
- Open the "Services" applet in the Control Panel
- Locate the “SQL Server (LDMSDATA)” entry and open its properties
- Enter “-m” into the “Start parameters” field
![SQL.png]()
- Start the service
- Open a Command Prompt as an administrator
- Enter the command:
osql -S CORENAME\LDMSDATA -E
*Note* Be sure to change CORENAME to whatever your server name is or you will get a big long message saying you messed up. - At the next prompts enter the following commands:
1> alter login sa enable
2> go
1> sp_password NULL,'new_password','sa'
2> go
1> quit - Stop the “SQL Server (LDMS)” service
- Remove the “-m” from the Start parameters field
- Start the service
- At this point you should be able to login to Management Studio using the SA user account and the new password you gave it.
- Once you confirm that you can log into SQL Server with the new SA password, launch LANDesk Configure Services and update the SA password on the General Tab
↧
Issues with Self electing services in Console
I can't see any services under the above tab in the console.
I have found this document which describes the issue we are having but the steps do not fix my issue: Unable to enable ANY service under "Self-electing subnet services"
I have found that the IIS Admin service will not start on the Core server which I am guessing may be the problem for us.
Looking at the errors and doing some research it seems that a previous issue we have had on the server may be casuing this problem.
We had to raise a call with Support as we could not login to the console and it was found that there was a problem with the IIS certificate. The support engineer recreated a new certificate which got us working again but since then the IIS admin service will not start.
Solutions on the web state to uninstall IIS and re-install it.
Can I do this on the Core server without breaking anything more?
↧
How to force Management Console not to use hostnames and to use IPs
Hey everyone.
I'd like to force Management Console to use IP address for Ping/Computer Management/etc from right-click context menu. By default it's using hostname to connect devices but if server and clients are not in domain, for example, or there is some DNS issues, then it's impossible to use Computer Management, for example, from Landesk Management Console.
Was tried to find some solutions how to force IP over hostname but wasnt able to find anything.
Would be grateful if someone will point me where to look such settings.
↧
↧
How to run this PowerShell script on all systems routinely? (To disable NETBIOS)
Hello,
For obvious security reasons - we want to disable NETBIOS Name Service on all machines in our network. This is a manual change that can only be automated via a script (good job Microsoft!). We tried deploying a GPO to run the PowerShell script on startup - but it does not work all the time (for all NICs) as the machine must have an active IP on all interfaces in order for the script to disable NetBios.
Is there anyway to run a PowerShell Script on machines every X hours or, after 30 minutes of logging in to their workstation?
This is the script we want to run. It iterates through all NICs and attempts to disable NetBios.
$adapters=(gwmi win32_networkadapterconfiguration )
Foreach ($adapter in $adapters){
$adapter.settcpipnetbios(2)
}
↧
Console Single Sign-On
Question:
What are the single sign-on options under Configure Services?
Answer:
Single Sign-On allows users to login to the Win Console without requiring credentials to be entered. Below are the three options:
- None
- This option requires you to enter a username and password when logging into the console
- Only
- This passes and authenticates with the current Windows credentials.
- Mixed
- This will allow you to either manually enter LDMS credentials or click login to pass the current Windows credentials
↧
can you copy console settings from one user to another
can you copy console settings from one user to another
↧
Video - Self-Electing Subnet Services in Ivanti Management and Security
↧
↧
Incorrect IP addres of managed device
Dear All,
I've a problem in my LDMS 9.60 SP2 with an incorrect IP address of the device. I do not know why but after installing the Landesk Agent on the client device, it appeared in the LDMS console with an incorrect IP. Because of that I'm not able to execute the "Patch and compliance scan" and deploy new patches to the client server.
I am quite new to the Landesk related topics, so I am asking for help as for a beginner . I have read a lot of articles about this problem, but none has been helpful to me.
↧
SQL Query To Remove User
DISCLAIMER
The following article contains information on manipulating your database.
It is CRITICAL that you have a full backup of your database prior to making any modifications to the database.
Failure to backup your database may result in permanent loss of some, or even all data.
Please consult with your DBA where applicable.
Overview
Attached is a SQL Query that will delete a console user and all of their associated details. This should only be used as a last resort, as you will lose data.
Any objects owned by that user will be removed, including (but not limited to)
- Distribution Packages
- Queries
- Reports
- Scheduled Tasks
This script is NOT supported by Ivanti. Use at your own risk.
In the script, you will need to provide the username of the user. The place to do so is indicated in the SQL script itself.
↧
Network view and Active Directory
Looking for an automatic way for the group devices in the network view to stay up to date with computers that are in AD. Does anyone have any clever ways they could share on how they handle this? Thanks!
↧
Console Install for 2016.3 fails on windows 10 1709
Anyone had a problem and fix for installing the 2016.3 console on windows 10 version 1709?
It seems to work on Windows 10 1607 with .net 4.62 1709 uses .net 4.7.
↧
↧
IEM v2017.1 - Bug sur la console Web pour la distribution logicielle (droit effectif non respecté, alors que OK sur la console lourde)
Bonjour,
lorsque je restreins les droits sur "Public" pour la distribution logicielle (pas de droits accordés à l'utilisateur), le résultat est cohérent sur la console lourde mais pas sur la console Web, l'utilisateur peut modifier et supprimer des tâches publiques.
Merci pour votre aide.
Cordialement
Benoît.
↧
Agents not communicating with the core server
Purpose
This document was created to cover various reasons why the agent won't communicate with the core server.
Solution
- Agent discovery is not working (agent status icons) - Agent Status Icons Suddenly Not Appearing in Console
- Firewall ports may be blocked - Ports used by LANDESK Management Suite - Full List
- Check that the following registry key exists on the core server:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL, Value name: ClientAuthTrustMode, Value type: REG_DWORD, Value data: 2
- Possibly related to database exceptions - 6 Overlooked Problems related to Database Exceptions
- Inventory is not processing your scans - 10 simple checks to Troubleshoot Inventory - Devices not updating, Duplicated or Missing Scans
- Inventory scans failing on client machines - Running Inventory Scan on a Client Machine Results in Error Message "The Inventory Server Did Not respond"
- Vulscan is failing to check in with the core server - About Vulscan and SSL Verification
↧
The window does not pop up when selecting the Change settings button to schedule an agent settings change
Problem
Any pop up window from the console, usually under agent settings or Patch and compliance, will not open. The button will be clicked and nothing else happens.
Solution
Please run the following command on the core server database. Be sure that you are taking the proper backups and snapshots prior to making any database modifications.
begin tran delete from KEYVALUE WHERE APPLICATIONNAME = 'SWDTaskSettings' AND KEYNAME = 'DefaultTaskOptions' commit
Once this is done running, relaunch the console and test creating a task.
↧
LDMS 9 Webconsole error "Exception: Conversion failed when converting the nvarchar value"
Symptom:
In the LDMS 9 Webconsole under administration preferences you receive the following red text error on the license page Error "Exception: Conversion failed when converting the nvarchar value
"
Resolution:
ApplyDownload the Latest Service Pack for Ivanti / LANDESK Software Products or patch WEB-4202390
Workaround:
This error can be resolved by removing a row from the database. (make sure to back up database before doing any delete statements)
In SQL Server Manager open a new query under the LDMS Database instance
Select * from CoreConfiguration
Note: Depending on configuration this table might return multiple rows. Find the row with the configuration name AgentDiscovery this is the row we need to remove.
In this example the delete statement would be:
delete from coreconfiguration where coreconfiguration_idn = 2
↧
↧
.NET error when installing LDMS 9 Remote Console on Windows Vista or Server 2003
Problem
Some users have seen problems with installing the LANDesk Management Console for LDMS 9 on a Windows Vista machine. The client machine will pass the prerequisite checker, but then once the installer starts, an error is presented that "The following prerequisite components are Missing: Microsoft .NET 2.0 or 3.0 must be installed". This will appear despite having .NET installed, even up to version 3.5 SP1. This will happen on any Vista or Server 2003 computers that have IIS or IIS components installed or active, but do not have the ASP.NET components installed. Normally this occurs on Vista when the client machine has Exchange management tools installed.
Cause
This appears to be caused by a conflict on the Windows Vista computer with IIS and .NET. The prerequiste checker correctly identifies Microsoft .NET installed on the machine, but the setup application checks to see if IIS is installed, it then checks to see if the ASP.NET functionality is installed on the IIS component.
Resolution
This can be resolved by installing the ASP.NET on the target computer or removing the Application Server Role. To do this, open the "Turn Windows features on or off" dialog (Control Panel -> Programs -> Programs and Features -> Turn Windows features on or off) and install the ASP.NET component (Internet Information Services -> World Wide Web Services -> Application Development Features -> ASP.NET)
Once this is installed, restart the Remote Console installation and it should complete successfully.
↧
Oracle issue causing Web Console Error: Unable to validate user with the database.
Description:
When logging into the Web Console you receive the error:
"Unable to validate user with the database".
With Log events turned on you will receive the following Event Viewer Error:
"OracleSQLServerName: TNS:could not resolve the connect identifier specified."
Cause:
The Oracle client directory did not have the correct permissions.
Resolution:
- Right click on the C:\Oracle folder (the root folder where your client is installed) and choose Properties.
- On the security tab add the local machine's Users group (or if you prefer, add the IIS and ASPNET users individually). Grant Read & Execute, List Folder Contents and Read privileges.
- Click "Apply".
- Click "Advanced"
- Check "Replace permission entries on all child objects ..."
- Click "Apply". This will take a while to propagate the security grants down to every file and folder of the Oracle client.
↧
Proxy Server configuration when using the LANDesk Components such as the Web Console
Many organizations use Proxy servers for internet connectivity. LANDesk components, including but not limited to, the LANDesk Web Console often fail when the proxy is misconfigured for the LANDesk environment.
This article will explain the proxy settings needed for the Web Console to work correctly.
Please note the following:Specific proxy configuration settings are outside the scope of LANDesk Technical Support. If there are any problems caused by using Proxy auto-detect settings in Internet Explorer, then either the Proxy server settings must be changed or the Proxy excluded for the LANDesk server as explained below.
When attempting to login to the web console, the following error can occur:
Could not log into the management console. Try logging in again.
Unable to validate the current user with the database.
Web Console logging can be enabled by adding the following registry key to the Core Server:
HKLM\Software\LANDesk\ManagementSuite\Core
Type: DWORD
Name: LogEvents
Value: 1
In the Application Log, the following information is displayed.
The description for Event ID ( 0 ) in Source ( LANDesk Abstraction Layer ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Request to get database connection string.L01NTLDK01 specified as core. |
Cause
This issue or other problems using the Web Console can be caused by incorrect proxy settings.
Microsoft Internet Explorer has the following options when configuring a proxy as seen below. These settings can also be controlled by using Group Policies.
It is important to differentiate between the Logged on user and the user configured for the LANDesk Com+ Application Identity. Each user will have their own proxy settings.
For the user configured for the LANDesk Com+ Application Identity, one of the following must be true:
- The proxy must be bypassed. (Recommended)
- The proxy authentication must succeed. (Be ready to involve your Proxy Administrator.)
Bypassing the Proxy
It is recommend that the proxy must be bypassed when the Core is talking to itself, and when workstations connect to the Web Console.
If the "Automatically detect settings" option is checked in the IE proxy settings then the Web Console authentication will fail. Microsoft does not allow for bypassing the proxy, so this option must NOT be checked.
If "Use a proxy server for you LAN" option is checked, then there is an option to "Bypass proxy server for local addresses." If this is not enabled and configured, then the proxy will still be used. This option must be configured to bypass the proxy for the Core Server IP, Core Server name and FQDN, and 127.0.0.1.
Authenticating to the Proxy
Proxy authentication is outside the scope of LANDesk support. LANDesk Support does not support or have information on how to configure proxy settings or provide assistance in configuring it.
What we do provide is information on what is failing.
If a proxy is in use and the user configured for the identity of the LANDesk COM+ Application cannot authenticate to the proxy, then "Unable to validate the current user with the database" will occur. Usually the site that is accessed by Com+ is the following:
Have the proxy administrator make any connections to this site work using the user configured for the identity of the LANDesk COM+ Application Identity. If the Proxy administrator is unsure how to do this, then you should resolve the issue using the other option of "Bypassing the proxy".
Resolution
Solution 1 - Bypassing the Proxy (Recommended)
- Disable "Automatically detect settings" for the IE Proxy settings for the user configured for the LANDesk Com+ Application Identity and any other LANDesk user that may not be able to authenticate to the proxy.
- Enable the proxy using the manual settings.
- Check the box for "Use a proxy server for you LAN".
- Check the box for "Bypass proxy server for local addresses."
![]()
- Click Advanced.
- Add Exceptions for each of the following items:
Core Server Name
Core Server FQDN
Core Server IP
Localhost IP
For example, the settings for a Core named vm88.mydomain.com with an IP of 10.1.1.1 would be:
vm88; vm88.mydomain.com; 10.1.1.1; 127.0.0.1![]()
- Click OK.
- Click Apply.
- Cick OK.
- Check the box for "Use a proxy server for you LAN".
Solution 2 - Configuring the Proxy to Correctly Authenticate
LANDesk has no information on this other than that we are attempting to hit the following site and proxy authentication is failing:
https://CoreServer/landesk/managementsuite/core/ssl/information/databaseinformation.asmx
- Change the Com+ Application Identity to a User That Can Authenticate on the Proxy.
- OR - - Have the Administrator of the proxy server configure the Proxy to properly authenticate the user configured for the LANDesk Com+ Application Identity. If the administrator is unsure as to how to do this, then use Solution 1 - Bypass proxy server.
↧