Quantcast
Channel: Ivanti User Community: Message List
Viewing all articles
Browse latest Browse all 12704

Re: Categorising software distribution.

$
0
0

Casper,

 

So one of the limitations of bundles/groups is that it does not support alias/forking. So for the distribution package if you use the dame distribution package in multiple bundles, this creates a management nightmare when you have to change the distro package. For this I would vote on the following ER SWD - Package Bundles - Allow package "aliases". Grouping is great for organization but the console's search feature only does one level, so keep this in mind when considering deeper hierarchies. Some of the issues can be softened by using a strict descriptive naming convention for distribution package, scheduled tasks, bundle/group, and category names. For OS determination you could name your distro, sched tasks, categories with OS name. So a scheduled task name of something like

 

NLGO - Global - Citrix - Install - Not sure what date is for - W7

 

So that way when you search for the object using the all branch you can eyeball the task and see where it belongs. It would be better if there was a column for group & the search supported multiple levels. Remember you can make the sched task as descriptive as possible and what is displayed to the user is from the distribution package. Categories is also another way to filter the scheduled tasks in the DM/Portal Manager.  Currently we decided to stay away from sub grouping in lieu of more specific naming. As far as packages for multiple os, it may take somewhat longer to package for multiple OS, but it is well worth it. A great simple and free tool for this is Inno Studio.Inno Setup make sure you download the IDE QuickStart Pack. I did a Lync package for multiple conditions OS with only a few lines of code.

 

As far as LDAP targeting from a DAL, this does have limitations. 1. You have to rely on the inventory record being accurate and then waiting for the core to resolve (LDAP group Enumeration on the client should happen much quicker and the load is somewhat dispersed onto the clients). 2. If you need combine LDAP/DAL tyoe query you can target based on LDAP and use a prereq query for other inv items.


Viewing all articles
Browse latest Browse all 12704

Trending Articles