Windows 8 Release Preview available now

On 31-5-2012 the third build of Windows 8 and is showed to the world. After the Windows Consumer Preview and Windows Developer Preview earlier last year, there's now a Release Preview available for download. Windows 8 is build on Metro, the User Interface we know from Windows Phone 7 devices. That way it's usable on servers, desktops, laptops and tablets, with touch interface!

The Windows 8 Release Preview ISO images can be download HERE

It's Windows reimagined and reinvented from a solid core of Windows 7 speed and reliability. It's an all-new touch interface. It's a new Windows for new devices. And it's easy to try now—whether you're installing it for the first time, or moving from Windows 8 Consumer Preview.

On 31-5-2012 the third build of Windows Server 2012 (formerly known as Windows Server 8) has become available for download also. Windows Server 2012 Release Candidate Datacenter can be download HERE

The next release of Windows Server, Windows Server 2012, will offer businesses and hosting providers a scalable, dynamic, and multitenant-aware, cloud-optimized infrastructure. It securely connects across premises and helps IT Professionals to respond to business needs faster and more efficiently.

More blogposts available for Windows 8 also:

Disable the GUI in Windows Server 8 with PowerShell
Guide to install Windows 8 on a VHD (Virtual Hard Disk)

Guide to remove Windows 8 on a VHD (Virtual Hard Disk)

Network Access Account in ConfigMgr 2012

Last week I installed ConfigMgr 2012 at a customer location and did some default configuration in it also. I've configured Software Updates, Exchange Connector and Endpoint Protection. Today I started with Operating Systems and imported Windows 7 source files to Build and Capture a reference image. This on a Hyper-V host to build a driver free reference image.

When starting the Build and Capture task sequence, errors where displayed almost immediately after starting it. These are the error messages seen:

- GetMPLocation failed (0x80004005)
- Failed to Run Task Sequence (0x80070057)
- Failed to query http://xxxxx for MP location

On most forums I read that I need to configure the Network Access Account right and create Boundary Groups to get the job done. But I configured everything right, why still the error messages where displayed?

So I checked the Network Access Account again. Just go to the Software Distribution Component properties for that. By default the following is selected: "Use the computer account of the Configuration Manager client". That way it didn't start the task sequence at all. I changed it to "Specify the account that accesses network locations" and selected my Network Access Account.

Beneath Security - Accounts is possible to edit the account credentials again. Strange enough when verifying the account it was running fine. Test connection to different shares where all okay. Because I didn't trust it, I changed it to a totally different password and still the account verification was fine. How is that possible?

Long story short, I typed in the password again and started the Build and Capture task sequence another time. All was running fine now! It was my password which wasn't correct, but there's no way to see that? ConfigMgr let you know all is running okay, and "Test connection" will let you see that "The connection was successfully verfied". Even with a bad password! (a bug maybe?)

I think there's something really strange with the Network Access Account password verfication. Maybe it's functionality is not good in the RTM version? Because in Beta2/RC the same thing cannot be done. Then the following error message will be displayed: "The specified network password is not correct"

Hopefully this will be fixed by Microsoft at a later time.

Installation Prerequisite Check for ConfigMgr 2012

When starting a new ConfigMgr installation there are many prerequisites that must be configured first. In this blog I will mention the most important ones.

The most known requirements are:

• Schema extensions: Configuration Manager Active Directory schema extensions are not required for site server installation, but are recommended to fully support the use of all Configuration Manager features; TechNet
• WSUS SDK on site server: ConfigMgr software update points require at least WSUS v3.0 SP2.  If using a remote software update point, the WSUS administration console must be installed on the site server;
• Microsoft RDC library registered: The Microsoft Remote Differential Compression (RDC) library must be registered for ConfigMgr site server installation; TechNet
• SQL Server service running account: The logon account for the SQL Server service cannot be a local user account or LOCAL SERVICE.  You must configure the SQL Server service to use a valid domain account, NETWORK SERVICE, or LOCAL SYSTEM;
• Verify site server permissions to publish to AD: The site server might be unable to publish to Active Directory. The computer account for the site server must have Full Control permissions to the System Management container in its Active Directory domain; TechNet
• SQL Server version: ConfigMgr sites require a supported SQL Server version with required hotfixes for site database operations to succeed. Before Setup can continue, you must install a supported version of SQL Server on the specified site database server; TechNet
• SQL Server sysadmin rights: Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions;
• BITS installed: Background Intelligent Transfer Service (BITS) is required for the management point and distribution point site system roles. Also, check if IIS/BITS services are running properly. Setup cannot continue until BITS is installed and enabled in the IIS settings;

Most other Prerequisite Checks can be found HERE. These are for ConfigMgr 2007, but will still be valid for 2012 installation.

Also check additional SQL Server requirements mentioned in my other blogpost: SQL Server requirements for ConfigMgr 2012 installation

After all this is done, it's possible to have a "All prerequisite rules pass successfully" status before ConfigMgr 2012 installation!

Update 25-6-2012: Clues added for installation!

SQL Server requirements for ConfigMgr 2012 installation

When installing ConfigMgr 2012 it's important to fullfill all SQL Server requirements. The following must be configured during installation:

• The instance of SQL Server in use at each site must use the following collation: SQL_Latin1_General_CP1_CI_AS;
• Only the Database Engine Services feature is required for each site server (Configuration Manager database replication does not require the SQL Server replication feature);
• Configuration Manager requires Windows authentication to validate connections to the database;
• You must use a dedicated instance of SQL Server for each site;
• When you use a database server that is co-located with the site server, limit the memory for SQL Server to 50 to 80 percent of the available addressable system memory. When you use a dedicated SQL Server, limit the memory for SQL Server to 80 to 90 percent of the available addressable system memory;
• Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory in the buffer pool used by an instance of SQL Server for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site;

If SQL Server is installed with a different collation: Latin1_General_CI_AS (for example) it won't work. ConfigMgr 2012 installation will fail during the prerequisite check and no installation is possible at all. Also a workaround to change the default collation don't seem to work then. Best thing is to install a brand new SQL Server with the right requirements.

During SQL Server installation choose the following configuration:

At Server Configuration, choose Collation and select Customize

Select SQL_Latin1_General_CP1_CI_AS instead of default

After that it's possible to have a successful ConfigMgr 2012 installation. Just make sure above requirements are configured.

Microsoft Private Cloud exam preparation

For the first time ever at MMS, attendees could take Microsoft Certification Exams onsite. For those interested in the Private Cloud, you could be one of the very first to take the beta version of Microsoft’s private cloud certification exams. For that reason I scheduled two exams and it will approximately take 8 weeks for the final score. The exams were not that easy; you must have good understanding of all MS Private Cloud products to have a good change. In this post I will share some hints & tips for the exams. 

When passing both exams and MCITP: Server Administrator you get the new "MCSE (Microsoft Certified Solutions Expert) Private Cloud" status. 

Exam 71:246 (58 questions)
For it seems most of MS Private Cloud exam questions are about Virtual Machine Manager, Operations Manager, Service Manager and Orchestrator. Furthermore there a questions on Data Protection Manager and WSUS integration in Virtual Machine Manager. It's the hardest one of the two exams.

Preperation materials: http://www.microsoft.com/learning/en/us/exam.aspx?id=70-246

The distribution of questions is about:

• Virtual Machine Manager: 30%
• Operations Manager: 20%
• Service Manager: 20%
• Orchestrator: 20%
• Data Protection Manager: 10%

Exam 71:247 (47 questions)
Again most of MS Private Cloud exam questions are about Virtual Machine Manager, Operations Manager, Service Manager and Orchestrator. Furthermore there are questions on App Controller, Data Protection Manager and App-V Server. This one seems a little bit easier then the other one.

Preperation materials: http://www.microsoft.com/learning/en/us/exam.aspx?id=70-247

The distribution of questions is about:

• Virtual Machine Manager: 30%
• Operations Manager: 10%
• Service Manager: 20%
• Orchestrator: 20%
• App Controller: 10%
• Data Protection Manager 10%

Because of the ConfigMgr 2012 exam 70:243 (which is final by now), there are (almost) no questions about Configuration Manager and Endpoint Protection. All other 6 products from the System Center 2012 suite will be used. 

Good luck with both exams! (and post the results)

Useful Information from MMS 2012 Las Vegas

Last week I was at Microsoft Management Summit in Las Vegas. With 5,500 delegates the event was sold out! It was a nice week with lots of useful information about Microsoft System Center 2012 and Microsoft Private Cloud. Besides the fact that there were many Configuration Manager 2012 sessions to follow, the Microsoft Private Cloud exams released at this event also. Therefore I scheduled two exams and it will approximately take 8 weeks for the final score. I had close contact with a lot of suppliers on ConfigMgr (add-ons) and OpsMgr (management packs).

Here's the information I have gained partly during MMS:

System Center 2012 & MS Private Cloud

• System Center 2012 is released officially on Tuesday April 17th 2012, during the Microsoft Management Summit
• All System Center 2012 products has some kind of integration with each other
• Live Migration is greatly enhanced in SCVMM 2012 & Network Virtualization in SCVMM 2012 available
• The new "MCSE: Private Cloud" exams (71-246 & 71-247) are available for Beta testing now
• Microsoft Certified Solutions Expert (MCSE) is reinvented for the cloud, "MCSE: Private Cloud"
• You must have good understanding of all MS Private Cloud products to have a good change

Windows Server & Windows Client

• Windows Server 8 is called Windows Server 2012 from now on, and will be released this year (2012)
• MCITP Windows Server 2008 has become MCSA (Microsoft Certified Solutions Associate) Windows Server 2008
• App-V 5.0 and UE-V (User Experience Virtualization) are available for download now
• There will be four Windows 8 client versions released, Windows 8 (x86/x64) and Windows 8 Pro (x86/x64)
• Metro style will be supported in ConfigMgr 2012 around the Windows 8 release, isn't that cool?!

Configuration Manager 2012

• Configuration Manager 2012 and Endpoint Protection 2012 are RTM now
• In ConfigMgr 2012 it will be possible to publish Metro style apps and Microsoft store apps
• Migration tools are really useful to migrate ConfigMgr 2007 components to ConfigMgr 2012
• Application approval in ConfigMgr 2012 and Service Manager 2012 is possible
• New Package Conversion Dashboard available for application migration, which is a seperate download
• App-V integration in ConfigMgr 2012 requires a App-V 4.6 client, otherwise it won't work
• You can simulate installation and removals for all kind of applications (e.g. MSI, App-V, XenApp)
• Package Conversion Dashboard has a deep integration in the ConfigMgr console, but must be installed seperately
• Citrix XenApp publications visible in ConfigMgr console now, publish as XenApp or App-V package
• Citrix Receiver is publishing apps deployed by ConfigMgr 2012, as XenApp or App-V package

Windows Intune & Embedded Device Manager

• Windows Intune pre-release announcement on April 18th 2012, during the Microsoft Management Summit
• With Windows Intune you can control and publish apps to iOS and Android devices
• With an Exchange connector, Windows Intune can manage Exchange ActiveSync (EAS) connected devices
• Windows Intune will support multiple Exchange policies, ConfigMgr will not (yet)
• Device Manager 2011 SP1 integrates with ConfigMgr 2007, Device Manager 2012 integrates with ConfigMgr 2012
• New in WEDM 2012: Software distribution & Software updates (above Compliance, Collections and Device imaging)

Microsoft Deployment Toolkit 2012

• Microsoft Deployment Toolkit (MDT) 2012 is RTM and available for download now
• Much of new features in MDT 2012; it will give you way more value on top of ConfigMgr functionality
• With DaRT tools in MDT 2012 it's possible to have remote control functionality in WinPE step
• MDT 2012 will have support for the new application model in ConfigMgr 2012 too
• In MDT 2012 there's continued support for ConfigMgr 2007, isn't that good news?!

Mobile Device Management

• Microsoft will provide deep management of almost all mobile devices, including Windows Phone, Android and iOS

Next year MMS 2012 will be in New Orleans, Louisiana. Hope to be there again for my 3rd Microsoft Management Summit!

Microsoft Private Cloud beta exams

For the first time ever at MMS, attendees can take Microsoft Certification Exams onsite. For those interested in the Private Cloud — you could be one of the very first to take the beta version of Microsoft’s private cloud certification exams.

The Beta version of the exams for the Private Cloud certification allows Microsoft to develop the most relevant exams to build a private cloud on Microsoft technologies. Those who achieve a passing score will be among the very first to receive the Private Cloud certification.

The Microsoft Private Cloud beta exams are:
Exam 071-246: Private Cloud Monitoring and Operations with System Center 2012
Exam 071-247: Private Cloud Configuration and Deployment with System Center 2012

You won’t want to miss this amazing opportunity to fulfill your certification requirements, and with the new Certification Center at MMS, you’ll have the chance to learn, practice, and even talk one-on-one with the training experts on a variety of technologies.

On Monday 16th I will attend both Exam Cram sessions for training.
On Thursday 19th and Friday 20th I will attend both beta exams.

Nice to be first (in the world) to take this beta exams!

Microsoft Management Summit 2012 sessions

Every year around April there's a huge Microsoft event called Microsoft Management Summit (MMS). This event is the top in Management solutions build on Microsoft System Center. This year I'm attending MMS also. I was there before in 2009, and now 3 years later, I will return to Las Vegas. Happy to be at this great event again!

The following topics I'm trying to schedule:

• Microsoft Deployment Toolkit 2012
• Microsoft Private Cloud overview
• Mobile Device Management solutions
• System Center Configuration Manager 2012
• System Center Endpoint Protection 2012
• System Center Operations Manager 2012
• Windows 7 deployment tips & tricks
• Windows Embedded Device Manager 2012

Nice to see that most sessions are about the new System Center 2012 suite and Microsoft Private Cloud solutions. Too much interesting sessions for me to schedule I guess :)

Windows 8 Consumer Preview available for download

On 29-2-2012 the second build of Windows 8 (server and client) is showed to the world. After the Windows Developer Preview earlier last year, there's now a Consumer Preview available for download. Windows 8 (server and client) is build on Metro, the User Interface we know from Windows Phone 7 devices. That way it's usable on servers, desktops, laptops and tablets, with touch interface!

The Windows 8 Consumer Preview ISO can be download HERE
The Windows Server "8" Beta ISO can be download HERE

How to install Windows 8 Consumer Preview from an ISO image

The easiest way to convert an ISO file to a DVD in Windows 7 is to use Windows Disc Image Burner. On a PC running Windows XP or Windows Vista, a third-party program is required to convert an ISO file into installable media—and DVD burning software often includes this capability. One option is the USB/DVD download tool provided by the Microsoft Store. You can also download Windows 8 Consumer Preview Setup, which includes tools that allow you to create a DVD or USB flash drive from an ISO file (Windows Vista or Windows 7 required).

More blogposts available for Windows 8 also:

Guide to install Windows 8 on a VHD (Virtual Hard Disk)

Guide to remove Windows 8 on a VHD (Virtual Hard Disk)

PXE Boot files in RemoteInstall folder explained

When installing WDS for PXE Boot functionality a RemoteInstall folder will be created. Most of times I install this role on the SCCM/ConfigMgr server with MDT integration. It's also possible to use a different server for that, as long the ConfigMgr PXE service point is installed on that server also. In this post I will explain the PXE Boot files which are installed.

After installation, the following files and folders are available in the RemoteInstall folder:

SMSBoot
- abortpxe.com > Used when no advertisement is available
- bootmgfw.efi > (available in x64 folder only)
- bootmgr.exe > In Boot order this is file 3 needed
- pxeboot.com > In Boot order this is file 2 needed
- pxeboot.n12 > Can be used to skip the second F12 requirement (!)
- wdsnbp.com > In Boot order this is file 1 needed (!)
SMSIMAGES
- Boot.xxx00001.wim (WDS x86 boot image)
- Boot.xxx00002.wim (WDS x64 boot image)
SMSTemp
- A temporary folder for updating boot images
Stores
- This is the Drivers (Metadate) store

The following outlines the download process.

1. A client is directed (by using DHCP Options or the PXE Server response) to download Wdsnbp.com
2. Wdsnbp.com validates the DHCP/PXE response packet and proceeds to download PXEBoot.com.
Note: PXEBoot.com requires the client to press the F12 key to initiate PXE boot. One can rename one of the other PXE boot files (such as pxeboot.n12) to download Wdsnbp.com to a different file. 
3. PXEBoot.com downloads Bootmgr.exe and the BCD store. The BCD store must reside in a \Boot directory in the TFTP root folder. Additionally, the BCD store must be called BCD.
4. Bootmgr.exe reads the BCD operating system entries and downloads Boot.sdi and the Windows PE image (Winpe.wim).
5. Bootmgr.exe begins booting Windows PE by calling into Winload.exe within the Windows PE image.

And some additional information also:

When using DHCP Options for PXE Boot, Option 66 and 67 are needed. Option 66 must be the IP-address of your WDS server, Option 67 must be SMSBoot\x86\wdsnbp.com (which is the first file needed during the PXE Boot process).

The default pxeboot.com triggers an F12 requirement. The first F12 requirement is needed when Network Service boot is not on top of list in the BIOS boot order. The second F12 requirement is needed because of pxeboot.com, which is only needed when using Lite Touch Installation (LTI).

The second F12 requirement can be skipped however when renaming the default pxeboot.com to pxeboot.f12 and pxeboot.n12 (which means no F12) to pxeboot.com. After that the second F12 requirement is not needed anymore, also not for Lite Touch Installation (LTI). This must be done in both the x86 and x64 folder to make it functional.

More information about "Troubleshooting the PXE Service Point and WDS in Configuration Manager 2007" can be found HERE

Microsoft Application Compatibility Toolkit 5.6 upload error

When installing Microsoft Application Compatibility Toolkit (ACT) it's possible to start inventory and application compatibility. ACT helps identifying which applications are compatible with Windows 7 (and Vista) operating systems. ACT is actually a collection of multiple tools. More about that HERE

In ACT it's possible to create an Inventory package, which can be deployed by Group Policy. That way an ACT Data Collector Service will be installed, which will running as long as configured in the Inventory package. The ACT service will collect application compatibility data and will send the information back to the ACT database.

But what to do when no data is returned? Just have a look at Event Viewer then. In my case there where a lot of ACT-LPS and ACTUpload errors. The ACT-LPS warning can be skipped, because it's not the problem here. The real problem is the ACTUpload error. This because I'm trying to upload inventory logs from Windows 7 SP1 devices.

The ACT v5.6 log processing server does not process logs gathered from Windows 7 or Windows Server 2008 R2 machines with SP1 installed. These logs are moved to the Failed folder on the log share and the data is not entered into the database. This is due to the fact that the ACT 5.6 database does not have an entry describing Windows 7 SP1 or Windows Server 2008 R2 SP1 and therefore does not recognize the operating system of the computer that created the log.

To resolve this problem, an entry describing Windows 7 SP1 or Windows Server 2008 R2 SP1 must be added to the ACT database's Dbo.OS table. This is described on Microsoft Support: http://support.microsoft.com/kb/2533953

It's possible also to change the Windows version in the XML files, which can be found in the [Log share]\Failed folder. A quick look in my file showed this in the 5th line of the XML: <OsInfo Id=”6.1.1” ...>
I manually changed that number to 6.1.0 and the file got imported correctly. Version 6.1.0 is for Windows 7, 6.1.1 is for Windows 7 SP1, but that’s not yet in the ACT Database. When moving files again from the [Log share]\Failed to the parent folder (one step higher) they will be in processed and placed in the [Log share]\Processed folder.

When application compatibility data is collected, check Send and Receive Data, and choose which data can be synced to Microsoft. In return you get compatibility information on all applications that other people have tested before.

Now you have a list of all applications with Windows 7 compatibility information! Just use it for free.

Using MAP and ACT for Windows 7 installation or migration

When migrating to Windows 7 you don't know if hardware is capable for that. Microsoft released a few tools for that, so you know if it's ready for Windows 7. These tools are Microsoft Hardware Assessment and Planning Toolkit (MAP) and Application Compatibility Toolkit (ACT). In this blogpost I will explain both tools and more tips and tricks also.

Microsoft Hardware Assessment and Planning Toolkit (MAP) is a tool that will help you prepare for a Windows 7 (or Office 2010) migration. It will help you inventory your hardware and verify that it's capable for that. MAP is an agentless, automated, multi-product planning and assessment tool for quicker and easier desktop and server migrations. Since there will be no agents installed, it uses WMI for inventory.

When starting inventory it's possible that Insufficient data is displayed. This because of non-existing objects or the're turned-off. It's possible also that firewall or WMI problems is the cause here. Most of times this can be found in the reports, which can be created. It will be saved as an Xlsx and Docx file. On the ClientAssessment tab (Xlsx) there will be errors like: Connection time out & Machine not found.

In Assessment Properties you can set custom settings for hardware requirements. That way you can decide yourself which hardware is ready for Windows 7 installation or migration. It can be used for other discoveries also. MAP can be download here: MAP v6.5

The Application Compatibility Toolkit (ACT) is a tool for inventory and application compatibility. It's kind of same as MAP, but it's strenght is on the application compatibility side. Not on the inventory side (we use MAP for that). ACT helps identifying which applications are compatible with Windows 7 (and Vista) operating systems. ACT is actually a collection of multiple tools.

In ACT it's possible to create an Inventory package, which can be deployed by Group Policy. That way an ACT Data Collector Service will be installed, which will running as long as configured in the Inventory package. The ACT service will collect application compatibility data and will send the information back to the ACT database.

When application compatibility data is collected, check Send and Receive Data, and choose which data can be synced to Microsoft. In return you get compatibility information on all applications that other people have tested before. Now you have a list of all applications with Windows 7 compatibility information. ACT can be download here: ACT v5.6

With MAP and ACT usage it's possible to check for installation and migration information and application compatibility! Just use it for free.

Microsoft Management Summit 2012

Every year around April there's a huge Microsoft event called Microsoft Management Summit (MMS). This event is the top in Management solutions build on Microsoft System Center. This year I'm attending MMS also. I was there before in 2009, and now 3 years later, I will return to Las Vegas. Happy to be at this great event again!

This year’s Tracks include:

• Application Management – includes things like Windows Azure, System Center Virtual Machine Manager, System Center App Controller 2012, Operations Manager, and Performance Management.
• Client and Device Management – includes things like Windows 7, Windows Intune, System Center 2012 Configuration Manager, System Center 2012 Endpoint Protection, WEDM, VDI, Cross-platform Management, Microsoft Application Virtualization (App-V), Microsoft Enterprise Desktop Virtualization (MED-V), Microsoft Desktop Optimization Pack (MDOP), Windows Internet Explorer 8, Windows Internet Explorer 9
• Fabric Infrastructure Management – includes things like System Center Virtual Machine Manager, System Center Operations Manager, System Center Data Protection Manager, System Center Configuration Manager, and System Center Advisor.
• Server and Virtualization Management – includes things like Windows Server 2008 R2, Windows Server 8, Group Policy, WSUS, PowerShell/WMI, System Center Advisor, AD, and Forefront Identity Manager.
• Service Delivery and Automation – includes things like Service Manager, Service Catalog, Orchestrator, and Private Cloud.

Most of sessions I will follow are in the Client and Device Management section. Thanks to myITforum for above information!

New: Using the System Center 2012 Unified Installer

System Center 2012 Unified Installer is a utility designed to perform new, clean installations of System Center 2012 for testing and evaluation purposes only. If you want to upgrade from an existing System Center installation or choose set up options such as high availability or multi-server component installs, please refer instead to the System Center 2012 component installation guides located on the Microsoft Private Cloud Evaluation Resource Page.

With the Unified Installer it's possible to install all System Center products as once, without the need to install a single product multiple times. That way products can be installed quicker and less screens are needed to install them. Just download Microsoft Private Cloud Evaluation Software first.

Just start the Setup.exe in the Unified Installer folder. Then the Install System Center button becomes available! After that a message box is diplayed.

Then the installation begins..

• Microsoft Software License Terms
• Component Selection (Orchestrator, Virtual Machine Manager, App Controller, Operations Manager, Configuration Manager, Service Manager & Data Protection Manager)
• Keep the following in mind:
• Orchestrator is a required Product Component (Unified Installer requires Orchestrator)
• App Controller depends on Virtual Machine Manager
• I've selected Orchestrator, Operations Manager & Configuration Manager here
• Component Media Location (for all products selected)
• Configuration Manager License Terms
• Prerequisite License Terms
• Prerequisite Media Location (e.g. SQL Server 2008 R2 + SP1 + CU4)
• Installation Destination Location (for all products selected)
• Servers (for all products selected)
• Service Accounts (Installer Account)
• Component Specific Questions (e.g. OpsMgr Management Group, ConfigMgr Site Code & Site Name)
• Communications and Updates
• Installation Validation
• Deployment Progress
• Deployment Summary Report

That's all you need to do to install the Microsoft Private Cloud Evaluation software. The hardest part here is to have enough available servers, download the Microsoft Private Cloud Evaluation software and all prerequisites needed for all products. Then the rest is fairly easy.

Update 30-1: Unfortunately it doesn't work in my demo environment. Even when I follow all needed preparation from Microsoft Technet, it's still failing on the first server, which is System Center Orchestrator. The error message displayed is: ERROR - Could not execute System Center Orchestrator Failed WinRM configuration checkWinRM configuration not confirmed. I like to hear feedback from other people on this specific installation. Maybe it's a known issue for you?

Update 6-2: Today I started the installation again because of new feedback (see comments). Thanks to ThomasH it's working now. Probably using WinRM is not enough when domain policies are also into place. Using Local Policies will start the installation and pass the WinRM configuration, which was failing before. Thanks for all feedback guys!

More information about the Unified Installer can be found on Microsoft TechNet: Unified Installer Release Candidate

Download System Center 2012 Release Candidate (RC)

Today Microsoft released the System Center 2012 Release Candidate plus optional Windows Server 2008 R2 SP1. Microsoft also released the new System Center 2012 Licensing model today. More about that HERE

The System Center 2012 Release Candidate contains:

• System Center 2012 Unified Installer (RC)
• System Center 2012 App Controller (Beta)
• System Center 2012 Configuration Manager (RC2)
• System Center 2012 Data Protection Manager (RC)
• System Center 2012 Endpoint Protection (RC2)
• System Center 2012 Operations Manager (RC)
• System Center 2012 Orchestrator (RC)
• System Center 2012 Service Manager (RC)
• System Center 2012 Virtual Machine Manager (RC)

Please Note: Many Microsoft private cloud scenarios require Windows Server 2008 R2 SP1. If you are using an older version, we highly recommend upgrading to experience the full Microsoft private cloud evaluation.

The Windows Server 2008 R2 SP1 is available in these languages: Chinese (Simplified), English, French, German, Japanese, Spanish

System Center 2012 Release Candidate is available for download now on Microsoft TechNet. GET STARTED NOW

Download Microsoft Private Cloud Evaluation Software

Today Microsoft released the System Center 2012 Release Candidate plus optional Windows Server 2008 R2 SP1 (a.k.a. Microsoft Private Cloud). Microsoft also released the new System Center 2012 Licensing model today. More about that HERE

A Microsoft private cloud dramatically changes the way your business produces and consumes IT services by creating a layer of abstraction over your pooled IT resources. This allows your datacenter to offer true infrastructure service capability as well as optimally managed application services.

Microsoft private cloud solutions are built on System Center and Windows Server.

System Center 2012 Release Candidate empowers you with a common management toolset for your private and public cloud applications and services. System Center helps you confidently deliver IT as a Service for your business.

Windows Server 2008 R2 SP1 (optional download) will give you improved powerful virtualization capabilities that can transform how you deliver IT services to your end users and enable you to lay the foundation of a private cloud infrastructure.

Please Note: Many Microsoft private cloud scenarios require Windows Server 2008 R2 SP1. If you are using an older version, we highly recommend upgrading to experience the full Microsoft private cloud evaluation.

The System Center 2012 Release Candidate contains:

• System Center 2012 Unified Installer
• System Center 2012 App Controller
• System Center 2012 Configuration Manager
• System Center 2012 Data Protection Manager
• System Center 2012 Endpoint Protection
• System Center 2012 Operations Manager
• System Center 2012 Orchestrator
• System Center 2012 Service Manager
• System Center 2012 Virtual Machine Manager

System Center 2012 Release Candidate is available for download now on Microsoft TechNet. GET STARTED NOW

Improvements to System Center 2012 Licensing

Today Microsoft released a new System Center 2012 Licensing model. Benefits of this new licensing model is Simplicity and Private Cloud optimization. Microsoft is committed to delivering products to customers that meet their current and future needs with as little complexity as possible. Key Licensing changes in System Center 2012 are:

Server Management Licensing:
System Center 2012 management licenses will be released in 2 editions differentiated by virtualization rights only:

• Datacenter: Maximizes cloud capacity with unlimited Operating System Environments (OSEs) for high density private clouds.
• Standard: For lightly or non-virtualized private cloud workloads.

The only difference between the editions is the number of Operating System Environments (OSEs) that you can manage per license. Datacenter Edition allows the management of an unlimited number of OSEs per license. Standard Edition allows the management of up to two OSEs per license.

To provide you with the capabilities you need to manage a private cloud, both Standard and Datacenter editions of System Center 2012 include all the System Center components relevant to managing servers:

• Configuration Manager (ConfigMgr)
• Service Manager (SCSM)
• Virtual Machine Manager (SCVMM)
• Operations Manager (OpsMgr)
• Data Protection Manager (SCDPM)
• Orchestrator (SCO)
• App Controller (SCAC)
• Endpoint Protection (SCEP)

Client Management Licensing:
System Center 2012 client management licensing provides simple, cost-effective options to manage and protect client systems. Client management licenses are available in three offers:

• Configuration Manager 2012: available on a per-user or per-OSE basis as well as in the Core CAL and Enterprise CAL suites.
• Endpoint Protection 2012: available as a per-user or per-device subscription as well as in the Core CAL and Enterprise CAL suites.
• Client Management Suite: available on a per-user or per-OSE basis as well as in the Enterprise CAL suite. It is composed of DataProtectionMgr, OpsMgr, ServiceMgr, and Orchestrator.

Core CAL and Enterprise CAL Suites will continue to be the most cost effective way to purchase client management products.

For more information about the new System Center 2012 Licensing model visit: Microsoft Volume Licensing

Deploy Windows Thin PC (WinTPC) with MDT 2010

Last year, on July 1, 2011 actually, Windows Thin PC (WinTPC) is released. WinTPC images are smaller than Windows 7 images, and hence have a lower attack surface.

WinTPC is an Microsoft Software Assurance (SA) benefit that provides a low footprint, locked down version of Windows 7 that enables organizations to repurpose existing PCs as thin clients, thereby reducing the need for new thin client hardware. And since these PCs retain their existing SA coverage, they do not need any additional Windows Virtual Desktop Access (VDA) licensing for VDI. 

WinTPC offers an excellent thin client experience by locking down the PC through write filters, while still providing users with a superior remote desktop experience through RemoteFXTM support. IT can deploy and manage WinTPC images to multiple PCs using System Center Configuration Manager (SCCM), and push updates to these PCs using Windows Update or Windows Server Update Services (WSUS).

Additionally, WinTPC leverages Windows Enterprise features such as BitLocker and AppLocker to further secure the endpoint. With BitLocker and BitLocker To Go technology WinTPC disk drives and flash storage can be encrypted, thereby ensuring that any data stored on disk is secure. With AppLocker, IT can prevent unauthorized applications from running on WinTPC.

WinTPC is a locked down version of Windows 7, and hence, will be able to run on any device capable of running Windows 7. The recommended specifications for running Windows Thin PC are:

• 1 GHz or faster 32-bit (x86) processor
• 1 GB RAM
• 16 GB available hard disk space

WinTPC can be deployed with ConfigMgr 2007 and MDT 2012. With MDT 2010 it's possible also, but then a unattend.xml change is needed. As mentioned in Windows Thin PC: Another flavor of Windows 7 the <UpgradeData> section from the unattend.xml that you use to deploy WinTPC must be removed then. Then it's working in MDT 2010 also. WinTPC can be deployed in just 15 minutes with MDT usage!

For managing WinTPC the normal Windows 7 Group Policies can be used. That way even more functionality can be excluded from the already stripped version of Windows 7. With write filters the disk partition can be keeped clean. WinTPC has both file-based and enhanced write filters. Write filters can be enabled to prevent users and applications from writing to disk, and hence ensure that the OS returns to a pristine image on every reboot.

With WinTPC you can have a fast Windows 7 version on almost all types of hardware which have Windows XP or Vista support. Just install the OS and have a look at yourself. Download 90 days trial

Mobile Device Management in ConfigMgr 2012

Next year (probably around MMS 2012) ConfigMgr 2012 will be released. One of the new features in this release will be Mobile Device Management integration. In the current System Center suite there was a single product for that, named: System Center Mobile Device Manager (SCMDM). Also there was a small integration in ConfigMgr 2007 possible. Both solutions were based on Windows Mobile 6.x devices. Because most customers have various mobile phone solutions this was not really an option. With ConfigMgr 2012 actually it is!

With Mobile Device Management in ConfigMgr 2012 there is more integration possible with mobile phone solutions. There will be support for iPads, iPhones, Symbian devices, Android devices and Windows Phone 7 devices. There will be a difference in Light Management and Depth Management devices. This can be seen on the following picture:

For Light Management devices an Exchange connector will be used. Then Mobile Device Management (MDM) will have the same functionality as in Exchange 2010 (nothing more unfortunately). With Depth Management there is more management possible, but only on WinCE 6.0, WM 6.0/6.1, WP 6.5 and Nokia Symbian based devices.

Let's hope there will be more functionality on Light Management devices above Inventory, Settings Management & Remote Wipe, like: Over the air enrollment & Software Distribution. Remote management on multiple platforms will be key here!

It's also possible to use Odessey's Athena to extend MDM functionality. More information about that can be found here: Symantec Athena Then the following functionality becomes available:

• Live, remote control of devices in the field
• Device software, application & patch provisioning & installation
• Comprehensive software and hardware asset information
• Location based data via GPS (current and bread crumb)
• Detailed phone and messaging information and stats
• Security to protect sensitive data (device lock & wipe)

In the Beta2 and RC releases available for download there isn't much to do on MDM functionality. Let's wait till ConfigMgr 2012 will be released (RTM or Final version) to see more of this.

More information about: System Center Mobile Device Manager
More information about: Mobile Device Management in Configuration Manager (2007)
More information about: Determine How to Manage Mobile Devices in Configuration Manager (2012)

Latest news on MS System Center 2012 Suite

This year the MS System Center 2012 Suite will be presented. There's nothing official to find about release dates, so my guess stays on Q1 2012 or probably Microsoft Management Summit (MMS) which is in April 16-20. The last months there were some interesting news around System Center, so here a quick overview.

Here we go:

• All products within the MS System Center 2012 Suite will have a new release (on the same time)
• There will be more integration within the various System Center products (because of Service Manager and Orchestrator)
• Service Manager will be the most important product in the 2012 suite (integration with Operations Manager [tickets], Configuration Manager [assets], and so on)
• Service Manager 2012 is the only version which integrates with Configuration Manager 2012, not the current one
• Forefront Endpoint Protection (FEP) will be called System Center Endpoint Protection (SCEP) from now on
• There will be integration between ConfigMgr and Orchestrator (checks and so on)

And some ConfigMgr 2012 news also:

• There will be Migration tools build-in to migrate applications, collections and OS images (and so on) by default
• With Package Conversion Manager (PCM) it's possible to convert old 2007 packages to the new 2012 application model
• Mobile Device Management (MDM) will have the same functionality as in Exchange 2010 (nothing more unfortunately)
• It's possible to simulate application deployments before they actually will be installed (isn't that cool?)
• Endpoint Protection will be integrated in ConfigMgr 2012 by default (no extension anymore)
• There will be (probably) e-mail notification in Software Catalog approvals (not in the console only)

It will be an exciting year with new products/functionality, and finally a brand new MS System Center 2012 Suite!