Posted tagged ‘Install’

App Portal 2013 Installation–Part 2

August 27, 2013


Up to this point we’ve prepared the environment for the App Portal end have installed the App Portal Web Service (ESDWebService).  The next step is to install the App Portal Platform, which consists of the App Portal Website, Service, and Database.

App Portal 2013 Platform Installation

  • On the server where you are installing the App Portal Platform, launch AppPortalSetup_2013.exe as an administrator.
  • Click Install when notified that Microsoft ReportViewer 2012 will be installed.


  • If you receive a Missing Roles error message that most likely means that you’ve missed an IIS component.  Thankfully the installer tells us which IIS component we are missing.  Visit to look up the reference ID.  In this example, I’ve missed IIS: 148 which is ASP.NET.  Exit the installer, correct the missing component, and return to the installer.



  • Click Next on the Welcome screen. Accept the license agreement on the next screen and then click Next.
  • Set the Destination Folder and then click Next.
  • In the Specify Site Alias screen, enter the DNS alias in the provided field and then click Next.  Did you forget to create an alias?  No worries, you can change this later.  In that instance use the server name and click Next.


  • Enter the Database Server Name in the provided field, enter a Database Catalog (e.g. AppPortal), and then click Next.
  • On the Logon Information, enter the service account details that has access to the SQL database and then click Next.  If you receive an error it is most likely because the Computer Browser service isn’t running.  Simply uncheck the Validate Account and Password and then click Next again.


  • Enter the name of the Global Catalog Server and the SMTP information.  For the email prefix and suffix setting an email address of would be appportal for the prefix and for the suffix.  Do not include the @ symbol.  Click Next.
  • On the Computer Discovery Method screen, leave the defaults (especially the Populate Sample App Portal Data checkbox) and click Next.
  • Click Install. Setup will now install the App Portal Platform.  This may take a little time.
  • Once setup has completed click the Finish button.  Now we need to verify that the App Portal Platform installed correctly.

Verifying App Portal 2013 Installation

  • Navigate to the root of C:\ and open the ESD_Upgrade_Log file.  Scroll to the bottom and locate the following entry: Database schema synchronization finished successfully.  Close the log file.
  • Launch Internet Information Services (IIS) Manager.  Click on Application Pools and locate SelfService.  This should be running on .NET Framework 4.0 and be set to use the service account.  Expand Sites and click on ESD.
  • On ESD, double-click Authentication.  Receive an error (shown below)?  That means that you forgot to remove the authentication lock so that App Portal can configure the authentication types.  Go back to the Default Web Site node and correct this using Configuration Editor (system.webServer/security/authentication/windowsAuthentication).  Verify that Windows Authentication is Enabled and that all other authentication types are Disabled on the ESD node.  Close Internet Information Services (IIS) Manager.



  • Launch Services.msc.  Locate ESDService and verify that the service is running as the service account.  Close the Services Window.

The App Portal 2013 Platform is now installed.  Next are post installation tasks to integrate the App Portal with your deployment system, which is SCCM 2012 in this example.


App Portal 2013 Installation–Part 1

August 23, 2013


All of our prerequisites are done and we are ready to begin installing the App Portal.  We will be installing the components in the following order: App Portal Web Service; App Portal Platform. 

Installing App Portal Web Service

We will be installing the App Portal Web Service on FLEXCM1, the only SCCM 2012 server in my lab.  Remember, if you have SCCM 2012, this service will only need to be installed on the CAS (or single primary).  If you are installing this on SCCM 2007 then you will need to install this on the CEN and each primary site server.

  • Launch AppPortalWebServiceSetup_2013.exe as an administrator on your target server.
  • Click Next on the Welcome screen.
  • Accept the license agreement and then click Next to continue.
  • Select your Destination Folder and then click Next.
  • The next screen will be labeled Primary Site Server Setup.  This is misleading.  You will want to plug in the information that is relevant for your environment.  If are installing this on your CAS, then you would put that information in here.  In my case, since everything was local, the installer populated the correct information.  Once you have the correct information, click Next.

AP Web

  • Click Install on the Ready to Install screen.
  • The installation should be pretty quick.  Once it has completed click Finish.

Verifying the App Portal Web Service Installation

Now that the web service installation is complete, did it install correctly?  Let’s take a few steps to verify that it is installed and working properly.

  • Launch Programs and Features and look for an entry for App Portal Web Service 2013.  Close Programs and Features.
  • Launch Internet Information Services (IIS) Manager. From the local computer name, navigate to Application Pools.  Locate ESDWebService.  This service should be using v2.0 of the .NET Framework and be running as LocalSystem (Identity).

AP ESDWebService

  • Expand Sites > Default Web Site.  Click on ESDWebService. Under IIS, double click Authentication.  In the Authentication screen Windows Authentication should be Enabled while all other authentication types should be set to Disabled.

AP Web Service Authen

  • Close Internet Information Services (IIS) Manager.
  • Open Internet Explorer and browse to http://%servername%/esdwebservice/esdwebservice.asmx.  You should NOT be prompted for a password and an ESDWebService screen should appear.
  • Click the link for Is2012 and then click Invoke on the next screen.  The value should be set to true (unless you are using SCCM 2007).  Close the results window to go back to the ESDWebService > Is2012 screen.  Click the here link.
  • Click the link for GetPackages, enter the SCCM server name for the strSiteServer value, and then click Invoke.  You should get an XML results screen containing some package information.

ESDWebService GetPackages

  • Close Internet Explorer and launch the Configuration Manager Console.
  • In Assets and Compliance, under Overview, expand User Collections and Device Collections.  Under User Collections you should see a new folder named App Portal Users for Site XXX (where XXX is your site code).  Under Device Collections you should see App Portal Devices for Site XXX.

AP User Collection

AP Device Collection

  • Close the Configuration Manager Console.  We have not validated that the App Portal Web Service has installed correctly and that it has the appropriate access to the SCCM environment.

In the next part, we will install the App Portal Platform…

App Portal Pre-installation Requirements

August 22, 2013

We are almost ready to perform our installation of the App Portal.  Before we do, we need to ensure that we have a few things ready, configured, and installed before we start.

Points of Consideration

  • Active Directory
  • User-Computer Relationship
  • App Portal Web Service Locations
  • Service Account
  • DNS Alias
  • Database

Active Directory: The App Portal obtains data from Active Directory as well as your deployment system (SCCM in our case).  User data is refreshed when AD User Discovery is run.  Be sure that this is set to run at regular intervals.

In SCCM 2012, you can check this by going to Administration > Overview > Hierarchy Configuration > Discovery Methods > Active Directory User Discovery.  Double click and then select the Polling Schedule tab.

User-Computer Relationship: The App Portal supports several methods for user to computer relationship mapping, including custom options.  The built-in options (for SCCM 2012) include: Use SCCM last logon user; Use SCCM Primary Console Usage; Use AD Computer Managed By; Use User Affinity

I’ve selected Use User Affinity for my implementation.

Want to change the user to computer relationship?  No problem.  Connect to the Admin space on the App Portal website and navigate to Site Management > Settings > Deployment > SCCM 2012.  Change the User / Computer relationship setting.

App Portal Web Service Locations: Depending on the deployment technology, SCCM 2007, SCCM 2012, or Altiris, there are different requirements as to where the App Portal Web Service needs to be installed.  For our SCCM 2012 implementation, we only need to install this web service on the CAS (or single primary).

Service Account: The App Portal requires a service account for installation.  This account requires access to SCCM and to the SCCM database.

We will be using sccmService for our service account.

DNS Alias: It is recommended that you have a DNS alias for App Portal.  I’ve setup appportal for my alias (creative, right?).

Database: App Portal only supports Windows Authentication for SQL.  Further the installing/service account requires DBO permissions.

App Portal Installation Files

  • AppPortalSetup_2013.exe: This is the installer for the App Portal Website, Service, and Database.
  • AppPortalWebServiceSetup.exe: This is the installer for the App Portal Web Service.
  • ActiveX Control for Internet Explorer.msi: Use this MSI to create a Package/Program in your deployment system to deploy to your App Portal client systems.  This MSI is used to identify the system connecting to the App Portal Web Site.  Don’t worry if you don’t use Microsoft Internet Explorer, App Portal supports most of the common internet browsers.  The ActiveX control wouldn’t be needed in those instances.

System Requirements

There are a number of requirements that needs to be in place in order for the App Portal to function properly.  Using the AppPortal2013InstallGuide.pdf as my reference, I’ve divided these into the following four areas:

  • Environment Requirements
  • Client Requirements
  • Server Requirements
  • Information Checklist

Environment Requirements

  • Active Directory Requirements: The App Portal requires a minimum of 2003 functional level for Active Directory.
  • DNS Requirements: IF you are going to leverage reverse DNS as a computer discovery method in the App Portal, your DNS environment will require a reverse DNS zone.
  • Deployment Technology: App Portal 2013 supports SCCM 2007, SCCM 2012, and Altiris.
  • Additional Altiris Requirements: Please reference the AppPortal2013InstallGuide.pdf for these requirements.
  • Inventory Requirements: App Portal relies on hardware inventory to function properly.  For SCCM, be sure hardware inventory is enabled.
  • Distribution Requirements: Software distribution must be enabled in SCCM for App Portal to function properly if you want to use it to distribute software in SCCM.  If you want to deliver Operating Systems then you’ll need to have OSD setup as well.
  • Discovery Requirements: Active Directory User Discovery must be enabled.  Additionally, there are several extensions that App Portal relies on.  These include: Mail; Department; Title; distinguishedName; manager; company; l (lower case L – location); postalCode; sn; givenName; physicalDeliveryOfficeName; DisplayName (SCCM 2012 only).
    • Go back into Active Directory User Discovery Properties in the Configuration Manager Console and click on the Active Directory Attributes tab to add the extensions displayed above.  After you make these changes be sure to initiate a discovery in order to collect this data.
  • Database Requirements: App Portal works on Microsoft SQL Server 2012, 2008, or 2005.
  • Mail System Requirements: App Portal needs an SMTP-compatible mail system in order to send notifications.
  • Internet Information Server (IIS) Requirements: The App Portal requires Microsoft IIS 7.0 or greater.
  • Authentication Requirements: App Portal requires Windows Authentication in to validate user credentials in AD.
  • Network Connectivity Requirements: The App Portal Website should be on the same physical network as the SCCM database (or Altiris database) and have a high speed connection (<= 100MB).
  • .NET Framework: App Portal uses .NET Framework 4.0 (or higher) App Portal Website and App Portal Web Service.  All other site servers require .NET Framework 2.0 SP1 or higher.

Still hanging in there?

Client Requirements

This is a MUCH shorter list:

  • Operating System Requirements: For Windows systems, App Portal supports Windows XP and higher.  App Portal can support any system which is an SCCM client.  We will show that with the Application Model at a later time…
  • Browser Requirements: For the ActiveX control to function, App Portal requires Internet Explorer 8.0 or higher.  App Portal also supports FireFox, Chrome, and Safari.  If you use these browsers you will need to use a different discovery method (or Alternate discovery method).
  • Trusted Sites: The App Portal website (DNS alias) should be added to Trusted Sites in Internet Explorer.

Server Requirements

App Portal Server Requirements are broken down in the following sections:

  • App Portal Web Service
  • App Portal Installation Platform
  • App Portal Service Account

App Portal Web Service

This requirement is for SCCM only, skip this for Altiris.

For SCCM 2007, the App Portal Web Service needs to be installed on the CEN as well as each primary site server.  For SCCM 2012, the App Portal Web Service will need to be installed on the CAS (or single primary) server.

App Portal Installation Platform

The server that will be hosting the App Portal Web Site and the App Portal Service must have IIS 7.0 or greater and must be Windows Server 2008 or greater (Windows Server 2008 R2 or greater is preferred).

App Portal Service Account

The App Portal service account will be used to interact with SQL and AD.  The APP Portal service account will require administrative permissions on client workstations if you with for the App Portal to successfully initiate machine policy evaluation to accelerate software deployments.

The  App Portal service account must have Read permission on the deployment system’s database and Read/Write permission on the App Portal database after installation (The install requires DBO).

Information Checklist

Almost ready to begin our pre-installation work, just need to ensure we have the following information available.

  • Deployment Server Name: This is going to be the CAS, CEN, or single Primary Site Server in SCCM.
  • All Primary Site Servers (SCCM 2007 only)
  • SQL Server Name
  • SQL Instance Name (if any)
  • SQL Installation Type
  • Service Account
  • Verify AD User Discovery Enabled
  • Verify AD Group Discovery Enabled
  • Verify AD System Discovery Enabled
  • SMTP Server Name

Preparing the App Portal Server

This is our last step before we begin our installations.  This work will be performed on the server that will host the App Portal Website, Service, and Database.  If you recall, that would be FLEXAP1 in my configuration (Windows Server 2012).

On the App Portal Server we will be performing the following tasks:

  • Install Required Roles
  • Configure IIS
  • Enable Computer Browser Service

Install Required Roles

We will be installing the Application Server and IIS roles.  If I were installing this on a Windows Server 2008 system , I would have to install .NET Framework 4.0 BEFORE I installed these roles.

  • In Server Manager, on the Dashboard, select Add roles and features.
  • If prompted with a Before you begin screen, click Next.
  • On the Select installation type screen, ensure that Role-based or feature-based installation is selected, and then click Next.
  • Validate that the local server is selected on the Select destination server screen and then click Next.
  • On the Select server roles screen select Application Server and Web Server (IIS), click Add Features when prompted, and then click Next.
  • Click Next on the Select features screen.
  • Click Next on the Application Server screen.
  • On the Select role services screen, leave .NET Framework 4.5 enabled, select Web Server (IIS) Support, click Add Features when prompted, and then click Next.

AP App Server Role Services

  • Click Next on the Web Server (IIS) screen.
  • On the Select role services, leave all the defaults and then check the following: IIS 6 Management Compatibility (and all sub-features); Management Service; .NET Extensibility 3.5; ASP; ASP.NET 3.5; Application Initialization.  Click Next.  PS, don’t worry if you miss one, the installer will let you know!
  • Click Install on the Confirm installation selections screen.

Configure IIS

Since my installation was done on Windows Server 2012, there is an additional step that I need to take in order for App Portal to function properly.  If you recall, App Portal relies on Windows Authentication.  IIS 8 in Windows Server 2012 has this locked by default…. so we need to enable that.

  • Open Internet Information Services (IIS) Manager.
  • Expand Sites from under the computer name and then click on Default Web Site.
  • In the middle pane, under Management, double click Configuration Editor.
  • In Configuration Editor, in the Section drop down, select system.webServer > security > authentication > windowsAuthentication.
  • In the Actions pane, under Section, click Unlock Section.

AP IIS Configuration Editor

  • Close Internet Information Services (IIS) Manager.

Enable Computer Browser Service

The Computer Browser Service is used during installation to validate that the service account works properly.  Check to ensure that the service is running (services.msc).  If it is disabled, enable it for the installation.  If you are not able to enable this service, uncheck the “Verify” setting during that portion of the installation.

We will begin installing the App Portal environment in the next post!