Hi all, We are currently deploying applications as part of an OSD task sequence using the ConfigMgr Packages tab in the MDT database (integrated with SCCM). Our packaging team have imported some virtualised apps into SCCM and want to deploy those as part of the build process. From what I can see, the only option is to install them from an Install Software task in the task sequence since that recognises that there is no program associated with package. If I try to add a virtualised package to the ConfigMgr Packages tab in the MDT database I have no program to add to the XXX00000:Program Name pair, so am I correct in thinking that this is not a valid route and that the only way to do it is through multiple "Install Software" tasks? Thanks Simon

Hi, i have no experience with App-V packages in a task sequence, so don't know if that will work. When I try that it gives the message "Please select a program". The best way for this (in my opinion) is to create collections for every App-V package available. Then create application groups, put users in it, and add it to their own collection. Advertise the App-V packages to their own collection, and it should be functional. Have a look at this blog for that: http://henkhoogendoorn.blogspot.com/2010/12/configmgr-2007-with-app-v-integration.html My ConfigMgr blog: http://henkhoogendoorn.blogspot.com Follow me on Twitter: @henkhoogendoorn

If I try to add a virtualised package to the ConfigMgr Packages tab in the MDT database I have no program to add to the XXX00000:Program Name pair, so am I correct in thinking that this is not a valid route and that the only way to do it is through multiple "Install Software" tasks? There are programs for AppV packages, but they are not exposed to the console; they are named "[Virtual application]", so you could try "XXX00000:[Virtual application]", BUT: the progam flags for "Allow this program to be installed from the Install Software task sequence without being advertised" are not set. That could most likely be done using the SDK, but it still has to be tested if it works in that case. Torsten Meringer | http://www.mssccmfaq.de

Thanks Torsten, that's really helpful. Guess I should have looked in WMI first ;-) I've written Powershell/WMI code to manipulate the "Allow this program to be installed from the Install Software task sequence without being advertised" setting previously so I should just be able to utilise that. I'll give it a shot later but if it's going to work, I think this is the most probable way. Cheers Simon