StifleR POC Quick Checklist
The below table is a checklist which can be followed to prepare for a StifleR Proof of Concept project.
Status | Type | Detail |
---|---|---|
Action | Review StifleR Documentation. | |
Decision Point | Determine how many locations will participate in the POC. | |
Decision Point | Determine how many clients will participate in the POC. | |
Action | Prepare a dedicated server (VM) to host the StifleR server. See specific hardware requirements. | |
Action | Provision a standard SSL web server certificate with StifleR server computer name in the Subject Name. | |
Decision Point | Determine if 2Pint Team will have remote access to POC environment. If so, provide the following:
| |
Action | If using Configuration Manager, LEDBAT and BranchCache should be enabled on the Distribution Points which serve the locations participating in the POC. | |
Action | Remove existing BITS, BranchCache, and Delivery Optimization policies from clients participating in the POC. See this page for more information on how to Configure Microsoft Peer-to-Peer Components. | |
Action | Open any Firewall Ports as documented here. | |
Action | Add Antivirus Exclusions as documented here. | |
Action | ||
Action | Install StifleR Server software on the StifleR Server. | |
Action | Install the StifleR Server Dashboard on the StifleR Server. | |
Action | Deploy StifleR Client in a phased deployment to clients participating in the POC. | |
Action | As clients report in, the Locations, Network Groups, and Subnets will automatically be created in StifleR. This should be reviewed in the StifleR Dashboard and changes should be made to regroup or reorganize the network hierarchy if necessary. Please see the Configure the Network Locations page for more information. | |
Action | Deploy Applications to clients and review Testing and Validation documentation. | |
Decision Point | Determine if StifleR has met the requirements set forth by the POC. |
Last updated