• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 353
  • Last Modified:

Exchange Management console issue

Hi
We have 6 Exchange Server in DAG environment. Service desk Engineer connected Exchnage console thorugh one of the terminal Server where Exchange Management tool is installed. When then connected by default it is conncted with one Exchnage Server where only database passive copies are there & during Mailbox user creation, they are error on auto load balacing , if not selected any specific Server ( Databases are splitted accross the mailbox Server). But when Exchange console connected with Active node by changing Seleted Server, its working fine. Everytime when SD Engineer connected with console , by defalt connect worng Server. How can I made it default Server where Mailbox cretaion is done properly.
0
padas6
Asked:
padas6
1 Solution
 
RadweldCommented:
By default Exchange console will connect to an Exchange server in the same AD site, if this Exchange server then becomes a copy server then this situation occurs because the information for the default server is stored in your user profile and is not dynamically updated.

The following blog should assist you.

http://lyncdup.com/2011/11/exchange-management-console-pointing-to-wrong-server-the-attempt-to-connect-to-httpserver-domain-compowershell-using-kerberos-authentication-failed/
0
 
padas6Author Commented:
Link is useful.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now