Shared mailboxes and resource mailboxes, created as such, do not require a separate Exchange or Windows CAL. This is where things get nit-picky in Exchange licensing. If you were to convert them to standard (user) mailboxes, then they would require licenses.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bud Durland Sent: Tuesday, September 8, 2015 10:07 AM To: [email protected] Subject: RE: [Exchange] Pre-pre-planning an Exchange install Thanks for the guidance. Three forests because 2 years ago, each site was its own independent company; growth through acquisition. Forest consolidation is in the long-term plan, but we've not put any resources into it yet. We do indeed have Windows CAL for each user; some on-line stuff I've read implied that another was required. Divining the right answer about MS licensing often involves chicken bones and the phase of the moon, so I wasn't sure. One site makes HEAVY use of shared folders. I'll have to see if creating a mailbox for the sole purpose of sharing it requires a license. I do have some exposure that I know I have to cover for web-mail only users that do not currently access anything on the Windows servers. FWIW, Kerio can use its own user database, or authenticate against AD (or Linux PAM). We're currently transitioning everyone to AD authentication. We have HA configured in our VMWare environment, so may not have to do that for the Exchange install. Bud Durland Director of Information Technology 1 Plant St. Plattsburgh, NY 12901 Office: 518.561.1812 Direct: 518.324.4850 Cell: 518.726.0967 Weatherchem.com | Moldriteplastics.com | Stulltech.com -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Tuesday, September 08, 2015 9:30 AM To: [email protected] Subject: RE: [Exchange] Pre-pre-planning an Exchange install Each site has its own AD forest? How did THAT happen? :) Sounds painful to administer to me. You only need a single Exchange server for 400 users, as long as you have a good backup plan. The PA (preferred architecture) would recommend you have a minimum of two configured to use a Database availability group (DAG) for high availability (HA). But with good hardware, operational maturity, and good backups, that isn't very necessary unless you are a 24/7 environment. Don't you already have a Windows CAL for each user? There is no need to double them up. If you don't have a Windows CAL for each user, then you are already in violation and that shouldn't be charged to an Exchange migration project. :) Snap judgements here... long term I'd suggest you put together a plan for forest consolidation. A company with 400 people doesn't need 3 forests, unless you require a Chinese wall between the business units. Short term, install Exchange in the main location and then treat Exchange as if it were in a "resource forest" for the other two locations. Which is exactly how I presume you have Kerio installed. So a single server installation goes (no HA): 1 server (or VM) 1 Windows Server license 1 Exchange Server license 400 Exchange Server CAL A dual server installation goes (provides HA): 2 servers (or VMs) 2 Windows Server licenses 2 Exchange Server licenses 400 Exchange Server CAL Since a single license of Windows Server Standard provides for two Operating System Environments, you actually only need a single license in a VMware environment, even for HA. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Bud Durland Sent: Tuesday, September 8, 2015 8:38 AM To: [email protected] Subject: [Exchange] Pre-pre-planning an Exchange install Good Day; Our company is using Kerio Connect to deliver e-mail and groupware functionality. I have been asked to attach an `approximate´ number to the cost of switching to Exchange. We have about 400 users spread across three sites. The main site hosts the mail server, and has about half of the user base. The balance of the users are split over the other two sites. The sites are interconnected via VPN. The main site has 100MB fiber. One remote site has 10mb fiber, and the third is using `business´ cable. Each site has its own Active Directory infrastructure. It´s been a long time since I played in the Exchange arena, so I don´t know what the current requirements are. From what I´ve found on-line: - An exchange system has several roles to be fulfilled, requiring at least two, maybe three servers; one for the mailboxes, one for relaying mail to the internet, etc. These servers should not be doing anything else. We're in a VMWare environment, so we can adapt accordingly. - An Exchange server license for each server running some component of Exchange - An Exchange user CAL for each user - A windows CAL for each user (over and above the CALs I currently own) Some questions that come immediately to mind: I know that Exchange is intimately tied to AD. What is the best way to have one Exchange system servicing the three sites? - Migrate all site to a single domain? Obvious management benefits, but lots of labor and user disruption - Create a new forest to include the three AD domains? How well (if at all) will Exchange work with that? Would it be a good idea to have a mailbox server in each site? What are the pros and cons of that? Any advice, or pointers to non-marketing technical info would be much appreciated. Bud Durland Director of Information Technology 1 Plant St. Plattsburgh, NY 12901 Office: 518.561.1812 Direct: 518.324.4850 Cell: 518.726.0967 Weatherchem.com | Moldriteplastics.com | Stulltech.com NOTE -- This message contains legally privileged and confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Thank you. NOTE -- This message contains legally privileged and confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. Thank you.
