I am trying to upgrade my LDMS Remote Console to v9.5.  I have successfully upgraded my core, installed .net 4.0 on my workstation, installed all other required windows updates, and when I run the installer, it fails on Upgrading Remote Console.  I have uninstalled all LANDesk components, disabled SEP, and it still fails.  I am not sure why.  I have attached the log file to this post.  Since there is very little information on upgrading the console, I was going off of what others have posted in similar discussions. I kicked off the remote console from the main setup.exe file for LDMS9.5.  I was never given the option to select what I wanted to do since, at first it detected my current installation of the console.  Even after uninstalling the Landesk components, and several reboots, the installer still picks up where it left off, on the Upgrading the Remote Console portion.

Any help would be appreciated.

Hi,

I haven't had a problem dragging and dropping a group or role to a user before and have done so with the Analyst role in the past. However, I am now receiving the following error message:

"Could not add role Analyst to user ________. Role Analyst has a different user type associated with it."

Looking for a little help why this would all of the sudden start up and how to resolve it. There are still two Analyst licenses available.

Problem

• Web Console timing out, not connecting, or being very slow
• An error of HttpException (0x80004005): Request timed out - (ignores executionTimeout)

Cause

This kind of issue is typically occurs when a server-side code function or macro executes for a period of time longer than the maximum timeout period allowed for server-side code execution.

This can be caused by multiple things :

-Too many users logging into the web console and overloading the worker processes, causing timeouts and big slowdowns on the web console and in extreme cases unusable

-A windows update slightly changing the .net framework in a unknown way , requiring the.net to be re-registered

-A slow network connection to the core server from the administrators computer

Resolutions

• To Re-register .net
• To increase the query time out for the console and web console
• And Decreasing/Managing load on worker processes associated with the web console
  

How to Re-register .net

To Re-register the ASP.NET 4.0 components. Please reference Microsoft KB 2015129for details, or a brief summary follows:

1. Open a command prompt with administrative privileges on the core server
2. Change directory to
   • 32-bit Windows:
     %windir%\Microsoft.NET\Framework\v4.0.30319
   • 64-bit Windows:
     %windir%\Microsoft.NET\Framework64\v4.0.30319
3. Re-register the components:
   aspnet_regiis.exe /iru
4. Reset the IIS services:
   Iisreset

How to increase the query time out for the console and web console

You can increase the query time out in the console and web console using this article :

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

Decreasing/Managing load on worker processes associated with the web console

Finally to decrease the load on the worker processes which for the remote console, you can set them to automatically 'recycle' so that the memory , cache etc. associated with these processes will automatically be cleared and new process be created in their place.

Here are some article on the process of recycling associated with the IIS application web pools

http://technet.microsoft.com/en-us/library/cc753179%28v=ws.10%29.aspx

In this example I am going to use the elapsed time option, this way you will know exactly when the application pool gets reset as opposed to every time a certain memory level is reached which can be very sporadic.

Under IIS manager , navigate to the application pools window pane, via the left column.

Right click the LDAppWeb, where the remote console application resides, and click on recycling…

Notice the default time interval for this application is 1740 minutes, change this to 120 minutes and the worker processes associated with this application pool will refresh ' recycle' every 120 minutes. This should relive pressure on the main web console.

This method can also be manually used instead of performing an iisreset cmd, as this will reset only the applications associated with the web console as opposed to the entire IIS infrastructure.

To do this , right click the LDAppWeb, located in the application pools window in the IIS and click recycle. This force the application pool to 'restart' at that moment in time. This can be used in times of urgency to relieve the load on the worker process immediately

Is there a way to select multiple scheduled tasks and delete them as a group? I have a couple hundred Windows 7 Pulls I'd like to get rid of.

Hi, I receive the following error message when attempting to open the console. I was upgraded to version 9.5 about one month ago. Everything worked fine until a week ago. I uninstalled the console then re-installed it and continue to get the same error message. The core server has not been renamed. I can successfully start the console on other devices. I am running Windows 7 64-bit.

Console Initialization Error:  Error calling ParseLocalConnectionString

Parameter name: local_connection_string.

After upgrading to 9.5 sp1 i dont not have the option to view as report on inventory for a machine?

In the inventory of a machine i used to go to software then add or remove programs then program then right click and hit view as report? I used to print this out and use it for machine upgrades but i dont get the view as report option anymore. Any ideas? Dont think they would remove it

Hi,

After a few days the core was installed the console is showing hundred of "Computer" object entries in the query tool, and each day is getting lager the number of these entries.

We don´t know where are they comming from. but the number is mounting up every day and it is becomming more and more difficult to work with queries.

Any idea on how to stop these from increasing and how to get ride of the already existing ones?.

Thanks!

View has changed and being admin I rarely if ever look at the web console. I have some users reporting the web console now is very hard to use and these users look up very basic info like who is the primary owner but this information is now impossible to find. Anyone use 9.5 web console and know where to view logged in user or primary owner information?

Hi,

How can I know all the software packages and patches applied with the LANDesk console to a client if the tasks has been deleted from the console? Is there any reference in the LDMS DB where all the software distributed to a client node is recorded permanently?

Thanks!

The links below go to the LANDesk Help Center user documentation:

• Console overview
• Console setup wizards
• Start the console
• Console Network View
  • Understand the Network View
  • Network View icons
  • Create groups in the Network View
  • Configure the Network View with column sets
  • Create column sets
  • Apply column sets to device groups and queries
  • About the Column Configuration dialog
• Managed devices
  • View managed devices
  • View device properties
  • Configure device monitoring alerts
  • Monitor devices for network connectivity
• Console tools and features
  • Access console tools
  • Move and resize tool windows
  • Search for items with the Find bar
  • Toolbar options
  • Shortcut menus
  • Status bar
  • Save console layouts
  • Change the core server connection
• Using the Inspector
  • Viewing data using the inspector
  • Auto-inspect items
  • Manually inspect items
  • Unlinking dynamic content

I have created a query to report on nodes with IE8 installed. But this query returns hundreds (1500) more nodes than really exist in the inventory database. Some of those roge nodes are computers we have discovered in UDD but stil have not been deployed with the LDMS agent. More over, these results are completely inconsistent when we run the query from different LDMS native consoles, the numbers are quite different from one remote console to the other... Weird. We are using LDMS 9.5.

Any ideas?

Description

Console commands run as the user logged into the Operating System not the User Logged into the Console.

Many security models require that users log into windows operating system as a user with minimal priviliges, and use a user with more rights only when necessary.

If this security model is used, it often occurs that users launch the 32-bit Console without switching users but then log into the 32-bit Console as the privileged user.

Many Console actions, especially right-click actions such as Remote Control, will fail or result in a prompt for credentials.

See the following article for more information:

Remote Control - Understanding the User Accounts Involved in Remote Control

Cause

Running the Console.exe process as a as the minimally-privileged user but logging into the Console as a privileged user does not cause processes launched by Console actions to occur as that privileged user. Instead processes are launched as the minimally-privileged user, which is logged into the operating system.

Resolution

The Console.exe process should always be launched as the privileged user.

To accomplish this change the 32-bit Console shortcut to prompt for the user when launched.

1. Right-click on the shortcut and choose Properties.
   
   
2. Click Advanced.
   
   
3. Check the box to Run with different credentials.
   
   
4. Click Ok to closed the Advanced Properties window.
   
   
5. Click Ok to close the shortcut properties window.
   
   
6. Run the shortcut and you now prompted to select the user to run as.
   
   
   

From within the LANDesk Console one of the more useful features is the ability to right click a machine and perform administrative tasks.

Some of these tasks are:

Request an inventory scan

Wake up a machine

Shut down a machine

Request a Security scan

When one of these options is selected the LANDesk console make a call to IIS and passes the command line parameters to the core.secure/corerequest.asmx page.

The URL for this page on the core server is:

http://localhost/landesk/managementsuite/core/core.secure/corerequest.asmx

This page is seen here being accessed from the core server.

Each command requires a client side identifier, this can be the Machine GUID (found in the registry under HKLM\Software\Landesk\Common API) or the machines IP address.

If the right click commands fail to run, check the following.

1.  Can theCoreRequest page be browsed from the Console running the commands?

http://[core server name]/landesk/managementsuite/core/core.secure/corerequest.asmx

2.  Verify that the command is being sent from the core server.

On the core server under the \\[Your Core Server]\LDMAIN share the raxfer.log file will store the attempt to run the remote execute.

<block>Thu, 19 Mar 2009 10:20:56 4724 388 Performing remote execute, target 10.16.228.214:9594, hash 5b5c5c77</block>

3. Verify that the command was recieved on the client.  In C:\Program Files\LANDesk\Shared Files\servicehost.log the command line parameters will be displayed.

<block>

Thu, 19 Mar 2009 10:36:14 2608: Exec: Exec: Launch request <"C:\Program Files\LANDesk\LDClient\vulscan.exe" /id=7 /run ldiscn32.exe /NTT=slc-smith-88:5007 /S="slc-smith-88" /I=HTTP://slc-smith-88/LDLogon/ldappl3.ldz /NOUI> (sync 0, timeout 300)

</block

Question

The 32-bit console shows the last logged in user.  Can showing the last username in the 32-bit console be disabled?

Answer

Yes.

1. Open theCoreConnectionMRU.xml with a text editor and remove the username.

2.Thenset the CoreConnectionMRU.xml to read only.

Note:This must be done separately on the Core and the Remote 32-bit consoles.

Description

The following is a twenty minute E-Learning session to help you understand the cause of the error "Unable to validate the current user with the database" when logging into the web console.

It explains the error, shows you have to duplicate the error, shows you why the error occurs, and finally how to resolve the error.

Download and Watch

E-Learning session

Description

This document is created to provide an LDMS 8.8 matrix that will help  indicate when the Web Console will successful authenticate versus when  authentication fails with: "Unable to validate the current user with the  database".

Failure to authenticate to the Web Console results in the following  error:

Unable to validate the current user with the database.

For more information on this error, please see the following community article:

Web Video: Unable to validate the current user with the database

LDMS 8.8 Matrix for the requirements to successfully login to the Web  Console

Other Causes that Prevent Logging into the Web Console

If the LANDesk1 Com+ Identity information is correctly a domain user that is in the LANDesk Management Suite group on the Core Server and this error still occurs, the following table contains other causes:

Description

Applies to LDMS 8.7, 8.8, 9.0

After deleting a node from the LDMS Console and refreshing the node pops back up into the list.

Console.exe.log:

3/7/2008 10:03:56 AM : Critical Exception: System.Runtime.InteropServices.SEHException: External component has thrown an exception.

at IDALLib.IDALRecordsetClass.DeleteDevices(String conStr, Object& pvtDevices)

Or:

Database.ExecuteDataTable: System.Data.OleDb.OleDbException: Invalid object name 'AlertRulesetDeployment'.

Key Words: Unable to Delete Nodes, Can not Delete Nodes, Cannot Delete Nodes, Unable to Delete Devices, Can not Delete Devices, Cannot Delete Devices.

Cause

There are two causes to this issue:

1) There is metadata in the LANDesk database which references in the delete query that no longer exists. The list of tables is created from the METAOBJATTRRELATIONS table.

Or

2) There is metadata missing for tables or columns that do exist in the database. LANDesk must have metadata to map out its delete statements.

Resolution for cause 1)

For LDMS 9.0Only, apply patch DB-4196790. Reboot is required!

For LDMS 9.0 SP2, apply patch DB-5236490.2 (Get from support).

If the problem still exists or forLDMS  8.8 or prior versions see below.

1) Stop all the LANDesk & Intel services

2) Backup the LANDesk DB

3) For SQL Databases

deletefrom METAOBJATTRRELATIONS where tablename in   (selectdistinct tablename     from METAOBJATTRRELATIONS     where tablename notin (select table_name from information_schema.tables))

4) For Oracle Databases

These commands should be run by an Oracle DBA. First you must compare the meta data with the actual data, replace the word 'LANDESK' with the correct user.

selectupper(tablename) from METAOBJATTRRELATIONS 
 minus select table_name from all_tables where owner = 'LANDESK';  

This will return the result you will use with the next statement to delete the bad reference. DO NOT DELETE VIEWS, only delete the incorrectly referenced table which is generally ALERTRULESETDEPLOYMENT.

Run the next command to remove the invalid table reference.

Replace the  with the result tablename (not views) returned in the first query.

deletefrom METAOBJATTRRELATIONS whereupper(tablename) = '

Resolution for cause 2)

This is a manual process of manually attempting to delete the record from the computer table. SQL studio will provide you the error which states what table that contains data for this computer still. It is either this table or one it depends on which doesn't have metadata.

Once the bottom level table or child table is found and a record is able to be deleted, then: select * metaobjattrrelations where tablename = 'tablename'

If no records are returned then metadata doesn't exist for this table.

Contact support or manually create metadata.

Run DBRepair.exe then CoreDBUtil.exe

-DBRepair

4) Download the Correct version of DB Repair from: Community article DOC-2297

5) Copy the file to ...\LANDesk\ManagementSuite.

6) Stop the LANDesk Inventory Server service.

7) Run DBRepair(DO NOT Run from a share (ldmain))

8) Click on each item except for anything under "Custom Data" and click the clean button.

9) Close DBRepair.

-CoreDBUtil

10) Run CoreDBUtil.exe from ...\LANDesk\ManagementSuite\ folder

11) Click the Build Components button (This compares the database to the file Datamart.xml and makes repairs. It usually takes 5-15 minutes. DO NOT Stop the process!!!)

12) When the Build Components process finishes a message will appear that says that the process is done.

13) Close CoreDBUtil.

14) Start the LANDesk Inventory Server service.

15) Start the LANDesk & Intel services that had been stopped in step 1 or alternatively reboot the core server.

NOTE: An issue has been resolved with the upgrade from 8.7 SP5 to 8.8 with the following SQL Query:

Update metaobjattrrelations set tablename = 'UNMODELEDDATA' WHERE TABLENAME = 'ALERTRULESETDEPLOYMENT'

Article on how to install Microsoft SQL Management Studio Express and Run a query:

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

========================================
  To Create a Column Set
  ========================================
  1. Click Tools | Administration | Column Set Configuration
  2. Right click My Column Set and click New Column Set...
  3. In the Column Configuration dialog, enter a name for the new column set
  4. Select inventory attributes from the list and add them to the Columns list by clicking Add to columns. Remember to select attributes that will help you identify the devices in the device list or returned by the query
  5. (Optional) You can customize how and where the columns appear in the network view by directly editing a component's heading, alias, and sort order fields; or by removing or moving the selected component up or down in the list with the available buttons
  6. (Optional) You can specify more precise qualifying data for software components. Select the software component, click the Qualify button, and then select a primary key value from the list of available values
  7. Click OK to save the column set

========================================
  To Apply a Column Set
  ========================================
  1. Click and drag the column set into the network view on the right or drag over the device group on the left

NOTE: Some inventory items may have more than 1 result. If that's the case duplicate devices may show in the console to represent each entry.

For more information, see page 31-33 of theLDMS 8.8 User's Guide

***NOTE*** At this time you are not able to set custom column sets for the scheduled tasks tool.

Selecting "manage local users and groups" on a device returns no information

One resolution for this issue is to ensure that the ASP.NET account has read permissions on the Inetpub folder on the LANDesk Core Server.

***Following is more troubleshooting information***

Troubleshooting and log files

Console calls a core webservice to contact CBA and run \ldclient\localaccount.exe on client to perform the local user query or modification.

1- Console.exe.log

Checking console log is a good start, it will record the detail error information when 'Manage local users and groups' window get blank. Most common cause for this issue is wrong IIS permission and directory security setting, console will log the detail http error like "Server Unavailable"...

Console log path: Core or Addition console
\Program Files\LANDesk\ManagementSuite\Console.exe.log

2- Web service access

A. Please confirm following URL can be access from core server or additional console,

http://<corename>/landesk/managementsuite/core/core.secure/LDRemoteManageAccount.asmx

***Replace <corename> by your coreserver host name***

If get any HTTP error here, please check IIS log as well and get HTTP error code at the end of log item,as following,

2010-01-18 22:36:08 W3SVC1 192.168.100.32 POST /landesk/managementsuite/core/core.secure/LDRemoteManageAccount.asmx - 80 - 192.168.100.32Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.42) 401 5 0

IIS log path: Core
\WINDOWS\system32\LogFiles\W3SVC1

B. HTTP Error code and resolutions

If access LDRemoteManageAccount.asmx failed,please go IIS manager-Default web site-Default web site-landesk-managementsuite-core-core.secure

HTTP 401 5 0
- Right click core.secure and properties,Directory Security tab, Authentication and access control, ensure only 'Integrated Windows authentication' was checked.

HTTP 500 0 0
A. Right click core.secure and properties,Virtual directory tab, confirm the setting like this screen shot,

B. Right click core.secure and Permissions, the default permission should be assigned as following,
Full Control: Administrators,LANDesk Management Suite,SYSTEM
Read&Execute/List Folder Contents/Read: ASPNET,NETWORK SERVICE

C. Identity setting for Application pools - LDAppmain, default identity should be NETWORK SERVICE, change it to LOCAL SYSTEM for test purpose.

Run IISRESET and try again,

Note: This should be used only for testing, Microsoft recommends that AppPools run as Network Service. If this resolves the issue, it usually signifies that the Network Service does not have proper rights to objects in IIS, can be either NTFS or IIS permissions.

3- Client

If console.exe.log have no error and only log message like "call webservice to get local account information",  LDRemoteManageAccount.asmx also can be opened successful, it might caused by network traffic blocking or client side issue.

A. Confirm CBA service can be access from core, the binocular icon display correctly in console network view. if not, check following,
- LANDesk Management Agent service is started,TCP&UDP 9595 is listening on client.
- Browse http://<client_name/IP>:9595 from core can open web page correctly.if not, check client firewall and network security setting to see any policy block the traffic.

B. Check following log for client side issue.

Log path: Client
C:\Program Files\LANDesk\Shared Files\residentagent.log
C:\Program Files\LANDesk\Shared Files\Servciehost.log
C:\Program Files\LANDesk\LDClient\localaccount.exe.log

***Attachment LocalUser_client_log.txt is a success log on client***

When logging in to console on one machine, an error appears which says: Console initialization error: The type initializer for "Computer" threw an exception. This error occurs after changing the password on the domain. After clearing the error, there is nothing listed under "All Devices". Logging into another computer with the remote console results in no problem. Other users can log into the console on the effected machine without a problem.

Cause License cookie for the current user is either damaged or incorrect.

Use the following steps to resolve the issue.  If one step does not fix the problem, continue on to the next step.

Step 1:

Open the registry editor on the machine affected and navigate to:

HKEY_CURRENT_USER\Software\LANDesk\ManagementSuite\Core\

Delete the LicenseCookie value.

Logging back into the console will recreate the license cookie.

Step 2:

Open a command prompt on the computer the console is installed on and run the following commands:

cd \program files\common files\system\ado

regsvr32.exe msado15.dll

cd \winnt\system32

dir atl*.dll

regsvr32.exe atl71.dll (or whichever atl.dll you have)

cd \program files\landesk\managementsuite

regsvr32.exe parser.dll

regsvr32.exe ldcache.dll

regsvr32.exe msinterp2.dll

regsvr32.exe idal.dll

In LDMS 8.7 this can happen if you are using a remote console, the core is on SP2 but you haven't installed SP2 on the remote console. In general, make sure that the SP version on the remote console matches the SP version on the core.

Step 3:
Run C:\Windows\Microsoft.net\framework\<.NET VERSION>\aspnet_regiis.exe -i

Step 4:
Reinstall the MDAC component on the machine. Right click and reinstall from C:\WINDOWS\inf\mdac.inf and obtain the file off of a windows CD. Or download a new copy from Microsofts site. Check Microsofts download site for the latest version.

Step 5:
Check the console.exe.log. If there is a COMException listed then change the COM+ objects to a different identity.

In LDMS 8.7 this can happen if you are using a remote console, the core is on SP2 but you haven't installed SP2 on the remote console. In general, make sure that the SP version on the remote console matches the SP version on the core.