Open cmd and type Cluster group "Cluster Group" /move
Also you can also specify the server to move the Active Manager
Type: Cluster group "Cluster Group" /Move:<<ServerName>>
2017年6月8日 星期四
2016年11月2日 星期三
Removing internal host names and IP addresses from message headers
Let’s take a look at what we’re talking about here. As a message makes its way from one server to another, it may be handled by more than one SMTP hosts. Each host adds a RECEIVED header at the beginning of message headers, leaving a trace of where the message has been and when (a timestamp).
Here are headers from a message received from Dell. (Unnecessary headers removed).
Received: from mailcluster.hkitzone.local (192.168.193.129) with Microsoft SMTP Server (TLS) id
15.0.1130.7 via Mailbox Transport; Mon, 18 Jul 2016 11:30:34 +0800
Received: from mailgw.hkitzone.hk (192.168.250.102) by
mailcluster.hkitzone.local (192.168.193.129) with Microsoft SMTP Server id
15.0.847.32; Mon, 18 Jul 2016 11:30:30 +0800
X-WSS-ID: 0OAHR2U-02-175-02
X-TMWD-IP-Reputation: SIP=104.47.41.108; IPRID=7469643D303030312E30413135303330312E35373843344435332E30303732; CTCLS=T2; CAT=Unknown
Received: from NAM03-DM3-obe.outbound.protection.outlook.com
(mail-dm3nam03on0108.outbound.protection.outlook.com [104.47.41.108]) (using
TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate
requested) by mailgw.hkitzone.hk with ESMTPS id
2E422D4E0AD; Mon, 18 Jul 2016 11:30:27 +0800 (HKT)
These headers can be used to determine the path taken by a message— useful information for troubleshooting and preventing message loops.
Here are headers from a message received from Dell. (Unnecessary headers removed).
Received: from mailcluster.hkitzone.local (192.168.193.129) with Microsoft SMTP Server (TLS) id
15.0.1130.7 via Mailbox Transport; Mon, 18 Jul 2016 11:30:34 +0800
Received: from mailgw.hkitzone.hk (192.168.250.102) by
mailcluster.hkitzone.local (192.168.193.129) with Microsoft SMTP Server id
15.0.847.32; Mon, 18 Jul 2016 11:30:30 +0800
X-WSS-ID: 0OAHR2U-02-175-02
X-TMWD-IP-Reputation: SIP=104.47.41.108; IPRID=7469643D303030312E30413135303330312E35373843344435332E30303732; CTCLS=T2; CAT=Unknown
Received: from NAM03-DM3-obe.outbound.protection.outlook.com
(mail-dm3nam03on0108.outbound.protection.outlook.com [104.47.41.108]) (using
TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate
requested) by mailgw.hkitzone.hk with ESMTPS id
2E422D4E0AD; Mon, 18 Jul 2016 11:30:27 +0800 (HKT)
These headers can be used to determine the path taken by a message— useful information for troubleshooting and preventing message loops.
How to remove Received headers in Exchange Server 2007/2010
Exchange 2007/2010 offers an easy way to accomplish this. If your transport server sends outbound email directly using DNS lookup, or delivers to a smarthost without authentication, simply remove the Ms-Exch-Send-Headers-Routing permission assigned to Anonymous Logon — that refers to anonymous users, as shown below:
Get-SendConnector “Connector Name” | Remove-ADPermission -AccessRight ExtendedRight -ExtendedRights ms-Exch-Send-Headers-Routing -user “NT AUTHORITY\Anonymous Logon”
訂閱:
文章 (Atom)