daknetworks.com

Install Windows 10 In-place upgrade on a domain is possible in a couple of ways.

The official way is to use the MICROSOFT DEPOLYMENT TOOLKIT found here: https://technet.microsoft.com/en-us/windows/dn475741.aspx

The other way is through simple network share.

Wait... what? Yes, network share.

STEP 1: get WINDOWS 10 ISO at https://www.microsoft.com/en-us/software-download/windows10ISO

• -you will see 4 options
  WINDOWS 10 (all languages)
  WINDOWS 10 K (Korean law)
  WINDOWS 10 N (European law)
  WINDOWS 10 SINGLE LANGUAGE (1 language only)
• -simply download the one you need. The one that matches what you have now which is probably WINDOWS 10 ALL LANGUAGES.
• -again, since you are doing an IN-PLACE UPGRADE, the ISO must match what's on your system now. Many of the issues people are having is that they are trying to upgrade their system with a WINDOWS 10 PRO SINGLE LANGUAGE when they have WINDOWS 7 ALL LANGUAGES installed on their machine.
• NOTE: do NOT use the MEDIA-CREATION-TOOL for this exercise.

STEP 2: mount WINDOWS 10 ISO

This means show the files that are in the ISO. Windows 7 cannot do this without some help such as WINRAR, 7ZIP or VIRTUAL-CLONEDRIVE. WINDOWS SERVER 2012, WINDOWS 8.1 and newer can do this without additional software. This can happen either through the GUI or through POWERSHELL command MOUNT-DISKIMAGE.

There is no correct way on how you mount the ISO, just do it.

STEP 3: create the network share

Create the share:

• md C:\installs\os\win10x64\unpack

And share it so everyone can read it (outside the scope of this article post).

STEP 4: copy the ISO contents onto a created network share.

I use ROBOCOPY to do this. It is built into WINDOWS 7 and newer. Something like:

• robocopy /e f:\ C:\installs\os\win10x64\unpack

STEP 5: Build your install package

Pretty easy when you know what to do it right.

• -select the setup.exe on the network share. Something like: \\myserver\installs\os\win10x64\unpack\setup.exe
• -type in the parameters: /auto upgrade /Compat IgnoreWarning /installfrom c:\Windows\AdminArsenal\PDQDeployRunner\service-1\exec\sources\install.wim /dynamicupdate disable /showoobe none /quiet
  NOTE: if you would like, you can save the log files as well. Add the following to the end of the parameters above: /copylogs \\myserver\installs\os\win10x64\logs
• -checkmark "Include Entire Directory"
• click PACKAGE PROPERTIES
• make sure the COPY MODE is changed to PULL (not PUSH).
• checkmark "use custom timeout" and change the number to 240.
• save the package.

STEP 6: deploy on test victim.

That should do it!!! If the test pc works, deploy to the rest of the pc's how you see fit.

==============================================================

If for some reason the above PDQ package fails, you can create a .bat file and fill it with following (adjust as necessary):

:: MAKE DIRECTORY.
md c:\installs\Windows10x64

:: COPY FILES.
robocopy /MIR \\myserver\installs\os\win10x64\unpack\ c:\installs\Windows10x64

:: CHANGE DIRECTORY.
cd c:\installs\Windows10x64

:: START THE IN-PLACE UPGRADE (OR CLEAN INSTALL).
start /wait setup.exe /auto upgrade /Compat IgnoreWarning /installfrom c:\installs\Windows10x64\sources\install.wim /dynamicupdate disable /showoobe none /quiet

• Save this .bat in \\myserver\installs\os\win10x64\unpack\
• Then create a PDQ package with this bat.
• Deploy as you see fit.