System Center 2012 Operations Manager – Setup – Database and WMI provider

I was trying to install SCOM 2012 in my lab environment but at the database wizard in the setup I getting an error after checking the SQL server name and instance.

The error was that I was using an unsupported version of SQL Server or WMI provider was not working. That’s was very strange, because I’m using SQL Server 2008 R2 SP1 with CU6. This Service Pack and CU6 is recommended for SCOM 2012 (SP1 beta).

I got this error in the log file. This log file is located at C:\Users\%username%\Appdata\Local\SCOM\Logs\OpsMgrWizard.log.

OK, this is odd. I’m using SQL Server 2008 R2 with Service Pack 1 and CU6 and this version is supported by SCOM. This must be a WMI error then! After researching on the Internet I have found this tool to solve the problem

Run this tool for SQL server. Command is: mofcomp.exe “C:\program files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof”

You will get this message. After this message you are able to continue the setup. =D

System Center 2012 Configuration Manager – Service Pack 1 (beta) Task Sequence BUG

Update 14-11-2013: This is not a bug. Read this onhttp://technet.microsoft.com/en-us/library/jj591552.aspx

The build and capture task sequence was updated to apply an operating system image instead of running Setup.exe for installation. You can still run Setup.exe for Windows 8 deployments by editing the task sequence in the task sequence editor. 

———————————————————————-

The problem is: if you add the source files from a Windows 7 setup DVD into SCCM you can’t use them because a bug in the wizard. If you make a Build and Capture Task sequence and browse to the Operating System installer package, there is no package.

In the screenshot you will see a folder called Root. This folder Root is the root of operating System Images. See for your self. I have a Windows 7 folder beneath the Root folder in Operating System installers. The Operting System Images is empty, so also no folders.

This is the view if I want to add the installer in the task seqeunce.

I don’t see the Windows 7 folder? Strange, but this is the “root” of Operating System Images.

Workaround:

You have to add the install.wim file from the source files directory of the Windows 7 setup DVD (folder). Follow the wizard to add the image.

After the wizard, go to Task sequence to make a Build and Capture Task.

Select Build and Capture. Select the added image and finish the wizard. Don’t use Join a domain, because we are using this task seqeunce to build a new image.

Edit the created Task Sequence. Highlight Apply Operating System.See right for the radio button Apply Operating System from an Original installation source. Browse to the installer (now you will see the installer package).

After that click on Apply and close the screen.

It’s now ready for build and capture.

Windows Intune v3 – Mobile Device and deploying Apps

Ok, it’s a long time ago that I was working with Windows Intune. Last week I was testing the Appstore in Intune for mobile devices.

The question was; must the mobile device has a sync connection with Exchange to deploy a App via Intune? According to the Intune Help and some blogs the mobile device must has a sync connection with Exchange otherwise it’s not possible to deploy Apps.

That’s is not true. Without a connection to Exchange you could deploy Apps from Intune. Exchange is only necessary to monitoring the device. Also to use a corporate policy for wiping or secure the mobile device.

Without a connection with Exchange you could go to the https://m.manage.microsoft.com. Log in with your Office365 or Corporate Active Directory credentials and choose your app. Install it and you’re done. The permission for deploying the app is only to users.