Administrator Guide

Manage Wyse Management Suite repository service
Wyse Management Suite repository is displayed as Dell WMS Repository: Tomcat Service in the Windows Local Services
window and is configured to start automatically when the server restarts.
Proxy support for Wyse Management Suite remote
repositories
From Wyse Management Suite 3.1, remote repositories support SOCKS5 proxy for all HTTPS and MQTT communications to
Wyse Management Suite.
Only system-wide proxies are supported since the remote repository runs as a Windows service. Also, only proxies with AD
authentication or no authentication are supported. You can configure the proxy servers using any method. Following are few
examples on how to configure proxy server information:
Using the netsh commandYou can use the following command to configure the proxy server information
netsh winhttp set proxy proxy-server="socks=localhost:9090" bypass-list="localhost
C:\Users\administrator.WMSAD61>netsh winhttp set proxy proxy-server="socks=<proxy
server IP>" bypass-list="localhost"
Current WinHTTP proxy settings:
Proxy Server(s) : socks=<proxy server IP>
Bypass List : localhost
Using the WPAD file configured in DHCPWyse Management Suite repository server must be configured with DHCP IP
address and Internet Explorer must be configured with Automatically Detect settings. You must configure the DHCP option
tag 252 with the WPAD.pac file. Following is a sample PAC file content:
function FindProxyForURL(url, host)
{
if (shExpMatch(host, "*wysemanagementsuite.com*")) {
return "SOCKS <proxy server IP>";
}
return "DIRECT";
}
You can also configure the proxy settings using group policies.
NOTE:
Proxy settings are read when the repository service starts. If you make any changes to the proxy settings later, you
must restart the repository service.
NOTE: Host name resolution is not set if SOCKS4 proxy is used. You must update the hosts file present in C:\Windows
\System32\drivers\etc to resolve the public cloud URL/hostname on the server where Wyse Management Suite
repository is installed. If SOCKS5 proxy is used, the hostname resolution using the DNS configured in network settings of
the server is resolved.
132 Remote repository