Question on Landesk ESA Web Access Log

May 28, 2018, 12:58 am

≫ Next: Publish URL link to desktop

≪ Previous: Some dashboard charts not generating 'Chart-generated queries'

$

0

0

We were experiencing difficulties in getting Web Access Log by the Landesk Endpoint Management ESA (Endpoint Security Audit).

The situations were the foillowing

- LDMS 2017.3 Management Suite (45 day trial license)

- ESA 4.1.0.0

- to manage Windows 7 PC's

- configured to get Web Access Log for http://www.pchome.com.tw

- as re-install both the LDMS and ESA agent, then reboot the PC's

- there was still no any Web Access Log found while the application log already showed using Chrome to get PCHOME website...

Any comments/suggestions on

- how to configure

- any possibilities to get Web Access Log for both HTTP and/or HTTPS options

Thanks.

---

Publish URL link to desktop

June 12, 2018, 5:56 am

≫ Next: Query contents of a config file

≪ Previous: Question on Landesk ESA Web Access Log

$

0

0

Hi

 

Is there any reason why "category" needs to be specified when creating a package for a desktop link? We don't have a need or want to use categories and can't see why it should be a pre-requisite. If you try and save the URL package it does not let you save because of it.

 

Regards

B

Query contents of a config file

June 12, 2018, 10:33 am

≫ Next: prompt for hostname in provisioning

≪ Previous: Publish URL link to desktop

$

0

0

We are starting to setup a rollout of an upgraded version of a piece of software (Hyland Onbase).  We have several different pushes, where the only difference is a couple of lines in the config file for the program, and determines certain policies, and the server cluster to connect to (different departments have different clusters). I figured out how to add the .config file to inventory, but was wondering if there is any way that a query can be written to look for specific information inside the config file?  I don't see any way to do it.

prompt for hostname in provisioning

June 13, 2018, 7:19 am

≫ Next: Kaspersky/LD AV not installing on Windows 10 clients

≪ Previous: Query contents of a config file

$

0

0

Hi,

there is a way for show a prompt and insert the hostname until osd ?

 

thx

Kaspersky/LD AV not installing on Windows 10 clients

June 14, 2018, 6:43 am

≫ Next: Question about Vulscan and (possibly) an issue

≪ Previous: prompt for hostname in provisioning

$

0

0

All of a sudden, Kaspersky/LANDesk AV will not install correctly on Windows 10 clients (Build 1709) as part of the agent installation. The symptoms are that it installs leaving the Kaspersky entry in Add/Remove programs; after a reboot, the 'K' icon in the system tray is grey rather than red, and it states that it is not activated. This is on a 2016.3 SU6 core.

 

Other symptoms:

 

The icon for the tool-tip it shows the version as 'Kaspersky Endpoint Security 10 for Windows 10.2.4.674' whereas on a Windows 7 PC it is shown as 'Kaspersky Endpoint Security 10 for Windows 10.2.5.3201 (mr3)'

After a first reboot, Vulscan tries to remove it and re-install and then re-brand, but fails several times (according to the logs)

 

I have also tried:

 

i. Setting the agent to download rather than install the AV files

ii. Installing the agent without AntiVirus, then using a Install/Update Security Components to install AntiVirus afterwards

 

This was working last week, and we have made no changes that I am aware of to our Core server. Please help!

Question about Vulscan and (possibly) an issue

May 23, 2018, 12:32 am

≫ Next: EPM Sample Reports

≪ Previous: Kaspersky/LD AV not installing on Windows 10 clients

$

0

0

Hello everyone,

 

I've got a question about the function of the Vulscan. Maybe we've got a problem here or not, who knows...

 

 

Our agent is configured that Vulscan runs on our servers every day at 9pm. Random delay up to 1 hour and at least 15 minutes.

And here is my first question: The 9pm time is not shown on the schedule overview, is that an issue (see picture)? In another agent

configuration (for our clients) the time is shown in the overview.

 

I found several Vulscan logs on our servers, but none from 9pm. For example there is a log from about 00:00 of 60kb and another from 05:50pm with 8mb

for 23rd of Mai. The times are different on other servers.

 

When I watch in the inventory and the scheduled tasks there are two Vulscan tasks. (5) started at 05:21am and (9) started at 17:00pm with command line /continue.

 

Can someone explain me if this is an issue or the function of Vulscan?

 

Thank you very much.

EPM Sample Reports

June 15, 2018, 11:55 am

≫ Next: Question on Inventory Results

≪ Previous: Question about Vulscan and (possibly) an issue

$

0

0

We are new to EPM and was hoping to get some input of some standard reports used by the community.  We are also using Xtraction, so between the 2 we want to start a good library of reports.

 

Any and all guidance would be greatly appreciated.

Question on Inventory Results

June 18, 2018, 7:51 am

≫ Next: Pxe representative configuration - HELP

≪ Previous: EPM Sample Reports

$

0

0

We are in the middle of testing in-place upgrades to our public computer labs from W10 1607 to W10 1803 via WSUS and ran into an issue with inventory results.  We set up an upgrade overnight in one of the labs and when we looked at the results in Ivanti it showed that 5 out of 19 machines had upgraded.  I remoted into one of the machines that reported as still being on 1607 and saw that it had in fact upgraded to 1803.  I then looked at the query results and saw that the machines still reporting as 1607 had a Last Updated by Inventory Server timestamp of 4:30AM, which was around the last reboot I had set up.  I highlighted all the machines reporting as 1607 and did a Full Sync Scan on them.  They still reported as 1607, including the one I knew was 1803.  I then remoted back into the machine reporting as 1607 but had upgraded and ran the inventory scanner from that end (C:\Program Files(x86)\LANDesk\LDClient\LDISCN32.exe) and the machine still reported to the console as 1607.

 

I finally rebooted all the machines reporting 1607 and after the reboot the Last Updated by Inventory Server timestamp changed to the current time and they all reported correctly that they were on 1803.

 

Am I doing something wrong?  Am I expecting results I shouldn't?   Shouldn't a Full Sync Scan (or an LDISCAN32.exe) have updated the server as to the OS version installed on the machine?  My understanding from previous versions was that a Full Sync scan would update the server.

Why did it take a reboot for them to report correctly?

 

Thanks for any help/insight

 

Rick Heckbert

 

Ivanti 2018.1

---

Pxe representative configuration - HELP

May 31, 2018, 3:09 am

≫ Next: How to set up Wake on LAN (WoL)/Wake on WAN

≪ Previous: Question on Inventory Results

$

0

0

Hello,

 

i'm new about Landesk Management Suite 2017 and i would like some help about the pxe configuration.

 

 

Before i worked with Sccm and the pxe was pretty easy for me. The question is:

 

 

i would like capture and then deploy win 10 image. Which are the instruction's, step by steps, for the pxe configurations?

 

 

Your help is really appreceted.

 

 

many many thanks

 

 

Stefano

How to set up Wake on LAN (WoL)/Wake on WAN

January 8, 2014, 8:21 am

≫ Next: 2018.1 Beta Patch

≪ Previous: Pxe representative configuration - HELP

$

0

0

Please confirm the following:

 

Port UDP 0: Opened on your network devices

WOL in the client BIOS: Enable

Device Agent has WoL enabled

 

And please also review the following articles on our community:

 

Understanding Wake On LAN

Understanding Wake On LAN

 

Troubleshooting WOL (Wake on LAN)

http://community.ivanti.com/support/docs/DOC-2090

 

Please also see the following information surrounding Wake on WAN which I think would apply more so in your circumstance.

 

This document discusses how it works and what needs to be done to set it up. Please review this documentation and test its functionality in your environment, and let me know if you run into any issues and where they occur. You may want to attach screenshots of errors or items that may be helpful to diagnose the issue.

 

Here is a basic checklist of what needs to be enabled for this to work:

1. WOL needs to be enabled in the BIOS
2. WOL needs to be enabled on the NIC
3. WOL needs to be enabled in the devices network settings
4. Routers and switches need to be configured to pass WOL packets between subnets (by default this is generally blocked)

 

As discussed in the aforementioned community document the associated traffic travels on port 0 by default. This can be changed via the following steps from the Ivanti Endpoint Manager Console on the core server:

 

1. Configure
2. Services
3. Scheduler [tab]
4. Wake On LAN settings
5. Change port

 

If configuring your network to accept this traffic is not an option, then at least one workstation must be available and running the Ivanti EPM Agent with the Targeted Multicast feature. In order for this to work, all the time, this device must be available or dedicated to this task.

 

Another thing to keep in mind as well is that in order to configure and use the Targeted Multicast feature on a machine to use WOL/WOW the following basic need has to be met:

 

Each subnet needs at least one Multicast Domain Representative. WOL/WOW will not work across subnets without these. Not only do they need to be on each subnet but they need to be online so they can receive these requests form the core.

 

To configure a Multicast Domain Representative, you can follow the simple instructions found using the link below from our Ivanti Help Center:

 

Ivanti Help Center

Configure Targeted Multicast

http://help.ivanti.com/Topic/Index/ENU/LDMS/9.5/Content/Windows/swd_t_configure_multicast.htm

2018.1 Beta Patch

June 4, 2018, 3:14 pm

≫ Next: Scheduled tasks hang until Core server is rebooted

≪ Previous: How to set up Wake on LAN (WoL)/Wake on WAN

$

0

0

So is anyone else wondering why those of us in the Beta test program have yet to receive the Patch to be on 2018.1 full release 2 weeks after it became available to the public? Do the engineers just not care? I mean UEM is pretty much a useless 200K dollar software at this point. Not much of our stuff is working right. All i get when asking about the patch is soon. well soon means a few days not a few weeks.

Scheduled tasks hang until Core server is rebooted

June 19, 2018, 7:08 am

≫ Next: Has anyone successfully pxe booted a dell latitude 7290?

≪ Previous: 2018.1 Beta Patch

$

0

0

Hello,

a customer of mine has an Ivanti 2017 Management Suite installed and they are testing some software distribution tasks.

They told me that every morning they find the scheduled tasks with the Pending icon still, so they reboot the Core server and everything seems to work correctly.

Unfortunately I don't have many informations about the real issue because I'm just reporting what he told me, but I'd like to know if there is something to look at before doing a proper troubleshooting, maybe something about refresh.

 

thanks in advance.

Has anyone successfully pxe booted a dell latitude 7290?

June 19, 2018, 9:20 am

≫ Next: Schedule Time Creep Issue

≪ Previous: Scheduled tasks hang until Core server is rebooted

$

0

0

We are using Management Suite 2016 service pack 6

 

We can get the wim loaded in both uefi mode or in legacy mode.  However, i can't get wpeinit to run due to there being no network driver loaded.  i have run drvload to load several different network drivers when i found the correct one that loaded i'm adding the x32 driver to the x32 wim and the x64 driver to the x64 wim.  the driver does work in both when using drvload but it does not work when adding it to the wim.  The weird thing is if i run drvload to the installeddrivers folder i can get network to work.  I've added the drivers using dism manually.  The driver i'm using is for the correct version of winpe.  However, i have tried previous versions of the driver which do work when using drvload.  Does anyone know what driver to use?

Schedule Time Creep Issue

May 31, 2018, 9:50 am

≫ Next: Inventory scan

≪ Previous: Has anyone successfully pxe booted a dell latitude 7290?

$

0

0

One thing we have noticed is that when you schedule a recurring task, the time scheduled creeps. For example if i schedule a task at 7AM and repeat every day, it will run the task and then reschedule 1 day from completion of the task not from the initial scheduled time. So if the task takes 30 minutes to run then the next scheduled time to run is at 7:30AM the next day. Well this is an issue because these reoccurring tasks we schedule are designed to be ran outside of regular business hours. With the time creep it will then begin running during production hours, thus impacting the users during peak hours. This should not be the way it is. The time should always be the time from the scheduled time, not the end time. That makes 0 sense. This also impacts running stuff in a maintenance window. Someone else has to have this issue too? Please fix this. seattleman1969

Inventory scan

June 19, 2018, 12:31 pm

≫ Next: PXE Service on Preferred Server does not start successfully

≪ Previous: Schedule Time Creep Issue

$

0

0

After I deploy the agent to a device , I have to do an initial manual scan off the device to get all the properties to show in the management console. Is there a way to do an initial inventory scan from the console without doing it from the device? The inventory scan function is not available for the device until the manual scan is done from the device. I am using the Management Console version 11.0.0.164. Please help. Thanks

---

PXE Service on Preferred Server does not start successfully

June 20, 2018, 2:52 am

≫ Next: Inventory scan failed : the system cannot find the file specified

≪ Previous: Inventory scan

$

0

0

Hello,

 

I'm new to the EPM solution, so perhaps am not complete familiar with the all the 'correct' terms.   We are running 2017.3 Update 4 (Version 10.1.30.401)

 

Our Preferred Servers are configured to support PXE booting.   On one of the Preferred Servers the "LANDesk(R) PXE Service" does not start successfully.    Each time the service starts it fails as an application error, shown the event log as:

 

Faulting application name: pxesvc.exe, version: 10.1.30.401, time stamp: 0x59a014a7

Faulting module name: ntdll.dll, version: 10.0.14393.2312, time stamp: 0x5b1a0c4d

Exception code: 0xc0000005

Fault offset: 0x00046bb1

Faulting process ID: 0x114c

Faulting application start time: 0x01d4087b6a0bf4ec

Faulting application path: C:\Program Files (x86)\LANDesk\PXE\System\pxesvc.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report ID: 31a2e217-2faf-46b1-862a-55311fc3cf43

Faulting package full name:

Faulting package-relative application ID:

 

This repeats every 1 minute, with the service is started again (I assume some watchdog component of the EPM Agent) and the application failing.

 

I have completely uninstalled the Agent using the "uninstallwinclient.exe /forceclean /showui /noreboot" option - and the manually rebooted, cleaned up and left over LANDesk folders from C:\Program Files (x86) and C:\ProgramData.  After this I have redeployed the Agent - but this does not help .

 

Nothing I've done has helped me to resolve this issue.

 

I wonder if anyone has any suggestions, or is experiencing a similar issue please?.

 

Thank you

 

Iain.

Inventory scan failed : the system cannot find the file specified

June 20, 2018, 2:27 am

≫ Next: Can I remove the CBA_Anonymous account?

≪ Previous: PXE Service on Preferred Server does not start successfully

$

0

0

Hello,

 

We're having a bit of a problem here; We're trying to run an inventory scan for clients' information where we only have name and ip address.

 

The problem is we always have this same error in the console : "the system cannot find the file specified". We already checked this documentation, changed the path and made sure the file in use was present in the client's folder.

 

When we checked the log (on the client side) related to the inventory scan, we're having this error :

 

Thu May 31 12:04:42 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Thu May 31 13:29:49 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Mon Jun 11 21:57:43 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Mon Jun 11 21:58:13 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Tue Jun 12 09:02:31 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Wed Jun 13 17:33:22 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Mon Jun 18 09:15:17 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Tue Jun 19 10:06:31 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Tue Jun 19 17:40:05 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

Wed Jun 20 09:15:56 2018: LDISendScanRequest failed to post - Session Error 3:  IOError

 

 

Does anyone have an idea on what it could be ?

 

Thanks in advance.

Can I remove the CBA_Anonymous account?

March 7, 2017, 4:59 pm

≫ Next: prompt for hostname in provisioning

≪ Previous: Inventory scan failed : the system cannot find the file specified

$

0

0

Issue:

A LANDesk administrator is questioning the necessity of the CBA_Anonymous account on client machines and is considering its removal.

 

What is it?

The CBA_Anonymous account is a local guest account created on any Windows computer that has a Landesk Agent. When your LDMS Core needs to communicate with an agent, it calls the CBA_Anonymous local account on the agent computer, to perform an LDPing on the client web service. The LDPing returns the hostname and Landesk inventory ID of the Agent computer as xml. This information is verified to authenticate the client before executing any task.

 

For more information, please click on the following link:

Landesk Agent Authentication using the CBA_Anonymous local guest account

 

Solution:

The removal of CBA_Anonymous has proven to exhibit various errors within various environments and may cause a fault in your services.

 

Please keep in mind that in versions 9.6 SP3 and later, the CBA_Anonymous account is no longer in the guest group, but is defaulted to the user's group. Please verify the version of your LANDesk agents if this is not the case.

 

For those machines 9.6 SP2 or earlier, the only known work around, which is unsupported, is to add CBA_Anonymous to the users group. You will however be required to ensure that the local policy "Deny Logon as Batch Job" does not contain the guests group. It can be found here:

Local Computer Policy>> Computer Configuration>> Windows Settings>> Security Settings>> User Rights Assignment

prompt for hostname in provisioning

June 13, 2018, 7:19 am

≫ Next: Deploy machines to a new domain?

≪ Previous: Can I remove the CBA_Anonymous account?

$

0

0

Hi,

there is a way for show a prompt and insert the hostname until osd ?

 

thx

Deploy machines to a new domain?

June 22, 2018, 6:02 am

≫ Next: Inventory Server error

≪ Previous: prompt for hostname in provisioning

$

0

0

Hi all,

 

We have a core server running in a domain, which images workstations for the same domain and then the install steps join them to the domain, etc. The workstation is then managed from LDMS (EPM) for remote, patch, etc.

 

We're having to implement a new domain as part of a global policy, which is tied to a PC rollout on Win 10.

 

My question is - can I use my existing LDMS server to image, deploy and manage workstations on a different domain? Or will I need to deploy a new management server as a member of that domain first?

 

Thanks!