Link to home
Start Free TrialLog in
Avatar of qosd
qosdFlag for United Kingdom of Great Britain and Northern Ireland

asked on

SBS 2003 exchange server moving too exchange 2003 std. interim forwarding of email to new exchange server

I have SBS 2003 server. (which the company has out grown 75+ users)
Moving to 2003 std server with exchange.
During an interim period I need to forward any emails to users I have moved onto new server.
The domain name <name.co.uk> for email recides on both servers as I move people across. I have removed the email account from the SBS server before adding them to new server.
Logistically I can't move everyone at the same time.

My problem is emails are not forwarding to new server.
Any ideas?
Avatar of Matthew Millers
Matthew Millers
Flag of Australia image

Are these in different exchange orgs?
Avatar of qosd

ASKER

They are totally diffent domains/organisations SBS can not have 2 exchange boxes
I assume you are not concerned about GAL syncing or free/busy over the orgs?

Create a temporary SMTP namespace in the new org.
If you have existing users in the old org, configure a forwarder in the AD object to a contact you have created representing the user in the new org using the new SMTP namespace.

If you are removing the users from the source org, create contacts to represent the users in the new org with the temp SMTP address, add a secondary proxy address for your live domain.
OK
All works in my case is
Create a new mail contact on new server and a contact as well which is pointing to the usermailbox on other server .
then on other server(old)create a distribution group to receive that email ...
Simple it work in my case
also if you are using pop mail you need to set forwarding rules to that distrubution group to the user mailbox
cheers
Are you using a different name space for that? Are you you routing the mail?
Well
if he got the different domain then he need to
Avatar of qosd

ASKER

I have as far as the world is cocerned 2 totally seperate domains. The server are in the same room. Same IP range.

"Vishal impact" you seem to be going down the correct way, routing is required.

I have tried the following.

Forwarding all email with unknown addresses. This does send alot of junk mail about
I need to send email back to the old server, this seems to work as it goes out and back in on the DNS for domain, sometimes. I use the old server as smart host for delivery and allow relay from ip address.
Due to the domain having a registration in new server it fails on sending due to unknown user.


I thought they were sharing the same namespace "name.co.uk"?

If they are completely different namespaces, just configure a contact in the old domain, then configure the user objects in AD to forward to this.
Avatar of qosd

ASKER

I am, the domains I am talking about are local active directory domains one of which is a SBS which will not allow any trusts what so ever.
OK
wat we did when we migrate server was took the pilot approach which is what we are talking about here as well in terms of migrating process this is called pilot approach if all knows and agree right.
SO say you have domain abc.com on new server and xyz on old server then :
what you need is to create a mail contact on server xyz.com which is forwarding that particular users mail to abc.com i.e good_smith@abc.com then on new server abc.com side create users good_smiths mailbox and a distribution group which will forward the mail coming from xyz.com to the users mailbox make the user good_smith as memeber of the distro group.
Now you need to setup the routing rules as emails coming in from the domain xyz dont know where to look for your users mailbox so this is the reason mail are getting failed to overcome this create a routing rule on mail connector i.e if you have pop mail connector create routing rule in that with distribution group and users mail address good_smith@xyz.com SO now ur done all emails looking for good_smith@xyz.com will go to the distribution goup and then from there finally to the users mailbox
cheers mate
hope this rings any bells to accept my solution
this works for sure so dont worry
Ok, this is the problem, if you are sharing SMTP name spaces, this means that both exchange orgs are authorative.

Have a look at post ID 20831094
Create a secondary name space (it can be anything - temp.local)
Create a SMTP connector with that namespace

Follow the rest of the post and you will be fine.

Matte
i dont think so there is any need to create new smtp connector as user is using smarthost on oneside for realy if i am not wrong
Creating more smtp though gives reudancy load balance on network but at this stage i wont suggest it as its still just a trial more ones the network is totally setteled doen then you can create another smtp connector
The reason why i say create a new SMTP connector is so you dont need to make any DNS changes (for MX lookups), and you can specify the smarthost for the temp namespace in the connector.

Having done this many times before, it is the simplest way to fulfill the posters requirements.
ASKER CERTIFIED SOLUTION
Avatar of vishal_impact
vishal_impact
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
If you are using a shared address space....
What did you end up doing? And how?
hi mattee
can you please be brief so i can explain
it