Home > SCCM > How SCCM 2012 may challenge you at first…

How SCCM 2012 may challenge you at first…


At MMS (Microsoft Management Summit) 2011 several sessions focused on SCCM 2012. I have to say it is an awesome product and I cannot wait to install Beta 2 when I get back in the office! But, it is my opinion that SCCM 2012 could be a challenge for many…at least initially.

The challenge I am speaking to is user and device affinity. This has been discussed for a long time now as the product has been developed. But, is your team ready after so many years of being so device focused? What I mean is for years we have all been focused on getting a device to a desired state for a user and had the expectation that they will use that device. With this release we have the ability to tell that user they can use any device (maybe a laptop), anywhere with an Internet connection (combined with terminal services, VDI, etc. we can even further extend the infrastructure) and have access to their applications without a huge administrative headache. The story here would be the user has applications on their laptop that they can use in the office. Maybe some can work offline when on the road. But, maybe other require access to data in the data center. So they have .MSI installs on their laptop and then when they log into Citrix they get App-V packages of those applications presented to them in their session…sounds good but it will take some planning and a lot of testing!

There are also some great tools to import applications from SCCM 2007 but I highly encourage you to really get a firm grasp on application delivery and how that can work with primary devices. Essentially you can control or allow your users to define their primary device. With this set in the database you can then create behaviors for how applications are delivered.

For example – One of the hands on labs at MMS had a great scenario. There were two package for App-V delivery (x86 and x64). There were another two packages for a business application, one that was a .MSI installation and another that was the App-V version of the same application. Each of the business applications can have dependencies for the App-V clients just like in pervious versions. But now you can define requirements within the packages (reduces the need for tons and tons of collections – I like it!!!!). A few examples of types of requirements are:

  • Operating System version
  • Available memory, hard drive space
  • Manufacturer of the device
  • Model of the device
  • User primary device (in this case you can deliver the .MSI to the primary device and App-V package to other devices)

The basic idea here is anything you may have used WQL queries within collections for you can now build right into the application package. That is AWESOME!!!!

Advertisements
Categories: SCCM
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: