Anything in the event logs?

On Mon, Nov 25, 2013 at 11:54 AM, Geoff Orlebeck <[email protected]>wrote:

> Hello Everyone:
>
>
>
> We are having an issue with a newly built Exchange 2010 server. Domain is
> one AD and one Ex2010 server. This is a newly created domain, so this is
> the first Exchange server in the new domain. Ex2010 server was installed
> using the “typical” installation option (HUB, CAS, Mailbox, Mgmt. Tools).
> Exchange installed without issue (or at least no visible errors from
> installer window). Now though, when attempting to launch EMC we are met
> with one of two error messages:
>
> 1)    If I login with the default Administrator account it comes up with
> an error stating it couldn’t find “DOMAIN\Administrator”.
>
> 2)    If I login with a different admin-level account I receive this
> error: “[exchangeserver.domain.org] Connecting to remote server failed
> with the following error message: The WinRM client received an HTTP server
> error status (500), but the remote service did not include any other
> information about the cause of the failure. For more information, see the
> about_Remote_Troubleshooting Help topic. It was running the command
> ‘Discover-ExchangeServer –UseWIA $true –SupressError $true –CurrentVersion
> ‘Version 14.3 (Build 123.4)”.
>
>
>
> I saw a suggestion about disjoining/rejoining the domain, so I gave that a
> shot without success. I bounced both servers and tried accessing EMC after
> they both came back from the clean restarts. The other oddity is using the
> built-in “Administrator” account everything (seemingly) works from EMS. I
> am able to (seemingly) perform any/all functions from the shell, but EMC
> continues to give the error message about being unable to find
> “DOMAIN\Administrator”. If I login as the other admin account, I get error
> #2 from above for both EMS and EMC. Any suggestions would be met with great
> appreciation. Thank you.
>
>
>
> -Geoff
>
> This message and any attached documents may be privileged or confidential and
> contain information protected by state and federal privacy statutes.  They are
> intended only for the use of the addressee.  If you are not the intended
> recipient, any disclosure, copying, or distribution of this information is
> strictly prohibited. If you received this transmission in error, please accept
> our apologies and notify the sender.
>
>

Reply via email to