In a previous post, we took a quick look at a fresh install of the Windows 10 Technical Preview, and we ended with the successful installation of the ConfigMgr 2012 R2 client.
Now that we want to perform some management functions on the Windows 10 machine, there are a few environmental items of note:
Microsoft .NET Framework – The installed version of .NET is 4.5.53323 (Release 381003). This becomes important for any applications requiring .NET, especially if you are creating Detection Methods and Dependencies in ConfigMgr. Note that as with Windows 8.x the .NET Framework 3.5/3.0/2.0 are available as features but not turned on by default.
Windows PowerShell – Windows 10 comes with PowerShell v5.0 (Build 9841) installed by default.
Adobe Flash Player – Windows 10 includes Adobe Flash Player v15.0.0.167
With these environmental items in place, we don’t need to install any prerequisites for recent agents such as App-V 5.0 or UE-V 2.0. Initiating some existing Application Deployments in my ConfigMgr lab, we see that they install successfully without any modification (in this case meaning requirements for .NET and PowerShell in particular were met):
With a quick reboot we see the UE-V Agent loading and synchronizing successfully (I actually had to switch back to the default Win10 theme after the UE-V agent roamed my Win7 desktop wallpaper to the new system exactly as designed).
We can also now install and run an App-V sequenced application through the Application Catalog.
One item that does NOT work right out of the box is System Center Endpoint Protection. The root of the C: drive shows the tell-tale signs of an unsupported OS:
Attempting a manual installation confirms this (although anecdotally, it apparently remains installed and working in the case of an in-place upgrade):
So, while completely unsupported in terms of official Microsoft toolset, the majority of common management tools appear to function just fine with the Windows 10 Technical Preview. Johan Arwidmark has even provided a quick (and similarly unsupported) way to add support for
deploying Windows 10 with MDT. This means that those of us who will eventually be asked to support the new OS in an enterprise environment have plenty of opportunity to work with Win10 in a reasonably functional fashion between now and its full release.
source:myitforum
