Hi,
We're using LANDesk to deploy Lync 2010 to end users. Deployment runs fine, everything gets installed but when a user logs in for the first time, a lync post-install is trigerred.
If the installation was done minutes before, there is no problem but if the sdmcache was cleared then users get the error below. is there a way to avoid this?
we are using LANDesk 9.0 SP3
Thanks
Jo
I have a package that has 12 dependant packages. So far the it installs just fine. Its a mix of Batch File, MSI, EXE, and Script packages. I am faced with two minor problems.
I am running 9.0 SP3, has anyone seen this erratic behavior? I am staying away from Provisioning for this as it is a task that will go out to a couple thousand production machines for a major application upgrade. Provisioning is not very customer facing friendly, I wish they would fix that window to be more customizable and intuitive of what is happening. 9 times out of 10 users freak out and call the help desk when they see it pop up!
I do hope that there is maybe a patch and that this does not happen in 9.5. I will test that later this week in my 9.5 test lab.
I have the Desktop Manager implemented so that end users can download and install software on demand. Everything is set up and works great except... it takes FOREVER to update. It takes about 10 minutes from the time I open the Desktop Manager until it starts "Synchronizing with Policy Server", which takes another couple of minutes. This is not really a huge deal, but it a major inconvienence which is preventing people from using the Desktop Manager. It just sits there saying (Not Responding) for over 20 minutes, and most people just kill it thinking it doesn't work. Is there anything I can do to optimize or speed up this process?
I'm on LDMS 9.5, no users are local to the core. About 10% of users are on VPN (including myself), the rest connect remotely the the management gateway. I have not done much testing, but I'm going to assume the timing is longer for those connecting through the gateway. I have less than 10 SWD policies. Thanks
We've recently upgraded from LDMS 9.0SP3 to 9.5, and I am having an issue with a PowerShell Distribution Package.
This PowerShell script worked fine under 9.0SP3 and ran successfully on approximately 300 Windows 7 workstations. Today, however, it is not working properly.
LANDesk marks the scheduled tasks as "successful", but the script is not running successfully.
There seems to be an odd issue associated with the execution policy... If I set the package to run as the "current user's account" I'll see the PowerShell window pop up briefly, and the script will run correctly. if I set the package to run as the "localsystem account" I'll get a brief message in the taskbar that indicates a process is trying to get my attention, but it always disappears before I can do anything with it - and the script does not run correctly.
Additionally - I tried "set-executionpolicy bypass" to make sure that signing wasn't the issue (even though the script is signed)... And after trying to run the scheduled task my execution policy is set to "restricted". This is not something that I've got set anywhere in my script. The scheduled task appears to be changing it to restricted for some reason.
Again - this script used to work fine.
Any suggestions?
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
Hi there, trying to create a batch java package and I got return code 1. I tried searching but couldn't find the problem. Can anyone offer some insights? Thanks!
Description:
Scheduled Task failed with Unknown Status Code (0x8DB00FF,3504:255)
Cause:
Folder Tree containing addittional files is to0 deep
Resolution:
Shorten the length of the path to the files
I've tried searching for a response to this but think that I must be missing something. I am running Landesk 9.5 and working on setting up my software distribution tasks. I would like to change the query associated with a task and seem to be unable to do so. I found a few posts for older versions of the software (http://community.landesk.com/support/thread/19744) that stated the way to remove a query is to remove the targeted devices and select "yes" to remove the associated query...I have removed all of the devices from the task but the queries were not removed. The task is currently canceled, and under all devices there are two "Unknown" devices listed. I believe these are the queries themselves as other tasks where I have only one query setup have only one "Unknown" device listed. Unfortunately whenever I try to delete "Unknown" it disappears for a brief second and then pops right back up again. Any assistance will be greatly appreciated, and if this is already mentioned in the forums somewhere I apologize for not being able to locate it.
-R
Hi there, hopefully someone can help me. I read the guides on the 2010 deployments. After deployment from Landesk, I'm asked to activate the MAK license. Is there a way to make this activate automatically without having any user interaction?
IIS7 blocks access to files in directories of a particular name.
Error
The remote server returned an error: (404) Not Found.
Cause
The error occurs when adding additional files to a package from a web path that contain blocked segment (directories.) This only occurs in IIS 7.0 and above because IIS blocks certain defined segments (directories) in the applicationHost.config file. The lists below are the filtered segments (directories) being blocked.
Web.config
bin
App_code
App_GlobalResources
App_LocalResources
App_WebReferences
App_Data
App_Browsers
Solutions
1. To remove the hidden segment form the applicationHost.config add the following near the bottom of the file, with other location tags.
<location path="sitename.com/subfolder/bin/debug">
<system.webServer>
<security>
<requestFiltering>
<hiddenSegments>
<remove segment="bin" />
</hiddenSegments>
</requestFiltering>
</security>
</system.webServer>
</location>
2. To remove the hidden segment from with the share directory where the packages are stored, place the following lines of code in the web.config file. This is the recommended solution because this only affects the web share where the software distribution packages are being stored.
<?xml version="1.0"?>
<configuration>
<system.webServer>
<security>
<requestFiltering>
<hiddenSegments>
<remove segment="bin" />
</hiddenSegments>
</requestFiltering>
</security>
</system.webServer>
</configuration>
3. To remove the hidden segment from the applicationHost.config type the following command with the segment (directory) to be removed from being blocked.
C:\Windows\System32\inetsrv\appcmd.exe set config "sitename.com/subfolder/bin/debug" -section:system.webServer/security/requestFiltering /-hiddenSegments.[segment='bin']
4. Verify the HTTP Binding are not limiting connections to a particular method, (i.e. IP address, NetBIOS, FQDN)
Hi All,
Please let me know the process to put key in Adobe CS5 distribution package...
Hello,
I try to transfert the font file (file.otf ), but when i select the file to deploy, i have a popup
have you fix this problem ?
Thank's
Arnaud
Hi All.
I am Using these below HHT Devices
MC 3190,
MC3090 G
LXE Mx8
MC55A0
I like this software ,
so i want to test this software on MC55a0 Devices . so please suggest me is there any Demo version is available or not
if yes then please share the Software link and process to install it
thanks for your great support.
Regards,
Chander Sharma.
Hi
We have just downloaded the LANDESK 9.50 on a server. It is still running in trial mode. Im trying to test Distribution packages.
Im distributing a msi package. The destination has the new agent and it appears to be working fine. When I run the task it fails on a return code 105.
Here is an extract of what I see in the "view log file" option.
Processing package : Cisco VOIP Agent
Wed, 10 Apr 2013 10:14:23 File (\\-----\-----\------\-------\-------AgentDesktop.msi) is not in cache
Wed, 10 Apr 2013 10:14:23 Will attempt Peer Download.
Wed, 10 Apr 2013 10:14:23 Will attempt Preferred Server Download.
Wed, 10 Apr 2013 10:14:23 About to call DownloadFiles (1 files) with these settings:
Wed, 10 Apr 2013 10:14:23 m_allowedBandwidthWAN: 100
Wed, 10 Apr 2013 10:14:23 m_allowedBandwidthLAN: 100
Wed, 10 Apr 2013 10:14:23 m_maxDiscoveryThreads: 15
Wed, 10 Apr 2013 10:14:23 m_discardPeriodSeconds: 604800
Wed, 10 Apr 2013 10:14:23 m_preserveDirectoryStructure: 1
Wed, 10 Apr 2013 10:14:23 m_bUseWanBWForPush: 0
Wed, 10 Apr 2013 10:14:23 m_bSynchronize: 0
Wed, 10 Apr 2013 10:14:23 m_downloadControl: AttemptPeer
Wed, 10 Apr 2013 10:14:23 m_preferredServerControl: AttemptPreferredServer
Wed, 10 Apr 2013 10:14:45 processing of package is complete, result -1918107543 (0x8dac0069 - code 105)
Where should I be looking to resolve this and any ideas what my problem might be?
Regards
Mike
While working on setting up my software deliveries, I have run into an issue (maybe two) that I cannot figure out cause of.
Here is the setup..
- Core server is located at my home office with remote locations connected via MPLS (1.5 - 3mb pipes...low bandwidth). I am attempting to utilize UNC path preferred servers at my remote locations.
- Software delivery setup using a Policy method "Required Installation" modified to "Require high speed connection" with Peer Download, Attempt Preferred server, and Allow source selected.
Outcome..
Software deliveries fail to the remote locations due to "insufficient bandwidth". If I set the policy to just require "Non-Ras connectivity" then they succeed. I am guessing this is because the clients are not utilizing the local preferred server. I also tried installing the software on a machine (through a different non bandwidth aware policy) at the remote site so the client would utilize a peer download, however when looking at the task information on a subsequent failed install on another machine at that location, I do not see where it even attempted to download from a peer or preferred server (though I might be reading it incorrectly). There are two things I have noticed while looking into this that I believe may indicate where the issue is. Sometimes the preferredserver.dat file can be located on the clients, and does have the correct server listed in the file, however it looks like the preferredserver.dat is removed when the client attempts to utilize it. And when looking at the proxyhost.log I can see where the client pulls the preferred server.dat file down...but then it looks like it tries to connect to the server via http which fails because IIS is not installed on the preferred server since I am attempting to only utilize UNC paths in my deployments.
Sidenotes..
- Testing the credentials on the preferred server properties works and data replications succeed.
- I have attempted to rehash the Distribution Packages (and tried multiple different packages with the same result)
- Clients can ping the preferred server (and the firewall on the server is disabled at the moment)
- The UNC share paths are identical on the core and preferred servers.
- I am using FQDNs in my paths on the distribution packages and preferred server setups to avoid potential DNS resolution issues (\\servername.domainname\packages)
I'm not sure if the peer downloads failing have the same root cause as the preferred servers not being utilized, but I would like to correct both issues if they are separate. Attached are some of the log files that are relevant. I'm probably just missing something simple in my configurations as this is my first deployment, I just can't figure what I have missed. Any assistance is greatly appreciated.
I will be keeping a list of all updates that a customer using LaunchPad should apply. If you are using LaunchPad it is recomended to bookmark this article.
1. Make sure that SP2a is applied to the Core Server and Clients. There are several LaunchPad and Policy updates that can only be gotten from Sp2a.
http://community.landesk.com/support/docs/DOC-1001
2. The following update resolves an issue with LaunchPad links not working when an executable with more then 8 characters is used.
http://community.landesk.com/downloads/patch/SWD-1962988.2-2.zip
3. If you highlight a link in the LaunchPad Portal and then select the "enter" key everything goes blank for a long period of time.
Note: If you create a category called "favorites" this feature will not work. A "favorites" category has been pre-configured.
http://community.landesk.com/downloads/patch/SWD-2080188.2-2.zip
4. If a LaunchPad task leverages an LDAP user query and more than one person share a machine. The users that were not targeted for the task see the URL link.
http://community.landesk.com/downloads/patch/SWD-2080688.2-2.zip
5. Delta Scans with a Deleted Section for LaunchPad tasks, cause a 4100 Exception for the inventory server.
http://community.landesk.com/downloads/patch/INV-2123388.2-2.zip
6. NEW: Custom Icons are not showing up for web URL's in launch pad.
http://community.landesk.com/downloads/patch/SWD-2111488.2-2.zip
Note: This will only resolve the issue with new links. Not existing links.
NOTE: See the Best Known Methods for LaunchPad:http://community.landesk.com/support/docs/DOC-4454
This document describes how to deploy Windows XP Sevice Pack 3 using LANDesk Management Suite and a Distribution Package. This is most easily done using the patch content in Patch Manager, however, it is possible to manually create a distribution package. This document describes how to manually create this distribution package.
Download XPSP3 from Microsoft. Make sure to download the full version for network installations.
Put XPSP3 on the web share or UNC share where you packages are stored. If you have not created a web share or a UNC share, create one now. Remember that the Core Server and the agent workstation must be able to access this web share or unc share.
Run the executable with a /? or /help to obtain a list of the possible command line parameters.
You probably only want one switch: /quiet. But you may also want to use the /norestart if you don't want to reboot right away. Or if /forcerestart if you really want the restart to occur. If you no you don't ever want it uninstalled, you can add the /n switch to not backup files needed for the uninstall. Open a command prompt on a test XP box and try out the switches until you have the ones you want.
In the Console create a new Distribution Package of type executable.
Create a new Scheduled Task.
Important! The Service Pack has an option to extract the service pack first before deploying it. Using that method with LANDesk is only recommended if a Delivery Method is used that is configured to "Run from source".
LANDesk Community,
LANDesk has recently become aware of some issues where deploying SP2 to a LANDesk Management Suite 8.8 agent can cause the Policy Invoker to fail--preventing a machine from being able to download policies. At this time, the issue is sporadic and has only been seen in small subsets.
Currently, only policies are known to be affected. All other types of distribution methods seem to be functioning as designed.
If 8.8 SP2 has not yet been installed, LANDesk recommends at this time to not install SP2 until a new SP2 client patch has been thoroughly tested and re-released. LANDesk expects to have the client tested and ready for download by early next week.
If 8.8 SP2 has already been installed and clients have been deployed, please contact support for a patch that has been written to specifically address the issue.
LANDesk Support
***UPDATE 11/20/08***
Attached to this document is patch SWD-2025388.2-2 which addresses a number of issues surrounding the Policy Invoker. It is recommended that all 8.8 SP2 customers apply the patch. The fixes contained in the patch are outlined below:
• Pushing an agent with both LANDesk LaunchPad and HIPS caused policy.client.invoker.exe to crash
• Pushing an Updated SP2 Agent to an SP 1 agent will cause the invoker service to crash
• Policy.client.invoker.exe crashes with a Disk I/O error
• "Policy.client.invoker.exe application error at xxxxxxxxx referenced memory at xxxxxxxxxx" popup window on client when installing SP2 agent on device that also has console with SP2 installed
• On a Win2k8 Server and Windows vista with client pushed, clicking on deploy in distribution portal gives error that it can't display the webpage, because Policy.cgi.exe crashes.
• Launching some JIT links in Launch Pad could cause the invoker service to crash.##
For LANDesk customers that have not yet applied SP2, we will be releasing a slipstreamed version of SP2 in the next couple of days that will contain the fixes mentioned above. Vulnerability content will also be created and released by next week.
At this time, we have a few other known issues which will be addressed by mid-December.
• Policies do not show up in the Software Deployment Portal for user based LDAP targets (CR20128)
• Link Management is not working with name more then 8 characters (CR19629)
• Upgrading an agent via policy fails to register the policy.invoker file due to the file being in use at the time of registration (CR20188)
o A temporary workaround is being provided via the attached custom vulnerability V_INTL_CD-8608.xml.webloc. It will register the invoker and start the service.
o If an agent is updated via Patch Manager, the agent will install successfully.
Note: Applying the current SP2 and patch SWD-2025388 or the future slipstreamed SP2 SP will get you to the same point. Also, for customers who applied patch 14775 there have been two additions made to the final 20253. 14775 does not contain the fix for the distribution portal error on Vista and Windows 2008. Secondly, the command to force the client database to recreate itself was not in the patch.
****UPDATE 11/20/2008****
We have a report of an issue with the latest version of the patch. The issue does not seem to be causing significant issues but due to the nature of this patch we are investigating this throughly. If you are running an updated version of the Policy.client.invoker.exe there is no need to roll this back or take significant action at this time.
****UPDATE 11/21/2008****
The issue reported late last night has been resolved. We now recommend that all 8.8 SP2 users to apply the patch SWD-2025388.2-2. Attached are three files. Please see the readme.htm inside the setup folder for instalation information.
SWD-2025388.2-2 - Invoker patch
V_INTL_LD88-Invoker-20253-882 - Vulnerability for the SWD-2025388.2-2
V_INTL_CD-8608.xml - Vulnerability to register and restart the invoker service if an agent is installed via a policy
The above patch and vulnerability will be released into content later this afternoon. A slipstreamed version of SP2 will follow next week.
***Update***
Fixed the linked file V_INTL_CD-8608
***Update***
SP2A has been released internal to LANDesk. If the rest of the testing goes as planned, we should be releasing SP2A Monday the 8th.
***Update***
SP2A has been released into content. If you have SP2 installed but SWD-2025388.2-2 SP2A will detect as vulnerable. You can either patch your machines using SP2A or SWD-2025388.2-2 to remediate to the SP2A level.
Steps to create an SWD package to push out a shortcut to the desktop of a user</h2>
One of the more common software distribution tasks is to place a shortcut for an application onto a users desktop.
This is very easy to do using LANDesk Enhanced Package builder.
Please follow these steps:
1. Install the LANDesk Package Builder Software on the machine that you are using as the "Source" machine.
Browse to the "
YourCoreServer\ldmain\install\Package_Builder" directory. Run the enusetup.exe installer. This will install the Package Builder Software onto the target machine.
2. Once the software is installed, go to Start | Programs | LANDesk Management | LANDesk Enhanced Package Builder.
3. Click the New document icon or go to File | New to create a blank project.
4. Under BASE INSTALLATION choose File.
5. Click on the Select Files button as shown with the red circle above, and browse to the desired Shortcut file. In this case, we are pointing to a shortcut for Mozilla Firefox.
6. Click the Open button. This will place it in the window, but not in the above section.
7. Click in the Destination Copy to: box, and then select the System Variable button. This will pull up a list of available system variables. Select the $ALLUSERSDIR$ variable which is first in the list.
8. In the Destination Copy to: box, append \desktop to the $ALLUSERSDIR$. It will end up looking like this: $ALLUSERSDIR$\Desktop. This tells Package Builder to place the shortcut onto the desktop directory for all users.
NOTE: If the icon exists and needs to be overwritten select the Overwrite drop down and change from Default to Yes.
9. Click the Add button which will put the entry into the upper pane with a 0001 FILE: entry.
10. Click File | Save As... and save the project to a directory.
11. Click Build | Build
12. The Build Install window will come up.
Select the One File Install option, and specify a folder for the build directory. It will create the directory if it does not exist. The Build completed window will come up with the location of the SWD package.
It will be in the build directory specified, in a directory called "Onefile".
13. The resulting EXE file can either be run manually, or be pushed out through LANDesk using Software Distribution.
NOTE: When creating the Software Distribution Package the type of package must be an SWD package, and NOT an EXE package. Any package created with Package Builder must be an SWD package as seen below.
1. On the core server navigate to c:\program files\landesk\managementsuite directory.
2. Open the apmservice.ini and add a logging section and the the following value:
Keepevents=on
Should look like:
[Logging]
Keepevents=on
3. Stop and restart the APM service
Verify that the ldmain\sdstatus\stored directory was created. If the stored directory does not get created. Please create it.
4. Enable XTrace for sdclient
5. Rerun the policy or detached task
6. Check the sdclient log to make sure the status is being sent by sdclient.
7. Verify that the status XML file was forwarded by the alert service by checking the alert.log in the %ProgramFiles%\landesk\shared files folder. This log should list the status for the HTTP post to the core server.
Should look something like:
2009-03-03 22:30:10(5252-5544) alert.exe:Processing alert internal.192_168_0_15.swd_sdclient.status instance
2009-03-03 22:30:11(5252-5544) alert.exe:Alert transmitted to http://LANDesk.Gateway@192.168.0.15/incomingdata/postcgi.exe?prefix=sdstatus\&suffix=.swd.xml
8. Check the IIS log on the core for the HTTP POST results. Verify event is in the stored policy events ldmain\sdstatus\stored. Also verify that the event was not put into the badstatus directory (Ldmain\sdstatus\badstatus).
9. Check APMStatusUpdateHandler.exe.log for errors. (LDMS 9.0sp2 and later)
10. Check the version of the Core Server. The latest support packs must be installed. See Community article 1001.