So we are looking to eliminate traffic going and coming from our Landesk core server as much as possible. We currently have 6 remote sites and each site has their own preferred server. Can someone help me understand how we can eliminate traffic going/coming from our Core server to our end users.
Any help would greatly be appreciated.
It is possible to display a custom message once during the initial install on a bundle distribution, reboot then start the second software install with no message coming up?
The problem I'm having is the custom message comes up a 2nd time upon the reboot to install the second software installation of the bundle, but truncated with not showing the full message with the snooze, delay buttons unless you drag the cornor of the message to make it full screen I have look at every setting, but there does not seem to be an option to only display the custom message on the first part software install of the bundle if there is a reboot between software installs.
Hi
Is it possible to schedule the deployment of an application to begin when the user shuts down Windows (i.e. the user clicks Shutdown and then the install begins)?
Thanks.
Hello,
Has anyone removed the Kaseya agent from PC's with Ivanti? If so do you have any scripts??
Thanks
Jim Petruzella
2017.3
CSA
When scheduling a task AND there is a maintenance window (ex SUNDAY) the task will show as Successful (the next time policy sync runs) the thing is that the task has not run yet. Can this be changed to show the real status of the task: Scheduled to run on Maintenance Window?
Also, is there a way to remove the "LANDESK active notification" message when the task runs?
-Best
When you have scheduled a Software Distribution or a Patch repair task you can specify which reboot settings you would like the clients' machines to use to fit your needs.
**If you have already started the task, you will need to restart the task for the change to take effect. Any machines that receive the task after that will use the newly assigned setting.
Let's review the Reboot Settings options and features.
Whichever setting is applied to the agent as its default will update automatically whenever vulscan.exe runs (Once per day by default).
Targeting machines through Active Directory is a very useful and convenient way to manage software deployments.
Ivanti EPM Software Distribution allows you to target an LDAP container or LDAP group.
This document outlines the steps that you need to complete to get this working.
1. Enable LDAP enumeration on the agents
The LDAP Enumeration registry setting instructs the agent to gather the current LDAP location and report this in the inventory of the machine.
The registry key which controls LDAP group enumeration behavior for Software Distribution is:
HKLM\Software\LANDesk\ManagementSuite\WinClient
DWORD: DisableLdapGroupEnumeration
0(default) - feature is disabled
1 - feature is enabled
To make this configuration a permanent part of the default Agent configuration, do the following.
Browse to the LDLOGON share on the core server. Open the ntstacfg.in# file with notepad.exe. Search for ldap, which should take you to this section:
; LDAP groups can be enumerated on the client, this provides more information in the inventory ; database and faster targeting of LDAP groups. This also generates network traffic between the ; client and the LDAP server, the following registry value can be used to disable this option REG54=HKEY_LOCAL_MACHINE, SOFTWARE\LANDesk\ManagementSuite\WinClient\DisableLdapGroupEnumeration, 0, , REG_DWORD
The default value is 0 which is Disabled. Change this to 1, and save the file.
On the Ivanti EPM Core server, go to Configure | Services | Inventory and restart the Inventory Service. This will run stamper.exe, which builds the ntstacfg.ini file from the ntstacfg.in# file.
Next, in the Ivanti EPM Console, go to Tools | Configuration | Agent Configuration and click the "Rebuild All" button. This will rebuild the Agent_Name.ini file from the ntstacfg.in# file.
After doing this all of the Ivanti EPM Windows Agents will have LDAP enumeration enabled when the agent is installed.
2. Configure the Directory Manager plugin
In the Ivanti EPM Console, go to Tools | Distribution | Directory Manager. Click the Key icon, and then the Add button. Enter the credentials of a domain administrator or a user that can browse the domain.
After successfully authenticating to the Active Directory domain, the domain structure should be browsable.
3.Create the scheduled task that will target the LDAP objects. For this example, the scheduled task is a Required Policy.
Save the policy after adding the software package and the delivery method.
Note: At this point, the policy has no targeted devices.
4.To target the LDAP group or Active Directory OU, from Directory Manager drag the group or OU down onto the scheduled task.
Browse to the desired OU in Directory Manager and highlight it.
Drag and drop the OU to the Scheduled Task that was created.
The following window will come up, prompting for the kind of LDAP objects to find. Depending on the type of query and what is going to be targeted (users or machines), this will change. For this example, both types are selected.
Another window will come up to save the query. The query must be saved.
After saving the query, the LDAP OU will be targeted in the scheduled task. To see the LDAP target, see the scheduled task under Target Devices.
Hi,
As part of our migration to LANDesk 2017 (10.1.30.401), we have upgraded over 1000 agents from 2016 and/or 9.6.
Unfortunately, all upgraded clients have lost the ability to install any software distributions.
Clients that are still running 9.6 or 2016 do not show these problems. Also, 2017 agents that were installed from scratch (no upgrade) are working fine.
The only workaround I have found is manually uninstalling the agent and reinstalling it - which is realy not an option considering the number of clients.
The behavior is identical for all upgraded 2017 clients:
Example parts from 2 sdclient_task####.log files (one VBS script and one EXE file):
...
Mon, 19 Feb 2018 18:31:20 ExpandEnvironmentVariables Result:
Mon, 19 Feb 2018 18:31:20 MakeHTTPRequest: POST: http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx
Mon, 19 Feb 2018 18:31:22 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:25 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:27 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:29 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:31 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:34 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:36 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:38 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:41 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:43 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 18:31:44 ERROR: Failed to submit to decrypt string
Mon, 19 Feb 2018 18:31:44 An error occured launching sdistscript (-1918107541)
Mon, 19 Feb 2018 18:31:44 Windows Script Output:
Mon, 19 Feb 2018 18:31:44
Mon, 19 Feb 2018 18:31:44 RunPackageInstall: stop on returncode=8dac4002 of package=<PackageName>
Mon, 19 Feb 2018 18:31:44 processing of package is complete, result -1918091262 (0x8dac4002 - code 16386)
...
...
Mon, 19 Feb 2018 21:39:15 Processing generic executable
Mon, 19 Feb 2018 21:39:15 MakeHTTPRequest: POST: http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx
Mon, 19 Feb 2018 21:39:18 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:21 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:23 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:25 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:28 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:30 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:33 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:35 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:37 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:40 MakeHTTPRequest: Failed http://<CoreServerName>:443/landesk/managementsuite/core/ServerAuthentication/serverauthentication.asmx on server (10054), server status: -1.
Mon, 19 Feb 2018 21:39:41 ERROR: Failed to submit to decrypt string
Mon, 19 Feb 2018 21:39:41 Failed to launched application - err=-1918107541
Mon, 19 Feb 2018 21:39:41 Launched application '<PathToExecutable>' ('') result -1918107541
Mon, 19 Feb 2018 21:39:41 Installation result 8DB5006B
Mon, 19 Feb 2018 21:39:41 RunPackageInstall: stop on returncode=8db5006b of package=test CMD
Mon, 19 Feb 2018 21:39:41 processing of package is complete, result -1917517717 (0x8db5006b - code 107)
...
Although the log file above shows failed HTTP requests, at the same time the IIS log file on the Core Server shows successful downloads:
2018-02-19 18:16:29 10.14.0.20 POST /LANDesk/managementsuite/core/serverauthentication/serverauthentication.asmx - 443 - <client IP address> - - 200 0 0 455
Thank you!
This may sound simple but it has me stumped at the moment...
I am looking to copy a file from an HTTP distribution share , down to a machine that has LANDesk agent installed, but is not on our domain.
The http share can be reached from the non domain device, so it is not an access rights issue.
From looking at the documentation I have tried the following , without success.
%LDMS_CLIENT_DIR%\sdclient.exe /f /p="http://LDMS_CORE/distribution/FILES/FILE.TXT" /dest="c:\landesk\FILE.TXT" /lan=90 /wan=60
Is this format incorrect or am I doing something wrong ?
Any help would be gratefully received.
Thanks
Hello,
I have few end user machines for which not to target any deployments in business hours, So i need to create maintenance window for these machines to avoid deployments in business hours.
When trying to install a Install_MS_Office2016_Visio_Pro_C2R_X86_DK_WinAll package on identical Lenovo laptops i get tis error on 2 out of 4 mashines..
Fri, 03 Nov 2017 13:56:03 ******* sdclient starting to process task *******
Fri, 03 Nov 2017 13:56:03 Task id to process: 1270
Fri, 03 Nov 2017 13:56:03 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.1270.RunNow._eoSDr5VpdpvኚdJGmCEqrTxCT0=.xml"
Fri, 03 Nov 2017 13:56:03 The nostatus flag has NOT been set.
Fri, 03 Nov 2017 13:56:03 Core name 'SPSVIVA-APP101' obtained from the registry
Fri, 03 Nov 2017 13:56:03 Sending task status, cmd line -coreandip=SPSVIVA-APP101 -taskid=1270 -retcode=229392442 "-ldap=CN=ABJ Andreas Bo Jensen,OU=Windows 10,OU=SPBrugere,DC=sampension,DC=net" -pkgid=368
Fri, 03 Nov 2017 13:56:04 The nostatus flag has NOT been set.
Fri, 03 Nov 2017 13:56:04 Core name 'SPSVIVA-APP101' obtained from the registry
Fri, 03 Nov 2017 13:56:04 Sending task status, cmd line -coreandip=SPSVIVA-APP101 -taskid=1270 -retcode=229392444 "-ldap=CN=ABJ Andreas Bo Jensen,OU=Windows 10,OU=SPBrugere,DC=sampension,DC=net" -pkgid=368
Fri, 03 Nov 2017 13:56:05 About to call DownloadFiles (19 files) with these settings:
Fri, 03 Nov 2017 13:56:05 m_allowedBandwidthWAN: 50
Fri, 03 Nov 2017 13:56:05 m_allowedBandwidthLAN: 75
Fri, 03 Nov 2017 13:56:05 m_discardPeriodSeconds: 604800
Fri, 03 Nov 2017 13:56:05 m_preserveDirectoryStructure: 1
Fri, 03 Nov 2017 13:56:05 m_bUseWanBWForPush: 0
Fri, 03 Nov 2017 13:56:05 m_bSynchronize: 0
Fri, 03 Nov 2017 13:56:05 Allowed download methods(m_downloadControl):
Fri, 03 Nov 2017 13:56:05 Source
Fri, 03 Nov 2017 13:56:05 m_preferredServerControl: AttemptPreferredServer
Fri, 03 Nov 2017 13:56:07 The nostatus flag has NOT been set.
Fri, 03 Nov 2017 13:56:07 Core name 'SPSVIVA-APP101' obtained from the registry
Fri, 03 Nov 2017 13:56:07 Sending task status, cmd line -coreandip=SPSVIVA-APP101 -taskid=1270 -retcode=229392444 "-message=100%" -pkgid=368
Fri, 03 Nov 2017 13:56:07 The nostatus flag has NOT been set.
Fri, 03 Nov 2017 13:56:07 Core name 'SPSVIVA-APP101' obtained from the registry
Fri, 03 Nov 2017 13:56:07 Sending task status, cmd line -coreandip=SPSVIVA-APP101 -taskid=1270 -retcode=229392258 "-ldap=CN=ABJ Andreas Bo Jensen,OU=Windows 10,OU=SPBrugere,DC=sampension,DC=net" -pkgid=368
Fri, 03 Nov 2017 13:56:09 ExpandEnvironmentVariables Result: /configure install-VisioPro.xml
Fri, 03 Nov 2017 13:56:09 LSWD or Executable Client Thread
Fri, 03 Nov 2017 13:56:09 PackagePath: [http://spsviva-app101/Softwarepackages/Microsoft Office 2016 Click 2 Run x86/setup.exe]
Fri, 03 Nov 2017 13:56:09 Processing generic executable
Fri, 03 Nov 2017 13:56:28 Launched application 'C:\Program Files (x86)\LANDesk\LDClient\sdmcache\Softwarepackages\Microsoft Office 2016 Click 2 Run x86\setup.exe' ('/configure install-VisioPro.xml') result 17006
Fri, 03 Nov 2017 13:56:28 Installation result 8DB5426E
Fri, 03 Nov 2017 13:56:28 CPolicyHistory::LoadHistoryDaysToKeep: No task history maintenance to perform, registry settings for task history maintenance mode is '-1'
Fri, 03 Nov 2017 13:56:28 RunPackageInstall: stop on returncode=8db5426e of package=Install_MS_Office2016_Visio_Pro_C2R_X86_DK_WinAll
Fri, 03 Nov 2017 13:56:28 processing of package is complete, result -1917500818 (0x8db5426e - code 17006)
This article covers one of the reasons you might be facing this message. If you want to have a detailed troubleshooting guidance, please read the following article:How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution"
This message is present in LANDESK Management Suite 9.6 [26.11.14]
When trying to deploy a package, whatever Task settings you use, you might see this message:
Client has initiated asynchronous policy execution
This message tells you that the Client is trying to pull a policy from the Core Server and does not manage to get it as it looks to get stuck in a loop.
This highlights a communication issue between them.
It can be that:
There might be other issues that will be reported if recognized.
As explained earlier, we have to check these settings in order to ensure our Core and Client are ready not only to see each other, but to exchange data.
To do so, follow the next steps:
From the Core Server
Right click on one of the client machine that has the issue and click "Properties"
What is important here is the Common Base Agent status.
If the status is: Not loaded
If the status is: Loaded
Go to the next step.
Take note of your Client IP address, in our example:
192.168.1.63
Then go on your Client machine and check your actual IP address:
If the IP address is the same, go to step III. Full Synchronization
If the IP address is not the same as the one you had earlier on the Console, run the following command from the client machine:
"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /V /mini
And execute a PolicySync:
"C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe"
This will verify and update your IP address to the Core Server and then trigger the APM page from the Core with the correct Client information. Your task will then continue.
If the Common Base Agent is Loaded and the IP address is not different from the one you actually have, then the message is showing because one or more files / components have changed during the task deployment.
In order to be sure that your Core Server and Client are properly up to date one for the other, you can launch a full synchronization scan from your client machine:
"C:\Program Files (x86)\LANDesk\LDClient\LDISCN32.EXE" /NOUI /SYNC
This will send not a delta but all the data from the client to the Core without showing any user interface.
And execute a PolicySync:
"C:\Program Files (x86)\LANDesk\LDClient\PolicySync.exe"
Now your task should be running as expected.
If you see that your task remains in the "Task Queued at Client for Execution" status after that, please read the following article: How to resolve "Task Queued at Client for Execution"
Environment:
LDMS9.0 SP3 or later
Sympton:
Your schedule task will be stay active status and never finish.
Error message and Logs needs to check:
1. In LANDesk.Scheduler.GlobalScheduler.Skeleton.exe.log
You may see the following exception:
Line 10767: 08/20/2013 15:17:12 INFO 14776:1 RollingLog : <MachineName> : Exception in GlobalSchedulerSkeleton: '', hexadecimal value 0x02, is an invalid character. Line 5, position 22.
Line 10768: 08/20/2013 15:17:12 INFO 14776:1 RollingLog : <MachineName> : at System.Xml.XmlTextReaderImpl.Throw(Exception e)
2. In the global scheduler log you may see the following:
<MachineName> has completed task with status 8 (An exception occured processing the delegated task.)
3. There is a .pmf file that is created for the scheduled task. It can be found in managementsute\landesk\file named corename-task-#.pmf. Where corename is the corename, and # is the task ID. Review that file to see if there are invalid characters looks like this:
<targets>
<target deviceId="xxxx" computerIdn="xxxx" />
</targets>
Reason:
The schedule task stacked at active status because of the exception, the task will not continue. The exception was because there was some invalid charicters contains in the "device ID"
Solution:
1. Delete the machine from All device list.
2. Then follow the steps in this document to clear the device ID on the machine.
Ivanti is moving further development of the Workspaces product into Portal Manager, and other utilities. This will allow us to address the use case scenarios and challenges faced by end users more appropriately. This document will go over what settings you will need to change in order to switch your environment to Portal Manager.
1) Disable Workspaces from current agent configuration.
Uncheck the box for "Add to program group>
2) Enable Portal Manager.
Once the correct options have been changed, you will need to address the current agents since, unchecking work-spaces will not remove it from the program group. Also, the links for Portal Manager will not be created since, this is part of the install.
Please use the script below that matches your version:
2017.X:
I have seen references in some places about being able to publish provisioning templates in the portal. But no matter what I do, I am unable to get it to show up in my portal.
The default Portal Manager deployment doesn't include any launchpad items. Use software distribution to add items to Portal Manager.
Items you can add to Portal Manager include:
This is what I ended up doing, though it did not work.
I created the os provisioning template and added actions. In Distribution Packages I made a new universal package | Provisioning. I included the template I had created before. I created scheduled task, went into the task, associated it to my workstation, set it to policy push, kicked it off. It shows as active in the progress window but nothing ever shows up in the Portal, even after I refresh it. I can add and remove typical distribution packages and it is reflected in the Portal window, so I know I can get some things to work.
I looked around and have yet to find documentation showing how to do this. Anyone know where such documentation would be?
Hello,
I work actualy with Landesk 9.0 SP3.
I want to deploy on some computer a powershell script and I want to take the exit code from powershell as return code for the déployment on the computer.
As prove of concept I tested with a file test.ps1 :
exit (1)
As I déploy this on my computer, it return always 0.
(the deployment went well)
And that's true, the script was executed on my computer.
I don't want this result, I want an error on the distribution result.
How is it possible ?
Thank's
Hi,
I have a scenario here on the software distribution:
If I'm required to push a 3GB software to a client device. While pushing the 3GB software to client and the status is "downloading 50%", then the client turn off the their device.
Question:
1. When the client turn back on their device, will the download continue at 50% or it will start the download again?
2. If the download will continue at 50%, do I required to configure any specific setting?
Hello together,
I want to update a registry entry over the software distribution, but it doesn't work with the actions task because the entry needs to be updated as administrator.
I tried to run the task under the LocalSystem account and also unter a local administrator account with a specified user. Both of them didn't work and didn't update the registry.
I copied the preview of the PowerShell-script(from the actions-package) and ran it manually on a computer with a powershell started as administrator.
The registry entry was now updated.
How can I run a powershell as administrator over the software distribution?
Thanks in advance
Dominik
This article only applies if the majority of the task targets are able to run the task properly, but one or a few targets get stuck in Asynchronous Policy Execution state. This indicates an issue with the devices themselves. If ALL devices in the task get stuck in this state, it usually indicates a core-side issue which is addressed in these documents:
How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution"
"Client has initiated asynchronous policy execution" - Return Code 1354
Asynchronous Policy Execution is not an error, but a status message. It indicates that the task has not started on the target device because it is waiting for something else to complete. This could be a vulnerability scan (vulscan.exe), a software install (sdclient.exe) or a process initiated by sdclient.exe or vulscan.exe (msiexec, wusa, cmd etc.).
Under normal circumstances, the other process will finish and close out allowing the task to move beyond Asynchronous state. However, on occasion, the actions being initiated get stuck, preventing other tasks from continuing. This document is intended to troubleshoot and address this condition.
First, check task manager on the device in question. Look for any of the following processes:
Sometimes, simply ending task on these processes or rebooting the client device will clear up the Asynchronous state. If this doesn't work, or if none of these processes are running, then we will move on to clearing out stuck policies on the core and client.
Attached to this article is a .ldms file that you can import to your managed scripts to accomplish this remotely or for many devices at once. Select the version that matches your LDMS version.
PLEASE NOTE: This script is provided as a courtesy only and may need to be edited or adjusted for your particular needs - Ivanti Support does not support custom scripts and will not be able to assist if this script causes unexpected issues.
This article discusses an issue where the client cache location is not updated on a Client/Preferred Server after a change.
After updating the Client Cache Location (via Client Connectivity Settings) files downloaded to a Device or Preferred Server still revert to SDMcache.
After updating the Client Cache Location within Client Connectivity Settings (seen below), the downloadmulticastconf.xml file on the Client is not updated properly.
Verification can be done by opening the downloadermulticastconf XML file (located at \ProgramData\LANDesk\TMCdownload on the client), and seeing one of two things:
1. The XML file shows the following line:
Original
<CacheDirectory>C:\ProgramData\LANDesk\ManagementSuite\sdmcache</CacheDirectory>
This line shows that the sdmcache is still the primary Client Cache location.
2. The XML file will be completely blank upon opening.
Delete the existing XML file from the \TMCDownload\ directory.
From the client device open a run prompt and enter the following:
Once the update has completed, verify the <CacheDirectory> line within the downloadmulticastconf.xml file (this will be re-written with the changesettings task) to verify the updated location of your Client Cache.
