This procedure can be used to set up a web repository with anonymous access for software distribution/Preferred Server using IIS 7.5

1. Start > Administrative tools > Internet Information services(IIS) Manager
2. Server name > sites ,then right click the "Default Web Site" > "Add virtual directory" and fill in the name and the path to the directory to be shared
3. After the virtual directory appears under the Default web site three , rigth click on it > edit permissions > Security > edit
4. Add:  the local IUSR , ANONYMOUS LOGON and NETWORK SERVICE they need at least "Read" and "List folder contents" rigths
5. Switch to feature view , in the central pane double click "directory browsing" and click "enable" under the action pane on the right   ( Be sure your newly created virtual directory is highligthed )
6. In Features View, double-click Authentication > On the Authentication page, select Anonymous Authentication.
7. In the Actions pane, click Edit to set the security principal under which anonymous users will connect to the site.
8. In the Edit Anonymous Authentication Credentials dialog box, select one of the following options:
--  Specific user, ( IUSR )
--  Application pool identity, if you want IIS processes to run by using the account that is currently specified on the property page for the application pool. By default, this is the Network Service account.
Important
If you use the Network Service account, you grant anonymous users all the internal network access associated with that account.
Note:  DO NOT convert the Virtual folder to an application folder

If you are using IIS 7, please visit: http://community.landesk.com/support/docs/DOC-20774

Note: If you are creating this virtual directory to a location that is off-core (such as a NAS server) your HTTP Redirect settings in IIS should not be set to point to the source of the directory. This will cause a loop and the HTTP directory will not resolve.

LDMS 9.6 SP2

I been trying to get this working with no success.

In a previous post it says that it "needs to be policy based and the packages need to be located on an http share on the core server"

This is what I have done:

1. Created a local account with read only access to a directory, in my case : C:\Users\Administrator\Documents\LDMS\SoftwareDistribution

2. Create a http share in my core as per this doc: https://community.landesk.com/support/docs/DOC-22861#comment-22670

    Now, this is for IIS 7.5 I'm running 8, there are a few sections that I'm not sure I'm configuring it correctly.

    In Step 8: Edit Anonymous Authentication Credentials dialog box, select one of the following options: --  Specific user, ( IUSR ) I selected that option and in credentials I entered the user name and password for the local account created in step 1. (is this correct, and if so why  the anonymous connection them?)

At this point I have a new virtual directory that point or should point to the share created in step 2.

I should be able to access this dir by going to http://localhost/softwaredistribution

I get this error, is that normal at this point?

Then when I create the package I get a 500 error

Your help is really appreciated,

Thank you.

We are rolling out IE11 with a custom package we created (batch file, exe’s, reg settings, etc). We are using a policy support push distribution method. We are on LDMS 9.6 SP2.

The task is set to prompt the user with a custom message and allow the user to Deploy Now or snooze. Also once the package is complete we force a reboot using the new 9.6 reboot settings (giving an option to defer until they can reboot).

So here is the issue. I dropped 30 PCs in there and clicked start. Most clicked on snooze but the 10 that clicked on Deploy Now had the package successfully deploy, the reboot prompt came up just fine, some rebooted…some deferred. The people that rebooted said after they logged in they were prompted again to install IE11. I checked and the task was successful on their PC the first time. So they don’t click anything and just reboot thinking something was up. After the reboot, they log in and after x amount of time it prompts them to install again. Some also tried to hit deploy now...which it does, prompts them to reboot, and then the cycle starts all over again. So far I have had to remove them out of the task, delete the task XML files on their PCs and do another policy sync to get it to stop.

Has anyone seen this with 9.6 SP2 using Policy Support push? Normally if a package ran again the user would have no clue but since this one prompts them, it is very obvious to them that something isn't right.

Environment

8.x

9.0

Description

Access is denied using Software Distribution from a UNC share

UNC Shares require credentials to be accessed by default.

When a LANDESK agent attempts to access a UNC share during a Software Distribution task, it uses the Local System account.

Scheduled Tasks or Software Distribution jobs result in the error "Unable to  Access the Package" or "Access is Denied".

An error 207 may also appear in the SDCLIENT.LOG file on target workstations.

Resolution

For 8.7 and Later configure a Preferred Package server for and enter credentials to the UNC share.

For more information on configure a Preferred Package servers: How to Configure a Preferred Package Server

Use an HTTP path instead of the UNC share make sure to allow anonymous access.

If a UNC share is required:

1.    Add the Domain Computers AD group to sharing and security permissions.
     a.  Test the UNC share with the AT command from client machine.

          For more information on this How to open a command prompt running as Microsoft's "Local System" account?

2. Setup the UNC package share as a null session share on your server.

Use the SYSSHRS.EXE utility found in the LDMAIN\Utilities folder on the Core Server to setup null-session shares.

          Follow these steps to ensure success:

               1.    Run the SYSSHRS.EXE program.
               2.    Make sure that all users have read access to the share.
               3.    Make sure packages are located at the root of the share.

For more information on null session shares, visit the Microsoft web site at http://www.microsoft.com and search on "null session shares"

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

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

We recently upgraded to LDMS 9.6 SP1 and we've discovered that none of our LDMS Operators that aren't part of the Administrators group can see "Reboot Settings" when checking the "Agent Settings" section of a Scheduled Task.  The only thing available under the Type column is "Distribution and Patch", which they are able to change.  We've looked through all the roles, but can't seem to figure out which permissions we need to grant to make the "Reboot Settings" available.

Any input/guidance would be appreciated.

Thank You!

We recently updated out Landesk software to 9.5 (I think) and one of the brilliant new "features" I believe is there with the explicit purpose of pissing me off.

I finally gave in and decided to create an account so that I can suggest that whom ever had AND approved this ideal be tarred and feathered. (extremely mild punishment compared to what is in my mind)

The "feature" that I'm referring to is how in the portal manager I can select a dozen items for installation and if I'm one pixel off on clicking the microscopic check box every thing else that was previously selected is now unselected and i get to start all over again... yay!!! (sarcasm)

I'm hopping against hope that there is some sort of fix for this...

PS. I image most of the computers where I work so this can happen to me 30 times a day.

Hi all,

I'm trying to deploy Microsoft Office Standard 2010 via Landesk whilst automatically activating the product. The Office package appears to be installing fine with the product key but when I try to access an application after installation, I receive a pop up window prompting me to activate the software. I have already amended the .msp file to include the product key and I also inputted a setup property to attempt AUTO_ACTIVATE and this didn't work. I have even tried creating a batch file to run cscript to try and activate the ospp.vbs file which Office imports upon installation and this doesn't work remotely but when I access the PC and run the batch file manually, the software activates without any problems. Does anyone have any ideas to get the software activated without any user input?

I've built a new package to deploy Office 2013 Standard, but it isn't deploying correctly.

We have an existing Office 2010 deployment package that works well, so I used it as a template for the 2013 package.  Just updated the .msp and the batch file to point at the new stuff.  I've attached a copy of the batch file I'm using to run it all.

Basically it does the following...

1. Unpack a .zip to C:\media\office2013win\
2. Copy the .MSP to C:\media\office2013win\updates\
3. Run setup.exe

If I run the batch file manually, it does exactly what I expect it to.

If I use LANDesk to deploy the batch file it will download all the files correctly, unpack things to C:\media\, and then just kind of hang there doing nothing.

It appears that setup.exe, even with a .msp that's configured to run silently, isn't actually running completely silently.  Despite the .msp attempting to completely suppress the UI, I'm still getting a brief splashscreen when setup.exe kicks off.  This did not happen with 2010.  I'm guessing that setup.exe is still trying to run in some semi-interactive manner, which is causing issues since it is running as the LocalSystem account.

I can confirm that the .msp is being processed, since the right options are installed with the right license key.  But it doesn't seem to be running completely silent.

Has anyone else run into this issue?  Does anyone else have a working Office 2013 deployment package?  Is there something obvious I'm doing wrong?

We have been using Landesk 9.0 SP3 until recently. We just upgraded to LD 9.6. SP2. I have a software distribution for Office 2010 using a bat file in a script. I understand that we shouldn't be using scripts any longer. How can this be done using a distribution package method?

Can someone tell me what the following mean sand how I find the issue

Task failed error  "the remote application has not completed, operation timed out 1410"

Thanks

Steve

LDMS 9.6 SP2

I have created a Software Distribution Task to cache the installer, which works just fine, the packages get in to the client with no problem.

Then I'm creating a second task to publish the application in the portal, works well, it completes and shows in the portal.

I then select the application and click the Launch, for which the LANDESK installation message appears and I select Install.

At this point the installer bar shows in the upper right corner as it should

But it just hangs in there, nothing else happens. This is I think because the exe requires user interaction, and the UI is hidden, since this is not an msi, the option to show the full UI is not available in the task.

Is there any other way to do this?

I look at this doc SDCLIENT.EXE Command Line Switches but I do not know if is the right way or how to implement it.

Your help is appreciated.

Thank you.

LDMS 9.6 SP2

While deploying a Software Task, I got the following error:

Fri, 19 Jun 2015 15:01:09 ******* sdclient starting to process task *******

Fri, 19 Jun 2015 15:01:09 Task id to process: 7157

Fri, 19 Jun 2015 15:01:09 Command line: /policyfile="C:\ProgramData\LANDesk\Policies\CP.7157.RunNow._d4Py+ULepep7zLf5LNWLnz8KRs0=.xml"

Fri, 19 Jun 2015 15:01:09 The nostatus flag has NOT been set.

Fri, 19 Jun 2015 15:01:09 Core name 'myserver' obtained from active task list

Fri, 19 Jun 2015 15:01:09 Sending task status, cmd line -coreandip=myserver -taskid=7157 -retcode=229392442 -pkgid=1014

Fri, 19 Jun 2015 15:01:09 File (http://myserver/SoftwareDistribution/npp.6.7.8.2.Installer.exe) is not in cache

Fri, 19 Jun 2015 15:01:09 The nostatus flag has NOT been set.

Fri, 19 Jun 2015 15:01:09 Core name 'myserver' obtained from active task list

Fri, 19 Jun 2015 15:01:09 Sending task status, cmd line -coreandip= myserver -taskid=7157 -retcode=229392444 -pkgid=1014

Fri, 19 Jun 2015 15:01:10 About to call DownloadFiles (1 files) with these settings:

Fri, 19 Jun 2015 15:01:10 m_allowedBandwidthWAN: 50

Fri, 19 Jun 2015 15:01:10 m_allowedBandwidthLAN: 75

Fri, 19 Jun 2015 15:01:10 m_discardPeriodSeconds: 604800

Fri, 19 Jun 2015 15:01:10 m_preserveDirectoryStructure: 1

Fri, 19 Jun 2015 15:01:10 m_bUseWanBWForPush: 0

Fri, 19 Jun 2015 15:01:10 m_bSynchronize: 0

Fri, 19 Jun 2015 15:01:10 Allowed download methods(m_downloadControl):

Fri, 19 Jun 2015 15:01:10 PeerOneSource

Fri, 19 Jun 2015 15:01:10 Peer

Fri, 19 Jun 2015 15:01:10 Source

Fri, 19 Jun 2015 15:01:10 m_preferredServerControl: AttemptPreferredServer

Fri, 19 Jun 2015 15:01:24 Updating system environment variable LDMS_PREFERRED_SERVER: myserver

Fri, 19 Jun 2015 15:01:24 The nostatus flag has NOT been set.

Fri, 19 Jun 2015 15:01:24 Core name 'myserver' obtained from active task list

Fri, 19 Jun 2015 15:01:24 Sending task status, cmd line -coreandip= myserver -taskid=7157 -retcode=229392444 "-message=1%" -pkgid=1014

Fri, 19 Jun 2015 15:01:37 The nostatus flag has NOT been set.

Fri, 19 Jun 2015 15:01:37 Core name 'myserver' obtained from active task list

Fri, 19 Jun 2015 15:01:37 Sending task status, cmd line -coreandip=myserver -taskid=7157 -retcode=229392444 "-message=100%" -pkgid=1014

Fri, 19 Jun 2015 15:01:40 DownloadFromSourceSteps: DOWNLOAD_ERROR_GENERAL_FAILURE

Fri, 19 Jun 2015 15:01:40 Download Error: err=1, path=http://MyServer/SoftwareDistribution/npp.6.7.8.2.Installer.exe

Fri, 19 Jun 2015 15:01:41 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)

However I have other files being downloaded with the exact same properties (in the task) location and local account, that ran just fine.

Are there any other troubleshooting steps that I need to take?

Regards

I have a LANDesk Power Users and when they view the "Scheduled Tasks and Policies" option on a device in the Console they can only see the tasks that are Public Users or their own tasks.   Is there a user setting that will allow them to see all the tasks and policies regardless on the owner?

Thank you,

Jim

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?

I keep getting this error "Download failed file not found at source(1)" "Download Error: err=11, " when trying to run a batch to execute some Office patches in a package. There is only like 7 Office patches i want to run on the computer through a batch file. The files are on the Preferred Server and in the same location as my other packages. I'm not sure why its telling me file not found at source?? Any ideas?

Thanks

How to:

You may have already deployed a scheduled task on some clients to be run at the Next Logon (See below the settings concerned for LDMS 9.5 & 9.6).

You hadn't got the time to press on Cancel button in Schedule Tasks menu, when you realised that the package wasn't correct and the tasks are already on Pending/Delayed Status on your Scheduled task in the LDMS Console (See below).

Hence, you'd like to prevent these tasks from launching for each client on Pending Status at the Next Logon.

Step by Step:

This is entirely possible by simply delete a registry key value which is created on each client for this the purpose of running the deployment after the Next Logon. These keys are either;

For 32 bits clients; HKLM - SOFTWARE - Intel - LANDesk - LDWM - Distribution - sdclient

or,

For 64 bits clients; HKLM - SOFTWARE - Wow6432Node - Intel - LANDesk - LDWM - Distribution - sdclient

The value of this key value looks like;

/p="\\CORE95SP3.sebdomain.local\ldlogon\Data\NotepadPlusPlus 655 silent.exe" /levels=3 /Hash=KG9YFoFvuv/DrnBUGPy9DQ== /pkgid=1008 /pkgname="NOTEPADPLUSSilent"
/FileListName="taskmanifest.CORE95SP3.1016.1008.ini" /FileListHash="fLNBblwNVcgWFawN/oU9xQ==" /exe /N /An /nopeer /nopref /nosource /wan=25 /lan=75 /taskid=1016 /taskName="NOTEPADPLUSSilent
 - 23/06/2015 02:15:46" /core="CORE95SP3:10.1.1.112" /sad=50 /runfromsource /EnableVirtualAppShortcuts /enableloggedoffuserinstall  /dmname="Standard push distribution AFTER LOGIN" /dmtype=3 /E

Then you need to delete these registry key on each client. For that, you may deploy a batch package on the clients concerned and run the following code with the System User;

REG DELETE HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intel\LANDesk\LDWM\Distribution /v sdclient

Then you can also remove these Pending machines from the Scheduled task to make it clean or even delete the scheduled task if you need to.

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=""]

Hi, we have LDMS 9.6 SP1 and are currently using it for patch and manual software deployment.  I am looking to begin taking the 1st steps with provisioning but before I get into OS deployment, I want a solution to automatically install a group of corporate apps to systems newly joined to the domain.  I have read many suggestion but want to make sure I adhere to best practices in 9.6.

What is the best way to accomplish this?

System configuration in OS deployment?

A distribution package scheduled task?

I forgot to mention, we currently deploy the Agent initially with GPO plus then our apps, We have had some issues with AV and I now understand that the issue is most likely interference with the LDMS agent and AV so we will deploy the LDMS agent with GPO, then Landesk will install the rest of the apps including AV.