Exchange 2010 RC Clean Install, Still bad
- Ok,
I have now tried this twice. A Clean install this time. I loaded up Server 2008 R2 and join a clean domain. Run setup for Exchange 2010 RC and it has just the warning on Organizational Prerequisets for it will run Setup /ADPrep at the beginning of the install. It installs with no problems, Mailbox, Client Access, Hub Transport and Management Tools all complete. I go to Exchange Management Console and then to Microsoft Exchange On-Premises and get the following:
Initialization Failed.
The following error occurred when searching for On-Premises Exchange Server:
[server#.Domain] Connecting to the remote server failed with the following error message:
The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting help topic. It was running the command 'Discover -ExchangeServer -UseWIA $true -SuppressError $true'.
I get this from the EMC and the remote shell. There must be some way to make this work. I am also not on a remote computer I am on the exchange server as the Administrator.
Michael R. Mastro II
All Replies
- Hi Michael,can you include the lines where this command
Discover -ExchangeServer -UseWIA $true -SuppressError $true -verbose
fails? - I am not sure where the lines are, as this is what is being displayed on the Exchange Management Console
Michael R. Mastro II I am not sure where the lines are, as this is what is being displayed on the Exchange Management Console
Execute the command displayed in the error window inside the Exchange Management Shell and add the -verbose flag to gain some more details.
Michael R. Mastro II- Ok upon launching the shell I get the following:
VERBOSE: Connecting to SERVER4.MRM2Inc.com
[server4.mrm2inc.com] Connecting to the remote server failed withthe following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (system.manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorID : PSSessionOpenFailed.
This happens 3 times then gives me the following
Failed to connect to any exchange server in the current site.
Please enter the server FQDN where you want to connect:
I enter in the server and it gives me the above one more time
Michael R. Mastro II Ok upon launching the shell I get the following:
Thanks, maybe this http://support.microsoft.com/default.aspx/kb/970875 helps you?
VERBOSE: Connecting to SERVER4.MRM2Inc.com
[server4.mrm2inc.com] Connecting to the remote server failed withthe following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (system.manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException
+ FullyQualifiedErrorID : PSSessionOpenFailed.
This happens 3 times then gives me the following
Failed to connect to any exchange server in the current site.
Please enter the server FQDN where you want to connect:
I enter in the server and it gives me the above one more time
Michael R. Mastro II- How do I verify that I have WinRM 2.0 installed. I know it should be part of Windows Server 2008 R2. I added those keys and rebooted as stated in the above kb and it is still not working.
Michael R. Mastro II - I have tried everything. Enabling all the authentication in IIS, have incremented the MaxFieldLength and MaxRequestedBytes to their limits. Disallowed Kerebos on WinRM, with that I did see a change in the message saying it needed Kerebos enabled. Reenabled it, and I still get the same messages over and over again. I cannot uninstall it since it says there are mailboxs, which I cannot remove because EMS and EMC do not work. If anyone has any other tricks I would like to know. I cannot see how they are going to RTM something that is clearly broke.
Michael R. Mastro II I have tried everything. Enabling all the authentication in IIS, have incremented the MaxFieldLength and MaxRequestedBytes to their limits. Disallowed Kerebos on WinRM, with that I did see a change in the message saying it needed Kerebos enabled. Reenabled it, and I still get the same messages over and over again. I cannot uninstall it since it says there are mailboxs, which I cannot remove because EMS and EMC do not work. If anyone has any other tricks I would like to know. I cannot see how they are going to RTM something that is clearly broke.
Michael R. Mastro II
Another try: http://social.technet.microsoft.com/Forums/fr-FR/2225/thread/658228f6-0e27-437b-9413-fb42a4451b03- The suggestions in that article did not work either.
First I did Enable-PSremoting -force which told me that the WinRM service was able to receive requests and that it was set up for remote management.
Second I tried to do the following:
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://server4.mrm2inc.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection
This gave me the following error:
[server4.mrm2inc.com] Connecting to remote server failed with the following error message : The WinRM client cannot process the request. If the authentication scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be added to the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. You can get more information about that by running the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
eption
+ FullyQualifiedErrorId : PSSessionOpenFailed
I then went into group policy on the domain controller and verified the Trusted Hosts in WinRM are set correctly, and as a precaution added the server FQDN to the list. Then rebooted the Exchange Server.
This still failed when I tried it again.
I then did the following:
Set-PSSession -ConfigurationName Microsoft.PowerShell -ShowSecurityDescriptorUI
From which I added the Domain Administrator and gave full control.
Reran everything again. Still no luck.
Now I am just frustrated with it.
Michael R. Mastro II - Michael, I have the exact same error as you.
I have tried many of the same tricks, lately trying winrm commands directly, akin to winrm set winrm/config/client '@{TrustedHosts="my IP address"}', disabling anonymous authentication to the powershell IIS virtual directory, trying Set-User "yourdomain\yourusername" -RemotePowerShellEnabled $true, forced IPv6 to be enabled on the TCP/IP properties, etc . WinRM seems to work by itself, but this annoying problem is frustrating.
My configuration is Win2008R2 for both Ex2010 and my single DC. I am running all commands while logged in as the Domain administrator on the EX2010 box. OWA is working fine, but the EMS will never come up, with the same HTTP error you are reporting. My whole world is sitting on VirtualBox and I accepted the defaults pretty much everywhere for all of these installs.
I hope that the MVP-space for Exchange can come through for a solution or at least guidance past this speedbump.
Regards,
Ken Gartner - *edited to fix command*
Did you folks already enable the account you are trying to launch EMS with for Remote PowerShell?
It's been a while since I did it, but launch EMS with run-as admin and then I think the command is;
Set-User -identity <user> -RemotePowerShellEnabled:$true
You have to do this or other admin accounts will never be able to properly run EMS.
Brian Day: MCSA 2000/2003, CCNA, MCTS: Microsoft Exchange Server 2010 Configuration, Overall Exchange/AD Geek.- Edited byBrian Day Tuesday, November 03, 2009 3:58 AM
Hi Brian,
I did try the set-user cmdlt from a regular Powershell 2.0 screen and I get the following:
The term 'set-user' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the sp
elling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:9
+ set-user <<<< Administrator -RemotePowerShellEnabled $true
+ CategoryInfo : ObjectNotFound: (set-user:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Michael R. Mastro II<see next post>
- Edited byBrian Day Tuesday, November 03, 2009 3:57 AM
- Ok.. I lead you on a wild goose chase, my apologies!
You do in fact need to open Exchange Management Shell (remember to do run-as Admin) while logged in as the admin account you originally installed Exchange with and then run;
set-user <user> -remotepowershellenabled:$true
You can then use get-user <user> | fl *remote* to verify it took.
If you're using the same account now as you did to install Exchange then this might not be the issue, but it is good to ensure it is still set correctly.
Also, does your admin account have a mailbox? Admin accounts require mailboxes in Exchange 2010, this is new... and kind of wierd as it goes against a lot of places policies of not mail enabling admin accounts.
Brian Day: MCSA 2000/2003, CCNA, MCTS: Microsoft Exchange Server 2010 Configuration, Overall Exchange/AD Geek. - The Set-User command did not function within the EMS, but was accepted syntax in a normal Powershell started with Adminstrator privileges. It was already set for me, so indicated that no further change was made.
The problem that Michael and I are reporting has other manifestations too. For example in the EMC, the left hand hierarchy reads as follows:
Microsoft Exchange
Microsoft Exchange On-Premises
If I click on the On-Premises link, I receive an Initialization Failed message in the center panel of EMC, with an explanation very similar to what we have seen from the EMS.
If I right-click Microsoft Exchange, select Add Exchange Forest and specify the local host (using its full domain address and login with default credential set), then I also receive the same kind of WinRM failure.
Thank you Brian for looking into this mystery.
Regards,
Ken - Keep in mind all EMC really is, is a big fancy wrapper front-end for EMS. When you see that on-prem initialization going on it is doing the same thing EMS does when you see it connect to a CAS server are return the cmdlets you are allowed to run. That error usually manifests itself when RemotePowershellEnabled isn't set to $true on an admin account.
Do you have any NICs that are enabled w/o network cables in them or anything?
Does the Application log have any warnings/errors with the same timestamp as when you opened EMS?
Brian Day: MCSA 2000/2003, CCNA, MCTS: Microsoft Exchange Server 2010 Configuration, Overall Exchange/AD Geek. - Nothing directly relevant in the Application Log on that particular, but errors exist from bootup that suggest parts of Exchange running on my local host (BREE) think that BREE is a "remote host" that is unavailable. For example:
Log Name: Application
Source: MSExchangeFDS
Date: 11/3/2009 1:04:58 PM
Event ID: 1018
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: Bree.sherwood.gartner.local
Description:
Process MSExchangeFDS.exe (PID=1524). Failed to connect to remote server BREE . The remote server may be down, or its Server service may not be running.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeFDS" />
<EventID Qualifiers="32772">1018</EventID>
<Level>3</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-11-03T13:04:58.000000000Z" />
<EventRecordID>1592</EventRecordID>
<Channel>Application</Channel>
<Computer>Bree.sherwood.gartner.local</Computer>
<Security />
</System>
<EventData>
<Data>MSExchangeFDS.exe</Data>
<Data>1524</Data>
<Data>BREE</Data>
</EventData>
</Event>
I don't have any disabled networks (am running from VirtualBox so control this carefully).
One point that might be relevant: when I installed Server 2008 R2, I disabled ipv6 somewhere along the way. It was not until after the Ex2010 install that I read this this is very important, so I reenabled it. Could it be there is some special initialization that has to be done, otherwise this machine might resemble the dangling NIC case you asked about?
I don't understand why the powershell environment available to me via the EMS has a different command set than the standard OS powershell -- the latter can run Set-User but the former (in its crippled condition) cannot, as mentioned by Michael as well.
I don't have a mailbox for my Domain Administrator, though I do have one for 'Administrator'. Is this sufficient or do I need to create another administrator mailbox, somehow?
I remain appreciative of your help Brian. I am not an experienced Exchange Admin and have merely been trying to get a basic system up and running so I can qualify my software to read its message tracking logs. A long journey, it appears.
Regards,
Ken
- A potential solution! Several other websites mentioned port 80 and IIS and being very picky.
- I Removed the feature "WinRM IIS Extension".
- I Added the feature "WinRM IIS Extension"
- I ran "winrm quickconfig"
- I rebooted.
Now my EMC actually initializes without error and looks pretty usable.
I get a different warning message in the EMS, which seems minor by comparison:
WARNING: Proxy creation has been skipped for the following command: 'Out-String', because it would shadow an existing local command. Use the AllowClobber parameter is you want to shadow existing local commands.
Brian & Michael -- thank you so much for you help getting up this steep learning curve with Exchange 2010!
Ken Gartner
http://www.permessa.com/exchange
- Hey Ken, sorry I didn't get to this thread today. It sounds like you're getting closer. I know this doesn't help your situation, but in the last 15 months and having installed probably dozens of builds of 2010 I've never run into this error myself and the 2010 setup has never been so much trouble or so intricate, it is usually *very* straight forward. I think something got borked along the way and it's really giving you a tough time here as a result. It truly shouldn't take this much work. :)
Brian Day: MCSA 2000/2003, CCNA, MCTS: Microsoft Exchange Server 2010 Configuration, Overall Exchange/AD Geek. - Hey Brian. I have the problem with ES2010 RC. I installed to Windows systems to try, 2008 enterprise and 2008 R2 enterprise/
in 2008 were a lot of problems with WinRM.
In 2008 R2 those problems were solved, but appeared the thing described in topic...
And I can't uninstall ES2010!!!!!!!!!!! thats a nightmare.
Is there any way to run through this?
What OS you are using to configure ES2010 correcrly?? - I have found the solvation of the problem, disable or reconfigure windows firewall and everything will work.
- Also seeing this identical issue in an in place upgrade of 2010 RC to 2010 RTM
Installed the WinRM IIS components, restarted and still receiving the error. Yes I have tried it in EMS and regular Powershell 2.0.
The cmdlets are just not there. EMS does not even allow me to do anything since it cannot connect. a get-module -list available does not show any exchange server modules either.
[PS] C:\Windows\system32>get-module -listavailableModuleType Name ExportedCommands
---------- ---- ----------------
Manifest ActiveDirectory {}
Manifest ADRMS {}
Manifest AppLocker {}
Manifest BestPractices {}
Manifest BitsTransfer {}
Manifest PSDiagnostics {}
Manifest ServerManager {}
Manifest TroubleshootingPack {}
Manifest WebAdministration {}
Michael R. Mastro II- Well I tried your potential solution... Though it did not work for me.
Michael R. Mastro II - Disabling Firewall did not help me though.
Michael R. Mastro II I am seeing a few errors in the event view from the same time I start EMS. They all come from different sources. And they all have no available troubleshooting. Also no failures under Windows Logs/Application.
From Windows Powershell I have 4 (3 Verbose 1 Error):
Log Name: Microsoft-Windows-PowerShell/Operational
Source: Microsoft-Windows-PowerShell
Date: 11/9/2009 1:36:30 PM
Event ID: 32784
Task Category: None
Level: Error
Keywords: PowerShell remoting transport
User: MASTRO\Administrator
Computer: Server4.MRM2Inc.com
Description:
Runspace Id: 25f658e1-85e6-4a12-b91b-448526de6ffc Pipeline Id: 00000000-0000-0000-0000-000000000000. WSMan reported an error with error code: -2144108297.
Error message: Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
StackTrace: <null>
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-PowerShell" Guid="{A0C1853B-5C40-4B15-8766-3CF1C58F985A}" />
<EventID>32784</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>10</Opcode>
<Keywords>0x8000000000000008</Keywords>
<TimeCreated SystemTime="2009-11-09T18:36:30.399374500Z" />
<EventRecordID>1218</EventRecordID>
<Correlation ActivityID="{00000100-0000-0000-6FDE-FF210761CA01}" />
<Execution ProcessID="6096" ThreadID="5824" />
<Channel>Microsoft-Windows-PowerShell/Operational</Channel>
<Computer>Server4.MRM2Inc.com</Computer>
<Security UserID="S-1-5-21-2915798834-571989394-305266165-500" />
</System>
<EventData>
<Data Name="SessionId">25f658e1-85e6-4a12-b91b-448526de6ffc</Data>
<Data Name="PipelineId">00000000-0000-0000-0000-000000000000</Data>
<Data Name="ErrorCode">-2144108297</Data>
<Data Name="ErrorMessage">Connecting to remote server failed with the following error message : The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.</Data>
<Data Name="StackTrace"><null></Data>
</EventData>
</Event>
WinRM I have 1 Error:
Log Name: Microsoft-Windows-WinRM/Operational
Source: Microsoft-Windows-WinRM
Date: 11/9/2009 1:36:30 PM
Event ID: 142
Task Category: Response handling
Level: Error
Keywords: Client
User: MASTRO\Administrator
Computer: Server4.MRM2Inc.com
Description:
WSMan operation CreateShell failed, error code 2150858999
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WinRM" Guid="{A7975C8F-AC13-49F1-87DA-5A984A4AB417}" />
<EventID>142</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>10</Task>
<Opcode>2</Opcode>
<Keywords>0x4000000000000002</Keywords>
<TimeCreated SystemTime="2009-11-09T18:36:30.399374500Z" />
<EventRecordID>19804</EventRecordID>
<Correlation ActivityID="{00000100-0000-0000-6FDE-FF210761CA01}" />
<Execution ProcessID="6096" ThreadID="5824" />
<Channel>Microsoft-Windows-WinRM/Operational</Channel>
<Computer>Server4.MRM2Inc.com</Computer>
<Security UserID="S-1-5-21-2915798834-571989394-305266165-500" />
</System>
<EventData>
<Data Name="operationName">CreateShell</Data>
<Data Name="errorCode">2150858999</Data>
</EventData>
</Event>
MailboxDatabaseFailureItems 1 Information:
Log Name: Microsoft-Exchange-MailboxDatabaseFailureItems/Operational
Source: Microsoft-Exchange-MailboxDatabaseFailureItems
Date: 11/9/2009 1:37:05 AM
Event ID: 1
Task Category: Store
Level: Information
Keywords:
User: SYSTEM
Computer: Server4.MRM2Inc.com
Description:
Failure Item (Namespace=1, Tag=16, Database=CN=Mailbox Database 1937904042,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MRM2 Incorporated,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MRM2Inc,DC=com, Instance=Mailbox Database 1937904042)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Exchange-MailboxDatabaseFailureItems" Guid="{08E893EA-4C11-4FFF-A737-99B9EEDEE4F4}" />
<EventID>1</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2009-11-09T06:37:05.920962000Z" />
<EventRecordID>21</EventRecordID>
<Correlation />
<Execution ProcessID="3184" ThreadID="4720" />
<Channel>Microsoft-Exchange-MailboxDatabaseFailureItems/Operational</Channel>
<Computer>Server4.MRM2Inc.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<Version>1</Version>
<Namespace>1</Namespace>
<Tag>16</Tag>
<DatabaseGuid>{4AD7716B-621E-4262-8D3F-B00B9DC35EE2}</DatabaseGuid>
<DatabaseInstanceName>Mailbox Database 1937904042</DatabaseInstanceName>
<Component>Store</Component>
<IOErrorIsSpecified>false</IOErrorIsSpecified>
<NotificationEventIsSpecified>false</NotificationEventIsSpecified>
<IOError>
<Category>0</Category>
<FileName>
</FileName>
<Offset>0</Offset>
<Size>0</Size>
</IOError>
<NotificationEvent>
<EventID>0</EventID>
<ParameterBufferSize>0</ParameterBufferSize>
<ParameterBuffer>
</ParameterBuffer>
</NotificationEvent>
</EventXML>
</UserData>
</Event>
HighAvailability 1 Information:Log Name:
Microsoft-Exchange-HighAvailability/Operational
Source: Microsoft-Exchange-HighAvailability
Date: 11/9/2009 1:38:31 PM
Event ID: 325
Task Category: Role Monitoring
Level: Information
Keywords:
User: SYSTEM
Computer: Server4.MRM2Inc.com
Description:
Active manager on this server is running as Standalone for duration 12:00:00.8142487 (AuthoritativeServer=Server4.MRM2Inc.com, ChangeFlags='%4', LastError='%5')
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Exchange-HighAvailability" Guid="{455E3D31-77EF-4853-94A1-032A399567EC}" />
<EventID>325</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>5</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2009-11-09T18:38:31.571998700Z" />
<EventRecordID>694</EventRecordID>
<Correlation />
<Execution ProcessID="2260" ThreadID="3012" />
<Channel>Microsoft-Exchange-HighAvailability/Operational</Channel>
<Computer>Server4.MRM2Inc.com</Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<EventXML xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="myNs">
<Role>Standalone</Role>
<AuthoritativeServer>Server4.MRM2Inc.com</AuthoritativeServer>
<ElapsedTimeInCurrentRole>12:00:00.8142487</ElapsedTimeInCurrentRole>
</EventXML>
</UserData>
</Event>
Michael R. Mastro II- On the phone with PSS now, hope to reach a resolution
- Well after a failure of the server, for some odd reason it would not boot up again. Setup recovery failed each time. So wierd. I have reinstalled Windows Server 2008 R2 and have setup all the pre-requisites. Though I am thinking about removing the WinRM IIS Extenstions first. I have my copy of Exchange 2010 RTM and ready to install it. Though I am hesitant to do so right now. Hopefully all things will go well, this time.
Michael R. Mastro II - Hi Boris, to answer your question I've done 2008 SP2, R2 RC and R2 RTM installs of 2010 over the last year. None of them have had as much trouble as this thread's have unfortunately so I've not been of much help here. :(
The firewall exclusions are configured regardless of if the firewall is turned on or off. One thing I can offer is to not disable the actual firewall service, just turn it off. I've seen some whaky things happen when the FW service is completely disabled instead of letting the service run and turning the FW off in the network config.
Brian Day: MCSA 2000/2003, CCNA, MCTS: Microsoft Exchange Server 2010 Configuration, Overall Exchange/AD Geek. I am experiencing the same issue, though I'll admit my install was not clean by any means. Was running ES2007 on WIN2K8 R2, forced an uninstall of ES2007, did some manual cleanup. Installed ES2010, ran into some issues with the information store mounting, but got that worked out, so I'm kind of shocked to find that this issue has given me the most grief. OWA works, IIS virtual directory structure looks sound, I've tried most all of the solutions presented here, but I've made no progress.
A potential solution! Several other websites mentioned port 80 and IIS and being very picky.
- I Removed the feature "WinRM IIS Extension".
- I Added the feature "WinRM IIS Extension"
- I ran "winrm quickconfig"
- I rebooted.
Now my EMC actually initializes without error and looks pretty usable.
I get a different warning message in the EMS, which seems minor by comparison:
WARNING: Proxy creation has been skipped for the following command: 'Out-String', because it would shadow an existing local command. Use the AllowClobber parameter is you want to shadow existing local commands.
Brian & Michael -- thank you so much for you help getting up this steep learning curve with Exchange 2010!
Ken Gartner
http://www.permessa.com/exchange
GREAT MAN, it just fixed my issue :)- I was told that as a workaround, WinRM and Powershell can be uninstalled and reinstalled
But we're working on tracing the issue now. Can someone else maybe verify this? - Well it worked perfectly fine as of right now. I installed it without WinRM IIS Extenstions installed on the server and it worked flawlessly. Question is should I add the extenstions?
Michael R. Mastro II - So I worked with MS' escalation team today on this and his mentors and they ran through a 1.5GB time trace and my install logs. There weren't any errors that stood out other than a cert issue I was aware of. Since it was the end of their day I took things into my own hands.
Ended up re-running the upgrade. Please not that I did get a debug error as soon as it tried to load the pre-reqs screen related to perms accessing an XML. I stopped there and did some research. Went back and got to the same point and hit continue instead of stop,etc. Ran through the 'upgrade' again and as soon as it was complete I now had access to me EMS and EMC
Very strange through indeed - I un-installed WinRM IIS Extenstions and then re-installed it and that solve my problem. Does anyne know why this solves the problem?
Thanks- Proposed As Answer byandrowa Monday, November 30, 2009 3:33 PM
- hi that worked for me too. but it took some time to dig down the whole bunch of messages.
