CloudInMyHead

My feedback

  1. 51 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead commented  · 

    What about all these others steps you took. Do we need to change all of those too?
    1) all SPNs are registered definetly correct. Delegation for the SDK-Account, etc. in AD correct.
    2) Kerberos authentication
    3) IIS authentication is as recomended:
    - VirtualSite "OperationsManager" > Authentication > Windows Authentication is enabled.
    - Provider (Negotiate first, then NTLM)
    - "Enable Kernel-mode authentication" is OFF
    - The same settings above also for the VirtualSite "MonitoringView"
    4) Application Pools
    - .NET CLR Version is v4.0 for both "OperationsManagerAppMonitoring" and "OperationsManagerMonitoringView". It did not help to switch Version 2.0. It did not help also to switch the "Managed Pipeline Mode" from "Integrated" to "Classic".
    5) There is no problem on the Web Console Server to access the SCOM Web Console.
    6) On the client site, in Internet EXplorer, the Web Console Server is trusted server in the local intranet. Kerberos authentication is enabled, etc..

    CloudInMyHead commented  · 

    I have the same issue!

  2. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 
  3. 6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 
  4. 189 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 
  5. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 
  6. 36 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 
  7. 2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 
  8. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  General Operations Manager Feedback  ·  Flag idea as inappropriate…  ·  Admin →
    CloudInMyHead supported this idea  · 
    CloudInMyHead commented  · 

    I agree! Troubleshooting steps would be handy in deployment as well. Might be nice to mention where the files are stored on the UNIX\Linux box when deployed from 2016 vs 2012 since that changed as well in 2016.

  9. 9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    CloudInMyHead supported this idea  · 

Feedback and Knowledge Base