Timeline for PowerShell Scripts in Windows Unattend Answer File XML
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 23, 2018 at 19:15 | vote | accept | ztmcoder | ||
| Jul 23, 2018 at 19:11 | comment | added | ztmcoder | It is working now. Had to change 'Requires User Input' to false. | |
| Jul 23, 2018 at 18:06 | comment | added | ztmcoder | Doesn't seem to be erroring out now. But the start menu layout does not get applied. Would that be because of Windows not waiting for the command to finish? Also does it matter if the command requires administrator privileges? | |
| Jul 23, 2018 at 16:21 | comment | added | ztmcoder | Ok I see it now. Going to give that a try. | |
| Jul 23, 2018 at 15:49 | comment | added | Appleoddity | You're getting a little confused between these two, similarly named components. There is "RunSynchronousCommand" which is part of the "RunSynchronous" block and windows-deployment component, which is what you are trying to add to oobeSystem which is not possible. Then there is the "SynchronousCommand" under the "FirstLogonCommands" block which is part of the Windows-Shell-Setup component, which is what I'm talking about | |
| Jul 23, 2018 at 15:43 | comment | added | ztmcoder | So whenever I right click on the 'Windows Deployment neutral' It only lets me add it to either Specialize or audit user and not the oobeSystem, which I want to add it to the OOBE System since that is where you should have the Synchronous Command. | |
| Jul 23, 2018 at 15:36 | history | edited | Appleoddity | CC BY-SA 4.0 |
added 541 characters in body
|
| Jul 23, 2018 at 15:17 | history | answered | Appleoddity | CC BY-SA 4.0 |