Kakemonstre

On the end of the main query, I not sure you can use the CASE statement like that. I would try to replace it with a "...AND SQL.Version0 in (@SQLVersions) then i would change the 3rd parameter query to return both the text value from the case statement and the version number. then use the Text for Parameter Name and the Versionnumber as value on the parameter itself.

OK ,looked at the query again and it might not be clear where to add collection sub query..... Best place to add it in the query above is on line 11 after the " vr.Operating_System_Name_and0 NOT LIKE '%server%' " part, before the parenthesis new line looks like this. FROM v_R_System vr WHERE vr.Client0=1 AND vr.Operating_System_Name_and0 NOT LIKE '%server%' AND vr.ResourceID in (Select ResourceID from v_FullCollectionMembership where CollectionID = @Collection) AS Total LEFT JOIN

See if this helps you out: http://larsenconfigmgr.blogspot.no/2015/04/how-to-add-collection-selection-to.html

Hi You have to use the "in" keyword when working with multi valued parameters. instead of "WHERE FC.CollectionID LIKE @ColID AND SQL.InstanceType0 LIKE @SQLInstanceTypes" use "WHERE FC.CollectionID in (@ColID) AND SQL.InstanceType0 in (@SQLInstanceTypes)" parameter has to be in parenthesis

It works when i publish to AD. had 2 more servers showing the same problem as the site server ,so i ended up publishing to AD. Just think it's strange that some servers manage to install the client just fine ,while other servers on the same vLan require site info to be published to AD.

This site does not currently publish to AD in fear of interfering with my CM2007 site. I push the client with the SMSSITECODE= FSP= AND SMSMP= parameters. hmman.log looks fine ,no errors or warnings.

Hi ,i'm trying to install the client on the site server ,the client installs ,but it can't locate its MP(MP is on another server). I have 2 other server in the same subnet where Push install works fine(Boundery is OK) ,Firewalls are disabled. This CM12 site does not publish to AD. This seems to be a problem only on the site server. This is from the location.log: Processing pending site assignment. Assigning to site 'C01' LSIsSiteCompatible : Verifying Site Compatibility for <C01> Retrieved lookup MP [MP.FQDN.COM] from Registry Attempting to retrieve lookup MP(s) from AD No lookup MP(s) from AD Attempting to retrieve lookup MP(s) from DNS Using default DNS suffix FQDN.COM Attempting to retrieve default management points from DNS Found DNS record of MP.FQDN.COM port 443 Lookup Management Points from DNS: Name: 'MP.FQDN.COM' HTTPS: 'Y' ForestTrust: 'N' Retrieved lookup MP(s) from DNS LSGetSiteVersionFromAD : Failed to retrieve version for the site 'C01' (0x80004005) Retrieved lookup MP [MP.FQDN.COM] from Registry Attempting to retrieve lookup MP(s) from AD No lookup MP(s) from AD Attempting to retrieve lookup MP(s) from DNS Using default DNS suffix FQDN.COM Attempting to retrieve default management points from DNS Found DNS record of MP.FQDN.COM port 443 Lookup Management Points from DNS: Name: 'MP.FQDN.COM' HTTPS: 'Y' ForestTrust: 'N' Retrieved lookup MP(s) from DNS LSIsSiteCompatible : Failed to get Site Version from all directories Won't send a client assignment fallback status point message because the last assignment error matches this one. Any idea?