Exchange Server 2007Comments (0)

Comments

You need sign in to comment! Sign up today!

Disabling IPv6 On Exchange 2007Comments (0)

Before you install Exchange 2013, you might need to disable IPv6 on some of your Exchange 2007 servers. Some connections between Exchange 2007 and Exchange 2013 don't work correctly when IPv6 is enabled and an Exchange 2007 server has both the Mailbox and Client Access server roles installed.

If you have Exchange 2007 servers that have both the Mailbox and Client Access server roles installed disable IPv6 by doing the following:

1. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\
2. If the DisabledComponents entry doesn’t exist, do the following to create it:
3. In the Edit menu, click New, and then click DWORD (32-bit) Value.
4. Type DisabledComponents and then press enter.
5. Double-click DisabledComponents.
6. In the Value data field, enter 0xFFFFFFFF

Alternatively, if you want to automate this, you can use something like the following.

To Set The DisabledComponents Registry Key:
Reg.exe Add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /T REG_DWORD /V DisabledComponents /D "0xFFFFFFFF"

To Check For The DisabledComponents Registry Key:
Reg.exe Query HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters /V DisabledComponents

Comments

You need sign in to comment! Sign up today!

Creating a Cluster Continuous Replication on Windows Server 2003Comments (0)

This topic describes how to successfully install and configure a CCR for Exchange Server 2007.

Pre-Installation:
When using the RTM version of Exchange 2007 with the MNS quorum with file share witness and Windows Server 2003 SP1, you must install a hotfix on each node prior to deploying CCR. The hotfix is described in KB921181.

Forming the cluster:
These procedures can be performed locally on the physical node or remotely. However, it is recommend that you perform these procedures on the node that will be the first node in the cluster.

It is also recommended to create a CNAME for the server that hosts the File Share Whiteness share. This share should be placed on a Hub Transport Server.

To add the first node do the following:
1. Open the Command Prompt and type: Cluster /create /wizard
2. The New Server Cluster wizard appears, click Next
3. In the Domain field, select the correct domain, in the Cluster name field, enter a unique name for the cluster (max 15 characters), click Next
4. On the Select Computer page, verify or type the name of the server that you plan to use. Click Advanced, and select Advanced (minimum) configuration, click Ok. Click Next
5. On the Analyzing Configuration page, the wizard analyzes the domain and the node for possible issues that can cause installation problems. Click Next
6. On the IP Address page, type the unique, valid cluster IP address and then click Next. The wizard automatically associates the cluster IP address with the public network by using the subnet mask to select the correct network. The cluster IP address should be used for administrative purposes only and not for client connections.
7. On the Cluster Service Account page, type the username and password for the Cluster Service account for example ExClusterUser, select the correct domain and then click Next
8. On the Proposed Cluster Configuration page, click Quorum. Select Majority Node Set from the drop-down box. Click Ok, and then click Next
9. On the Creating the Cluster page, review any warnings or errors, click Next
10. Click Finish

To add the second node do the following:
1. Open the Command Prompt and type: Cluster ExCluster /add /wizard
2. After the Add Nodes wizard appears, click Next
3. In the Domain list, select the correct domain, click Next
4. In the Computer name field, type the name of the node that you want to add to the cluster, click Add and then click Next
5. After the wizard has analyzed the configuration, click Next
6. In the Password field of the Cluster Service Account page, type the password for the Cluster service account, click Next
7. On the Proposed Cluster Configuration page, review the configuration settings and then click Next
8. After the second node is added to the cluster, click Next
9. Click Finish

To create and secure the file share for the file share witness:
1. Open the Command Prompt and type: mkdir MNS_FSW_DIR_E2K7CCR, this is the directory that the cluser will use
2. Create the share by typing: FSW=C:\MNS_FSW_DIR_E2K7CCR /GRANT:ExClusterUser, FULL
3. Assign permissions by typing: cacls C:\MNS_FSW_DIR_E2K7CCR /G BUILTIN\Administrators:F ExCluserUser:F
4. Logon to with the ExClusterUser and verify that the share is accessible from the first cluster node.

To configure the MNS quorum to use the file share witness:
1. Open the Command Prompt and type: Cluster ExCluster res “Majority Node Set” /priv MNSFileShare=\\FSW\MNS_FSW_E2K7CCR
2. A warning message appears, this indicates that the resource must be restarted to have effect.
3. To restart the resource type: Cluster ExCluster group “Cluster Group” /move
4. To check the value of the file share property type: Cluster ExCluster res “Majority Node Set” /priv

Comments

You need sign in to comment! Sign up today!

Cluster Continuous Replication Recovery BehaviorComments (0)

This topic descripes the expected recovery actions for a variety of failures.

Operating System stop, error or hang:
Automatically failover

Total storage failure:
No action is taken - Manual failover

Data center failure:
Automatically failover

Operating system driver fails:
No action unless operating system fails

Operating system drive out of space:
Automatically failover

Complete failure of the cluster’s public network:
No action is taken

Loss of cluster quorum:
No action is taken

Information store failure:
Automatic restart of Information store resource. If the Information store resource failure is during a restart, a failover is triggered

Application (binary files) drive failure:
No action is taken

Application (binary files) drive out of space:
No action is taken

Complete loss of database or storage group, or database complete failure:
Automatic attempt to remount the affected databases. If this attempt fails, the database remains in a failed state, but no failover of the clustered mailbox server occurs

Partial failure of storage group or database:
No action is taken

Corrupted log detected for storage group:
No automatic recovery action. The copy goes into a broken condition and must be reseeded

Database or transaction log drive out of space:
No automatic recovery action. The databases in the storage group are dismounted.

Comments

You need sign in to comment! Sign up today!

Exchange 2007 Receive-ConnectorsComments (0)

There are two default receive connectors after a successful installation.
- Default Receive Connector
- Client Receive Connector

The Default Receive Connector listens on port 25 and accepts incoming mail from authenticated senders/hosts. It’s configured to accept mail from Mailbox Servers, other Hub Transport servers, and Edge Transport servers.
The Client Receive Connector listens on port 587 for POP and IMAP requests.

To make the Default Receive Connector accept incoming mail from Internet or if you have created a new Receive Connector called “Inbound” you must make it accept anonymous requests. This is done trough EMS with the command:
Set-ReceiveConnector -identity “Inbound” -PermissionGroups AnonymousUsers

Comments

You need sign in to comment! Sign up today!

How to Import 3rd party certificate in Exchange 2007Comments (0)

After you have created and requested the certificate you will be receiving a certificate file from your vendor.

To import it onto Exchange, start a EMS and type the following:
Import-ExchangeCertificate -Path C:\Name_of_Cert | Enable-ExchangeCertificate -Services “IIS, POP, IMAP, SMTP”

To see the certificates installed, type:
Get-ExchangeCertificate

You can now see the certificates with thumbprints and it’s services currently enabled.

To get more information type:
Get-ExchangeCertificate | fl

Comments

You need sign in to comment! Sign up today!

SAN Certificate Request using Exchange Management ShellComments (0)

If you want to request a SAN certificate you have to use the EMS to create the requestfile.

Fire up Exchange Management Shell:
New-ExchangeCertificate -GenerateRequest -Path c:\SANCertRequest.csr -KeySize 2048 -SubjectName “c=Country, s=State, l=City, o=CompanyName, ou=Department, cn=webmail.company.com” -DomainName webmail.company.com, autodiscover.company.com, ex-cas01.company.com -PrivateKeyExportable $True

Comments

You need sign in to comment! Sign up today!