When creating SCCM task sequences to deploy desktops, seperate tasks are often used to apply different device drivers based on the hardware the desktop is being deployed to.
For this to work we first need to find the model of the computer we want to apply the drivers to.
Then we require a WMI query based on that computer model, which is applied as a condition to the apply drivers task.
1. On the computer you want to apply the drivers to, use WMIC to find the computer model.
This may be displayed as an actual known name, or it may be displayed as a specific hardware build model
I'm currently in the middle of a Windows 8 implementation in which most of the AppX packages need to be disabled and blocked so that users cannot access them.
One of the more important one's as you can imagine is SkyDrive. Why these kind of applications have found their way into a default installation of Windows for an enterprise environment I do not know, and it really frustrates me.
However rather than use some of the registry hacks out their I've seen to disable various aspects or powershell to remove the apps on a per user basis which is difficult to manage I looked around for what I thought was a much better solution.
You can you AppLocker to block access to not just .exe's and scripts but also AppX packages. It's managed and applied by GPOs which makes it easy for everyone supporting the environment to understand. And the control can be granular, from a single GPO you could allow a group of users to run and app but disallow everyone else, all in 1 GPO and for multiple apps.
One of the first and easiest customizations you will want to make to your SCCM 2012 server once you get it doing magical things is change the name thats displayed on your clients.
The Organization name which is by default "IT Organization" is displayed within the Software Center, Application Catalog, Windows PE and task sequence dialogs.
Recently I found myself looking at an error which I've seen many times before with different customers View environments in which they are unable to connect to desktops getting the following error..
"The connection to the remote computer ended"
Share this blog post on social media:Tweet
All advice, installation/configuration how to guides, troubleshooting and other information on this website are provided as-is with no warranty or guarantee. Whilst the information provided is correct to the best of my knowledge, I am not reponsible for any issues that may arise using this information, and you do so at your own risk. As always before performing anything; check, double check, test and always ensure you have a backup.