Wow, until you quoted the sensor_install.log, I would have expected a problem like “BESClient is installed on D: drive on the servers” or “you need to quote the path on the CD command as there are spaces in it”. But if that server_install.log is getting generated that implies the batch file is at least working enough to launch the installer.
It looks like this product in particular is problematic, in that it reaches up ti the internet at installation time to download more of its package. You might ask your vendor to provide an “offline installer” that doesn’t require additional downloads.
Otherwise, check whether your traffic from Servers to Internet is allowed, you may need to define a proxy server or add firewall rules. In some organizations it is common to require a proxy server to access the Internet, and your infra team might configure the proxy clients via a Group Policy or logon script that applies to clients but not to servers.
The way this particular product is doing its downloads looks troubling from a security perspective as well…if it’s downloading a CA certificate on the fly and then explicitly trusting it for the remaining downloads, it might possibly allow a man-in-the-middle attack if an adversary could replace both the downloaded CA key and the payload it is authenticating. Usually one would expect CA keys to either be trusted by the OS explicitly (like public web browsing) or baked-in to the product configuration (like a BigFix masthead), not downloaded dynamically at installation time.