Unfortunately that method does not give us the control we need. By scripting the SMSNomad calls I can control what packages are pre-cached when. For example, larger bandwidth intensive packages like the image and drivers are only pulled over the WAN on the weekend when these remote sites are closed for business, while smaller packages are pulled daily. Plus there are packages that are not needed in the Nomad cache in these remote sites. There are certain models that will not be in these locations so caching the drivers for those isn't needed.
Mike From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Wednesday, February 05, 2014 12:41 PM To: [email protected] Subject: [MDT-OSD] RE: SCCM 2012 R2 PowerShell - Packages Referenced in Task Sequence Why not use a separate task sequence instead? We do the same thing and just use reports to cross reference. We have a 'Pre-Cache' task sequence that includes any software that we use in OSD. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Marable, Mike Sent: Wednesday, February 05, 2014 12:26 PM To: [email protected] Subject: [MDT-OSD] SCCM 2012 R2 PowerShell - Packages Referenced in Task Sequence I want to know if I'm missing something in the native PowerShell support in SCCM 2012 R2. I'm looking to pull a listing of the packages referenced in a task sequence. With SCCM 2007 I have a script that uses a number of WMI queries to pull that data but I'm hoping to use the native commandlets if possible in SCCM 2012. The big picture is this. I need to write a script that will in essence, inventory our production build task sequence for all of the packages that are directly referenced. This list is then used to pre-cache those packages on a number of build servers that use 1E's Nomad Branch Cache. Checking the command reference on TechNet I'm not finding something that will generate this list. Using the "Get-CMTaskSequence" it will list the referenced packages but each one is buried inside a block of code. I could parse the package IDs out but it is starting to feel like a problematic rabbit hole I'm heading down. Before I updated my existing WMI script to make it work in SCCM 2012 I thought I'd ask the group in case I'm overlooking something. Mike Marable Application Programmer/Analyst Lead Enterprise Device Engineering and Management MCTS, MCITP, MCSA [Profile<https://www.mcpvirtualbusinesscard.com/VBCServer/MikeMarable/profile>] -------------------------------------------- "The difficult we do at once. The impossible takes a little longer." -US Army Corps of Engineers "It is better to have less thunder in the mouth and more lightning in the hand." -Apache Proverb [Description: Description: Description: Description: Description: Description: Description: Description: win7logoTiny]Microsoft Support for Windows XP ends April 2014! Click here to find out more about Windows 7<https://processmgt.mcit.med.umich.edu/sites/mcit/customer/applicationsoftware/Pages/Windows7.aspx>! ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. ********************************************************** Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues
<<inline: image001.png>>
