Doing a ConfigMgr 2012 R2 SP1 fresh installation

Recently I did a blogpost about doing a ConfigMgr 2012 R2 SP1 upgrade. This because it will result in different behavior, and running tasks in the background after the upgrade. This time I started a ConfigMgr 2012 R2 SP1 fresh installation, which is something different really. Installation is doing fine with no running tasks in the background after installation. Much better this way!

And I needed both installation media this time as well :-)

This because starting with this release, Microsoft has merged the 2012 and 2012 R2 codebase. This means form this point forward both 2012 and 2012 R2 use the exact same files. The ONLY difference is a setting that blocks 2012 users from certain features to R2 because they've not paid for it. This is where the two files come in:

SC2012_SP2_ConfigMgr_SCEP.exe is the actual install/upgrade binary that everyone needs to run.
SC2012_R2_SP1.exe is the file which serves one purpose only: an upgrade path for people from 2012 to 2012 R2, if they upgrade their license to unlock the locked-out features. That's why it's so small. Remember it will NOT upgrade your ConfigMgr infrastructure.

More about that here: System Center Configuration Manager Team Blog (in comments)

Installation progress in short:

Installation is done within 35 minutes, with no running tasks left. Use the file 'SC2012_SP2_Configmgr_SCEP.exe' for that.

After installation you have System Center 2012 Configuration Manager SP2 in-place, with no R2 features available.

After that start the file 'SC2012_R2_SP1_Configmgr.exe' to continue. This file unlocks R2 features missing in the other installation. You will need a R2 license for that officially.

Installation is done in a blink of an eye. This because it's used only to unlock R2 features in the ConfigMgr console.

When starting the console again, you have System Center 2012 R2 Configuration Manager SP1 now. Very nice indeed :-)

From now on this will be the way for fresh ConfigMgr installation. Stay tuned for more ConfigMgr news soon!

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1

Check the database before doing a ConfigMgr 2012 R2 SP1 upgrade

When doing a ConfigMgr upgrade (like ConfigMgr 2012 R2 SP1), it's good to check the database first. When upgrading a production environment, you want to make sure that everything went fine, and no error is given on the database. This can be done with the following command(s), which are recommended before upgrade.

When you want to start a Database Consistency Check against the ConfigMgr database, run the command: DBCC CHECKDB
This performs the following operations:
-Runs DBCC CHECKALLOC on the database.
-Runs DBCC CHECKTABLE on every table and view in the database.
-Runs DBCC CHECKCATALOG on the database.
-Validates the contents of every indexed view in the database.
-Validates the Service Broker data in the database.

Source: https://technet.microsoft.com/en-us/library/bb693745.aspx 

After that build a new server with the same SQL installation (version and configuration like collation) and import a copy of the ConfigMgr database on that server. This because you cannot test a database upgrade on a active ConfigMgr Site server! To test the database upgrade before doing it in production environment, just run the command: SMSSETUP\BIN\X64\Setup.exe /TESTDBUPGRADE <database> (from new ConfigMgr installation media)

Start Begin TestDBUpgrade

Yes, I'm sure about it :-)

TestDBUpgrade is done

After some time (22 minutes in my case) the following message is displayed in ConfigMgrSetup.log: Configuration Manager Setup has successfully upgraded the database. With that it's time to start the upgrade in production environment as well. Don't forget to have a good backup (as mentioned earlier) all times.

Happy upgrading! :-)

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1
Doing a ConfigMgr 2012 R2 SP1 upgrade (Notes from the field)

Doing a ConfigMgr 2012 R2 SP1 upgrade (Notes from the field)

Last week I did a lot of ConfigMgr 2012 R2 SP1 upgrades already. I did 5 upgrades on different environments, resulting in different behavior. Let's have a look at that. Before you begin just make sure you have a good backup! Most of time I start with a ConfigMgr backup and snapshot of ConfigMgr and SQL VM's. Better safe then sorry :-)

Then start the SP2 media (still confusing) to implement SP1 in your environment. It will be finished in around 30-45 minutes. The crazy part is starting after that. ConfigMgr isn't done with the upgrade, but running tasks in the background. Strange enough it's hard to see what's the status of that, and sometime it's stuck too and a reboot is needed. Let's have a look again.

When the upgrade wizard is finished and you start the ConfigMgr console, have a look at Site & System status. The MP will be down for almost one hour. When looking at Software Library the ConfigMgr client package and boot images are not updated yet. Because of that OS deployment isn't possible too. Sometimes it will be started automatically within one hour, sometimes a reboot is needed to start processing again. A nasty situation for sure.
 
Installation progress in short: 

Installation done in the wizard

 

Installation done in the logfile 

 

Installation is done, but a lot of components still needs to be updated:

-Monitoring components installation
-Monitoring server roles installation
-Setting up management point
-Installing services
-Installing Component Monitor
-Installing SMS Executive
-Installing Database Notification Monitor
-Installing Site Control Manager
-Installing Hierarchy Manager
-Installing Inbox Manager
-Installing policy provider
-Installing management point control manager

 

Management point in critical state

 

SMS Replication Configuration Monitor stops

 

SMS Site Component Manager degraded

 

Site Component Manager stopping

 

Site Component Manager shut down

  

The Management point is in critical state, because it must be installed again. No communication possible for almost one hour. The SMS Site Component Manager is degraded, because most of Site components needs to be installed again. When installation is stuck, it may help to reboot the Primary server. (not recommended, just wait first)

 

 

When looking at Component Status, they will be gone (66 items) because communication is down. Big oops moment :-)

SMS MP Control Manager back online

 

Site Components back online

 

As I sayed earlier, it can take on hour before the Management point is healthy again and Site Components are back in business. It may help to reboot the Primary server once, when there's no progress seen (recommended only when nothing changed after one hour). After the reboot you will see that functionality is restored soon! When looking at Software Library the ConfigMgr client package and boot images will be updated now. Still it's a nasty upgrade, because you think it's done in 30-45 minutes, and not one hour after that. Strange enough it's hard to see what's the status of that, and sometimes it's stuck too and a reboot is needed.

Why not mention in the wizard, installation is not finished and will take another hour? Or count another hour on the wizard and finish it in 60-90 minutes, instead of running tasks in the background? I guess this can be better with another release in future. Hope it helps!

More blogposts about ConfigMgr 2012 R2 SP1:
ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)
New functionality in System Center 2012 R2 Configuration Manager SP1

Update: More status pictures will be added soon!

New functionality in System Center 2012 R2 Configuration Manager SP1

Last week I did a few blogposts about the System Center 2012 R2 Configuration Manager SP1 Release and Upgrade. After the upgrade both Consoles and Clients must be upgraded as well. ConfigMgr clients can be upgraded with the Automatic Client Upgrade (like always when installing big updates). Let's have a look at new functionality added to the ConfigMgr console and boot images.

After installation the version has changed to 5.00.8239.1000 in About Configuration Manager dialog box and Site server properties. The current ConfigMgr 2012 R2 key will work with R2 SP1 also.

The OSD screen is changed and looks a little better if you ask me..

With all checkmarks enabled (which is default), only drivers that match the architecture, which are in the storage or network class, and are digitally signed are available. Much better, because I've seen complete driver packages in boot images before!

Deployment Verification is a cool feature, that makes sure no deployment on default collections (except All Unknown Computers) and collections with more then 100 systems (which is a default value) can be done. No more Required deployments on the All Systems collection from now on :-)

During deployment no default collections (except All Unknown Computers) and collections with more then 100 systems (which is a default value) are available. A message is displayed, that deployment has potential to be a high risk one.

When a required deployment is done, and the checkmark "Hide collections with a member count greater than site's minimum size configuration" is unchecked, a message is displayed. A checkmark must be set on "I want to create this high risk deployment (This wil generate an audit status message)" to continue.

With Cumulative Update 1 to 5 included, and a bunch of improvements, it's a must-have to install SP1 in your organization. I installed it twice already without any problems. Let's wait for ConfigMgr 2016 later this year (Q4 CY2015) now!

Upgrade ConfigMgr 2012 R2 to SP1 with SP2 media (confusing)

Today I started my first (and second) ConfigMgr 2012 R2 upgrade. When looking on Microsoft Evaluation Center, there is the choice between ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 media. When looking at ConfigMgr 2012 R2 SP1 there's the choice between a SP2 and SP1 file as well. Strange thing is SP2 is 762MB in size and SP1 is only 1,10MB in size. Let's have a look at some more information about this (Preinstall Information).
 

Upgrading your installation: If you have a System Center 2012 R2 Configuration Manager installation, you can use the System Center 2012 Configuration Manager SP2 media to install the latest patches and automatically upgrade to System Center 2012 R2 Configuration Manager SP1.
New installation: Install System Center 2012 Configuration Manager SP2 first, and then install System Center 2012 R2 Configuration Manager SP1 at the top-tier site of your hierarchy. Both of these installation files are included as part of this evaluation.
 

Error message when starting SP1 installation before SP2

When SP2 is installed, you can install SP1 successfully
(but it's needed only on new installations)

So yes, you must actually run ConfigMgr 2012 SP2 when you have ConfigMgr 2012 R2 SP1 installed. Very confusing if you ask me? Using ConfigMgr 2012 R2 SP1 is needed only for new installations at the top-tier site of your hierarchy. Crazy it's less then 5MB in size!? Otherwise it's not needed to install this file (but it surely does install fine after ConfigMgr 2012 SP2 too). Just checked that one too.

The installation/upgrade went fine after all, and was done within 60 minutes. The second upgrade was done within 100 minutes, but was a larger site to upgrade. There will be new functionality added to the ConfigMgr console and boot images as well. This will be mentioned in another blogpost published soon. Because R2 functionality is built-in, no need to use R2 media anymore!

After installation the version has changed to 5.00.8239.1000 in About Configuration Manager dialog box and Site server properties. The current ConfigMgr 2012 R2 key will work with R2 SP1 also.
 
More information about the servicepack can be found here: ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released
 
Microsoft websites to visit:
What's New in System Center 2012 R2 Configuration Manager SP1
Announcing the availability of System Center 2012 R2 Configuration Manager SP1 and System Center 2012 Configuration Manager SP2
Planning to Upgrade System Center 2012 Configuration Manager

ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 released

As mentioned on Microsoft Ignite last week, ConfigMgr 2012 R2 SP1 and ConfigMgr 2012 SP2 are now released and can be downloaded. The service packs deliver full compatibility with existing features for Windows 10 deployment, upgrade, and management. Also included in the service packs are new hybrid features for customers using ConfigMgr integrated with Microsoft Intune to manage devices. Some of the hybrid features that you can expect to see are conditional access policy, mobile application management, and support for Apple Device Enrollment Program (DEP). You can view the full list of hybrid features included in these service packs here: What's New in System Center 2012 R2 Configuration Manager SP1
 

 
Here's a list of improvements included, there are quite a lot of them:
-Sites and Hierarchies (2 improvements)
-Application Management (2 improvements)
-Content Management (6 improvements)
-Operating System Deployment (8 improvements)
-Reporting (3 improvements)
-ConfigMgr and Microsoft Intune (17 improvements)
 
Additional improvements that are included in this update:
-ConfigMgr Company Portal App (Windows 10 support)

To apply this update, you must have ConfigMgr 2012 (SP1/R2) installed. SP1/SP2 provides support for Windows 10 and improves data transfer reliability for slow and latent networks with new checkpoint restart functionality for distribution points and pull DPs. Increases secondary site from 5,000 clients to 10,000 clients and standalone primary to 150,000 clients. The version that is displayed in the About Configuration Manager dialog box is now 5.00.8239.1000.
 
This update replaces Cumulative Update 1 to 5 for System Center 2012 Configuration Manager R2

For more information have a look here: System Center Configuration Manager Team Blog
 
MSDN subscribers can expect these service pack downloads to be available next week. Microsoft is also planning to make these service packs available on the Volume Licensing Service Center (VLSC) on May 27th. You may also use your existing product key to transition from the evaluation version to the full product version.
 
More blogpost on this topic:
Microsoft Ignite day 1 (Keynote) recap
Microsoft Ignite day 2 (Session) recap
Cumulative Update 5 for ConfigMgr 2012 R2 released

Cumulative Update 5 for ConfigMgr 2012 R2 released

Today Cumulative Update (CU) 5 for ConfigMgr 2012 R2 is released. It fixes 13 issues and 1 additional change is included. No need to install CU4 anymore when using this one.

Here's a list of issues that are fixed, there are quite a lot of them:
- Reporting (1 fix)
- Software distribution and application management (3 fixes)
- Site servers and site systems (5 fixes)
- Client (1 fix)
- Operating system deployment (3 fixes)

Additional changes that are included in this update:
- Endpoint Protection (anti-malware platform update)

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. The version that is displayed in the About System Center Configuration Manager dialog box is 5.0.7958.1604.

This update replaces Cumulative Update 4 for System Center 2012 Configuration Manager R2

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

Note: Because ConfigMgr 2012 SP2 and 2012 R2 SP1 is released next week (may 14th) already, it's better to wait for the service pack then installing this one. Just saying ;) Why Microsoft is releasing another CU so soon before the SP is not clear to me. Do you?
Johan Arwidmark mentioned on twitter: Wow, don't deploy CU5 for SCCM 2012 R2, those updates are included in SP2 which is releasing next week, and SP's are more tested than CU's.

More information about the service pack:
Microsoft Ignite day 1 (Keynote) recap
Microsoft Ignite day 2 (Breakout) recap

Cumulative Update 4 for ConfigMgr 2012 R2 released

Today Cumulative Update (CU) 4 for ConfigMgr 2012 R2 is released. It fixes 27 issues and 4 additional changes are included. No need to install CU3 anymore when using this one.

Here's a list of issues that are fixed, there are quite a lot of them:
- Client (2 fixes)
- Software distribution and application management (6 fixes)
- Network Access Protection (1 fix)
- Operating system deploymenjt (2 fixes)
- Administrator Console (1 fix)
- Site servers and site systems (6 fixes)
- Mobile devices (5 fixes)
- Migration (1 fix)
- Reporting (2 fixes)
- Software updates (1 fix)

Additional changes that are included in this update:
- Windows PowerShell (lot of changes)
- Data replication (performance replications)
- Endpoint Protection (anti-malware platform update)
- Operating systems other than Windows (Mac OSX 10.10, Suse Linux Enterprise Server 12 (x64)

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. The version that is displayed in the About System Center Configuration Manager dialog box is 5.0.7958.1501.

This update replaces Cumulative Update 3 for System Center 2012 Configuration Manager R2

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

Install Cumulative Update 2 for ConfigMgr 2012 R2

Today I had time to install Cumulative Update 2 (CU2) for ConfigMgr 2012 R2. KB2970177 (CU2) solves a lot of issues in ConfigMgr and is therefore highly recommended. More about CU2 improvements in another blogpost. No need to install CU1 anymore, because it's integrated in CU2 (which is same as other cumulative update packs before). No need to install the latest Endpoint Protection anti-malware platform update also (which is from March 2014 at the moment). This one is integrated in KB2970177 (CU2) as well.

After installation, which is default as always, there will be update packages created and the version will be updated (5.0.7958.1303). To be better safe then sorry do a restart of the ConfigMgr server after patching. Still strange that Microsoft is saying it isn't needed (TechNet), but the installation wizard mentions it is needed! :)

After setup you have the benefit of all updates and hotfixes. Don't forget to update other ConfigMgr servers, consoles and clients as well. You can find packages for that in the console after the update.

Cumulative Update 2 for ConfigMgr 2012 R2 released

Last week (on June 21, 2014) Cumulative Update (CU) 2 for ConfigMgr 2012 R2 is released. It contains 20 updates and hotfixes included. No need to install CU1 anymore when using this one.
 
Here's a list of issues that are fixed, there are quite a lot of them:
- Administrator Console (2 fixes)
- Application Virtualization (2 fixes)
- Operating system deployment (5 fixes)
- Asset Intelligence (1 fix)
- Mobile device management (1 fix)
- Software distribution (3 fixes)
- Site systems (4 fixes)
- Configuration Manager SDK (1 fix)
- Client (1 fix)
 
In addition to various issue fixes, this update also includes the following:
- An updated Cumulative Update Setup Wrapper (Installer)
- Updated list of supported Linux and UNIX clients
 
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 R2 

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

Install Cumulative Update 1 for ConfigMgr 2012 R2

Today I had finally time to install Cumulative Update 1 (CU1) for ConfigMgr 2012 R2. KB2938441 (CU1) solves a lot of issues in ConfigMgr and is therefore highly recommended. More about CU1 another blogpost. No need to install KB2905002 anymore after installation. This because it's integrated in CU1 now.

Let's have a look at the installation:

First screen when running setup

When successful you can continue

5.0.7958.1203 is the new version

New update packages in the console

After setup you have the benefit of all updates and hotfixes. Don't forget to update other ConfigMgr servers, consoles and clients as well. You can find packages for that in the console after the update.

Cumulative Update 1 for ConfigMgr 2012 R2 released

Today Cumulative Update (CU) 1 for ConfigMgr 2012 R2 is released. It contains 22 updates and 7 hotfixes included. Great that the following issues are solved, because both of them I experienced last weeks:

-With App-V 5.0 SP2, App-V packages that are being used cannot be uninstalled (ever). > true!
-External drives, such as some USB thumb drives, are displayed as fixed disks instead of removable media. Attempts to start and install an OS image result in error messages. > true!

Here's a list of issues that are fixed, there are quite a lot of them:
-Administrator Console (3 updates)
-Mobile Device Management (1 update)
-Reporting (1 update)
-Application Virtualization (2 updates)
-Internet-based clients (1 update)
-Software Center (3 updates)
-Operating system deployment (6 updates and 4 hotfixes)
-Endpoint Protection (1 update)
-Application management (2 updates and 1 hotfix)
-Supported operating systems (1 hotfix)
-Site systems (1 update)
-Windows PowerShell (1 hotfix)
-Wake-up proxy (1 update)

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. Great that CU1 is available now!

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

Anti-malware platform update for Endpoint Protection clients

As you can see a new Endpoint Protection (SCEP) update is available for System Center (SCCM) 2012 R2 installations. This is the third update available for SCCM 2012 R2 till now. In this blogpost an overview of all R2 hotfixes.
 
1) An update is available for the "Operating System Deployment" feature of System Center 2012 R2 Configuration Manager
2) Per-computer variables for imported computers are not read in System Center 2012 R2 Configuration Manager
3) November 2013 anti-malware platform update for Endpoint Protection clients

This article describes an anti-malware platform update package for the following clients:
- SCCM 2012 R2 Endpoint Protection clients
- SCCM 2012 (SP1) Endpoint Protection clients
- Forefront Endpoint Protection (FEP) 2010 clients

These packages update Endpoint Protection client services, drivers, and UI components.

Microsoft regularly releases anti-malware platform updates to guarantee consistency in protection, performance, robustness, and usability in a malware landscape that is constantly changing. This update package is dated November 2013.

You can download the Hotfix here: Microsoft Support

New ConfigMgr 2012 R2 Policy Hotfix available

Yesterday a new ConfigMgr 2012 R2 Policy Hotfix is released. This because Per-computer task sequence variables that are defined for imported computers are filtered out of client policies. This prevents the variables from being read during task sequence execution. This problem does not affect per-computer variables that are defined for existing clients.

This update applies only to Primary sites.
Important Per-computer task sequence variables have to be recreated if they were created after System Center 2012 R2 Configuration Manager was installed but before this update is applied.

You can download the Hotfix here: Microsoft Support

New ConfigMgr 2012 R2 OSD Hotfix available

A few days ago a new ConfigMgr 2012 R2 OSD Hotfix is released. This because many customers couldn't PXE boot anymore. Have a look at these forums for more information about the issue:
Microsoft Technet, Windows Noob & MyITForum

This update resolves the following issues:
Issue 1
After you enable the PXE Service Point role on an instance of a specific distribution point, or you select the Deploy this boot image from the PXE-enabled distribution point property of a boot image, the Windows Deployment Service (WDS) stops running. Additionally, entries that resemble the following are logged in the Windows Application log:

Faulting application name: svchost.exe_WDSServer, version: 6.3.9600.16384, time stamp: 0x5215dfe3
Faulting module name: MSVCR100.dll, version: 10.0.40219.1, time stamp: 0x4d5f034a
Exception code: 0xc0000005
Fault offset: 0x000000000005f61a
Faulting process id: 0xae4
Faulting application start time: 0x01cec5d767184634
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Program Files\Microsoft Configuration Manager\bin\x64\MSVCR100.dll

Note This problem affects only distribution points that are installed on site servers.

Issue 2
When operating system image files are downloaded to Configuration Manager 2012 R2 clients, you may find that the download takes longer than it did in previous versions of Configuration Manager 2012 clients. You may see this behavior when the target client is running Windows PE or a full Windows operating system.

You can download the Hotfix here: Microsoft Support

System Center 2012 R2 downloadable VHDs available!

Do you want to experience System Center 2012 R2 products?
 
Microsoft have made VHDs available for evaluation:

 
System Center 2012 R2 Configuration Manager – Evaluation (VHD)
System Center 2012 R2 Service Manager – Evaluation (VHD)
System Center 2012 R2 Service Manager Data Warehouse– Evaluation (VHD)
System Center 2012 R2 Operations Manager – Evaluation (VHD)
System Center 2012 R2 Orchestrator – Evaluation (VHD)
System Center 2012 R2 Data Protection Manager – Evaluation (VHD)
System Center 2012 R2 Virtual Machine Manager – Evaluation (VHD) 
System Center 2012 R2 App Controller – Evaluation (VHD)

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

Update: Password for above VHDs is pass@word1 or Pass@word1 
This cannot be found on internet actually, but because passwords were used on older System Center VHDs before, the're still working. Just make usage of it!

Update 17-2-2016: New download links available!

System Center 2012 R2 Configuration Manager – Evaluation (VHD)
System Center 2012 R2 Service Manager – Evaluation (VHD)
System Center 2012 R2 Service Manager Data Warehouse– Evaluation (VHD)
System Center 2012 R2 Operations Manager – Evaluation (VHD)
System Center 2012 R2 Orchestrator – Evaluation (VHD)
System Center 2012 R2 Data Protection Manager – Evaluation (VHD)
System Center 2012 R2 Virtual Machine Manager – Evaluation (VHD)
System Center 2012 R2 App Controller – Evaluation (VHD)

Next Release of Windows Intune (v5) coming in 3 days!

During Microsoft TechEd Europe in June 2013, the next release of Windows Intune (Wave E) is announced. This release will focus on deeper System Center integration, more consistent experiences across different mobile devices, and better data protection. Windows Intune 5.0 will offer direct management for Android also, so no need to use EAS for that anymore.

Here is what we know so far:
 -Choice between Company-owned or Personal-owned to decide management
-Native self-service portal apps for Windows, iOS and Android devices
-Registering and Enrolling devices through the cloud
-Deploy VPN profile and Wi-Fi profile policies and configurations
-Supports more policies on all supported device types
-Selectively and remotely wipe corporate data from managed devices

It will be coming in 3 days (Oct. 18) when Windows Server 2012 R2, Windows System Center 2012 R2 and Windows 8.1 is released. Stay tuned for more news next week!

Mark Your Calendars for Oct. 18: The R2 Wave is Coming!

Reminder: Microsoft will release Windows Server 2012 R2, Windows System Center 2012 R2 and the latest update to Windows Intune in 3 days (Oct. 18), the same day Windows 8.1 will be released.

According to Microsoft Corporate Vice President of Windows Server and System Center Brad Anderson, it’s no coincidence that all four updates will be available on the same day. This will be done every time from now on! You can read more about it In the Cloud blog.

Recent posts about this topic:
Updates and New Features in ConfigMgr 2012 R2 (about System Center 2012 R2, Windows 8.1 and Windows Intune v5)

Premise vs. Premises in ConfigMgr 2012

Last month during the "Windows Management User Group (WMUG) NL day with Wally Mead", one minor detail was seen in the demo's. I guess nobody was seeing it (?), but I did because a colleague of my (Rob Beekmans, @robbeekmans) was mentioning it to me earlier. Here it comes! :-)

In ConfigMgr 2012 SP1 a Distribution Point type is called On-premise. This is wrong because the proper term is On-premises as in - on your premises (see below).

In ConfigMgr 2012 R2 they corrected this, because a Distribution Point type is now called On-premises. Good job Microsoft!

From Dictionary.com
Premise: a proposition supporting or helping to support a conclusion.
Premises: a tract of land including its buildings.

As I was saying before: one minor detail fixed! 

Upgrade ConfigMgr 2012 SP1 to 2012 R2 Preview

Last week ConfigMgr 2012 R2 Preview became available for download. More about that can be found in the following blogposts: "Updates and New Features in ConfigMgr 2012 R2" and "TechEd 2013 Europe announcements".

Now it's time to update labs with the new bits, Windows Server 2012 R2 Preview and System Center ConfigMgr 2012 R2 Preview. My existing lab is running on Windows Server 2012, SQL Server 2012 SP1 and ConfigMgr 2012 SP1. This installation is described in the following blogpost: "Install ConfigMgr 2012 SP1 on Server 2012 and SQL 2012 SP1". Let's update my lab!

I did an update of Windows Server 2012 first. Within 5 minutes (on SSD) Windows Server 2012 is upgradet to Windows Server 2012 R2 Preview. Nothing special on that one.

After that it's needed to remove Windows Assessment and Deployment Kit (ADK) 8.0 and install ADK for Windows 8.1 Preview. Just select Deployment tools, Windows PE and USMT again.

Last start the System Center ConfigMgr upgrade after that. As described in "Updates and New Features in ConfigMgr 2012 R2". Upgrade to R2 is possible only from ConfigMgr SP1 with Windows ADK 8.1 which can be found HERE.

Just follow these steps for the upgrade:
- Start Splash.hta and choose Install
- Before you begin > Next
- Getting started > Upgrade this ConfigMgr site
- Product key > Install the evaluation edition of this product
- License terms > Accept these license terms
- Prerequisite licenses > Accept these license terms (3x)
- Prerequisite downloads > Download required files (23 items)
- Server language selection > English
- Client language selection > English
- Settings summary > Setup type: Upgrade
- Prerequisite check > In my case 2 items about built-in collections and SQL memory allocation
- Begin install > Elapsed time: 21 minutes
- Upgrade: Core setup has completed!

Very nice to have System Center ConfigMgr 2012 R2 installed now! Expect more blogposts to come about R2 later this month.