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 ;-)

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.

Using Maintenance Windows in ConfigMgr 2012

In ConfigMgr 2007 it was already possible to configure Maintenance Windows on collections. With Maintenance Windows a Service Window can be set, for installation and/or rebooting functionality. In ConfigMgr 2012 this functionality is still available, which is very handy for Patch Management on production systems. That way you are sure about installation and/or rebooting times, which are usually not during working hours.

Maintenance Windows can be set at the following ways:

• In ConfigMgr 2007: Rightclick on the collection, and choose: "Modify Collection Settings" > Maintenance Windows tab
• In ConfigMgr 2012: Rightclick on the collection, and choose: "Properties" > Maintenance Windows tab

Choose to create a new schedule here, and set properties for the right Service Window. I my case this will be every saturday between 13:00 and 17:00

When configuring Patch Management jobs in ConfigMgr 2012, properties can be set for Maintenance Windows. In the "Automatic Deployment Rule", used for Patch Management, there can be options set to "perform activities outside any defined maintenance windows". Normally this will not be the case.

There can also be options set to suppress reboots on servers and workstations. That way Software Updates will be installed within the Maintenance Window, while rebooting the system will not be done. Then this will be an manually action.

Now have a look at the server where Software Updates are advertised. When Scan Cycle has been run, and updates are needed for the system, an icon will be available in the System tray.

When rightclick on the icon, two options will be available. "Open Software Center" and "View Required Software". Both will have different functionality. When starting "Open Software Center" the following is possible:

There are Software Updates available, but not installed yet. This because of the Maintenance Window! Status here says: "Past due - will be installed". You can also have a look at Options here. There will be settings available for Remote Control and Power Management also.

When choose Schedule here, it is still possible to overrule the Maintenance Window, and install software directly. This is a manually action which can be done per system, which is most of times not recommended. Just leave it.

When starting "View Required Software" it is possible to change software installation settings also. They will be also available in Software Center > Options screen. Again there is a possibility here to install them directly, or "outside the configured business hours".

Best thing is leave these settings alone, and trust on the already configured Maintenance Window. That way you can make sure that installation and/or rebooting is only done within the Service Window!