I've tested the win 10 image on my (unlicensed) t01. I'm not sure if the image was supposed to install win10 home or pro, but the end result was an unlicensed win10 home. That is, a trial of uncertain life span...
Regardless of the licensing issues, I do have some notes (in no particular order) to share:
1. You can modify the OEM model info to T01 instead of T02 in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation .
2. Before installing any drivers, make sure to enable .Net 2 in Windows Features:
2.1 WinKey + R
2.3. "Programs and Features" -> "Turn Windows features on or off"
2.4. ".NET Framework 3.5 (includes .NET 2.0 and 3.0)"
A few of the drivers, namely the wifi drivers, have modules that depend on it. Worse, without it you won't be notified of the failure. You'd simply miss the cisco modules and won't know why stuff isn't working
3. The intel z2300 series drivers ragor_ali linked work and of higher release versions. I'm using them but newer releases doesn't mean better so try them first and revert to the previous ones if something isn't working.
4. If you install all the drivers and the wifi adapter is missing, it might be a silent IRQ conflict. That is, the device driver won't even show the adapter isn't there... To solve this, first try to do a hard reboot. If that fails, try another hard booting but with only the minimal peripherals (only a keyboard and maybe a mouse on the otg if you have one. no usb powered hub. no usb-lan dongle, no usb sound card...). Trying to figure out why the RTL8723BS wasn't showing was the only reason I discovered the .Net dependency and it took over 3 hours of trying out random things so I highly suggest hard rebooting before trying out other options.
5. When you first boot, after the WinPE ghosting finishes, you'll be landed into the T02 factory's KMS deployment stage. You'll be logged into Administrator and have a few batch files shortcuts on the desktop. There will be a popup-window with a few options and a reboot button to press (instead of Next\Done). I check-boxed Generalize and pressed reboot.
Just for general information, the installation copied the KMS activation and bios utilities into c:\tools and placed a few shortcuts on the desktop for activation stages. A factory line worker (usually called "runner") would have the Meegopad linked to a local lan and a KMS server to activate the device. By following the batch files as their ordered names suggest, the device would produce a device dependent hash key, send it to the local KMS server that's linked to Microsoft's key dispatching servers, receive a bios key, and burn it into the bios.
I'm explaining this to both inform, and discourage people who don't know about all of this from messing around with these tools. It's quite trivial to brick a device by burning an incompatible firmware. Besides, while there are KMS software exploits to activate windows 10, the tools provided here are only the client side for burning the bios and are useless without a legitimate server that's connected to Microsoft to receive keys.
Anyhow, I'm happy to say the image is clean of unnecessary software. My T01 came with a Chinese antivirus, cloud storage solution and some other useless stuff for people who don't speak Chinese and don't live in China back when it had windows 8.1. So installing a clean win10 is nicer
As a final side-note, I've run the T01 using Debian 8\7 for over a year using the stable (3.16 now I think) 64bit kernel and 32bit uefi bootloader (multiarch net install iso) without any unusual issues. It didn't support WiFi or sound so I was using a powered hub, usb sound card and a lan-usb dongle. The system was working nicely enough and had weeks long uptimes I only interrupted when rebooting after updating kernels. Newer kernels will cause the system to freeze and become unresponsive forcing a hard reboot by detaching the power cord but debian will be backporting security patches and firefox versions to this kernel until 2020 so it's completely fine to stay with the stable branch and the 15$ worth of peripherals I was using.
Otherwise, the system run fine with the exception of video playback in the browser (firefox). Since I was streaming from a local NAS using VLC and an NFS mount from a local NAS server, it didn't bother me. The only reason I decided to install windows 10 is because I already deleted win8 a while ago and I'm gifting the device to someone who needs the wifi and doesn't have a clue on how to maintain a Debian install. I would also recommend midori browser since it's faster then firefox and minitube, livestreamer and vlc for working around local and remote video playback.
Note that kernel lower then 4.3 but higher then 3.16(debian stable) don't support the internal SD card reader and are extremely unstable, while kernels newer then 4.3 are just unstable So, you're better off with debian stable until something changes.
Good-luck out there,