deploymentresearch / hydrationkitws2022 Goto Github PK

I have updated the following files

ConfigurationFile.ini - line 147 with SQLSYSADMINACCOUNTS="TIMBO\Administrator" "BUILTIN\Administrators"

Install-HYDSQLServer2019.ps1 - line 133 with $OriginalSQLSYSADMINACCOUNTS = "SQLSYSADMINACCOUNTS="TIMBO\Administrator" "BUILTIN\Administrators""

Note that CU15 (SQLServer2019-KB5008996-x64.exe) is in the Updates folder

But there seems to be an error displayed as indicated in attachment

Any help, much appriechated

Regards

Tim

During the Initial hydration when copying over the Applications (xml control file) - that control file is missing several of the applications.
So while the source files all copy over the applications are not being populated correctly in the deployment workbench.
All applications for DC01 are there, but the CM01 is missing several applications.

Step 3.4 in the guide says "Copy the Windows ADK 11 WinPE Addon setup files (3 GB) to the following folder:
C:\CMLab\DS\Applications\Install - WinPE Addon for Windows ADK 11\Source". The correct path to place the files in is "C:\CMLab\DS\Applications\Install - Windows ADK 11 WinPE Addon\Source". The screenshot is correct, but the text is wrong.

Steps 3.5 and 3.6 in the guide mention the path "C:\CMLab\DS\Applications\Install - SQL Server 2019\Source". The correct path based on the folder created by the script is "C:\CMLab\DS\Applications\Install - SQL Server 2019 Standard\Source". The screenshots are correct, but the text is wrong.

This is a minor issue and easily fixed.
However I wanted to report it.

When the Deployment starts on VmWare the following errors occur:

Hello,

I have recently setup a new Lab comprised of DC01 and CM01, however checking the memory settings limit in SQL Server, they were not set at all.
Looking at the BDD log file for this step it states "Application Configure - Set SQL Server Memory Usage returned an unexpected return code: 1".
Looking at the application's wsf script (Configure-SQLServerMemory.wsf) I spotted that the osql.exe runs from "C:\Program Files\Microsoft SQL Server\120\Tools\Binn\osql" instead "C:\Program Files\Microsoft SQL Server\150\Tools\Binn\osql" that is set in SQL Server 2019.
I will create a pull request also about it.

As mentioned in Pull request #16.