Search This Blog

Saturday, June 28, 2014

Identify Whether SCCM 2012 R2 CU2 has been installed

Cumulative Update 2 for System Center Configuration Manager 2012 R2 has been released http://support.microsoft.com/kb/2970177

image

So once again it’s time to take a closer look at the version changes, this time for CU2.

After upgrading to System Center Configuration Manager 2012 R2 CU2, you will be able to identify the update as shown here.

First let us take a look at the console, after the update the console reports version 5.0.7958.1303

image

The console reported version 5.0.7958.1203 before updating which is 2012 R2 CU1.

image

The Console update is also listed in Control Panel as an Installed Update.

image

The site will still report version 5.00.7958.1000 after the update.

image

In order to check if the update has been applied we must look in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\CULevel

CULevel reports 2 after CU2 has been applied.

image

Before updating CULevel reported 1 because Cumulative Update 1 was installed.

image

This update is also visible under Installed Updates in Control Panel.

image

The client will report 5.00.7958.1303 after the client has been updated.

image

With these components updated:

image

Before updating the client reported 5.00.7958.1203 for 2012 R2 CU1 client.

image

System Center 2012 R2 Cumulative Update 2 also includes quite a lot of changes to PowerShell support for Config Manager http://support.microsoft.com/kb/2962855

Tuesday, June 24, 2014

0x8007010B as result of a scheduled task

when running a scheduled task you might get the error 0x8007010B

image

This error simply means that the  “Start In” folder is incorrect.

Change the incorrect folder in start in:

 

Please note that quotation marks are NOT valid characters, they are valid in the “Program/script” field.

image

And the result should then be better the next time you try:

image

Thursday, June 19, 2014

ADMT with support for Windows 2012 R2

Looks like we now have a updated version of ADMT with support for Windows 2012 R2, the version number has not changed.

At the same time there is a new version of the Password Export Server.

At this point in time I have only been able to find the updated version on Microsoft Connect.

Jump to the address https://connect.microsoft.com/directory/non-feedback sign with Microsoft and join Program Windows Server Active Directory Migration Tool (ADMT) found as shown here under Product

Azure Active Directory Customer Connection:

image

Download links when connected:

image

The documentation has also been updated:

http://www.microsoft.com/en-us/download/details.aspx?id=19188

This guide assists Active Directory administrators in performing domain migration through the use of the Active Directory Migration Tool version 3.2 (ADMT v3.2). ADMT v3.2 has recently been updated and re-released. The version remains v3.2 because it’s functionally the same as its predecessor (that is, there are no new features). This final release includes various bug fixes and can be used with all supported Windows operating systems and versions of Windows Server Active Directory.

 

image

image

See also http://technet.microsoft.com/en-us/library/cc974332(v=ws.10).aspx

Wednesday, June 18, 2014

Start control Panel Items even though it has been restricted

I often find my self working on a computer where the control panel has been restricted so that only selected item are shown (hidden).

image

Some of the missing items can still be started and also as an other user if necessary.

image

Item

Command

Action Center

wscui.cpl

Date and Time

timedate.cpl

Configuration Manager

%WINDIR%\CCM\SMSCFGRC.cpl

Device Manager

devmgmt.msc

Flash Player

FlashPlayerCplApp.cpl
(c:\Windows\syswow64\FlashPlayerCplApp.cpl)

Internet options

inetcpl.cpl

Java (Almost Smile)

Javaws –viewer
(c:\Windows\syswow64\Javaws –viewer)

Mail

C:\Program Files (x86)\Microsoft Office\Office15\MLCFG32.CPL

Mouse

main.cpl

Network Connections
(not Network and Sharing Center)

ncpa.cpl

Power options

powercfg.cpl

Region

intl.cpl

 

Sound

mmsys.cpl

Example of command:

image

The GPO settings in play here are:

User Configuration\Policies\Administrative Templates\Control Panel\Show only specified Control Panel items

 image

There are of course more command line options but they do not all work when control panel has been restricted. Let me know if you has knowledge of more commands that works in this scenario.

 

Tuesday, June 10, 2014

SCCM 2012 R2 TESTDBUPGRADE

Before upgrading SCCM 2012 to for example 2012 R2 we should test the upgrade on a copy of the database.

http://technet.microsoft.com/en-us/library/8b6ff5c8-3c84-49fb-8bc7-930bed865de5#BKMK_TestSiteDBUpgrade

The documentation states: Make a copy of the site database, and then restore that copy to an instance of SQL Server that uses the same edition as your site database and that does not host a Configuration Manager site. For example, if the site database runs on an instance of the Enterprise edition of SQL Server, make sure you restore the database to an instance of SQL Server that also runs the Enterprise edition of SQL Server.

If the SQL server is running on a virtual machine then it might for some be nice to just test it on a clone of the production server without network connectivity.

If you try it you will see this error: SQL instance hosting an active site Database – Cannot run TESTDBUPGRADE on a SQL Instance which host an active site Database. And Begin TestDBUpgrade is unavailable (grayed out).

image

If you delete the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS

image

After deleting the registry key you will be allowed to run TestDBUpgrade.

image

image

Monday, June 2, 2014

Get-WmiObject : Retrieving the COM class factory for component with CLSID {xxx} failed due to the following error: 80070005.

I have been writing about this before:

http://larslohmann.blogspot.dk/2013/05/cscript-error-can-find-script-engine.html

Apparently not only vbscript is affected by this but also PowerShell.

Get-WmiObject : Retrieving the COM class factory for component with CLSID {xxx} failed due to the following error: 80070005.

The script works outside the task sequence also with alternate credentials and task sequence is not in WinPE phase.

image


When trying to connect to the SCCM server (WMI) from a task sequence step with alternate credentials the problem shows up again.


Since last time I have also seen the problem with dotNet 1.1 is installed.


The workaround is the same as in the original post, and with the workaround implemented  the script works as expected, Powershell code shown here with workaround marked.

image

 

image