What are the variables I can use in a batch file to run via Distribution Packages?
If I am sending additional files to the client for installation, where are these files going to reside?
In LDMS_LOCAL_DIR ? Are these additional files going to be purge automatically after the script runs?
Thanks
Need help in creating a group(s) or query that will automatically get software install.
For example: if I create a query using OU structure for HR, a new machine get deployed to HR and put into this OU then it will automatically get specific software install.
Is this possible?
Thanks,
hi,
I was trying to run a batch file to install some software on the clients using distribution packages. I want to prompt user before install, and allow user to delay. The prompt shows when I run policy.sync.exe as I was testing and wanted to be quick for the test process. The problem is, I tried every delivery method, including the "user-controlled installation" delivery method with "allow user to delay" and "prompt before install" options, when the prompt shows, no matter I choose to snooze or to deploy now, the icon at system tray comes out saying installing software and batch starts right away. WHY??? Is there anything I've done wrong?
We are using management suite 9.50.0.530. The client is Windows 7 Pro SP1 in english. The agent on client is 9.5 3-13.
Is anyone using package bundles? I am trying to deploy a bundle with 3 packages. The middle package needs to reboot before the final package is installed. I can't seem to make this work. Is anyone else doing (or attempting) this? Provisioning does not help me because this has to be a policy (in the swd portal).
-Tracy
Hi
I need a script/batch file I can run to collect info of what logon server clients are using to troubleshoot a routing issue
I was after something using the set logonserver command but want to put it into a veriable output
Either
set logon server >> \\path\%hostname%
or
output the machine hostnames with the result of a set logonserver to a file called the server name
or is there a better way anyone can think of?
Thanks
Colin
Using LDMS 9.5 SP1 and we are trying to troublshoot an issue with one of our delivery methods. We noticed that the dbo.deliverymethod table does not have any data in it. Is there another table we should be looking at to view our delivery methods?
Thanks,
Lance
Anyone create a a Cisco Anyconnect distribution package when complete has the built in hostname and AD child domain ?
It is pretty straight forward to create a .exe that can be distributed but this lacks hostname to connect to and the AD domain the account uses.
When you create the Cisco Anyconnect .exe using the Web portal a exe file is created but also a Cisco folder is copied to
%LOCALAPPDATA% C:\Users\{username}\AppData\Local . This holds information relating to the host to connect to and the AD domain. Is it possible using Landesk to copy a folder in a share to a user environment variable path like %LOCALAPPDAT% ?
We set up for all our Packages an uninstall Association. Now we made a few Package Bundle, which we deploy for selected Clients. Then we make a policy for these bundle. The installation works fine, but if we remove a client from this Task, the uninstall won't happen.
If I watch the sdclient.log from this task, it says begin Policy.Required.PortalRemoval. After a few seconds I can see in the log, task comleted successful, but the Software is still installed.
The funny thing is, when I deploy only one Software with the Delivery Method, install it and the remove the client from the task. The uninstall will work correctly.
Do you have made any experience with this behavior?
Best Regards,
Kevin
I am looking to leverage the portal manager in my organization on Landesk 9.5 sp1 to empower users to install approved software packages on their own to reduce demand on the Helpdesk.
The image will help give an understanding.
You can see that I am using the left most menu for applications. I am looking for a better way to organize as ultimately I suspect there will be 10-15 applications here.
Second, I have not been able to determine what the center pane under name, type, description etc. is for.
Can someone give me an example of how this portal could leveraged? I picturing major headings on the left under launch pad like Office Apps, Backup Ups etc that would populate a selection to the center screen for choices. Does this make sense?
Ultimately I am in need of some resources and insight into how to use this part of Landesk and what it can truly do.
Thanks in advance,
James
Wondering if anyone can help with this.
WinZip has to kill the Explorer Shell (desktop icons, start menu, etc) if it is being installed on a system that already has an earlier version installed due to the hooks it has in the 'right click context menu'.
If I run my WinZip package manually, the Explorer shell is killed and at the end, it is restarted, but if I run is via the LANDesk Portal, it is killed and does not restart. This is, I am 99% sure, because it is running a local system.
I know that if I bring up the task manager and type in explorer.exe it will restart... but users are not going to know that.
Add a command to to my package to restart explorer.exe does not work either when run via the Portal, again, because it is running as the local system.
Does anyone have a work around?
Since we went to 9.5 SP2 we are unable to delete package bundles. I can create a new package bundle without any distribution package and when i try to delete it i get the following message (please see picture).
Versions effected: LDMS 9.0 SP3 and newer
Problem:
Scenario: Configured policies (not policy supported-push) with a reschedule "daily" (Or Hour, Week, Month) and the option "Devices that did not succeed".
When running the task unfortunately the second option is ignored completely. The package is installed every day on every client even on the successful ones. Is this option not supported for policies or is this a bug?
Cause:
This process is working as designed.
As the delivery method being used is a policy as opposed to a push, this acts like a pull from the client to the core. The client will not have access to the task on the core letting it know if it has been successful or not. And as such when the task runs again, the package will be made available to the machine again for installation. And the core will then install the package again.
Whereas a push, pushes the package from the core to the client, with the core having all knowledge of which machines have been successful and which ones have not.
Solution:
To use a push delivery method as opposed to a policy one. The reason is described above.
More information about delivery methods can be found in this article:
Another solution is to use query based distribution, this will then only install the package to machines which do not have the package installed as realised by the query. (If configured correctly)
If you use this method it you can use the following framework to both monitor the installation of the package and distribute it.
Query based distribution:
It is recommend that you read this article for further information on how to create a query so you have a better idea of the framework that I am going to describe:
Create two queries. One that finds the computer without the package installed and one which shows you which computers have the package installed.
Here are some examples of the Query based distribution framework solution:
Here are the two different queries. I have put them in a separate folder for easy administration. As described before the 'Installed' Query will help me monitor the rate of package distribution as the other query is used in the scheduled task package distribution.
This is an example of the installed query, use this as an example for creating your specified to your task and environment
This query will help you monitor what the distribution package has been successfully installed on.
This query is an example of a query you can use to help identify nodes that do not have the package that you want installed on them. Now we have to be careful here as a poorly configured query can give us issues when distributing this package, for example distributing to OS's that do not support the package or servers that you do not want having it. For example the above query will give the following result:
As you can see from this return of the query that some of the machines being brought up are not compatible with the software (Mac OS X) or not desired (Microsoft Windows Server.)
By customising the query further we can eliminate this problem and only target the machine which are compatible and desired:
As you can see I have added two more select statements to help specify what machines i am targeting.
Note that I have used an 'OR' Boolean when selecting the OS this because a windows OS cannot be both windows version 7 and 8
Query return now:
That’s much better the query is now specific and now will only target machines that we want it to. This is why we have to be careful when creating these queries for use in this method as we do not want to target machines that will always fail or that might require a reboot or is not needed, on servers.
Once this queries have been created drag them on to your scheduled package distribution:
Run /Start the task and then your targets will appear:
Now you have complete the customisation and can use any delivery method that you wish and any time interval for the automatic reschedule of the task.
If I wanted to create a role where a console user could only add and remove machines to an existing task and then be able to deploy that task how would you assign that permission? I don't want them to have any access to Distribution packages, Direcotry Management or Delivery Methods the admins will build all that one the back end. Just need techs to add machines to a task and start the task.
Hi ,
I'm sequencing LANDesk management console 9.5 SP1 using APP-V 5.0.when i install the application locally it's working fine.But after sequencing i'm getting below error when i launch and enter my credential.
Could you please suggest why i'm getting this error.
Regards,
Maheswaran
Environment:
LDMS9.5 SP2
client OS : Win8,Win7, and XP
Description:
You want to deploy a package via policies so your users are prompted before downloading or running package .
Although the policy is configured correctly you notice than the package installs without prompting the user
Steps to Duplicate:
Display progress to user UI : Display progress to user
Allow the user to delay runningthe package
Promot user before downloading package....
Prompt user before running package.
2. Created a scheduled task for a package and associated the policy to that task.
3. Started task
Solution:
Defect was created TFS126028
Please monitor the release of a Patch from http://community.landesk.com/support/docs/DOC-27264
As a workaround you can use a push
Environment:
9.5 Service Pack 1
Description:
Option to "Delay until next logon" is not working as a policy
Steps to Duplicate:
Configure a policy delivery method with the deferal option selected of, "Delay until next login"
Execute a task using the policy delivery method you just configured
On the core side you will see a message saying that the task is waiting for a logon.
On the client side you will see that a local task has been created with filter OS event logon
Log off and log back in on the client
Actual result: The policy does not run
Expected result: The policy will run
This is a known defect. TFS# 88174 and is address in SP2
Workaround:
Push delivery methods are working as this is only affecting policies.
I am somewhat familiar with building distribution packages, only a built a few. I soon will be faced with uninstalling Adobe 9x from 120 machines, and reinstalling Adobe X.
Can someone help me navigate the proper way to do this?
If I select 3 applications from Portal Manager and then launch the distribution, Portal Manager crashes. Anyone else seen this?
I cancelled a batch task deployment. But the machines still show as active. the weird thing is that these machines are not on. And since the task has already been canceled, I cant not cancel it again. Should I just delete the job or will it still try to run when the machine does come online. If I delete the machines,it comes back.
I am on LDMS9 SP4.
I am looking for a way to configure up tasks/delivery method/whatever to get package installation a certain way. I am testing v9.5 SP2, but can't find a way to work this.
I want to be able to have a task, that when it kicks off on the client, is initially silent, the files associated with the task are downloaded\cached locally, and only then it automatically prompts the user to run the installation. So, not the pre-caching feature in Delivery Methods which doesn't run the installation, but something like it that then DOES run the installation. All in one step.
I have a user base that travels a LOT. And I don't want to prompt the user to close an application to install the something (say an Adobe Acrobat update)., then have to wait a long time until the package is then downloaded over a slow link before it actually installs. If you have several of these this can make the user wait a long time before the download and install are done before they can use their app again.
Any ideas how this can be done with the newest version?
Thanks!