Explore Windows 10 IoT shell

- [Narrator] Let's take a look at the capabilities of the IoT Shell now that we've got connected up to our Windows 10 IoT core device. You can get device info. There's a command line access. There's a way to get to the tutorials, which is what we're going to do in order to run Blinky. There's settings. And, there's power management. So, let's go take a look. Here I am, connected up to the Windows IoT device, using the Windows IoT Remote Client. And, we'll go through and look and see what's going on here. So, the device info, this is the screen that shows you how you're connected, you're IP addresses, your device name, which network you're connected to, which version of the operating system you're connected to, and what devices, especially USB you have connected.

The command line, as we already saw, is very very similar to PowerShell. And, if you don't want to remote into PowerShell, you can connect up by physical keyboard and a mouse and run. It's a little flaky which is why PowerShell was so much better. But, it's getting better over time. And, you can run this with or without the Remote Client. I'm using it with Remote Client right now in order to be able to capture this video. But, you can plug that USB keyboard and mouse directly into your Raspberry Pi or other device and completely run it without having your development system functioning at all.

Tutorials gives you a list of prebuilt things you can go ahead and run such as Blinky and a variety of other things, which is what we're going to do to validate our hardware. Shows you the current time of day and date. And, then, there's a modest settings capability. You can specify which language you want and which keyboard layout you want. You can select a direct ethernet connection or, you can use one of the wi-fis that's available to you. And, finally, you can turn Bluetooth on and off. Right now, as I'm recording this course, interacting with Bluetooth devices is a little bit clunky in Windows 10 IoT.

However, the next release is going to have full capability to allow you to create both Bluetooth peripherals and Bluetooth central devices using the G-A-T-T, GATT profile mechanism. This UI here will probably change at that point because you won't have to pair every single device. Right now, as of 14393, the version of Windows 10. 10.0.14393, only supports being a Bluetooth central and requires you to pair with devices that have pairing capability. Alright, that's a quick look at the device portal.

Now, let's go ahead and run Blinky. In order to enable remote screen access to your IoT device, you have to go through the device portal so, you begin by coming to the IoT dashboard. Right click on your device. Select open in device portal. When you do that, it's going to ask you for your administrator credentials. So, put in Administrator and our administrator password for our IoT device. And, there we go. We won't save that. But, this particular web page, which is actually running on a server, on your IoT device, allows you to connect up and configure everything pretty much like you could with PowerShell except without having to do all of the typing.

In our case right now, the main thing we want to do is enable remote access. So, we're going to come back here and enable the Windows IoT Remote Server. Click Ok. And, there we go. It's enabled at boot and currently running. In order to access this screen, you need to download from the Windows Store, a particular Beta app, that allows you to access your IoT core device. The link is right here on the screen. So, it's called Windows IoT Remote Client. It's a standard store installation so, there's nothing magic about that. I've gone ahead and already installed that on this particular box. So, I'm going to go ahead and run it.

And, then, I can select my discovered device. And, click Connect. And, there we go. We're remotely connected to our Windows IoT core device.