How can I compare all the settings on 2 different agent configurations?  I don't see a report available for this and it looks like I can only open one Agent Configuration Properties at a time.   Trying to compare differences in the 2 agents without doing a screen shot of each window of each config.  (novice user)

When configuring agents I'm trying to identify is "Software Distribution" is a feature we should have checked.  We have always used Scheduled tasks to deploy software to Agent workstations but have never used the Desktop Manager or the Portal.

What features require "Software Distribution" exactly?

Thanks

Jonathan

Agent Deployment for LANDesk Management Suite

General Information

  Standard Push:The agent files are located on the core server and distributed via a push task. The credentials used in the Scheduler configuration on the core server are critical for this type of distribution.

    Self-Contained Executable: Agent files are compiled into a completely self-contained executable that is portable. This method is efficient and helps with a lot of network configurations however the executable does not get updated when the configuration changes or when files are updates by patches or new releases. It is recommended to keep these executables in a central location and perhaps date them as well so that they can be rebuilt as needed. Two self-contained executables are created for this option one with status (shows GUI to the user) and one without.

    Advance Agent: The primary purpose of this agent deployment method is to control the amount of bandwidth used during agent install. However, the design has many other uses. The agent is broken up into two files (and MSI and an EXE). The MSI will install a temporary service on the client where it will gradually stream down the main executable and install the agent. The temporary service is removed. Since the temporary service comes in MSI form this design also makes it favorable for deployment using an Active Directory login script. (Note: Including security definitions with the agent can make the primary executable very large and greatly increase agent download/install times)

     Wscfg32.exe: This is an executable located on the core server in the ldlogon sub-folder. When executed on a client it will pull the settings in a default windows configuration and launch an agent install window. Changes can be made to the configuration before starting the agent install.

     Other Operating System Information: Macintosh and Linux/Unix agents will work somewhat different than Windows based ones. For details on those agents please check their component landing pages.

Supported Platforms and Compatibility Matrix for LANDesk Management Suite

Install and Configuration

• Video:Agent Installation Methods
• Video:Agent Configuration
• Video:Management Suite 9 Fundamentals Agent Configuration
• How to create an Advance Agent
• How to create an Advance AgentDocumentation for Agent Configuration and Deployment (Best Known Method for LANDesk 9)

Troubleshooting and Known Issues

     General Troubleshooting Recommendations:

• The LANDesk agent (just like any other program) can be affected by Anti-virus, Spyware, and other blocking programs. Closing or suspending such programs may help with agent installation.
• When right-clicking on an agent two of the options will be "Schedule agent deployment" and "Schedule update to agent settings". The difference between these two is that the update will not deploy any files and only make changes to when scan run etc. If a new feature is added to the configuration or removed then a full agent deployment will be required.
• If an error occurs during the creation of the agent (advance agent or self-contained) a log file is generated. Typically the agent configuration was told to include a certain file and the process either couldn't find the file or didn't have access to it.

• Advance Agent install process and troubleshooting tips
• Why can't I install the Advance Agent over itself on a client?
• UninstallWinClient.exe may not run correctly on Windows 7 under UAC
• How to completely remove LANDesk from a remote console or client device

Additional Options and Information

• Video:Agent Deployment via Login Script
• Video:Agent Deployment via WSCFG32
• Customizing the LANDesk Agent using the NTSTACFG.IN# file
• How to uninstall the LANDesk Agent on Windows Platforms
• How to uninstall the LANDesk Agent on Macintosh Platforms

Notice:Any E-Learning content is available by default to Members who have a minimum support agreement at Professional level.

NOTE: This article is not a comprehensive list of documents and issues. You can continue to search the rest of the community or the portion specific to Agent Deployment if this page hasn't helped.

Has there been a resolution to installing the LANDesk agent onto a Windows Server that is running in Core Mode?  I heard awhile ago, that it was not supported.  I was hoping that a solution or workaround has been created?

When installing the server agent on Windows Server 2008 we get the following errors in the event log.

Just wondering if  anyone else has seen this?

Using 9.5 SP1 with latest 9.50.1 base patch (2013-0813) and Data Analytics 9.5 SP1 with patch 99.

------------------------------------------------------------------------------------------------------------------------------------------------

Faulting application name: ldstate.exe, version: 9.50.0.530, time stamp: 0x506d7ae0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x772b1221
Faulting process id: 0xfd4
Faulting application start time: 0x01ce9e9db6158098
Faulting application path: C:\Program Files (x86)\LANDesk\LDClient\ldstate.exe
Faulting module path: unknown
Report Id: 5bcc3700-0a91-11e3-9efb-005056be00f0

-------------------------------------------------------------------

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ldstate.exe
P2: 9.50.0.530
P3: 506d7ae0
P4: StackHash_76a7
P5: 0.0.0.0
P6: 00000000
P7: c000041d
P8: 772b1221
P9:
P10:

Attached files:
C:\Windows\Temp\WERD9EE.tmp.appcompat.txt
C:\Windows\Temp\WERDBE3.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WERDBF4.tmp.hdmp
C:\Windows\Temp\WERDE46.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ldstate.exe_c86651c86a75317afbe178b6c2adda221ad3356_cab_5ae2de72

Analysis symbol:
Rechecking for solution: 0
Report Id: 5bcc3700-0a91-11e3-9efb-005056be00f0
Report Status: 4

-------------------------------------------------------------------

Faulting application name: LDAlert.exe, version: 9.50.0.530, time stamp: 0x506d63fb
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x772b1221
Faulting process id: 0x9f0
Faulting application start time: 0x01ce9e9db61f0a18
Faulting application path: C:\Program Files (x86)\LANDesk\LDClient\LDAlert.exe
Faulting module path: unknown
Report Id: 5d8089a0-0a91-11e3-9efb-005056be00f0

Faulting application name: LDAlert.exe, version: 9.50.0.530, time stamp: 0x506d63fb
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x772b1221
Faulting process id: 0x9f0
Faulting application start time: 0x01ce9e9db61f0a18
Faulting application path: C:\Program Files (x86)\LANDesk\LDClient\LDAlert.exe
Faulting module path: unknown
Report Id: 5d8089a0-0a91-11e3-9efb-005056be00f0

------------------------------------------------------------------

Faulting application name: ldlocalprt.exe, version: 9.50.2.1, time stamp: 0x50f6b11c
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x772b1221
Faulting process id: 0x2418
Faulting application start time: 0x01ce9e9db623ced8
Faulting application path: C:\Program Files (x86)\LANDesk\LDClient\ldlocalprt.exe
Faulting module path: unknown
Report Id: 5dca7340-0a91-11e3-9efb-005056be00f0

------------------------------------------------------------------

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: ldlocalprt.exe
P2: 9.50.2.1
P3: 50f6b11c
P4: StackHash_76a7
P5: 0.0.0.0
P6: 00000000
P7: c000041d
P8: 772b1221
P9:
P10:

Attached files:
C:\Windows\Temp\WERE20C.tmp.appcompat.txt
C:\Windows\Temp\WERE2C9.tmp.WERInternalMetadata.xml
C:\Windows\Temp\WERE2D9.tmp.hdmp
C:\Windows\Temp\WERE309.tmp.mdmp

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_ldlocalprt.exe_4da0d1f3ac9f71391f1918d63647b2e8294894b_cab_6e0ee345

Analysis symbol:
Rechecking for solution: 0
Report Id: 5dca7340-0a91-11e3-9efb-005056be00f0
Report Status: 4

We've been running through upgrading all our agents to 9.5 SP1 from 9.0 SP3 and i've started running into a number of issues with software deployments tasks, errors relating to 'agent out of date' errors 'please update client' type messages etc. Seems simply enough, work around was put in place by creating a new deployment policy that specifies to only use methods supported on individual clients.

But i was still curious as to how this could be the case, in most instances for our servers we completed manual installs with varying degree's of success - any number of issues with kaspersky updating / not updating at all / only installing the kaspersky a/v and not badging it LANDesk etc, so looking further into the device inventory i've found that the software deployment components themselves have not been getting updated on all clients - its very hit and miss.

Working combinations seem to be LD agent version 9.50.2.6 & policy.sync.exe 9.50.2.14 or 9.50.1.1 the clients with issues look to have lower versions of policy sync, i can see 9.0.2.29, 9.00.0.473, 9.0.1.3.

Is it possible to update the software distribution components only, similar to the method we can use to update installed security components to the latest version?

A great feature to have would be an agent health check of sorts, that could give you a summary of all agent versions against what they should be as per the core's latest updates etc and then an update worker process that simply downloads the latest components the agents are missing and installs.

I often use the Last Scanned date as an indication of when a computer was last online. We have over 1500 total devices. Approximately 200 of these have dates older than November 1, some back to September.

I left most of the agent settings as default when preparing it so no odd scheduling conflicts. Based on this, what percentage of my computers should display a Last Scan date within 7 days of now?

Thanks,

Sheldon

We have about 1500 devices with LD agents. What I notice is that over time, these agents stop reporting back to the core; the last scan dates stretch out for weeks. So as I get ready to push out the new SP1 agents, I'm thinking of adding the Agent Watcher piece to see if I can figure out why.

Does this add any significant overhead to our client machines?

Thanks...

We are getting several devices that fail the install. Checking the MSI logs, they all seem to have this same error:

Action start 17:52:59: SetClientDirAction.
MSI (s) (24:98) [17:52:59:235]: Doing action: MSILocalizationAction.dll
Action ended 17:52:59: SetClientDirAction. Return value 1.
MSI (s) (24:98) [17:52:59:235]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'MSILocalizationAction.dll'
MSI (s) (24:98) [17:52:59:235]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (24:98) [17:52:59:235]: Note: 1: 2721 2: MSILocalizationAction.dll
Action start 17:52:59: MSILocalizationAction.dll.
DEBUG: Error 2721:  Custom action MSILocalizationAction.dll not found in Binary table stream
MSI (s) (24:98) [17:52:59:236]: Product: DefaultProductName -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2721. The arguments are: MSILocalizationAction.dll, ,

The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2721. The arguments are: MSILocalizationAction.dll, ,
Action ended 17:52:59: MSILocalizationAction.dll. Return value 3.
Action ended 17:52:59: INSTALL. Return value 3.

Any ideas?

We have a script that runs after our systems are imaged that install several pieces of software and the system is not always on the network at the time.  The LANDesk agent is the first thing to install after a system is imaged and since 9.5 SP1 it is taking 10 minutes longer to install the agent (it is taking about 10-14 minutes to install where it only takes 5-6 minutes to install while on the network).

I ran procmon on a system off the network and found that there appears to be a 10 minute timeout trying to get the ResolveDeviceID and GetHashFile from the core server.  Note the agent was started at 9:46 and finally finished at about 10:02

Vulscan log (c:\programdata\vulScan\vulscan.log) entry retrying over and over again:

Fri, 15 Nov 2013 10:01:30 Action SOAPAction: "http://tempuri.org/GetHashForFile" failed, socket error: 11004, SOAPCLIENT_ERROR: 5.  Status code: -1, fault string:

Vulscan log (c:\programdata\vulScan\vulscan.log) entry giving up after 10 minutes:

Last status: Failed: No response from core

Self update Failure: Core did not return requested file hashes.  Error: 80004005

Fri, 15 Nov 2013 10:01:30 ERROR: Socket timeout of 600000 milliseconds was exceeded.  Giving up

softmon log (c:\programdata\vulScan\softmon.log) entry retrying over and over again:
Fri, 15 Nov 2013 09:59:13 Action SOAPAction: "http://tempuri.org/ResolveDeviceID" failed, socket error: 11004, SOAPCLIENT_ERROR: 5.  Status code: -1, fault string:

softmon log (c:\programdata\vulScan\softmon.log) entry giving up after 10 minutes:

Fri, 15 Nov 2013 09:59:28 ERROR: Socket timeout of 600000 milliseconds was exceeded.  Giving up

Has anyone else seen this issue?

QUESTION:

How to include setting, file with all agents

ANSWER:

The NTSTACFG.IN# can be used for this purpose.

The NTSTACFG.INI corresponds to the default agent configuration.

STEPS to implement this changes:

#1

From the core server Browse to LDLogon in the path:

C:\Program Files\LANDesk\ManagementSuite\ldlogon

#2

Locate the file NTSTACFG.IN#

And modify the following file which affects all agents:

C:\Program Files\LANDesk\ManagementSuite\ldlogon\ntstacfg.in#

#3

On the core server run the stamper.exe to apply the changes from NTSTACFG.IN# to NTSTACFG.INI

C:\Program Files\LANDesk\ManagementSuite\stamper.exe

OR

Restart the Inventory Server service (it will initiate the stamper.exe at restart)

#4

Check that your changes have been apply by navigating to:

C:\Program Files\LANDesk\ManagementSuite\ldlogon

#5

Open the NTSTACFG.ini that should reflect those changes.

#6

From now all new Agent Configuration will contain these changes.

In order to apply this changes to all existing Agent configuration.

Then open the console and go to Tools - Configuration -Agent Configuration

And click on the Rebuild All in that section (that will update all existing agent configuration)

#7

Note that the file NTSTACFG.IN# contains 3 main sections that need to be updated:

                [Products] -> refer to our new section (yes= enable / NO= Disable)

                [Component Order] -> order to follow

                [new section to create] -> to include new file to add with agent install for example

ENVIRONMENT:

All LDMS version

Configured dynamic Preferred Servers will not work with AdvanceAgent  because the "scaled down" version of the downloader contained in  AdvanceAgent does not have full functionality for Preferred Server built  in. This was done to keep the AdvanceAgent as small as possible for  deploying via group policy. This means that AdvanceAgent is not able to  get a dynamic list of preferred servers from the Core Server or able to use Preferred Server for authentication to locked down shares.

Even though dynamic discovery and authentication are not  supported by AdvanceAgent, the legacy Preferred Server method can still be used. You can enable the use of preferred server(s) by simply creating a registry key on the workstation before installing the agent.

Please note that LDMS 9.0 SP2 and later agent needs Microsoft Visual C++ 2005 to be installed on the Windows XP client prior to advance agent installation. Without MS Visual C++ advance agent service will crash. Windows 7 clients come with MS Visual C++ already included.

Important note: by default advance agent will use HTTP path to download the .EXE file. If your preferred server is not configure with IIS, you must change the path for the .EXE file to UNC path! Failing to do so will result the .EXE being downloaded from the core server instead.

Add the following key to the workstation before running your  AdvanceAgent.msi

[HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\WinClient\SoftwareDistribution]
"PreferredPackageServer"="THLANDESK;THLANDESK90"

Multiple servers are separated by a semicolon (as shown  above). Up to 3 Preferred Servers may be used.

Another way to accomplish this task is to edit the  AdvanceAgent.msi with Orca and add the registry key. This method will  allow installing the msi as you normally would without having to perform  additional steps.

1. Download and install Orca.msi (Google knows where this is)
2. Edit the AdvanceAgent.msi of the desired agent configuration with Orca
3. Scroll down to Registry then right click and select "Add Row"
4. Fill out all required fields (key value can be random numbers, then fill the other fields using the values from the registry key at the top of this article)
   
5. Set 'UsePreferedServer' to #1.
6. Save the .msi
7. Deploy the .msi normally (manually, GPO, scheduled task, etc)

Notice in the following xtrace of LDDwnld, that the original path in the AdvanceAgent setup http://landesk.com/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe has been escaped to http://THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe (THLANDESK being 1 of 2 preferred servers added with the registry key above.

LDDwnld.xlg (xtrace log) This log will verify that the download is coming from the Preferred Server(s) vs. the core.

04/15/2010 08:28:33.391    1016    440    lddwnld.cpp    2246    Calculating levels in 'http://THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe'
04/15/2010 08:28:33.407    1016    440    lddwnld.cpp    2265    UNC/URL prefix removed, calculating for 'THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe'
04/15/2010 08:28:33.407    1016    440    lddwnld.cpp    2279    current levels 1, remaining path '/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe'
04/15/2010 08:28:33.407    1016    440    lddwnld.cpp    2279    current levels 2, remaining path '/AdvanceAgent/THLANDESK90 No Extras.exe'
04/15/2010 08:28:33.407    1016    440    lddwnld.cpp    2279    current levels 3, remaining path '/THLANDESK90 No Extras.exe'
04/15/2010 08:28:33.423    1016    440    lddwnld.cpp    2281    Calculated 3 levels for path 'http://THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe'
04/15/2010 08:28:33.423    1016    440    lddownload.cpp    1322    AddFileToDownloadSet: called with sourcePath http://THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe, hash 
04/15/2010 08:28:33.423    1016    440    lddwnld.cpp    2092    GetFileInformation - same path last=http://THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe current=http://THLANDESK/ldlogon/AdvanceAgent/THLANDESK90 No Extras.exe

Since the agent file hash is contained in the MSI, the original path in the AdvanceAgent setup does not need to be accessible. In normal LANDesk Software distribution jobs, the original source patch is contacted to verify the files on preferred servers are authentic.

Note: This registry key should be removed after full agent install to fully utilize dynamic Preferred Server capabilities.

Description

LANDesk allows for the configuration of a single username and password for managing Virtual OS Hosts. Using the ESX web services and can be accessed and some inventory information can be obtained. This document describes how to configure the LANDesk Virtual OS Hosts username and password and how to discover and get basic information from Virtual OS Hosts.

Note: Management Suite talks to an ESX web interface to get the discovery information.  Please refer to the following VMWare knowledgebase article for more information:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006543

Note: ESX* 5 is supported in LDMS 9.5.1(9.5 service pack 1) and higher.

Configuration Steps

The following steps will walk you through configuring LANDesk Virtual OS hosts.

1. Open the LANDesk Management Suite Console on the Core server.
2. Click on Configure | Services.
   
3. Click on the OS Virtualization tab.
4. Enter the Credentials needed to access the Web Console for the ESX server.
5. Click OK.
   
6. Click on Tools | Configuration | Unmanaged Device Discovery
   
7. Click the Scan Networks button.
   
8. Click New and give the Scan Configuration a name.
9. Click More >> to expand the addition options.
   
10. Check the Discover Virtual Hosts.
11. Uncheck all other options.
12. Enter the Starting and Ending IP address for the range you would like to scan.
13. Click Add.
14. Click Scan now.
    
15. After the Scan completes click Close.
16. Click on Virtual Hosts in Unmanaged Device Discovery.
    
17. Right click on the ESX servers that appear and choose Move to Inventory Database.
    
18. The ESX server will now show under Virtual OS Hosts | All virtual Hosts.
    
19. Right Click on the ESX server and choose Inventory Scan.
    
    1. This will launch a Virtual Host inventory scan.
       
20. After the scan completes Right click on the ESX server and choose Inventory.
    
21. You will see the inventory for the ESX server including all the Clients that are running on the ESX server.
    

The following is a list of Services and Executables run on the 9.0 SP2 Landesk Agent.

SERVICES

LANDesk Message Service

LTAClientEnforcer

LANDesk Ping Discovery Service

LANDesk Remote Control Service

LANDesk Targeted Multicast

LANDesk(R) PXE MTFTP Service

LANDesk(R) PXE Service

LANDesk Policy Invoker

LANDesk(R) Antivirus

LANDesk(R) Management Agent

LANDesk(R) Software Monitoring Service

EXE

C:\WINDOWS\system32\msgsys.exe
C:\WINDOWS\system32\cba\pds.exe
C:\Program Files\LANDesk\LDClient\issuser.exe
C:\Program Files\LANDesk\PXE\System\PXEMTFTP.exe
C:\Program Files\LANDesk\PXE\System\PXESvc.exe
C:\Program Files\LANDesk\LDClient\LTAClientEnforcer.exe

C:\Program Files\LANDesk\LDClient\ActiveNotifyer.exe

Description: If it is determined that a local scheduler task should be removed from client computers it can be done through a script run as a scheduled task in the LANDesk Management Suite 32 bit console.

Resolution:

Create a Query

1) In the 32 bit console right click on My queries and click New Query

2) Under Machine Components go to Computer | Device Name

3) Click Exists and click Insert

4) Click the button labeled Select Columns

5) Under Machine Components go to Computer | LANDesk Management | Local Scheduler | Scheduled Tasks

6) Click on Handle and click the button labeled >>

7) Click on Executable Path and click the button labeled >>

8) Name the query "Local Scheduler Handles" and click Save

9) Run the query and find the Handle number for all of the local scheduler tasks you want to delete

Note: The default Handle number for Vulscan.exe (security and patch) is 555 and the default Handle number for ldiscn32.exe (inventory scan) is 777

Creating the script to delete the local scheduler tasks

1) In the 32 bit console go to Tools | Distribution | Manage Scripts

2) Right click on my scripts and click New Custom Script

3) Name the script and click OK

4) Select all and delete it

5) Paste the following into the script

[MACHINES]

REMEXEC0=<qt/>%LDMS_CLIENT_DIR%\LocalSch.exe<qt/> /del /taskID=HandleID

6) Change HandleID to the handle number you found in the query - The script in this example will delete the default security scan task

7) Save the script

8) Right click on the script and click Schedule

9) Drag computers into the task and start it

Applies to LANDesk Management Suite 8.8
Applies  to LANDesk Management Suite 9.0

Problem:

When trying to push out an agent to a new computer you receive the following error in the ScheduledTaskHandler log.

Remote execute of application 'C:\$ldcfg$\IPCheck.exe', params  'SPIAMAREALLYLON' on SPIAMAREALLYLON (1e32a8c0)
Wed, 22 Jul 2009  11:30:48 SPIAMAREALLYLON, CBA discovery & IPCheck failed
Wed, 22  Jul 2009 11:30:48 SPIAMAREALLYLON Removing temporary directory
Wed,  22 Jul 2009 11:30:48 Remote execute of application 'cmd', params '/c  rmdir /s /q C:\$ldcfg$' on SPIAMAREALLYLON (1e32a8c0)
Wed, 22 Jul  2009 11:30:50 [Operation failed] RemoteExecute, cmd /c mkdir C:\$ldcfg$

Cause:

The Computer name of the target is longer than the 15 character limit that NetBIOS can support. This is causing the hostname check that IPcheck performs to fail.

Resolution:

This problem does not occur when using the Advance Agent or the self--contained installation file.

Cause

Locate the Computer Inventory Record from all devices and delete it. Then rerun the UDD Scan

The computer has a entry in Pending Unmanaged Client Deployments.

From the Network View | Configuration | Pending unmanaged client Deployment, delete the Computer record. Then Rerun the UDD Scan.

Description

How to create a self-contained agent package to be installed by client devices.

Resolution

1. Open the LANDesk Management Suite console.
2. Go to Tools | Configuration | Agent Configuration.
3. Configure the agent settings according to your environment needs.
4. Click on 'Save'.
5. Right-click on the newly-configured agent, select 'Create self-contained client installation package'
6. Save the exe file on a network share accessible by users.
7. From the client devices, run the executable that was created above. Note - There will be two executables created one with status and one without, these will determine what will be shown on the client screen during install.

Hello,

Since upgrading from Landesk 9.0 Sp4 to 9.5 Sp1 (and adding Mirror Driver) many (or maybe all) workstations seem to get a few of these Event viewer notifications (Application log) each day.  There doesn't seem to be any performance issues but this is a bit distrurbing.  Thank you. Jonathan

Log Name:      Application

Source:        LANDesk Remote Control Service

Date:          11/18/2013 9:11:30 AM

Event ID:      2

Task Category: None

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      BOSWS09805.amsa.com

Description:

Remote control action:  ¹çF  ÇÙ ù%ݪf‚ÚÅÀ™Åk&#144;×ßÅ Ð! °åXé¦Z´^ålRGÈjck4 Å(FEùyÿ ¥‡°¼"^|q*0¨zãc ërB†½&![ǤžxwÖJÝõÁ=ÛMÓ¾?¬füê0…Œõ¡H4ƒH$ÝŠép§Q<  Initiated from  by user , Security Type: Integrated

Event Xml:

<Event xmlns='http://schemas.microsoft.com/win/2004/08/events/event'><System><Provider Name='LANDesk Remote Control Service'/><EventID Qualifiers='16384'>2</EventID><Level>4</Level><Task>0</Task><Keywords>0x80000000000000</Keywords><TimeCreated SystemTime='2013-11-18T14:11:30.000000000Z'/><EventRecordID>33269</EventRecordID><Channel>Application</Channel><Computer>BOSWS09805.amsa.com</Computer><Security/></System><EventData><Data>Remote control action:  ¹çF  ÇÙ ù%ݪf‚ÚÅÀ™Åk&#144;×ßÅ Ð! °åXé¦Z´^ålRGÈjck4 Å(FEùyÿ ¥‡°¼"^|q*0¨zãc ërB†½&amp;![ǤžxwÖJÝõÁ=ÛMÓ¾?¬füê0…Œõ¡H4ƒH$ÝŠép§Q&lt;  Initiated from  by user , Security Type: Integrated</Data></EventData></Event>