Viewing application deployment types takes a long time, up to a minute or more, due to inefficiently authored WQL in .\XmlStorage\ConsoleRoot\SoftwareLibraryNode.xml.

When you find this WQL:

SELECT dt.* FROM SMSDeploymentType AS dt JOIN SMSCIRelation AS rel ON dt.CIID=rel.ToCIID JOIN SMSApplication AS app ON app.CIID = rel.FromCIID WHERE app.CIUniqueID='##SUB:CI_UniqueID##' AND rel.relationtype=9 ORDER BY rel.Priority

and replace it with this WQL:

SELECT dt.* FROM SMSDeploymentType AS dt where dt.CIID in (Select rel.ToCIID from SMSCIRelation AS rel where rel.FromCIID in (Select app.CIID from SMSApplication AS app where app.CIUniqueID='##SUB:CI_UniqueID##') AND rel.relationtype=9)

in SoftwareLibraryNode.xml, data returned is identical and viewing application deployment types is reduced to 1 or 2 seconds or so.

Is it possible for Microsoft to re-evaluate their WQL queries so it will result in more efficient SQL-behind?

FYI: The original WQL will result in this SQL query:

select all dt.CIID,dt.LocaleID,dt.ApplicabilityCondition,dt.AppModelName,dt.CIID,dt.CIUniqueID,dt.CITypeID,dt.CIVersion,dt.ConfigurationFlags,dt.ContentId,dt.CreatedBy,dt.DateCreated,dt.DateLastModified,dt.EffectiveDate,dt.EULAAccepted,dt.EULAExists,dt.EULASignoffDate,dt.EULASignoffUser,dt.IsUserCI,dt.IsBundle,dt.IsEnabled,dt.IsExpired,dt.IsHidden,dt.IsLatest,dt.IsQuarantined,dt.IsSuperseded,dt.IsUserDefined,dt.LastModifiedBy,dt.Description,dt.DisplayName,dt.CIInformativeURL,dt.LocaleID,dt.ModelID,dt.ModelName,dt.NumberOfDependedDTs,dt.NumberOfDependentDTs,dt.PermittedUses,dt.PlatformType,dt.PriorityInLatestApp,dt.SDMPackageVersion,dt.SedoObjectVersion,dt.SourceSite,dt.Technology
from fnListDeploymentTypeCIs(1033) AS dt
INNER JOIN vSMSCIRelation AS rel ON dt.CIID = rel.ToCIID
INNER JOIN fnListApplicationCIsList(1033) AS app ON app.CIID = rel.FromCIID
where (app.CIUniqueID = N'##SUB:CIUniqueID##' AND rel.RelationType = 9) order by rel.Priority

The updated WQL will result in this SQL query:

select all dt.CIID,dt.LocaleID,dt.ApplicabilityCondition,dt.AppModelName,dt.CIID,dt.CIUniqueID,dt.CITypeID,dt.CIVersion,dt.ConfigurationFlags,dt.ContentId,dt.CreatedBy,dt.DateCreated,dt.DateLastModified,dt.EffectiveDate,dt.EULAAccepted,dt.EULAExists,dt.EULASignoffDate,dt.EULASignoffUser,dt.IsUserCI,dt.IsBundle,dt.IsEnabled,dt.IsExpired,dt.IsHidden,dt.IsLatest,dt.IsQuarantined,dt.IsSuperseded,dt.IsUserDefined,dt.LastModifiedBy,dt.Description,dt.DisplayName,dt.CIInformativeURL,dt.LocaleID,dt.ModelID,dt.ModelName,dt.NumberOfDependedDTs,dt.NumberOfDependentDTs,dt.PermittedUses,dt.PlatformType,dt.PriorityInLatestApp,dt.SDMPackageVersion,dt.SedoObjectVersion,dt.SourceSite,dt.Technology
from fnListDeploymentTypeCIs(1033) AS dt
where dt.CIID in (select all rel.ToCIID from vSMSCIRelation AS rel
where (rel.FromCIID in (select all app.CIID from fnListApplicationCIsList(1033) AS app where app.CIUniqueID = N'##SUB:CIUniqueID##') AND rel.RelationType = 9))

Important: Be sure to replace ##SUB:CIUniqueID## with your applications CIUniqueID which can be viewed in the console by adding the 'CI Unique ID' column.

Some of our customers work in the application model with available deployments. They would like to let the employees choose which application they want to install, but the update should be installed automatically if the user has already installed an application himself via the software center.

Let's assume that with the help of Supersedence we update Application with name "Av1.0" with a second Application named "Av1.1" via available deployment. Then the supersedence should recognize whether the product assigned with the help of the available deployments was installed on a client and if so, the update should take place automatically. if this is not the case, only the new version can be displayed in the software center (as the behavior is now)

Please put in Event based deployment versus Time based deployment based on file/registry/Event log change. The deployment date should be used as the absolute earliest the event could take place. The expiration date should still hold true.

The action could possibly happen on a single device, but need to occur to devices within a boundary/collection.

The usage scenario is when a computer device is being used in a 24 hour retail setting, and the maintenance window is dependent on when the retail location determines a time in which it can take such action. The retail store may only have a single device that's given the signal that such action should take place on all of its devices.

I always have three version of Flash to import. Flash for Active-X, Firefox, and Chrome. I'm just using Flash as an example.

All of the installers are .msi I'd like to create a folder called "sources" place all of my .msi files in the "sources" folder then click import. The import wizard would import all of the .msi applications and place the source .msi in a target folder automatically for deployment. Maybe include a template in the import wizard. The template would be the same for all imported .msi applications. Example install for Device, Only Show notifications for restarts, Silent/Hidden install etc.