Recent content by harshkapadia


  1. Can't Run Custom Script through `autounattend.xml`.

    I am using microsoft-windows-shell-setup-firstlogoncommands-synchronouscommand and setting the correct execution order. Even then, I tried chaining all the three commands into one as mentioned in the previous post by garlin and it did not run at all. The NAS wasn't mounted as well. (My user is...
  2. Can't Run Custom Script through `autounattend.xml`.

    Okay so I'm now running the following commands through FirstLogonCommands in autounattend.xml. Output as see in the Windows VMs at C:\Windows\Panther\UnattendGC\setupact: 2024-05-13 10:55:37, Info [Shell Unattend] LogonCommands: Set command 'NET USE X: \\nas\mailbox...
  3. Can't Run Custom Script through `autounattend.xml`.

    Does anyone have any ideas on what can be done? Do you have any ideas, @hsehestedt? (Sorry for tagging.)
  4. Can't Run Custom Script through `autounattend.xml`.

    I tried using EnableLUA = 1 in the VMs, but that didn't change anything.
  5. Can't Run Custom Script through `autounattend.xml`.

    I'm using EnableLUA = 0 in the VMs, but not on my physical machine.
  6. Can't Run Custom Script through `autounattend.xml`.

    I just tried the 2nd method mentioned above (post #5) and that didn't work as well. I still get the 'Open File - Security Warning' dialog.
  7. Can't Run Custom Script through `autounattend.xml`.

    I tried all the following in a command prompt with Admin permissions, i.e., an elevated command prompt. I checked both the VM and my physical machine by executing the mk-dir-test-2.cmd file (as shown in the first post) directly from the NAS using the \\redacted\mk-dir-test-2.cmd command and it...
  8. Can't Run Custom Script through `autounattend.xml`.

    Where exactly do I have to run the Unblock-File commands? I tried putting them as individual steps directly in the SynchronousCommand section after the trusted zone addition script and before actually calling the two scripts, but that didn't work. I got the same security warning dialog. Uhh...
  9. Can't Run Custom Script through `autounattend.xml`.

    Pictures of Registry Editor in the VMs with the NAS values set.
  10. Can't Run Custom Script through `autounattend.xml`.

    Thank you for your advice, @garlin! The trusted location IP address script added the NAS IP to the registry, but I got the same error as in the first post in this thread, the 'Open File - Security Warning' dialog. In fact, this time I was not able to run both, the mk-dir-test-2.cmd script as...
  11. Can't Run Custom Script through `autounattend.xml`.

    Hello, I am creating Windows 11 Pro VMs the unattended way using autounattend.xml. I am able to successfully install Windows. I am now trying to map a NAS/network share persistently on startup and am also trying to install some software on startup, but am unable to. I either get an error or the...
  12. Solved Autounattend Install <ProductKey> Setting Cannot be Read from Answer File

    Thank you all, this worked for me. A combination of @garlin, @hsehestedt and @Kari's advice and tutorials helped. The modified tutorial that @hsehestedt mentioned in another thread of mine: Unattend.xml Missing on Booting.
  13. Solved Unattend.xml Missing on Booting.

    I saw that doc and read it. It still didn't help me understand that if I want an unattended install, I need to name the file autounattend.xml, not unattend.xml and should place the file in the root directory, not in the Windows\Panther directory. I also couldn't find a doc that told me that I...
  14. Solved Autounattend Install <ProductKey> Setting Cannot be Read from Answer File

    Oh okay, I didn't realise that there needs to be a KMS server on the network. Sorry! I definitely don't care about licensing the Windows 11 Pro VMs that I'm creating, because they're going to be used for relatively short durations. I just tried three installations: - Removed the ProductKey...
  15. Solved Unattend.xml Missing on Booting.

    Thank you all so much for all the help! I had been struggling with this for quite some time. Just renaming the file to autounattend.xml and placing it at the root of the ISO resolved the issue, without having to mount the ISO or anything like that. I don't think Microsoft's documentation is...
Back
Top Bottom