I would like to open a discussion about software distribution with LANDesk and the User Context. I have read some pptx from LANDesk explain that the user will be centric on the next product version. I hope, because now it's not really the case. I will explain why based on a true case study I'm facing today.
Big company, worldwide (80 sites / region), 10'000 devices and around 350 business appications. A majority of these applications have some settings that need to implement into the user context, means some registry settings HKCU, some INI, XML file in the user profil, etc...
The solution we are trying to implement is using one MSI SD package. This packages will run in the system context. Then to apply settings based on the user, another package (VBS) will put the user settings and of course will run in the user context. And then doing a scheduled task, that will run in the main package the MSI and in the final package the VBS. It works quiet fine, but with that we cannot handle all different scenarii.
- First of all if no body is logged on, the task failed (VBS) it's difficult to debug and to know what is true or not...
- Second if another user is logged on, the user part of the packages will not apply.
- Third, if the settings change after installation. For example, we have some application that need to have the user connexion server in a HKCU key. If we migrate the server how do we distribution the users settings update??
I'm sure you are thinking about login script, GPO or GPOP. But not really. The problem is, applications that need user settings, are often site based, means we need to create around 350*80 GPO (in the worst case). Not really a solution. And I do not talk about the Login script (something like 50 pages!). Jmac tell me also that you can change the shortcut of the applications to apply settings, yes it works. But if you need to build a new MSI with specific shortcut, I prefer to use Active Setup, more efficient. In short term, the way we find, is to use the AD to store the applications settings, then the VBS will query the AD to get settings and finally we put Active Setup for the next user login.
The question is what is the answer / solution with LANDesk. Is there some way to do all or some of this tasks? I'm alone to want to use LANDesk in that way?
Please, I'm waiting about you comment, remark, opinion or criticism