Laserfiche WebLink
the project team will have a clear understanding of how Exchange Online will be able to assist in meeting your business <br />objectives. <br />1. Current Environment review <br />o Active Directory <br />0 Messaging Environment <br />o Network <br />2, Requirements Gathering and validation <br />o Business requirements <br />o Technical requirements <br />3. Map requirements to Office 365 Service Descriptions <br />o Office 365 Platform Service Description <br />o Exchange Online Service Description <br />o Exchange Online Archiving Service Description <br />o Exchange Online Protection Service Description <br />4. Identify requirements not met by Exchange Online and recommend potential alternatives <br />DESIGN SESSIONS <br />Based on the requirements identified in the Planning session, Seller will work with the project team to determine the end. <br />state Exchange design. During the design sessions, priority will be placed on quickly identifying the resources and system <br />changes necessary for the production implementation. In some circumstances, the items listed below may have been <br />identified prior to the design session. Potential resources include: <br />1. Server (physical or virtual) acquisition, installation, and configuration <br />2. Data storage <br />3. Network devices such as load balancers or reverse proxies <br />4. Additional required licenses <br />5. Security (including Certificates, DNS, etc.) <br />Potential changes include: <br />1. Storage configuration <br />2. Active Directory remediation <br />3. Active Directory schema changes <br />4. Implementation of firewall and web proxy rules <br />5. Software updates to current environment to support compatibility with the new version <br />Seller will make every effort to identify these resources and changes as early in the design process as feasible. In some cases, <br />the Customer may need several days or weeks to meet with responsible stakeholders, acquire the identified resources, or <br />implement the necessary changes. This may affect the timeline for the production implementation. <br />Core System Design <br />o Directory Integration and Authentication <br />• Active Directory and Namespace Integration <br />• Directory Synchronisation <br />• Supported authentication methods <br />• Extemal client support <br />• Public Key Infrastmmum (PKI) <br />• Firewall requirements <br />• Server Requirements <br />o Transport Design <br />• DNS and Namespace design <br />• Routing <br />ProPrear, nd Confi&nfial Pagc3 SLED- 111701 CDW Govemmmt LLC <br />SOW 122020 <br />