Hello,

I have just installed my company's new core server 9.5, and the help desk staff will be using remote console to use LANDesk. When they try to remote into a computer it asks for their credentials everytime before they are allowed to control any machine. I did some searching through the community portal and thought it had something to do with the COM+ accounts. I changed the accounts out for AD credentials, but my help desk staff is still being asked to input their own credentials everytime. Is there something that I am missing?

Thank you!

Anthony

Problem

When try to log into Core server, there will be a error message pop up saying:"Console Initialization Error: Unable to connect to the remote server"

You will see below error message in the console.exe log and screen shoots shown as below.

+++Console.exe.log++++

05/14/2013 16:53:59 INFO  1524:Main Thread RollingLog : Starting authentication

05/14/2013 16:53:59 INFO  1524:Main Thread RollingLog : Resolving rights for ADMINISTRATOR

05/14/2013 16:54:01 INFO  1524:Main Thread RollingLog : WebException Exception: Unable to connect to the remote server

Environment

LDMS9.0 or later version

Cause

Site Bindings does not specify the SSL certificate

If it is certificate issue such as certificate missing or incorrect. More information can be found in this article:

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

Solution

1. Open IIS manager->Site-> You will see something similar to below screen shoot.

2. Click Bindings

3. Add-> Choose https-> Choose the correct Landesk certificate-> Clilck Ok

4. Try to log on the core server again.

Hi,

Assigned rol and rights to a user to only see Scripts, Distribution and Scheduled Tasks from a Web console. Although the web console user is not an administrator he is able to see all the scripts and packages in the core server even though these scripts are set as private for a different user. All scripts and packages are shown as "PUBLIC" in LDMS 9.5 web console even though these packages are set as private in the native console.

Anybody found same problem?

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

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

We run multiple Support Groups, eg Infrastructure, Applications, Desktop Support. At 80% of SLA we need to send a message to the manager of the Assignee's Support Group only and not all the managers. How would I do this using Response Levels within Service Level Management?

Error

When opening the Console, after entering your credentials and trying to login, you receive the error:

Console Initialization Error: Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.

The request failed with the error message:

--

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">

<head>

<title>IIS 7.5 Detailed Error - 500.19 - Internal Server Error</title>

<style type="text/css">

<!--

body{margin:0;font-size:.7em;font-family:Verdana,Arial,Helvetica,sans-serif;background:#CBE1EF;}

code{margin:0;color:#006600;font-size:1.1em;font-weight:bold;}

.config_source code{font-size:.8em;color:#000000;}

pre{margin:0;font-size:1.4em;word-wrap:break-word;}

ul,ol{margin:10px 0 10px 40px;}

ul.first,ol.first{margin-top:5px;}

fieldset{padding:0 15px 10px 15px;}

.summary-container fieldset{padding-bottom:5px;margin-top:4px;}

legend.no-expand-all{padding:2px 15px 4px 10px;margin:0 0 0 -12px;}

legend{color:#333333;padding:4px 15px 4px 10px;margin:4px 0 8px -12px;_margin-top:0px;

border-top:1px solid #EDEDED;border-left:1px solid #EDEDED;border-right:1px solid #969696;

border-bottom:1px solid #969696;background:#E7ECF0;font-weight:bold;font-size:1em;}

a:link,a:visited{color:#007EFF;font-weight:bold;}

a:hover{text-decoration:none;}

h1{font-size:2.4em;margin:0;color:#FFF;}

h2{font-size:1.7em;margin:0;color:#CC0000;}

h3{font-size:1.4em;margin:10px 0 0 0;color:#CC0000;}

h4{font-size:1.2em;margin:10px 0 5px 0;

}#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS",Verdana,sans-serif;

color:#FFF;background-color:#5C87B2;

}#content{margin:0 0 0 2%;position:relative;}

.summary-container,.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}

.config_source{background:#fff5c4;}

.content-container p{margin:0 0 10px 0;

}#details-left{width:35%;float:left;margin-right:2%;

}#details-right{width:63%;float:left;overflow:hidden;

}#server_version{width:96%;_height:1px;min-height:1px;margin:0 0 5px 0;padding:11px 2% 8px 2%;color:#FFFFFF;

background-color:#5A7FA5;border-bottom:1px solid #C1CFDD;border-top:1px solid #4A6C8E;font-weight:normal;

font-size:1em;color:#FFF;text-align:right;

}#server_version p{margin:5px 0;}

table{margin:4px 0 4px 0;width:100%;border:none;}

td,th{vertical-align:top;padding:3px 0;text-align:left;font-weight:bold;border:none;}

th{width:30%;text-align:right;padding-right:2%;font-weight:normal;}

thead th{background-color:#ebebeb;width:25%;

}#details-right th{width:20%;}

table tr.alt td,table tr.alt th{background-color:#ebebeb;}

.highlight-code{color:#CC0000;font-weight:bold;font-style:italic;}

.clear{clear:both;}

.preferred{padding:0 5px 2px 5px;font-weight:normal;background:#006633;color:#FFF;font-size:.8em;}

-->

</style>

</head>

<body>

<div id="header"><h1>Server Error</h1></div>

<div id="server_version"><p>Internet Information Services 7.5</p></div>

<div id="content">

<div class="content-container">

<fieldset><legend>Error Summary</legend>

<h2>HTTP Error 500.19 - Internal Server Error</h2>

<h3>The requested page cannot be accessed because the related configuration data for the page is invalid.</h3>

</fieldset>

</div>

<div class="content-container">

<fieldset><legend>Detailed Error Information</legend>

<div id="details-left">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Module</th><td>IIS Web Core</td></tr>

<tr><th>Notification</th><td>BeginRequest</td></tr>

<tr class="alt"><th>Handler</th><td>Not yet determined</td></tr>

<tr><th>Error Code</th><td>0x800700b7</td></tr>

<tr class="alt"><th>Config Error</th><td>There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined

</td></tr>

<tr><th>Config File</th><td>\\?\C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\mbsdkservice\web.config</td></tr>

</table>

</div>

<div id="details-right">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Requested URL</th><td>https://landesk95:443/mbsdkservice/msgsdk.asmx</td></tr>

<tr><th>Physical Path</th><td>C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\mbsdkservice\msgsdk.asmx</td></tr>

<tr class="alt"><th>Logon Method</th><td>Not yet determined</td></tr>

<tr><th>Logon User</th><td>Not yet determined</td></tr>

</table>

<div class="clear"></div>

</div>

</fieldset>

</div>

<div class="config_source content-container">

<fieldset>

<legend>Config Source</legend>

<pre><code> 5: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

<span class="highlight-code"> 6: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/></span>

7: <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

</code></pre>

</fieldset>

</div>

<div class="content-container">

<fieldset><legend>Links and More Information</legend>

This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.

<p><a href="http://go.microsoft.com/fwlink/?LinkID=62293&IIS70Error=500,19,0x800700b7,7601">View more information »</a></p>

</fieldset>

</div>

</div>

</body>

</html>

The same error will also show in the Console.exe.log file

Reason

Opening a Console calls several webservices which are configured by a web.config file. In this file are several .Net Framework sections defined. LANDesk uses mainly .Net Framework 2.0, so sections that aren't defined in the main .Net Framework 2.0 configuration, the machine.config, need to be defined in the web.config.

However, all LANDesk webservices are run in an IIS Application Pool. This pool is configured to run with a specific .Net Framework version. If the application pool is somehow re-configured to use a higher .Net Framework version, it can be that the sections in the web.config are already defined in the main machine.config file for that .Net Framework version, resulting in the config error a duplicate section is defined.

This can be caused by .Net Framework updates or errors in the (un-)install of LANDesk software and updates.

Resolution

Look in the complete error message for the URL and the web.config file that are being logged as containing a duplicate section. In the above error:

<tr><th>Config File</th><td>\\?\C:\Program Files (x86)\LANDesk\ManagementSuite\landesk\mbsdkservice\web.config</td></tr>

</table>

</div>

<div id="details-right">

<table border="0" cellpadding="0" cellspacing="0">

<tr class="alt"><th>Requested URL</th><td>https://landesk95:443/mbsdkservice/msgsdk.asmx</td></tr>

Open the Internet Information Services Manager on your Core Server, and find the specified URL/Webservice (in the example MBSDKSERVICE). Right Click on this the Webservice - Manage Application - Advanced Settings. Note the Application Pool the webservice is running in.

In the same IIS Manager, open the Application Pools, find the pool noted before, righ click on it and open Basic Settings. Change the .Net Framework version to 2.0. Restart the Application Pool.

We've noticed an issue with Landesk 9.5 and the Management Console and the Web Console.  Today, a technician attempted to locate a user in LD and remote to her PC using the Webconsole.  When he located her, ti brought PC 501XXX.  However, she is actually attached to PC 502XXX.    The tech reported this issue, though after the user gave him the Device Name, he found her, to us and I immediately searched her last name in the Management Console.   I found her correct PC name as the only result in my search. 

Why is there a difference in the information that Web and Management Console reports?

The last log file we received was from last Thursday, June 6.  We don't have any filters.  ???

LDDrive.exe is part of “Real-time Inventory and Monitoring”

1.     You could replace the ‘LDDrives.exe’ on the affected client, but copying over the file from one not reporting the issue. LDClient directory

2.     Since we depend on the Visual Studio file ‘msvcr90.dll’ reinstalling Visual C++ via the vcredist_x86.exe or vcredist_x64.exe from the LDClient folder. (this is the 2008 version)

3.     Another option is to turn off the “Real-time” monitoring and redistribute the agent

4. Re-install the agent on this machine.  It could be that during the initial install something corrupted the file.

I want to do a software monitoring report but only for active ( turned on) machines. I need to produce a report of all microsoft products that are installed on active machines only. But I can't seem to figure out how to tell the query within software monitoring or using the query tool on the management console.

Hi,

We have been testing Windows 8 Pro in our Office with Landesk 9.5 and noticed that the remote control is very slow accessing a Windows 8 Machine and I can only see the top left hand corner of the screen as if it's not scalling correctly. Has anyone encountered this issue?

Testing remote control on a Windows 7 Machine doesn't experience these issues

Issue:

Device statuses (offline / online) are not displayed correctly on the core server.

Possible cause:

Mostly, if all devices are affected in the console, the issue is caused by a false proxy server setting on the core server or has a different network related cause.

Steps to troubleshoot:

The general benefit from  following these steps is to be able to investigate each phase of the process, that is done by the LAndesk Console (console.exe *32 process in task manager) when a device is clicked in network view. If the issue is related to a network / proxy / firewall configuration problem, at least some of these steps should fail:

!!!Before testing, please open Task MAnager and check the account, which runs the "console.exe *32" process. Then please open a cmd line and type "whoami".

Please ensure, that the result of the command is the same, that you can see in task manager!!!

Test 1

Please set "Use DNS" in the Landesk Console  to disabled (Configure > Agent status options...) then,

Srtep 1:

Please open the following page from the core - Client IP should be the IP of the test client

"http://ClientIP:9595/allowed/ldping"

If successful, you should see a small XML page with the DeviceID in it

Step 2:

Try to ping the IP address of the test device

Step 3:

Please issue the command: "telnet [IPaddress of the testclient] 9535"

(If the telnet client is not installed on the core, please install it in features. It doe not influence LAndesk in any way)

The command line window should display random characters if successful.

This step checks, if the TCP port 9535 is opened on the client

Test 2

Please unset "Use DNS" in the Landesk Console  to enabled (Configure > Agent status options...) then

Step 1:

Please open the following page from the core - machine-name should be the hostname of the test client

"http://machine-name:9595/allowed/ldping"

If successful, you should see a small XML page with the DeviceID in it.

Proceed with Step 2 + Step 3 according to Test1

If any of the above steps fail, the error message you get should point you to the right direction, where to investigate further.

In my organization we create containers in the NETWORK TREE->DEVICES->PUBLIC DEVICES where we organize our computers according to department, lab, etc.  With LDMS 9.0 I used to be able to click on one of these containers and the console would refresh the status of each machine in the container.  Within a few seconds of clicking on a container I could see which machines were powered on, were remote control ready, had inventory data collected, etc.

Now with 9.5 I click on the same container and nothing happens.  I have to select a machine before its status is displayed.  It is also a much slower process to refresh status than before.

I thought 9.5 was supposed to do a better job with this but it almost seems to be a step backward.  Is this the normal behavior in 9.5 or am I experiencing something out of the normal parameters?

-I am pleased that the active user of the computer is correctly displayed-this is better!

Bonjour,

Nous venons de mettre à jour le serveur Landesk en version V9 SP4.

Nous souhaitons mettre à jour l'installation de la console dans cette même version, car actuelllement nous installons la version de base puis les 3 patch l'un après l'autre.

Pouvez-vous me donner la procédure pour patcher l'installation de la console, ce qui nous permettra de n'avoir qu'un seul setup à exécuter.

D'avance merci.

Cdt

No matter what user I use to access the web console - I am getting no options on the left hand side other than Data Analytics

This includes my LANdesk service account that is a full adminstrative user both inLANDesk and on my domain. I would normally be expecting options for remote control and queries

THis is a new 9.5 installation and we are trying our role based administration. I've read the articles and the manuals - but probs doing something fundementally simple and stupid.

Some clues where to start looking woud be good.

LD9.5

Does anyone know if they are making any changes in 9.5 SP1 to make the console faster responding to device status?

I have set my agent setting in the console every which way and nothing makes a difference. Here is what I've noticed.

1. Whether I set it to all visible items DNS or not or selected items Dns or not  I see at the bottom of the console it pinging devices  not in my visible screen or the one I have selected. As you scroll down the list of devices things get worse which makes sense if its trying to ping every computer in my database.

2. Sometimes I get the red circle but when I click on the device the circle goes away so I can't get some of the options, wake on lan/wan etc.

3.It seems to be slower on my core console.

4. If you do a query I notice at the bottom of the console, so many devices selected so it must be trying to ping every device since it thinks they are all selected even though I can't veiw them all at once and have not selected any on the screen.

Where are the instructions or best known methods doc for installing the Web and/or stand alone console for LDMS 9.5

Why is this information NOT included in the LDMS 9.5 user guide

Currently running Version 9.0 SP4

We are seeing sudden extreme latency in the console, especially in the patch manager.  We have database deadlock errors in the WSVulnerabilityCore.log and when we look at deadlocks in the database, we see anywhere between 3k and 27k (depending on the number of worker processes we run in IIS).  When we run vulscan, it either times out or it does the scan and then reports that it can’t send the data to the core.  The deadlocks are in CVDetected, CVResults and the Vulnerability table.  We also see general console slowness in most phases.  Remote control can't authenticate, reports timeout for deadlocks, and even clicking on "All Devices" within the console will occasionaly time out.

Through all of this, we don’t see any elevated CPU usage on either the core or the db servers.  In fact, they are mostly flat, keeping under 10% utilization.  The core server and database server should be overkill for the load on it.  There are currently 14.5K clients on it.  Core server has 32GBs of RAM on the same switch as the Database server with 52GBs of dedicated RAM for the SQL instance.

As soon as we stop the LDAppVulnerability app pool, the deadlocks in the db disappear and performance in the console returns to normal. 

We have played with the number of worker processes for the Vulnerability app pool increasing and decreasing (3 is normal for us).  We have slimmed down the amount of vulnerabilities to scan for as much as possible.  We were orginally running Version 9.0 SP3 but are now on SP4 with the clients upgraded to that.  We have reindexed the DB and core DB util.  No apparent network/firewall changes.

This appears to be a load vs. IIS issue as functionality is better after business hours when all the clients are asleep.  Anybody seen anything like this or have suggestions?

Description:

After renaming the core server machine, the local LDMS Console fails to initialize reporting the following pop-up window error:

The error reported in the log is the following:

Exception Details: </b>System.ArgumentNullException: Error calling ParseLocalConnectionString<br>Parameter name: local_connection_string<br><br>

In this scenario, opening  the "LANDesk configure services" from Start > All Programs > LANDesk > LANDesk Configure Services fails to start, reporting a pop up window error.

Where W2008R2SP1ENG is the previous machine name, and W2008R2SP1NEW is the new one.

1. Locate the previous machine name lingering in the LANDesk registry keys

- Open the registry editor

- Find the previous machine version

- Replace it with the current one

In this case, the following three keys have been updated:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite]

"CoreServer"="previous machine name"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\LDWM\DBUtil]

"Inventory Server Name"="previous machine name"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\LANDesk\ManagementSuite\Setup]

"CoreServer"="W2008R2SP1ENG"

Environment:

LANDesk Management Suite 9.50.0.530, Windows Server 2008R2 SP1 Standard Edition

We are running Landesk Management suite9. SP4 is installed on the core server.

My console also has SP 4 patch installed.

This started last week after i rebooted my PC, prior to that everything worked just fine for years.

When I launch my console it will authenticate and then give me this message

" the core server you are connecting to does not appear to have a valid license. "

Now this only happens on my system, we have about 10 other people in the office and it works fine for them on their computers. I can log on their PC and use LANDesk. On my PC it will always give me the message above no matter who logs on.

I tried cctivating the core server, that all works fine. And uninstalling and reinstalling console on my PC several times.

I'm running Windows 8 pro 64bit, just like everyone else in my office.