Problem:

Scheduled tasks will not run when starting them.

Resolution:

Please follow the steps to restore the scheduler service:

1- Go to Start- Administrative Tools- Services
2- Right click on the LANDesk Scheduler Service, select Properties.
3- Go to the Log On tab, select Local System as the logon account.
4- Save and start the service.
5- In the Management Console, go to Configure- Services- Scheduler
6- Click on Change Login, reenter the account info for the Domain Admin account used for the Scheduler.
7- Restart the Service.

Affected versions: LDMS 9.x

Staging Files

LDMS 9.6

1. Schedule your Distribution Task.
2. Right Click on the task and select Properties.
3. Go to the Task Setting page, and select the following options.
   1. Task Type: Policy OR Policy Supported Push
   2. Download Options: Pre-cache
4. Save the task settings.
5. Add targets and run task.

LDMS 9.5

1. In the Management Suite Console go to: Tools - Distribution - Delivery Methods.
2. In the Delivery Methods tool, expand My Delivery Methods.
3. Right click on Policy, and select New Delivery Method.
4. On the Network Usage page of the settings, under "File Transfer/Source Download Options" select Pre-cache.
5. Other setting can be set as desired. Save the settings once complete.
6. Schedule the distribution package.
7. Right click the scheduled task, select Properties.
8. On the Delivery Method page, select Policy, and select your new Pre-cache method from the list of available delivery methods.
9. Save the task.
10. Add targets and run task.

Legacy Delivery Methods

When using the Management Gateway on Legacy versions of LDMS 9.0 and older, only Policy-based Delivery Methods can be used.  Such Delivery Methods do not allow for pre-staging a file but always run the primary file of the Distribution Package.

Workaround

In order to pre-stage a Distribution Package create a copy of the Distribution Package and move the current Primary File to be an additional file and replace the Primary File with a blank batch file.  Even though the Primary File will always run, it now does not matter because a blank batch will of course do nothing and will always run successfully.

This is also very useful to pre-stage files in environments where Multicast is either not desired or not functional.

• • Symptom
  • Cause
  • Solution

Symptom

Software Distribution task fails with the following results:

Result: The request is not supported.

Return Code: 50

On the client, the sdclient_task##.log shows:

Windows Script Hosts file can not run from source with a HTTP path.

RunPackageInstall: stop on returncode=80070032 of package=PXE Representative Deployment

processing of package is complete, result -2147024846 (0x80070032 - code 50)

Cause

Within the Scheduled Tasks properties, under Task Settings, Download Options is set to 'Run from Source (execute on share)', and the Packages Primary file is set to download HTTP. Certain packages such as Windows Script Host packages are unable to be 'ran from source' if the source is defined using a URL.

Solution

• Set the Scheduled Tasks' Download Options to Download and Execute.

- or -

• Change the file path to be UNC.

Hi,

As stated in the LANDesk Content Replication - Source Configuration document, "The Source representative will periodically check the files on the source, determine the hash and write that information to an XML file". Does anyone know how often this is? Periodically is quite vague...

Also:

- is there a way to modify it, like a registry key or something else?

- is there a way to clear this and force a full recalculation on the source representative?

Thanks in advance,

Patrick

Environment:

LDMS 9.0+

Question:

For security or monitoring reasons, you need to download the Packages on a specific port other than the default Http port 80 or Https port 443 from a preferred server.

How can I set that up?

Here is the setup details;

1- Source Server: Hostname "CORE95SP2" - where the data are stored (In this example; on the Core Server on http://CORE95SP2/landesk/files/TESTREP1/)

2- Preferred Server: Hostname "CORE95SP2RS"

3- IP Address range of Nodes concerned: 192.168.1.2 - 192.168.1.254

4- Port: 8093

• Configuration of the Port 8093 on the web server where files are stored:

ATTENTION: In this example, I used IIS 7 for the Web Server but it can be other system. The idea is to allow an access to a directory on the Web Server through a port (In this example, 8093)

a- Go on the Web Server, then open the IIS manager

b- Go on "Default Web Site", and be sure that "Directory Browsing" is installed on the Feature View in section "IIS" (Otherwise you may need to install this feature as a Role Service)

c- In the Actions pane (Right side), click on Bindings and a popup will open called "Site Bindings"

d- Click on the button "Add..." and choose the following;

• Type: http
• IP address: All Unassigned
• Port: 8093

d- Click on the button "OK", then "Close" (see below a printscreen of the configuration)

e- From an Internet Explorer, test if it works by typing the URL, in this example, http://CORE95SP2RS:8093/landesk/files/TESTREP1/

• Configuration of the Source Server:

a- Go on the LDMS Console > Tools > Distribution > Content replication / Preferred servers

b- On Content replication - Sources, click on New to create a new Source server configuration

c- On the tab "Configuration":

• Input the server name; In this example CORE95SP2
• Input the UNC or http path; In this example http://CORE95SP2/landesk/files/TESTREP1/
• Input the credentials in Connect as User; In this example sebdomain\administrator
• Click on the button "Test credentials" to be sure this account/password is correct

d- Click on the "Save" button to record your configuration (see below a printscreen of the configuration)

• Configuration of the Preferred Server CORE95SP2RS:

a- Go on the LDMS Console > Tools > Distribution > Content replication / Preferred servers

b- On Content replication - Preferred servers (Targets), click on New to create a new preferred server configuration

c- On the tab "Configuration",

• Input the server name; In this example CORE95SP2RS:8093
• Input the Read-Only credential; In this example sebdomain\administrator
• ATTENTION: Don't click on the button "Test credentials...", it won't work and it won't be a valid test. Just be sure that this account has read access to the folder concerned through http protocol on port 8093
  

d- On the tab "IP address ranges", input the IP address range concerned; In this example 192.168.1.2 - 192.168.1-254

e- On the tab "Sources", select the Source server; In this example CORE95SP2

f- Click on the "Save" button to record your configuration (see below a printscreen of the configuration)

Other Interesting link: How to: Deploy a Distribution Package on a different Http ports than 80/443 ports from a Preferred Server configured with a Replicator Server

Description

Resolution

Issue

• PolicySync.exe.log shows errors

Request: exception - The remote server returned an error: (503) Server Unavailable.
Request: failed get response from APMService.
Exit PolicySync.exe with code -3

• Task may be stuck with a status of "Client has initiated asynchronous policy execution"
• IIS log shows:

POST /ApmService/PolicyRequest.asmx - 80 - 127.0.0.1 - 503 2 0 62

Cause

This is a Microsoft IIS error indicating your environment has maxed out its allowed number of connections to IIS.

• 503.2 - Concurrent request limit exceeded.

Resolution

Note:  Because this deals with modifying configuration information for IIS, users assume all responsibility when implementing changes or modifications outlined in this information.

Increase the allowed number of concurrent requests in IIS as outlined by Microsoft in the article:

Click Start and then click Run.

In the Run dialog box, type notepad %systemroot%\Microsoft.Net\Framework64\v2.0.50727\CONFIG\machine.config, and then click OK.

Locate the processModel element that looks like this: <processModel autoConfig="true" />

Replace the processModel element with the following value: <processModel enable="true" requestQueueLimit="15000" />

Save and close the Machine.config file.

 

For Windows Server 2008, in the Run dialog box, type appcmd.exe set config /section:serverRuntime /appConcurrentRequestLimit:<#of users * 1.5>.

 

- Modifying the ASP.NET Request Queue Limit

Note: appcmd.exe is located at %systemroot%\system32\inetsrv\appcmd.exe. It may be necessary to change directories within the command window to successfully initiate this command.

Problems/Symptoms

The Intel Scheduler service is stopped. Attempts to start the service result in the following error:

Error 1069: The service did not start due to a logon failure

Cause

The username or password used to start the Intel Scheduler service is incorrect.

Solution

Open the properties of the LANDesk Scheduler Service in Windows Services, go to the Log On tab, and specify a valid username and password.

Purpose

This document provides a quick How-To for setting up replication. It will not go into details on all areas of this component, but rather gives a getting started style view at setting up replication.

For more information on Replication please see: Using LANDesk Content Replication

Setup Core Share

The point of replication is to get files off the core to a different preferred server. So to start we need a share that will be used to store the files we are going to replicate.

Note: In this doc I create a new share, but you could use any share such as ldlogon and it should be ok.

• On the Core create a new directory
  • C:\share
• Share the folder
  • I share mine to everyone with read/write permissions. It just makes it easier.
• You now have a share \\core\share
• Copy some files into the share folder to be replicated
  • Example: \\core\share\firefox.exe

Setup Client Share

Replication copies files from one share to the clients share of the same name. This means that any machine that will be replicated to must have a share setup of the same name as the source.

We previously created \\Core\Share, so the client must have one setup as \\Client\Share.

The physical location on the drive won't matter, so long as the naming convention is the same.

(i.e. C:\Share creates the same UNC share path as C:\Temp\Share. They both become \\client\share)

Add Preferred Servers

In Content Replication add a preferred server for:

• Core (this will be where files are replicated from originally)
• Client (this will be who gets the files in the end)

Add Sources

• In Content replication click Sources, and choose New Source.
• In the Source Properties window, fill out the Configuration section
  • Name:
    • This can be anything, it is a unique way to tell what the source is.
  • UNC or http path:
    • This needs to be the path to the share we originally setup
  • Connect as user
    • A user account that has rights to the share.

Configure Client Preferred Server

• In Content Replication, select Preferred Servers
• Double click the Client Preferred server to open it to edit
• Click Selected Replicator
• In the list of devices shown, pick the Replicator that will be in charge of copying files from the source to this Preferred Server.
• Click Select

• Next click Sources
• Select the Source we added earlier and choose Include
  • This defines that the client will receive the files from this source.
• Click Save

• Next click Write Credentials
• Provide credentials that will have write permissions to the share
  • Since we are copying to this machine, we write the files onto it. Only machines that will receive replicated files need the Write Credentials.
• Click Save

Start Replication

• In Content Replication click All Tasks | Not Scheduled
• There will be an entry showing the Source and Preferred server we just setup
• Right click this entry and choose Start Content Replication Now

• If everything was setup correctly, it should show as successful.

• Description
• Cause
• Troubleshooting

Description

When trying to deploy a software in a post 9.6 SP1 environment, we get the message: Client has initiated asynchronous policy execution and the task stays Active

Please note that there is a document for 9.6 without any patch: “Client has initiated asynchronous policy execution” – Return Code 1354

Cause

This error is usually caused by a program running in background on the client machine that prevents the deployment from working.

The common processes are the following:

• SDCLIENT.EXE
• vulscan.exe
• MSIExec.exe
• sdistbat.exe
• cmd.exe

In my case, I created a BATCH file that runs a ping -t but never exits which leads SDCLIENT to interprete that the installation is still running. This results in SDCLIENT not being able to run another process.

Troubleshooting

This one might be tricky to troubleshoot as there are no logs where you can see that the task cannot be processed because of another one. For that reason, we will need to go for another source of information.

Basically, what happens when a task is scheduled is that the Server makes it available via APM and ask the client to check if it is entitled to get it.

The client then goes to the APM web service and gives its information to see if a task is available for him.

The task is then downloaded as an XML file on the client in C:\ProgramData\LANDesk\Policies

It then goes to C:\ProgramData\LANDesk\Policies\RunNow in order to be processed and usually disappears instantly when the task starts.

Before that, no logs are being generated for this task because it did not start. That means that you should be able to find in C:\ProgramData\LANDesk\Policies\RunNow the task(s) that are blocked with their Task IDN which will help you identify which task has generated the problem.

In our case here is what I can see in this folder:

I will then go to the Core and check which task is the 5054 (as it is the one that has been started first at 08:39), the best is to right click on the device and choose Scheduled tasks and diagnostics:

Now that we have the faulty task, let’s check what it should do, trigger, etc. and where the problem might be, because it means that this task is not finished or blocked.

In my case, the script only does a ping -t but there is no exit which means I need to check on the client is one of the process is running, like the SDCLIENT, the sdist and/or the cmd.

I will then stop PING.EXE first, as it is the last one being triggered

1. SDCLIENT.EXE
2. sdist
3. CMD.EXE
4. PING.EXE

And I can see that CMD is being automatically closed, as SDCLIENT and sdist.

I can now go on the Core Server and see that the task failed, but also that the other task completed successfully:

On the client side, we can then check in C:\ProgramData\LANDesk\Policies\RunNow:

There you go, it is unblocked.

But there is still one thing, we need to change our ping -t script in order to have it not blocking the next distributions.

To do so, we need to understand that the task needs to finish at some point and report its status back to the Core. With a ping -t, it basically never ends until we close it. So I can simply change it to have a timeout of 10sc and an exit:

The task is now being processed, and after 10sc, the PING stops, and the script exits, letting other tasks being processed.

I'm having a strange issue with pushing out a MSI file for a new Flash Player update. It works on some PCs but not others. I checked the log files on the computers that are not taking the update but I'm not sure what it causing the problem. I have tried with the local account then my admin account but I'm still seeing the same results.

Here is the log file on a failed install:

Wed, 08 Jul 2015 17:32:48 ******* sdclient starting to process task *******

Wed, 08 Jul 2015 17:32:48 Task id to process: 3082

Wed, 08 Jul 2015 17:32:48 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.3082.RunNow._&#47ck75WgVIOSlp2nKyOttwU0ULLE=.xml"

Wed, 08 Jul 2015 17:32:48 File (\\10.50.0.67\msi$\Adobe\Flash Player\FP18ActiveX203.msi) is cached locally

Wed, 08 Jul 2015 17:32:48 The nostatus flag has NOT been set.

Wed, 08 Jul 2015 17:32:48 Core name '10.30.1.5' obtained from active task list

Wed, 08 Jul 2015 17:32:48 Sending task status, cmd line -coreandip=10.30.1.5 -taskid=3082 -retcode=229392444 "-ldap=CN=Denise Bell,OU=AAV,OU=Domain Users,DC=tmtech,DC=com"

Wed, 08 Jul 2015 17:32:48 About to call DownloadFiles (1 files) with these settings:

Wed, 08 Jul 2015 17:32:48 m_allowedBandwidthWAN: 50

Wed, 08 Jul 2015 17:32:48 m_allowedBandwidthLAN: 75

Wed, 08 Jul 2015 17:32:48 m_discardPeriodSeconds: 604800

Wed, 08 Jul 2015 17:32:48 m_preserveDirectoryStructure: 1

Wed, 08 Jul 2015 17:32:48 m_bUseWanBWForPush: 0

Wed, 08 Jul 2015 17:32:48 m_bSynchronize: 0

Wed, 08 Jul 2015 17:32:48 Allowed download methods(m_downloadControl):

Wed, 08 Jul 2015 17:32:48 PeerOneSource

Wed, 08 Jul 2015 17:32:48 Peer

Wed, 08 Jul 2015 17:32:48 Source

Wed, 08 Jul 2015 17:32:48 m_preferredServerControl: AttemptPreferredServer

Wed, 08 Jul 2015 17:32:50 The nostatus flag has NOT been set.

Wed, 08 Jul 2015 17:32:50 Core name '10.30.1.5' obtained from active task list

Wed, 08 Jul 2015 17:32:50 Sending task status, cmd line -coreandip=10.30.1.5 -taskid=3082 -retcode=229392444 "-message=100%"

Wed, 08 Jul 2015 17:32:51 The nostatus flag has NOT been set.

Wed, 08 Jul 2015 17:32:51 Core name '10.30.1.5' obtained from active task list

Wed, 08 Jul 2015 17:32:51 Sending task status, cmd line -coreandip=10.30.1.5 -taskid=3082 -retcode=229392258 "-ldap=CN=Denise Bell,OU=AAV,OU=Domain Users,DC=tmtech,DC=com"

Wed, 08 Jul 2015 17:32:53 ExpandEnvironmentVariables Result: /i /norestart /passive

Wed, 08 Jul 2015 17:32:53 MSI Client Thread

Wed, 08 Jul 2015 17:32:53 PackagePath:  [\\10.50.0.67\msi$\Adobe\Flash Player\FP18ActiveX203.msi]

Wed, 08 Jul 2015 17:32:53 Execute Msiexec.exe with command Line: "Msiexec.exe"  /norestart /passive /i "C:\Program Files (x86)\LANDesk\LDCLient\sdmcache\msi$\Adobe\Flash Player\FP18ActiveX203.msi" REBOOT=ReallySuppress

Wed, 08 Jul 2015 17:32:53 GetHighPrivilegeToken: GetTokenInformation return=1312

Wed, 08 Jul 2015 17:33:05 MSI result 8DB50643

Wed, 08 Jul 2015 17:33:05 RunPackageInstall: stop on returncode=8db50643 of package=Adobe Flash Player Active X 18.203

Wed, 08 Jul 2015 17:33:05 processing of package is complete, result -1917516221 (0x8db50643 - code 1603)

I'm trying to push a bat file through software distribution which imports a Reg key. I'm running into this error and can't quite figure it out. I am including a portion of the log file output. If I go into the sdmcache folder and run the bat file manually, the Reg key is successfully imported.

Here is a portion of the log file:

Wed, 08 Jul 2015 10:04:43 Core name 'mycoreservername' obtained from active task list

Wed, 08 Jul 2015 10:04:43 Sending task status, cmd line -coreandip=mycoreservername-taskid=357 -retcode=229392258 -pkgid=82

Wed, 08 Jul 2015 10:04:43 ExpandEnvironmentVariables Result:

Wed, 08 Jul 2015 10:04:43 Batch file Client Thread

Wed, 08 Jul 2015 10:04:43 PackagePath:  [\\mycoreservername\packages\bat\Lynctaskbar.bat]

Wed, 08 Jul 2015 10:04:58

Wed, 08 Jul 2015 10:04:58 Bat file output :  C:\Program Files (x86)\LANDesk\LDClient\sdmcache\packages\bat>call "Lynctaskbar.bat"    C:\Program Files (x86)\LANDesk\LDClient\sdmcache\packages\bat>reg.exe import "\\mycoreservername\Packages\registry_keys\lync_minimizetaskbar.reg"   C:\Program Files (x86)\LANDesk\LDClient\sdmcache\packages\bat>"C:\Program Files (x86)\LANDesk\LDClient\sdistbat.exe" /setbatchstatus=1 

Wed, 08 Jul 2015 10:04:58 Installation result 8DB50001

Wed, 08 Jul 2015 10:04:58 RunPackageInstall: stop on returncode=8db50001 of package=Lync_minimizetaskbar

Wed, 08 Jul 2015 10:04:58 processing of package is complete, result -1917517823 (0x8db50001 - code 1)

Does anyone have a clue about these error codes?

SDCLIENT.EXE supports the following command-line parameters:
sdclient.exe /p="" [/g=] [/All] [/R] [/N] [/An] [/Ac] [/Ab] [/fui] [/msi] [/exe] [/bat] [/wsh] [/ps1] [/bw=xxx] [/lan=xxx] [/wan=xxx] [/disableclientqueue] [/runasuser] [/timeout] [/L] [/F] [/O] [/dest=] [/timeout] [/msg=""]

Environment:

LDMS 9.6, SP1, SP2

Description:

If you use detection rule(s) for registry items in distribution packages to evaluate if a software is already installed or not and therefore should be installed you may notice that on 64-bit devices the detection rule is only evaluated against the 32-bit registry hive and not the 64-bit hive. In result 64-bit software cannot be successfully detected through the registry keys.

Solution:

The issue is the .dlls on the client are all 32-bit .dlls. When a 32-bit .dll looks in the HKLM\Software portion of the registry, it will always look in HKLM\Software\Wow6432Node, even if the user specifies HKLM\Software. Once we create the keys in the correct portion of the registry, the reg check on the client works correctly.

However we do know that while the client applications are running as 32-bit dlls, it is possible to access the x64/native registry. Information about getting around the registry redirection in 32-bit apps appears to be outlined here: https://msdn.microsoft.com/en-us/library/windows/desktop/aa384235%28v=vs.85%29.aspx"https://msdn.microsoft.com/en-us/library/windows/desktop/aa384235(v=vs.85).aspx.

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.

Purpose

This document outlines how to obtain SOAP request and response information. This can be useful when testing IIS Connection issues.

Programs Needed

This document will make use of Wireshark and WebService Studio.

Capture a SOAP Request/Response with Wireshark

• Install Wireshark on the client machine to test with
• Begin a trace of network traffic
• Perform the task that issues the SOAP request
  • Example: Run C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe to request policies for the client machine
• Stop the Wireshark capture
• Apply the filter: ip.addr == {core ip address} && http
  • This will show the Post to the Core, and the Response from the Core.

Full Request URI

• In the Wireshark Trace, select the line that lists the Source as the Core's IP
• Expand Hypertext Transfer Protocol
• The Full request URIwill be the the address we are trying to reach for the test
  • Example: PolicySync calls http://96-core3.evdomain.local/ApmService/PolicyRequest.asmx

Requested Application

• In the Wireshark Trace, select the line that lists the Source as the Core's IP
• Expand the eXtensible Markup Language | <soap:Envelope | <soap:Body> |
• The value listed below the <soap:Bodyis the specific application that was requested
  • Example: PolicySync.exe called for RequestClientPolicies

SOAP Request Parameters

• In the Wireshark Trace, select the line that lists the Source as the Core's IP
• Expand the eXtensible Markup Language | <soap:Envelope | <soap:Body> |
• Below the Requested Applicationare the SOAP Request Parametersthat were used
  • Example: PolicySync.exe passed parameter values for
    • nonce
    • inventoryId
    • ldapUser
    • ldapUserGroups
    • ldapMachine
    • ldapMachineGroups

• Right click the Requested Application and choose Copy | Bytes | Printable Text Only
  • This will give a plain text copy of the xml that includes the SOAP Request Parameters

<RequestClientPolicies xmlns="http://tempuri.org/">      <nonce>3buvLh8LDbMFL+BFL32/fw==</nonce>      <inventoryId>{fe495d5d-404a-234c-9cab-697f258e8db7}</inventoryId>      <ldapUser>CN=Nevans,CN=Users,DC=evdomain,DC=local</ldapUser>      <ldapUserGroups>        <string>CN=Domain Admins,CN=Users,DC=evdomain,DC=local</string>        <string>CN=Denied RODC Password Replication Group,CN=Users,DC=evdomain,DC=local</string>        <string>CN=Administrators,CN=Builtin,DC=evdomain,DC=local</string>        <string>CN=Enterprise Admins,CN=Users,DC=evdomain,DC=local</string>        <string>CN=Users,CN=Builtin,DC=evdomain,DC=local</string>        <string>CN=Administrators,CN=Builtin,DC=evdomain,DC=local</string>        <string>CN=Domain Users,CN=Users,DC=evdomain,DC=local</string>      </ldapUserGroups>      <ldapMachine>CN=96-AGENT,CN=Computers,DC=evdomain,DC=local</ldapMachine>      <ldapMachineGroups>        <string>CN=Domain Computers,CN=Users,DC=evdomain,DC=local</string>      </ldapMachineGroups>    </RequestClientPolicies>

SOAP Response

• In the Wireshark Trace, select the line that lists the Source as the Client'sIP
• Expand the eXtensible Markup Language | <soap:Envelope | <soap:Body>
  
• The Requested Application will be listed with response information beneath it
  • Example: PolicySync.exe requested 'RequestClientPolicies'

Testing SOAP Requests with WebService Studio

WebService Studio requires .Net 2 and 3. You may be prompted to install this if running on Windows 8 or newer.

• Launch WebServiceStudio.exe
• In the WSDL EndPoint field, enter the Full Request URI

• Click Get
• The form will display Messages about the connection
• Once connected, under the Invoke tab, there will be a list of returned Applications

• Select the Requested Applicationto test
  • Example: When running PolicyRequest.exe, it sent a request to RequestClientPolicies

• In the Input section, beneath 'Body', are the SOAP Request Parameter fields
• Select a variable and enter the Value
  • Example: In our Wireshark trace, we listed the nonce Parameter as:<nonce>3buvLh8LDbMFL+BFL32/fw==</nonce>

Note: The ldapUserGroups Parameter showed in wireshark as including multiple records. Selecting this Parameter and changing the Length value will provide additional fields.

• Once the Parameter values are filled out, click Invoke
• The Output section will contain the SOAP Response

Note: The Request/Response tab lists the SOAP information in XML that can be copy/pasted.

I have a problem with the "Packages sync", out of nowhereIstartedto failthis task and start to say this when the thask end it:

In the file Policy.sync.log say:

Mon, 13 Jul 2015 16:19:53 Checking if we have a valid local database file before attemp to start policy.sync.exe

Mon, 13 Jul 2015 16:19:53 [START] Policy synchronization started.

Mon, 13 Jul 2015 16:19:54 Get ldap info from cache since failed to contact ldap server.

Mon, 13 Jul 2015 16:19:54 Sending policy request to core server.

Mon, 13 Jul 2015 16:19:54 Requesting policy for {D2719161-F521-9F4B-990C-04B21259E668}, user ITAUCHILE\CCGS5425, ldap user CN=Gomez Stamulis\, Carla Constanza CCGS5425,OU=Chile BKB,OU=Accounts,OU=BAND,DC=Itauchile,DC=cl, ladp machine

Mon, 13 Jul 2015 16:19:55 Web request returned 0 The web request was successful.

Mon, 13 Jul 2015 16:19:55 No policy downloaded from core

Mon, 13 Jul 2015 16:19:55 Processing new and updated remote operations

Mon, 13 Jul 2015 16:19:55    In LoadNewAndUpdatedOperations

Mon, 13 Jul 2015 16:19:55    Out LoadNewAndUpdatedOperations

Mon, 13 Jul 2015 16:19:55    In ConvertDataTable

Mon, 13 Jul 2015 16:19:55    Out ConvertDataTable

Mon, 13 Jul 2015 16:19:55    In RemoteOperationDownload::Download

Mon, 13 Jul 2015 16:19:55    Out RemoteOperationDownload::Download

Mon, 13 Jul 2015 16:19:55    In PolicyResponseData::ProcessExecuteOperations

Mon, 13 Jul 2015 16:19:55    Out PolicyResponseData::ProcessExecuteOperations

Mon, 13 Jul 2015 16:19:55 Processing deleted remote operations

Mon, 13 Jul 2015 16:19:55    In ConvertDataTable

Mon, 13 Jul 2015 16:19:55    Out ConvertDataTable

Mon, 13 Jul 2015 16:19:55    In WriteServerResponse

Mon, 13 Jul 2015 16:19:55    Out WriteServerResponse

Mon, 13 Jul 2015 16:19:55 Policy request has been processed.

Mon, 13 Jul 2015 16:19:55 Checking for rescheduled policies

Mon, 13 Jul 2015 16:19:55 [STOP] Policy Synchronization application complete.

I have no idea what could be wrong, i didn't make any changes at all and it worked beforeand now it doesn't.

I have 9.50.3.1 version, service pack 2.

Thanks you for your help!! :/

LDMS 9.6 SP2

As soon as I try to create or edit a new Distribution Package I get the error.

I went out on vacations and I had to change my AD password due to AD policy, would this affect LDMS some how? Any ideas what to look for?

Thank you.

Using LDMS 9.6 SP2

Connected via CSA

What is  the difference between these 2 options?

In Task Settings you can set the frequency:

And you can also set the schedule in Schedule Task:

What is the difference?

I need to run this task asap and keep trying if it fails.

Thank you.

I understand in 9.6 I understand Multicast Domain Representatives are no longer used.

My understanding of their use was A. WOL would be sent to computers from there. B. Patches would be sent there then to computers and the same for software.

So how do these things above function now?