Comments on: Export & share MDT Applications (New Tool) http://deployment.xtremeconsulting.com/2009/11/06/export-share-mdt-applications-new-tool/ Fri, 12 Mar 2010 21:35:20 +0000 http://wordpress.com/ hourly 1 By: keithga http://deployment.xtremeconsulting.com/2009/11/06/export-share-mdt-applications-new-tool/#comment-123 keithga Wed, 09 Dec 2009 20:28:53 +0000 http://tmintner.wordpress.com/?p=169#comment-123 Thanks! Exporting apps from SMS/SCCM is a good idea. I'll add it to my list of requested tools. Keep the ideas comming. :^) Thanks!

Exporting apps from SMS/SCCM is a good idea. I’ll add it to my list of requested tools. Keep the ideas comming. :^)

]]> By: Rliving http://deployment.xtremeconsulting.com/2009/11/06/export-share-mdt-applications-new-tool/#comment-92 Rliving Thu, 03 Dec 2009 08:22:57 +0000 http://tmintner.wordpress.com/?p=169#comment-92 Hi Keith, Very nice tool! I like the application archive idea. I have a question related to packaged application sharing, but with a slightly different twist. At my work, we have a requirement to use the same SMS (SMS 2003 SP3) packages to build the Base Reference Images as we use to deploy out to existing clients. With some Program variations on Imager versions, meaning ones where we do not want any of the normal daisy chained reboot or program install notifications to occur during the automated image build. My question is, do you have a tool that could read the SMS db for a given ProgramID, and pull the install commands and source files (source files from a given SMS DP) for that program and any daisy chained programs. Then place that information into an imported able Applications XML (like what you’ve done here)? This would allow you to take advantage of the all the configuration and packaging effort that’s already done in SMS, within MDT and not have to Manually configure those SMS packaged applications. Thoughts? Thanks, Roy Hi Keith,
Very nice tool! I like the application archive idea. I have a question related to packaged application sharing, but with a slightly different twist.

At my work, we have a requirement to use the same SMS (SMS 2003 SP3) packages to build the Base Reference Images as we use to deploy out to existing clients. With some Program variations on Imager versions, meaning ones where we do not want any of the normal daisy chained reboot or program install notifications to occur during the automated image build.

My question is, do you have a tool that could read the SMS db for a given ProgramID, and pull the install commands and source files (source files from a given SMS DP) for that program and any daisy chained programs. Then place that information into an imported able Applications XML (like what you’ve done here)? This would allow you to take advantage of the all the configuration and packaging effort that’s already done in SMS, within MDT and not have to Manually configure those SMS packaged applications.

Thoughts?

Thanks,
Roy

]]>