Environment:

LDMS - All Versions

Description:

When deploying a package through a policy, some of your clients may return an Error Code 16385 (i.e: "IDS_SDCD_INSTALL_SUCCESSFUL" according to the documentation here). As you may notice on your clients concerned by this Error Code, it doesn't necessarily mean that it was indeed installed succesfully but it may also mean that.

Cause:

1- If policy was required and run once in the configuration and it's already deployed before, sdclient_task***.log (On the client,look at C:\Program Files\LANDesk\LDClient\data\)

will contain the information as below:

                         The package {Package-***} was deployed by another policy.

Then, the error 16385 may be returned because the package has already been installed on the client for some reasons, or at least something makes it believe so.

2- It may also be due to 2 tasks running at the same time and try to install it which may cause this error message.

Solution:

1- Create a new task to deploy again the package with the option in the "Schedule Task" pane; "Deploy packages in this task even if they were previously deployed" and try again

2- Restart the client(s) concerned in order to close any other task(s) which may block the deployment of the package and try again

Applies to LANDesk Management Suite 9 SP2 and greater

LANDesk Content Replication can be used to keep files updated and current throughout an enterprise. The process uses a LANDesk managed node assigned as a Replicator to move files from configured Sources to target Preferred servers. There are several steps in the process and LANDesk uses existing agent functionality and tools to perform the replication.

For more information on Content Replication and Preferred servers see : Using LANDesk Content Replication

Creating the File List

The first step in a replication task is started is creating the file list. The Replicator will start with a Source and replicate it to all assigned Preferred servers. The Replicator will first compare the files and hashes that are on the Source with the ones that are already on the Preferred server. Any files that are missing or where the hash doesn't match will be replicated to the Preferred server.

The manifest of files is only created every 30 minutes.

The replicator.log will show the following to indicate if it recreated the manifest or not:

  "Manifest file is old or missing so will be re-generated"

or

  "Manifest file will NOT be regenerated."

Download the Files

Once the Replicator has identified the files that need to be replicated to the Preferred server, it will download the files needed to the cache on the Replicator. This will be located in C:\Program Files\LANDesk\LDClient\SDMCache. The download will use the bandwidth throttling settings configured in the Replicator settings. All files that are downloaded will remain in the cache of the Replicator for a period of time. This time can be configured as part of the Replicator settings.

Push the Files to the Preferred server

The Replicator will next use the write credentials configured in the Preferred server settings to write the files to the Preferred server. The Preferred server must have a UNC share in order for the Replicator to write to it. The Preferred server can also deliver files to clients via HTTP, but UNC must be available for replication to work. For each files that is copied to the Preferred server the Replicator will write a hash file. The file contains details about the file including the hash. This file is written to a custom directory named LDHashDir that is created in each folder and sub-folder. The LDHashDir will contain a special hash file for each file that was written to the Preferred server by the Replicator.

Ending the Job

If the Replicator is configured to continue until the job is complete, it will copy all the files needed to a Preferred server, then move on to the next Preferred server assigned to the same Source. The Replicator will download any additional files needed for the subsequent Preferred servers. Once the first Source has been replicated to all assigned Preferred servers the Replicator will move on to the next Source.

If the job is configured to end after a certain amount of time, it will stop when the set time is reached. The time starts when the job starts. For example, a job is set to start at 8:00 PM and run for 4 hours. If the job drifts a little and starts at 8:30 PM, it will not end until 12:30. When the job reaches the maximum time period it will stop replication right where it is. If it is in the middle of a file, the partial file will remain on the Replicator.

Resuming a Job

There are a variety of reasons that a job may be interrupted or stopped before it is complete. It could have been manually stopped by the administrator, maxed out the allowed duration, or the Source, Preferred server or Replicator could lose power or network connectivity. LANDesk will resume the replication at or near where it left of the next time the replication job runs. Exactly where the job will resume depends on why the job stopped.

Manually Stopped

If the job was manually stopped by the administrator selecting Disable task in the LANDesk console, the job will resume right on the file that it stopped on

Ran Out of Time

If the job was stopped because it got to the maximum allowed duration, the job will resume right on the file where the job stopped.

Preferred server or Source Becomes Unavailable

The Replicator will update the core with the most current status and resume within a few files of where it stopped.

Replicator Becomes Unavailable

The Replicator frequently checks in with the Core server and sets a checkpoint every 200 files. If the Replicator loses power or crashes, the next replication job will resume at the most recent checkpoint that was sent to the Core server. For example, a Replicator gets to file 200 and sends a checkpoint to the core. Then it gets to file 375 and the power goes out. The next time the job runs, it will resume at file 201.

For more information on Content Replication and Preferred servers see:

Using LANDesk Content Replication

Issue:

How to change the time that files remain in the SDMCACHE directory.

The SDMCACHE directory is where LANDesk products store files that were downloaded during Software Distribution or Patching tasks. By default, this folder is purged every 7 days on normal agents and every 14 days on subnet representative agents.

Solution:

1. Change the following registry values on the client:

32bit

HKLM\Software\Intel\LANDesk\LDWM\Distribution\Multicast\Discard Period

HKLM\Software\Intel\LANDesk\LDWM\Distribution\Multicast\Subnet Rep Discard Period

64bit

HKLM\Software\Wow6432Node\Intel\LANDesk\LDWM\Distribution\Multicast\Discard Period

HKLM\Software\Wow6432Node\Intel\LANDesk\LDWM\Distribution\Multicast\Subnet Rep Discard Period

Defaullt Data for Discard Period is set to (604800) in seconds = 7 days

Defaullt Data for Subnet Rep Discard Period is set to (1209600) in seconds = 14 days

Increase the data value in seconds.

Note: When updating the registry, this will update the *.info files located in ldcacheinfo directory for the discard date.

2. Restart the LANDesk Targeted Multicast service on the client.

Note: This does not change the time for files that are already in the SDMCACHE directory. To change the time for existing files in Management Suite 9.0 SP2 or higher, delete the LDCACHEINFO subfolder from each directory containing files needing the longer discard period before restarting the service.

To verify that the files have been cached the intended amount of time, run "TMCsvc.exe /F|more" from a command prompt in the \LDClient directory. This command will output cached files "time to live" values to screen.

Greetings everyone, We just started using Landesk.  I am starting with software distribution, is there a master list of return codes anywhere for Scheduled Tasks?  I know I can just search for them here and it's been a big help so far, I was just looking for an easier method.  Thanks for the help.

Hi all,

If I request a prompt before running the package and a result status to be displayed to the user, the package name is shown, instead of the description. Is that normal?

I would expect the package description to be shown to the user, rather than the name. As stated in the package properties, the description field's title says : "Description to show to end users on download".

Am I doing/understanding something wrong?

Patrick

LANDesk Management Suite 9.50 Service Pack 2

There are no error messages, the files just aren't available to add.

I also have a support ticket - https://support.landesk.com/ViewCase.aspx?Case=5001300000kDT4jAAG

Has anyone gotten it to run?

I'm attempting a silent installtion of lotus 8.5.3 using the Executable and the following commandlines.

/S/V"SETMULTIUSER=1 ADDFEATURES=ClientSingleLogon /QB"

This action never executes though, it hangs and just sits in the active state not firing off on the PC.

On LANDesk 9.5 SP1, users are unable to right-click under Scheduled Tasks > My tasks and click "Create Software Distribution task.."

The options are all grayed out.  If they click directly on a Distribution package and click "Create scheduled task" It will work fine.

Is there another role or did this behavior change in LANDesk 9.5 SP1?  LANDesk Administrators can still do this but not other roles in LANDesk.

The users in question have all the rights to Software distribution in their Role.

HI,

I have created a package that uses a pre-requisite query to detect if the device has IE 10 installed. The package is still installing even though the device is identified in the pre-req query? Is there a log file that records if the prereq filter was passed?

Regards

Andrew

The current environment is LANDesk 9.5 SP2

The issue is there's 40 PCs which i'm pushing Power Management Policy out to

30 of these succeeded but 10 remained as active

Of those remaining as active the Result was either "Machine Successfully Discovered" or "Cannot find agent"

I restarted the Scheduling Service so I could delete and re-run the task which returned the same issue for those 10 PCs

To test that they were receiving commands from LANDesk I deployed a piece of software to the PCs which went through seamlessly

Thinking there might be an overlap of an existing policy I created the scheduled task to remove power management policies, but again those 10 PCs got stuck in active with the same result codes

Any advice or ideas?

We are running Management Suite 9.50.2.6 and intermittently get a intermittent error of "the machine failed the prerequisite query" on policy supported push software deployments. These deployments do not have prerequisites. If we wait long enough most will eventually successfully run. I've been trying to identify a cause but as of yet have not been able to. I have run both security and inventory scans as well as rebooted and deleted the local workstation DB. Nothing has consistently resolved the issue. I've not been able to recreate at will. There is no task log created when this error is seen. Any suggestions about a cause or how to troubleshoot would be appreciated.

We would like to stream some videos at remote locations. Trying to figure out if the videos can be replicated to preferred servers so the remote sites are not pulling from source each time a video is streamed.

I am deploying a Package (Batch) that shows on some System (Done 0) and others (Done 16385).

All Systems with Code 16385 dont have the Batch Package installed, instead the Logfile shows

that the package was deployed by another policy.

Ok, I know that I maybe started another Task before, but I canceled the Task and deleted it, before I made

a new Task, but I stopped that task, also because I noticed 16385 on some systems and no install.

Anyone has an Idea what is going wrong and where can I look or better delete the other Policy?

At the moment I can't found another task with that package.

Logfile:

Thu, 04 Nov 2010 08:19:50   Status 229392385: Starting task, if nothing goes wrong we will treat this as successful.
Thu, 04 Nov 2010 08:19:50   Setting the active operation to SDClientTask.KXXX7.1652.xml
Thu, 04 Nov 2010 08:19:50   + begin Task.KXXX7.1652
Thu, 04 Nov 2010 08:19:50     + begin DeliveryMethod.KXXX7.10
Thu, 04 Nov 2010 08:19:50       + begin Policy.Required.PortalRemoval
Thu, 04 Nov 2010 08:19:50       - end
Thu, 04 Nov 2010 08:19:50     - end
Thu, 04 Nov 2010 08:19:50     + begin SWD.ExecuteOnly.Proxy.59
Thu, 04 Nov 2010 08:19:50       + begin SWD.MultipleTaskProtection.KXXX7.1652
Thu, 04 Nov 2010 08:19:50         The package {Package-59} was deployed by another policy.
Thu, 04 Nov 2010 08:19:51       - end
Thu, 04 Nov 2010 08:19:51     - end
Thu, 04 Nov 2010 08:19:51   - end
Thu, 04 Nov 2010 08:19:51   Reporting complete status of 229392385 for task 1652.
Thu, 04 Nov 2010 08:19:54 Core name 'KXXX7:1XX.1X.237.28' obtained from active task list
Thu, 04 Nov 2010 08:19:54 Sending task status, cmd line -coreandip=KXXX7:1XX.1X.237.28 -taskid=1652 -retcode=229392385 -complete "-ldap=CN=Usern Nicole,OU=Users,OU=NASA1,DC=kdomain,DC=group,DC=local"
Thu, 04 Nov 2010 08:19:54   SDClient task complete
Thu, 04 Nov 2010 08:19:54 - end
Thu, 04 Nov 2010 08:19:54 [STOP]
Thu, 04 Nov 2010 08:19:54 ProcessInvokerStateRecords() received status complete.

Kind Regards

Troga

PS: I am also noticing that some (other) Batch Tasks stays some times on Active but are successful done, this happens before

Landesk 9 SP1 Agent but those clienst already have v9 SP1 Agent!

Is there a default setting for what sdclient uses as its default delivery method?  I am seeing some machines, when we are doing a profile migration, the sdclient will indicate have this in the sdclient.log:  "Mon, 07 Jul 2014 21:25:48 ParseCommandLine: No user logged in and fail operation".  If a user is logged in, the operation will proceed correctly.  I have tested this with just a single command in a script to download a file with the same result.  The capture profile command is ,"<qt/>C:\Program Files (x86)\LANDesk\LDClient\sdclient.exe<qt/> /f /o /p="http://10.3.100.55/ldlogon/LaunchProcessAsUser.exe" /disableclientqueue, STATUS ".  If that matters at all.   I am running 9.5 SP 2 with LD95-CP_BASE-2014-0417 installed.   Any thoughts?  Thanks

Can someone jog my memory - there was a way you can view the sdclient command for a package in LANDesk - I think it was directly in the database?

You search by package ID and it shows the exact sdclient path that was executed on the machine when the package ran?

I am unsure if was in the DB or the registry -

We are unable to send out this package to a test system, any thoughts?  We are running LDMS 9.5 SP2.  It does connect, download one of the packages and starts download the other, I can see an '@@partial@@_' being created, its size grows, but after about a minute, the task fails and the partial downloaded file is left in the sdmcache folder on the client. 

Here is the sdclient_task.log excerpt form the client,

Thu, 10 Jul 2014 10:49:48 About to call DownloadFiles (1 files) with these settings:

Thu, 10 Jul 2014 10:49:48 m_allowedBandwidthWAN: 25

Thu, 10 Jul 2014 10:49:48 m_allowedBandwidthLAN: 75

Thu, 10 Jul 2014 10:49:48 m_maxDiscoveryThreads: 15

Thu, 10 Jul 2014 10:49:48 m_discardPeriodSeconds: 604800

Thu, 10 Jul 2014 10:49:48 m_preserveDirectoryStructure: 1

Thu, 10 Jul 2014 10:49:48 m_bUseWanBWForPush: 0

Thu, 10 Jul 2014 10:49:48 m_bSynchronize: 0

Thu, 10 Jul 2014 10:49:48 m_downloadControl: SourceOnly

Thu, 10 Jul 2014 10:49:48 m_preferredServerControl: NoPreferredServer

Thu, 10 Jul 2014 10:49:52 processing package 'DSM Agent 9.0.03500 i386' 1 of 3 total packages

Thu, 10 Jul 2014 10:49:52 ExpandEnvironmentVariables Result: /i /quiet /norestart ADDDEFAULT=FirewallDPI,AntiMalware,DsaConfigFeature,NotifierApplication,MainApplication

Thu, 10 Jul 2014 10:49:52 File (\\ldmscore01\files\Agent-Windows-9.0.0-3500.i386.msi) is not in cache

Thu, 10 Jul 2014 10:49:52 About to call DownloadFiles (1 files) with these settings:

Thu, 10 Jul 2014 10:49:52 m_allowedBandwidthWAN: 25

Thu, 10 Jul 2014 10:49:52 m_allowedBandwidthLAN: 75

Thu, 10 Jul 2014 10:49:52 m_maxDiscoveryThreads: 15

Thu, 10 Jul 2014 10:49:52 m_discardPeriodSeconds: 604800

Thu, 10 Jul 2014 10:49:52 m_preserveDirectoryStructure: 1

Thu, 10 Jul 2014 10:49:52 m_bUseWanBWForPush: 0

Thu, 10 Jul 2014 10:49:52 m_bSynchronize: 0

Thu, 10 Jul 2014 10:49:52 m_downloadControl: AttemptPeer

Thu, 10 Jul 2014 10:49:52 m_preferredServerControl: NoPreferredServer

Thu, 10 Jul 2014 10:50:11 SAD -1: Failed to send message (type 44, length 20) over socket.

Thu, 10 Jul 2014 10:50:15 SAD -1: Failed to send message (type 44, length 20) over socket.

Thu, 10 Jul 2014 10:50:19 SAD -1: Failed to send message (type 44, length 20) over socket.

Thu, 10 Jul 2014 10:50:22 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)

Thu, 10 Jul 2014 10:50:22 An error (-1918107543) occured installing package DSM Agent 9.0.03500 i386

Thu, 10 Jul 2014 10:50:22 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)

Any thoughts?

I have AdminStudio 10 with SP2 installed and am having doubts whether this will work with Windows 7.

On a clean Windows 7 system (no virus protection Landesk or such) I copied our installer for Visio 2007 Professional down from our server

Launched AdminStudio (as Administrator)  and selected Migrate to Windows Installer

Clicked on Repackage using Repackaging Wizard

AdminStudio created a folder with lots of files and 2 msi files.

I uninstalled Visio from this system and rebooted

Attempted to install using the newly built MSI by"

Double clicked on the new MSI and got an error "Error 1606. Could not access the network location %ProgramFiles%\DVD Maker.  Retry / Cancel.

Needless to say the installer fails.

I must be missing some steps here.

I am having a problem with a particular shortcut in the LaunchPad. I have a deployment package which works fine. I create a LaunchPad link with all of the required fields filled out. I schedule the link and the software installs fine, but when I click on the shortcut in the LaunchPad I get an error:

LANDesk Launchpad Error (shortcut.runner)

CreateProcess failed to launch executable; contact your network administrator.

Now, if I manually create a shortcut on the desktop with the exact same options specified in the Launchpad Link Manager, the program opens fine. This is not a problem with the distribution package.

I did a quick test and had the Launchpad link set to deploy the shortcut to both the Launchpad and the Desktop. Both links failed! I checked the properties of the failed link that LANDesk deployed to the desktop and the "Target" of the link has an error in it. The error is from the "Command Line Arguments" section of the Link Properties in Link Management. I have specified:

-Djava.ext.dirs=lib;lib\web -jar UpdateClient.jar

And the resultant desktop shortcut has:

CreateShortcut.LDMS9.1765.69.69

I have attached screenshots of the salient error messages.

So it looks like LANDesk is not building the shortcuts properly. Any ideas?

HI,

I am currently using LanDesk Administrator version 9.50.3.1.

I am trying to create LaunchPad items in link manager, in particular, using the custom icon feature. I am not able to choose an icon file. I just get the red exclamation symbol and a message stating the following:

The link cannot be saved because the data is invalid. An icon file (with an .ico extension) must be chose if the icon type is 'Custom'.

Any one else had this problem?

Creating LaunchPad links using the default icon option works fine.

Many thanks

Paul

Problem:

User deferral in the delivery method does not work correctly. It seems to take on a life of it's own.

Solution:

1) Remove the machine from the task

2) Run a policy sync on the machine in question.

This will typically do it for you. If for some reason it does not, this indicates an issue with the ClientDB, it should be purged using the PurgeClientDB.ini against the machine.