The command completed successfully but no settings have been saved.
I get a message as is captioned in the heading for this post when i Apply an edit for a Hub Transport setting from a domain administrator account that is delegated the Exchange Server Administrator role. I'm am not a seasoned Exchange administrator, however, i searched diligently for documentation to explain this perplexing issue (to me) and I can't find such.With respect to the TechNet prescriptions i'm reading, I want to make a change to the default External DNS Lookup properties of theHub Transport configuration to best accommodate my installation by specifying a particular Network Adapter for DNS Lookup and i have delegated the Exchange Server Adminstrator role to an account that i used to perform such, however, Exchange won't save the change i make. Rather, Exchange reverts the property back to All Available IPv4 Addresses. Specifically, I set the External DNS Lookup parameter to a specific Network Adapter of my multihomed Exchange server and i'm confronted with the following message: The command completed successfully but no settings of '<eServer>' have been modified. Needless to say, i recurse and review the properities and they have reverted back as said. I'm aware of the needed Exchange Server Administrator role and i am concerned about impact of any inherited Exchange View Only Administrator memberships; respectively, i followed the TechNet discussion about How to Delegate Server Administration, however, i'm still left with the same delima. I tried stopping the Transport services and making the changes; nada. Currently, i'm unable to make the said configuration change. I'd be deeply obligated to someone shedding some light on this;how to troubleshoot this dilema would even be helpful. Thanks,Glenn Glenn of xSyLent
May 13th, 2009 5:08am

The good news is that mail will flow in spite of the "no settings" message; providing routing and smtp are setup right.Of my scenario, i was trying to critique a working configuration (i.e. make it more specific). -i was learning this aspect of Exchange and i initially didn't know where my problem was (or how to identify it).I still have criticism about Exchange's mechanics for the administration that this post regards and it's all detailed in the following post:http://social.technet.microsoft.com/Forums/en/exchangesvrtransport/thread/5df13c73-e8ce-42d3-80cd-9d7d3345a83eSome lyrics come to mind that may help sooth any anguish while wrestling this issue: "u can checkout any time u like, but u can never leave","trying to find a woman who has never been born". Cheers!Glenn of xSyLent
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2009 9:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics