Change the Port Used to Download Files From the Server
search cancel

Change the Port Used to Download Files From the Server


Article ID: 286598


Updated On:


Carbon Black App Control (formerly Cb Protection)


Steps to change the port used to download files from the App Control Server.


  • App Control Server: 8.10.2+
  • Microsoft IIS: All Supported Versions


  1. Verify the firewall, proxy, or other network filtering allows for the desired port to be accessed via the Server Address, example:
  2. Log in to the application server as the Carbon Black Service Account.
  3. Open IIS Manager and in the left-hand pane expand: Server > right click Sites > Add Website and use the following details:
    • Site name: Hostpkg
    • Application Pool: AppCDownloads (for older versions please use this KB to setup second app pool)
    • Physical Path: C:\Program Files (x86)\Bit9\Parity Server\hostpkg\
    • Connect As: Application user (pass-through authentication)
    • Binding Type: https
    • IP Address: All Unassigned
    • Port: Relevant Port (Ex: 8443)
    • SSL Certificate: Specify the same one bound to Parity Console Web
  4. Click OK.
  5. Select the new Site (Hostpkg) and double click the MIME Types options.
  6. Add the following:
    • File name extension: .pem | MIME type: application/x-pem-file
    • File name extension: .egk | MIME type: application/x-egk-file
    • File name extension: .enc | MIME type: application/x-enc-file
    • File name extension: .bt9 | MIME type: application/x-bt9-file
  7. Use an administrative command prompt to issue the command:
  8. Test downloading a file from the new Site in a browser, example:
  9. Log in to the Console and navigate to: System Configuration > Advanced Options > Edit
  10. Adjust the Resource Download Location and Certificate Download Location with the new Site, example:
  11. Restart the services:
    • Carbon Black App Control Reporter
    • Carbon Black App Control Server

Additional Information

When the IIS Certificate for Parity Console Web is replaced, the certificate bindings for the new Hostpkg Site will also need to be updated with the same certificate