Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Download Vmware Connection Server Extra Quality
49 views
Skip to first unread message
Inge Offley
Jan 21, 2024, 9:59:31 AM1/21/24
to
I noticed that in the folder C:\Program Data\VMware\VDM\dumps there were some dumps from Tomcat service. At every restart ot the Connection server service a dump appeared with the size of about half a GB. I tried to open those dumps with Visual Studio, but I didn't find any useful information.
download vmware connection server
Download File https://t.co/nMKmoo4QVo
I have had this problem since the beginning, about a year ago. I'm on Horizon 7.13. This system was installed and setup by a consultant, first mistake. He was was given an impossible time line, second mistake. The problem is this. Almost all users are being directed to one Connection Server, I have two. It will not balance out the session between the two servers. I use a pair of UAG servers. Their connections are fairly balanced between them. They communicate with a load balancer in front of the Connection Servers. The load balancer has been checked twice and it's configuration verified by the vendor. I have talked to vmware support more than once and currently have an open case. Does anyone have any ideas why all sessions seem to gather on one Connection Server?
I created VMWare ssl web template from CA. Configured everything for Enroll. On the replica server - requested the certificate and completed the certificate process. Imported the certificate to Trusted Root Authorities folder as well. I did this after replica server was installed. I did delete self signed certificate that was created during replica server install. I deleted because did not needed as, I am using certificate from CA.
I am unable to click on the HTML Access Client and get to my resources on the connection server through Chrome i get a "Failed to connect to Connection Server" But again this only happens in Chrome. Any suggestions?
We have the same issue and I was looking at the KB. This KB doesn't state it, but you have to create the locked.properties file. I read it in =en_US&cmd=displayKC&externalId=21447.... I was looking in my connection servers trying to find the locked.properties. I hope that this works.
I added the locked.properties file with the check=Origin=false line to all my connection servers. I can connect to each of the connection servers using the specific DNS name for each server through Chrome. What I can't do now is connect through a DNS name that our Security gave us to use. Using that DNS name will direct us to one of the connection servers that is available.
Just upgraded to the latest 7.0.1. Have done many upgrades without an issue. I have two connections server 01, 02. After the upgrade I was not able to login to my main one - 01. After being able to login via 02 I checked the status and the box is red and says "The service is not working properly" Tried restarting the services and the box numerous times and no luck.
It was just an upgrade from 7.0 to 7.0.1. I cannot get anything to load on 01. And all services are running properly and have been rebooted/restarted numerous times. I also checked the time between the servers and they seem fine.
Also check "\VMware\VMware View\Server\broker\webapps" directory for the following list of folder - admin, ROOT, portal. You can also try stopping the connection server services and then delete the admin and ROOT folders. After this start the connection broker service and check for viewadmin page.
I ran into this same issue with my upgrade last night from 7.0.0 to 7.0.1. I ended up calling into support to resolve the issue. The tech mentioned that sometime with two servers (connection and replica) that you have to update both servers to get the management portal to work. That didnt help my issue. I ended up having to uninstall the connection server, reboot, and then reinstall on both servers. After the reinstall all my pools and settings were present. Hope this helps
I ended up having a similar issue when upgrading from 6.2.2 to 7.0.1. The first connection server upgraded fine without issue. The second/replica install said it was successful but reported the same error you got in the Horizon Administrator. Tried the same thing of service restarts and reboots and those did not work either. Ran the installer again, once again said the install/upgrade was successful but still issues. After looking at it then, it was now actually missing the view connection server service and the application was not even shown as being installed. Ran the installer a third time, installed fine yet again services came up and the box finally registered with View/Horizon in a working state. Weird, but have not had any issues with it since.
should keep the configuration but take snapshots, backups, and write down settings of your environment before doing the upgrade like the documentation says. just in case. I didnt have an issue losing configuration on my upgrade. The first server went fine and picked up where it left off and the replica was the one giving me fits.
He resolved the problem by uninstalling the Horizon 7 Connection Server component from Programs & Features (leave the AD LDS Instance alone) before installing the 7.0.1 package. Not sure if it's necessary, but we rebooted after uninstalling and again after installing 7.0.1. You will be prompted to use the existing instance during install - click OK. This issue seems to be specifically related to connection servers that are paired with security servers. We're back online after following the procedure from Jacob's blog.
It's also a good idea if these servers are still around (recommended to do this first actually), to log into them and uninstall Horizon View (VMware Horizon 7 Connection server), the AD LDS Instance, Horizon HTML access and remove the AD LDS role in Server Manager.
Once you perform a full cleanup of the old or obsolete servers, replication should return to a healthy status. It might also be a good idea to restart the VMware Horizon View Connection Server service on each Connection server one by one.
In our case, we quickly raised the minimum test infrastructure and provided test updates from 2303 to 2306 and from 2303 to 2309. The problem arose in both cases, until we updated the second POD and the connection appeared, then the third POD. When upgrading from 2306 to 2309 there was no problem.
I am planning to upgrade OS on my Connection servers (running version 2211) from Windows 2016 to 2019. What would be the correct procedure? Can I just do the in-place upgrade? I would appreciate your suggestions.
BTW, I have always followed your BLOG to implement my Connection servers to the environment and they are running solid from the day one. Thank you in advance.
I would add a Replica server, reconfigure the load balancer to send traffic to the new server instead of the old server, and then remove the old server. If any UAGs connect directly to the old server, then reconfigure the UAGs too.
Need to migrate the standard connection server from a 2012 server MS OS to 2019 MS OS. Can I create a replica of the 2012 connection server or does the new 2019 need to be a standard deployment? We have another connection server that used the 2012 standard to replicate from as well. If I have to use standard for the 2019 OS buildout does that also mean i need to replicate the other connection server off the new 2019 standard?
We are currently using the built-in HA features for UAGS and a primary connection server and a replica connection server. No load balancer. Had the primary connection server go down and connections failed to the replica. Started digging into DNS and found we never add an entry for examplevdi.domain.com for the replica server.
So if a primary connection server goes down and there is no load balancer then manual intervention should happen by changing the DNS record to point to the replica? Or is there a better way to go about it?
Next question: if there are vCenter related issues during publishing/recomposing a pool, vmware advises to shutdown the connection servers, reboot the vcenter and power on the connection servers 1 by 1. Does it matter in which order those connection servers are being started? What I know is that the last installed replica server becomes the primary connection server (from a ADAM database perspective) so do we need to start rebooting with the last installed connection server first?
Next question: By default vCenter could/should handle a bunch of tasks before it start queueing. There is a well explained vmware article how this works. Horizon by default has an x amount of provisioning connections (default is being used in this environment). During a recompose/publish of a pool, it takes 50-80 minutes to republish 300+ desktops. Hardware : Cisco UCS M5 blades (20gb network interfaces), PureStorage NVMe disks. This should not take this long. I am rearchitecting this environment since one the things this customer is doing is to use resource pools per pool and difference LUNs per pool as well.
Thanks, that might be the solution. My problem is I need 7.1x, I'm on 7.5. 2008 R2 is no longer supported (and it is time to get off of it). I tried upgrading the OS but View didn't work after that. So, I'm stuck creating a new view server. I do have a security server. I think between the two of you I have a good plan.
The UAG's point to an internal URL that balances between the Connection servers, if you don't have a load balancer you could create a dns cname record and point it to one of the Connection servers, when you need to reboot that server move the record.
I really do think I'll go with your plan to create the replica with the older version of connection server but new OS, make it a replica. Then get rid of the old connection server - rinse repeat to create a new replica. And I already have a DNS cname so that the "outside" DNS name and the inside DNS name are the same.
This connection type automatically detects which broker protocol a connection server is using so users in a mixed environment (e.g., one that uses View Connection Servers and PCoIP Connection Managers) do not have to manually reconfigure the session type each time they switch brokers.
f5d0e4f075
download vmware connection server
Download File https://t.co/nMKmoo4QVo
I have had this problem since the beginning, about a year ago. I'm on Horizon 7.13. This system was installed and setup by a consultant, first mistake. He was was given an impossible time line, second mistake. The problem is this. Almost all users are being directed to one Connection Server, I have two. It will not balance out the session between the two servers. I use a pair of UAG servers. Their connections are fairly balanced between them. They communicate with a load balancer in front of the Connection Servers. The load balancer has been checked twice and it's configuration verified by the vendor. I have talked to vmware support more than once and currently have an open case. Does anyone have any ideas why all sessions seem to gather on one Connection Server?
I created VMWare ssl web template from CA. Configured everything for Enroll. On the replica server - requested the certificate and completed the certificate process. Imported the certificate to Trusted Root Authorities folder as well. I did this after replica server was installed. I did delete self signed certificate that was created during replica server install. I deleted because did not needed as, I am using certificate from CA.
I am unable to click on the HTML Access Client and get to my resources on the connection server through Chrome i get a "Failed to connect to Connection Server" But again this only happens in Chrome. Any suggestions?
We have the same issue and I was looking at the KB. This KB doesn't state it, but you have to create the locked.properties file. I read it in =en_US&cmd=displayKC&externalId=21447.... I was looking in my connection servers trying to find the locked.properties. I hope that this works.
I added the locked.properties file with the check=Origin=false line to all my connection servers. I can connect to each of the connection servers using the specific DNS name for each server through Chrome. What I can't do now is connect through a DNS name that our Security gave us to use. Using that DNS name will direct us to one of the connection servers that is available.
Just upgraded to the latest 7.0.1. Have done many upgrades without an issue. I have two connections server 01, 02. After the upgrade I was not able to login to my main one - 01. After being able to login via 02 I checked the status and the box is red and says "The service is not working properly" Tried restarting the services and the box numerous times and no luck.
It was just an upgrade from 7.0 to 7.0.1. I cannot get anything to load on 01. And all services are running properly and have been rebooted/restarted numerous times. I also checked the time between the servers and they seem fine.
Also check "\VMware\VMware View\Server\broker\webapps" directory for the following list of folder - admin, ROOT, portal. You can also try stopping the connection server services and then delete the admin and ROOT folders. After this start the connection broker service and check for viewadmin page.
I ran into this same issue with my upgrade last night from 7.0.0 to 7.0.1. I ended up calling into support to resolve the issue. The tech mentioned that sometime with two servers (connection and replica) that you have to update both servers to get the management portal to work. That didnt help my issue. I ended up having to uninstall the connection server, reboot, and then reinstall on both servers. After the reinstall all my pools and settings were present. Hope this helps
I ended up having a similar issue when upgrading from 6.2.2 to 7.0.1. The first connection server upgraded fine without issue. The second/replica install said it was successful but reported the same error you got in the Horizon Administrator. Tried the same thing of service restarts and reboots and those did not work either. Ran the installer again, once again said the install/upgrade was successful but still issues. After looking at it then, it was now actually missing the view connection server service and the application was not even shown as being installed. Ran the installer a third time, installed fine yet again services came up and the box finally registered with View/Horizon in a working state. Weird, but have not had any issues with it since.
should keep the configuration but take snapshots, backups, and write down settings of your environment before doing the upgrade like the documentation says. just in case. I didnt have an issue losing configuration on my upgrade. The first server went fine and picked up where it left off and the replica was the one giving me fits.
He resolved the problem by uninstalling the Horizon 7 Connection Server component from Programs & Features (leave the AD LDS Instance alone) before installing the 7.0.1 package. Not sure if it's necessary, but we rebooted after uninstalling and again after installing 7.0.1. You will be prompted to use the existing instance during install - click OK. This issue seems to be specifically related to connection servers that are paired with security servers. We're back online after following the procedure from Jacob's blog.
It's also a good idea if these servers are still around (recommended to do this first actually), to log into them and uninstall Horizon View (VMware Horizon 7 Connection server), the AD LDS Instance, Horizon HTML access and remove the AD LDS role in Server Manager.
Once you perform a full cleanup of the old or obsolete servers, replication should return to a healthy status. It might also be a good idea to restart the VMware Horizon View Connection Server service on each Connection server one by one.
In our case, we quickly raised the minimum test infrastructure and provided test updates from 2303 to 2306 and from 2303 to 2309. The problem arose in both cases, until we updated the second POD and the connection appeared, then the third POD. When upgrading from 2306 to 2309 there was no problem.
I am planning to upgrade OS on my Connection servers (running version 2211) from Windows 2016 to 2019. What would be the correct procedure? Can I just do the in-place upgrade? I would appreciate your suggestions.
BTW, I have always followed your BLOG to implement my Connection servers to the environment and they are running solid from the day one. Thank you in advance.
I would add a Replica server, reconfigure the load balancer to send traffic to the new server instead of the old server, and then remove the old server. If any UAGs connect directly to the old server, then reconfigure the UAGs too.
Need to migrate the standard connection server from a 2012 server MS OS to 2019 MS OS. Can I create a replica of the 2012 connection server or does the new 2019 need to be a standard deployment? We have another connection server that used the 2012 standard to replicate from as well. If I have to use standard for the 2019 OS buildout does that also mean i need to replicate the other connection server off the new 2019 standard?
We are currently using the built-in HA features for UAGS and a primary connection server and a replica connection server. No load balancer. Had the primary connection server go down and connections failed to the replica. Started digging into DNS and found we never add an entry for examplevdi.domain.com for the replica server.
So if a primary connection server goes down and there is no load balancer then manual intervention should happen by changing the DNS record to point to the replica? Or is there a better way to go about it?
Next question: if there are vCenter related issues during publishing/recomposing a pool, vmware advises to shutdown the connection servers, reboot the vcenter and power on the connection servers 1 by 1. Does it matter in which order those connection servers are being started? What I know is that the last installed replica server becomes the primary connection server (from a ADAM database perspective) so do we need to start rebooting with the last installed connection server first?
Next question: By default vCenter could/should handle a bunch of tasks before it start queueing. There is a well explained vmware article how this works. Horizon by default has an x amount of provisioning connections (default is being used in this environment). During a recompose/publish of a pool, it takes 50-80 minutes to republish 300+ desktops. Hardware : Cisco UCS M5 blades (20gb network interfaces), PureStorage NVMe disks. This should not take this long. I am rearchitecting this environment since one the things this customer is doing is to use resource pools per pool and difference LUNs per pool as well.
Thanks, that might be the solution. My problem is I need 7.1x, I'm on 7.5. 2008 R2 is no longer supported (and it is time to get off of it). I tried upgrading the OS but View didn't work after that. So, I'm stuck creating a new view server. I do have a security server. I think between the two of you I have a good plan.
The UAG's point to an internal URL that balances between the Connection servers, if you don't have a load balancer you could create a dns cname record and point it to one of the Connection servers, when you need to reboot that server move the record.
I really do think I'll go with your plan to create the replica with the older version of connection server but new OS, make it a replica. Then get rid of the old connection server - rinse repeat to create a new replica. And I already have a DNS cname so that the "outside" DNS name and the inside DNS name are the same.
This connection type automatically detects which broker protocol a connection server is using so users in a mixed environment (e.g., one that uses View Connection Servers and PCoIP Connection Managers) do not have to manually reconfigure the session type each time they switch brokers.
f5d0e4f075
0 new messages