The NetTCPIP module isn't available on any OS before Server 2012, regardless of 
what version of WMF/PowerShell you install.

I don't understand what you mean by "of course the host name is also showing up 
on these IP addresses". If you don't want them to register in DNS, you can do 
that in the GUI. That's not what SkipAsSource is about.

If you are referring to the message header spit out by each transport, you 
change that with Exchange Management Shell. Set-ReceiveConnector and 
Set-SendConnector.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Kurt Buff
Sent: Saturday, June 18, 2016 5:30 PM
To: ntsysadm
Subject: [NTSysADM] 2008 R2 and SkipAsSource

All,

I've got an Exchange 2010 server running on 2008 R2 with multiple hub 
transports - but this isn't about Exchange as such.

I've separated the extra SMTP transports onto different IP addresses, but of 
course the host name is also showing up on these IP addresses, and I'd like to 
put a stop to that, as it's causing some confusion.

I've tried to use netsh to set SkipAsSource for the addresses used by the extra 
SMTP transports, and it's not working, including manually removing the 
addresses and re-adding them with netsh with the requisite options to set 
SkipAsSource.

I've tried to apply https://support.microsoft.com/en-us/kb/2386184
(x64 version, to match the OS), but during installation it says that it isn't 
applicable and exits. When I search for that hotfix
(get-hotfix) it doesn't show. The box is fully patched (except for this month's 
patches, which are coming next week).

The machine has PowerShell v2 on it, which doesn't support setting SkipAsSource.

So, two questions:

o- What am I missing to configure SkipAsSource on this machine?

o- What is the latest version of PowerShell that's safe to install with 
Exchange 2010, and would that work to set SkipAsSource?

Thanks,

Kurt


Reply via email to