mardi 17 mai 2011 15:19
I thought I would just download the Exchange Server 2010 SP1 demo vhd from Microsoft (SLC-DC01.vhd) and would be going in no time. Unfortunatelly Exchange Server doesn't initialize because of some DNS issues with PowerShell and WinRM. Reading through the Getting-Started I see that there is a second vhd needed for a machine called SLC-OCS.vhd.
I couldn't find a download link for this VHD.
My question now is:
Do I actually need two VHDs SLC-DC01.vhd and SLC-OCS.vhd?
If yes, where can I download the second VHD?
Is there a better way to get hands-on experience with Exchange Server 2010. E.g. a set of hands-on labs to deploy, configure and maintain Exchange Server?
Toutes les réponses
jeudi 19 mai 2011 09:39
What's error your got when trying to start Exchange Management console?
Please open services.msc and check if all the exchange services are starting.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT
- Marqué comme réponse Gen Lin mercredi 25 mai 2011 02:27
dimanche 8 janvier 2012 05:20
Was there ever a solution? I have the same problem.
The error message when opening up Exchange Management Console and clicking on Microsoft Exchange On-Premises is:
The following error occurred while attempting to connect to the specified Exchange server 'slc-dc01.contoso.com':
The attempt to connect to http://slc-dlc01.contoso.com/powershell using "kerberos" authentication failed: Connecting to remote server failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troubleshooting Help topic.
samedi 12 mai 2012 03:47I am having the same issue. Any direction would be appreciated. Thank you.
samedi 12 mai 2012 13:05I was able to resolve this by using: http://support.microsoft.com/kb/2027062
mercredi 14 novembre 2012 23:32I tried this but i still get the same error. Any other suggestions?