4 Replies Latest reply on Jul 2, 2015 3:08 AM by amagi

    Windows 10 Deployment




      We are currently trying to deploy Windows 10 Tech Preview in anticipation of the full release.


      At the moment I'm try to install it via mapping a network drive. Creating a task with dependent packages + setup.exe as the main installer doesn't work either.


      Script Here

      net.exe use I: "\\*servername*\packages\Windows 10" /persist:no

      "I:\Setup.exe" /Auto:Upgrade /NoReboot /DynamicUpdate Disable

      net.exe use O: /d


      When the batch task is kicked off Disk activity on the test machine increases as expected, after around 5 minutes or so, the activity stops and setup.exe etc are still open in task manager (see below).


      No UI pops up, however, the network drive is mapped.


      Currently running LD 9.6 SP2.


      I'm unsure if anyone else has tried installing Win10 but all feedback would be appreciated.

        • 1. Re: Windows 10 Deployment

          Please note, when command window is ran from the location of the files UI appears and can complete installation.

          • 2. Re: Windows 10 Deployment

            What happens when you kill the process?  Does the Provisioning Template continue?  It looks like setup.exe is waiting for some input but it is running as System and so its not going to give you any UI.  With your script ending on Net Use then as long as that finishes successfully it should show up as successful. 

            • 3. Re: Windows 10 Deployment

              When I kill the process tree setup.exe will close down (as you expect) however it will go back to the task, sometimes saying failed, some saying success. I'm not sure whether it will need an answer file as when launching it through cmd locally boots the upgrade?

              • 4. Re: Windows 10 Deployment
                amagi Expert

                You are upgrading an existing OS with a software distribution package, not using provisioning template.

                If you want to understand what is going wrong you shuold run the task with different credential (you can set another user under the packages options).

                If you log on the target machine with the same credentials you can view the UI (maybe is still waiting for a mouse click, but the user "SYSTEM" doesn't have the desktop, so...no UI visible)