Today the Next Release of Windows Intune is announced. The Next Release of Windows Intune is adding new client management capabilities as it relates to System Center 2012 Configuration Manager (ConfigMgr) Service Pack 1 (SP1) Beta.
Microsoft offers two separate endpoint management solutions – System Center 2012 Configuration Manager (ConfigMgr) for on-premises management, and Windows Intune for management through the cloud. With ConfigMgr 2012 SP1 and the next version of Windows Intune, Microsoft is taking the first step in delivering interoperability between these products through Configuration Manager’s administration console.
This will enable customers to add mobile devices managed through the cloud with Windows Intune into their ConfigMgr 2012 SP1 console and manage all the devices through one tool. While you can continue to use Windows Intune as a "fully in the cloud" management solution for PC and mobile device management, the interoperability of Microsoft's on-premises and cloud services is a big step forward for organizations that want to manage all of their devices from one place.
To evaluate the current release of Windows Intune, you can sign up for a free 30-day trial of Windows Intune at the Microsoft website.
Brad Anderson mentioned during MMS 2012 in Las Vegas already: Regarding Windows Intune and ConfigMgr: "as we go forward we are going to bring these two closer together".
Great to see that ConfigMgr 2012 and Windows Intune now works together to manage both on-premises and through the cloud! Look for availability of ConfigMgr 2012 SP1 and the next release of Windows Intune in early 2013.
More information about Windows Intune can be found HERE.
Monday, September 10, 2012
System Center 2012 SP1 (Beta) available now!
Today the System Center 2012 Service Pack 1 Beta has become available. Service Pack 1 (SP1) will bring many important improvements to all System Center components. Let's have a look at the new Configuration Manager (ConfigMgr) 2012 features.
One of the most significant changes is support for Windows 8. Configuration Manager SP1 supports Windows 8 in the following ways:
Other significant changes include the following:
Great to see that Windows Server 2012, SQL Server 2012 and Windows 8 are all supported now. Also good to see that significant changes has been added to this already great product. There's still more to come in ConfigMgr with new Service Packs and Releases!
With SP1, the capabilities of ConfigMgr 2012 will be extended to manage Windows Embedded thin clients, Point-of-Sale (POS) terminals, digital signage, kiosks, and Thin PC's. This functionality means additional devices can be managed by ConfigMgr 2012 SP1 without requiring any additional software. Isn't that great!?
More information can be found HERE. The Beta is now available for download on the Microsoft Download Center website.
One of the most significant changes is support for Windows 8. Configuration Manager SP1 supports Windows 8 in the following ways:
- You can install the Configuration Manager client on Windows 8 computers and deploy Windows 8 to new computers or to upgrade previous client operating versions. Configuration Manager also supports Windows To Go.
- Configuration Manager supports Windows 8 features, such as metered Internet connections and Always On Always Connected.
- You can configure user data and profiles configuration items for folder redirection, offline files, and roaming profiles.
- You can configure new deployment types for Windows 8 applications, which support standalone applications (.appx files) and links to the Windows Store.
Other significant changes include the following:
- Support for Windows Server 2012 and SQL Server 2012.
- Clients are now supported on Mac computers, and on Linux and UNIX servers.
- Windows PowerShell cmdlets are available to automate Configuration Manager operations by using Windows PowerShell scripts.
- Support for cloud services, including a new distribution point for Windows Azure.
- More flexible hierarchy management with support to expand a stand-alone primary site into a hierarchy that includes a new central administration site, and the migration of a Configuration Manager SP1 hierarchy to another Configuration Manager SP1 hierarchy.
- Support for multiple software update points for a site to provide automatic redundancy for clients in the same way as you can configure multiple management points.
- Client notification to initiate some client operations from the Configuration Manager console, which include downloading computer policy and initiating a malware scan to be performed as soon as possible, instead of during the normal client policy polling interval.
- Support for virtual environments that allow multiple virtual applications to share file system and registry information instead of running in an isolated space.
- Email alert subscriptions are now supported for all features, not just Endpoint Protection.
Great to see that Windows Server 2012, SQL Server 2012 and Windows 8 are all supported now. Also good to see that significant changes has been added to this already great product. There's still more to come in ConfigMgr with new Service Packs and Releases!
With SP1, the capabilities of ConfigMgr 2012 will be extended to manage Windows Embedded thin clients, Point-of-Sale (POS) terminals, digital signage, kiosks, and Thin PC's. This functionality means additional devices can be managed by ConfigMgr 2012 SP1 without requiring any additional software. Isn't that great!?
More information can be found HERE. The Beta is now available for download on the Microsoft Download Center website.
Friday, September 7, 2012
Overview of new Microsoft 2012 exams
Today I passed the System Center 2012 Configuration Manager (ConfigMgr) exam. ConfigMgr 2012 is the only System Center product with a dedicated exam. The other System Center products are bundled in a Microsoft Private Cloud exam. Because of new Microsoft System Center 2012 exams, Windows Server 2012 exams, and Windows 8 exams, I place a complete overview in this blogpost. Here we go!
MCTS: System Center 2012
70-243 Administering and Deploying System Center 2012 Configuration Manager
As mentioned earlier this is just for ConfigMgr 2012. The other System Center 2012 products are bundled in the Microsoft Private Cloud exams.
MCSE: Microsoft Private Cloud
70-246 Monitoring and Operating a Private Cloud with System Center 2012
70-247 Configuring and Deploying a Private Cloud with System Center 2012
All System Center 2012 products (except ConfigMgr 2012) are bundled in these exams. More information about both exams HERE
More information: Microsoft Learning
MCSA: Windows Server 2012
70-410 Installing and Configuring Windows Server 2012
70-411 Administering Windows Server 2012
70-412 Configuring Advanced Windows Server 2012 Services
The MCSA: Windows Server 2012 certification shows that you have the primary set of Windows Server skills that are relevant across multiple solution areas in a business environment.
More information: Microsoft Learning
MCSE: Server Infrastructure
70-413 Designing and Implementing a Server Infrastructure
70-414 Implementing an Advanced Server Infrastructure
The MCSE: Server Infrastructure certification validates your ability to build comprehensive server infrastructure solutions.
More information: Microsoft Learning
MCSE: Desktop Infrastructure
70-415 Implementing a Desktop Infrastucture
70-416 Implementing Desktop Application Environments
The MCSE: Desktop Infrastructure certification validates your skills in desktop virtualization, remote desktop services and application virtualization.
70-417 Upgrading Your Skills to MCSA Windows Server 2012
If you have an MCSA: Windows Server 2008 certification, you may take Exam 417 to upgrade to the MCSA: Windows Server 2012.
More information: Microsoft Learning
MCSA: Windows 8
70-687 Configuring Windows 8
At the moment this is the only Windows 8 exam available.
70-688 Managing and Maintaining Windows 8
Update 18-1-2013: A new Windows 8 exam is available now!
70-689 Upgrading Your Skills to MCSA Windows 8
The MCSA: Windows 7 certification allows you to upgrade to the MCSA: Windows 8 certification, by taking a single upgrade exam.
Update 18-1-2013: The Windows 8 upgrade exam is available now!
That's it for now! I think there will be more exams to come about deployment with MDT 2012. This in combination with Windows 8 and Office 2013. With these exams there's lot to do next months! :)
MCTS: System Center 2012
70-243 Administering and Deploying System Center 2012 Configuration Manager
As mentioned earlier this is just for ConfigMgr 2012. The other System Center 2012 products are bundled in the Microsoft Private Cloud exams.
MCSE: Microsoft Private Cloud
70-246 Monitoring and Operating a Private Cloud with System Center 2012
70-247 Configuring and Deploying a Private Cloud with System Center 2012
All System Center 2012 products (except ConfigMgr 2012) are bundled in these exams. More information about both exams HERE
More information: Microsoft Learning
MCSA: Windows Server 2012
70-410 Installing and Configuring Windows Server 2012
70-411 Administering Windows Server 2012
70-412 Configuring Advanced Windows Server 2012 Services
The MCSA: Windows Server 2012 certification shows that you have the primary set of Windows Server skills that are relevant across multiple solution areas in a business environment.
More information: Microsoft Learning
MCSE: Server Infrastructure
70-413 Designing and Implementing a Server Infrastructure
70-414 Implementing an Advanced Server Infrastructure
The MCSE: Server Infrastructure certification validates your ability to build comprehensive server infrastructure solutions.
More information: Microsoft Learning
MCSE: Desktop Infrastructure
70-415 Implementing a Desktop Infrastucture
70-416 Implementing Desktop Application Environments
The MCSE: Desktop Infrastructure certification validates your skills in desktop virtualization, remote desktop services and application virtualization.
70-417 Upgrading Your Skills to MCSA Windows Server 2012
If you have an MCSA: Windows Server 2008 certification, you may take Exam 417 to upgrade to the MCSA: Windows Server 2012.
More information: Microsoft Learning
MCSA: Windows 8
70-687 Configuring Windows 8
At the moment this is the only Windows 8 exam available.
70-688 Managing and Maintaining Windows 8
Update 18-1-2013: A new Windows 8 exam is available now!
70-689 Upgrading Your Skills to MCSA Windows 8
The MCSA: Windows 7 certification allows you to upgrade to the MCSA: Windows 8 certification, by taking a single upgrade exam.
Update 18-1-2013: The Windows 8 upgrade exam is available now!
That's it for now! I think there will be more exams to come about deployment with MDT 2012. This in combination with Windows 8 and Office 2013. With these exams there's lot to do next months! :)
Tuesday, August 28, 2012
Error in ConfigMgr 2012 Self Service Application Catalog
Last days I installed a new ConfigMgr 2012 demo environment. Everything was working fine after installation on my server, but when accessing a client it went wrong. It wasn't possible to start the Self Service Application Catalog from within the Software Center.
The following error message was displayed here:
Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
Good news is there's an easy solution for this, which can be find on: Microsoft Support
To resolve this issue, run the following command line:
aspnet_regiis.exe /iru
The Aspnet_regiis.exe file can be found in one of the following locations:
%windir%\Microsoft.NET\Framework\v4.0.30319 (x86 computer)
%windir%\Microsoft.NET\Framework64\v4.0.30319 (x64 computer)
Cause of this has something to do with IIS and .NET installation order. After run this command the Self Service Application Catalog is working! Now it's possible to use this great new functionality.
The following error message was displayed here:
Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
Good news is there's an easy solution for this, which can be find on: Microsoft Support
To resolve this issue, run the following command line:
aspnet_regiis.exe /iru
The Aspnet_regiis.exe file can be found in one of the following locations:
%windir%\Microsoft.NET\Framework\v4.0.30319 (x86 computer)
%windir%\Microsoft.NET\Framework64\v4.0.30319 (x64 computer)
Cause of this has something to do with IIS and .NET installation order. After run this command the Self Service Application Catalog is working! Now it's possible to use this great new functionality.
Thursday, July 26, 2012
Vacation time!
Today my vacation is starting for the next coming weeks. During my vacation there will be no new blogposts as you can guess :) So enjoy yourself (I will do also) and expect a lot of new information and knowledge later this year. There will be lot to write and share about upcoming and already available Microsoft products.
Thanks for visiting my blog and see you later!
![]() |
| It's vacation time now! |
Labels:
Henk's blog,
Vacation,
Vacation time
Wednesday, July 25, 2012
Location of OpsMgr 2012 installation logfiles
During installation of OpsMgr 2012 bad things can happen (sometimes). Then it's very useful to know where the installation logfiles are placed, to know what's going on. Yesterday I wrote a blogpost already about a Microsoft update which brakes the OpsMgr installation. That blogpost can be found HERE. Today I explain where the installation logfiles resides.
Just open Windows Explorer for that and browse to the
%LocalAppData%\SCOM\Logs directory. Then the following logfiles can be seen:
Because of multiple installations yesterday, I also have multiple Setup(x).log files in my Logs directory.
On the SQL Server where I've installed the Reporting component the following logfiles can be seen:
Because of these logfiles you know where to look for troubleshooting. In my opinion these logfiles are viewed best with Trace32.exe which can be found HERE. Just install the "System Center Configuration Manager 2007 Toolkit V2" and open Trace32.exe for making it the default viewer for logfiles. Hope to help other people this way!
Just open Windows Explorer for that and browse to the
%LocalAppData%\SCOM\Logs directory. Then the following logfiles can be seen:
- FullPrereq.xml: Contains adjusted prerequisite check information
- OMConsole.log: Verbose logging of installation of the Operations console
- OMServer.log: Verbose logging of installation of the mgmt server role
- OpsMgrSetupWizard.log: Reports activity and progress of setup wizard
- SCOMPrereqCheck.log: XML output of the prerequisite checker
- Setup(x).log: Detailed logging of installation progress
- WebConsole.log: Verbose logging of installation of the Web console
Because of multiple installations yesterday, I also have multiple Setup(x).log files in my Logs directory.
On the SQL Server where I've installed the Reporting component the following logfiles can be seen:
- FullPrereq.xml: Contains adjusted prerequisite check information
- OMReporting.log: Logs progress of installation of the reporting feature
- OpsMgrSetupWizard.log: Reports activity and progress of setup wizard
- SCOMPrereqCheck.log: XML output of the prerequisite checker
- Setup(x).log: Detailed logging of installation progress
Because of these logfiles you know where to look for troubleshooting. In my opinion these logfiles are viewed best with Trace32.exe which can be found HERE. Just install the "System Center Configuration Manager 2007 Toolkit V2" and open Trace32.exe for making it the default viewer for logfiles. Hope to help other people this way!
Tuesday, July 24, 2012
Cannot start service OMSDK during OpsMgr 2012 setup
Today i ran into an error during a new (clean) OpsMgr 2012 installation. During the Prerequisite Check all went fine, but when installation started it went wrong. The errors started during the installation of new System Center services. There were errors like:
I've seen a lot off solutions for this errors, but for me this were the right ones:
They mentions:
The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000 or 7011. Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start.
We had the same problem both services failed to start after applying windows updates. It also caused a problem with de SQL reporting service(s) not automatically starting after a restart. The update that caused the problem for us was 'Update for Microsoft Windows (KB2677070)'. After removing that update both services started fine again and on servers with the SQL Reporting Service installed it would start automatically once again.
After this the Data Access service was started and OpsMgr 2012 installation was continuing! How it's possible that Microsoft releases a patch (which is still available) that brakes the OpsMgr 2012 setup? Hope they have a fix for this issue soon.
- Cannot start service OMSDK on computer
- The System Center Data Access service could not start
- A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access Service service to connect.
- No connection could be made because the target machine actively refused it <IP-address>:5724
I've seen a lot off solutions for this errors, but for me this were the right ones:
- A service does not start + reboot the server
- SDK and Configuration service timeouts + reboot the server
They mentions:
The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000 or 7011. Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start.
We had the same problem both services failed to start after applying windows updates. It also caused a problem with de SQL reporting service(s) not automatically starting after a restart. The update that caused the problem for us was 'Update for Microsoft Windows (KB2677070)'. After removing that update both services started fine again and on servers with the SQL Reporting Service installed it would start automatically once again.
After this the Data Access service was started and OpsMgr 2012 installation was continuing! How it's possible that Microsoft releases a patch (which is still available) that brakes the OpsMgr 2012 setup? Hope they have a fix for this issue soon.
Monday, July 23, 2012
How to Create a Windows To Go USB Drive
With Windows 8 coming within a few months it's good to have a look a new functionality. One way to install Windows 8 is on a VHD (Virtual Hard Disk). New in Windows 8 is the option to mount VHD files and boot from it! A guide to install Windows 8 on a VHD can be found HERE. Great that so many people viewed this blogpost to install it that way. In this blogpost I explain the new Windows To Go functionality.
Windows To Go is an enterprise feature of Windows 8 that enables users to boot Windows from a USB-connected external drive. Windows To Go drives can use the same image enterprises use for their desktops and laptops and can be managed the same way. Windows To Go is not intended to replace desktops, laptops or supplant other mobility offerings. Rather, it provides support for efficient use of resources for alternative workplace scenarios.
You need the following for installation:
That way you don't have to download a full copy of Windows Automated Installation Kit (AIK) for Windows 7 (1.7 GB) found HERE.
How to Create a Windows To Go USB Drive:
After the command has completed you are ready to use your new Windows To Go USB device. Now it's time to reboot your system and start from the USB device. There will be some final configuration during first start. During the session the USB device must be plugged in.
What a great year with many new Microsoft releases and functionality!
Windows To Go is an enterprise feature of Windows 8 that enables users to boot Windows from a USB-connected external drive. Windows To Go drives can use the same image enterprises use for their desktops and laptops and can be managed the same way. Windows To Go is not intended to replace desktops, laptops or supplant other mobility offerings. Rather, it provides support for efficient use of resources for alternative workplace scenarios.
You need the following for installation:
- 16 GB or larger USB 2.0 / 3.0 Drive
- Windows 8 Release Preview ISO (download HERE)
- ImageX.exe stand-alone straight from Microsoft (download HERE)
That way you don't have to download a full copy of Windows Automated Installation Kit (AIK) for Windows 7 (1.7 GB) found HERE.
- Quick Format the USB device with NTFS, and create a partition on it
- Extract or mount the Windows 8 ISO and copy the Install.wim file (Sources folder) to a folder where ImageX.exe is also placed
- Have a look at the drive letter which is used for the USB device and type the following command: ImageX.exe /apply Install.wim 1 F:\ (where F: is the drive letter of your USB device)
- The result (after some time) must be "Successfully applied image"
- Once this is done the boot record on the USB device must be changed with the following command: Bcdboot.exe F:\Windows /s F: /f ALL (where F: is the drive letter of your USB device)
- The result must be "Boot files successfully created" now
After the command has completed you are ready to use your new Windows To Go USB device. Now it's time to reboot your system and start from the USB device. There will be some final configuration during first start. During the session the USB device must be plugged in.
What a great year with many new Microsoft releases and functionality!
Labels:
BCDBOOT,
ImageX,
Release Preview,
Windows 8,
Windows To Go,
WindowsToGo
Friday, July 20, 2012
Installing Microsoft Office 2013 Customer Preview
Today I installed the new Microsoft Office 2013 Preview. Because the existing Office 2010 installation on my Windows 8 Release Preview device, I choose for a upgrade. The installation is done in a few minutes and a reboot is needed afterwards. Then the new functionality can be used. The following tiles are available after installation:
Just notice that Lync 2013 is installed by default now, no other installation is needed for that. Programs that are still exists after the upgrade are:
- SharePoint Workspace 2010
- Office Picture Manager
- Lync 2010
As far as I can see everything works fine after the upgrade. Nice to see that Microsoft Office 2013
will have support for Touch devices, SkyDrive, Yammer, Skype and Cloud services
now!
Tuesday, July 17, 2012
Microsoft Office 2013 Customer Preview has arrived
Yesterday a new Office has arrived. It's called Microsoft Office 2013.
Microsoft Corp. CEO Steve Ballmer unveiled the customer preview of the new Microsoft Office, available at office.com/preview.
The next release features an intuitive design that works beautifully with touch, stylus, mouse or keyboard across new Windows devices, including tablets. The new Office is social and unlocks modern scenarios in reading, note-taking, meetings and communications and will be delivered to subscribers through a cloud service that is always up to date.
The new, modern Office will deliver unparalleled productivity and flexibility for both consumers and business customers. It is a cloud service and will fully light-up when paired with Windows 8
Microsoft Corp. CEO Steve Ballmer unveiled the customer preview of the new Microsoft Office, available at office.com/preview.
The next release features an intuitive design that works beautifully with touch, stylus, mouse or keyboard across new Windows devices, including tablets. The new Office is social and unlocks modern scenarios in reading, note-taking, meetings and communications and will be delivered to subscribers through a cloud service that is always up to date.
The new, modern Office will deliver unparalleled productivity and flexibility for both consumers and business customers. It is a cloud service and will fully light-up when paired with Windows 8
While the full lineup of offerings and pricing plans will be announced in the fall, Ballmer discussed three new Office 365 subscription services. When available, each new subscription offer will include the new 2013 editions of the Office applications. In addition, subscribers will receive future rights to version upgrades as well as per-use rights across up to five PCs or Macs and mobile devices. More about new functionality HERE
MSDN members can download Office at CLICK
Office Language Packs and other downloads at CLICK
Nice to see that Microsoft Office 2013 will have support for Touch devices, SkyDrive, Yammer, Skype and Cloud services now!
Tuesday, July 10, 2012
Windows 8 and Windows Server 2012 available soon
Yesterday Microsoft revealed on the Worldwide Partner Conference in Toronto that Windows 8 will be Release to Manufacturing (RTM) in the first week on August, with a release in late October to retail stores.
Today Microsoft revealed that Windows Server 2012 will be RTM at the same time (August 2012), with a release in September already.
That way both Windows 8 and Windows Server 2012 will be RTM in August and available for download also. Just a few weeks later the products are final and ready on selling points.
Good news that Microsoft has so many new releases in one year!
Today Microsoft revealed that Windows Server 2012 will be RTM at the same time (August 2012), with a release in September already.
That way both Windows 8 and Windows Server 2012 will be RTM in August and available for download also. Just a few weeks later the products are final and ready on selling points.
Good news that Microsoft has so many new releases in one year!
Labels:
Release to Manufacturing,
RTM,
Windows 8,
Windows Server 2012
Friday, July 6, 2012
Upgrade OpsMgr 2012 from evaluation to retail version
Last days I installed a clean System Center Operations Manager (OpsMgr) 2012 server. After installation the following configuration task was seen in the OpsMgr console: Upgrade to full version
This because during installation there is no possibility to fill in a product key. That must be done after installation. Strange thing, because with System Center Configuration Manager (ConfigMgr) 2012 it can be filled in during installation. When you don't fill in the product key, an evaluation version (180 days) is used by default.
To upgrade OpsMgr 2012 from evaluation to Retail version use the following commands:
1) Start Operations Manager Shell (PowerShell)
2) Enter "Set-SCOMLicense –ProductID <product-key>"
3) Choose Yes or press enter for default
4) Reboot the OpsMgr server or restart the "System Center Data Access Service" (!)
After that start the OpsMgr 2012 console, choose Help > About, and you will see Version 7.0.8560.0 (Retail) now.
Labels:
Evaluation version,
OpsMgr 2012,
PowerShell,
Retail version,
SCOM 2012
Tuesday, July 3, 2012
System Center 2012 Service Pack 1 CTP2 announcement
A few weeks ago during TechEd 2012 NA the System Center 2012 Service Pack 1 CTP2 was announced. The Service Pack contains updates to System Center 2012 for compatibility with Windows Server 2012 Release
Candidate including support for Azure VM and capabilities for Hosted Service
Providers.
It is available for download here: System Center 2012 Service Pack 1 CTP2
This Community Technology Preview (CTP2) enables System Center customers to
jointly evaluate System Center 2012 and Windows Server 2012 Release Candidate.
CTP2 includes updates and enhancements to the following System Center 2012
components:
For ConfigMgr 2012 it includes also additional operating support to extend manageability to Mac OS X and Unix/Linux servers. Nice to see that ConfigMgr 2012 has cross platform support soon!
It is available for download here: System Center 2012 Service Pack 1 CTP2
- Virtual Machine Manager
- Improved Support for Network Virtualization
- Extend the VMM console with Add-ins
- Support for Windows Standards-Based Storage Management Service, thin provisioning of logical units and discovery of SAS storage
- Ability to convert VHD to VHDX, use VHDX as base Operating System image
- Configuration Manager
- Support for Windows 8
- Ability to deploy Windows 8 Apps
- Real-time administrative actions for Endpoint Protection related tasks
- Data Protection Manager
- Improved backup performance of Hyper-V over CSV 2.0
- Protection for Hyper-V over remote SMB share
- Protection for Windows Server 2012 de-duplicated volumes
- Uninterrupted protection for VM live migration
- App Controller
- Service Provider Foundation API to create and operate Virtual Machines
- Support for Azure VM; migrate VHDs from VMM to Windows Azure, manage from on-premise System Center
- Operations Manager
- Support for IIS 8
- Monitoring of WCF, MVC and .NET NT services
- Azure SDK support
- Orchestrator
- Support for Integration Packs, including 3rd party
- Manage VMM self-service User Roles
- Manage multiple VMM ‘stamps’ (scale units), aggregate results from multiple stamps
- Integration with App Controller to consume Hosted clouds
- Service Manager
- Apply price sheets to VMM clouds
- Create chargeback reports
- Pivot by cost center, VMM clouds, Pricesheets
- Server App-V
- Support for applications that create scheduled tasks during packaging
- Create virtual application packages from applications installed remotely on native server
For ConfigMgr 2012 it includes also additional operating support to extend manageability to Mac OS X and Unix/Linux servers. Nice to see that ConfigMgr 2012 has cross platform support soon!
Labels:
ConfigMgr 2012,
Configuration Manager,
CTP2,
SCCM 2012
Monday, July 2, 2012
System Center 2012 Unified Installer is working now
System Center 2012 Unified Installer is a utility designed to perform new, clean installations of System Center 2012 for testing and evaluation purposes only. With the Unified Installer it's possible to install all System Center products at 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.
Last week I started the installation again because of the new RTM release. Just prepare your install and target computer with local policies, as mentioned in the comments and on Microsoft TechNet:
Preparing an Installer Computer for System Center 2012
Preparing a Target Computer for System Center 2012
Also use the steps mentioned by ThomasH mentioned in my other blogpost: Using the System Center 2012 Unified Installer
Computer Config \ Administrative Templates \ System \ Credentials Delegation \ Allow Delegating Fresh Credentials
State = Enabled
Server = WSMAN/*
Computer Config \ Administrative Templates \ System \ Credentials Delegation \ Allow Delegating Fresh Credentials with NTLM only server Authentication
State = Enabled
Server = WSMAN/*
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Client \ Allow CredSSP authentication
State = Enabled
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Client \ Trusted Hosts
State = Enabled
TrustedHostList = *
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service \ Allow Automatic Configuration of listeners
State = Enabled
IPv4 filter = *
IPv6 filter = *
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service \ Allow CredSSP authentication
State = Enabled
In a command prompt, run:
gpupdate
Winrm quickconfig
Very handy in "Prerequisite Media Location" is the download link for every prerequisite!
When the error message "The WinRM settings are not configured correctly" is displayed, look at the log \Users\<user>\AppData\Local\Microsoft System Center 2012\Unified Installer\LOGS for more information!
During installation the following screens are displayed:
In this case I'm only installing Orchestrator (which is mandatory), Operations Manager and Configuration Manager 2012.
Conclusion: The System Center 2012 Unified Installer is an easy way to setup a demo environment quickly. It's working when you download all products and prerequisites and prepare all your servers! Too bad it's not possible to use a single SQL Server installation, it will be installed for all products selected. But it's for sure a handy solution!
Last week I started the installation again because of the new RTM release. Just prepare your install and target computer with local policies, as mentioned in the comments and on Microsoft TechNet:
Preparing an Installer Computer for System Center 2012
Preparing a Target Computer for System Center 2012
Also use the steps mentioned by ThomasH mentioned in my other blogpost: Using the System Center 2012 Unified Installer
Computer Config \ Administrative Templates \ System \ Credentials Delegation \ Allow Delegating Fresh Credentials
State = Enabled
Server = WSMAN/*
Computer Config \ Administrative Templates \ System \ Credentials Delegation \ Allow Delegating Fresh Credentials with NTLM only server Authentication
State = Enabled
Server = WSMAN/*
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Client \ Allow CredSSP authentication
State = Enabled
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Client \ Trusted Hosts
State = Enabled
TrustedHostList = *
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service \ Allow Automatic Configuration of listeners
State = Enabled
IPv4 filter = *
IPv6 filter = *
Computer Config \ Administrative Templates \ Windows Components \ Windows Remote Management (WinRM) \ WinRM Service \ Allow CredSSP authentication
State = Enabled
In a command prompt, run:
gpupdate
Winrm quickconfig
Very handy in "Prerequisite Media Location" is the download link for every prerequisite!
When the error message "The WinRM settings are not configured correctly" is displayed, look at the log \Users\<user>\AppData\Local\Microsoft System Center 2012\Unified Installer\LOGS for more information!
During installation the following screens are displayed:
In this case I'm only installing Orchestrator (which is mandatory), Operations Manager and Configuration Manager 2012.
Orchestrator will be installed first because of runbook functionality
All needed prerequisites will be installed first at the same time
All selected System Center products are successfully installed now!
After that a nice Deployment Summary Report is displayed.
Conclusion: The System Center 2012 Unified Installer is an easy way to setup a demo environment quickly. It's working when you download all products and prerequisites and prepare all your servers! Too bad it's not possible to use a single SQL Server installation, it will be installed for all products selected. But it's for sure a handy solution!
Friday, June 22, 2012
Windows 8 and Windows Server 2012 Beta Exams
This week I received a message from Microsoft that the first beta exams for the Windows 8 and Windows Server 2012 portfolios are available now! Both exams can be registered through the Prometric website. Just have a look at the new (public) beta exams:
Good luck with both exams!
- 71-410 Installing and Configuring Windows Server 2012
- Find details in the 70-410 preparation guide
- 71-687 Configuring Windows
- Find details in the 70-687 preparation guide
Good luck with both exams!
Labels:
71-410,
71-687,
Prometric,
Windows 8,
Windows Server 2012
Thursday, June 7, 2012
ConfigMgr 2012 Software Update classifications
When implementing ConfigMgr 2012 it's a good thing to use the product for patch management also. This because of better management above of default WSUS functionality. In ConfigMgr 2007 I preferred the ConfigMgr way already instead of WSUS. In the 2012 release patch management is even better, so there will be less discussion about the topic. Just use ConfigMgr 2012 for patch management!
When adding the Software Update point role, there must be some kind of configuration take place. This can be done on the role mentioned and on Site Components. On the Software Update point role a Proxy server can be configured. All other configuration must be done on Site Components. The following classifications are available here:
In ConfigMgr 2007 there was also a Driver classification. That one isn't available anymore in the 2012 release. That's because of the driver catalog in ConfigMgr: http://technet.microsoft.com/en-us/library/hh301101.aspx
Remember: Selecting above items doesn't download anything for you. It will only replicate WSUS catalog data, so you can see if updates are needed or not.
When adding the Software Update point role, there must be some kind of configuration take place. This can be done on the role mentioned and on Site Components. On the Software Update point role a Proxy server can be configured. All other configuration must be done on Site Components. The following classifications are available here:
- Critical Updates: Broadly released fixes for specific problems addressing critical, non-security related bugs.
- Definition Updates: Updates to virus or other definition files.
- Feature Packs: New feature releases, usually rolled into products at the next release.
- Security Updates: Broadly released fixes for specific products, addressing security issues.
- Service Packs: Cumulative sets of all hotfixes, security updates, critical updates, and updates created since the release of the product. Service packs might also contain a limited number of customer-requested design changes or features.
- Tools: Utilities or features that aid in accomplishing a task or set of tasks.
- Update Rollups: Cumulative sets of hotfixes, security updates, critical updates, and updates packaged together for easy deployment. A rollup generally targets a specific area, such as security, or a specific component, such as Internet Information Services (IIS).
- Updates: Broadly released fixes for specific problems addressing non-critical, non-security related bugs.
In ConfigMgr 2007 there was also a Driver classification. That one isn't available anymore in the 2012 release. That's because of the driver catalog in ConfigMgr: http://technet.microsoft.com/en-us/library/hh301101.aspx
Remember: Selecting above items doesn't download anything for you. It will only replicate WSUS catalog data, so you can see if updates are needed or not.
Friday, June 1, 2012
Virtual Machine Manager 2012 RC to RTM upgrade
Today I want to install the System Center 2012 suite again with RTM version. Before I started the Virtual Machine Manager (SCVMM) must be upgraded from the RC to RTM version. This because my RC installation is expired (180 days evaluation) and cannot be used anymore. The following error message is displayed:
A default upgrade from SCVMM RC to RTM is not possible because it's not supported. The following error message is displayed then:
Microsoft has a SCVMM upgrade tool available for doing this. It can be requested HERE Best thing is to open a support incident via the web for free usage. In my case the upgrade tool was available within one (1) hour!
Just follow the steps described in the e-mail message which is send by Microsoft. The most important ones are in this blog post also.
First make sure no open connections are available to SCVMM. Also have a look at which service account is used for the VMM service. Then click uninstall, choose remove features and select the necessary modules. In my case I selected VMM Management Server, VMM Console and VMM Self-Service Portal. On the Database options page make sure to choose Retain Data.
After uninstalling, which takes a few minutes, the database must be upgraded from RC to RTM version. This can be done with the UpgradeVMM2012RC.exe tool, send by Microsoft. With UpgradeVMM2012RC.exe /? you can see what different parameters you can use. The command I used here is showed in the picture. Good news: The upgrade successfully completed!
Now it's time to install SCVMM again. Just start the RTM setup and specify the VMM database retained from the RC installation. Also the Service account used for the VMM service must be filled in again. Select all the components to install the SCVMM RTM version.
When an error message is displayed that the upgrade cannot be done, make sure that all VMM RC components are uninstalled before. It's also possible that an error message is displayed that the VMM Library share already exists. Just remove the share before starting setup again.
After that the Setup completed successfully! Now it's time to look at new functionality and update the existing VMM Agents.
A default upgrade from SCVMM RC to RTM is not possible because it's not supported. The following error message is displayed then:
Microsoft has a SCVMM upgrade tool available for doing this. It can be requested HERE Best thing is to open a support incident via the web for free usage. In my case the upgrade tool was available within one (1) hour!
Just follow the steps described in the e-mail message which is send by Microsoft. The most important ones are in this blog post also.
First make sure no open connections are available to SCVMM. Also have a look at which service account is used for the VMM service. Then click uninstall, choose remove features and select the necessary modules. In my case I selected VMM Management Server, VMM Console and VMM Self-Service Portal. On the Database options page make sure to choose Retain Data.
After uninstalling, which takes a few minutes, the database must be upgraded from RC to RTM version. This can be done with the UpgradeVMM2012RC.exe tool, send by Microsoft. With UpgradeVMM2012RC.exe /? you can see what different parameters you can use. The command I used here is showed in the picture. Good news: The upgrade successfully completed!
Now it's time to install SCVMM again. Just start the RTM setup and specify the VMM database retained from the RC installation. Also the Service account used for the VMM service must be filled in again. Select all the components to install the SCVMM RTM version.
When an error message is displayed that the upgrade cannot be done, make sure that all VMM RC components are uninstalled before. It's also possible that an error message is displayed that the VMM Library share already exists. Just remove the share before starting setup again.
After that the Setup completed successfully! Now it's time to look at new functionality and update the existing VMM Agents.
Labels:
RC,
RTM,
SCVMM,
Upgrade Tool,
Virtual Machine Manager 2012,
VMM
Thursday, May 31, 2012
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)
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)
Labels:
Release Preview,
Windows 8,
Windows Server 2012
Wednesday, May 16, 2012
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.
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.
Labels:
80004005,
80070057,
ConfigMgr 2012,
Network Access Account,
SCCM 2012
Tuesday, May 8, 2012
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:
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!
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!
Labels:
Collation,
ConfigMgr 2012,
SCCM 2012,
SQL Server
Monday, May 7, 2012
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:
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:
After that it's possible to have a successful ConfigMgr 2012 installation. Just make sure above requirements are configured.
- 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.
Labels:
Collation,
ConfigMgr 2012,
SCCM 2012,
SQL Server
Thursday, April 26, 2012
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.
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:
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:
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)
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)
Labels:
Microsoft Management Summit,
MMS,
MMS 2012,
MMS2012
Subscribe to:
Posts (Atom)




























