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!

MDT 2012 Beta 2 integration in ConfigMgr 2012 RC

On 10 november 2011 the Beta 2 of Microsoft Deployment Toolkit (MDT) 2012 is released. MDT 2012 can be used as a single OS deployment solution, but can also be used for ConfigMgr 2012 RC integration. In this blog I will describe the installation, integration and new functionality.

What's new in MDT 2012 Beta 2:
MDT 2012 Beta 2 offers new User-Driven Installation components and extensibility for Configuration Manager 2007 and Configuration Manager 2012 as well as integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for Lite Touch Installation remote control and diagnostics.

Key benefits include:

• Full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment.
• Improved Lite Touch user experience and functionality.
• A smooth and simple upgrade process for all existing MDT users.

First download Microsoft Deployment Toolkit 2012 Beta 2 on Microsoft Connect: https://connect.microsoft.com/site14/Downloads/DownloadDetails.aspx?DownloadID=8689

Make sure ConfigMgr 2012 RC is installed for this integration. This is decribed here: Installing the ConfigMgr 2012 Release Candidate (RC)

Then install MDT 2012 Beta 2 with the default features.

After installation start "Configure ConfigMgr Integration".

The next screen will be displayed then:

All needed values are filled in by default, so move on. When installation is all fine "Operation completed successfully" is displayed.

Start the ConfigMgr 2012 RC console for new MDT features now.

Beneath Software Library > Operating Systems > Task Sequences, the following option is added:

Choose "Create MDT Task Sequence" for a new task sequence with MDT functionality.

For people who used MDT 2010 integration in ConfigMgr 2007, this screen looks very familiar.

It is also possible to select MDT features in existing task sequence. Just edit them, and choose Add > MDT

Have a look at my older blogpost for more explanation of all choices: MDT integration in ConfigMgr 2007

Beneath Software Library > Operating Systems > Boot Images, the following option is added:

Choose "Create Boot Image using MDT" for a new boot image with MDT functionality.

At last you can use the build-in scripts that's included with MDT, for using in ConfigMgr 2012 Task sequences. With MDT integration in ConfigMgr 2012 you have the best of both worlds. And with new functionality in MDT 2012 here is even more available! (User Driven Installation)

VMware vCenter Protect Update Catalog (Patch Management)

A few months ago I posted a blog about "System Center Updates Publisher (SCUP) 2011 integration in ConfigMgr". This can be found here: Blogpost: SCUP 2011 

With SCUP 2011 you can create and install update packages that's not in WSUS by default. This time I have an interesting expansion on SCUP 2011. It's called "VMware vCenter Protect Update Catalog" (formerly known as Shavlik SCUPdates).

"VMware vCenter Protect Update Catalog" is a data catalog for deploying 3rd party, non-Microsoft updates with Microsoft's System Center Configuration Manager (ConfigMgr). Our data catalog extends ConfigMgr to cover updates for these applications, which are not covered natively in ConfigMgr. Updates for the most attacked applications such as Adobe Reader and Acrobat are made available in these files. The files also include detection and deployment data for additional Microsoft legacy applications.

Supported Third-Party Applications: 

• Adobe Acrobat
• Adobe Flash Player
• Adobe Reader
• Adobe Shockwave
• Apple iTunes
• Apple QuickTime
• Apple Safari
• Apple Application Support
• Citrix Presentation Server for Windows Server 2003
• Citrix XenApp for Windows Server 2008 x64, x86
• Java Runtime Environment
• Mozilla Firefox
• Mozilla SeaMonkey
• Mozilla Thunderbird
• Opera
• RealNetworks RealPlayer
• Skype
• And many more

More information, trial software and a datasheet can be found here:
http://www.vmware.com/products/datacenter-virtualization/vcenter-protect-update-catalog/overview.html

Nice to see that SCUP functionality will be more interesting now!

Microsoft Management Summit 2012 Registration Open

Today I received the following message:

Microsoft Management Summit 2012 Registration Open

http://www.mms-2012.com/

Innovation. Expertise. Community.

At the 2012 Microsoft Management Summit (MMS) the brightest and most skilled IT Professionals from around the world meet to increase their technical expertise through deep hands-on technical training, sharing of best practices, and interaction with innovators and pioneers in desktop and device management, datacenter and cloud technologies.

We hope you will join us for this popular event designed to stimulate new thinking and forge lasting relationships among a remarkable group of IT professionals and industry leaders.

Be the First to Try New Technology

At MMS you will be the first to learn about how Microsoft management technologies enable a new breed of datacenter through private cloud and public cloud solutions, and deliver a more flexible and productive desktop infrastructure. You’ll also gain free access to valuable trial software and be able to visit with over 50 technology companies who will be exhibiting their latest innovations and technology solutions.

Five Days of Intense Learning & Networking

MMS offers a jam packed schedule of learning opportunities that will help you accelerate your career and solve today’s most challenging technical problems while preparing you for tomorrow’s innovation.

Learn about a variety of technologies by attending sessions through either labs or self-paced labs, as well as Microsoft Certification Exam and tests when you’re ready to take the next step.

Bring your questions, your experiences and your curiosity to structured and unstructured networking events that will provide the opportunity to meet and discuss topics of common interest peer-to-peer or with Microsoft and industry experts.

Register now: http://www.mms-2012.com/registration
April 16-20 @ The Venetian, Las Vegas, Nevada

Installing the ConfigMgr 2012 Release Candidate (RC)

On 27 october 2011 the Release Candidate (RC) of ConfigMgr 2012 is released. Because I'm doing ConfigMgr implementations most of times, I want to know which changes are made during installation. In this blog the setup of this new release is viewed, to see if there are any differences between previous releases. This installation is done on a Windows Server 2008 R2 Enterprise x64 server.

Have a look on Microsoft TechNet for download information: Download Microsoft System Center 2012 Pre-Release Products

Nice to see that ConfigMgr 2012 is now combined with Endpoint Protection 2012, which is the successor of Forefront Endpoint Protection 2010.

Unpack the file, and start Splash.hta for starting the setup. The following screen will be seen then, which has many new options in it:

When choosing INSTALL a message is displayed that DotNet Framework 3.5 SP1 and 4.0 are needed for starting the installation. So let's see first what's needed on the server for having a successful installation:

• DotNet Framework 3.5 SP1 and 4.0 (with default IIS Role Services)
• Remote Differential Compression (RDC)
• Background Intelligence Transfer Service (BITS)
• Windows Server Updates Servies (WSUS) > (optional)
• IIS Role Services > IIS 6 WMI Compatibility

While ConfigMgr 2012 Beta 2 must be installed on SQL Server 2008 with SP1 and CU10 (because SP2 and R2 are not supported), they can be used for installation now! For SQL Server 2008 SP2 with CU6 is needed or SQL Server 2008 R2 SP1 with CU3 is needed.

For Supported Configurations information, visit http://technet.microsoft.com/en-us/library/gg682077.aspx

Then the installation begins..

• Available Setup Options (Primary Site Server, Central Administration Site, Recover a Site Server)
• Microsoft Software License Terms
• Updated Prerequisite Components (15 items till now)
• Server Language Selection (English by default and 5 other languages) which is new in RC
• Client Language Selection (English by default and 21 other languages) which is also new in RC
• Site and Installation Settings (Site Code, Site Name, Console)
• Primary Site Installation (install a standalone site, or join an existing hierarchy)
• Database Information (Server and Database name, Instance name)
• SMS Provider Settings (cannot be installed on a clustered SQL server)
• Client Computer Communication Settings (Native or Mixed mode)
• Site System Roles (Choose HTTP or HTTPS for MP or DP, this can be choosen per rol)
• Customer Experience Improvement Program Configuration
• Setting Summary
• Prerequisite Check
• Install.. (this takes a while..) 

After that ConfigMgr 2012 RC is installed! Not that hard I think? Just 12 minutes has been used to install ConfigMgr and database.

Nice to see that Endpoint Protection 2012 is immediately available in the ConfigMgr console now. This with Antimalware and Windows Firewall policies by default.

Next blog will zoom deeper in new features of this ConfigMgr release! I'm very excited again about this new ConfigMgr release! Hope you are too!

Disable the GUI in Windows Server 8 with PowerShell

Last month I installed Windows Server Developer Preview (Windows Server 8). This can be found here: Windows Server 8 installed

There is the choice between installing the Full Installation, Server Core or Features on Demand edition. By default when doing a Full Installation the GUI is installed. In this blogpost I wil explain how to remove the GUI with usage of PowerShell.

This is the default screen after doing a Full Installation

Start Windows PowerShell with the default button available

In PowerShell the following commands are needed to remove the GUI:

• Import-Module ServerManager
• Get-WindowsFeature
• Remove-WindowsFeature Server-Gui-Shell
• Shutdown /r /t 5

After reboot the default screen is changed, no background anymore..

When logon, Server Manager and a command window is started

In PowerShell it's possible to enable or disable Windows features again

Open the command window for that and use the following commands:

• PowerShell
• Import-Module ServerManager
• Get-WindowsFeature
• Add-WindowsFeature <Name> (or)
  Remove-WindowsFeature <Name>

The following command are needed to install the GUI again:

• Add-WindowsFeature Server-Gui-Shell
• Shutdown /r /t 5

If needed, Windows PowerShell Getting Started Guide:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa973757(v=vs.85).aspx

Thanks to @RandolphWinjaja for PowerShell support.

Deploy Office 2010 with the Office Customization Tool (OCT)

Office 2010 will be installed with Setup.exe by default. It's however possible to use the Office Customization Tool (OCT) to decide which functionality must be used during install. With the created MSP file afterwards it's possible to do a unattend install with the usage of ConfigMgr. How to do that is explained in this blogpost.

First create a source location for the Office 2010 files. Run the Setup.exe with the /Admin parameter then. Choose to create a new Setup customization file.

There is the choice to choose between "Office Open XML formats" or "OpenDocument formats". In my case I choose to keep the current settings.

There are a lot of settings which can be configured in the Office Customization Tool. The most used are "Installation location and organization name" (and a few other settings).

Then select (in my case) "Licensing and user interface". I'm using a KMS client key here. For unattend and silent install use [Display level: None] and Suppress modal. Uncheck "Completion notice" here.

There is the choice to remove older Office versions before installing Office 2010.

Select which programs must be installed during Office 2010 setup. That's all for now for having a unattend Office 2010 install.

Choose "Save as" for creating a MSP file. This MSP must be placed in the Office 2010 source location then. Choose the Updates folder for that. All MSP files placed in the Updates folder will be automatically installed/used during install.

Then create a new package in ConfigMgr, with a Setup.exe command line. There are no additional installation switches needed. It's however possible to use an config.xml file for additional configuration. More about that on this TechNet post: http://technet.microsoft.com/en-us/library/cc179195.aspx

Hope things are clear now for Office 2010 deployment.

Create new Windows collections based on Query rules

Collections in ConfigMgr can be used for dynamic view. This will happen when a Query rule is used, based on Operating Systems or Active Directory containers (for example). There are a few blogs which describes this functionality already:

How to create a query based on Direct membership is described here:

• How to create or change new Windows collections in ConfigMgr

How to configure ConfigMgr collections to Active Directory containers is described here:

• Creating dynamic collections in ConfigMgr
• Configure dynamic collections in ConfigMgr
• Query ConfigMgr collections with Active Directory

In this blog I will describe how to create a new collection with Query rule.

First create a new collection in ConfigMgr and choose Membership rules based on Query rule. Click the [yellow database icon] and choose the query explained below. Choose "Dynamically add new resources" when using ConfigMgr R3 to automatically add new devices.

In this case I'm using a Resource class based on System Resource and  "Edit Query Statement" for creating a new Query rule.

Select the Criteria tab and the [yellow star icon] for that. Click "Select" afterwards.

In this case I'm using a Attribute class based on System Resource and a  Attribute based on "Operating System Name and Version".

When choose OK in the screen before (Select Attribute) the above screen will be displayed. Choose [Operator: Is Like] and Value based on Operating System variable here.

When choose OK in the screen before (Criterion Properties) the above screen will be displayed. Click OK afterwards.

The new collection with Query rule is ready now. All Windows 7 systems (in my case) will be automatically added in this new collection.

For new Windows releases use the following queries:
 

• Windows Vista: Value = %Workstation 6.0%
• Windows 7: Value = %Workstation 6.1%
• Windows 8: Value = %Workstation 6.2%
• Windows Server 2008: Value = %Server 6.0%
• Windows Server 2008 R2: Value = %Server 6.1%
• Windows Server 8: Value = %Server 6.2%

That way it's possible to create new collections with support on new Operating Systems. I will add support for new Operating Systems later when available.