Okay, so that is Run command.
Let's see, another thing I want to show you is resource health.
So if we look under Resource health,
this gives us a great insight into the availability of the machine.
Of course, we want an available status, so there's no known Azure platform
problems, and then we can look at the history over the last four weeks
here, whenever there might have been an event.
Oftentimes, you'll find these are customer initiated,
if a VM has stopped, restarted, that kind of stuff.
But then sometimes, there may be a Microsoft
platform issue to be aware of as well.
Diagnose and solve problems.
Where does that bring us?
That brings us into the troubleshooter here where we can take a
look. This is quite a few troubleshooters,
wow! A significant list of them, as a matter of fact. Close out of there.
And then lastly, I had mentioned the importance of alerts, that you
can set alerts on just about any event that happens in your
subscription. You can set an alert so that you have code run or you do
notifications whenever a resource health or alert rule fires, and you
can come down here and customize the conditions of what you're looking
for, etc., etc.
You know,
because I know, as much as any IT professional, that if you
turn on too many alerts and notifications,
it can easily be a situation where you grow numb to them.
I really know that one intimately.
Finally, let's come back into the VM, and let's go back to
Serial console and give that another try. Now that we've
worked around, there we go.
So this is replicating what you would see if you plugged in literally an
RS‑232 cable into the serial port on the back of the hardware.
And it brings us to a simple console interface.
And we can just do a ch to do a channel listing. Right now, there's
just one channel, 0, for the serial console itself, but if we want to
get into a command prompt in PowerShell, we can start a command channel
by typing cmd, and then we can do ch to get a channel list. Ch ‑? is
going to give us syntax help, but before I do that, look at that list
there. It looks like our command channel is channel 1, so keep that in
mind.
Why?
Because in order to switch to a channel by its number, we do ch ‑si,
and then the channel that we want to switch to.
So in my case, it's ch ‑si 1. Okay? Let's press Enter to continue.
We're asked to authenticate with a credential on this machine. I'm
trying to think if this VM is a domain controller.
I don't believe it is.
I don't believe it's a domain member, so I'm going to ignore
Domain, and let me type my password carefully. Hopefully, I'll get it right the first try.