A Wonderful Workflow
-
Request: "Install a Windows 10 VM in place X".
Instead of waiting 3 more weeks or so to download the RTM version from MSDN, I have to install the latest Beta build. Reason: "We already told the customer it'll be a beta version".
The external line of place X is incredibly slow. It would take an estimated 3 days to download the ISO, thereby also making external traffic on that site nearly impossible for the customer.
I downloaded the file at my desk - 30 minutes - and FTP'd it over VPN to place X's FTP server. Unfortunately, the VPN also isn't very
trustworthyreliable, so I had to package the ISO in a multi-part compressed file and send it over in a way that I could redo parts that somehow failed. 10 hours and several CRC-errors later, the file was however on the remote site.But the FTP is in the DMZ, so there is no way for me to WinSCP the file to the ESX server. Solution: put an FTP client on a different machine in place X, download the file from the FTP server, and now use WinSCP to finally put the image on the ESX datastore.
Tomorrow I'll do the install itself. I'm curious what obstacles await me then...
sigh
-
The real joy will be when the standalone beta ISO expires and ultimately stops booting on purpose.
If you use a licensed Windows 8 and upgrade it to 10 as part of the beta, it will not expire.
-
The real joy will be when the standalone beta ISO expires and ultimately stops booting on purpose.
No, the real joy will be when it (tries to) auto-downloads the next build.
Also, this seems a case where sneaker-net (USB) would have been faster...
-
Unfortunately, the VPN also isn't very trustworthy, so I had to package the ISO in a multi-part compressed file and send it over in a way that I could redo parts that somehow failed.
Is
rsyncfor Windows still not a thing? A quick google suggests no...
-
-
YOURPC <--- DOWNLOADSERVER
YOURPC --- FTP over flaky VPN ---> FTPSERVER
fail, retryYOURPC --- FTP over flaky VPN ---> FTPSERVERsplit the file
YOURPC --- FTP over flaky VPN ---> FTPSERVERretry
YOURPC --- FTP over flaky VPN ---> FTPSERVERretry
YOURPC --- FTP over flaky VPN ---> FTPSERVERassemble on FTPSERVER
SOMEPC <--- FTP --- FTPSERVER SOMEPC --- SSH ---> ESXSTORE
-
The real joy will be when the standalone beta ISO expires and ultimately stops booting on purpose.
If you use a licensed Windows 8 and upgrade it to 10 as part of the beta, it will not expire.
None of this is true.
To run the beta, you have to be in the insider program. On release, you get upgraded to the full version, but with no official license. This is fine if you're a home user; Microsoft has basically said that they're okay with people running Windows 10 this way, because the cost to them is negligible. However, this is for a business, I assume, and if so, Microsoft will sue them if they don't purchase a license.
-
Unfortunately, the VPN also isn't very trustworthy, so I had to package the ISO in a multi-part compressed file and send it over in a way that I could redo parts that somehow failed.
I assume you meant "reliable" more than "trustworthy" given the rest of your sentence.
The next time you have to do this, do it a bit differently: get a download accelerator like GoZilla or something and download it in 10 or so pieces. I had to do this to get a network driver once--the thing was only 60MB but it was in China behind, I have to assume, a piece of string and two tin cans, based on how slow the download was and how many times it timed out. Download accelerator will automatically open up multiple connections to grab part of it at a time, and automatically retry any failures.
-
No, the real joy will be when it (tries to) auto-downloads the next build.
Well, you can probably turn that off.
-
There's also
ROBOCOPYwith the/Zflag, but it's not all that user friendly. At least it's a builtin since Vista.
-
Ms engineer disagrees
-
Yes, if you continue to run a preview build and don't update, the build will expire. Too bad that has nothing to do with the current situation.
