Well, I saw or received an email for this Virtual IOT Bootcamp sponsored by Hackster.IO, Microsoft and Raspberry PI: https://blog.hackster.io/microsoft-hackster-and-raspberry-pi-launch-virtual-iot-bootcamp-a0b58280813b#.499wu6ntf
It was a 3-day Online Training course in March 28-30th 2017, 7:30am - 2:30pm PST, for makers and the enterprise individuals (I have many days of vacation that I must use) that involved hardware and IOT stuff. I had been interested and the cost seemed reasonable - $200 a day/track or $300 total for both tracks. Best of all, you get $570 (list?) worth of technology to keep. And if you're lucky, there was even a 25% discount code that was also emailed (in my case, received after I had rushed to sign up before it filled up with participants). There were scheduled guest speakers and many hands-on labs to learn.
- Makers: Seeed's IoT Kit + the Raspberry Pi
- Enterprise: Intel's compute stick
Registered to both tracks? Get all 3 kits
Due to me not receiving "25% code" initially and thus requesting the discount to be refunded, I did have an initial administrative ordeal to overcome so that I would have ALL required hardware delivered on time. So far, I have received the Intel Compute module but I was told the rest of my hardware was being shipped yesterday. So far, 4 emails to 2 different individuals (I hate emails to address something that one 5 minute phone call can straighten out) and 3 phone calls to the Microsoft Agent who was coordinating these activities.
Today is 2/16/17, I have already downloaded the Raspberry Pi Raspbian image 1-11-2017 (https://downloads.raspberrypi.org/raspbian_latest). So now to pre-stage that 32GB SD card using Win32DiskImager (https://sourceforge.net/projects/win32diskimager/files/latest/download) for when my next Raspberry Pi 3 arrives along with the Grove kit.
While I waited, I installed the Windows 10 Enterprise Preview from: https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewadvanced and used the Windows USB/DVD Download Tool to create a bootable Windows 10 Enterprise media to install on the Intel Compute module onto a 16GB Sandisk USB stick.
Be advised that the Intel Compute Stick requires an USB Mouse and Keyboard and a HDMI monitor. I did have an issue with my "default resolution and frequency" upon reboot (after complete setup!!) that yielded a black screen. The Windows 10 boot was select 64hz but "optimum was 60hz" for my monitor. Solution - leave the monitor powered off initially, for a minute or so, then all's well.
I hope I haven't gotten ahead of myself by doing this step today and not during the IOT Bootcamp.
After the Windows 10 Enterprise ISO was downloaded onto the 16GB USB stick, I installed the stick into the available USB 3.0 port on the Compute Module and powered ON the Compute module. This was a "normal" Windows 10 build; the only issue(s) I had was figuring out how to enter my "Windows Online Account info" into the login screen instead of creating a "Local" account.
Once the login account is created and Internet WiFi login is completed, the build will connect and try to download updates. I tried unsuccessful the 1st time. I don't know why it initially failed, but by "skipping" that step and allowing the system to complete my desktop environment build, it did connect and update itself, however, it can't activate!!
I am still required to download, setup and create a Skype for business account as well as Microsoft Azure free account but these will be created a week before the course in March 28th to 30th because of a time-out period.
On Friday, 2/17/17, I received the rest of my kit: Raspberry Pi and Groove kit; but the shipping wasn't nice.
There were issues with coding in the labs. I needed a desktop to do coding, a laptop to display the lab, and a TV connected to another laptop for the "not so live stream".
I was able to do the coding following the lab guide, but needed to stay up all night each of the 3 days to do so. The Microsoft Azure Labs caused much frustration days later when I discovered that the examples were running in the cloud and using the free $200 of Cloud time even though my computers were off. This wasn't made clear to the participants either that found out as I did. I complained that this was a security issue, as well. I'll never do that again.
I did learn a bit. but I did become quite frustrated and vowed never to do it again.