Hi, I am facing one problem with my Exchange 2010 public folders. When any user try to access PF it asks for login credentials in Ms Outlook. But for authentication its going on our old server which is not running now. From OWA also it is not accessible. Last year we have migrated from Exchange 2003 to Exchange 2010. We have singel exchange server running. Please help me out. Login prompt should be redirected to our new Exchange 2010 server. Thanks in advance..

Ensure that the correct public folder store is set on the properties of the mailbox database. Was the Exchange 2003 server removed correctly following the Microsoft guide on the process? Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Thank you for your quick reply Simon.. Exchange 2003 is not demoted yet.. its powerd off permanently.. we have assigned another network card to our Exchange 2010 server with old exchange 2003 server's ip address..and created dns entry with the same old server name into our dns server. can you please tell where i can get mailbox database properties? -Raj-MRaj-M

What do you mean "demoted"? Was the Exchange 2003 server also a domain controller? You can't just turn an Exchange server off and expect things to work - you need to remove Exchange correctly. If the server was a domain controller as well then that is going to cause problems, because Exchange will be trying to use that server. It sounds to me like the removal of Exchange 2003 wasn't completed correctly and that is the cause of the problems. Mailbox Database properties, right click on the database and choose Properties. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Yes.. Exchange 2003 was additional DC.. But some other PF which were on old server are accessible.!Raj-M

The point is - the state you are currently in, I wouldn't expect anything to work. Your migration is not complete - Exchange will still think the old server is there and will attempt to use it. Is the original server still available and can be turned on? If not, but nothing has been done to it, then I would be looking to recover it in to a new build so that the migration can be completed successfully. There are no shortcuts to a successful migration - simply turning the server off doesn't complete things. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

The point is - the state you are currently in, I wouldn't expect anything to work. Your migration is not complete - Exchange will still think the old server is there and will attempt to use it. Is the original server still available and can be turned on? If not, but nothing has been done to it, then I would be looking to recover it in to a new build so that the migration can be completed successfully. There are no shortcuts to a successful migration - simply turning the server off doesn't complete things. Simon. Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

creating a DNS record for your old 2003 server and pointing to 2010 server doesn't help. If some content is stil on 2003 and not on 2010 wont help. If you can, put the server back on (2003) and then move exch to another server any other roles it's perform, then demote the server. Sukh

creating a DNS record for your old 2003 server and pointing to 2010 server doesn't help. If some content is stil on 2003 and not on 2010 wont help. If you can, put the server back on (2003) and then move exch to another server any other roles it's perform, then demote the server. Sukh

You can follow this article for removing your last 2003 server http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/removing-last-exchange-2003-server-exchange-2007-part1.html Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82