You can use store procedures to build your app list on the fly similar to previous installed software method.
Script to add machine to collection though would work, it will take time to get policy and start the installation, plus, depending how many builds are concurrently SCCM will take a hit on collection refresh. Cesar A On Mar 31, 2015 3:57 AM, "Robert Spinelli" <[email protected]> wrote: > So client uses MDT to build all new machines, were in the process of > rolling out SCCM 2012, but the MDT team isn’t ready to integrate with SCCM > 2012 yet. > > > > What is the best way to get the machines to install the required > applications from SCCM during the MDT build without having to wait hours > for every collection to refresh? We base all our collections off of AD > group, so machine named Computer01 is in AD group Contoso\WinZip + 30 other > app groups. We have about 1000 collections, so can’t use incremental > updates. The only solution I can come up with is during the MDT build have > a script that adds Computer01 as a direct membership to all 30 collections > and then at the end remove that direct membership from each collection. > > > > They build about 100 machines a day which means each collection we hit > will update during the build which mean probably throughout the day every > collection in the environment will be updating, which seems like not a > great idea. > > > > Curious if anyone else has had to tackle this. > > > > Thanks > > > > Rob > >
