Why not simply have the other admin undo what [s?]he knowingly did? Once settings/functionality is restored, have a conversation with the other admin that addresses their concerns and whether or not they can accomplished without breaking functionality, or if another approach is more appropriate.
-- Espi On Tue, Sep 1, 2015 at 2:56 PM, D R <[email protected]> wrote: > Help, please..... > > This is what we have. > > Someone, not me, went in and made some modifications to the Exchange > Server via the EAC. Now, things are munged up. :( > > 1. Autodiscover is not working. > 2. The EAC shows a 404 error > 3. Users cannot share their Calendars. > > First one: When attempting to connect a phone/tablet to our Exchange > Server, from the outside, Autodiscover will not work. BUT, I can connect > via imap.(imap.server name.com) So, everyone is still able to get to > their email outside the organization. > > Second issue: When I attempt to open the EAC, I do get the login name and > password. But, as soon as I enter the credentials a window appears and it > has iexplorer a the top and my URL changes from the http://localhost/ecp > to http://localhost/owa/authentication. I enter the same credentials and > then I get a 404 error on the web page. > > Third issue: When the first two issue happened, then the users started to > report that they couldn't share their calendars, when they were able to do > so before. > > Now, I cannot get tot he EAC, but EMS is working. I can still Add Email > Accounts and put people in Distribution Lists. > > After talking to the other admin, he decided that the features for > Autodiscover and such, which I think is located in the Mail Flow, or > Servers, that it they should be set to a different authentication method > than what they were originally set to. > > Is there a site that has the EMS/Powershell commands that will allow me to > manipulate Exchange to that level and put everything back? > > Daniel > > -- > Daniel Rodriguez > [email protected] >
