Click Next.Ĭhoose the Connect to an existing SQL Server Database radio button. The next screens will do the actual Manager installation.ĭéjà vu? Groundhog Day? Now we proceed with the actual installation of App Volumes Manager. The installation up to this point has been a bootstrap of sorts. Not Shown! – You may be presented with a Windows User Account Control (UAC) prompt. Navigate to the Installation directory.Ĭheck the I accept the terms in the License Agreement checkbox (you did read all that, right?) and Click Next.Ĭhoose the Install App Volumes Manager radio button since we are installing the App Volumes Manager. Let’s get started…Īfter downloading App Volumes 4 ( ), mount the ISO to your App Volumes server. I am going to assume that you have some level of technical proficiency if you are this far along in your journey and will not add mundane details like how to mount an ISO or what buttons to click unless following a particular workflow and feel the details are absolutely necessary. If you read and follow the three articles provided, you will not encounter an error when configuring the App Volumes Manager database authentication! Please see the following articles, Configuring Microsoft SQL Server for VMware Horizon View, MSSQL SSL/TLS Certificate Chain Fix, and Adding a Computer Account to MS SQL Server for a VMware App Volumes Manager Database, for more information. I have also added the App Volumes server computer account to the database permissions. I will also mention that I have installed MS SQL Server 2016 and have set up TLS certificates on the Windows guest as well as configured SQL Server to use the certificate. Documentation seems to be almost non-existent regarding the database requirements, besides which version to use, but nothing specific on database settings or user/computer/other authentication settings. I have spent countless hours troubleshooting this and looking for documentation. I will start out this post to mention that if you try to install App Volumes 4 and are stuck on the SQL database portion trying to get Windows Integrated Authentication (WIA) working, you are not alone. Ref: (VMware App Volumes Installation Guide) Verify the computer account is added to the list of logins. On the User Mapping page, Choose the checkbox next to the database being mapped to the user (computer) account (assuming the database has already been created). On the Server Roles page, choose the sysadmin checkbox to grant the role to the user. You can assign it later after creating the database if needed. Select the Default database for App Volumes Manager if it was already created. Choose the Windows authentication radio button.ģ. The dollar sign is necessary to signify the account as a computer and not the name of a user. Do not use the Search… button! Type the Login name: as DOMAIN\computer-name$ Contact your support personnel.This post will probably work for other use cases, but I am specifically needing it for VMware App Volumes Manager.ġ. Module C:\Program Files (x86)\VMware\VMware Horizon View Client\vmwHorizonClientController64.dll failed to register. Contact your support personnel.Įrror 1904. MSI (s) (3C:D8) : Product: VMware Horizon Client - Error 1904. MSI (s) (3C:D8) : Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1904ĬustomAction +vmwHorizonClientController64.dll returned actual error code -2147024770 (note this may not be 100% accurate if translation happened inside sandbox) Can you please help me to figure out how to fix this problem, the objective is to remotely connect to a VDI. I have attached the logs generated during installation. I tried few options like unselecting support for Skype, HTML5 and Teams, changing folder directory, didn't work. I have a problem installing VMware horizon client 5.5.1 in my New Laptop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |