What is the new URL in order to import hp warranty from Hp portal to LANDesk , before it was configured in the rule "https://h20566.www2.hp.com/portal/site/hpsc/public/wc/home/ " but it is not working anymore.
↧
Hp warranty URL
↧
Problems trying to run powershell command "Import-StartLayout" from Endpoint Manager task
I'm working on getting our Windows 10 image ready for provisioning. Per documentation around the Internet you generate an xml file and run the Import-StartLayout command to import it. Whenever I try to run it via a provisioning task I get the following error:
The term 'Import-StartLayout' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
If I run this manually as myself or as Local System from a powershell prompt it works fine. But when it runs through any Endpoint Manager task it fails with this error. I found someone having a similar issue here Run powershell and DISM in OS provisioning but when I try the steps listed here I can't get past this error. I've tried running the command directly as a provisioning task, creating a distribution package as a powershell or batch script, and running the task as Local System, a domain admin user, or the currently logged in user. I've also tried adding the Import-Module StartLayout listed in the bottom comment and that also doesn't work. I'm at a loss at this point on what to do there. Is there something about running Powershell scripts via Endpoint Manager here that I am missing? I've tried this on Windows 10 1703 and 1709 and both do this. We are running Endpoint Manager 2016.3.
↧
↧
Ivanti Endpoint Management in the cloud?
Any idea on Ivanti Endpoint Management in the cloud, if it's already release and available? As per Rex McMillan, Principal Product Manager, the one who discussed the New in Ivanti Endpoint Manager 2017.1 (formerly LANDESK Management Suite) last June 2017 on demand webinar that the Endpoint Management is now available on cloud and it's hosted in AWS and will be release soon for the people who like a hosted vs. on premise solution. I need to know if it is already release and available for trial? Thanks.
↧
ServiceNow Integration with EPM
Hello everyone, we have recently implemented IEM in our environment and would like to integrate it with our ServiceNow platform for asset management. Has anyone attempted integrating their serviceNow environment to get asset information from LDMS/EPM ?
Thank you
↧
Can I update Landesk Agents to version 9.6?
I have 9.5 core version.
↧
↧
LANDesk 2017.1.1 SWD: batch installation package don't show GUI application
Hello at all,
at the office we use
LANDesk Management Suite 2017.1.1
I created a batch, where is opening a application GUI with additional information for the logged on end user:
START User_Wait_Message_x64.exe
and tested by using psexec in system user context, it worked fine.
This batch is as a batch installation package at LANDesk inbounded.
At deployment I recognized that the applications is started and shown in process manager, but the GUI will not shown by loggod on user.
How can show the user the GUI of this application during package installation?
P.S.: the only alternative way I now try is during package installation to create a scheduled task and start the task,
Thanks a lot for feedback
kind regards
Tralveller
↧
How do I make the remote control cursor visible?
We are running LDMS 2016.3. We have deployed the Landesk agent to all our workstations and servers. The Remote Control tool works well, except for the fact that I can't see the cursor on the remote screen. If the user starts moving their mouse around, I can't see it. I can't imagine that a remote control tool would not let you see the remote cursor, so I must be doing something wrong here. Suggestions?
↧
Need to create a role that can only see inventory, what permissions do i need to set?
I need to create a role where the users can only see the inventory, run queries and reports. I looked through the default roles and they all seem to have more than what's requested or not enough.
Using Landesk Management Suite 2016
↧
Ivanti Endpoint Agent Update kills Commvault backups
Hello,
Last weekend, I pushed out an agent update from 2016.3 to 2017.3. In the process, the agent broke C++ 2013 on our core Commvault backup servers. This required a repair installation of C++ 2013. It didn't cause a lot of issues because it was caught quickly. Similarly, the Commvault agent on our Exchange server was failing to take backups. The reason ended up being the same. A repair installation of C++ also fixed this. Since we have already found the solution, I don't need a response to this. However, it would be great if this could be passed along to developers to work out any compatibility issues between the Landesk/Ivanti agent and the Commvault agent.
Just for reference, the error that displays when the backups fail or when the services fail to start is "The program can't start because mfc120u.dll is missing from your computer. Try reinstalling the program to fix the problem."
If I can provide any more information, please let me know.
Thanks,
Justus
↧
↧
Health dashboard confirming/deleting alert
Hello
Im new in managing our Landesk in our company and I'm really newby in this. I whould need help with Acnowledge alert. I'm trying to confirm these errors, because I know I already fix them, but Im unable to do so, because button is for not possible to use. Im attaching screenshot, what could give you more info. Also, when Im raising this question, is possible to basically delete all these logs to start logging again ?
Thanks for help !
↧
New Ivanti agent unable to connect to new core
Hi all,
I've got a Landesk 9.6SP2 server that I inherited, and I am bringing a 2017.3 system up in parallel. I cloned the database and installed 2017.3, and now I am to the point where I am running a test system with an agent. I created the new agent after making new definitions in the requisite places (client connectivity, inventory settings, etc) to point to the new server. The agent installs, I can remote it and the system will send inventory data, but the security scan fails in a couple of places. It fails on "Checking for updated settings" with "Failed: No response from core" and "Checking for updates on core XXXX", then in "Parsing Information" it says "Failed: Cannot interpret data". Looking at the vulscan log, I have two errors: "Self-update failure: Core did not return requested file hashes" and "ERROR: Unable to get contents of file: "C:\programdata\vulscan\ReplicationBehavior_Replicator_11577.xml"
I do not find that file in the vulscan directory and I don't know what process would create it, but I do find a lot of references to the old core, so I removed all the agents and definitions that imported from the old database and made a new agent from the default settings that pointed to the new definitions I created earlier. I still have many references to the old server in the vulscan direcctory, but I don't know where they are coming from, or if they are even the problem. Any pointers would be greatly appreciated. Thanks.
↧
Remote Control to workstations
Hello, we have a set of workstations at a remote location that we are unable to remote control. The workstation comes back with up to date Hardware scans in the management console, but the option to remote is unavailable. It is not showing that they are not available to be connected to (crossed circle). Two laptops at this location are still accessible though. Devices had a different Agent configuration than our other workstations, and were able to use the html remote, but still they did not show they were able to be remoted to. After updating the agent configuration on a few machines, the option to html control is now gone (as it is suppose to be with this config) but are still not showing as a remotable device.
Currently running Magagement Suite 2016 version 10.0.0.271
Thanks
↧
servers targeted with ldap query
Is there any way to prevent servers from getting targeted in scheduled tasks via a ldap query? Cant find anything on this and it's becoming an issue. Software is getting deployed to servers because we have users targeted and they are logging in on servers. ie/ computer support staff and this also affects citrix servers.
Any advice? currently LANDesk version 2016 sp3
Thanks
Val
↧
↧
Migrate database from 9.6 to 2017.3
Does anyone know if it is possible to migrate/import a database from LANDesk 9.6 SP2 to 2017.3? I've got my new core up and running on its own database, but it has taken me so long to do that, there are a myriad of things out of sync. There are only two choices that I can see: either I go through by hand and make all the changes from one core to the other, or I can have the DBA restore a snapshot of the current database and reinstall LANDesk which will do the upgrade for me. I am really hoping I can avoid the pain of either option.
↧
Options: Computer Management, Event Viewer, Local User and Groups, Ping, Terminal Services Remote Control, Terminal Services Remote Control Console and Tracert in the Ivanti's Endpoint Manager version 2017.3 are located under Computer Management.
Options: Computer Management, Event Viewer, Local User and Groups, Ping, Terminal Services Remote Control, Terminal Services Remote Control Console and Tracert in the Ivanti's Endpoint Manager version 2017.3 are located under Computer Management.
↧
Portal Manager long term support?
Our institution is getting ready to implement either Landesk Workspace or Portal Manager to allow end users to install pre-approved software packages. We are currently on 9.6 and might consider moving to LD2016 in the near future. We are leaning more towards using Portal Manager because the default interface lists the available software package (easiest for users, little navigation, everything is right there). My question is, what is the long term support for Portal Manager? Will it be phased out in favor of Workspace at some point? I don't want to get our users used to Portal Manager, then have to switch to something that looks different to them later. But if it going to be phased out in favor of Workspace then I'd rather get our users accustomed to navigating the application. If Portal Manager is going to stay for the long term then we would rather stick with that.
Thank you for any advice.
↧
Landesk EPS - LDAV Kaspersky and Windows 10 Fall update 1709
Landesk EPS - LDAV Kaspersky and Windows 10 Fall update 1709.
We are finding that LDAV KAV is not compatible with Windows 10's Fall update (1709).
All clients upgraded to the Fall update have the LDAV/KAV crashing or consuming multiple cores for no apparent reason. It also marks all LDAV clients as "invalid keys or not activated" and when you look the logs, there are literally millions of entries with the same text:
ERROR: Failed to delete Kaspersky Endpoint Security 10 Service Pack 1 Maintenance Release 3
We also tried building Windows 10 1709s from scratch and the behavior is the same.
- C:\Program Data\LANDesk\Log creating new, 2MB ldav_install.X.log files at the rate of at least 8 per minute, rolling over after 8 (for a total of 8), each containing tens of thousands of repetitions of:
- Mon, 06 Nov 2017 08:26:55 ERROR: Failed to delete Kaspersky Endpoint Security 10 Service Pack 1 Maintenance Release 3
- This is the only line in the file
- C:\Program Data\LANDesk\Log creating new, 10MB ldav_update.X.log files at the rate of at least 8 per minute, rolling over after 8 (for a total of 8), each containing nearly a hundred thousand repetitions of:
- Mon, 06 Nov 2017 08:32:26 ERROR: Failed to delete Kaspersky Endpoint Security 10 Service Pack 1 Maintenance Release 3
- This is the only line in the file
Anybody else having this problem?
Is this another bug?
Thanks in advance.
Logs Attached
Message was edited by: Aaron Day
↧
↧
Best practises for creating an IEM UAT test environment?
Hi there,
I'd like to update our IEM core from 2017.1SU1 to 2017.3 (in order to hopefully resolve a BSOD bug that's popping up on some machines who's agent has been updated from 9.6sp3 -> 2017.1SU1).
However, before I do this on the production core I'd like to test the update in a lab environment.
I have updated a test core now to 2017.3, I've rebuilt the agents and created a self contained exe agent and have installed this on a test workstation (hoping to install on another 3-4 for testing the BSOD doesn't occur).
As the UAT core contains a backup of the live database I've disabled the scheduler service so no tasks are run on production devices.
Question is, is there a recommended series of tests you can run through to verify most systems are functional, without affecting live devices? Does anyone else have a UAT testing procedure they use before updating IEM on their production core?
I can run tests such as software distribution to the handful of devices with the UAT agent, but I would have to enable the scheduler service for this wouldn't I....and that may potentially mean old tasks start running against devices, unless I clear every one out first perhaps.
↧
Is auditing still available in EPM 2017.3?
I'm building an EPM 2017.3 environment from scratch that we will migrate our LDMS 2016.3 clients to early next year.
The auditing module appears to be missing. Has it been moved or is it gone from this version?
↧
Inventory Scanner Bug in 2017.3
Just a heads up, I have noticed the inventory scanner is no longer processing .MINI files after upgrading to 2017.3 (including 2017.3_SU1). You will need to rename the .MINI files to .MINISCN for them to be processed. Pretty big oversight I think, and hopefully it gets patched soon.
My endpoint clients are still 2016.3, and I am assuming that 2017.x sends the new extensions. We will eventually begin rolling out the new agents system-wide, we just have a bigger change control process to follow, so it takes time. Until then, 'ren *.MINI *.MINISCN' is invaluable. I'll be reporting it as a bug as well.
~Kevin Brooks
↧