Replies: 2 comments 6 replies
-
same problem here |
Beta Was this translation helpful? Give feedback.
5 replies
-
@checkitsedo I was checking at the customer side --> both scheduled tasks are running with SYSTEM. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When running Start-OOBEDEPLOY (after installing and importing OSD module) as part of a TS in the OOBE phase I get the error above. I would assume the cmdlet is part of the OSD module no? googling it does point to the Start-OOBEDeploy script but not much further.
any help?
Here is the full script
Beta Was this translation helpful? Give feedback.
All reactions