This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Exchange 2013

vijay.anand over 7 years ago

Hi,

Currently mid of a sync project for Exchange 2013, once OneIM accepts the credentials am getting the WinRM error.

Followed the steps: "configuring Participating Servers for Remote Access through Windows PowerShell®"

still I get an error, any advice.

Regards,

Vijay

0 Troy Grandy over 7 years ago

Whenever I am working with a power shell connection I always test that I can connect to that remote server via power shell from the job server where this is being setup. If you can connect then this tells you that power shell is configured correctly
Cancel
Up 0 Down

Cancel
0 vijay.anand over 7 years ago

Hi Troy/Experts,

I tried to connect via powershell still I get the same error as mentioned above, eventhough the Exchange server port 80 is open and listening. There is nowhere in the UI to configure advanced connection properties, it only asks for credentials and the dns lookup.

Customer is asking why the 1IM connector is unable to connect with https ? Microsoft recommends https and the customer doesn't connect with http for other applications.

Please advice.

Regards,
vijay
Cancel
Up 0 Down

Cancel
0 Markus Weiss-Ehlers over 7 years ago

Hi Vijay,

which version of OneIM are you using?

By the way, the capability to use SSL for the remote PowerShell connection is something the customer has to enable on the Exchange Servers as well so nothing that is configured right ootb. Big difference to Exchange Online here.
Cancel
Up 0 Down

Cancel
0 vijay.anand over 7 years ago

Hi Markus,

Am using 7.1.2

Once I give the credentials in exchange connector it populates me the organization level. Then I click next and get this error.
WinRM is running on exhange server and port 80 is open.

I dont know what I miss for basic integration.

Regards,
Vijay
Cancel
Up 0 Down

Cancel
0 Markus Weiss-Ehlers over 7 years ago

My advise is to use Google to tracke the WinRM issues and error 403. There tons of things that can go wrong, from using proxy servers, HHTP Redirection and so on. Here is one to start with

https://social.technet.microsoft.com/Forums/ie/en-US/01389ebf-ab4c-4de6-a30c-1c990bfc9c97/the-winrm-client-received-an-http-status-code-of-403-from-the-remote-wsmanagement-service-remote?forum=exchangesvradmin

The upcoming version 8 of One Identity Manger will support the option to use HTTPS for the WinRM connection. Again, customer has to configure this configuration on his on-prem Exchange environment (difference to Exchange Online).
Cancel
Up 0 Down

Cancel
0 vijay.anand over 7 years ago

Hi Markus,

Customer is running exchange server on Windows 2007, and powershell virtual directory is not there by default.

Is it advisable to create manaully for our integration prurpose ?

Thanks,
Vijay
Cancel
Up 0 Down

Cancel