On the View connection broker side you could do a backup/export of the ADAM database, build out the new server, and then import the database in. On the composer side you could utilize the same...
See more...
On the View connection broker side you could do a backup/export of the ADAM database, build out the new server, and then import the database in. On the composer side you could utilize the same methodology of migrating the SQl express database and then just pointed the new composer install to that database. Since your backing up and restoring on both instances you should be able to power down the old 2K8 servers and bring them back online in case you needed to roll back. ,,
I'm not sure I completely understand the question, however you should be able to point both vCenters to the external PSC controllers without any issues.
I think they both offer platforms that would easily get the job done from both a performance and stability standpoint. The key will be defining your criteria in more detail and then seeing whic...
See more...
I think they both offer platforms that would easily get the job done from both a performance and stability standpoint. The key will be defining your criteria in more detail and then seeing which solution fits. Maybe you prefer the hypconverged and one stop shopping of nutanix or maybe you prefer to build out your infrastructure from the ground up with a set of dell servers. I think it's up to you to define this criteria and then pick the best fit for your environment.
Here is a link to the VMware PSC topologies KB. It should give you an idea of what to look for. VMware KB: List of recommended topologies for VMware vSphere 6.0.x
In my experience this has been really simply. Just stop services on View composer, backup database, restore to different SQL server, and finally change your ODBC on the View composer server to p...
See more...
In my experience this has been really simply. Just stop services on View composer, backup database, restore to different SQL server, and finally change your ODBC on the View composer server to point to the new SQL server. The events DB is really the same thing and you just have to point the new SQL server in in the configuration page located in the View Admin portal.
We recently went through the SQL upgrade process and we opted to move the vCenter and View database to a new SQl server we had built. I don't recall experiencing any issues in between the time...
See more...
We recently went through the SQL upgrade process and we opted to move the vCenter and View database to a new SQl server we had built. I don't recall experiencing any issues in between the time we moved and when we actually upgraded the products to their latest versions. I think we waited about a week post SQL migration before we started the vCenter upgrade. Then after that was completed we did our View upgrade. You will want to make sure your clients are up to date or re enable TLS 1.0 after your move to 6.2.1 as clients 3.3 and earlier use TLS 1.0 which is disabled in 6.2. This got us a little bit as we didn't realize how many older clients we had. Release Notes for VMware Horizon 6 version 6.2.1
A black screen is typically some kind of port being blocked by the firewall. See the KB below for the required ports. VMware KB: Network connectivity requirements for VMware View Manager 4.5 ...
See more...
A black screen is typically some kind of port being blocked by the firewall. See the KB below for the required ports. VMware KB: Network connectivity requirements for VMware View Manager 4.5 and later
You could put the files/folders in the C:\users\public\desktop folder on the image and then recompose the pool. That should produce desktops with the files in place for you.
I'm just taking a stab with a KB based on the error message, VMware KB: VMware Horizon View Client cannot connect to a View Connection Server host in a proxy server environment. This is all...
See more...
I'm just taking a stab with a KB based on the error message, VMware KB: VMware Horizon View Client cannot connect to a View Connection Server host in a proxy server environment. This is all internal with no security servers, etc? If you visit the CB url from an internet browser does it respond correctly? The error is generated on an attempt to connect to the pool which means you get authenticated and are displayed your pool list correctly?
We saw this same message in our physical environment. We ended up having to remove the printers and cleaning up the drivers from the impacted workstations. Once we did that we reinstalled eve...
See more...
We saw this same message in our physical environment. We ended up having to remove the printers and cleaning up the drivers from the impacted workstations. Once we did that we reinstalled everything and the printer jobs started flowing normal.
Once you have the golden image on the new vCenter you could create a snapshot and recompose the pool on that snapshot which would in turn create a replica on the new vCenter.
Am I understanding it correctly that you have 30 machines in a dedicated pool. You have several classes of students that need to access these machines? Since it's persistent desktops it wil...
See more...
Am I understanding it correctly that you have 30 machines in a dedicated pool. You have several classes of students that need to access these machines? Since it's persistent desktops it will be a 1:1 mapping with a user account so if you want multiple classes to utilize the same desktops you will have to use generic accounts. For example, student1, student2, student3, etc will all have a 1:1 mapping for a desktop in the pool and can be used by multiple classes
Here is the IOS client documentation, https://www.vmware.com/pdf/horizon-view/horizon-client-ios-document.pdf. It says you must have iPhone 5s, 6, or 6 Plus.
You enable it via the Biometric authentication on the View connection server. There is a section on it in the View admin guide page 61. https://pubs.vmware.com/horizon-62-view/topic/com.vmw...
See more...
You enable it via the Biometric authentication on the View connection server. There is a section on it in the View admin guide page 61. https://pubs.vmware.com/horizon-62-view/topic/com.vmware.ICbase/PDF/view-62-administration.pdf
I think the first thing to do is generate a log bundle while the problem is presenting itself. This would be needed if you open a case with VMware and generally may be an easy way to determine ...
See more...
I think the first thing to do is generate a log bundle while the problem is presenting itself. This would be needed if you open a case with VMware and generally may be an easy way to determine the issue. The second thing I would do is revert the last change (certificate) to test and see if that is an easy fix. If you didn't remove the old certificate than you could just switch the friendly name back to it and attempt to start up the services.