Following my Hospital's update to LANDesk 9.5 SP1 a couple weeks ago, I found that NONE of our PCs were installingORrebooting after the package deployment of our new agent when pushed. On top of that, NOpushedreboot scripting/config would force the needed Desktop level restart to complete the Agent installation post9.5 SP1 enterprise upgrade.
Issues I found:
- ALL script & package deployments failed across the enterprise environment post 9.5 SP1 install, starting with the Agent itself.
2. Restarting the LANDesk core, Replication Servers, and all pieces between resulted in nothing at all...
- *No WSUS or enterprise security changes were made between the SP implementation time frame and the eventual Ad-Hoc resolution*
3. Researching on the LANDesk support site, Google, MSDN, and numerous other sources seemed a waste of time.
4. After a week straight of tearing apart/ decompiling and re-engineering the Raw LANDesk Agent & respective .ini (in the uncompiled form using Orca & Installshield Premier Edition)... I realized the .Ini & .MSI were missing the traditional properties or component logic of a simple embedded */Force* reboot command flag.
5. The .ini was only listing the Agent settings generated by the Admin build console. (which didn't have theforcedreboot command at all...) only the "Reboot if needed" which never occurred when pushed.
- Following this discovery, I ended up adding the needed properties directly to the .ini & .MSI *copied off the Core prior to alteration of course*
![]()
- Added the string execution sequence to the .ini, and then left it alone (Uncompiled) until I got a hold of the LANDesk Support group to validate my freshly coded fix. **Side note: if you make any direct changes to the test Agent via the console, it will remove any changes and rewrite your .ini**
After we spoke to the support rep at LANDesk for quite some time. We ended up going line by line in the Agent Config tool, assessing the the Core config remotely, and performing a WEBex session to prove my point of the 100% failure rate on our Win 7 x64 & Win XP systems, being executed directly from the Core or an Admin console. He had to get a "Senior engineer" to inquire with regarding my coding questions he couldn't answer, I was told they'd get back to us the next week.... However, 20mins after I hung up, I received the following message via email from their Senior engineer, verifying the voracity of my initial assertion that the only way the Agent was going to reboot EVERY TIME *thereby completing the Agent install*, was todirectly edit the .iniand add the logic in manually..... priorto the compiling of the Agent executable.
|
Cheers!
JDrucks
- Sr. Application Infrastructure Engineer
- LANDesk Admin