When viewing the Package Server in the Agent UI, it only provides UNC codebases. The Admin has selected HTTP, HTTPS, and UNC in Package Service Settings. However the package server was only creating and sending up UNC download sources.
Errors observed in the Agent Logs:
The unlocking of IIS configuration settings using the application "C:\windows\system32\inetsrv\appcmd.exe unlock config -section:system.webServer/handlers" has been succeeded.
Application output:
Unlocked section "system.webServer/handlers" at configuration path "MACHINE/WEBROOT/APPHOST".
-----------------------------------------------------------------------------------------------------
Process: AtrsHost.exe (1152), Thread ID: 3088, Module: AtrsHost.exe
Priority: 4, Source: Altiris.TaskManagement.Common.IISHelper.EnsureWebConfigSectionHandlersUnlocked
Web Server (IIS) role is installed, but the next required Role Services are missing: .NET Extensibility 3.5, ASP.NET 3.5.
-----------------------------------------------------------------------------------------------------
Process: AeXNSAgent.exe (6716), Thread ID: 3200, Module: AeXNSCPackageServer.dll
Priority: 2, Source: Package Server Agent
Not all required features of IIS are installed. IIS will not be used and Package Server's virtual directories will be deleted.
-----------------------------------------------------------------------------------------------------
Process: AeXNSAgent.exe (6716), Thread ID: 3200, Module: AeXNSCPackageServer.dll
Priority: 2, Source: Package Server Agent
What are the required IIS features for the Task Server and the Package Server to build HTTP/s code bases?
ITMS 8.x Package and Task Site Services
Windows Server 2012 R2, 2016, 2019, 2022
There are a set of IIS Features that are required. When those required Features are not installed, the HTTP download option is not available for clients to use. These IIS Features are also required for Package and Task services.
In this particular case, the agent has a check for Roles and Features that needs to be meet. The Agent logs should show what requirements are not present. For example:
"Web Server (IIS) role is installed, but the next required Role Services are missing: ASP, IIS Management Console."
NOTE: .NET 3.5 is no longer required. If you see the message in the logs for .NET 3.5: "Web Server (IIS) role is installed, but the next required Role Services are missing: .NET Extensibility 3.5, ASP.NET 3.5." and other references to .NET 3.5, installing the 4.5 or higher version is all that is required.
Install any missing components and restart the Symantec Management Agent, and you should see HTTP / HTTPs now available.
Here are the Roles/Features as they show up in the Add Roles and Features Wizard:
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
Health and Diagnostics
HTTP Logging
Performance
Static Content Compression
Security
Windows Authentication
Request Filtering
Application Development
ASP.NET 4.6 or higher !!
.NET Extensibility 4.6 or higher!!
ASP
ISAPI Extensions
ISAPI Filters
Websocket Protocol
Management Tools
IIS Management Console
IIS 6 Management Compatibility
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibility
IIS 6 Scripting Tools
IIS 6 Management Console
For Scripting purposes: in the order of installation to avoid cross dependency requirements:
Common HTTP Features IIS-CommonHttpFeatures
Static Content IIS-StaticContent
Default Document IIS-DefaultDocument
Directory Browsing IIS-DirectoryBrowsing
HTTP Errors IIS-HttpErrors
Application Development IIS-ApplicationDevelopment
ASP.NET 4.6 !! IIS-ASPNET
.NET Extensibility 4.6 !! IIS-NetFxExtensibility
ASP IIS-ASP
ISAPI Extensions IIS-ISAPIExtensions
ISAPI Filters IIS-ISAPIFilter
WebSocket Protocol IIS-WebSockets
Health and Diagnostics IIS-HealthAndDiagnostics
HTTP Logging IIS-HttpLogging
Security IIS-Security
Windows Authentication IIS-WindowsAuthentication
Request Filtering IIS-RequestFiltering
Performance IIS-Performance
Static Content Compression IIS-HttpCompressionStatic
Management Tools IIS-WebServerManagementTools
IIS Management Console IIS-ManagementConsole
IIS 6 Management Compatibility IIS-IIS6ManagementCompatibility
IIS 6 Metabase Compatibility IIS-Metabase
IIS 6 WMI Compatibility IIS-WMICompatibility
IIS 6 Scripting Tools IIS-LegacyScripts
IIS 6 Management Console IIS-LegacySnapIn
An example of using command-line to install Features: dism.exe /online /enable-feature /featurename:IIS-WebSockets