Quantcast
Channel: Ivanti User Community : All Content - Data Analytics
Viewing all 359 articles
Browse latest View live

Basic guide to configure and troubleshoot LANDesk Data Analytics Discovery Services Remote Agents

$
0
0

This article will try to describe the most common problems and their possible causes, that could occur when using Discovery Services Remote Agents.

This article is not intended to be a complete guide and does not include all options available, that can be configured in Discovery Services Remote Agent (in the rest of this document referred as Remote Scanner)

 

For a complete description of Remote Scanners, please visit the following website:

http://help.landesk.com/Topic/Index/ENU/LDDA/9.5/Content/DA/ldda_t_discovery_services.htm

 

Before starting your troubleshooting, always make sure, that you have the latest version of LDDA.

The most up-to-date LDDA version can be downloaded in the following document:

"LANDesk Data Analytics 9.51 Sustaining Patch Information"

New LANDesk Data Analytics 9.51 Sustaining Patch Information

 

General Information

 

A remote scanner is a device, which has a "LANDesk Data Analytics Discovery Services Remote Agent"  and a Landesk Agent installed on it.

The purpose of it is to run the same scans as Discovery Services on the core server is capable of, but independently from the core server.

The remote scanner receives its configuration from the core server and then executes the scans in every 24 hour - by default.

The logfiles of the remote scanner can be found by default in "C:\Users\administrator>"C:\Program Files (x86)\LANDesk\Data Analytics\Discovery Services\"

 

Installation of the remote scanner:

Please ALWAYS use the pre-configured scheduled task in the Landesk Console, if you whish to install a remote scanner, Simply drag and drop the target device to the task and start it.

RS1.PNG

 

Configuring the remote scanner

This can be done on the core server in LDDA > Discovery services > Configurations. You can specify in each configuration, if the given configuration should be available for one or more remote scanners. If you select a device in the below dialog, it will automatically download the configuration and scan according to its settings (in the example only 1 remote scanner is selected with the hostname "W7SP1x64") as it starts its next reular scan.

RS1.PNG

There are also 2 command line switches, that can be used for starting a remote scan IN ADDITION to the regular scans.

 

The "/NOSERVICE" switch

Starts an immediate scan using all available configurations for the given device and also refreshes the available configurations from the core server.

 

Example:

"C:\Users\administrator>"C:\Program Files (x86)\LANDesk\Data Analytics\Discovery Services\ManagedPlanet.DiscoveryServices.RemoteScanner.exe" /NOSERVICE"

 

The "/CONFIG" switch - only available from LDDA Patch 47 and above

Starts an immediate scan using the specified configurations in the command - in the below example ONLY the configuration "153 wmi" will be used during the scan

 

Example:

"C:\Users\administrator>"C:\Program Files (x86)\LANDesk\Data Analytics\Discovery Services\ManagedPlanet.DiscoveryServices.RemoteScanner.exe" /CONFIG="153 wmi" /NOSERVICE

 


Most common issues

 

After installing an LDDA patch on the core server the remote scanners cannot be updated - The scheduled task to deploy the new remote scanner fails with "Failed to download all additional files"

You might need to reset the hash of the remote scanner distribution package before you can install the updated version of the scanner. This can be done in Landesk Console > Tools > Distribution > Distribution Packages > Public Packages > Data Analytics.

ds.jpg

 

After installing an LDDA patch on the core server the remote scanners cannot be updated - The scheduled task to deploy the remote scanner fails with error core 1603

You might need to uninstall the old version before you can push the new remote scanner version to the target device. T

 

After deploying a remote scanner it does not appear in Discovery Services  in the Landesk Console

Alone the installation will not start a remote scan. Please run the remote scanner with the "/NOSERVICE" switch and wait some minutes. After this the scanner should be available in the Discovery Services Configurations.

 

If this does not happen,

 

Please try to open the following link from on the remote scanner in an Internet Explorer window:

 

http://CORESERVERNAME/DiscoveryServices/DSReceive.asmx

(Please substitute CORESERVERNAME with the hostname of your core server)

 

This should display the following XML website:

RS1.PNG

 

If you receive the an error message instead of the above website, please check the proxy settings of the remote scanner.

 

 

Please refer to the following article for troubleshooting Discovery Services log files.

The logs created by the remote scanner are identical with the ones created on the core server:

 

Basic troubleshooting guide for Landesk Data Analytics - Discovery Services

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

 




Not all SCCM records are importing - Why?

$
0
0

I just performed an SCCM import using DTS.  The SCCM collection (all systems) that is referenced in the rule contains 2910 records but when I did the import it brought in 2766 records.    I culled out the delta units and analyzed them but I don't see any common thread between the records that did not come over in the import.   Are there some exclusion criteria that prevents certain SCCM records from being imported?   Its not the "null" or "non" SCCM clients as some of those imported correctly (but not all). 

Why can't I see the SLM compliance report in teh console when I can see it on the server

$
0
0

All,

 

We are a new LDMS core and LDDA customer

 

We ran the rule to process all software rules and can now launch the the Executive report pack report

"SLM Report With Expandable Detail"  but we cannot see the same report on the Remote Console (service pack 1).   What would be the cause of this issue?

 

Dave

Data Analytics product install fails with an Error 27520. Error opening XML file...

$
0
0

Problem:

Installation of LANDesk Data Analytics at the Core Server or Remote Console may fail with a message similar to this:

Error 27520. Error opening XML file C:\xxxxxx.xml. 1

 

Cause:

This issue can happen when the domain or local user doing the installation does not have local administrator rights or domain admin rights.

 

Solution/ Workaround:

Verify the user installing Data Analytics is a local administrator, a domain administrator, or a member of the domain admins group.

Possible to connect LDMS to LDSD db for reports?

$
0
0

Is it possible to connect an LDMS 9.5 (Not SP1) Core to an LDSD 7.5 database for reports?

Issue with SLM report with expanded details

$
0
0

I am running the SLM report with expanded details under the software compliance section in ERP

 

I have computer groups set up.   Basically it is all the computers and software in each country

 

For the groups I set up a few days ago all of the calcs are processing cleanly. 

 

For the groups I set up just yesterday the report is coming out incorrectly.  In these cases installs = licenses exactly and there are 0 variances for each software title.  This is true even though I have not loaded any licenses for many of the line items that show license coverage for the installs.

 

Is there a process that has to run each night to perform the calcs?   I have run the calculate function in SLM / Administration but that does not resolve the issue.

 

Help

 

Dave

Unable to send executive reports via mail

$
0
0

Hi,

 

We have upgarded to 9.5 sp1 as per suggestions from Landesk to fix scheduling issue but still neither shceduling nor mails are working.

Can you give a pointer where to look for logs. I have checked sendmail.exe.log but it is of no use.

 

Regards

Manish

How to install Data Analytics 9.51 w/ Patch77 on LDMS 9.5 (not SP1)

$
0
0

I’d like to help you avoid the frustrations that I went through in determining the correct license credentials and install sequence for Data Analytics 9.51 for LDMS 9.5 without SP1. For SP1, the installations are still the same but the Activation of LDDA 9.51 in LDMS 9.5 SP1 is integrated into LDMS opposed to needing to activate LDDA 9.51 independently.

 

1 - On your Core or test Core, install LDDataAnalytics.exe, then reboot - http://community.landesk.com/support/docs/DOC-26994 - Under Additional Component Downloads: Data Analytics for 9.5

 

2 - After the reboot, install LDDA.exe, then reboot - http://community.landesk.com/support/docs/DOC-29070 - Under Download Links: LANDesk Data Analytics Update

 

3 - At the Activate Data Analytics Components window, enter your specific Data Analytics license credentials. If you’re still on 9.5 and not SP1, make certain you use your specific DA credentials. Your LDMS Core creds will not work here.

 

4 - If for some reason you need to close out of the activation, you can always go back in via here: \Program Files (x86)\LANDesk\ManagementSuite\ManagedPlanet.Activate.Client.exe In my case, I closed out, installed the Patch77, rebooted, then activated.

 

5 - After the reboot from #3 or the activation from #4, install LDDA951Patch77.exe - http://community.landesk.com/support/docs/DOC-29101 - It’s the attached .zip file to that page (document)


How do I set Computer.Barcode to active?

$
0
0

How do I set Computer.Barcode to active?

Possible to import a List into the properties of a field in a Web Form?

$
0
0

  I am creating a web form in LDDA 9.5 for scanning barcodes of new assets and have a long list of items that I'd like to display in a dropdown for a field.  In the Create a List area under Use a list of values, is it possible to import a list or will I need to type each item individually?

 

Thanks!

Will Standarize/Map Data create columns?

$
0
0

I'm using LDMS 9.5 w/ Data Analytics 9.5 and am wanting to centralize the location of device attributes as shown in Inventory.  For example, the display/monitor details are stored in Computer.Video.Monitors.Monitor and I'd like them to also be stored in Computer.Asset Info  ...  Will I need to create each of the attributes inside Computer.Asset Info then use Map Data to map them directly?

 

Thanks!

Allen

Executive Report Pack - Monitored Tasks

$
0
0

Does any one have any information on how to use this feature? I could not find any further information on it here or in the 9.5 guide. I have my smtp server specified, and my desired task enabled, but no email is sent.

 

monitor_tasks.PNG

 

Thanks

Good ways to use list data in a Web Form?

$
0
0

I'm creating some web forms and one of the fields will be a drop-down that contains a fixed list of values. This is nice and easy because I can choose to 'Create a List' and then add the values to the list in the web form definition.

 

However, I would also like to use this list in a different form without having to type in the information again creating two lists to maintain. This would make me think I should use the 'Link to a table in the database' option. This is where things start go wrong for me.

 

I can't see a simple way of creating and maintaining a list in a table without having to manually create a table in the database (outside of LDDA) and building some way of keeping it up to date via an import rule using another source such as a CSV.

 

In short, is there a standard way of building a table, keeping that up to date, and then referencing it from a web form?

 

A perfect example of this is the 'Map IP Gateways To Locations' web form. This allows me to update the contents of a table and reference this as many times as I like but this table already exists. I'd like the same functionality of list creatin/maintenance but without manual modification of the database as that will be difficult for my customer to maintain long-term.

 

Mark McGinn

MarXtar Ltd/MarXtar Corporation

http://landesk.marxtar.co.uk

LANDesk Expert Solution Provider

 

 

The One-Stop Shop for LANDesk Enhancements

- Wake-On-WAN - Distributed Wake-On-LAN, Scheduled Power Down, and SWDist Sequencing

- State Notifier - Real-Time Device & User State Inventory Updating & Alerting

Update - New Stand-Alone State Notifier Console for Service Desk Operators

Update - State Notifier now detects machine and user Idle states

Update - WoW & State Notifier now integrate for even more functionality

Request: Please add Windows 8 and Server 2012 to OS Normalization

$
0
0

Please add Windows 8 and Server 2012 to Operating System Normalization in DTS.

 

FYI, really appreciate the recent wave of patches coming from DA/MP !

Barcode CSV Import or Data Import

$
0
0

In LDMS 9.5 and LDDA 9.5, I'm needing to import data into LDMS and into its SQL db to then use this data in dropdowns inside my DTS web forms.  What are the differences of or advantages of using the Barcode CSV Import option or the Data Import option for this import?

(see attached pic of the two)

 

Thanks in advance!


Basic troubleshooting guide for Data Analytics - Web import rules

$
0
0

Issue:

Web Forms are not inserting information, or insert the wrong information to the Inventory of the devices.

 

General explanation:

Landesk Data Analytics > Data Translation Services contain several rules, which can populate / create various fields in the inventory of the managed devices. This will focus on the rule DTS > HP\Compaq Warranty > HP\Compaq Warranty as an example.

The purpose of this rule is to gather warranty related information from the Dell website, then insert this information to the inventory of the client under "Comupter" > "Warranties" > "Warranty"

This is not meant to be a complete explanation related to web import rules.

For this please refer to the help site of Landesk Data Analytics:

http://help.landesk.com/Topic/Index/ENU/LDDA/9.5/DTS_Main

 

 

Trouble shooting steps:

 

Step 1

Always check, if you are using the most up-to-date version LDDA. The web import rules are regulary revised and updated according to the changes made on the web sites we gather information from.

You can download the latest LDDA version from the Product Download section of LAndesk Commuinty

http://community.landesk.com/support/community/product_downloads

 

Step 2

Create a copy of the problematic rule by right clicking it and selecting copy, as it could be difficult to restore a rule to its original form after it has been modified.

 

Step 3

Double click the COPY of the rule to start to investigating. The first dialog lets you select where the the collected information should be stored.

If you select "Management Suite" - Computer Data, the information collected will be inserted into the LANDesk Inventory of the devices the rule applies to.

If you select "Asset Control", the information collected will be inserted into the Asset Control module of LDDA, which is practically a separate client database in LDDA. Selecting this option will NOT update the LANDesk Inventory of the devices.

After we have confirmed that the collected information will be saved to the correct database location,  click next.

 

LDDA95-2013-02-28-10-39-14.PNG

 

Step 4

 

In the next dialog, we can set the URL of the website, from which we wish to collect information and configure the how we want to connect to it.

It's good to test if we can access the URL from an Internet Explorer window using the same connection settings. After we have confirmed that the URL can be opened without problems, click next.

 

LDDA95-2013-02-28-10-39-14.PNG

 

Step 5

 

In the next dialog, we will concentrate on 2 fields: "Field Name " and "Attribute"

 

LDDA95-2013-02-28-10-39-14.PNG

 

"Attribute" tells LDDA the Inventory information from the device to use in the web site. In our case it is "Computer" > "System" > "Serial Number", which has the value "5CB2210TG6".

 

LDDA95-2013-02-28-10-39-14.PNG

 

"Field name" indicates the name of the web form field we will use to insert the information that we got from the Inventory of the device.

A first check would be to comfirm in the source code of the page that we are accessing to verify this field name exists.

 

This is an example using Firefox. After clicking Options > Web Developer > Page Sorce, the source code of the page will be displayed.

In our case the source code part that contains the field name, "rows[0].item.serialNumber" will look like:

 

LDDA95-2013-02-28-10-39-14.PNG

 

Most of the problems encountered will be caused by any of the following:

 

Cause 1:

The attribute set up in the web form contains no data or the wrong data

 

Solution 1:

Configure a different attribute that contains the correct information.

To do this, select the line that contain the wrong attribute name, then click edit and select the correct attribute, then click OK

 

Cause 2:

The fields name has been changed on the website since the lastest release of LDDA.

 

Solution 2:

The next LDDA version will reflect the change, but as a temporary workaround you could adjust the rule to the new field name.

A useful tool can be found using Firefox to identify the new field name.

Select Options > Web Developer > Inspect and point to the field you would like to use. It will tell you the name, which can be used in the source code to find the entry you need to enter in LDDA

 

LDDA95-2013-02-28-10-39-14.PNG

 

Step 6

 

After checking the settings in step 5 there is one more item to review where you can specify if dates should be treated in US format or not. If you have problems related to the date format, you might want to disable the option "Treat dates as US format".

 

Remarks:

There are other type of web import rules that connect directly to the API of the given provider. In these cases you will not configure the web site related settings, but the inventory arrtibute part of this guide still applies.

Data Analytics (Managed Planet) Processes Won't Stop

$
0
0

There are times when you need Data Analyitcs to be completely stopped.  Sometimes turning off the services is not enough.  If you have Data Analytics (Managed Planet) processes that won't stop, please do the following:

 

  1. Stop all LANDesk & Managed Planet services.
  2. Turn off "Real Time Processing".
  3. Stop IIS.
  4. On the Core Console stop the Inventory Service in Configure > Services > Inventory
  5. Delete or move all .mp files from \Program Files (x86)\LANDesk\ManagementSuite\ldscan
  6. Delete or move all files from \Program Files (x86)\LANDesk\ManagementSuite\ldscan\ErrorScan
  7. Delete or move all files using the cmd line from \Program Files (x86)\LANDesk\ManagementSuite\MP_TEMP\WEB
  8. Reboot the core or restart the services you stopped to get Data Analytics running again

How to patch manually Data Analytics (Managed Planet)

$
0
0

Core:

  1. Stop all Managed Planet services.
  2. Shutdown the LDMS console.
  3. Copy the managementsuite directory into the \program files (x86)\landesk\managementsuite directory LDMS was installed to.
    • If the copy fails due to open/locked files, please seeDOC-27544.
  4. Copy the ldms directory into the inetpub\wwwroot\landesk\ldms directory the web console was installed to.
  5. Run Database Installation from the LANDesk\Data Analytics program group.  You must run Database Installation before the next step.
  6. You must run Database Installation before this step.  Depending on your version of LDMS 9, copy the appropriate files from the directory that says xxxx Only.

 

IF ANY OF THESE STEPS FAILS TO COMPLETE, STOP!       Open a support ticket.

 

Remote Console:

  1. Copy just the files in the managementsuite directory (not the complete directory structure) to the mangementsuite directory the remote console was installed to.

AJAX network error on install

$
0
0

Data Analytics (Managed Planet) requires AJAX from Microsoft to install.

 

Environment:

Windows Server 2008 and 2008 R2 Standard

Not seen in Windows Server 2003

Errors:

Initial install:

The feature you are trying to use is on a network resource that is unavailable.

Click OK to try again, or enter an alternate path to a folder containing the installation package 'ASPAJAXExtSetup [1].msi' in the box below.

ajax install.png

 

When trying to repair:

A network error occurred while attempting to read from the file location:\ASPAJAXExtSetup [1].msi

ajax reinstall.png

Cause:

When you rename the installer from ASPAJAXExtSetup [1].msi to anything else, it will fail.

 

Resolution:

Rename installer to ASPAJAXExtSetup [1].msi.

Software Store links not working with roaming users between x86 and x64 architecture windows systems

$
0
0

Description

When a user with a roaming profile moves from a x64 to a x86 device, (or vice-versa), the shortcuts from the Software Store still link to the program folder of the other architecture.

Cause

Software Store links only get updated by a call of ssclient.exe.

Solution

For roaming users it is necessary to call ssclient.exe every time they log-on to a system to ensure the links meet the local architecture.

This can be done via a GPO that places a shortcut to ssclient.exe in the start-up folder of the start menu for these roaming users. That way ssclient.exe gets started every time the user logs in and all shortcuts are adjusted to the local architecture.

Viewing all 359 articles
Browse latest View live


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