PC deki RAM miktari ne kadardir?

DC ile Exchange 2007 ayni Server'dami?

Exchange 2007'nin son roolup ve SP'si yuklu mu?

Neden IPv6 sorusunun cevabi ise, exchange 2007 icerisindeki bazi bilesenlere IPv6 desteginin sunulmasi olarak aciklanabilir, ornegin bir transport rule yaratilmasi esnasinda IPv6 ya gore rule yaratabiliyorsunuz. Tum liste asagidaki gibi:

http://technet.microsoft.com/en-us/library/bb629624(EXCHG.80).aspx

Exchange 2007 SP1 and SP2 components that are directly affected by IPv6
Source Feature IPv6 supported? Comments
Transport
IP Allow List and IP Block List
Yes
For more information about the IP Allow list, see How to Add IP Addresses to the IP Allow List and IP Block List.

Transport
IP Allow List providers and IP Block List providers
No
Currently, there is no widely accepted industry standard protocol for looking up IPv6 addresses. Most IP Block List providers do not support IPv6 addresses. Therefore, if you allow anonymous connections from unknown IPv6 addresses on a Receive connector, you increase the risk that spammers will bypass IP Block List providers and successfully deliver spam into your organization.

For more information about the IP Block list providers, see How to Configure IP Allow List and IP Block List Providers.

Transport
Sender reputation
No
The Protocol Analysis agent does not compute the sender reputation level (SRL) for messages that originate from IPv6 senders. For more information about sender reputation, see Sender Reputation.

Transport
Sender ID
Yes
For more information, see Sender ID.

Transport
Receive connectors
Yes
IPv6 addresses are accepted for the following components:

Local IP address bindings

Remote IP addresses and IP address ranges

We strongly recommend against configuring Receive connectors to accept anonymous connections from unknown IPv6 addresses. If your organization must receive mail from senders who use IPv6 addresses, create a dedicated Receive connector that restricts the remote IP addresses to the specific IPv6 addresses that those senders use.

For more information, see Receive Connectors.

Transport
Send connectors
Yes
IPv6 addresses are accepted for the following components:

Smart host IP addresses

The SourceIPAddress parameter for Send connectors that are configured on Edge Transport servers
Note:
If you want to specify an IPv6 address for the SourceIPAddress parameter, make sure that the appropriate DNS AAAA and MX records are configured correctly. This helps ensure message delivery if a remote messaging server tries any kind of reverse look-up test on the specified IPv6 address.
For more information, see Send Connectors.

Transport
Incoming message rate limits
Partial
Incoming message rate limits that you can set on a Receive connector, such as MaxInboundConnectionPercentagePerSource parameter, the MaxInboundConnectionPerSource parameter, and the TarpitInterval parameter only apply to global IPv6 address. Link local IPv6 addresses and site local IPv6 addresses are not affected by any specified incoming message rate limits. For more information about incoming message rate limits, see Managing Message Throttling.

Unified Messaging
All features
No
Unified Messaging doesn't support IPv6 in any version of Exchange 2007. For more information, see Unified Messaging.

High Availability
IPv6 addresses
Yes
Static IPv6 addresses are supported by Windows Server 2008 and the Microsoft Windows Cluster service. However, using static IPv6 addresses goes against best practices. Therefore, Exchange 2007 SP1 and SP2 on Windows Server 2008 doesn't support configuring static IPv6 addresses during setup.

Failover clusters support Intrasite Automatic Tunneling Addressing Protocol (ISATAP). They support only IPv6 addresses that allow for dynamic registration in DNS. Therefore, link local addresses can't be used in a cluster.

For more information, see New High Availability Features in Exchange 2007 SP1.

Outlook Anywhere
DSProxy component
No
When a client that is using Outlook Anywhere tries to connect to Exchange 2007 SP1 and SP2 running on Windows Server 2008, the client cannot connect. This happens because the RPCProxy component on the Client Access server that is running under Windows Server 2008 cannot connect through port 6004 to the DSProxy component on the Exchange Mailbox server.

For more information, see Outlook Anywhere Client Connectivity Issue Because of TCP/IPv6