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
{{ message }}
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.
Details of the scenario you tried and the problem that is occurring
I'm using a Script resource to run a cmd that installs software.
The first run always, always returns an error "No user exists".
After the first run, dsc auto corrects the issue and it works without a problem and the node gets in compliance.
Verbose logs showing the problem
PS>TerminatingError(install-univ-v5.cmd): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: No users exist. Please set up a user."
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Details of the scenario you tried and the problem that is occurring
I'm using a Script resource to run a cmd that installs software.
The first run always, always returns an error "No user exists".
After the first run, dsc auto corrects the issue and it works without a problem and the node gets in compliance.
Verbose logs showing the problem
PS>TerminatingError(install-univ-v5.cmd): "The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: No users exist. Please set up a user."
The DSC configuration that is used to reproduce the issue (as detailed as possible)
The text was updated successfully, but these errors were encountered: