The official blog of the Microsoft System Center Configuration Manager Product Group
Now that Windows 8 and Windows Server 2012 are available, we want to provide an update to our previous post on the plans for Windows 8 and Windows Server 2012 support in System Center Configuration Manager and Endpoint Protection.
System Center Configuration Manager
As previously announced, we are adding support for Windows Server 2012 and Windows 8 in System Center 2012 Configuration Manager Service Pack 1 (available in early 2013) as well as for System Center Configuration Manager 2007 SP2, Configuration Manager 2007 R2, and Configuration Manager 2007 R3.
Today, we are releasing the updates to System Center Configuration Manager 2007 that will enable the manageability of Windows 8 and Windows Server 2012.
By applying this update to the Configuration Manager 2007 SP2 client (includes Configuration Manager 2007 R2 and Configuration Manager 2007 R3), our client support matrix includes the following:
As previously announced, we are adding support for Windows Server 2012 and Windows 8 in both System Center 2012 Endpoint Protection Service Pack 1 and Forefront Endpoint Protection (FEP) 2010 with Update Rollup.
Today we are releasing an update to the Forefront Endpoint Protection (FEP) 2010 client. Apply this update for Windows 8 and Windows Server 2012 support. This applies to the Forefront Endpoint Protection client in an environment that is managed by System Center Configuration Manager 2007.
--The Configuration Manager Team
This posting is provided "AS IS" with no warranties and confers no rights.
This is fantastic news, though kind of odd that 2007 got it out the door first. I'm going to remain hopeful that this means SP1 is going to be sooner rather than later.
Are there any workarounds get to Windows 8/Server 2012 to work (in HTTPS config)? We already have dozens of 2012 servers and Windows 8 clients (since September) and an inability to manage these systems is a major problem. Having to wait 6 months (September until early 2013 (Jan-March)), and run that long unmanaged is really bad. This is holding up our Windows To Go roll out.
To clarify previous comment, any there workarounds for Configuration Manager 2012 RTM? (Non-SP1 Beta)
I've introduced this information based on the above article on my blog (in Japanese) as well.
With Microsoft pushing Windows 8 so heavily and having so much riding on it you would think they would provide support for it at launch. Waiting 4-6 months after launch to even have current AV support is ridiculous. This is why MS continue to fail at new products. AV and Management products should be available day 1. Otherwise we cannot test, deploy, or support your shiny new OS. Even the competition is able to get their products in full support with a month. It makes me wonder why anyone relies on MS's own products when their competitors all seem to do it better and faster. Since you own the code MS should be the first one with support.
Hi Guys, Cant find answer to these anywhere so:
Do we need to apply this patch from Global SS down?
Do we need to apply to secondaries?
Do we need to close all MMC console when installing?
*if* MS stick to their publically stated GA+90 days release cycle then SP1 for SC2012 should be released before Feb 1st 2013 to support Win 8 and Srv 2012.
However, as an enteprise customer, we have had access to RTM Win 8 and Srv 2012 since August 2012. So the time gap between Enterprise availability of the OSes and SC2012 SP1 release is a rediculous 6 months. Brad Anderson or another exec figure needs to accept that these timeframes are not acceptable for your customers.
You have a new desktop and Server OS we cannot manage using your flagship endpoint management suite. A highly improved virtualisation platform in Hyper-V 3 that your Virtual Manager app cannot manage and neither OS has AV support from SC2012 to we cannot protect them either.
This is category basics you are failing on!!
how are your Enterprise customers going to roll out Windows 8 with no support for this in 2012? We're still waiting for SQL 2012 support as well!
If i apply that kb2750782 to server do i also need to install to all clients (including win7 clients) or just Win8 clients?
It would be nice if soemone from the ConfigMgr Team would answer these questions.
@Pete, Russell, graetis
The general recommendation with this update is a top-down installation to include secondary sites. We also recommended applying the MSP to all clients for the sake of consistency, but the specific issue addressed does only affect Windows 8 and Windows Server 2012-based clients. Admin consoles should be closed before applying the update. For additional details on installing updates please see our general hotfix installation guidance article for Configuration Manager 2007 support.microsoft.com/.../2477182.
I have tried twice to apply the hotfix to my one and only primary server. A package deployment wizard dialog box appears during the hotfix installation, and at one point it prompts for a path to the .msp file. The msp file in question cannot be found anywhere on the primary server, let alone the "default" path it suggests. However I proceed with the default path and the wizard throws an error. However the hotfix installation "appears" to complete. Unfortunately the Windows 8 and Windows Server 2012 products are still not listed in the software updates component tabs.
Does SCCM 2007 R2 with update patch, can support Windows 8 To Go?