Hello Commvault Community,
Due to the fact that more and more environments are based on CommServe Linux, which by default has a built-in WebServer module, which in the case of Linux OS doesn’t support the O365 configuration, the WebServer module is increasingly being transferred to machines with Windows OS - this is a requirement for the O365 configuration.
Commvault documentation specifies that the WebServer package should be installed on access nodes that will cover O365 configurations.
-
If we have a pure Windows machine with no role in O365 or any other configuration in the Commvault environment, can such a server act as a dedicated O365 WebServer?
If so, will Commvault automatically detect it? If not, where should I change it as the one responsible for connecting to Microsoft portals for the O365 configuration? Maybe some Additional Setting?
Does an O365 WebServer necessarily have to be part of the configuration (located on an Access Node or IndexServer)?
- What if we have a scenario where we want to redirect required traffic to the Internet and required Microsoft portals through an additional HTTP proxy? Is this possible and supported?
The Network Topology and advanced HTTP Proxy settings for the Access Node/IndexServer where the WebServer package is installed for O365 configurations aren’t respected and doesn’t work.
Is there anything specific to this scenario?
Previously, when CommServe was on Windows and simultaneously acted as a WebServer for the entire Commvault environment and O365 configuration, traffic via HTTP Proxy worked without any problem, and now, when there must be a dedicated WebServer for O365, HTTP Proxy doesn’t work. We don’t know whether this is a intentional action to ensure communication during verification with MS portals, or whether it should be possible to configure it so that a dedicated server for WebServer or Access Node for O365 with the WebServer role installed is regulated by HTTP Proxy.
Thanks&Regards,
Kamil
