[Bug]: Certificate server installation fails randomly

[mfgjwaterman]

Description

At random intervals my script fails at the installation of the CA. Closer inspection of the certocm ca installation log file reveals this error message:

Enterprise CA option availability status: ENUM_ENTERPRISE_UNAVAIL_REASON_DS_UNAVAILABLE

Indicating that the DC cannot be located at the time of installation. The script continues but the CA installation fails.
powershell_support_pack_2023_06_05-21_45_40.zip

Security-Lab.txt
Failed - logs.zip

Steps to reproduce the issue

Run the script a couple of times and it will fail. Like 1 in 10 will error out. Script is attached. I tried to find the root cause for a couple of days but I'm out of options.

PowerShell Version

Name                           Value
----                           -----
PSVersion                      5.1.22621.963
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.963
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

AutomatedLab Version

Name                      Version
----                      -------
AutomatedLab              5.48.0
AutomatedLab.Common       2.3.17
AutomatedLabDefinition    5.48.0
AutomatedLabNotifications 5.48.0
AutomatedLabTest          5.48.0
AutomatedLabUnattended    5.48.0
AutomatedLabWorker        5.48.0

[mfgjwaterman]

I fixed it! This week my single client (Win10) also started behaving differently. A machine would successfully install, but de DefaultUser0 would remain active. Manually logging in and restarting (The script would also never finish), did the trick. That got me thinking.... What I've done is installed the latest version of PowerShell (7.3.4) and executed the same script from the shell, instead of ISE with 5.1. That worked consistently. I did the same for the attached script and I now get consistent success results.

Hope this info is useful. Case closed as far as I'm concerned.

[raandree]

Thanks for letting us know, @mfgjwaterman. Just to be sure I have got this correctly: Was the script execution consistent in the ISE or PowerShell 7?

[mfgjwaterman]

In PowerShell 7 and in VS Code with PowerShell 7. In ISE with PowerShell 5.1 it failed.

[stale]

This issue has been automatically marked as stale because it has not had activity from the community in the last 30 days. It will be closed if no further activity occurs within 10 days. If the issue is labelled with any of the work labels (e.g bug, enhancement, documentation, or tests) then the issue will not auto-close.