Install over the top of the existing...
*ASB **http://XeeMe.com/AndrewBaker* <http://xeeme.com/AndrewBaker> *Providing Virtual CIO Services (IT Operations & Information Security) for the SMB market…* On Tue, Nov 26, 2013 at 1:15 PM, Geoff Orlebeck <[email protected]>wrote: > I guess that is the next best course of action. Again, excuse my > inexperience, but when you say “reinstall” you are referring to performing > an actual uninstall then reinstall…not just re-running the installer and > trying to install over the top of the existing installation, yes? > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Michael B. Smith > *Sent:* Tuesday, November 26, 2013 10:12 AM > > *To:* [email protected] > *Subject:* RE: [Exchange] Ex2010 EMC Initialization Fails: > > > > While IPv6 is required for supportability, it does not cause this > particular issue. > > > > A reinstall will not undo any work, as long as you specify the same set of > parameters. J > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Geoff Orlebeck > *Sent:* Tuesday, November 26, 2013 1:06 PM > *To:* [email protected] > *Subject:* RE: [Exchange] Ex2010 EMC Initialization Fails: > > > > Michael: > > > I was looking through various links and TechNet articles and found > something related to IPv6. I noticed the server replied to ping with IPv6 > addresses, but IPv6 was unchecked in the NIC properties (I’m inheriting the > base 2008 R2 server from a build template). I didn’t see the reg key in > there for disabling IPv6, or at least setting IPv4 as the preferred method. > I added it and the server is now replying with IPv4 address, but the issue > persists. Not sure if that has anything to do with this. > > > > As for the reinstall of Exchange, I just want to confirm whatever work I > have already performed won’t be undone by the reinstall (database creation > and mailbox additions to AD users). Thanks. > > > > Geoff > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Michael B. Smith > *Sent:* Tuesday, November 26, 2013 9:56 AM > *To:* [email protected] > *Subject:* RE: [Exchange] Ex2010 EMC Initialization Fails: > > > > A re-install of Exchange – from an ELEVATED CMD PROMPT. > > > > If it added the exception, then winRM is ok now. That was part of the > problem. :P > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Geoff Orlebeck > *Sent:* Tuesday, November 26, 2013 11:16 AM > *To:* [email protected] > *Subject:* RE: [Exchange] Ex2010 EMC Initialization Fails: > > > > I should have clarified. It stated it added the exception, but I’m still > getting the same error when launching EMC. > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Geoff Orlebeck > *Sent:* Tuesday, November 26, 2013 8:12 AM > *To:* [email protected] > *Subject:* RE: [Exchange] Ex2010 EMC Initialization Fails: > > > > Michael: > > > > I ran the “winrm quickconfig” from the elevated cmd and it asked to create > a WinRM listeneron http://*, which I told it yes and the response was it > created the WinRM listener to accept WS-Man requests. > > > > Not to show my complete lack of experience, but when you say a re-install, > are you referring to the WinRM component? Or the full Exchange installer? > I’m not sure how to perform the reinstall of WinRM. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Michael B. Smith > *Sent:* Tuesday, November 26, 2013 6:01 AM > *To:* [email protected] > *Subject:* RE: [Exchange] Ex2010 EMC Initialization Fails: > > > > Try a “winrm quickconfig” and a re-install from an ELEVATED CMD PROMPT. > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Steve Ens > *Sent:* Monday, November 25, 2013 12:48 PM > *To:* [email protected] > *Subject:* Re: [Exchange] Ex2010 EMC Initialization Fails: > > > > Geoff, I'm fairly certain I've had that problem with my Exchange 2010 box > in the past too. Let me look at my notes and I'll get back to you. > > > > On Mon, Nov 25, 2013 at 11:43 AM, Geoff Orlebeck <[email protected]> > wrote: > > I ran this utility last week and everything came back as “passed”. I’m > fairly new with Exchange, I’ve done about 2-3 Exchange standard installs > and never encountered this. The only thing different on this install than > on other Exchange deploys I have performed was we modified the program > files install directory from the standard “C:\Program Files\...” to the > “D:\Program Files…” (as decided by higher ups than me). Normally I leave > default install directory and move database/log files to data drive. I > don’t know if that has any bearing, but this is the first time I’ve > installed the Exchange program files to the non-default directory. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Candee > *Sent:* Monday, November 25, 2013 9:37 AM > > > *To:* [email protected] > *Subject:* Re: [Exchange] Ex2010 EMC Initialization Fails: > > > > Have you seen this? > > http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx > > Worth a look. > > On Mon, Nov 25, 2013 at 12:30 PM, Candee <[email protected]> wrote: > > 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. > > > > > > > > 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. > > > > > > > > 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. > > > > > > 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. > > > > > > 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. > > > 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. > >
