Unexpected reboot upgrading ConfigMgr Admin Console

No Gravatar

Yesterday I upgraded my ConfigMgr 2012 R2 lab to SP1 and encountered a small bit of trouble.  During the SP installation the Admin Console failed to uninstall; during installation the MSI performed an unexpected reboot.

Scenario

  • The primary site server had recently been upgraded to CU5 for ConfigMgr 2012 R2 but had several reboots since.
  • As far as I can remember the Admin Console was not running when the service pack installation began, nor any time during the installation.
  • The Admin Console failed to uninstall during the service pack installation.
  • After the service pack installation, a manual reboot was performed.
  • The Admin Console was reinstalled via command line.  The MSI return code of 1641 was generated and MSI automatically rebooted the server.

Details

Below are some details captured from the installation logs.

in C:\ConfigMgrSetup.log

INFO: AdminConsole will be deinstalled first for upgrade – "E:\Program Files\Microsoft Configuration Manager\bin\I386\ConsoleSetup.exe"/uninstall /q.

ERROR: Configuration Manager console uninstallation failed. Check log file ConfigMgrAdminUISetup.log.

WARNING: Configuration Manager console installation failed. ConfigMgrAdminUI.log has further information.

in C:\ConfigMgrAdminUISetup.log

5/14/2015 2:46:55 PM   MSI: Another application has exclusive access to the file ‘E:\Program Files\Microsoft Configuration Manager\AdminConsole\AdminUILog\CMSitePSProvider.log’.  Please shut down all other applications, then click Retry.      

5/14/2015 2:46:55 PM   MSI: Action 14:46:55: Rollback. Rolling back action:

5/14/2015 2:46:55 PM   Installation failed with error code 1603

The server was manually restarted

The Admin Console installation was initiated via command line from an elevated PowerShell ISE session.

"E:\Program Files\Microsoft Configuration Manager\Tools\ConsoleSetup\ConsoleSetup.exe" /q TargetDir="E:\Program Files\Microsoft Configuration Manager\AdminConsole" EnableSQM=0 DefaultSiteServerName=LAB-CM.lab.local

In ConfigMgrAdminUISetup.log

5/14/2015 3:28:56 PM   MSI: You must restart your system for the configuration changes made to System Center Configuration Manager Console to take effect. Click Yes to restart now or No if you plan to manually restart later.    

5/14/2015 3:28:56 PM   Installation succeeded. Windows Installer has initiated a reboot.

*Notice that the time difference in the 2 log lines in <=1 second.  Also, no visible prompt was generated asking about a reboot.

In ConfigMgrAdminUISetupVerbose.log

MSI (s) (78:04) [15:28:56:261]: Windows Installer installed the product. Product Name: System Center Configuration Manager Console. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.

MSI (s) (78:04) [15:28:56:261]: Value of RebootAction property is

MSI (s) (78:04) [15:28:56:261]: Windows Installer requires a system restart. Product Name: System Center Configuration Manager Console. Product Version: 5.00.8239.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Type of System Restart: 1. Reason for Restart: 1.

MSI (s) (78:04) [15:28:56:261]: Closing MSIHANDLE (1) of type 790542 for thread 5124

MSI (s) (78:04) [15:28:56:261]: Deferring clean up of packages/files, if any exist

MSI (s) (78:04) [15:28:56:261]: MainEngineThread is returning 1641

MSI (s) (78:98) [15:28:56:261]: RESTART MANAGER: Session closed.

 

Hopefully no one else runs into this scenario.

May 15, 2015

Posted In: ConfigMgr 2012

Tags:

Windows 10 Technical Preview Build 9926 and ConfigMgr

No Gravatar

It’s a good day to not be assigned to a customer… Microsoft released Windows 10 Technical Preview Build  9926!

I took a moment to download all 4 ISO files (Professional and Enterprise, 32 and 64 bit), inventoried the ISOs to help keep track of them, and deployed one in my ConfigMgr 2012 R2 CU3 Hyper-V lab.  Here are some interesting first impressions.

 

ConfigMgr client install

CCMSetup.exe shows the computer is domain joined and X64.  Nothing unexpected there.  But notice the operating system “ ‘Microsoft Windows 10 Pro Technical Preview’ (10.0.9926). Service Pack (0.0). SuiteMask = 272. Product Type = 18.”

image

Interesting.  Let’s back up a minute and see what Windows says.

Windows version

Command Prompt shows “Microsoft Windows [Version 10.0.9926]”

About Windows (WinVer) shows “Version 10.0 (Build 9926)”

image

Let’s explore what WMI has to say about the OS

image

Manufacturer            : Microsoft Corporation
Caption                 : Microsoft Windows 10 Pro Technical Preview
Version                 : 10.0.9926
BuildNumber             : 9926
OperatingSystemSKU      : 48
OSArchitecture          : 64-bit
OSLanguage              : 1033
OSProductSuite          : 256
OSType                  : 18
ProductType             : 1
ServicePackMajorVersion : 0
ServicePackMinorVersion : 0
SuiteMask               : 272

Back to ConfigMgr

OK, CCMSetup completed successfully and everything looks good.

image

 

Now this is odd… ClientIDManagerStartup.log shows “OS Version: 6.2”.  I thought it was 10.0.9926.

image

Just to compare

  • Windows 10 Technical Preview build 9860 shows 6.2
  • Windows Server 2012 R2 shows 6.2
  • Windows 8.1 Update 2 shows 6.2
  • Windows 7 SP1 shows 6.1

At least there is some consistency, but where in the world is ConfigMgr pulling that from!

ConfigMgr Console

Let’s flip over to our ConfigMgr console.

Below is a side-by-side comparison of the 9860 build and the 9926 build from a device object property perspective.

Build 9860 shows the operating system as “Microsoft Windows NT Workstation 6.4”

Build 9926 shows the operating system as “Microsoft Windows NT Workstation 10.0”

image

And here is a side-by-side comparison of the operating system data from Hardware Inventory as shown in Resource Explorer.

Build 9860 shows a Caption of “Microsoft Windows Technical Preview” and a version of “6.4.9860”

Build 9926 shows a Caption of “Microsoft Windows 10 Pro Technical Preview” and a version of “10.0.9926”

image

Summary

With Windows 10 Technical Preview Build 9926, Microsoft has definitely changed directions with the version and left behind the 6.x series.

From a ConfigMgr perspective, the client is successfully installing, getting machine policies, running hardware and software inventory, running Software Update scans, and Compliance Setting scans.  Everything looks good… now for some OS Deployment.

January 23, 2015

Posted In: ConfigMgr 2012, Windows 10

SCCM Application Requirement of MSI ProductCode

No Gravatar

I had a situation recently where an application needed to be installed on all workstations (desktops and laptops) unless another application was installed.  Traditionally I would use collections to accomplish this.

  • create a collection “Deploy Mfg App vVersion – Exclusions” for the “exceptions / exclusions” and use a membership query of inventory data to populate the collection.
  • create a collection “Deploy Mfg App vVersion – Targets” and exclude the collection “Deploy Mfg App vVersion – Exclusions” as a membership rule
  • Ensure that the exclusion collection update schedule was about 5 minutes before the targets collection update cycle.
  • Deploy to the “targets” collection.

However, I thought of trying a different approach and using the real-time Requirements feature of the Application model.  Since this software was to be installed on any workstation unless a specific MSI application was already installed, I needed to create a custom requirement or Global Condition.

Global Condition MSI Product Code

Windows / Setting / WQL query / String / root\CIMv2 / Win32_Product / IdentifyingNumber

 

Now add the MSI Product Code as a requirement, set the Operator to “Not equal to” and enter the MSI Product Code.

App Requirement excluding MSI Product Code

Using a Simulated Deployment, the before and after results clearly indicate that before the Requirement was added the product “Lync 2013 Basic Client” was Applicable and afterwards is is NotApplicable.

AppIntentEval_MSI Product Code

Happy deploying!

August 14, 2014

Posted In: ConfigMgr 2012

SCEP 2012 client log files

No Gravatar

Looking for client log files I had to do a bunch of digging.  This is what I’ve concluded (for now).

C:\Windows\Temp\ (technically the System Temp folder)

  • MpCmdRun.log
  • MpSigStub.log

C:\ProgramData\Microsoft\Microsoft Security Client\Support (technically the %ProgramData%\Microsoft\Microsoft Security Client\Support folder)

  • EppSetup.log
  • EppSetup_#.log
  • MSSecurityClient_Setup_<version>_epp_install.log
  • MSSecurityClient_Setup_<version>_epp_uninstall.log
  • MSSecurityClient_Setup_<version>_eppManagement_install.log
  • MSSecurityClient_Setup_<version>_eppManagement_uninstall.log
  • MSSecurityClient_Setup_<version>_FEP_install.log

C:\Windows\CCM\logs (technically <SCCM Client location\logs folder> which can be discovered at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Client\Configuration\Client Properties\Local SMS Path)

  • EndpointProtectionAgent.log
  • UpdatesDeployment.log (for definition updates)
  • UpdatesHandler.log (for definition updates)
  • UpdatesStore.log (for definition updates)
  • UpdateStore.log (for definition updates)
  • WUAHandler.log (for definition updates)

C:\Windows (technically the %windir% folder)

  • WindowsUpdate.log (for definition updates)

The Technical Reference for Log Files in Configuration Manager lists these server side files:

  • EPCtrlMgr.log
  • EPMgr.log
  • EPSetup.log
  • NotiCtrl.log

This product has a few different names depending on the version and where you look in the application and logs.  Here are a few alternative names:

  • Microsoft System Center Endpoint Protection (the product GUI)
  • SCEP (just the acronym)
  • Microsoft Endpoint Protection (as seen in WSUS definitions)
  • Microsoft System Center Configuration Manager Endpoint Protection
  • Microsoft Configuration Manager Endpoint Protection (as seen in some product documentation)
  • Microsoft Security Client (as seen in the software’s folder structure)
  • Microsoft Antimalware Client (as seen in the software’s folder structure)
  • Microsoft Security Essentials
  • Microsoft Forefront Endpoint Protection 2010 Client (as seen in WSUS products…  technically this is the old version but it is still there)

Thanks to a few other bloggers for getting me started

July 11, 2014

Posted In: ConfigMgr 2012

ConfigMgr Admin Console install notes

No Gravatar

This is a FAST-PUBLISH article and is incomplete.

A few quick notes on installing the ConfigMgr 2012 Admin Console.

The console is a 32-bit (x86) application and it will run on many operating systems

  • Install .NET Framework 4.0
  • Install the console
  • Install any hotfixes you have applied to the server such as a Cumulative Update

For in-console reporting

  • Install .NET Framework 4.0 Extended (not the Client Profile).  This should have already been installed as a dependency to the Admin Console.
  • Install SQL 2012 CLR Types which is part of the SQL Server Feature Pack.  There is a Windows Installer package for 64 and 32 bit Windows
    • ENU\x64\SQLSysClrTypes.msi
    • ENU\x86\SQLSysClrTypes.msi
  • Then install Microsoft Report Viewer 2010 SP1.

Command Line Parameters

  • ConsoleSetup.exe /q TargetDir=”%ProgramFiles%\Microsoft Configuration Manager\AdminConsole” EnableSQM=1 DefaultSiteServerName=SCCMPrimarySiteServer.Contoso.com
  • ConsoleSetup.exe /uninstall /q
  • ReportViewer.exe /q:a /c:”install.exe /q /l %temp%\ReportViewer2010SP1.log” [credit]

 

July 3, 2014

Posted In: ConfigMgr 2012