Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

E2K7 Transportconfig - remove internalsmtpserver IP address

199 views
Skip to first unread message

VID-DB

unread,
Nov 7, 2007, 1:30:00 PM11/7/07
to
Is there any way to remove an old\invalid IP address that has been added in
as an "internalsmtpserver" using the set-transportconfig -internalsmtpservers
cmdlet?

I need to be able to remove an IP address that has been replaced.

Also what is the proper syntax to add a range of IP addresses using the
"Set-TransportConfig -internalsmtpservers" cmdlet? For future reference,
how would you remove\adjust the range once added?
--
Don B.


Bharat Suneja [MVP]

unread,
Nov 8, 2007, 10:19:34 AM11/8/07
to
Using the shell, get-transportconfig | select internalsmtpservers.
Copy the existing ip addresses
Add them again using:
set-transportconfig -internalsmtpservers 1.2.3.4,1.2.3.5,1.2.3.6

SP1 allows you to do this using the EMC.
--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"VID-DB" <V...@nospam.nospam> wrote in message
news:62E03E3D-CCF3-4997...@microsoft.com...

VID-DB

unread,
Nov 8, 2007, 10:45:01 AM11/8/07
to
Thank you Bharat,

While I was waiting for a response, I discovered that process of just
reposting all of the current correct IP's again using the set command using
trial and error. While this works, it does not seem like the ideal solution
if you happen to have a lot of IP addresses listed individually since you
would need to re-enter all but the incorrect entry. (Copy/Paste is our
Friend) I hope Microsoft will adjust this in someway.

Is there a syntax to enter a range of addresses rather than just individual
IP's?
I.e. I want to add a range of internal smtp servers with 192.168.0.2
through 192.168.0.15 AND 192.168.0.45 AND 192.168.0.50

I can't find any samples in Microsoft documentation other than individual IP
addresses

Anxiously awaiting SP1 for many reasons!
--
Don B.

0 new messages