It depends on the complexity of the environment, but these are the expected time frames:
On-premise installation:
...
Topic
...
Time frame estimation (hours)
...
Preparing system requirements
...
8
frame for a single deployment.
For lines marked for High availability add additional 30% for planning
All lines are relevant for on prem. For SaaS- only the lines that are marked for SaaS
Column week is the estimated number of weeks the project will take
Topic | SaaS | High availability | Webex | MS Teams | Time | Week | Resources / Comments |
|---|---|---|---|---|---|---|---|
Preparing system requirements | X | V | V | V | 8 hours | 1 | |
Initial installation and requirements verification |
X | V | V | V | 4 hours | 1 | ||
Configuration finalization and additional installation |
4
Training and enrollment
2
Further testing
2
SaaS installation:
Topic
Time frame estimation (hours)
Configuration finalization and additional installation (if required)
4
Training and enrollment
2
Further testing
V | V | V | V | 4 hours | 2 | ||
Proxy configuration | X | V | V | 6 hours | For MS Teams proxy only | ||
Webex Pre load data for cache | V | X | V | X | 4 hours | 2 | loading existing rooms and users |
For Ethical wall- run in learning mode | V | X | V | V | 2 weeks | 3-4 | Build policy cache by running EW in learning mode |
Test and verify policies. Modify as needed | V | X | V | V | 4 hours | 4 | |
Handling existing content | V | X | V | NA | 2 weeks | 3-4 | Optionally handling existing content that violates EW policies. No customer resources for this stage |
Training and enrollment | V | X | V | V | 4 hours | 5 | |
Further testing | V | X | V | V | 4 hours | 5 | |
Go Live | V | X | V | V | 8 hours | Monitor and tune system |
| Info |
|---|
On a SaaS installation , it is will take AGAT 48 hours to set up the SaaS service |