![]() ![]() ![]() With Exchange 2013, asking for the server name makes no sense since effectively this is not what is required. Quite obviously the Profile creation dialog is no longer fit for purpose. The fact that every mailbox has a unique opaque GUID should really tell you how stupid the situation is. Every mailbox has a unique GUID and you can get this by running this cmdlet at the Exchange Shell: Note how the Server name changes to something in the format and Close the Profile configuration Wizard.īasically the GUID shown in step 13 is the Mailbox GUID. You may now click on Check Name this will now resolve the Mailbox without problems. Like that we can have a more complete resource to refer to.Ĭlick OK and OK to go back to the server settings. If you are one of them please share your solutions. I will also tell you straight away that I saw posts complaining that the procedure I am presenting here does not work. Since I see others posting questions on this issue I hope this will help them. I collected bits and pieces of info from the forums, found what works for me and here it is. I will admit with you I did not thoroughly research every detail. ![]() So here I put together my procedure of how I am creating profiles now. You go to the Outlook Profile dialog and suddenly this refuses to create a profile complaining about Outlook connectivity. When running Exchange 2013, on manually creating an Outlook profile, you discover things have changed. We clicked a little button that resolved these details and went ahead to open Outlook and access our mailbox. Once upon a time we created Outlook profiles by simply filling a server name and a mailbox user name. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |