Migrated from Exchange 2003 to Exchange 2010

I just migrated from Exchange 2003 to Exchange 2010.  I have 2 completely separate forrests that have a trust setup amongst them.  Each users mailbox is setup on exchange 2010 as a linked mailbox from the Exchange 2003 forrest where I have Server 2003 R2 AD domain.  The exchange 2010 domain is Server 2008 R2.  Currently all users accounts are housed in the Server 2003 but will be migrating them in the next couple of weeks.

There are a few issues I am running across.  The first one is people's cache contacts in outlook for what used to be the .nk2 file appears not to be working.  Not sure how to ge the nk2 file setup properly.

The second issue is the smtp relay or rather receive connectors.  I have a few canon copy machines and I am having issues with sending to pdf with the copy machines to external accounts.  It took me all day to get it working for internal users in the domain and the copy machines are not using any authentication cause I could not get it to work to with authentication.

But now I am unable to send to any external recipients.  The problem is that we have tenants in our suite who are alos able to use the canon copy machine to scan to pdf and it used to wrk fine with exchange 2003 but I cannot figure out what needs to be changed to amke sure that they can scan to pdf as well as not affecting anything else.  Here are the current screenshots for the current receive connectors.  I have 2 one for default connector and the other for client connector.

 Client Exchange General
 Client Exchange Network
 Client Exchange Authentication
 Client Exchange Permissions
 Default Exchange General
 Default Exchange Network
 Defaul Exchange Authentication
 Default Exchange Permissions
cmptrdrAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MegaNuk3Commented:
Use this article to setup a new Receive Connector the devices can use: http://exchangepedia.com/2007/01/exchange-server-2007-how-to-allow-relaying.html
0
davorinCommented:
And if you are using outlook 2010 now, use this one to import NK2 files:
http://support.microsoft.com/kb/980542
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MegaNuk3Commented:
What issue are you getting with the .nk2 files? Is it just that emailing an internal user from cache results in a NDR? If so, you have 2 options:
1.) clear the Nk2 file and let it rebuild
2.) add X500 email addreses to all your exchange 2010 mailboxes: http://blogs.technet.com/b/sbs/archive/2009/05/21/cannot-reply-to-old-emails-or-modify-old-calendar-items-after-pst-mail-migration.aspx
0
The Five Tenets of the Most Secure Backup

Data loss can hit a business in any number of ways. In reality, companies should expect to lose data at some point. The challenge is having a plan to recover from such an event.

cmptrdrAuthor Commented:
I had originally seen the link tha was mentioned but some of my concerns were what people said below and not sure what needs to be done in this instance as well as some of the commands do not seem to work 100%.  What do I do with my current receive connectors cause I am afraid to bring down the current exchange environment making these changes.

"As you know when a receive connector is created it is set to use \All Available IP address\ (in the network tab). If I leave this setting the way it is, will the two receive connectors conflict (because of the new bindings), or should I change the default receive connector from use \All Available IP address\ to \150.742.100.3\?
Reply
29 Bharat Suneja January 10, 2011 at 12:37 pm
Yes, you must change all Receive Connectors which use the same port number to be bound to specific IP addresses to avoid socket/binding conflicts.
If you have a Receive Connector that uses a different port number (e.g. 525), and it’s the only connector which uses that port, you can continue to use the All (“All available IP addresses… “) binding for it."

I took away everything that I had done in the link that you sent because I was afraid what it might do because of the above comments.  As well as the fact see attached screen shot with an error I received when following directions.

 Exchange Error
0
cmptrdrAuthor Commented:
I will have to check th .nk2 situation on Friday when I get back in the office.
0
MegaNuk3Commented:
Leave your existing receive connectors as is and add a new IP address to your server, then bind the new receive connector to that, then you don't have to worry about ports and conflicting with existing receive connectors...
0
cmptrdrAuthor Commented:
MegaNuk3 how do I add a new IP address to my server?  Then how do I bind the new receive connector to that.  I am very green and new with Exchange 2010.
0
cmptrdrAuthor Commented:
Also what about the error message that I was getting like something is wrong with the command.
0
MegaNuk3Commented:
Check the first article I posted it explains it all
0
cmptrdrAuthor Commented:
I don't understand the part of adding a new IP to my exchange hub server.  Do I need to physically get another Network card to add another IP to my exchange server.  Currently I have NIC teaming in place I could possible turn of the team but then I would be suseptible to failed NIC.  Also if my exchange has two IP's wouldnt that be confusing for DNS.  HOw would it know which IP to go to?
0
MegaNuk3Commented:
You just add an additional IP address to the existing NIC (Team) through TCPIP 4 properties...

You then setup the new Receive Connector to work on the new IP address and then configure anything you want to be able to relay to send to the new IP address.

The old receive connectors will not be affected by this and will still work. Does it matter which IP address people go to from DNS resolution? I don't think so.
0
cmptrdrAuthor Commented:
I had another resource that I went to assist with this issue and they provided me withe follwoing information that worked.  So what I did was created a new receive connector on the same NIC no new IP or anything.  I did this from the graphical interface.  Give it a name.  Under the network tab of the new receive connector leave all available IPV4 addre4sses in there and remove tje defaults for receive mail from remote servers that have these ip addresses and add the ip address of your copy machine.  In the authentication tab make sure only Transport Layer Security (TLS) is checked along with Externally Secured (fro example, with IPsec).  Those should be the only two checked in this connector.  In the permission groups only have Exchange servers checked and it worked properly
0
MegaNuk3Commented:
So are you saying that none of our comments were helpful or assisted in this solution? Most of the things you have mentioned are on that article I posted...
0
cmptrdrAuthor Commented:
IT was partiall correct the easiest and most direct was the otehr expert who worked with me on the issues.  I tried to go back and grant some points but it would not allow me to do so.  Also I like the graphical interface to do this it is much easier and there was no need for an additional IP address.  I could not understand the directions given but if I can give partial credit or award some points now I would do so but not sure how to do this.
0
MegaNuk3Commented:
Objecting so author can re-allocate points.
0
MegaNuk3Commented:
Thanks for some points anyway. You could of accepted your comment as the Accepted Solution and ours as the assisted ones though.
0
cmptrdrAuthor Commented:
I had another expert assist me with this question and was able to direct me through setting it up with much more ease than the article origianl posted.  I would say there is some good information in the first article but still kind of vague.  In one of the comment I posted it had the easiest and most straight forward way of doing it.  The .nk2 thing worked great.  So because it was not very easy through the command shell I am only giving a few points for that.

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.