EecITSupport's Posts

Trying to replace Horizon Security server with UAG.  Everything works after test deployment, able to connect to VDI from external network.  The only thing that's not working is our external remote we... See more...
Trying to replace Horizon Security server with UAG.  Everything works after test deployment, able to connect to VDI from external network.  The only thing that's not working is our external remote webpage.  https://remote.mydomain.com In the current environment, external IP for "remote" is NAT to the Security server. Internally, "remote" is routed to the Connection server.  My assumption is that the external traffic hits our firewall, then forward to Sec server, then pass to Connection server and back. Verified the firewall nor any internal security is blocking the traffic as everything works when external traffic is routed through Sec server, but if I NAT the traffic to UAG, https://remote.mydomain.com comes up as site not reachable.   Ran "curl https://remote.mydomain.com" command from the UAG console and receive the following message curl: (60) SSL cert problem: unable to get local issuer certificate.  curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it. Could this be the reason UAG is not passing the request to Connection Server?  If so, how can I fix this as we don't plan to use a SSL from trusted CA.
thanks mchadwick19, Would you say be in terms of size that SQL Standard is needed?  Also, are you recommending that Composer on 1 server and SQL on a separate server? Thanks again!
Planning to upgrade from Windows vCenter 6.5 to VCSA 6.7, and need to migrate View Composer currently co-installed on this server to a new Windows server.  Is SQL Express powerful enough to handl... See more...
Planning to upgrade from Windows vCenter 6.5 to VCSA 6.7, and need to migrate View Composer currently co-installed on this server to a new Windows server.  Is SQL Express powerful enough to handle roughly 150 virtual desktops or best to pay the $ for SQL Standard? Thanks in advance. 
Looks to be an issue only when someone logs into 1803 for the 1st time, no longer getting those CPU warning once someone been on it.  Thanks for your reply.
vSphere 6.5 Horizon View 7.3.2 After upgrading few Win10 VMs to Build 1803 from 1709, getting more VmCPUUsageAlarm from these machines (2 CPUs, 6 GBs RAM).  Anyone experienced similar iss... See more...
vSphere 6.5 Horizon View 7.3.2 After upgrading few Win10 VMs to Build 1803 from 1709, getting more VmCPUUsageAlarm from these machines (2 CPUs, 6 GBs RAM).  Anyone experienced similar issue with 1803? Any suggestions? Thanks in advance.