The following section lists the different compliance policies and architecture that is supported for the SEG V2 platform.

Supported

Not supported

FR

Future Release

Table 1. Classic SEG and SEG V2 Feature Comparison

 Features

Classic

V2

  Compliance Policies

General Access Policies

 

 

Sync Settings

Managed Device User

EAS Device Type

EAS Mail Client

User

Managed Device Policies

 

 

MDM Inactivity

Device Compromised

Device Encryption

Device Model

Device OS

Require EAS Profile

Email Security Policies

 

 

Email Classification

Attachment Control

VMware Browser Integration

  Architecture

Mail Server

 

 

Microsoft Exchange (2010+)

Office 365

IBM Notes Traveler (8.5+)

Google

Other ActiveSync

Authentication

 

 

Basic Authentication

Certificate Authentication (KCD)

Outbound Proxy

 

 

To API

To Email Server

Sizing

Without Email Security Policies

2 CPU Core per 4,000 devices

2 CPU Core per 8,000 devices

With Email Security Policies

2 CPU Core per 500 devices

2 CPU Core per 4,000 devices

For more information on sizing requirements, see Implementation of SEG (Classic Platform) (Classic Platform) and Hardware, Software and Networking Requirements for SEG (V2 Platform) (V2 Platform).