NobleSavage

Unfortunatly the situation is such that each location I support (about 60) requires their own software bundle. I understand that long term I should probably handle this with a UDI task sequence but I barely have available time to type this out =P. So as it stands now for sake of moving my upgrade project along I have to create seperate task sequences per location.

I am a powershell noob so I am hoping someone can point me in the right direction. I have many different task sequences as part of an XP to Windows 7 migration and when I run across a model of PC that we didn't know we had I have to manually add the new driver package to all those existing task sequences. Anyone know of some usefull powershell commands that would add the new driver package into any existing task sequences?

I am in the process of building our corporate Windows 7 Enterprise image and one of the features I love with SCCM 2012 R2 is the abiiity to apply Windows updaes directly to the image file using the Scheduled Updates feature. On paper this seems a great way to apply monthly updates without having to rebuild your image. I have found an issue though with this and figured I would ask the community in hopes I am just missing something simple. When I apply updates to the image using the above method those updates do show under the "Installed Updates" tab of the image, however they do not list themselves under Programs and Features > Installed Updates once you are actually booted into the OS. Transversly it would seem that updates applied within the OS do show under Programs and Features but not the "Installed Updates" tab of the image file. This means there is not one place that will accuratly show you what all the patches and hotfixes are that are applied in that image. This could be an issue for me since I have several programs that install hotfixes on their own and I would like to see everything in a single pane of glass if possible. Am I missing something?

So when I first started automating software installs back in the day the prevailing wisdom was to repacking everything in an msi for control over the installation parameters. Nowadays it seems like several vendors give you the installation switches you need right in the exe. So my question is now with SCCM2012 should I focus any of my time on repacking exe's or extracting the msi's out of the exe's and then editing them with an msi editing software or just leave the exe as is?

I am getting ready to install SCCM 2012 for our production environment. I played around with SCCM 2007 in a lab environment but never messed with deploying Windows Updates through it. Going forward we will be using SCCM to do our patching and I was curious what best practices were with SCCM and SUP. Should I install these roles on the same piece of hardware or is it better to seperate them off. I imagine I will have around 10,000 clients reporting back and getting patched when all is said and done.

Thanks for the clarification

Hello All, First off I would like to say thanks for all the great knowledge, I am a former Altiris Admin who is setting up SCCM for the first time and i would not have been able to do it without this site and its awesome guides. One question I have is that alot of the guides I see describing how to do the cool stuff within task sequences look like they are using the MDT integrated task sequences. So I was wondering when I setup a new OS deployment task sequence should I be looking to use the MDT integrated task sequences or can the regular SCCM OSD task sequence do most of the same things?