Managed Services
- Server Installations, configurations & support.
- Internet/Intranet & E-mail Solutions on Networks.
- VPN Installation & Configuration.
- ADSL Solutions including remote access and working from Home.
- Wireless Network Solutions.
- mySQL Server Installation.
- SharePoint Services.
- E-mail Security Solutions.
- Backup Solutions & disaster recovery options.
- Client & Server Support including 24x7 Facility Management.
- Implement MS security hot fixes.
- Verify Anti virus definitions & live updates.
- Diagnosing possible hardware issues.
- Firewall / security check.
- Complete documentation of Network Configuration.
- Migration: Active Directory, Exchange Servers
Exchange Server 2003 , 2007 & 2010
Major changes from previous versions of Exchange Server include:
- The high availability options for Mailbox Databases (SCC: Single Copy Clustering, CCR: Clustered Continuous Replication and LCR: Local Continuous Replication) and site resiliency functionality (SCR: Standby Continuous Replication) have been replaced by Database Availability Groups (DAGs) in Exchange Server 2010. Major DAG benefits include providing database level high availability (as opposed to server level), support for up to sixteen (16) copies of each database, and flexible configuration (databases copies may be added / removed at will without requiring major server reconfiguration). Each server that runs the Enterprise edition of Exchange Server 2010 can host up to 100 database copies.
- High availability for the Client Access Server role in Exchange Server 2010 is provided by using Client Access Server (CAS) arrays. A CAS array can contain multiple Client Access Servers in an Active Directory site and provide a single name endpoint for client connections. CAS arrays cannot span multiple Active Directory sites.
- In Exchange Server 2007, a clustered mailbox server could not be combined with any other roles. In Exchange Server 2010, the Mailbox Server Role may be combined with the Client Access Server and/or Hub Transport roles, regardless of whether or not the mailbox server participates in a Database Availability Group.
- With the introduction of the RPC Client Access service, all Outlook clients access their mailbox database through the Client Access Server role. This abstraction layer allows for improved load balancing and redundancy and minimal client impact in the event of a database level switchover/failover event.
- Exchange Server 2010 extends the large mailbox support introduced in Exchange Server 2007, and also introduces a Personal Archive feature to allow messages to be retained longer without the need for a 3rd party archival system. The Personal Archive is implemented as a secondary mailbox for archive-enabled users, and in Exchange Server 2010 Service Pack 1, the Personal Archive may be located on a different database than the primary mailbox, which may reside on a different disk if desired.
- Administration delegation can now be performed at a very granular level due to Exchange Server 2010's implementation of Role Based Access Control (RBAC). Users and administrators can be given extremely fine grained abilities for functions provided both within the Exchange Management Console or Exchange Management Shell and in Outlook Web App. For example, a compliance officer may be given the ability to perform cross mailbox discovery searches within Outlook Web App; a help desk technician may be granted the ability to set an Out Of Office message for other employees within the company, or a branch administrator in a remote office may be granted the permission to perform specific Exchange Management Shell commands that pertain only to the Exchange server in their branch office.
- Distribution groups can now be "moderated", meaning that distribution groups can now be configured to allow users to join at will or only with a group moderator's permission, and individual messages sent to distribution groups can now be approved or denied by a moderator.
- Exchange Server 2010 introduces a transport concept called "Shadow Redundancy" which protects e-mail messages while they are in transit. If a Hub Transport server or an Edge Transport server fails after it has received a message for processing, but before it was able to deliver it to the next "hop" server, the server which sent the message to that transport server is now able to detect the failure and redeliver the message to a different Hub Transport or Edge Transport server for processing.
