You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Run the script a couple of times and it will fail. Like 1in10 will error out. Script is attached. I tried to find the root cause for a couple of days but I'm out of options.
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.
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.
stalebot
added
the
Stale
The item has been there for a while and not updated. Quite soon it will be closed.
label
Aug 12, 2023
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
PowerShell Version
AutomatedLab Version
The text was updated successfully, but these errors were encountered: