Software Center not showing applications in ConfigMgr Current Branch

Recently I had an issue at customer location where applications were not showing in ConfigMgr Current Branch. When opening Application Catalog instead all applications showing up without any problem. In the old days only software packages were displayed in Software Center, leaving the Application Catalog for applications. Apparently I was closer to the solution then expected, because I was still looking at the older Software Center, where using the new one was enabled in Client settings. Let's have a closer look.

At this location the shortcut was offered by Group Policy Preferences instead of ConfigMgr default. Microsoft did update the Software Center in ConfigMgr Current Branch, but did not replace the executable which is used. Therefore the link which is used for the old and new Software Center differs form each other:

Old location > C:\Windows\CCM\SCClient.exe

New location > C:\Windows\CCM\ClientUX\SCClient.exe

So yes, you can offer both old and new Software Center, where the old one only showing software packages, and the new one offers both software packages and applications. Long story short: after changing the shortcut in Group Policy Preferences, the issue was gone. Happy with this easy solution ;-)

Site Component Manager failed to install SMS_DMAPPSVC_CONTROL_MANAGER

When installing ConfigMgr 1511 or upgrading to ConfigMgr 1511, the following (known) issue may appear: Site Component Manager failed to install this SMS_DMAPPSVC_CONTROL_MANAGER.
 

 

Site Component Manager could not copy file "D:\Program Files\Microsoft Configuration Manager\bin\x64\InformationService\Config\srvboot.exe" to "<ConfigMgr> \SMS\bin\x64\InformationService\Config\srvboot.exe". The operating system reported error 2: The system cannot find the file specified.

This because a line is missing in the install.map file in the ConfigMgr\root folder. Just add the following line, and place it into the SMS_DMAPPSVC_CONTROL_MANAGER component of the file, to install it successfully: FILE <srvboot.exe><0><3667640>

After that the component will be installed succesfully!

Comment Jason Sandys: This is a known, but completely benign issue. It is annoying but ignorable in 1511. The product group are aware though and *may* issue a fix.

Source: Microsoft TechNet

ConfigMgr 2012 R2 User-based application deployment

Today I deployed applications for Application Catalog usage. During installation the following error message was showed: The software change returned error code 0x643(1603). This is just a generic MSI error and tells you very little. Within Event Viewer the following error message was showed: Administrative Privileges Required. For it seems the user doesn't has enough permissions here?

Within the application deployment, User Experience tab, you can choose Installation behavior. There's "Install for user", "Install for system", and "Install for system if resource is device; otherwise install for user". Mine was configured on last one. Changed that to "Install for system", and all my issues were gone.

So long story short, when deploying to "Install for user", the account must have permissions to run the command-line provided in the chosen deployment type. When deploying to "Install for system", this isn't needed, and deployment is done under SYSTEM permissions.

When looking on Microsoft Technet HERE and HERE it seems that administrator permissions are needed indeed. When using "Install for system" this isn't needed. Issue solved.

List of System Center 2012 SP1 issues still growing

System Center 2012 SP1 is Generally Available, but contains a lot of bugs. Otherwise you can say that additional configuration is needed to let function ConfigMgr well again. Here's a list of ConfigMgr issues known. The list mentioned is still growing everyday. I installed SP1 at customer locations already, and have indeed additional configuration to make it functional again. Let's have a look:

1. ConfigMgr 2012 USMT Migration Fails After SP1 Applied
2. Active Replica Error after the SP1 upgrade for ConfigMgr 2012
3. Server 2012 OSD Issues in ConfigMgr 2012 SP1
4. System Center 2012 Configuration Manager Application Catalog does not refresh on F5 in Windows 8 or Windows Internet Explorer 10
5. Site replication degraded then a minute later, changes back to active
6. Beware when installing ConfigMgr SP1 when still using vSphere 4 or running other platforms not supporting Windows 8
7. ConfigMgr 2012 SP1 client installation error with MicrosoftPolicyPlatformSetup.msi - Hotfix Available! or utilize the new SP1 bits
8. Changes to built-in collections are overwritten when you upgrade to System Center 2012 Configuration Manager SP1
9. Antimalware Policies issue, a workaround, and a forgotten Beta message with ConfigMgr 2012 SP1
10. Service Pack 1 for MS ConfigMgr 2012 Resets the SUP Port to 80 and Why does WSUS not sync anymore in ConfigMgr 2012 SP1?
11. MAC client fails to register in System Center 2012 Configuration Manager SP1
12. Editing reports in Configuration Manager may fail when Internet Explorer is not the default browser
13. System Center 2012 Configuration Manager Application Catalog requires Compatibility Mode in Internet Explorer 10
14. Configmgr SP1 : Windows 7 deployment is not supported anymore from the setup.exe
15. Application Catalog link breaks if you change the regional settings decimal separator in Software Center in System Center 2012 Configuration Manager
16. Client push fails with Authenticode Signature error
17. The 8dot3name settings are disabled on the volumes upon partitioning and formatting of the local disk
18. Antivirus can cause corruption and/or incomplete installations
19. Missing PCM icon even after a successful installation - Workaround available
20. Application evaluation fails in System Center 2012 Configuration Manager running on Windows XP
21. Unhandled exception when launching the System Center 2012 Configuration Manager SP1 Console (Microsoft.ConfigurationManagement.exe)
22. Boot images not updated after upgrading to SP1 in System Center 2012 Configuration Manager
23. CMTrace displaying full logs as empty
24. Software Update-Based Client Installation Fails
25. Virtual Application Fails to Install with Event ID 1008 in the Windows Applications and Services Logs
26. A Migrated Configuration Manager 2007 Configuration Baseline Fails to Evaluate on Client Computers
27. Error Microsoft.Reporting.WinForms.ReportServerException when you run the Roaming User Profiles Health Report

 

There are issues reported also on other System Center products, but ConfigMgr has the most by far. The whole list can be found HERE. Let's hope that the list not becomes any longer.. 

Update 21-1-2013: New issues added to the list
Update 30-1-2013: New issues added to the list again

Application Catalog - Cannot Connect to the Application Server

Today there was a issue with the Application Catalog. When starting the Application Catalog from Software Center the following error was displayed: "Cannot Connect to the Application Server". Strange thing because it was working earlier fine.

Actions that I've done to investigate it:

• Uninstall both Application Catalog roles
• Check SMSPORTALWEBSetup.log and SMSAWEBSVCSetup.log in the Configuration Manager folder to track the uninstall progress
• Install both Application Catalog roles with defaults
• Run %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe /-i –enable
• Solution from SithaYuvaraj

Looking on MS TechNet I found the following post: SCCM 2012 App Catalog Web Page Error

For me this did the trick:

• Adding SYSTEM and/or Local Service account permissions on the Windows\Temp folder

After that the Application Catalog is running fine again! This permissions are needed to let SYSTEM and/or Local Service write to the folder.

Update 29-2: As mentioned on SithaYuvaraj, If you have IPV6 enabled on the SCCM server you may run into this issue as well. Disabling it (or configure it again) resolves this issue!

New Application Catalog in ConfigMgr 2012

In ConfigMgr 2007 their was no default possibility to request new software. When users wanted additional applications, an e-mail or phone call was needed to get it. Some customers were using "Run Advertised Programs" then, to build a kind of Software Catalog. This was working also, but not that user friendly. In ConfigMgr 2012 this is changed with a new Software Center and Application Catalog. In this blog I will describe what functionality comes with these new programs.

In ConfigMgr 2012 there are four new roles available. Two of them has something to do with the Application Catalog. These are:

• Application Catalog Web Service Point (HTTP or HTTPS)
• Application Catalog Web Site Point (HTTP or HTTPS)

I have choosen HTTP on both roles here. Both are needed to have the Application Catalog working. The Software Center is automatically present when the ConfigMgr client is installed. This program is available from the start menu, which is a much better place then the Control panel I think. From the Software Center, the Application Catalog can be started. The Software Center is used for applications and patches that are deployed to the device. The Application Catalog is used for applications that are available for users.

Also there are additional settings available in the "Default Client Agent Settings" > Computer Agent. There the default Application Catalog website can be set, and Install permissions (for users and/or administrators). Now only new applications must be created, and deployed to a user collection. Otherwise applications will not be seen in the Application Catalog!

When opening the Software Center - Installation Status for the first time, there are no applications available. There is an "Track my application requests" here also, which leads to the Application Catalog.

When opening the Software Center - Installed Software for the first time, there are no applications available. There is an "Find additional applications from the Application Catalog" here also.

At Options, settings can be configured for Work information, Power management, Computer maintenance and Remote control. Power management and Remote control can be managed from the "Default Client Agent Settings" policy. For Work information and Computer maintenance this is not possible.

When choosing one of two above links, the Application Catalog is opened in a new web browser. There are no applications seen yet, this because these must be deployed to a user collection first. Now let's have a try!

I have added some new MSI files, which are imported as Applications. These MSI files are deployed to a User collection, which I named Software Catalog. A user group is added to this collection, so with next refresh on the Software Catalog window, my applications must be available (real time)!

When importing these Applications, choose to "Require administrator approval if users request this application" if needed. Otherwise uncheck this. Also user categories, user documentation and a localized description can be added. This can be different for each language selected! To finish it, selecting an icon for the application is also possible.

As you can see some applications need approval here. Other applications can be installed without a approval request. When requesting a new application, a reason is required to request it. In the ConfigMgr console "Approval Requests" is seen beneath Application Management. Within this screen all requests are visible (with reason information), and status for requested, denied or approved.

Now Application Management can be done within the same ConfigMgr console. No need to install a additional solution for this anymore! The only thing noticed, when application settings are changed in the ConfigMgr console, they are not available in the Software Catalog for some time. Hope this will be fixed in a newer release. For this moment a valuable addition in ConfigMgr 2012.