Engineer's Notes

A year or so  ago I deployed an internal portal of our company based on SharePoint 2016. We were starting to use AlwaysOn on our SQL servers, but I was not sure if this would be applicable for the SharePoint 2016 and decided to use one of the SQL servers of this AlwaysOn group to store SharePoint databases. It was running fine but the need to move the content databases as well as service applications databases to the AlwaysOn arised a couple of weeks ago. That meant that these databases would stay on this server and their copies will appear on the second SQL server. AlwaysOn group listener appears as a separate SQL server, so this database move will look like a move to another database server. First of all to get the list of all databases we will run a PowerShell cmdlet: Get-SPDatabase | ft Name,DatabaseConnectionString You can see all the databases that reside in this SharePoint 2016 deployment. Some of these databases are Content databases, while the others are service application

When you create a pool in VMWare Horizon View Administrator console you are able to modify the settings of this pool. However, some options may be grayed out and you would not be able to modify them using the web interface. I ran into that during the re-creation of one of the pool. I have set the option "Allow users to choose protocol" to Yes, while it was required to deny the protocol selection. I tried to find a way to change this option and noticed the following VMWare forum topic:  Cannot change Remote Desktop-Protocol . There is an answer from one of the forum members who described the method to modify pool settings using ADSI editing tool. You will need the following article to be able to connect to ADAM Database of VMWare Horizon View:  Connecting to the View ADAM Database (2012377) . Using this article I was able to connect to the ADAM Database and to find the required parameter by comparing its values with the values of another pool. The name of the attribu

During the PoC project of VMWare Horizon View 7.6 for our customer we have noticed quite a weird issue with the View agent. In short, after the installation of View agent 7.7, any Windows 10 golden image gets into automatic repair state and is not able to boot normally. This issue had been reproduced on Windows 10 1803 and Windows 10 1809 LTSC. While this problem arises with Agent 7.7, there are no issues with Agent 7.6. In addition, the main reason is Persona Management component. You will not experience the issue if you are not using Persona Management in your environment. We have been testing desktop pools with the View Agent 7.6 and Persona Management and all the desktops were working quite good. All the golden images are configured using Local GPOs to define the settings of View Agent software, including the Persona Management component. Unfortunately, we were not able to use Domain GPOs for these VMs and VDI desktops due to some security restrictions of the customer. My colleag