Upstream_Collector.ps1

Preinstallation Checklist

Before beginning, verify the following items. If any are not complete, please stop installation.

  • ISO/USB Media still inserted into system, along with verify the drive letter.
  • Are two drives provisioned for the system? C: for OS, and a second for the Collector Installation.
  • Has Microsoft Support provided a unique CollectorId?
  • Do you have the entire Collector hierarchy mapped out already? Which collectors are forwarding where?

Script Execution

  1. Logon onto the Collector and open a PowerShell command window with elevated privileges by right-clicking on Start -> All Programs -> Accessories -> Windows PowerShell -> Windows PowerShell and selecting “Run as Administrator”.

    From the PowerShell command prompt, execute:

     & "Z:\Deploy\CER Source Files\SERA Collector\Upstream_Collector.ps1"
    
  2. Enter the drive letter of the drive containing the install media
    Enter the drive letter of the install media (Ex. Z:)

  3. Enter the drive letter to store the DDWS Website
    Enter the drive letter that will be used to store the DDWS website and data collected (Ex. D:)

  4. Enter the port that the DDWS will listen for forwarded data on. This is an HTTP port. SSL will be configured later, and the HTTP binding can be manually removed. If you change the port, you will need to update the “Data Director Web Service” firewall rule to match manually.
    What HTTP port should the DDWS listen on, SSL will be configured later if required? (Ex. 8080):

  5. Enter the timeout, in seconds, for data transfers. We recommend 1200 (20 minutes).
    What timeout should the transfer services use in seconds? (Ex. 1200):

  6. Is this server forwarding data? Enter ‘y’ to forward data to another Upstream Collector, or to forward data to a Cab Import service. Enter ‘n’ to utilize as a ‘Storing Collector’.
    Is this server forwarding data? (y/n):

  7. If storing, you will not be presented with this prompt. If forwarding, you will be prompted if the forwarding is going to a Cab Import service.
    Is this server forwarding to a Cab Import system? (y/n):

  8. If forwarding to Cab Import, enter the UNC or Local path that Cab Import is monitoring.
    Enter the path which cab import is monitoring (Ex. \cer-db\IncomingLogsCabs, E:\IncomingLogsCabs)

    Note: Use the format of http(s)://fqdn:port. If 80 is used for http, or 443 for https, the port number can be left off.

  9. If regular forwarding, enter the URL to forward to.
    Enter the full URL this server will forward to (Ex. http(s)://upstream.domain.com:8080)

  10. Enter the Collector ID (Note:This should have been predetermined as part of the pre-deployment planning session)
    Enter the collector ID (with the dashes) for this server (Example: db8101f0ff-002-FFF-03-000000-01-01-0001)

    IMPORTANT: Enter the collector IDs of EACH collector that will be forwarding data to THIS collector. These are typically your ‘Client Facing Forwarding Collectors’, but could also be other collectors in the chain.
    Enter collector IDs forwarding to this server, type ‘done’ when there are no more.

    Note: More collectors can be added later by manually editing XML files in DriveLetter:\DDWS_Website\bin\app_data\collectors.xml. Please consult Microsoft support for assistance.

  11. After typing ‘done’, you will be asked to verify the collector IDs that were entered. If a mistake has been made, press Ctrl+C to exit the script and rerun it.

    Note: Collector is operational, however forwarding will fail until the Upstream Collector has been deployed. Downstream collectors should start forwarding to this collector upon restarting the Data Director Service on each collector.