Hi,

I have a host (s?) that is not updating its last scanned date when I look at All Devices in the Network View.  When I look at Security and Patch Information it shows the correct date (according to the vulscan logs on the host).  Below are the logs and I have also attached a screenshot.  Any ideas?

Thanks

Brad

I have a MAC with LANDesk installed and the logs say its reporting info to my server but when i run a query to find it it is not showing up. Anyone else have the same issue or have a fix or have a way to trouble shoot it as I'm new to the world of LANDesk?

Below is the log from this mornings log in showing that is working

Hello all,

I have been working on creating a provisioning template from scratch for our Windows 10 image and I am so close, but still coming across an issue.

The template images the machine with the wim perfectly, injects the unattend file (the ld default unattend). The only modifications to the unattend are my KMS key and an Auto logon section which logs into the only local user on the image.

Once the machine finishes its oobe loading screen, it auto logs into the local profile. YESSSS!

Then, nothing continues. The ld Provisioning window never pops up to complete the rest of the tasks in the template. The ldprovisiong folder is still in the C drive, rather than being deleted.

Under the ldprovisioning folder, there are two log files, Confighandler.log and ldprovision log. I have attached them to this post for reference.

config handler:

2018-10-23 17:47:50(6604-6600) ConfigHandler.exe:Attempting traditional agent install.

2018-10-23 17:47:50(6604-6600) ConfigHandler.exe:LDLogon Path: \\BHLD1\ldlogon

2018-10-23 17:47:50(6604-6600) ConfigHandler.exe:Mapping drive using preferred server credentials

2018-10-23 17:47:51(6604-6600) ConfigHandler.exe:going to execute \\BHLD1\ldlogon\wscfg32.exe /f /L /NOUI /NOREBOOT /C="Install Agent.ini"

ldprovision ends with:

2018-10-23 17:47:50(804-5048) ldProvision.exe:The file (c:\ldprovisioning\ConfigHandler.sig) was successfully downloaded

2018-10-23 17:47:50(804-5048) ldProvision.exe:Done with download handler.

2018-10-23 17:47:50(804-5048) ldProvision.exe:Launching action handler [ConfigHandler.exe] with parameters ["]

No user logged in, change CurrentTokenWithInteraction to CurrentToken

At this point on my management console, the template history shows a Blue ? icon next to the agent installation task and my script which should occur after that. (pic attached)

On the machine, I mapped and ran  \\BHLD1\ldlogon\wscfg32.exe /f /L /NOUI /NOREBOOT /C="Install Agent.ini" under my Landesk admin domain credentials which started the installation silently, and ran an inventory scan.

The device appears in my management console with the correct name, however It appears as offline.

The provisioning task never completes and I am at a loss for why this is occurring. Any ideas?

Good Afternoon,

I wanted to start a friendly discussion on everyone's experiences with Ivanti 2018.1 so far.  I am wondering if the problems we are having are an issue with an unknown bug (which i highly doubt) or something else on our end.

Currently our problem is random, but templates fail to deploy usually on the Deployment of packages stage of the template.  But a template that takes normally say 2 hours to run, now takes 5 or more hours to run and most of the time fails.  It seems to be completely random (location based).  Our network team states that they see nothing wrong.  We do have an active case open and working with support, but wanted feedback from anyone using 2018.1.

Our other experiences so far are with Network Map:  Even though we are not discovering over WAP but the agent discovered all nodes from our laptop devices from our wireless subnets.  It also discovered users home networks and added them to our network MAP and not sure how we can remove that.  i haven't contacted support about this as our other issue is more important.  For the time being we disabled Network mapping.

Another possible issue is with PXE Booting.  I had PXE booting working in 2017.3 and since upgrading to 2018.1 I seem to not be able to detect a PXE rep on the subnet.  Again becuase of the other issue, I have not looked into this at this time.

Outside of that, everything else seems to be going great.

So that being said, what have your experiences been?

I am currently trying to figure out how to set up a scope so that a limited user can provision a machine in a specific Device Group, but also has the ability to Provision BareMetal Machines.

Any ideas or thoughts behind this?

We are currently on 2018.1 of Ivanti Endpoint Manager so far.

Hi Experts,

the below screen shot if from  SDMCache, Please help me in understanding these files, its a same KB file downloaded twice ??. Whats the difference between -glb or glb_twXXXX.exe

This has been taking a huge amount of disk space . Thank you..

Contents

Discovery

Discovery is the process of finding Unmanaged Devices (PC’s, printers, servers, switches, routers, or any other device with an IP address, whether wired or wireless) on the network. The Discovery process looks for devices referred to as Unmanaged Devices. Once identified, certain devices can have a LANDESK Agent deployed to them, making them manageable from the Console from that point on.

Discovery can use two methods to find Unmanaged Devices, namely, Unmanaged Device Discovery (UDD), and eXtended Device Discovery (XDD).

Unmanaged Device Discovery (UDD)

The Unmanaged Device Discovery (UDD) method sends ping packet requests (ICMP protocol) on a predefined subnet range, and listens for ICMP Replies. The information obtained from ICMP Reply packets is used to compare with database entries to see if the responding machines are already present in the database. The MAC address and the NetBIOS Name are in the response packets. Management Suite searches for those entries in the database to ascertain whether the device is in the database.

If the corresponding MAC Address or NetBIOS Name, discovered in the network scan, is not present in the database, the device will be added to the UDD tool.

UDD lists the Operation System, if known, on devices it discovers. If the device was discovered via NT Domain discovery, the Operating System is listed in the Active Directory table, so UDD uses what is in the table to populate the UDD column. For all other UDD discovery, LANDESK uses NMAP Operating System Fingerprinting to discover the operating system on a Device. This technology sends malformed packets, which each operating system responds to in different ways. Through the responses, the Operating System is often discernible.

If you don't designate a subnet address range on a TCP/IP search, discovery is performed only on the network segment where the console initiating the discovery resides. For example, if you've installed four Consoles on four different PC workstations, each residing on a different network segment, you would have to initiate four scans, one from each of the four Consoles.

On network segments where there are no PC workstations with Consoles installed, you must use a subnet address range to scan that network segment.

To Launch a UDD Scan:

1. On the LANDESK Console click Tools > Configuration > Unmanaged Device Discovery.

2. On the Unmanaged Device Discovery tool click Scan Network (first icon on left on toolbar).

3. Enter the IP address range to scan in the Starting IP, Ending IP, and Subnet mask fields.

4. Click the More button if you desire to set additional scan options, then click Close.

     a. Standard network scan

     b. LANDESK Common Base Agent

     c. NT or LDAP Domain discovery

     d. LDAP

     e. IPMI-enabled devices

     f. Intel vPro-AMT devices

     g. Virtual hosts

5. Click Add.

6. Click Scan now, or Schedule task, to scan immediately or schedule the scan for later.

If from the Scan Network screen you click the More option, you will see this window.

Discover devices using a standard network scan: Searches for computers by doing an NMAP ping sweep. This is the most thorough search, but also the slowest. You can limit the search to certain IP and subnet ranges. By default this option uses NetBIOS to try and gather information about the device.

• IP OS Fingerprinting: Uses NMAP to try to discover what OS the device has.
• Use SNMP: UDD uses Simple Network Management Protocol (SNMP) to discover devices. Click Configure to enter information about SNMP on your network.
• Discover devices with LANDESK PDS2 installed: Searches for the standard LANDESK agent, formerly called Ping Discovery Service 2 (PDS2) on computers. This option discovers computers that have LANDESK products installed.
• Discover devices using NT domain: Searches for devices in a domain you specify.
• Discover devices using LDAP: Searches for devices in a specified Light-weight Directory Access Protocol (LDAP) directory.
• Discover Virtual Host: Looks for servers running the VMware ESX Server.

UDD Rights

In order to perform UDD a Console User needs to have Unmanaged Device Discovery right assigned to them through Role-Based Administration.

The View right grants the Console User the right to see and access the UDD tool. The Edit right grants the ability to create UDD scanner configurations. The Deploy right grants the ability to schedule and run different UDD scans.

NOTE: Agent discovery cannot be used to search outside firewalls, because firewalls generally limit the flow of packet traffic to designated ports.

Extended Device Discovery (XDD)

Extended device discovery (XDD) can help you find devices that UDD scans do not discover. XDD uses a managed device elected to be a listener on its subnet. XDD enabled managed devices listen for Address Resolution Protocol (ARP) broadcasts and maintain a cache (both in memory and in a file on the local drive) of devices that make ARP requests. Networked devices use ARP to obtain a Dynamic Host Configuration Protocol (DHCP) assigned address to join a network. Even heavily firewalled devices rely on ARP. Because of this, XDD can help you find devices that UDD scans do not discover.

Client Self-Election Process

In order to have one (and only one) device listening on each subnet, and reporting discovered devices to the Core Server, Management Suite uses a unique and ingenious process called the Client Self-Election Process (CSEP). In CSEP, one device on each subnet performs the role as listener. If that managed device is turned off or disconnects from the network, another device dynamically becomes the listener. With this technology, each subnet always has a listener so no devices are missed, and only one device per subnet is sending discovery information to the Core Server, utilizing only a minimal amount of bandwidth.

The CSEP implementation eliminates the need to have multiple agent configurations for devices on subnets. There is no need to have a configuration for listeners, and a separate configuration for non-listener devices. The self-election process makes it possible for each device to have the same configuration, and be able to be the listener, if elected.

Self-Electing Subnet Services

Currently, two services can be configured to use Self-Electing Subnet Services (SSS or S³), including Extended device discovery (ARP), and Extended device discovery (WAP). To configure the services to use S³, open the Self-electing subnet services tool. Here, the desired state of both services can be set. It also shows the subnets configured to use S³.

To set devices to be a part of the S³ election process, use the Client Connectivity agent setting. The setting is made by selecting the Enable self-electing subnet services checkbox, on the Self-electing subnet services page.

The Self-electing subnet services page sets which devices will participate in the election to be a listener. The Extended device discovery page configures how devices will work the process. Parameters include:

1. Use address resolution protocol (ARP): Whether to discover ARP announced devices
   • Duration ARP entry stats cached (in seconds): The length of time to keep discovered devices in the cache (default 86400 or 1 day)
   • Maximum delay before pinging an unknown device for the LANDESK agent (in seconds): Default 3600 or 1 hour
   • Frequency the cached ARP table is refreshed (in seconds): How often discovered devices are reported to the Core Server
   • Logging Level: The level of logging to select (IF the Force logging level checkbox is selected. Levels include:
     1. Errors only
     2. Errors and Warnings
     3. Debug
   • Give desktops preference over laptops: Whether to weight the election process to give desktops a higher probability of being selected to be the listener.
2. Use wireless access point discovery (WAP): Whether to discover WAP devices
   • Frequency of WAP scan (in seconds): How often discovered to scan for WAP devices
   • Logging Level: The level of logging to select (IF the Force logging level checkbox is selected. Levels include:

1. Errors only

2. Errors and Warnings

3. Debug

Process for XDD Discovered Devices

If Management Suite does not find a corresponding MAC address or NetBIOS Name in the database, the Core Server will act upon these added devices by waiting a random amount of time (between 15 minutes and 1 hour) to send a ping request to Agents that would exist on a managed device. The ping request packets from the Core Server are TCP port 9595 to the Standard LANDESK Agent, TCP port 9535 to the LANDESK Remote Control service, and TCP port 4343 to HTML5 Remote Control.

• Standard LANDESK agent: Enables the Ping Discovery Service (PDS). If the standard LANDESK agent is installed on a device, you can schedule software distributions and device setup configurations.
• Remote control: Lets you remotely access and control a device.

Any device that is not in the database, and does not send a response packet to the ping requests will be added to the UDD list.

There is a column in the UDD list titled “ARP Discovered”. Items found via a UDD scan populate the ARP Discovered field with “false”, while XDD discovered devices populate the field with “true”.

XDD can be set to listen to Wireless Access Point (WAP) traffic as well. If enabled, the listener will report wireless routers to the Core, and these routers will appear in the UDD list.

Setting an Agent Setting to include XDD

1. To include XDD as a part of agent setting, do the following:

2. Open the Agent Settings tool in the Console (Tools > Configuration > Agent Settings).

3. Expand My agent settings or Public agent settings and select Client connectivity.

4. Click the Create New Settings icon on the Agent settings toolbar. (The Client connectivity settings window appears.) OR open an existing Agent Setting you wish to change.

NOTE: This can optionally be configured by editing an Agent Configuration setting, selecting Client connectivity, and clicking [Configure]. (The Configure client connectivity settings window appears. Click [New]; (the Client connectivity settings window appears OR open an existing Agent Setting you wish to change.)

5. Click Extended device discovery (left window).

1. Click to select the Use address resolution protocol (ARP) checkbox, and configure the desired settings.
2. Optionally, you can click to select Use wireless access point discovery (WAP) checkbox and configure the desired settings.
3. Click Save.

I trying to understand how the "Core alert ruleset" functions on EPM 2018.1. 

This statement confuses me on the Description of "Core alert ruleset":

"Defines rules for alerts which are generated on the core. This ruleset is not manually deployed to clients." .  Does this mean it should not be added to the "Selected Configurations" for my Default Alert Agent Setting or are they already in place and functioning? 

Also there is one in the "Core alert ruleset" list that I would like to perform an email action on ... "Inventory Server - Database Maintenance Performed" .  It's already listed with a "log handler configuration" Action.  I wanted to create the Alert with an Email Action to send an email when Maintenance is performed.  I clicked the "New" button but "Inventory Server - Database Maintenance Performed"  is not anywhere in the Alert list I can choose from.  There are not any listings for "inventory Server" at all ... where do they come from?  I can clone the Alert but I can't change the action.

Another question is what log file is the "log handler configuration" action looking at. 

Alerting has always been confusing and the documentation is definitely lacking.

Regards,

Jim

We're running EPM 2017.3.3 - is there a way to get an alert when new software is detected, or run a report that shows software installed in the last X days?

The information can be found when the Management Console ( console.exe ) is open. Navigate in the menu bar to "Help" and then "About". In the next window click on "More info..." to get more detailed version information.

Ivanti Endpoint Manager 2018.1 SU1 (11.0.0.164)

README: https://community.ivanti.com/downloads/Readme/Pages/EPM2018.1-SU1.html Release Date: Useful links: Ivanti Endpoint Manager 2018.1 release information and useful links   Information about patches: Console.exe Ivanti 11.0.0 - Software License Monitoring vanti 11.0.0 - IT Asset Management LANDESK Software - Data Analytics Ivanti 2018.1 - SU LANDESK Management Suite Version LANDESK Software - Data Analytics Content 11.0.0.1089 11.0.0 11.0.0 11.0.1600 2018.1.1 - 2018-0705 2018.1.1 10.3.1510

Ivanti Endpoint Manager 2018.1 (11.0.0.164)

README: https://community.ivanti.com/downloads/readme/pages/epm2018.1readme.html Release Date: 2018/05/11 Useful links: Ivanti Endpoint Manager 2018.1 release information and useful links   Information about patches: Console.exe Ivanti 11.0.0 - Software License Monitoring vanti 11.0.0 - IT Asset Management LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content 11.0.0.1089 11.0.0 11.0.0 11.0.1600 10.3.1501

Ivanti Endpoint Manager 2017.3 SU5 (10.1.30.401)

README: https://community.ivanti.com/downloads/Readme/Pages/epm2017.3-SU5.html Release Date: 2018/06/12 Useful links: Ivanti Endpoint Manager 2017.3 Release Information and Useful Links Information about patches: LANDESK Software 10.1.30 - Software License Monitoring LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console Ivanti 2017.3 - SU LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content LANDESK Management Suite Version 10.1.30 10.1.30 9.6-ThinkManagement 2017.3.5 - 2018-0608C 10.3.1579 10.3.1464 2017.3.5

Ivanti Endpoint Manager 2017.3 SU3 (10.1.30.401)

README: https://community.ivanti.com/downloads/Readme/Pages/epm2017.3-SU3.html Release Date: 2018/05/01 Useful links: Ivanti Endpoint Manager 2017.3 Release Information and Useful Links Information about patches: LANDESK Software 10.1.30 - Software License Monitoring LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console Ivanti 2017.3 - SU LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content LANDESK Management Suite Version 10.1.30 10.1.30 9.6-ThinkManagement 2018-0118B 10.3.1578 10.3.1501 2017.3.3

Ivanti Endpoint Manager 2017.3 SU2 (10.1.30.401)

README: https://community.ivanti.com/downloads/Readme/Pages/epm2017.3-SU2.html Release Date: 2017/12/06 Useful links: Ivanti Endpoint Manager 2017.3 Release Information and Useful Links Information about patches: LANDESK Software 10.1.30 - Software License Monitoring LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console Ivanti 2017.3 - SU LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content LANDESK Management Suite Version 10.1.30 10.1.30 9.6-ThinkManagement 2017-1129 10.3.1578 10.3.1457 2017.3.2

Ivanti Endpoint Manager 2017.3 SU1 (10.1.30.401)

README: https://community.ivanti.com/downloads/Readme/Pages/epm2017.3-SU1.html Release Date: 2017/10/23 Useful links: Ivanti Endpoint Manager 2017.3 Release Information and Useful Links Information about patches: LANDESK Software 10.1.30 - Software License Monitoring LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content Ivanti 2017.3 - SU LANDESK Management Suite Version 10.1.30 10.1.30 9.6-ThinkManagement 10.3.1554 10.3.1465 2017-1013 2017.3.1

Ivanti Endpoint Manager 2017.3 (10.1.30.401)

README: https://community.ivanti.com/downloads/readme/pages/epm2017.3readme.html Release Date: October 5th 2017 Useful links: Ivanti Endpoint Manager 2017.3 Release Information and Useful Links Information about patches: LANDESK Software 10.1.30 - Software License Monitoring LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content 10.1.30 10.1.30 9.6-ThinkManagement 10.3.1554 10.3.1440

Ivanti Endpoint Manager 2017.1 SU2 (10.1.10.287)

README: https://community.ivanti.com/downloads/Readme/Pages/EPM2017-SU2.html Release Date: Useful links: Information about patches: LANDESK Software 10.1.10 - Software License Monitoring LANDESK Software 10.1.10 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console Ivanti 2017.1 - SU LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content LANDESK Management Suite Version 10.1.10 10.1.0 9.6-ThinkManagement 2017-0707 10.3.1527 10.3.1435 2017.1.2

Ivanti Endpoint Manager 2017.1 SU1 (10.1.10.287)

README: https://community.ivanti.com/downloads/Readme/Pages/EPM2017-SU1.html Release Date: Useful links: Information about patches: LANDESK Software 10.1.10 - Software License Monitoring LANDESK Software 10.1.10 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console Ivanti 2017.1 - SU LANDESK Software - Data Analytics LANDESK Management Suite Version 10.1.10 10.1.0 9.6-ThinkManagement 2017-0627D 10.3.1527 2017.1.1

Ivanti Endpoint Manager 2017.1 (10.1.10.287)

README: https://community.ivanti.com/downloads/Readme/Pages/IEM2017Readme.html   Release Date: May 3rd 2017   Useful links: Information about patches: LANDESK Software 10.1.10 - Software License Monitoring LANDESK Software 10.1.10 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content 10.1.10 10.1.0 9.6-ThinkManagement 10.3.1497 10.3.1385

LANDESK Management Suite 2016.3 SU5 (10.1.0.168)

README: https://community.ivanti.com/downloads/Readme/Pages/LD2016.3-SU_5.html Release Date: Useful links: Information about patches: LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software 10.1 - SU LANDESK Software 10.1.1 - Software License Monitoring LANDESK Software - Data Analytics LANDESK Management Suite Version LANDESK Software - Data Analytics Content 10.1.0 9.6-ThinkManagement 2017-0731 10.1.1 10.3.1429 2016.3.5 10.3.1442

LANDESK Management Suite 2016.3 SU4 (10.1.0.168)

README: https://community.ivanti.com/downloads/Readme/Pages/LD2016.3-SU_4.html Release Date: Useful links: Information about patches: LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software 10.1 - SU LANDESK Software 10.1.1 - Software License Monitoring LANDESK Software - Data Analytics LANDESK Management Suite Version LANDESK Software - Data Analytics Content 10.1.0 9.6-ThinkManagement 2017-0612B 10.1.1 10.3.1424 2016.3.4 10.3.1440

LANDESK Management Suite 2016.3 SU3 (10.1.0.168)

README https://community.ivanti.com/downloads/Readme/Pages/LD2016.3-SU_3.html Release Date: Useful links: Information about patches: LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software 10.1 - SU LANDESK Software 10.1.1 - Software License Monitoring LANDESK Software - Data Analytics LANDESK Management Suite Version LANDESK Software - Data Analytics Content 10.1.0 9.6-ThinkManagement 2017-0210 10.1.1 10.3.1389 2016.3.3 10.3.1423

LANDESK Management Suite 2016.3 (10.1.0.168)

README: https://community.ivanti.com/downloads/Readme/Pages/LD2016.3.html Release Date: Useful links: Information about patches: LANDESK Software 10.1.1 - Software License Monitoring LANDESK Software 10.1.0 - IT Asset Management LANDESK Software 9.6 - ThinkManagement Console LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content 10.1.0 10.1.0 9.6-ThinkManagement 10.3.1353 10.3.1301

LANDESK Management Suite 2016.0 (10.0.0.271)

README: https://community.ivanti.com/docs/DOC-39935 Release Date: Useful links: Information about patches: LANDESK Software 10.0.0 - Software License Monitoring LANDESK Software 9.6 - ThinkManagement Console LANDESK Software - Data Analytics LANDESK Software - Data Analytics Content 10.0.0 9.6-ThinkManagement 10.0.1111 10.0.1111

LANDESK Management Suite 9.6 SU3 (9.60.0.244)

README https://community.ivanti.com/downloads/Readme/Pages/LD96SP3.html Release Date: Useful links: Information about patches: LANDESK Software 9.60 - Service Pack 2 LANDESK Software - Data Analytics LANDESK Software 9.60 - Service Pack 3 LANDESK Software 9.60.2 - Software License Monitoring LANDESK Software - Data Analytics 9.61 Update LANDESK Software 9.60.4 - SU LANDESK Software - Data Analytics Content 9.60.2.72A 9.62.0670 9.60.3.168D 9.60.2 9.62.1106 2017-0509 10.3.1423

LANDESK Management Suite 9.6 SU2 (9.60.0.244)

I saw EPM2018.1-SU1 readme page https://community.ivanti.com/downloads/Readme/Pages/EPM2018.1-SU1.html but I can't find a link to download.

Is it available yet?

HI THERE ,

Is there any way to stop downloading the updates from the console on a machine that already downloading the patches ???

Thank youu 

Hi All

When creating Definition download filters, how do people go about finding the correct combination of Definition Type, Severity and Comparison rules.

Ideally what i'm looking for is to be able to search the Ivanti definition servers, find updates that i'm interested in, and create rules that match the categories shown in my search.

Real world example: currently we are looking for the correct combination for the Windows Feature updates, e.g 1709, 1803 etc.
Took a stab in the dark and tried the combination, Vulnerability, Service pack, Vendor contains Microsoft, which was correct, however there has to be a better way than taking a stab in the dark.

Thanks

We are runnig on 2017.3 and facing some problems with the provisioning of Windows 10 UEFI(PXE64BiT) we do have several Preferred servers in your locations.

The Problem is, hat they will not be taken e.g. I want to install a client in china but it do not take the preferred server in china, it takes the one in germany. I already checked the preferred server configuration and this one ok, installations with Windows 7(PXE32BIT) are working fine. Do you have any idea ?

Than you

     Hello everybody ,

I can't push the patches for several machines with error code 412, so I saw in an ivanti procedure that the problem is related to the configuration of a registry key : "Common AppData"="C:\ProgramData"

I'd like to know if anyone has a solution to deploy this key using a script and deploy it by distribution packages

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders]

"Common AppData"="C:\ProgramData"

Thanks for the help !!

Hello everyone,

I would like to know how can I get a list of queries that are running on a specific device.

Thank you in advance.

Best Regards.

Marco

I am trying to run a compare variable action using if conditions to apply an action on machines that are deployed running Bitlocker.

I want to look up the database field :

"Computer"."Mass Storage"."Drive Encryption"."Protection Status"

This field has two states:

"1 - on" and "0 - off"

What i want is when "1 - on" is found, it runs a script and if it is not found, it continues.

What I have done:

1. Created public variable with Database value with the above information

2. I created a provision template and put an if condition statement under the System Migration and use the Compare Variable. See attached Graphic

For now, i just want the Wait window to pop up to verify functionality.  It seems this does not work and I am not sure why.

I have tries the value to be = and 1 - on as well and it fails.

Thoughts, Tips, Comments?

Any help is appreciative.

How can i bypass this issue?

I have desktop PCs that show up with Type= Workstation, and others are Type= Machine. How does the system determine this, and why would similar computers show up differently?

Hallo in die Runde,

folgendes Problem tritt bei einem Teil unserer Clients auf:

Der Sicherheitsscan findet den Core Server nicht.

Darauf hin haben wir den Kaspersky Antivirus- und den Ivanti Client komplett entfernt und neu installiert.

Die Installation läuft ohne Probleme beim anschließenden Sicherheitsscan passiert wiederum nichts.

So sieht das dann aus.

Hat Jemand ne Idee was wir hier machen können?