ehrnst
require guide of installation
is that possible to share the guide of installation? such as how to install and configure the webapi in windows server 2012 R2 with IIS 8.5 + SCOM 2012 R2?
I am very aware of the limitations, but have you checked here? https://github.com/ehrnst/System-Center-Operations-Manager-API/wiki/Installation-and-configuration I also blogged on the first release, which didn't have DW settings, but it might help. https://adatum.no/operationsmanager/web-api-for-scom
Hi. What dosent work? Can you share some error messages?
Martin
On Wed, Apr 24, 2019 at 8:27 AM famingxia [email protected] wrote:
have tried above solution, but not works
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ehrnst/System-Center-Operations-Manager-API/issues/28#issuecomment-486085945, or mute the thread https://github.com/notifications/unsubscribe-auth/AFC6E5VXMLPNDHT6LG26N23PR74VZANCNFSM4HEPB7JA .
Hi. We would like to set this up in our SCOM server however we can't make it work. Although I am quite confused with the directories. Where does Bin folder point to? Is that the parent directory of this repository?
Hi. We would like to set this up in our SCOM server however we can't make it work. Although I am quite confused with the directories. Where does Bin folder point to? Is that the parent directory of this repository?
Hi Elixa. Not sure what you have done already. but you have downloaded the latest release? https://github.com/ehrnst/System-Center-Operations-Manager-API/releases
A small guide is available here; https://github.com/ehrnst/System-Center-Operations-Manager-API/wiki/Installation-and-configuration
What you do is that you create a new IIS site and unzip the folder to where you want the site.. Using inetpub is also possible
Hi Martin,
Thank you very much for your response!
So far, we have compiled the code downloaded in Github. Then we created a new web service in IIS - we did not add it under the Default Web Site. We made some changes in Web.config to allow all users and enabled Windows authentication to solve 401 errors. However we get 403 Forbidden error now when we try to access the API in internet explorer. I assumed this is because of the anonymous auth set when accessing the API in the browser? Now we are testing the API through Powershell to solve the credentials error but we get this instead:
Could you assist us again on why we are encountering this?
We finally made it work btw. So we are having the issue because we enabled Anonymous Authentication in IIS.
Thanks for letting me know. I don't know, but I assume it doesn't work with anonymous authentication, as SCOM will check the user's permissions. I guess a rewrite is needed for that to work.
Hopefully you can make use of it either way!
Martin
On Thu, Mar 12, 2020 at 2:05 AM Elixa-Mae A. Pesa [email protected] wrote:
We finally made it work btw. So we are having the issue because we enabled Anonymous Authentication in IIS.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ehrnst/System-Center-Operations-Manager-API/issues/28#issuecomment-597955224, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFC6E5UGVEKMUKU2L7BDB5DRHAYNFANCNFSM4HEPB7JA .