Because I'm a glutton for punishment, I recently started rolling out System Center Configuration Manager 2012 R2 SP1 and System Center Endpoint Protection across our VDI environment. There are always some considerations to be made in a pooled desktop / gold image type environment when loading software that uniquely identifies devices, but lucky for me SCCM/SCEP handled this just fine without any tweaking. However, there were some nuances to how SCEP policies are applied that caused some serious hair-pulling before I spotted the issues.
October 23, 2015
Subscribe to:
Posts (Atom)
Red Flags and the Value of Experience
One of the things I hear often said, and something I subscribe to as well, is the idea that a lot of technical knowledge in the world of IT ...
-
Because I'm a glutton for punishment, I recently started rolling out System Center Configuration Manager 2012 R2 SP1 and System Center E... -
UPDATE: Turns out this is a known issue during the 1.5 > 5.1 VSM upgrade and a fix should be released in an upcoming patch. That's ... -
Having repeated this nightmarish migration several times now, here's the steps I've found to be most efficient: Import your XenSer...