Essay for you

Sccm Application Catalog Website Point Critical Thinking

Category: Critical thinking

Description

SCCM App Catalog won - t install applications if started as user other than the one logged in - Server Fault

We have been playing around with SCCM's Application Catalog and have come across an interesting quirk. My manager has directed me to implement the catalog so that software that falls somewhere between the "one-off install" and "needed by the entire workgroup" points on the spectrum of how many people need it should be published to the Application Catalog. Our help desk technicians can use the App Catalog to deploy these kinds of software to select users that need it as the situation warrants.

We practice account separation, for example, our help desk rockstar Emmet Brickowski has two Active Directory user accounts. His regular unprivileged account, CONTOSO\ebrickowski he should be using for all his regular work and when a UAC prompt rears its ugly head he has an privileged account ( CONTOSO\ebrickowski-adm ) that is a member of BUILTIN\Administrators on all our workstations.

When Joe User calls the help desk, Emmet remotes in or physically goes to help the user (our culture is big on face-to-face customer time), logs into the App Catalog with his privileged CONTOSO\ebrickowski-adm and sees a plethora of software that he can install in a standardized method for our user.

Except when Emmet presses the Install button he gets this:

Now I cannot find anything in the client-side logs for what happened. Nothing in the AppIntentEval.log. AppDiscovery.log. AppEnforce.log logs and the ConfigMgrSoftwareCatalog.log which is supposed to record the Application Catalog action does not exist.

If we deploy an application to a User Collection containing our regular users and they use the same account they are logged in to Windows as to log into the Application Catalog the same application that previously failed installs. This leads me to believe that you cannot use a separate account for the App Catalog as the current Windows session. Which is kind of a bummer.

  • Can anyone verify that you are required to use the same account to access the Application Catalog as you are currently using in your Windows session?
  • What logs if any should I look into to investigate further?
  • Is there another or better way to accomplish our desired goal of using the Application Catalog as a technician accessed software store?

asked Aug 20 '15 at 17:33

This is by design, only users logged into the computer can install apps via the app catalog. Trying to "fake out" the app catalog by logging into it with a different Id won't work.

The proper way to go about this is to either advertise the programs to all users, or, since that could get messy, have your Rockstar techs log into the computer with their admin account, either in person or remotely with the new SCCM RC. The new one let's techs access the login screen whereas the old one didn't.

Note: you're slightly going against the grain of what MS is trying to accomplish with the app catalog, it's intended for users to install the apps they need, to minimize helpdesk work in a way, so with a little permission finesse you should be able to avoid disasters, but I completely get why you wanna do it this way, I just wanted to mention this so you're aware of why this is a pain.

answered Aug 21 '15 at 12:18

"going against the grain of what MS is trying to accomplish". leadership wants what leadership wants. I pass both options back to them and see what they choose. I'm just trying to make life easier for my techs. – kce Aug 21 '15 at 16:57

Heh, sounds familiar. Rock on @AlaskanHomie. – BigHomie Aug 21 '15 at 18:03

Since there is a technician involved anyway why don't you just have the technician deploy the desired application to that user from the SCCM console?

If you wanted to make it more interactive for the end-user the technician could temporarily add the end-user to an "all applications available" user collection while they access the catalog and figure out what they want to install. Then, once the end-user has the applications installed, you can take them back out of that collection, and maybe deploy the applications they just installed to their user via some other collection.

answered Aug 20 '15 at 21:50

Other articles

Missing Required Software in SCCM 2012 Beta 2 Software Catalog

So, if you’re trying to install an available application from the Software Catalog, you may get a missing required software error. This typically happens on Windows 7 but not on Windows XP. After some investigation, guess what. The Internet Explorer Protected Mode is causing this to happen. The reason this does not occur on my Windows XP is that it does not have a version of Internet Explorer that has this Protected Mode.

To solve it, you need to include the SCCM 2012 server which is also the Application Catalog Web Site Point. To do that, select on the Trusted Sites, and then click the Sites button.

Here’s where you should include the URL of your Application Catalog Web Site Point. This may require you to close and open (restart) your Internet Explorer browser. Try again and it worked like a charm for me after that.

Like this: Post navigation Leave a Reply Cancel reply

I was going crazy troubleshooting this.

good one! i facing same problem and i found this article

I like the valuable info you provide in your articles.

I will bookmark your weblog and check again here regularly.
I’m quite sure I’ll learn plenty of new stuff right here!
Best of luck for the next!

SCCM 2012 Application Catalog Website: Make sure WCF is activated - and

Home › SCCM › SCCM 2012 Application Catalog Website: “Make sure WCF is activated” and .NET Unhandled Exceptions

SCCM 2012 Application Catalog Website: “Make sure WCF is activated” and .NET Unhandled Exceptions

In my brand new environment I am happily installing the marvelous SCCM features when from nowhere I have difficulty adding the application catalog website role to my single server standalone primary site. What in the world. I see two repeating errors:

Site Component Manager failed to install component

The WCF is not activated

Solution: Make sure the WCF is activated.

I start looking around and realize that I’ve forgotten to include the WCF service as a part of the .NET framework installation.

I install the feature and both subfeatures, then open the CM service manager and restart the SMS_SITE_COMPONENT_MANAGER service so that the installation will immediately restart, or I could have waited 60 minutes and viola!

Or so I thought….after it was successfully installed I was getting unhandled exception .NET errors when attempting to browse to the CMApplicationCatalog website.

Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’.

DOH! I forgot to register the .NET Framework 4.0 components like a big fool. Props to Russ Rimmerman for posting up .

I ran this command: %windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –i –enable, which didn’t work for me, it just kept spitting out the help message, which one other person complained of in the above Russ Rimmerman post, even when drilling into the directory with the command prompt. After fiddling around with that for a while I started getting this error: aspnet_regiis.exe is not a valid Win32 application.

So I performed a repair of the .NET framework 4.0 from the Programs and Applications in control panel, then performed the following command line, which worked:

Annnnnd it worked! Except, then I was getting an authentication problem where no matter what credentials I used I couldn’t log in. Peachy.

So then I found this article:

Where they suggested to once again, remove the roles from the server, perform aspnet_regiis.exe /iru, then reinstall the roles.

and FINALLY 8 years later we have a working Application Catalog. And now I need a nap.

Moral of the story:

  1. Ensure that .NET WCF is installed as a prereq
  2. Ensure that .NET 4.0 is registered with IIS (You can do this by installing .NET 4.0 before the IIS roles, or via the command line afterwards)
  3. Ensure that your installation of .NET 4.0 is good.

SCCM Management Point Critical Status - Configuration Manager 2012

  • Like This
  • Unlike
i.luciano@tcnb.com 07 Oct 2013

I am having nothing but trouble with my SCCM 2012. I am running Server 2012 Standard, SQL server 2012 and SCCM with Endpoint Protection SP1. The install looks like it goes well but when i start to try and use client push i start to get all types errors. Under site status i have a critical staus for the Management point. And under component status my SMS_MP_CONTROL_MANAGER and SMS_NOTIFICATION_SERVER components have a critical stauts as well. I already have tried reinstalling a total of three time. If any one had any help or insight into my issues please help.

I have attatched my log files.

  • Like This
  • Unlike
lord_hydrax 08 Oct 2013

Looks like the Management Point is not installed at all, it keeps failing with a fatal error when it tries to install.

I think this article is relevant to do a clean install of a MP and worth a shot:

    - Remove the MP as a site system role (if it is still installed), wait for it to finish

    - Remove IIS completely

    - Reboot the server

    - Stop the Task Scheduler Service

    - Rename the %windir%\Tasks folder to something else (or move it)

    - Start the Task Scheduler Service (this will recreate the %windir%\Tasks folder)

    - Reinstall IIS, BITS, WebDAV

    - Ensure BITS and WebDAV are enabled

    - Reinstall the MP

New important features in SCCM 2012

User Centric Management. Software distributions can now be targeted at users rather than just at devices.

Call center, help desk or where multiple users share the same hardware.Additionally, users can define a primary device (or you can set up rules to determine a primary device) and have a different software policy for primary and non-primary devices. Consider the scenario where a manager logs onto a subordinates workstation temporarily, if the system is not designated as his primary device, any applications specifically targeted at managers primary devices, will not be available to him on that system.

Dependency-based software distribution or “Conditional Delivery”

In SCCM 2012 Requirement Rules and/or Global Conditions are used to specify preconditions for a deployment such as: available hardware (e.g, available hard disk space, etc.), software pre-requisites (e.g. Office must be installed as a prerequisite for Office SP1), user affinity – conditional delivery also determines which device is the user’s primary or secondary device and behaves accordingly. This is a much more elegant approach to application management, especially when coupled with the new concept of Deployment Types. An application can have multiple deployment types (such as an upgrade, uninstall, virtual app, local install, mobile device version) and the deployment type can be triggered based on the Requirement Rules or Global Conditions. This mean that delivery method automatically determines whether a user is on a virtual machine, a mobile device, terminal server, or a desktop/laptop and then determines how to deliver the application to the user – choosing between streaming the application, publishing it on a presentation server, or through regular software deployment method. Note, that application needs to be packaged only once within the system. This also mean that many application package in sccm 07 need to be re-packaged in order to use this new sccm 12 features.

Collection-based configuration settings

Client configuration settings are designated at a site level in 2007

Now Configuration Settings and can be applied to desktops, servers, mobile devices and users. This mean that this new functionality is the able to remediate WMI, registry, and script settings that are not compliant. Automated remediation can drastically reduce TCO.Settings and can be applied to desktops, servers, mobile devices and users

Software Center is a local SCCM client program that replaced Run Advertised Programs present in SCCM 2007. Software Center allows users to set some configurable settings and to see what software are available for install.Note diference between Software Center and Application Catalog: The Application Catalog or Software Portal is the web page for available applications that user can install while Software Center helps the user track the status of available and required software, and lets users configure various options, such as their business hours to prevent their computer from restarting during their working day.

Software Portal or Application Catalog

The software portal allows applications to be available to a user via a web page, which user can install on their own schedule. This allows for less user disruption, as software applications aren’t forced on users. Applications on demand also reduce the burden on the IT staff, as they don’t have to always be available to distribute an application to a user. The software portal is ideal for delivery of non-critical applications to a user. Applications can still be associated to a user or a group, thus giving administrators control over which applications users can install. User do not have to have SCCM client in order to use Software porta, but it has to have the MS Silver light and ActiveX control (called ClientBridgeControl) must be allowed to run. This ActiveX control is is installed together with the SCCM client.

Now we have under same console all old SCCM 2007 services and Microsoft Application Virtualization (App-V)Microsoft Enterprise Virtualization (Med-V)Citrix XenAppMicrosoft Forefront 2010

And no more MMC. Huraaa!

Hierarchy and Client Improvements

Throttling and scheduling tasks can be administered on the distribution points, which will remove the requirement for additional primary sites when these tasks needed to be divided between different administrative groups. Role based security is also being introduced in SCCM 2012, thus bringing granular control settings to the system, which will allow enterprise administrators to assign site specific administrators only the rights they need to perform the tasks.

How to Fine Tune the Monitoring of ConfigMgr SCCM 2012 with SCOM OpsMgr Management Pack

SCOM Management Pack for Configuration Manager 2012 is available. This post will help to know more about the critical classes which need to be monitored via SCCM 2012 Management Pack. This may also help to understand the registry keys and event IDs involved in the monitoring process. The details of registry keys and event ids will be very helpful at the time of troubleshooting CM 2012 issues. Note that, I’ve not included performance monitoring and threshold settings details in this post.

In my experience, we waste loads of time in implementing and fine tuning SCCM 2007 MP. Implementing Management Pack directly into production environment is not very good approach. The best method is to implement the MP in lab environment and configure and fine tune it. Once you’re convinced with the alerts then move to production environment. Read the installation guide of the Management Pack and that should be the first step you need to take before the implementation of MP.

SCCM 2007 Management Pack won’t work with ConfigMgr 2012. CM 2012 MP can be used with SCOM 2007 R2 or later and System Center Configuration Manager 2012.

Before going into details of classes, I just wanted share an excellent blog post from Kevin Holman on CM 2012 MP improvements. As per his analysis there are loads of improvements in the management pack for CM 2012. The biggest problem with ConfigMgr 2007 MP is that it just converted from MOM 2005. Hence it came with lots of bugs. Following are the improvements highlighted as part of SCCM 2012 MP.

NO SCRIPTS in the Monitoring, Decrease in Lines of code, Decrease in Number of workflows, Disabled Workflows out of the box and Well documented guide.

The details of Critical Classes in ConfigMgr 2012 Management Pack :-

Fallback status point is monitored via the registry key “HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_FALLBACK_STATUS_POINT\ Availability State”

Management point is being monitored through HTTP responses, IIS and SMS Agent Host service. Along with this SCOM will monitor the threshold settings on all the threads of Management Point.

a) Management Point HTTP Response Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_MP_CONTROL_MANAGER\ 65AC53A5-8C79-4DF9-AE79-A53F689C2222\ Severity
b) IIS Service Availability Monitor on Management Point NT Service: W3SVC
c) Management Point Availability Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\\Availability State
d) SMS Agent Host Service Availability Monitor NT Service: CcmExec

PXE service point is monitored through WDS availability and this is by accomplished by monitoring NT Service: wdsserver .

Site database server availability is monitored via SQL Writer Service Availability Monitor NT Service: SQLWriter

Software update point availability is monitored via registry key and two NT services mentioned below.

a) Software Update Point Availability Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\\Availability State
b) IIS Service Availability Monitor on Software Update Point NT Service: W3SVC
c) WSUS Windows Service Availability Monitor NT Service: WSUSService

Reporting services point Availability can be monitored through

a) Reporting Service Point Availability Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\\Availability State.

b) SQL Reporting Service Availability Monitor NT Service: ReportServer

Application Catalog web service point availability is monitored via following registry and service.

a) IIS Service Availability Monitor on Application Catalog Web Service Point NT Service: W3SVC
b) Application Catalog Web Service Point Availability Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\\Availability State
c) Application Catalog Web Service Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_AWEBSVC_CONTROL_MANAGER\ F0128B76-DD22-481D-A65B-270201AED381\ Severity
d) Application Catalog Web Service IIS Configuration Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_AWEBSVC_CONTROL_MANAGER\ 0B543BAC-54C7-463D-BDA5-ADD9F71AEA09\ Severity

Application Catalog website point availability is monitored via following registry and service.

a) IIS Service Availability Monitor on Application Catalog Web Site Point NT Service: W3SVC
Application Catalog Web Site Point Availability Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\\Availability State
b) Application Catalog Web Server Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_PORTALWEB_CONTROL_MANAGER\ 0B12B4BA-B838-4927-ADC1-2E9602B076E3\ Severity
c) Application Catalog IIS Configuration Monitor Registry: HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_PORTALWEB_CONTROL_MANAGER\ 4A06F831-B577-4C10-8643-8C577C2C22B3\ Severity

Database Notification Monitor availability is monitored via Windows Event ID 2420 (Site server fails to execute a maintenance task)

Distribution Manager availability is monitored via Windows Event ID 2323 (i.e Distribution manager fails to access network).

Primary To Central Site Replication monitoring has achieved through following WMI queries. Primary Site To Central Site “Global Data Receiving Status Monitor”, “Global Data Sending Status Monitor” and “Site Data Sending Status Monitor”. Default time interval is 6 minutes.

Central To Primary Site Replication monitoring has achieved through following WMI queries. Central Site to Primary Site Global Data Receiving Status Monitor, Global Data Sending Status Monitor and Site Data Receiving Status Monitor. Default time interval is 6 minutes.

Primary or Standalone site server availability is monitored through Active Directory Configuration Monitor for Device Management Registry key status HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_EN_ADSERVICE_MONITOR\ CAFD8C35-08B6-4772-9101-B1B220CBA044\ Severity. There are loads performance threshold monitoring can also achieved through SCOM.

Site Component Manager availability is monitored via following event IDs, NT service and registry Keys.

a) Windows Event ID 4909 (Site component manager fails to read Active Directory objects)
b) Windows Event ID 4912 (Site component manager fails to update Active Directory objects)
c) Windows Event ID 1037 (Component manager fails to access site system)
d) Site Server Component Service Availability Monitor via NT Service: SMS_SITE_COMPONENT_MANAGER
e) Site Component Manager Availability Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_SITE_COMPONENT_MANAGER\ Availability State

Site Server Role availability is monitors via following registry key. Site Server Connectivity To SQL Database Server Via Registry Key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role\\Availability State

Site Server availability is ensured via following registry keys and WMI Query.

a) Database Certificate Validity Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_HIERARCHY_MANAGER\ FBCA00DB-7C9D-4d6d-9F84-07C605B31191\ Severity
b) WSUS Synchronization Failed WMI Query
c) SQL Server Disk Space Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_HIERARCHY_MANAGER\ 6FD0B53A-35DA-4da1-84C9-A9E1B6C12828\ Severity
d) SQL Server Firewall Port Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_HIERARCHY_MANAGER\ 8D5E5CC1-CCF5-4c66-BC8A-527C9066161B\ Severity
e) SQL Server Port Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_HIERARCHY_MANAGER\ B1B669B9-6C11-4b8e-A09A-4E515D20F4F6\ Severity
f) SQL Server Service Broker Certificate Validity Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_HIERARCHY_MANAGER\ 812A1E5F-B31C-45a5-89EE-695460882F38\ Severity
g) SQL Server Service Broker Port Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_HIERARCHY_MANAGER\ D362CF53-926B-4f7d-A4A2-0691D3F177F5\ Severity

WSUS Control Manager Availability is being Monitored via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_WSUS_CONTROL_MANAGER\ Availability State

WSUS Synchronization Manager Availability is being Monitored via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_WSUS_SYNC_MANAGER\ Availability State

WSUS Configuration Manager availability is being monitored by following event ids and registry key.

a) WSUS Configuration Manager Availability Monitor via Registry key HKLM\SOFTWARE\Microsoft\SMS\Operations Management\Components\ SMS_WSUS_CONFIGURATION_MANAGER\ Availability State.
b) Fail to configure proxy setting on WSUS server via Windows Event ID 7000.
c) This rule generates alert when the WSUS configuration manager fails to publish client to the WSUS server via Windows Event ID 6613.
d) Fail to subscribe to or get update categories and classification via Windows Event ID 6603.
e) WSUS version mismatch via Windows Event ID 7004.

Note :- The core information shared in this post is taken from the following document. Download the doc from ConfigMgr_MPGuide_Appendix.docx. Even Kevin’s blog has also inspired from the document OpsMgr_MP_ConfigMgr.docx .

How to install SCCM 2012 Application Catalog

In part 1 of this SCCM 2012 R2 Installation Guide blog series. we planned our hierarchy, prepared our SCCM 2012 R2 Server and Active Directory.

In part 2. we installed and configured SQL in order to install SCCM 2012 R2.

In part 3. we installed a stand-alone SCCM 2012 R2 Primary site.

In the next 16 parts. we will describe how to install the numerous site systems roles available in SCCM 2012 R2. Role installation order is not important, you can install roles independently of others.

This part will describe how to install SCCM 2012 Application Catalog web service point and the Application Catalog website point.

Role Description

The Application Catalog web service point provides software information to the Application Catalog website from the Software Library.

The Application Catalog website point provides users with a list of available software.

This is not a mandatory site system but you need both the Application Catalog website point and the Application Catalog web service point if you want to provide your user with a Self-Service application catalog (web portal).

Site System Role Placement in Hierarchy

The Application Catalog web service point and the Application Catalog website point are hierarchy-wide options. It’s supported to install those roles on a stand-alone Primary site or child Primary site. It’s not supported to install it on a Central Administration site or Seconday site. The Application Catalog web service point must reside in the same forest as the site database.

If you’re having less than 10,000 users in your company, co-locating the Application Catalog web service and Application Catalog website roles on the same server should be ok. The web service role connects directly to the SCCM SQL database so ensure that the network connectivity between the SQL server and the Application Catalog web service servers is robust.

If you have more geographically distributed users, consider deploying additional application catalogs to keep responsiveness high and user satisfaction up. Use client settings to configure collections of computers to use different Application Catalog servers.

Continue to read the complete blog post here. http://www.systemcenterdudes.com/how-to-install-sccm-2012-application-catalog/

How to install SCCM 2012 Application Catalog

How to install SCCM 2012 Application Catalog

In the first part of this SCCM 2012 and SCCM 1511 blog series, we planned our hierarchy, prepared our SCCM Server and Active Directory.

In part 2. we installed and configured SQL in order to install SCCM.

In part 3. we installed a stand-alone SCCM Primary site.

In the next 16 parts, we will describe how to install the numerous site systems roles available in SCCM 2012 R2 and SCCM 1511. Role installation order is not important, you can install roles independently of others.

This part will describe how to install SCCM 2012 Application Catalog web service point and the Application Catalog website point.

Role Description

The Application Catalog web service point provides software information to the Application Catalog website from the Software Library.

The Application Catalog website point provides users with a list of available software.

This is not a mandatory site system but you need both the Application Catalog website point and the Application Catalog web service point if you want to provide your user with a Self-Service application catalog (web portal).

Site System Role Placement in Hierarchy

The Application Catalog web service point and the Application Catalog website point are hierarchy-wide options. It’s supported to install those roles on a stand-alone Primary site or child Primary site. It’s not supported to install it on a Central Administration site or Seconday site. The Application Catalog web service point must reside in the same forest as the site database.

If you’re having less than 10,000 users in your company, co-locating the Application Catalog web service and Application Catalog website roles on the same server should be ok. The web service role connects directly to the SCCM SQL database so ensure that the network connectivity between the SQL server and the Application Catalog web service servers is robust.

If you have more geographically distributed users, consider deploying additional application catalogs to keep responsiveness high and user satisfaction up. Use client settings to configure collections of computers to use different Application Catalog servers.

Read more on how to provide a great application catalog experience to your user in this Technet blog article .

If your client needs HTTPS connections, you must first deploy a web server certificate to the site system. If you need to allow Internet clients to access the application catalog, you also need to deploy a web server certificate to the Management Point configured to support Internet clients. When supporting Internet clients, Microsoft recommends that you install the Application Catalog website point in a perimeter network, and the Application Catalog web service point on the intranet. For more information about certificates see the following Technet article.

Prerequisites

Using Windows Server 2012, the following features must be installed before the role installation:

Application Catalog web service point

  • .NET Framework 3.5 SP1 and 4.0
  • HTTP Activation
  • Non-HTTP Activation
  • ASP.NET (and automatically selected options)
  • IIS 6 Management Compatibility
    • IIS 6 Metabase Compatibility

Application Catalog website point

  • Common HTTP Features
    • Static Content
    • Default Document
  • Application Development
    • ASP.NET (and automatically selected options)
  • Security
    • Windows Authentication
  • IIS 6 Management Compatibility
    • IIS 6 Metabase Compatibility
SCCM 2012 Application Catalog Installation

For this post we will be installing both role on our stand-alone Primary site using HTTP connections. If you split the roles between different machine, do the installation section twice, once for the first site system (selecting Application Catalog web service point during role selection) and a second time on the other site system (selecting Application Catalog website point during role selection).

  • Open the SCCM console
  • Navigate to Administration / Site Configuration / Serversand Site System Roles
  • Right click your Site System and click Add Site System Roles
  • On the General tab, click Next

  • On the Site System Role tab, select Application Catalog web service point and Application Catalog website point, click Next

  • On the Application Catalog Web Service Point
    • In the IIS Website and Web application name fields, leave both to the default values
    • This is just the name that you’ll see in IIS after the installation (see next screenshot). It has nothing to do with your user facing portal
    • Enter the port and protocol that you want to use

  • On theApplication Catalog WebSite Point
    • In the IIS Website keep the default value
    • In Web application name, enter the name that you want for your Application Catalog. This is the URL that will be published to your users
    • Enter the port and protocol that you want to use

  • On the Application Catalog Customizations tab, enter your organisation name and the desired color for your website

  • On the Summary tab, review your settings, click Next and complete the wizard

Verification and Logs files

You can verify the role installation in the following logs:

  • ConfigMgrInstallationPath\Logs\SMSAWEBSVCSetup.log and awebsvcMSI.log – Records details of about the Application Catalog Web Service Point installation
  • ConfigMgrInstallationPath\Logs\SMSPORTALWEBSetup.log and portlwebMSI.log – Records details of about the Application Catalog Website Point installation
  • Open the SCCM Console
  • Go to Monitoring / System Status / Component Status
  • See status of the components SMS_PORTALWEB_CONTROL_MANAGER and SMS_AWEBSVC_CONTROL_MANAGER

Verify that the Application Catalog is accessible :

  • Open Internet Explorer
  • Browse to http://YourServerName/CMApplicationCatalog
    • Replace YourServerName with the server name on which you installed the Application Catalog Website Point
    • Replace CMApplicationCatalog with the name that you give your Application Catalog. (Default is CMApplicationCatalog)

If everything is setup correctly, you’ll see a web page like this :

URL Redirection

The default URL to access the Application Catalog is not really intuitive for your users.

It’s possible to create a DNS entry to redirect it to something easier (ex: http://ApplicationCatalog)

The following Coretech article describe how to achieve that.

Client Settings

Ensure that the client settings for your clients are set correctly to access the Application Catalog

  • Open the SCCM Console
  • Go to Administration / Client Settings
  • Right-click your client settings and select Properties
  • On the left pane, select Computer Agent
  • Click the Set Website button and select your Application Catalog (the name will be automatically populated if your Application Catalog is installed)
  • Select Yes on both Add Default Application Catalog website to Internet Explorer trusted site zone and Allow Silverlight application to run in elevated trust mode
  • Enter your organisation name in Organisation name displayed in Software Center

That’s it, you’ve installed your SCCM 2012 Application Catalog, publish the link to your user and start publishing your applications.