Just in case as I've seen this a few times recently with bundles. Does the bundle also include theuninstallation for the applications? I've seen afew times now where the bundle is being used as a group and without realising it has been deployed as a bundle which installs and then uninstalls the same package.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality
No. In this case we look all the software packages that would be installed through provisioning and split them off into bundles. The idea was to create a modular group of core and optional software bundles that could be used across provisioning tasks. If we decide to add or remove an application from our core software group, we only have to change the bundle, not all the OSD provisioning tasks that use it.
I set the bundle as a scheduled task and tested it on a system without any of the software included in the bundle installed. Delivery method is set to "Push", "Standard push distribution". When the task is started, a "software deployment" window pops up on the target system. Once the countdown timer completes or the "deploy now" button is clicked the window closes and the target system moves to the "Successful" status with a return code of 16385. No software from the bundle is installed.
We have resolved the issue. The bundles will not work with certain characters in the name. The bundles we were using were named Standard Apps for non-lab PC's and Core Apps for all PC's. After removing the apostrophe from the name the bundles are installing correctly.