http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4

Exchange Server 2007 용량 산정 (사이징)

Mailbox Role
Factors
- Number of mailboxes
- Mailbox average size
- User profiles
- Security/auditing mechanisms
- Use of mobile devices (Blackberry included)
- Outlook mode (online/cached)
- Archiving/Messaging Record Management
- High Availability Model (CCR, LCR, SCR)
- Cache Warming

사용자 유형 카테고리

CPU
1 processor core for every 1,000 light/medium user mailboxes
1 processor core for every 500 heavy user mailboxes
8 cores maximum

Memory
2GB + 2 ~ 5MB/mailbox (위 사용자 유형에 따라)
32GB maximum 권장 (32GB 이상은 비용 문제 발생)
최소 메모리는 다음 표와 같이 저장소 그룹의 개수에 따라 달라진다.

Network
1 x Gbit minimum
With CCR use separate NICs for public and private networks

Disk
Use the Exchange 2007 Mailbox Server Role Storage Requirements Calculator.
또는 다음 항목 고려
- Balance I/O performance and Capacity
- Add 5% onto database LUN size for Content Indexing
- Add 10% onto database LUN size for Overhead / white space
- The default Deleted Items retention period (14 days) adds up to 30% in the database LUN
- Take SLA factors into account (database recovery time, backup window, etc.)
- Target for 100GB of maximum database size


HUB Transport Role
Factors
- Mail queue stored in JET database
- CCR (Transport Dumpster)
- Message rate
- Message tracking
- Average message size
- Number of enabled transport agents
- Antivirus and third-party applications
- Journaling

CPU
소규모 조직의 경우 1개 또는 2개의 코어 필요
중/대규모의 경우 다음 표 참고

Network
Gbit Recommended


CAS Role
Factors
- Non-MAPI 클라이언트의 수 (CAS 서버에서 메시지 변환 작업 발생)
- OWA rendering
- Enabled services
> IMAP, POP3
> Outlook Anywhere
> Exchange ActiveSync
- Web services
> AutoDiscover
> Availability
> OOF
- OAB distribution

CPU
Up to 4 cores
1 : 4 CAS : Mailbox cores

Memory
2GB/core
16GB Maximum

Disk
특별한 요구 사항 없음

Network
Gbit recommended


Edge Transport Role
Factors
- Message rate
- Average message size
- Number of enabled transport agents
- A/V and A/S
- SMTP Connections
- Percentage of malware

CPU
2 processor cores recommended
Up to 4 cores

Memory
2GB minimum, 16GB maximum
1GB/core

Disk
Capacity = (average message size x maximum queue) + Logs
Transport rules and message rate influence the IOPS needed
Back Pressure:
- RTM: 최소 4GB 여유 공간
- SP1: 최소 500 MB 여유 공간

Network
2 x Gbit recommended (1 in, 1 out)


Active Directory / Global Catalogs

Set-Mailbox -Identity <MailboxIdParameter> -Languages  <languagecode>
예)Set-Mailbox -Identity administrator -Languages  ko-kr
 
Languages 매개 변수는 기본 설정 순서대로 이 사서함의 언어 기본 설정을 지정합니다.
해당 언어가 지원되는 경우 여러 Exchange 구성 요소에서 기본 설정 언어로 사서함 사용자에게 정보를 표시합니다.
이러한 구성 요소 중에는 할당량 메시지, NDR(배달 실패 보고서), Microsoft Outlook Web Access 사용자 인터페이스 및 UM(통합 메시징) 음성 안내가 포함됩니다.

참고 사이트 (MS Technet)
http://technet.microsoft.com/ko-kr/library/bb123981.aspx

Exchange 관리 셸을 사용하여 Outlook Web Access의 로그온 및 오류 언어 설정을 구성하려면 다음을 수행합니다.
Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -LogonAndErrorLanguage <language code>

Exchange 관리 셸을 사용하여 Outlook Web Access 가상 디렉터리의 기본 클라이언트 언어 설정을 구성하려면 다음을 수행합니다.
Set-OwaVirtualDirectory -identity "Owa (Default Web Site)" -DefaultClientLangugage <language code>

Exchange 관리 셸을 사용하여 개별 사서함의 클라이언트 언어 설정을 구성하려면 다음을 수행합니다.
Set-Mailbox –identity <mailbox identity> -languages <language code>

I see a lot of memory related Exchange Server 2007 questions in the Exchange 2007 forum on the MSExchange.org boards, so this month my plan was to talk about what has changed in regards to memory utilization in Exchange Server 2007 compared to previous versions of Exchange Server. As most of you remember, because Exchange Server 2003 was based on 32-bit architecture, this version of Exchange Server was limited to using a maximum of 4GB of memory. Because Exchange Server 2007 is based on 64-bit architecture, this limitation is no longer there. In fact Exchange Server 2007 has much better memory utilization than Exchange Server 2003 had, and is capable of using 32 GB of memory and more. Personally, I have deployed Exchange 2007 Mailbox servers with 16 GB of memory installed, and I have seen Store.exe processes grow as large as to approximately 14 GB in size!
These memory utilization changes are excellent for large enterprise IT organizations, but several of the smaller organizations with a relatively small amount of mailbox-enabled users (between 10-30) and an Exchange 2007 Mailbox server with let us say 4 GB of memory often seem to experience problems with excessive memory utilization. Several Exchange administrators report that their Exchange 2007 Mailbox server uses more memory than the amount of physical memory installed in the server. This means that the server can become sluggish and unresponsive.
With Exchange Server 2003, the store process was bound to a certain memory cache limit. The upper bounds of this limit were typically set at around 900MB. With Exchange Server 2007 which uses 64-bit architecture, the limit on database cache size is no longer present. Currently, the default minimum cache size for Exchange 2007 is 512MB (for machines with at least 2GB RAM), and there is no maximum value set, which means that ESE (store.exe) will grow the cache to consume almost all available RAM on the server if there is no other memory pressure on the system. A larger database cache size typically results in greatly reduced disk I/O as reading information from memory is much faster than reading information from disk. If memory pressure occurs, that is other applications request/require memory, ESE will appropriately shrink the size of the database cache automatically.
Okay, I hear you say, that was a good explanation, but unfortunately this is not the behavior I experience in my environment. So, what can I do if my Exchange 2007 server is sluggish and unresponsive? Although generally not recommended by Microsoft, there is one thing you can do. You can set a limit on the ESE database memory cache. This is done by following the below steps:

Warning!
Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your Operating System. Neither MSExchange.org nor Microsoft can guarantee that these problems can be solved. Modify the registry at your own risk!

· Start ADSI Edit by clicking Start > Run and typing ADSIEDIT.MSC
· Open the following object: Configuration > Services > Microsoft Exchange > Exchange organization > AdministrativeGroups > Your administrative group > Servers > Server name > Information Store
· Right-click the Information Store, and then click Properties.
· Under the list of Attributes, scroll down and select msExchESEParamCacheSizeMax

Note
The msExchESEParamCacheSizeMax parameter controls the ESE buffer size. Its value is expressed as a page count, and must be set to an exact multiple of 8192 for maximum efficiency. If this value is not met, the cache size is rounded up to the next 32-MB boundary when virtual memory is allocated. If this value is incorrectly set, memory may be wasted.

Exchange에서는 메시지 크기 제한 설정을 하는 부분이 3군데이다.
1. 사용자별 설정
2. Transport Config 설정
3. 송신 커넥터와 수신 커넥터에서 설정

기본적으로 새 계정을 만들게 되면 제한 설정은 제한 없는 상태이다.
그리고, Transport Config도 없는 상태이다.

세번째, 커넥터 쪽이 문제이다.
기본적으로 커넥터를 만들게 되면 기본 값이 10MB가 된다. (송수신 각각 10MB)
GUI 로 는 확인이 불가능하고, 수정 또한 불가능 하므로 Shell을 사용해야 한다.

Shell에서 아래와 같이 입력을 해 보면 현재 설정 값을 알 수 있다.
Get-SendConnector | Select identity, Maxmessagesize
Get-ReceiveConnector | Select identity, Maxmessagesize

10MB로 제한되어 있는 것이 확인된다면 아래와 같이 입력하여 설정값을 수정한다.

Set-SendConnector "커넥터 이름" -MaxMessageSize 용량
예)  Set-SendConnector "Connector Name" -MaxMessageSize 50MB

Set-ReceiveConnector "커넥터 이름" -MaxMessageSize 용량
예) Set-SendConnector "Connector Name" -MaxMessageSize 50MB

Edge 서버가 있을 경우 Edge 서버에서도 설정해 주어야 한다.

http://technet.microsoft.com/ko-kr/library/bb124345.aspx

사용자가 자동 로그인을 시도하면 다음과 같은 순서로 DNS를 쿼리한다.

1. _sipinternaltls._tcp.<domain> - 내부 TLS 연결(포트 : 5061)
2. _sipinternal._tcp.<domain> - 내부 TCP 연결(포트 : 5060)
3. _sip._tls.<domain> - 외부 TLS 연결(포트 : 443)
4. _sip._tcp.<domain> - 외부 TCP 연결(포트 : 443)



추가 기능에 대한 필요 서버

Edge 서버

인증서 요구 사항

사용 포트

Outlook.exe /<Parameter>

/c messageclass
Creates a new item of the specified message class, works for any valid MAPI form.
For example:
/c ipm.activity creates a Journal entry
/c ipm.appointment creates an appointment
/c ipm.contact creates a contact
/c ipm.note creates an e-mail message
/c ipm.stickynote creates a note
/c ipm.task creates a task

/CleanClientRules
Starts Outlook and deletes client-based rules. For non-Exchange users.

/CleanFinders
Sets Outlook 2003 Search Folders back to the default state (deletes custom Search Folders)

/CleanFreeBusy
Cleans and regenerates free/busy information.

/CleanProfile
Removes invalid profile keys and recreates default registry keys where applicable.

/Cleanpst
Launches Outlook with a clean Personal Folders file (.pst)

/CleanReminders
Cleans and regenerates reminders.

/CleanRules
Starts Outlook and deletes client- and server-based rules.

/CleanSchedPlus
Deletes all Schedule+ data (free/busy, permissions, and .cal file) from the server.

/CleanServerRules
Starts Outlook and deletes server-based rules. Used only with Exchange server accounts.

/CleanViews
Restores default views.

/FirstRun
Starts Outlook as if it were run for the first time.

/ImportPrf prffilename
Launches Outlook and opens/imports the defined MAPI profile (*.prf). If Outlook is already open, queues the profile to be imported on the next clean launch.

/Profile profilename
Loads the specified profile. If your profile name contains a space, enclose the profile name in quotation marks.

/ResetFolderNames  (시스템 폴더 이름 변경 - 받은 편지함(inbox) 등)
Resets the language of the default folders to the language of the Outlook client.

/ResetFolders
Restores missing folders for the default delivery location.

/ResetOutlookBar
Rebuilds the Outlook Bar.

/ResetWunderBar
Rebuilds the new Outlook Control Bar in Outlook 2003.

/Rpcdiag
Opens Outlook and displays the remote procedure call (RPC) connection status dialog.

/Sniff
Starts Outlook and forces a detection of new meeting requests in the Inbox, and then adds them to the calendar.

Exchange Server 2003의 경우

받은 편지함
https://<ServerName>/exchange/<UserName>/?cmd=loadmodule&module=inbox

일정
https://<ServerName>/exchange/<UserName>/?cmd=loadmodule&module=calendar

연락처
https://<ServerName>/exchange/<UserName>/?cmd=loadmodule&module=contacts

작업
https://<ServerName>/exchange/<UserName>/?cmd=loadmodule&module=tasks


Exchange Server 2007의 경우

받은 편지함
https://<ServerName>/owa/<UserSMTPAddress>/?cmd=contents&module=Inbox

일정
https://<ServerName>/owa/<UserSMTPAddress>/?cmd=contents&module=calendar

연락처
https://<ServerName>/owa/<UserSMTPAddress>/?cmd=contents&module=contacts

작업
https://<ServerName>/owa/<UserSMTPAddress>/?cmd=contents&module=tasks

(<UserSMTPAddress>를 지정하지 않으면 인증된 사용자의 기본 사서함이 열린다.)