Environment

8.7

Problems/Symptoms

When trying to delete a scheduled task a pop-up error similar to the following appears:

"DELETE statement conflicted with COLUMN REFERENCE constraint 'FK_TAM_LD_TASK_IDN'. The conflict occurred in database 'landesk', table 'TaskAllowedMachines', column 'LD_TASK_IDN'."

Cause

This happens if the package that the task is based upon has a prerequisite query.

Solution

For LANDesk Management Suite 8.7 Download the latest Service Pack for LANDesk Software products

Is there a document somewhere that details how the communication between the server and the agent takes place?

I seem to be having issues with some of my laptops that come in through a VPN, the default connection/IP is being reported as the external/public interface as opposed to the VPN interface and i'm wondering if this may be causing an issue with the communication.

The problem I'm having is that some of the VPN connected laptops are sitting in an "active" state for extend periods of time then failing with return 1110 Cannot find agent.

Hi Friends,

Kindly help me with the below issue, LANDesk agent is getting uninstalled automatically in most of the system in my network. Kindly suggest.

Thanks,

Dinesh

Hi Friends,

Kindly help me with the script to uninstall opera browser silently using landesk software distribution.

Thanks,

Dinesh

Purpose

Additional verbose logging is available for Policy and Policy Supported Push Tasks. This Logging can be turned on to assist in troubleshooting issues encountered when targeting as task using Policy and Policy Supported Push methods. Once enabled additional information will be written to the ...\LANDesk\Management Suite\Log\PolicyTaskHandler.log file.

Steps

• Open Scheduled Tasks
  • Select Tools from the menu bar
  • Select Distribution
  • Select Scheduled Tasks
• From the Scheduled Tasks Toolbar
  • Select Configure Settings (Gear Icon)
  • Select Default Scheduled Task Settings

• Check the Enable Verbose Policy Task Handler Logging box
• Click Save

• Restart the Scheduler Service
  • Select Configuration from the menu bar
  • Select Services
  • Select Scheduler tab
  • Click Restart

The issue that I am having is LANDesk both 9.0 and 9.5 never show completed when trying to push Office 2013. Office will actually install on the client machine but within the log files LANDesk always just shows "Processing generic executable" and nothing more. I am never presented with a completed return code.The way I have my package setup is that I have all additional files included they are pushed to the client. I have my .msp within the office "updates" folder. I can run office manually just fine but when going though LANDesk it seems to be somewhat of a headache.

My Account is running as the "LocalSystem Account" I have a slew of office return codes but it never offers a return code because the task actually times out.

I have also packaged Office a few different ways as well. I have made a script to just call the .exe same things happens. I have tired running from source but when I do this within 9.6 i am presented with "Client has initiated asynchronous policy execution" Return code 1354 - This will not time out but just stay present in "Active" status until I cancel out the scheduled task. I believe this might be an issue with 9.6 and I have seen some other users presented with.

Has anybody else encountered these issues?

In some special cases it is necessary to send up custom messages to the console during a deployment task. In LDMS 9.6 SP1 and later this is not as common as we have implemented task stages so you can see if the task is in the Core Initiated, Downloading, Installing, or Completed states. For large deployment packages that are scripted it is helpful still to send a status up to the core detailing what step the task is on. Previously this was possible by using the following command in your script.

"%LDMS_LOCAL_DIR%\..\SDClient.exe" /taskid=%task_id% /msg="Any Message"

However, this method is being deprecated and replaced with SendTaskStatus.exe which is a more capable process dedicated specifically to sending a task status for any type of task to the core server.

Here are the command line options for SendTaskStatus.exe. The required parameters are "-core", "-taskId", and "-retcode" all other are optional.

Command line syntax:

sendtaskstatus.exe -core=<core> -taskId=<taskId> -retcode=<return code> -message="message"

Arguments:

• -core
  • Name of the Core Server
• -coreandip
  • The IP Address of the core server, or the name:IP address of the core server.
• -taskId
  • ID for which the return code is to be updated. You can use the %task_id% variable for this parameter to avoid having to set the task ID manually in each script every time they are scheduled.
• -return code
  • Current return code for the task. If using a BAT script and you'd like to pass up the return code for the most recent action in the script you can use the %errorlevel% variable.

Optional Arguments:

• -complete
  • When specified the task is treated as being completed and will be moved to either the Successful or Failed status buckets in the task depending on the return code.
• -message
  • A custom message to be displayed in the scheduled task message column in the console.
• -ldap
  • LDAP information to be reported with the status.
• -log=<file>
  • Path to a log file which will be reported.
• -pkgId=<id>
  • Software distribution tasks use the package id to update a set of tasks that all target the same package.

Example Command of a simple task message update used in a BAT script:

"%LDMS_LOCAL_DIR%\..\SendTaskStatus.exe" -core=mycore.landesk.com -taskid=%task_ID% -retcode=%errorlevel% -message="Configuring System"

LANDESK Management Suite 9.5 and 9.6

Landesk 9.5 SP1

Does anyone know if there is a way to either limit the number of times a user can install the same software title assigned to them via Landesk, or is there a way to block a user from installing software on any machine they log into?

for the most part, software is assigned to an user's machine. But for a large number of users, the software is assigned to their ID so the software is available to install as soon as they log into their new machines. Those users in particular can install software assigned to them on any machine they log into. We are researching possible ways to restrict this. Like looking for a way to block faculty from installing software assigned to them on their graduate student machines or TA machines or on lab machines, etc. A few have realized they can do this... Perhaps we can limit the number of times a specific user can install a specific software title?

Banner is our parent system, some of that information is passed to AD which our LANDesk is connected to.

Any help is greatly appreciated!

I'm trying to put together a MSI distribution package for ApplicationXtender Desktop 6.5 with retrieval only option.  It is a MSI install, and I have the command line as:

/i /quiet ADDLOCAL=DocumentManager /norestart

The installation files are stored on network storage.  I have double checked the path and it matches what I have set up in LANDESK.  I added the whole ApplicationXtender Desktop installation directory into "Additional files," minus the MSI itself.  Scheduled the task and ran it, but keep getting this error:

"One or more of the depend files could not be found."

Error code 16418.

I have tried resetting the package hash, and also tried starting over by deleting and re-creating the distribution package, but nothing seems to work.  What am I missing here?

Hello.

We are currently doing a side-by-side upgrade to upgrade from LD9.5 SP2 to LD9.6 SP1.

What is the best practice method for migrating queries, packages and tasks in that situation?

I've so far established the following:

* CORE sync will not work as both COREs are not on the same version

* Items can be exported manually to a .ldms file, but it fails to import on the LD9.6 CORE because the <AssemblyVer> value does not macth. It's possible to change the value to match the new CORE and then the import seems to be successful, but I can find multiple threads on the community that says this is not a supported method and you shouldn't do it - i.e. https://community.landesk.com/support/thread/23198

* The tool package.porter.exe can be used to export public packages to an .xml file, but the import fails on the LD9.6 CORE with the following error:

The following exception occurred while importing the distribution package : System.MissingMethodException: Method 'LANDesk.ManagementSuite.SoftwareDistribution.Business.Package.CategoryName' not found.

   at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)

   at LANDesk.ManagementSuite.SoftwareDistribution.Business.ImportExport.XmlPorterHelper.InitializeObjectFromXml(XmlNode node, Object instance, Type type, String[] properties, String[] required, IPorterProcessCallback callback)

   at LANDesk.ManagementSuite.SoftwareDistribution.Business.ImportExport.PackagePorter.ExtractPackage(String connectionString, XmlNode child, String serverName, Boolean bReplace, IPorterProcessCallback callback, Boolean publishing, BooleanrenameReplicatedPackages)

I can then manually remove the lines with "<CategoryName> </CategoryName>" in the xml file and then the package is imported without any errors being shown. Unfortunately I've found that an eventual prereq. query is not imported even though it's present in the xml file which means that the package is not correctly imported.

Please advise how we can successfully migrate the queries, packages and tasks that we need on the new CORE. Upgrading the old CORE to the same version as the new CORE so CORE sync. can be used is currently not an option.

Thanks in advance.

Note: I've asked LANDesk Support the same question, but with this thread I'm hoping to get some "real life experience" input on this situation as well.

I'm trying to install Microsoft UE-V agent v2.1 which requires a storage location to be defined which includes %username%. The storage location is a network share: \\server\share\%username% which must be a literal string and the %username% should not be expanded at installation time.

From the command line, it is installed using the ^ character:

AgentSetup.exe /quiet /norestart SettingsStoragePath=\\server\share\%^username%

Using a %^username% results in LANDesk trying to use a variable from the inventory record, which fails because it doesn't exist.

Using a double %% results in the variable being expanding in to the Username variable, which is the computer hostname as the job is run under the system account. This causes UE-V to use a single settings storage location for all users which is unwanted.

How can LANDesk be prevented from expanding the %username% ?

I have just created a distribution app for Autoroute 2010 and scheduled a task. Whenever I run this task the "LANDesk Global Scheduler application" starts to use a crazy amount of memory 4-5gb. If I end the SDCLIENT task on the device all is OK?

Weirdly on first created schedule task it ran but downloaded a complete random package and failed. I deleted the scheduled task and recreated and now its running but still eating up memory.

The download is 1.8GB and currently at 1.7GB so will see what happens when this specific task finishes but wondering if anyone has seen anything similar?

what are switchs key to i can push Microsoft project pro 2007, also if there any speculate configration   / i already prepare MSP File

Deploying adobe reader 11.10 multiple agents reporting Return Code 1110 Cannot Find Agent. Yet several agents are online and pingable. I can also force an inventory scan but not deploy anything.

Issue

When opening LANDESK Workspace a Security Alert message appears. If you view and install the Certificate the message still appears each time Workspace is opened.

Resolution

A Self-Signed Certificate needs to be created in IIS for the FQDN of your Core, associated with your Core's Default Web Site, and then pushed to the Client using Group Policy.

Creating a Self-Signed Certificate

• Open Internet Information Services (IIS) Manager
• In the Connections pane select your Core
• In the Features pane double click Server Certificates
  

• In the Server Certificates Actions pane select Create Self-Signed Certificate...

• Enter the Fully Qualified Domain Name (FQDN) of your Core in the Specify a Friendly name for the Certificate: (CoreName.Domain.com)

• Click OK

Export Certificate to your Group Policy Server

• In the Server Certificates pane select the certificate you created
  
• In the Server Certificates Actions pane select Export...

• Select the location of your Group Policy server in Export To: and give it a file name
• Enter a Password: and Confirm Password:
• Click OK
  

Apply Certificate to the Default Web Site on your Core

• In the Connections pane expand your Core
• In the Connections pane expand Sites
• In the Connections pane select Default Web Site
• In the Actions pane under Edit Site select Bindings...

• On Site Bindings click Add
• Under Type: select https
• In Host Name: type the FQDN of the Core (CoreName.Domain.com)
• Under SSL Certificate: select the certificate you created

• Click Select...
• Click OK (on Add Site Bindings)
• Click Close (on Site Bindings)

Create and Enforce Group Policy for your new Certificate

• Open Group Policy Management (Start > Run > type gpmc.msc)
  • Deploy Certificates by Using Group Policy
• Expand Forest: domain.com
• Expand Domains
• Right click your domain
• Select Create a GPO in this domain, and link it here...

• Name the new GPO and click OK
  • For consistency it can be named the same as your certificate CoreName.Domain.com
• Right Click the new Linked Group Policy Object and click Edit
• In the Group Policy Management Editor expand
  • Computer Configuration
  • Windows Settings
  • Security Settings
  • Public Key Policies
• Right click Trusted Root Certification Authorities
• Select Import

• On the Certificate Import Wizard
  • Click Next > on the first screen
  • Click Browse... to select the exported certificate file and click Next >
  • Enter the password created for this certificate and click Next >
  • Click Next > on the Certificate Store screen
  • Click Finish on the last screen
• In the Group Policy Management window
  • Right Click the new Linked Group Policy Object and click Enforce

Apply the new Group Policy on Client Devices

• The new Group Policy will be enforced on Client Devices
  • When the device is rebooted
  • When a background update is executed, the default is 90 minutes @(Group Policy refresh interval for computers)
  • When gpupdate /force is run (Refresh Group Policy settings with GPUpdate.exe)

Environment:

LDMS 9.6, 9.6 SP1

Review Date:

23.02.2015

Description:

After installing LDMS 9.6 or 9.6 SP1 can no longer install Preliminary or Final package, only Main is installed. Package itself was either created from scratch in 9.6 environment or was imported from 9.5 infrastructure, where it was working flawlessly, so what's changed in 9.6?

Observations:

- Package Order doesn't work

- Ignores the Preliminary packages and installs the main package only

- the packages involved in the task work individually though

Solution:

The reason why we see this issue is:

- Package Order (Preliminary/ Main/ Final) is a deprecated feature only available for Agent still running legacy 9.5 version

- 9.6 Agents are unable to use it

- With 9.6 we should be looking to use either Provisioning Template (it gives good results, plus user can control multiple software packages, installation order etc.) or go with Package Bundles. This is the direction Landesk is taking in the SWD component.

Environment:

LDMS 9.6

Problem:

After beginning task clients are stuck in an active state with a task status of "Client has initiated asynchronous policy execution", and never progresses.

Purpose:

This document is designed to help identify the point of failure that lead to the task hanging in the console, whether that was a problem with Core communication, or clients failing after receiving the task. As you go through the steps, when you identify the step in the process with the error you will shift into troubleshooting that particular step of the process as the following steps are dependent on the success of the preceding steps.

Cause:

While this status is NOT an error message, it simply means that the core tried to contact the device and told it to check in and grab the task that it needs to install. However, sometimes the machine does not respond that it received the task and does not run it, and since the core at this point is waiting on a response from the client machine it leaves the task in an active status. We need to look at the clients and find out why they did not get the task.

Troubleshooting Steps:

A. Core and Client Communication:

1. Check the PolicyTaskHandler.log on the core for errors. It should have discovered and sent the sync command to each client, if successful it should look like this. If there are errors there, investigate further.

11/24/2014 22:37:13 INFO  5936:1    RollingLog : [Task: Firefox 26++ - 10/29/2014 1:42:08 PM, TaskID: 2080, ProcID: 5936] : Discover: Discovering machine: [Client123] using it's known ip address [10.14.111.50]...

11/24/2014 22:37:15 INFO  5936:1    RollingLog : [Task: Firefox 26++ - 10/29/2014 1:42:08 PM, TaskID: 2080, ProcID: 5936] : Discover: Successfully discovered machine: [Client123]

11/24/2014 22:37:15 INFO  5936:1    RollingLog : [Task: Firefox 26++ - 10/29/2014 1:42:08 PM, TaskID: 2080, ProcID: 5936] : TargetMachineContainer.MachineTargetOS: Operating System is: [Microsoft Windows Server 2012 R2 Server Datacenter Edition (full installation), 64-bit] for machine: [Client123]

11/24/2014 22:37:15 INFO  5936:1    RollingLog : [Task: Firefox 26++ - 10/29/2014 1:42:08 PM, TaskID: 2080, ProcID: 5936] : SyncPolicyTask: Synchronizing policy with the command: [C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe -taskid=2080], to machine: [Client123]

    **On LDMS 9.6 the PolicyTaskHandler.log is located on the Core Server at \Program Files\LANDesk\ManagementSuite\Log\PolicyTaskhandler.log

2. Check the ServiceHost.log on the client machine to verify it received the command to synchronize and execute the task. If it was successful  you should see the following line in the log.

Mon, 24 Nov 2014 22:37:15 4856: Exec: Exec: Launch request <"C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe" -taskid=2080> (sync 0, timeout 2147483647)

    **In LDMS 9.6 without any Service Packs installed the ServiceHost.log file is located in the following locations:

          32-Bit Clients: C:\Windows\System32\ServiceHost.log

          64-Bit Clients: C:\Windows\SysWOW64\ServiceHost.log

    ***In LDMS 9.6 SP1 and later the ServiceHost.log is located at C:\Program Files (x86)\LANDesk\Shared Files\ServiceHost.log

B. PolicySync.exe

1. On the client machine look at the PolicySync.exe.log checking for any error messages. If it was successful you should see something similar to the following. If there are errors, investigate further. Note that HTTP errors will be placed in this log, you can double check the error code and match it to the error code in the IIS logs on the core server if present.

11/24/2014 22:37:18 INFO  244:1     RollingLog : Run PolicySync.exe -taskid=2080

11/24/2014 22:37:19 INFO  244:1     RollingLog : Request: Request policies

11/24/2014 22:37:20 INFO  244:1     RollingLog : Request: GetWebResponse ok

11/24/2014 22:37:20 INFO  244:1     RollingLog : Request: Has 1 targeted policies

11/24/2014 22:37:20 INFO  244:1     RollingLog : HandleRunNow: has 1 run now policies

11/24/2014 22:37:20 INFO  244:1     RollingLog : Exit PolicySync.exe with code 0

C. SDClient.exe and Vulscan.exe

1. Once the policies synchronize PolicySync.exe calls on SDClient.exe (Software Distribution) or Vulscan.exe (Patch Management) to execute the task. It is at this point that the core will finally receive its first update to the task status and will not longer show the "Client has initiated asynchronous policy execution" message. You can find the logs for SDClient and Vulscan.exe on the client machine, from there you can verify any errors.

C:\Program Files (x86)\LANDesk\LDClient\Data\SDClient.log

C:\Program Files (x86)\LANDesk\LDClient\Data\SDClient_task##.log

-OR-

C:\ProgramData\Vulscan\Vulscan.log

C:\ProgramData\Vulscan\Vulscan.1.log

C:\ProgramData\Vulscan\Vulscan.2.log

C:\ProgramData\Vulscan\Vulscan.3.log

Unfortunately there is not a one size fits all response to tasks get hung with that status. However, it is a fairly safe bet that if multiple machine in the same task got hung up, they got hung up for the same reason. So fixing the issue on one machine may fix it for the rest. However, as always if you have any questions, or get stuck during the troubleshooting process please contact LANDESK Support to assist in finding and resolving the problem.

Purpose

Method for remote unprovisioning of vPro clients, for troubleshooting and correcting issues that may require the client to be unprovisioned.

The Intel(R) AMT Unprovision Utility is a simple command line utility that allows users to remotely unprovision an Intel(R) AMT system without requiring a

separate management console.

Note: This test will make use of the free 3rd party application Intel Unprovision.exe. LANDESK does not endorse nor support any 3rd party software. Users assume all liability when working with 3rd party software.

Steps

1. Download the Intel UnprovisionEx.exe tool.
2. Unzip the files to your Software Distribution Storage.
3. In the Management Suite Console, create a new Software Distribution Executable package.
4. In the Package Information section use the UnprovisionEx.exe as the primary file.
5. In the Install/Uninstall Options section add the following switches into the install/uninstall options: -hostname %computername% -user admin -pass P@ssw0rd -full
   • For the password please use the admin password for your vPro machines .
   • The -hostname can be either the listed variable, FQDN or IP address.
6. Save the package and schedule it out to the vPro devices you would like to unprovision.
7. Once these machines are in the pre-provisioned state attempt to zero-touch provision these devices.

(To verify the provisioning state of the machine please reference https://community.landesk.com/support/docs/DOC-31903)

Hello,

I am new to LDMS, having the following problem:

Our enviroment is running LDMS 9.5, and Lync 2013 was rolled out to about 2000 clients.(Push-pull). Many of the clients are still getting the popup , even after the software was successfully installed, Any help is welcome.

Thank you very much!

DST

Sorry in advance if this is not the correct place for this.  If not point me in the right direction.  What is the best resource for detailed instructions on making a new build.  Thanks