Hi All,

Please let me know the process to put key in Adobe CS5 distribution package...

Hi,

I am new to LandDesk and I have just created 2 packages. One of them is a batch file and the delivery method I chose is Push|Silent Install- from Source- NoReboot. The other is an executable and the method chosen is Push|Silent Install- from Source- NoReboot.

However, when I start the tasks, I see that it asks for actions during installation (Next etc.)

How can I bypass these actions? The idea is to install the software remotely on multiple PCs at the same time, without being prompted for actions.

Thanks.

I am doing a package to uninstall MS Visio 2007 I got the error (Sdclient.exe or the installation program was terminated at the client" when trying to deploy executable package)

And here is the log:

Downloading file \\ldsrv01\Packages\Stuff\Uninstall Microsoft Products\Visio 2007\Uninstall.bat (/dw4dCO0/jFmT6UTP3qH7A==, 5)

Wed, 16 Jan 2013 09:48:00 5672 5224 Downloading file 1 of 1 from '\\ldsrv01\Packages\Stuff\Uninstall Microsoft Products\Visio 2007\Uninstall.bat'

Wed, 16 Jan 2013 09:48:00 5672 5224 Batch file Client Thread

Wed, 16 Jan 2013 09:48:00 5672 5224 PackagePath:              [\\LDSERVER\Packages\Stuff\Uninstall Microsoft Products\Visio 2007\Uninstall.bat]

Wed, 16 Jan 2013 09:48:04 5672 5224

Wed, 16 Jan 2013 09:48:04 5672 5224 Installation result 8DB50001

Wed, 16 Jan 2013 09:48:06 5672 5224 Sending task status, cmd line -coreandip=LDSRV01:10.20.4.152 -taskid=3716 -retcode=-1917517823 -complete -pkgid=413

Wed, 16 Jan 2013 09:48:07 5672 5224 processing of package is complete, result -1917517823 (0x8db50001 - code 1)

I changed the delivery methods as per a previous article to be Run the package from the source and then I got error ( Incorrect Function)

And here is the log:

Processing package : MS Visio 2007 XML

Wed, 16 Jan 2013 10:02:50 2424 3868 File (\\ldsrv01\Packages\Stuff\Uninstall Microsoft Products\Visio 2007\Uninstall.bat) is cached locally

Wed, 16 Jan 2013 10:02:50 2424 3868 processing of package is complete, result 229392397 (0x0dac400d - code 16397)

Wed, 16 Jan 2013 10:02:51 2424 3868 File (\\LDSERVER\Packages\Stuff\Uninstall Microsoft Products\Visio 2007\Uninstall.bat) is cached locally

Wed, 16 Jan 2013 10:02:51 2424 3868 Batch file Client Thread

Wed, 16 Jan 2013 10:02:51 2424 3868 PackagePath:      [\\ldsrv01\Packages\Stuff\Uninstall Microsoft Products\Visio 2007\Uninstall.bat]

Wed, 16 Jan 2013 10:02:51 2424 3868 Adding '\\ldsrv01\Packages\Stuff\Uninstall Microsoft Products\Visio 2007' to the path

Wed, 16 Jan 2013 10:02:54 2424 3868

Wed, 16 Jan 2013 10:02:54 2424 3868 Installation result 80070001

Wed, 16 Jan 2013 10:02:56 2424 3868 Sending task status, cmd line -coreandip=LDSRV01:10.20.4.152 -taskid=3741 -retcode=-2147024895 -complete

Wed, 16 Jan 2013 10:02:58 2424 3868 processing of package is complete, result -2147024895 (0x80070001 - code 1)

Any advise?

Has anyone had any success pushing the click to run Office 365 installation to users in there domain. I am having an issue with push. I have downloaded the ODT(office deployment tool) and the click to run Office 365 sources. I have created a bat file to run the setup.exe and configured my configuration.xml file but it will not run in LanDesk.

If you have any tips or example scripts for pushing this would be greatly appreciated.

Thanks,

James P

Hi all,

I've created a software distribution package and I'm trying to deploy it to my own workstation as a test, but I can't seem to get the download started. I'm using 9.6 and I'm able to deploy an agent installation normally, no troubles there. I read through some of the support articles (How to troubleshoot tasks hung with a status of "Client has initiated asynchronous policy execution" and "Client has initiated asynchronous policy execution" - Return Code 1354) and found that the PolicyTaskHandler.exe.log on our core server looks vastly different than the article says it should. Here's the entry I see every time I try to start the scheduled task:

06/02/2015 08:40:07 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : ***PolicyTaskHandler run options***

06/02/2015 08:40:07 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : Accelerated push: [True]

06/02/2015 08:40:07 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : Use DNS/WINS resolution for discovery: [True]

06/02/2015 08:40:07 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : Wait for machines to finish: [False]

06/02/2015 08:40:07 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : Maximum Push or Policy-supported push run time minutes: [30]

06/02/2015 08:40:07 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : Verbose logging: [False]

06/02/2015 08:40:18 INFO  4224:1     RollingLog : [Task: Direct - 6/2/2015 8:16:52 AM, TaskID: 24, ProcID: 4224] : PolicyTaskHandler finished processing task, setting task status to [ASYNC_EXECUTION]...

I feel like the answer is right in front of me, but no change I make to the agent settings, scheduled task, or package itself seems to make a difference. What am I missing?

Hi,

we've sometimes a problem when trying to distribute a package. When I start distribution tasks some of the affected computers complete it without any problems others quit with an error in the console "Failed to download all additional files for a package".

The appropiate log says the following:

Mon, 27 Apr 2009 09:48:26 File (http://xerxes/landesk/files/FLG/ccmclean.exe) is not in cache
Mon, 27 Apr 2009 09:48:26 Downloading file to C:\Programme\LANDesk\LDClient\sdmcache\taskmanifest.XERXES.31.7.ini, attempt 0
Mon, 27 Apr 2009 09:49:39 DownloadFile returned 490
Mon, 27 Apr 2009 09:49:39 Downloading file to C:\Programme\LANDesk\LDClient\sdmcache\taskmanifest.XERXES.31.7.ini, attempt 1
Mon, 27 Apr 2009 09:50:51 DownloadFile returned 490
Mon, 27 Apr 2009 09:50:51 Downloading file to C:\Programme\LANDesk\LDClient\sdmcache\taskmanifest.XERXES.31.7.ini, attempt 2
Mon, 27 Apr 2009 09:52:03 DownloadFile returned 490
Mon, 27 Apr 2009 09:52:03 ..\AdditionalFiles.cpp(65): (8DAC4026): Failed to download file http://LANDesk.Gateway@172.22.0.12/ldlogon/FileLists/taskmanifest.XERXES.31.7.ini : (80070002)
Mon, 27 Apr 2009 09:52:03 processing of package is complete, result -1918091226 (0x8dac4026 - code 16422)

We are using 8.8 SP2.

I read through several community posts and some of them are describing the above problem but up so far the solution was "solved with SP2".

Any help is welcome - but beware I'm a Landesk newbie.

TIA,

Ronald

Hi There,

Does anybody have any ideas of sending this via software distribution ?

Thanks,

Mark.

Hi All,

I'm new to the LanDesk tool. I have been trying to resolve package deployment failures but no luck.

We deployed VC++ Runtime 2010 on a test pc where it already has the higher version of VC++ (2012) installed on it and hence the deployment failed.

After this, i tried to deploy other packages like Adobe, Office but the installation never gets triggered on the client PC. When i check the scheduled task for these packages, it shows the status as "Active", Result : "client has initiated asynchronous policy execution" and the Return Code "1354".

The last few lines of the sdclient.log file has these entries:

Wed, 17 Sep 2014 09:53:58 PostInstallInventoryScan: Successfully created inventory scanner task.

Wed, 17 Sep 2014 09:53:58 Sending task status, cmd line -coreandip=coreserver -taskid=198 -retcode=-1918091262 -complete "-log=C:\Program Files (x86)\LANDesk\LDClient\data\sdclient_task198.log" -pkgid=177

Wed, 17 Sep 2014 12:22:09

RunAppMain: command Line :

Wed, 17 Sep 2014 12:22:09

Wed, 17 Sep 2014 12:22:09 Task is not required to send status

Can anyone able to provide any advice on what can be done to overcome this issue?

Thanks,

Gopal

Greetings,

I have set up ACDSee for deployment but the push job goes to Failed even when the installation is successful.

The ACDSee msi does actually prompt for a reboot after installation but this is halted due to LD using REBOOT=ReallySuppress.

In earlier distributions I have bypassed the 'Failed' status creating a batch script which returns Code 0 instead

of 3010 (ERROR_SUCCESS_REBOOT_ REQUIRED).

However in this case I can't find any msi return code which is related to a reboot required,

would have been great if anyone could have a look at the LD log and clarify why LD returns a Failed status in this case:

Note that in this case ACDSee is successfully installed and the machine is not rebooted,

ACDSee works as it should:

Processing package : ACDSee

Fri, 28 Mar 2008 13:09:00 File (
....\ACDSee for Pentax 2.0.msi) is not in cache

Fri, 28 Mar 2008 13:09:00 MSI Client Thread

Fri, 28 Mar 2008 13:09:00 PackagePath:      http://\\....\ACDSee\ACDSee for Pentax 2.0.msi

Fri, 28 Mar 2008 13:11:11 Installing MSI package

Initializing the MSI package information

Starting the installation of the MSI package

Installing MSI package from '
....\ACDSee\ACDSee for Pentax 2.0.msi' using options 'ALLUSERS=1 COMPANYNAME="xxxx" USERNAME="xxxx" REBOOT=ReallySuppress ALLUSERS=1'

Stating Action : Action 13:09:07: INSTALL.

Stating Action : Action 13:09:07: AppSearch. Searching for installed applications

Stating Action : Action 13:09:07: LaunchConditions. Evaluating launch conditions

Stating Action : Action 13:09:07: WMPVersionCompare.

Stating Action : Action 13:09:08: FindRelatedProducts. Searching for related applications

Stating Action : Action 13:09:08: ValidateProductID.

Stating Action : Action 13:09:08: setUserProfileNT.

Stating Action : Action 13:09:08: setAllUsersProfile2K.

Stating Action : Action 13:09:08: CHECK_REG_KEY.

Stating Action : Action 13:09:08: CostInitialize. Computing space requirements

Stating Action : Action 13:09:08: FileCost. Computing space requirements

Stating Action : Action 13:09:08: IsolateComponents.

Stating Action : Action 13:09:08: SetARPInstallLocation.

Stating Action : Action 13:09:08: CostFinalize. Computing space requirements

Stating Action : Action 13:09:08: SetARPReadme.

Stating Action : Action 13:09:08: SetPageLibraryDirectory.

Stating Action : Action 13:09:08: SetODBCFolders. Initializing ODBC directories

Stating Action : Action 13:09:08: MigrateFeatureStates. Migrating feature states from related applications

Stating Action : Action 13:09:08: InstallValidate. Validating install

Stating Action : Action 13:09:08: SetParentExeProperty.

Stating Action : Action 13:09:08: SetSIPHomeProperty.

Stating Action : Action 13:09:08: RemoveExistingProducts. Removing applications

Stating Action : Action 13:09:08: InstallInitialize.

Stating Action : Action 13:09:09: AllocateRegistrySpace. Allocating registry space

Stating Action : Action 13:09:09: ProcessComponents. Updating component registration

Stating Action : Action 13:09:09: GenerateScript. Generating script operations for action:

Stating Action : Action 13:09:09: UnpublishComponents. Unpublishing Qualified Components

Stating Action : Action 13:09:09: UnpublishFeatures. Unpublishing product features

Stating Action : Action 13:09:09: StopServices. Stopping services

Stating Action : Action 13:09:09: DeleteServices. Deleting services

Stating Action : Action 13:09:09: UnregisterComPlus. Unregistering COM+ Applications and Components

Stating Action : Action 13:09:09: SelfUnregModules. Unregistering modules

Stating Action : Action 13:09:09: UnregisterTypeLibraries. Unregistering type libraries

Stating Action : Action 13:09:09: RemoveODBC. Removing ODBC components

Stating Action : Action 13:09:09: UnregisterFonts. Unregistering fonts

Stating Action : Action 13:09:09: RemoveRegistryValues. Removing system registry values

Stating Action : Action 13:09:09: UnregisterClassInfo. Unregister class servers

Stating Action : Action 13:09:09: UnregisterExtensionInfo. Unregistering extension servers

Stating Action : Action 13:09:09: UnregisterProgIdInfo. Unregistering program identifiers

Stating Action : Action 13:09:09: UnregisterMIMEInfo. Unregistering MIME info

Stating Action : Action 13:09:09: RemoveIniValues. Removing INI file entries

Stating Action : Action 13:09:09: RemoveShortcuts. Removing shortcuts

Stating Action : Action 13:09:09: RemoveEnvironmentStrings. Updating environment strings

Stating Action : Action 13:09:09: RemoveDuplicateFiles. Removing duplicated files

Stating Action : Action 13:09:09: RemoveFiles. Removing files

Stating Action : Action 13:09:09: RemoveFolders. Removing folders

Stating Action : Action 13:09:09: CreateFolders. Creating folders

Stating Action : Action 13:09:09: MoveFiles. Moving files

Stating Action : Action 13:09:09: InstallFiles. Copying new files

Stating Action : Action 13:09:09: InstallPFC.

Stating Action : Action 13:09:09: DuplicateFiles. Creating duplicate files

Stating Action : Action 13:09:09: PatchFiles. Updating files

Stating Action : Action 13:09:09: BindImage. Binding executables

Stating Action : Action 13:09:09: CreateShortcuts. Creating shortcuts

Stating Action : Action 13:09:09: RegisterClassInfo. Registering class servers

Stating Action : Action 13:09:09: RegisterExtensionInfo. Registering extension servers

Stating Action : Action 13:09:09: RegisterProgIdInfo. Registering program identifiers

Stating Action : Action 13:09:09: RegisterMIMEInfo. Registering MIME info

Stating Action : Action 13:09:09: WriteRegistryValues. Writing system registry values

Stating Action : Action 13:09:09: WriteIniValues. Writing INI file values

Stating Action : Action 13:09:09: WriteEnvironmentStrings. Updating environment strings

Stating Action : Action 13:09:09: RegisterFonts. Registering fonts

Stating Action : Action 13:09:09: InstallODBC. Installing ODBC components

Stating Action : Action 13:09:09: RegisterTypeLibraries. Registering type libraries

Stating Action : Action 13:09:09: RegisterComPlus. Registering COM+ Applications and Components

Stating Action : Action 13:09:09: InstallServices. Installing new services

Stating Action : Action 13:09:09: StartServices. Starting services

Stating Action : Action 13:09:09: SelfRegModules. Registering modules

Stating Action : Action 13:09:09: RegisterUser. Registering user

Stating Action : Action 13:09:09: RegisterProduct. Registering product

Stating Action : Action 13:09:10: PublishComponents. Publishing qualified components

Stating Action : Action 13:09:10: PublishFeatures. Publishing product features

Stating Action : Action 13:09:10: PublishProduct. Publishing product information

Stating Action : Action 13:09:10: ScheduleReboot.

Stating Action : Action 13:09:10: RegisterACDEncodeQT.

Stating Action : Action 13:09:10: registerACDEncodeRM.

Stating Action : Action 13:09:10: RegisterACDFX.ax.

Stating Action : Action 13:09:10: registerACDWaterMark.

Stating Action : Action 13:09:10: ACDRegInstaller.

Stating Action : Action 13:09:10: SetSTXProperty.

Stating Action : Action 13:09:10: SetFileAssociation.dll.

Stating Action : Action 13:09:11: DBUpgrade603. Upgrading existing database

Stating Action : Action 13:09:11: InstallFinalize.

Stating Action : Action 13:09:11: ProcessComponents. Updating component registration

Stating Action : Action 13:09:11: RemoveODBC. Removing ODBC components

Stating Action : Action 13:09:11: CreateFolders. Creating folders

Stating Action : Action 13:09:12: InstallFiles. Copying new files

Stating Action : Action 13:10:59: CreateShortcuts. Creating shortcuts

Stating Action : Action 13:11:00: RegisterClassInfo. Registering class servers

Stating Action : Action 13:11:00: RegisterProgIdInfo. Registering program identifiers

Stating Action : Action 13:11:00: WriteRegistryValues. Writing system registry values

Stating Action : Action 13:11:00: RegisterTypeLibraries. Registering type libraries

Stating Action : Action 13:11:00: RegisterUser. Registering user

Stating Action : Action 13:11:00: RegisterProduct. Registering product

Stating Action : Action 13:11:01: PublishFeatures. Publishing product features

Stating Action : Action 13:11:01: PublishProduct. Publishing product information

Stating Action : Action 13:11:03: RegisterACDEncodeQT.

Stating Action : Action 13:11:04: registerACDEncodeRM.

Stating Action : Action 13:11:04: RegisterACDFX.ax.

Stating Action : Action 13:11:05: registerACDWaterMark.

Stating Action : Action 13:11:05: DBUpgrade603. Upgrading existing database

Stating Action : Action 13:11:05: RollbackCleanup. Removing backup files

Stating Action : Action 13:11:05: SetFileAssociations.

Stating Action : Action 13:11:10: AutorunDevDetect.

Failed to install the MSI package.

Installing MSI package (-127 seconds)

Installation of the MSI package failed

Fri, 28 Mar 2008 13:11:11 MSI result 8DAC4002

Fri, 28 Mar 2008 13:11:11 processing of package is complete, result -1918091262 (0x8dac4002 - code 16386)

I have created a brand distribution job and task, I pushed it to a 1000 machines. I have a large number of machines that come back with error 16395 (The package is already installed), This is the first time this package has ran on any of these computers and the strange thing is that all the computers that have error 16395 did run the task and it was successful. Has anyone else seen this behavior and if so how do I make sure it doesn't happen again. We are seeing this a lot since we to 9.6 sp1.

I have a whole bunch of scripts that I've generated using AutoIT that work great on Win2k and WinXP. I'm now trying to get them to work on Windows 7 (32 bit and 64 bit). I am deploying the scripts using LANDesk Management Suite version 8.8 and version 9 (two separate LANDesk core servers). The problem I'm seeing (I think) is that the UAC is stopping the programs from running (even though UAC is as disabled as much as it can be). LANDesk Management Suite downloads the scripts to the machines successfully using a pull-based technology, and then executes the scripts with the local computer SYSTEM account. The programs never display anything until I logout and log back in. I then get a message from Windows 7 telling me that there is one or more programs asking to interact with the desktop. If I allow the interaction, then Win7 goes into some sort of "secure" desktop mode (something I haven't been able to find anything about online yet), and the scripts finally show up. They can be as simple as:

#RequireAdmin
MsgBox(0,'Test','Hello World!')
Exit

If I manually browse to the executable and run it, after being prompted to allow it to run, the script executes successfully.

Any ideas?

Here's the code:

REM If pnamain.exe is running, kill it

tasklist.exe | find /I "pnamain.exe">NUL
sdclient.exe /msg="Line 1 completed ErrorLevel %ERRORLEVEL%"
if "%ERRORLEVEL%" == "0" taskkill /F /IM pnamain.exe 
sdclient.exe /msg="Line 2 completed ErrorLevel %ERRORLEVEL%"

exit 0

I added the sdclient messages to figure out where I was having problems. I've confirmed that the code is working, and I'm getting a "Line 2 completed ErrorLevel 0" message in the console. pnamain.exe is also getting killed off.

For whatever reason it is returning 16386 Failed to install package.

I would have thought the exit 0 line would have caused it to exit successfully not matter what. If pnamain.exe wasn't running at the time the bat file ran, I thought whatever the ERRORLEVEL was would be the status of the scheduled task. Apparently not.

Can anyone lend some insight into this?

Thanks

Dear all

We are trying to install a 3rd party MSI but getting the dreaded 1603 MSI error.  We have tried allsorts inc. elevating NTFS/registry/DCOM permissions to no avail and we have checked we can install other MSIs fine with out current version of InstallShield (11.5).  I have attached the verbose MSI logfile in the hope someone can read and understand it and shine some light on our predicament. I have copied an extract from the logfile below for quick reference to the seemingly problematic area:-

------------------
MSI (s) (68!70) [11:46:40:300]: Creating MSIHANDLE (236) of type 790531 for thread 2160
1: Failed to extract IGdi.dll, Ignore it.
MSI (s) (68!70) [11:46:40:300]: Closing MSIHANDLE (236) of type 790531 for thread 2160
MSI (s) (68!54) [11:46:40:300]: Creating MSIHANDLE (237) of type 790531 for thread 2644
1: ISMsiServerStartup Failure, Failed to Initialize script support, Error = 0x80070006
MSI (s) (68!54) [11:46:40:300]: Closing MSIHANDLE (237) of type 790531 for thread 2644
MSI (s) (68:3C) [11:46:40:300]: Closing MSIHANDLE (194) of type 790542 for thread 2392
1: MsiServerStartup failed. Abort installation.
Action ended 11:46:40: ISStartup. Return value 3.
MSI (s) (68:58) [11:46:40:316]: Doing action: ISCleanUpFatalExit
Action ended 11:46:40: ISMsiServerStartup. Return value 1603.
------------------

I have looked in the InstallShield/Acresso Forums and scoured the web generally and found loads of people suffering the same fate.  What appears to be consistent is that:-

- Launch MSI as local system when an admin is logged in: works
- Launch MSI as local system when nobody is logged in: works

- Launch MSI as local system when a non-admin local user is logged in: works. 

- Launch MSI as local system when a non-admin domain user is logged in: doesn't work (our environment).

We can force the installation to be successful by adding the logged on domain user to a "Desktop Admins" group which effectively elevates their permissions to 'administrator'.  However, this really is our last resort and least preferred solution because it's against IT Policy to any user to install unauthorised apps.  Attached the logfile from a successful installation so comparisons can be made between a failed and successful installation if helpful when troubleshooting.  I have tried StartAsUser.exe  but the install fails due to lack of admin rights as expected.  There must be a way to get this MSI installed without having to elevate the permissions of the logged-on user.

Any ideas please?

Many thanks

Scott

Hi guys..

we are running LDMS 9 SP2. and i am seeing a strange issue with a few clients - there may be more but we have not checked the estate.

We have a few machines that cannot get the preferred server list and are behaving oddly. You can remote control them, If you send a package to them it caches but the log file says this.

Hi,

I was wondering how i can remotely uninstall some software on users

machine's?

Thanks

Hi,

I try to uninstall and install new fonts on few computers, i think to do it with batch file with XCOPY files into Windows/fonts directory but iot don't works...

Anyone know about it ?

How to manage fonts with Landesk Management Suite ?

Thx

Ben

I use LDMS 9SP3

All, we've recently been asked to install a font set on all of the machines in our network (around 3,000 machines). I've scoured the web and the community but just seem to be more confused than when I began. Here's what I'm working with:

• we've placed the font set in a centralized location on our software distribution folder
• we're targeting c:\windows\fonts all our machines
• we have our landesk service account and the local admin account to work with

I thought it woud be as simple as finding a way to copy the files to c:\windows\fonts; however, I've read where end users would need to be power or admin users OR there would need to be registry entries.

Sooo...long story short, how many of you have deployed font sets to 1000+ machines? How did you accomplish this (any details or scripts would be greatly appreciated)?

Hello! I'm fairly new to the LANDesk world (the person at my company who was in charge of it left). I'm currently testing out LANDesk Management Suite 9.6 SP1 to update our current 9.0 version. I'm having some difficulty with trying to figure out how to configure the Portal Manager. What I'm trying to do is get all the applications that we make available to the user end up in the LaunchPad. As it sits right now, the application is only coming up on the left hand panel under Task History. If someone could help me out on this, I would greatly appreciate it! (I've tried looking online, and the only things I've been finding hasn't helped me at all).

Hello All,

This is probably a really simple question although I am not that knowledgeable on scripting nor pushing batch files through LANDesk, but we are trying to put a web icon on all of our employee desktops. I am sure there may be a better way to do this, if so please let me know but here is how I did it.

I created a batch script:

xcopy "\\servername\Network Support\Software\Point 11 Browser\Point 11.Ink" c:\users\public\desktop

and then created my batch script distribution package pointing to the folder the batch script is in and then creating the scheduled task. I drag my computer in for testing and it fails with error code 4.

This is the log I get when the job fails:

Processing package : Point 11 Icon
Thu, 18 Aug 2011 08:35:45 File (\\servername\software$\Batch_Files\Point11.bat) is not in cache
Thu, 18 Aug 2011 08:35:47 Performing TCP connection with a timeout of -1 milliseconds
Thu, 18 Aug 2011 08:35:49 ILdDownloading file to C:\Program Files\LANDesk\LDClient\sdmcache\ldlogon\FileLists\taskmanifest.PRDLANDESK.38.21.ini, attempt 0
Thu, 18 Aug 2011 08:35:51 ILdDownloadFile returned 0
Thu, 18 Aug 2011 08:35:51

Downloading file \\servername\software$\Batch_Files\Point11.bat (lH8Jba+otz6qY5/g4CNO/g==, 3)
Thu, 18 Aug 2011 08:35:51 Downloading file 1 of 1 from '\\servername\software$\Batch_Files\Point11.bat'
Thu, 18 Aug 2011 08:35:51 processing of package is complete, result 229392397 (0x0dac400d - code 16397)

Thu, 18 Aug 2011 08:35:51 File (\\servername\software$\Batch_Files\Point11.bat) is cached locally
Thu, 18 Aug 2011 08:35:51 ILdDownloading file to C:\Program Files\LANDesk\LDClient\sdmcache\ldlogon\FileLists\taskmanifest.PRDLANDESK.38.21.ini, attempt 0
Thu, 18 Aug 2011 08:35:53 ILdDownloadFile returned 0
Thu, 18 Aug 2011 08:35:53

Downloading file \\servername\software$\Batch_Files\Point11.bat (lH8Jba+otz6qY5/g4CNO/g==, 3)
Thu, 18 Aug 2011 08:35:53 Downloading file 1 of 1 from '\\servername\software$\Batch_Files\Point11.bat'
Thu, 18 Aug 2011 08:35:53 Batch file Client Thread
Thu, 18 Aug 2011 08:35:53 PackagePath:     [\\servername\software$\Batch_Files\Point11.bat]
Thu, 18 Aug 2011 08:35:56
Thu, 18 Aug 2011 08:35:56 Installation result 8DB50004

Thu, 18 Aug 2011 08:35:58 processing of package is complete, result -1917517820 (0x8db50004 - code 4)

Thanks in advance!

Running LANDesk Management Suite 9 with Service Pack 2. I'm attempting to install an executable package on a Windows 7 machine. When I try, the console shows a status of "Failed" and the error message "Sdclient.exe or the installation program was terminated at the client. Return code 1." I have never encountered this error before, and all of my other software packages have installed successfully in the past. To be sure, I also deployed a test package that ran successfully.

All LANDesk services are running under the local system account. The log file shows that all of the required files were downloaded to the client, and there are no indications of errors. Here is the last block of text from the log:

Fri, 20 Apr 2012 09:56:21 6316 6712 Downloading file 614 of 614 from 'http://betty.rf.odu.edu/packages/SageMIP/Support/Scripts/TECleanup/48253_XPsp3_11000_TE_Cleanup.sql'

Fri, 20 Apr 2012 09:56:22 6316 6712 LSWD or Executable Client Thread

Fri, 20 Apr 2012 09:56:22 6316 6712 PackagePath:           [http://betty.rf.odu.edu/packages/SageMIP/setup/Setup.exe]

Fri, 20 Apr 2012 09:56:22 6316 6712 Processing generic executable

Fri, 20 Apr 2012 09:56:22 6316 6712 Launched application 'C:\Program Files\LANDesk\LDClient\sdmcache\packages\SageMIP\setup\Setup.exe' ('/passiveui') result 1

Fri, 20 Apr 2012 09:56:22 6316 6712 Installation result 8DB50001

Fri, 20 Apr 2012 09:56:24 6316 6712 Sending task status, cmd line -coreandip=BETTY.RF.ODU.EDU:10.2.184.18 -taskid=82 -retcode=-1917517823 -complete -pkgid=20

Fri, 20 Apr 2012 09:56:25 6316 6712 processing of package is complete, result -1917517823 (0x8db50001 - code 1)

There are no errors in the event logs for the device, either. I'm stuck. Appreciate any insights!