Multiple OneView Environments

[NogNog]

Hello Community

I have a question about the OneView Windows Admin Center extension.

I tried to install the extension on our WAC Server. It doesn't work and this error occurs:

 

For your Information: On our WAC environment there is no internet access and we have servers connected from different Domains and there are three OneView environments total.

Can you help me with this issue?

Thank you and kind regards!

[Doug de Werd]

Have you tried the suggestions from ChrisLynch in your previous post?  This sounds like the lack of internet connection is causing a problem.  The links Chris provided show how to manually download the extensions and then add them locally to your WAC server.

[Doug de Werd]

The multiple domains and OneView insrtances are not a problem if you can't even install the extension.

[Doug de Werd]

Are you having the same problem when trying to load other extensions?  This same issue has been reported on other vendors' extensions, so it is most likely related to not having an internet connection.

What version of WAC are you using?

[NogNog]

I tried the suggestions. I put the Extension .nupkg File on a directory.

[NogNog]

I didn't try to install other extensions. I'll try it.

I am using the version 2009. This should be the right version, right?

[NogNog]

I tried to install another extension. It was this extension:https://dev.azure.com/WindowsAdminCenter/Windows%20Admin%20Center%20Feed/_packaging?_a=package&feed=WAC&package=dellemc.dellemcpowerpath&protocolType=NuGet&version=1.0.0 

There was no problem installing it offline.

I don't really get why there is a problem with the platform integrety.

Hopefully you can help me further.

[NogNog]

@Doug de Werd have you seen my answer?

Kind regards 

NogNog

[Doug de Werd]

We are looking into it.  We have not yet been able to reproduce this is our lab - we can successfully install the extension without an internet connection.

I'll post more once I get more information.

Thanks,

Doug

[NogNog]

Hello @Doug de Werd 

We found the problem. There were two Intermediate Certificates and one Root Certificate who were not trusted:

Now I need to figure out, how to configure the extension.