Cumulative Update 4 for ConfigMgr 2012 SP1 released

On January 28, 2014 (missed that one) Cumulative Update (CU) 4 for ConfigMgr 2012 SP1 is released. Missed that because I'm doing ConfigMgr 2012 R2 implementations a lot, but that's no excuse ;) It contains 13 fixes and/or improvements this time.

Today I'm installing this update because of a lot of issues on a ConfigMgr 2012 SP1 environment. Therefore it's still a valid installation, because there's no SP2 available.
 
Here's a list of the issues that are fixed:
- Software distribution (4 fixes)
- Operating system deployment (4 fixes)
- Administrator console (1 fix)
- Application Virtualization (2 fixes)
- Endpoint Protection (1 fix)
- Site Server (1 fix) 
 
Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

This update replaces Cumulative Update 3 for System Center 2012 Configuration Manager Service Pack 1
 
For more information or download the update have a look here: Microsoft Support

How to install CU3 and recognize the update afterwards

This week I did a new ConfigMgr 2012 SP1 installation, and installed Cumulative Update (CU) 3 afterwards. In this blogpost I explain how to install the update, and how to recognize it afterwards.

Just download CU3 here: Click
or have more information here: Click

Start the installation and choose:
-Welcome to setup > Next
-Prerequisite Check > Next
-Install the update for the ConfigMgr console
-Yes, update the site database
-Select all (site servers, consoles, clients)
-Choose to create update packages (4x)
-Setup Summary > Next
-Installation Progress (You should see this now)

 -Installation Complete > Finish

Let's have a look now to recognize it. It can be done on multiple places!
-ConfigMgr console properties (5.0.7804.1400):

Installed software updates (KB2882125):

Registry check (HKLM\Software\Microsoft\SMS\Setup):

Installed software packages (4x):

ConfigMgr client version (<ConfigMgr folder>\Client):
This one must be File version 5.0.7804.1400 now!

SCEP client version (<ConfigMgr folder>\Client):
This one must be File version 4.3.215.0 now!

As you can see all is okay now. Don't forget to update other ConfigMgr consoles and already existing ConfigMgr clients with the new software packages. After that you are ready and set again!

Cumulative Update 3 for ConfigMgr 2012 SP1 released

Last week (on friday) Cumulative Update (CU) 3 for ConfigMgr 2012 SP1 is released. It contains 17 fixes and adds support for Windows 8.1-based client computers in ConfigMgr SP1. Windows 8.1 is added to the supported platform list for the following features:
-Software distribution
-Software update management
-Compliance Settings

For OS deployment it''s still needed to upgrade to ConfigMgr 2012 R2 when it becomes available next month.

Here's a list of the issues that are fixed:
-Operating System Deployment (4 fixes)
-Windows PowerShell (1 fix)
-Software Distribution (4 fixes)
-Windows Intune (2 fixes)
-Endpoint Protection (1 fix)
-Site Systems (2 fixes)
-Reporting (2 fixes)
-Software Updates (1 fix)

Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

This update replaces Cumulative Update 2 for System Center 2012 Configuration Manager Service Pack 1

For more information or download the update have a look here:
Microsoft Support

Cumulative Update 2 for ConfigMgr 2012 SP1 released

Today Cumulative Update (CU) 2 for ConfigMgr 2012 SP1 is released. It contains 18 fixes and updated support for Linux and UNIX clients. With CU2 it's possible to add WinPE 3.1 boot images for VMWare Workstation and ESX Server support. More about that issue here: BSOD in VMware 4.1 when booting with WinPE 4.0 images

Here's a list of the issues that are fixed:
- Administrator console (2 fixes)
- Application Virtualization (2 fixes)
- Operating system deployment (4 fixes)
- Asset Intelligence (1 fix)
- Mobile device management (1 fix)
- Software distribution (3 fixes)
- Updated list of supported Linux and UNIX clients
- Site systems (3 fixes)
- Configuration Manager SDK (1 fix)
- Client (1 fix)
- Cumulative Update Setup Wrapper (Installer)

Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

This update replaces Cumulative Update 1 for System Center 2012 Configuration Manager Service Pack 1

For more information or download the update have a look here:
Microsoft Support

Cumulative Update 1 for ConfigMgr 2012 SP1 released

2 days ago Cumulative Update 1 for ConfigMgr 2012 SP1 is released. It contains 18 fixes and 39 new cmdlets. Here's a list of the issues that are fixed:

- Administrator console (2 fixes)
- Site systems (2 fixes)
- Device management (1 fix)
- Software updates (3 fixes)
- ConfigMgr client (4 fixes)
- PowerShell (6 fixes)

Just install it in your environment when experiencing problems described in this article. When not affected by these problems, Microsoft recommends to wait for the next service pack that contains this update.

For more information or download the update have a look here:
Microsoft Support

Install ConfigMgr 2012 SP1 on Server 2012 and SQL 2012 SP1

Last month I installed a new lab environment with new components: ConfigMgr 2012 SP1, Windows Server 2012 and SQL Server 2012 SP1. All Configuration will be mentioned in this blogpost. Here we go!
 
In my setup I'm using 2 VM's: 1 Domain Controller (VDC01) with 2GB memory and 1 SQL/ConfigMgr server (VCM01) with 8GB memory. Let's start with the Domain Controller first.
 
- Install Windows Server 2012 (5 minutes on SSD);
- Change computer name to VDC01 and restart;
- Add static IP-address (192.168.137.x) to the network-adapter;
- Add Roles with PowerShell cmdlets (Install-WindowsFeature -Name AD-Domain-Services,DNS,RSAT);
- Add Features with PowerShell cmdlets (Install-WindowsFeature NET-Framework-Core -Source D:\Sources\SxS);
- Promote to Domain Controller in Server Manager (Add a new forest);
- Choose Contoso.com as Root domain name (for example) and use default settings in the wizard. Only warnings are displayed in the Prerequisites check, so choose Install after read them;
- After restart login with a Domain Administrator account. Disable Windows Firewall and IE ESC for all profiles/accounts;
- Create 2 service accounts for SQL (SVC_SQL) as Domain User and SCCM (SVC_SCCM) as Domain Admin.

Let's start with the ConfigMgr server now!

- Install Windows Server 2012 (5 minutes on SSD);
- Change computer name to VCM01 and restart;
- Add static IP-address (192.168.137.x) to the network-adapter;
- Add Roles with PowerShell cmdlets (Install-WindowsFeature -Name Web-Server, WDS, RDC, BITS);
- Add Role Services with PowerShell cmdlets (Install-WindowsFeature -Name Web-WMI); 
- Add Features with PowerShell cmdlets (Install-WindowsFeature NET-Framework-Core -Source D:\Sources\SxS);
- Promote to Domain Server in Server Manager (Contoso.com);
- After restart login with Domain Administrator account. Disable Windows Firewall and IE ESC for all profiles/accounts.

- Install SQL Server 2012 SP1 and make sure the collation is set to "SQL_Latin1_General_CP1_CI_AS";
- Choose: Database Engine Services, Full-Text search, Reporting Services and Management Tools (2x);
- Choose default settings where possible and start installation;
- Configure SQL Server and SQL Server Agent to run with the SVC_SQL account (SQL Server Configuration Manager);
- Configure Reporting Services to run with the SVC_SQL account (Reporting Services Configuration Manager).

- Add WSUS with PowerShell cmdlets for SQL database (Install-WindowsFeature -Name UpdateServices-DB, UpdateServices-Ui);
- Start C:\Program Files\Update Services\Tools\WsusUtil.exe Postinstall SQL_INSTANCE_NAME=VCM01 CONTENT_DIR=C:\WSUS.
 
- Start Extadsch.exe on VDC01 from ConfigMgr media for a schema update (D:\SMSSETUP\BIN\X64);
- Create a System Management container (beneath System) with ADSIEdit at set permissions for VCM01 (Full control, This object and all descendant objects);
- Install Windows Assessment and Deployment Kit (ADK) on VCM01 (Deployment tools, Windows PE, USMT);
- Assign maximum server memory (4096 MB) in SQL Server Management Studio in SQL Server properties.

At last ConfigMgr installation can be started!
 
- Install a Configuration Manager primary site;
- Enter License key or start an evaluation version (180 days);
- Download required files or Use previously downloaded files;
- Choose Server and Client languages (english default);
- Choose a Site code and Site name for the ConfigMgr environment;
- Install the primary site as a stand-alone site;
- Choose SQL Server and SMS Provider location;
- Configure the communication method on each site system role;
- Install a Management point and Distribution point (HTTP);
- Watch the prerequisite check, which shows only a "SQL Server process memory allocation" warning in my environment;
- Installation is done in 12 minutes on SSD.

Above steps can be done in just one day. After that a new lab environment is running with new components: ConfigMgr 2012 SP1, Windows Server 2012 and SQL Server 2012 SP1. Have fun!

New ConfigMgr 2012 and SCEP 2012 SP1 Binaries available!

The binaries for ConfigMgr 2012 and SCEP 2012 have been updated to correct some minor issues. The binaries have been updated at the Download Center, and also on the Technet and MSDN download sites.

For ConfigMgr 2012 SP1, the updated download release of SP1 includes the following hotfix: Installation error 0x800b0101: System Center 2012 Configuration Manager Service Pack 1 client
 
For SCEP, the new binaries include fixed files (Linux/iOS) that were corrupt in the initial release. Microsoft System Center 2012 Service Pack 1 Configuration Manager - Clients for Additional Operating Systems
 
New ConfigMgr 2012 and SCEP 2012 SP1 Binaries available!
MSDN Download Link and Technet Download Link

This means if you downloaded the binaries prior to today (1/25) - you will likely need to re-download them. Source

Note: Don't forget to use the new bits when installing ConfigMgr 2012 SP1 from now on!

System Center 2012 SP1 downloadable VHDs available!

Do you want to experience System Center 2012 SP1 products?

Microsoft have made VHDs available for evaluation: 

• System Center 2012 Service Pack 1 - Configuration Manager – Evaluation (VHD)
• System Center 2012 Service Pack 1 – Service Manager – Evaluation (VHD)
• System Center 2012 Service Pack 1 – Service Manager (Data Warehouse) – Evaluation (VHD)
• System Center 2012 Service Pack 1 – Operations Manager – Evaluation (VHD)
• System Center 2012 Service Pack 1 – Orchestrator – Evaluation (VHD)
• System Center 2012 Service Pack 1 – Data Protection Manager – Evaluation (VHD)
• System Center 2012 Service Pack 1 – Virtual Machine Manager – Evaluation (VHD)

Just use them to have a look at all the new features!

Update: Added the Virtual Machine Manager VHD to the list also.
Thanks to Eric Berg for the comment!

System Center 2012 SP1 Generally Available!

Today Microsoft announced the general availability of System Center 2012 SP1!  While the RTM bits have been available for a few weeks already to TechNet, MSDN subscribers and volume licensing customers, today marks the broad availability of System Center 2012 SP1 to all customers. SP1 isn't just an update on ConfigMgr. It will provide a lot of new functionality above of existing ConfigMgr 2012 features.

The System Center 2012 SP1 release is chock full of new features to light up the new functionality found in Windows Server 2012.  The combination of System Center 2012 SP1 with Windows Server 2012 provides the foundation of what Microsoft calls the ‘Cloud OS’. More information about Updates and New features in ConfigMgr 2012 SP1 can be found in this blogpost.

The System Center Service Pack 1 setups for each component can be used to install a completely new installation of a System Center 2012 SP1 component or can be used to upgrade an existing component from System Center 2012 to System Center 2012 SP1. Download Microsoft System Center Private Cloud Evaluation Software: System Center 2012 SP1 plus optional Windows Server 2012 download

Customers who are planning to install the Configuration Manager client on x64 machines should review this KB2801987 prior to installation.

System Center 2012 SP1 issues

Microsoft System Center 2012 SP1 adds a bunch of new features to the Suite of products. I have deployed it a few times at companies already without a lot of problems. The only issue I have encountered so far is with Software Updates "Remote configuration failed on WSUS Server" which is described HERE.

On MyITforum however there is a list created about System Center 2012 SP1 issues. This because there are a ton of reports coming in that SP1 is causing some frustrating issues in those companies that have decided to deploy it already. This Wiki post serves to capture the issues in a central location to ensure everyone is aware of them and their potential workarounds until Microsoft releases fixes.

As a member of myITforum and a member of this group you can modify this live document to include issues that you have encountered.

Source: System Center 2012 SP1 Woes, Gotchas, and Workarounds

The first hotfix is available already: ConfigMgr 2012 SP1 client hotfix for MicrosoftPolicyPlatformSetup.msi error available

Upgrade ConfigMgr 2012 to Service Pack 1

Last week on december 12, Service Pack 1 (SP1) was available on TechNet or MSDN subscriptions. Because my lab environment is running on SP1 Beta, I thought the whole installation must be done again. Good news is that the upgrade from SP1 Beta to SP1 RTM can be done without any issues at all. The only thing important is, it isn't supported in any way. But because it's my lab environment that doesn't count.
 
Let's have a look at the upgrade:
 

Choose "Upgrade this Configuration Manager site" to start installation

 

A new feature in SP1 is that more Server languages are available now

 

 During Prerequisite check a new warning message is shown on collections

 

And finally after a "few" minutes waiting the installation is done! :)

 

Very nice to have a lab environment with ConfigMgr 2012 SP1 now!!

 

Just start to download the bits and experience the new features and functionality yourself. More on the new stuff can be found HERE. Hope you like it as much as I do! More to come about SP1 later.



System Center 2012 SP1 available now!

Great news! System Center 2012 SP1 is available now! It can be download on Microsoft TechNet if you have a TechNet or MSDN subscription. Lucky me I have one because of my Microsoft Certified Trainer (MCT) status.

With Service Pack 1, Windows 8 and Windows Server 2012 support are available. Just connect to Microsoft TechNet and download the bits!

Updates and New Features in ConfigMgr 2012 SP1

Last month I was at System Center User Group (SCUG) NL day with Wally Mead. Wally Mead has been with Microsoft for more than 20 years, and working with Systems Management Server since SMS 1.0 was in development. The following Updates and New Features for ConfigMr 2012 SP1 were mentioned: 
 
Deployment of Windows 8:

• Core OS Deployment Scenarios (Windows 8/ 2012 support)
• Windows To Go support (create and build by ConfigMgr)
• Managing Windows 8 Apps (for both x86 and RT)
• Always-on Always connected (preserves battery life)
• Metered Connections support (for paid networks)
• Used Space BitLocker (saves time during OSD)
• Bitlocker pre-provisioning from WinPE mode (5 minutes versus 3 hours)

 
Management Capabilities of Windows RT and Windows Phone 8:

• Windows 8 Apps (easier and faster to deploy)
• Windows 8 Apps in the Windows Store (new type of software)
• Pull Software Distribution (MDM)
• Settings Management (with ConfigMgr policy)
• Compliance Monitoring (MDM)

 
Embedded Device Support in SP1:

• Better support for write filters
• Write filter orchestration for updates and OSD
• SCEP support for installation and updates
• Desired Configuration Management extensions
• OS deployment optimized for embedded devices

 
And many many more:

• User Data and Settings Management (User policy)
• Windows Intune management in ConfigMgr console (!)
• Distribution Point for Windows Azure (in the cloud)
• Database Replication Controls (make the hierarchy easier to control)
• Security and Compliance for Endpoint Protection
• Real-time Administrative Actions (force machine policy)
• Support for App-V 5.0, PowerShell, Non-Windows devices
• Support for SCEP on MAC, UNIX and Linux systems

 
Service Pack 1 isn't just an update on ConfigMgr. It will provide a lot of new functionality above of existing ConfigMgr 2012 features.
The General Availability release of System Center 2012 SP1 is scheduled for early January.

System Center 2012 SP1 release date

System Center 2012 Service Pack 1 has reached RTM, Microsoft announced recently. RTM refers to feature-complete products. The General Availability release of System Center 2012 SP1 is scheduled for early January. Because Q1 2013 was mentioned last months, this is way earlier then expected. 

Windows Intune is set for an "early 2013" update also. With Windows Intune, Mobile Device Management in ConfigMgr becomes available.

A few notes to make the upgrade path crystal clear: 

• General Availability is targeted for early January;
• Upgrade from SP1 Beta is only supported for TAP customers who installed RC;
• Non-TAP customers will only be able to upgrade from DPM 2012 RTM to DPM 2012 SP1 RTM;
• There is no upgrade path from BETA SP1 to RTM SP1, you must reinstall DPM 2012 RTM, then upgrade to SP1 RTM.

Availability of SP1 RTM for SA costumers is probably January 3, 2013. Great news we can download the bits within a few weeks from now!
 

Source: Redmond Channel Partner

Update 2-1-2013: System Center 2012 SP1 is now available for download from the Microsoft Volume Licensing site.

How to update ConfigMgr 2012 RTM to SP1 (Beta)

Next year (Q1 2013) System Center 2012 Service Pack 1 (SP1) becomes available. This Service Pack will be released for System Center 2012 and not just for ConfigMgr only. SP1 for ConfigMgr will bring a lot of new features and functionalities, which are described HERE.
 
To update a ConfigMgr 2012 RTM environment to SP1 (Beta) the following is needed: 

• Uninstall Windows Automated Installation Kit (Windows AIK)
• Download Windows Assessment and Deployment Kit (Windows ADK) for Windows 8 which is available HERE
• Install Windows ADK by adksetup.exe and choose Install (which download the files needed online first) or choose Download (which download all files for offline usage)
• The only features needed are Deployment Tools, Windows PE and USMT.
• Upgrade the SQL Server installation from SP1 CU4 to SP2 which is available HERE or SP1 CU6 which is available HERE

 
After that the prerequisite check should not display any errors anymore:

When both Deployment Tools and Windows PE must be installed on other Site servers too, it's because of multiple SMS Providers that are installed. Otherwise you will be fine and setup can be started immediately.

During installation boot images will be upgraded from WinPE 3.0 to 4.0 automatically. Just remember to update ALL Distribution points after the upgrade, because this will not be done automatically (!)

Remember: After the upgrade all ConfigMgr 2012 RTM clients must be updated to SP1 (Beta) too. Not that it won't work otherwise, but because new features and functionalities will not be functional then.
It can be done automatically with Site Hierarchy settings (Client Installation Settings).

SP1 for ConfigMgr will bring a lot of new features and functionalities!

ConfigMgr 2012 Service Pack 1 features

Next year (Q1 2013) System Center 2012 Service Pack 1 (SP1) becomes available. This Service Pack will be released for System Center 2012 and not just for ConfigMgr only. It containes updates for compatibility with Windows 8, Windows Server 2012 and other enhancements including support for Azure VM and capabilities for Hosted Service Providers. For ConfigMgr 2012 it will be a big step forwards, because of multiple new features and functionalities!

In this blogpost I will mention these:

– Support for Windows 8 (for both ConfigMgr/SCEP client installation and Operating System deployment);
– Support for Windows To Go (Full Windows 8 installation on a certified 32GB USB-stick);
– User data & profile configuration by means of folder redirection, offline files & roaming profiles;
– New deployment types for Windows 8 applications, including standalone applications and links to the Windows Store;
– Support for Windows Server 2012 (for both ConfigMgr client installation and Operating System deployment);
– Support for SQL Server 2012 (installation of ConfigMgr database);
– ConfigMgr client installation on MAC computers, Linux and UNIX servers;
– Possibility for Windows PowerShell cmdlets (to automate ConfigMgr tasks);
– Support for cloud services, including a new Distribution Point for Windows Azure;
– A more flexible hierarchy management for Central Administration Site (CAS) and Primary Site servers;

– Support for multiple Software update points (SUPs), with automatic  redundancy (same as Management points);
– Console Extensions integration in ConfigMgr console (downloading computer policy and initiating a malware scan to be performed as soon as possible);
– Support for virtual environments that allow multiple virtual applications (App-V packages) to share file system and registry information instead of running in an isolated space;
– Email alert subscriptions are now supported for all features, not just Endpoint Protection (useful for the Application Catalog);
– Multiple application types for Software Catalog usage and deployment, Mobile Device APP stores and App-V 5.0 (!) support;
– Support for App-V 5.0 packages (release: Q1 2013);
– Windows Intune integration (finally a Mobile Device Management solution for cloud device management);
– Support for Windows Embedded devices, because of Windows Embedded Device Manager (WEDM) integration.

As you can see a lot of new features and functionalities are added in ConfigMgr 2012 SP1. I'm very enthusiastic that this already great product (compared to previous versions), will be more advanced with every release. Stay tuned for more information early next year!

New System Center 2012 VHDs available

Yesterday Microsoft has released System Center 2012 VHDs, based on Service Pack 1 (beta). Thay way it's very easy to have a look at all new functionality in a demo environment. The downloads consists of files that must be extract into a single pre-configured VHD file for this System Center component. The VHD enables you to create a virtual machine to evaluate the different System Center components.

The VHDs can be found on the following locations:

System Center 2012 Service Pack 1 Beta – Data Protection Manager – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta – Operations Manager – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta – Orchestrator – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta – App Controller – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta– Service Manager – Evaluation (VHD)

Unfortunately no VHD is available for System Center 2012 Configuration Manager (ConfigMgr) with Endpoint Protection. Maybe it will be released at a later moment. Just have fun with the already available ones!

How to create a reference image in ConfigMgr

In ConfigMgr 2007 and 2012 the most used functionality is Operating System (OS) deployment. With OS deployment it's possible to migrate or install an unknown or known system, which can be a server, fat client (desktop or notebook), thin client or virtual desktop. To migrate or install an unknown or known system, a reference image is needed. This is the image created on a (virtual) system, which is prepared for deployment. Unfortunately you can't use the Install.wim from the Windows XP, Vista or Win7 ISO file, because it will be installed on the D: drive by default. That's the Microsoft way for creating images :)

A reference image can be created with a Build and Capture task sequence, which is the preferred way. All Windows files from a ISO file must be imported in ConfigMgr to use this task sequence. A Windows OS will be installed on the host system, Sysprep is running which reboots the system, Windows PE will start automatically and a reference image will be uploaded to the ConfigMgr server. A default Build and Capture can be created within the task sequence wizard. The ConfigMgr client will be installed in this reference image (mandatory step).

Another possibility is using ConfigMgr Capture media on an already installed system. That way the system must be joined to a workgroup and Sysprep files must be present on the host OS. In Windows 7 or Windows 8 this isn't needed, because Sysprep is build-in. When ConfigMgr Capture media is started (within Windows, because it isn't bootable) Sysprep is running which reboots the system. Windows PE will start automatically after reboot and a reference image will be uploaded to the ConfigMgr server. No ConfigMgr client will be installed this time.

A reference image contains software updates and maybe a few applications like DotNet Framework for example. It's not a best practice to install user-specific applications in the reference image. Just keep it as clean as possible! That's also the reason to create it on a virtual machine, because less drivers are needed. When using ConfigMgr 2007 it's needed to install software updates during Build and Capture to have an updated image. In ConfigMgr 2012 it's not needed anymore to install software updates during installation. Just build the image and use Offline Servicing in ConfigMgr 2012 for offline update integration.

With Windows Server 2012 and Windows 8 (which will be supported in ConfigMgr 2012 SP1), no reference image is needed anymore. Within Windows Server 2012 and Windows 8 it's possible to mount an ISO file by richtclick and mount it, without the need for additional software. Just copy the Install.wim from the (mounted) ISO file and import it in ConfigMgr 2012 SP1. Use Offline Servicing for offline update integration and you're done! That way you can save a lot of time which can be used for all new awesome functionality in ConfigMgr!

That's it for now. If there are still questions about this topic, use comments below.

One management product to rule them all

As mentioned in my other blogposts, Service Pack 1 for System Center 2012 will become available in Q1 2013. With SP1 for ConfigMgr 2012 (which is part of System Center) a lot of new functionality is added to this already awesome product. In this blogpost I created an overview of all ConfigMgr Client support for this product. Expect a lot of new possibilities: One product to manage them all.

ConfigMgr 2012 SP1 will do management on the following OSEs:
 
Client devices:

• Windows XP SP3, Windows Vista SP2, 
• Windows 7 (SP1), Windows 8
• Windows To Go

Server devices:

• Windows Server 2003 SP2, Windows Server 2003 R2 SP2
• Windows Server 2008 SP2, Windows Server 2008 R2 (SP1)
• Windows Server 2012

Thin Clients based on Windows XP SP3:

• Windows Embedded Standard 2009
• Windows XP Embedded SP3
• Windows Fundamentals for Legacy PCs (WinFLP)
• Windows Embedded POSReady 2009
• WEPOS 1.1 with SP3

Thin Clients based on Windows 7:

• Windows Embedded Standard 7 with SP1
• Windows Embedded POSReady 7
• Windows Thin PC (SA benefit)

MAC Computers:

• Mac OS X 10.6 (Snow Leopard), Mac OS X 10.7 (Lion)

Linux and UNIX Servers:

• AIX version 5.3, 6.1, 7.1
• HP-UX version 11iv2, 11iv3
• Red Hat Enterprise Linux (RHEL) version 4, 5, 6
• Solaris version 9, 10, 11
• SUSE Linux Enterprise Server (SLES) version 9, 10 SP1, 11

Mobile devices (Depth management):

• Windows Mobile 6.1, Windows Mobile 6.5 (phones)
• Nokia Symbian Belle (phones)

EAS connected Mobile devices (Light management):

• Windows Phone 7
• Android, iOS (phones and tablets)

Windows Intune integration (Depth management): 

• Windows Phone 7, Windows Phone 8
• Windows Runtime (RT) tablets
• Android, iOS (phones and tablets)

Are you excited yet about all Operating Systems which can be managed? With ConfigMgr 2012 SP1 (and Windows Intune integration) all modern OSEs can be managed for Servers, Clients, Thin Clients and Mobiles. Installing ConfigMgr is not about managing Windows clients anymore, it's about managing a whole range of devices. The future is bright!

Resources: Supported Configurations for Configuration Manager

Installation Prerequisite Check for ConfigMgr 2012 SP1 Beta

Today I installed the new System Center 2012 Configuration Manager (ConfigMgr) SP1 Beta. During the upgrade some new prerequisites are needed on the ConfigMgr server. In this blogpost I will mention the new prerequisites and where to find them. There we go:

• WSUS on site server: ConfigMgr requires WSUS of at least version 3.0 SP2 with KB2720211 and KB2734608 installed
• User State Migration tool (USMT) installed: he User State Migration Tool component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue
• SQL Server version: ConfigMgr sites require a supported SQL Server version with required hotfixes for site database operations to succeed (in my case I installed SQL Server 2008 R2 SP2 to go further)
• Windows Deployment Tools installed: The Windows Deployment Tools component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue
• Windows Preinstallation Environment installed: The Windows Preinstallation Environment component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue

After installing all prerequisites, setup can be continued.

In my next posts expect more to see about new functionality! Have a look HERE for all improvements.