►
Description
Are you struggling to keep track of your hybrid infrastructure? In this video, Matthew Dowst, Managing Consultant for Quisitive, shares his expertise on using PowerShell to manage your hybrid environment with Azure Arc. Learn how to execute scripts on remote servers and keep track of your local and cloud environments using PowerShell. This is a must-see for anyone looking to streamline their hybrid infrastructure management with Azure Arc and PowerShell.
Matthew Dowst will provide you with some tips and tricks on how you can use PowerShell to ease the burden of managing a Hybrid infrastructure.
Meeting Description:
With today's hybrid infrastructures, being able to keep track of everything is becoming increasing difficult. Microsoft has introduced Azure Arc to make managing Hybrid environment much easier, but it still can be a burdensome task. But we can do better!
Matthew Dowst will provide you with some tips and tricks on how you can use PowerShell to ease this burden of managing a Hybrid infrastructure. We'll look at some different ways you can execute a script on remote servers and how you can use PowerShell to help keep track of your local and cloud environments.
Speaker Bio:
Matthew Dowst is a Managing Consultant for Quisitive. Matt is passionate about all things DevOps and automation, utilizing multiple different technologies, but PowerShell is my passion.)
A
Good
evening,
ladies
and
gentlemen,
welcome
to
the
Research
Triangle
Powershell
user
group
tonight
we're
going
to
be
talking
about
managing
hybrid
infrastructures
with
Azure,
Arc
and
Powershell,
but
before
we
get
started,
let
me
say
hello
to
my
co-host:
Phil
Bossman,
hey
Phil!
How
are
you
I'm
doing?
Well,
Mike,
it's
it's
a
good
time
tonight
and
who
is
our
speaker
this
evening.
B
Well
tonight
we're
having
Matt
daoust
and
he's
a
managed
consultant
for
acquisitive
and
Matt's
passionate
about
all
things
about
devops
and
Automation
and
then
using
multiple
Technologies.
Powershell
is
one
of
them,
but
certainly
Azure
Arc,
and
you
know
devops
overall,
so
really
excited
to
have
you
Matt
welcome
thanks,
hey
Matt.
C
Talking
about
Azure,
Arc
and
and
Powershell,
and
essentially
how
you
can
manage
your
entire
infrastructure
through
you
know,
just
a
couple
of
simple
scripts
to
be
able
to.
You
know,
connect
to
all
your
different
machines
and
devices,
whether
they're
in
Azure-
and
you
know,
in
other
clouds
or
on
premise.
A
C
Yes,
so
background,
you
know,
just
you
know,
assistant
administrator
working
as
a
consultant
I
have
a
went
into
automation,
the
Chief
Architect
of
our
managed
automation,
solution,
acquisitive
and
yeah.
The
large
part
of
that
is
managing
hybrid
infrastructures.
You
know
we
try
to.
You
know,
focus
on
you
know
one
technology
or
another,
but
you
know
once
you
start
getting
out
there
in
the
field,
you
see
that
everything
is
is
everywhere.
C
C
A
So
we're
gonna
turn
it
over
to
you.
Ladies
and
gentlemen,
we
hope
you
enjoyed
the
presentation
if
you're
joining
the
Research
Triangle
Powershell
users
group
for
the
first
time
in
YouTube,
check
out
our
Channel.
We
have
plenty
of
other
videos,
but
right
now
we're
going
to
focus
on
Mr
Matt
and
take
it
away
thanks.
C
Guys
so,
as
I
mentioned,
you
know,
the
the
purpose
here
is
to
really
kind
of
show
how
Azure
Arc
can
be
used
as
the
next
level
in
remote
Powershell
management.
Right.
So
just
kind
of
you
know
the
quick
history
on
that.
You
know
Powershell
five
one
was
you
know
based
on
WS
man.
It
was
Windows
only
you
know
with
Powershell
seven,
they
added
the
you
know
open
SSH,
which
allowed
you
know
cross-platform,
but
still
you
know
you
have
to
be.
You
know
able
to
locally
talk
to
all
those
machines.
C
C
When
Azure
came
along,
it
really
kind
of
changed
the
platform
because
they
introduced
The
Run
command,
which
allows
you
to
run
a
command
directly
inside
an
Azure
VM
from
essentially
anywhere
that
you
have
a
you
know:
Port
443,
open
on
and
now
a
an
extension
of
that
which
Microsoft
introduced
last
year
and
has
recently
come
out
of
preview
is
azure
Arc.
What
Azure
Arc
does?
Is
it?
It's?
C
A
agent
based
that
goes
on
to
your
local
machine
and
it
provides
you
a
lot
of
the
capabilities
that
you
would
receive
as
if
it
were
an
Azure
VM
right.
So
this
VM
could
be
in
AWS.
It
could
be
in
a
psphere
cloud.
It
could
be
on
hyper-v,
it
could
be
a
physical
box,
it
doesn't
matter
as
long
as
it
can
talk
to
azure
you
can
receive.
C
So
we'll
kind
of
see
here
how
you
can
get
that
kind
of
prep
your
environment
for
being
able
to
create
this,
and
a
great
example
of
this,
this
these
scripts
I'm
going
to
show
I,
originally
wrote
when
log
4J
came
out
right,
because
we
had
lots,
people
asking
hey,
we
have
machines
everywhere
and
it's
log4j,
it
was
affecting
Windows,
it
was
affecting
Linux.
You
know
how
can
we
search
across
all
of
these
devices
and
can
get
a
Consolidated
report
back
on?
C
You
know
what
machines
may
be
affected
and
our
customers
that
had
Azure
Arc
it
was,
it
was
simple.
You
know
we
half
a
day
had
a
script
up
and
running
and
scanning
their
entire
environment
coming
back
and
checking
all
of
their
devices
for
any
log4j
vulnerabilities.
You
know,
which
include,
checking
Registries
checking
installed,
applications,
actually
file
level
searches.
All
of
those
type
of
things
such
anything
that
you
could
do
with
a
Powershell
script.
You
can
now
do
on
any
remote
sheet
that
you
have
in
there.
C
So
another
before
Azure
Arc,
another
way
to
be
able
to
do
this
was
kind
of
through
hybrid
run
book
workers
through
the
Azure
automation
platform
and-
and
these
are
these
still
do-
play
a
a
really
strong
role.
They
they
have
a
lot
more
capabilities
than
what
you
would
have
with
Azure
Arc
script
session
so
similar
in
the
way
that
it
works.
There's
an
agent
on
the
machine.
You
register
the
machine
with
azure.
C
However,
when
you
build
a
hybrid
run
book
worker,
it
has
the
full
capabilities
of
azure
automation,
which
includes
the
built-in
key
vaults
variables,
all
those
type
of
things
in
all
your
different
run
books
a
little
balancing
stuff
like
that.
So
that's
that's
really
for
building
a
fully
automated
solution
right,
something
that's
going
to
run
over
and
over
and
over
again.
C
What
we're
going
to
talk
about
today,
the
Azure
VM
run
commanded
the
arc
script
extension
or
more
of
your
ad
hoc
type
situations
right.
You
don't
have
a
you
know:
systems
management,
integration,
thing
that
you
need
to
get
out
to
different
environments.
You
know
you
have
gpos
can't
go
out
to
your
Linux
boxes.
Those
type
of
things
right,
so
we're
gonna,
take
a
look
at
how
you
can
use
these
these
two
systems
together
to
really
you
know,
create
that
holistic
solution
there
for
you,
so
the
the
Azure
VM
run
Command
right.
C
If
you
haven't
seen
it,
you
can
literally
go
into
the
Azure
portal,
open
up
a
box
type
in
a
Powershell
command
and
it'll,
execute
on
that
box
and
come
back
and
report
it
to
you.
There
are
two
Powershell
commands
for
it,
which
can
get
kind
of
you
know
it
makes
it
a
little
more.
You
know
people
are
wondering
well,
which
one
do
I
use
right.
So
the
the
invoke
run
command
allows
for
the
add-on
execution,
but
it
is
a
one-time
execution.
So
it's
going
to
go
out.
C
It's
going
to
run
that
script,
the
it's
going
to
sit
there
and
your
machine
is
going
to
spin
the
whole
time
it's
doing
and
it's
gonna
pop
out
the
results
the
set
Azure
run
command,
allows
you
to
actually
send
that
command
to
that
machine,
and
then
it
run
it
in
the
background.
So
you
free
up
your
session,
which
you'll
see
here
in
just
a
minute
to
allow
you
to
continue
doing
other
things.
C
You
know
we
need.
We
need
to
get
a
list
of
our
devices.
We
need
to
get
a
script
to
execute,
we
need
to
execute
the
script
and
then
we
need
to
get
the
results
from
it
right.
It's
you
know,
no
matter
where
you're
running
whether
you're
running
you
know
Powershell
five,
one
WS
man
or
you're
over
in
an
arc.
It's
it's
all
gonna.
That
process
is
gonna,
remain
the
same
all
right,
so
real
quick
before
we
jump
into
the
code,
so
just
kind
of
show.
C
You
know
one
of
the
benefits
of
Arc
here
is
I,
have
Azure
virtual
machines
and
I
have
Arc
server,
which
are
on
on
premise
and
hyper-v
host
all
together
in
one
spot
right,
so
I
can
go
in
here
and
I
can
tag
them.
I
can
apply
policies.
I
can
apply
Defender
Forum,
all
those
type
of
things
right
here
inside
the
portal.
So
actually,
if
I
open
up
a
park,
server.
A
Matt
I
had
a
question
for
you,
yes,
and
so,
when
you
get
to
a
natural
break
here,
you
don't
have
to
do
this
right
now,
but
there's
probably
some
people
that
have
never
seen
Arc
before.
Maybe
don't
even
know
the
premise
right.
So
maybe
if,
when
you
get
an
opportunity,
if
we
can
just
explain
the
overarching
idea
of
what
Arc
is
what
it's
used
for
and
like
the
idea
behind
the
agents
that
you
would
deploy
or
something
like
that,
definitely.
C
So
you
know
the
shark
is
a
way
to
be
able
to
bring
your
on-premise
other
cloud
resources
into
Azure
right.
So
tonight
we're
actually
going
to
look
at
servers,
but
you
can
actually
bring
in
SQL
boxes.
You
can
bring
in
kubernetes
clusters
and
you'll
now
see
in
preview,
where
you
can
actually
join
in
a
VMware,
Center
or
a
virtual
machine
manager
device,
and
what
that'll
do
is
that'll
create
an
object
up
in
Azure
for
all
of
your
on-premise
devices.
So
you
can
then
maintain
all
of
those
you
can.
D
C
A
And
so
just
to
expand
on
that
a
little
bit.
So
it's
it's
agent
based
in
almost
all
cases
right,
yes
and
so
you're
deploying
an
agent
to
machines
and
what
that
agent
is
doing
is
a
Fed
essentially
delivering
the
bill.
The
ability
of
azure
Arc
console
to
act
as
a
single
pane
of
glass
so
that
all
the
important
stuff
that
you
all
want
to
know
about
your
infrastructure
objects,
regardless
of
their
location.
As
Matt
said
on-prem
in
the
Azure
cloud.
D
C
And
Microsoft
has
made
it
very
easy
for
you
to
be
able
to
onboard
devices
in
here.
You
actually
click
through
here
and
it
will
generate
a
Powershell
script
for
you
to
join
all
of
your
devices
into
Arc.
So
getting
them
into
Arc
is,
you
know,
is
the
first
step
in
the
process
and
then
from
there
you
know,
there's
there's
Untold
things
you
could
do
like
I
said
you
can
run
them
through
update
management.
You
can
apply
policies
to
them,
you
can
by
Defender
some
things
have
cost
to
them.
C
Some
are
free,
I,
think
updates
and
policies
are
free,
Defenders
going
to
have
you
know,
charges
behind
it,
but
just
putting
an
arc
server
in
here
itself.
There's
no
charge
right,
so
you
can
put
an
arc
server
in
here,
and
you
know
one
of
the
best
uses
that
that
we've
seen
from
it
is
just
being
able
to
keep
track
of
everything.
C
You
know
if
you
have
servers
that
are
in
you
know,
on-premise
and
in
Azure
it's
it's
hard
to
kind
of
maintain
like
which
ones
where
and
now,
who's
in
charge
of
that
one
and
those
type
of
things.
This
makes
it
really
easy,
because
you
can,
you
know,
like
I
said
you
could
see
them
all
here
in
one
paint,
a
class
you
can
add,
you
know
you
can
add
tagging
to
them.
You
can
manage
them.
C
C
C
Arc
box
has
a
similar
functionality,
but
through
the
console,
it's
not
quite
as
clean.
It
requires
that
you
have
it
your
code
stored
up
in
a
storage
blob,
and
then
it
you
know,
creates
a
connection
out
to
it.
It's
it's
not
the
prettiest
thing,
but
it's
it's
got
it.
There.
You've
got
to
remember
this.
Arc
is
Gen.
One
right
and
Azure.
Vms
are
have
been
around
for
10
years
now.
A
Before
you
get
the
code,
I
got
one
question
for
you,
so
a
gentleman
in
the
chat
was
asking
does
I
I
know
you
mentioned
that
the
the
preview
of
vcenter
management
and
he's
asking
does
it
support
VMware
VMS
and
what
I
think
he's
asking
is?
Can
you
manage
VMware,
VMS,
directly
and
I?
Think
the
answer
is
no.
C
You
you're,
you
are
correct.
I
would
say
that
I
see
it
coming
like.
If
you
look
at
some
of
the
previous
stuff
they
have
in
here,
they
now
have
these
Azure
Arc
virtual
machines,
which
allow
you
to
deploy
a
Azure
image
to
a
local
private
cloud
and
I
know
that
they
before
they
even
got
vmm
in
here
they
got
vcenter
in
here.
So
right
now
what
what
this
decenter
does?
Is
you
install
it
on
the
vcenter
and
it
installs
the
agents
for
you
right
it?
C
Just
it
just
helps
you
and
you
know,
whenever
you
deploy
a
new
item,
it's
going
to
automatically
get
added
in
there.
It's
it
doesn't
provide
you
the
functionality
of
vcenter,
so
you
can't
like
provision
a
VM
through
it
right,
but
you
do
have
the
it.
What
it
will
do
is
it'll
bring
the
devices
into
here.
A
A
Good
yeah,
and
so
the
other
question
in
chat.
Just
this
is
an
easy
one.
I
probably
can
do
it,
but
someone
would
like
to
know.
Is
it
easy
to
install
the
agent
for
a
bulk
of
machines
like
100
or
200,
and,
and
so
Matt
was
just
saying
earlier-
that
Arc
will
provide
us
a
very
generic,
simple
script,
to
get
Azure
Arc
agents
installed
on
the
machines.
You
just
need
a
method
to
deploy
those
scripts,
and
that
could
be
any
number
of
options.
A
C
I
go
here,
enter
all
your
things
and
then
be
like
here's.
Your
script
come
go
run
this
on
your
devices
and
they'll
all
come
in
there
and
I've
I've
never
had
any
issues
with
this
script
running
it
as
always
worked
wonderfully
so
I've
done
it
through
gpos,
I've
done
it
through
config
manager
or
just
straight
through.
You
know,
remote
power
show.
C
As
we
were
talking
about
before
running
a
command
on
a
zure
VM,
it's
really
straightforward.
You
have
the
set
Azure
RM
command
right.
I
just
have
a
simple
script.
Here,
it's
going
to
get
me
back
the
name
of
the
computer
right
when
you're
using
these
set
run
command.
You
also
want
to
give
it
a
run
command
name
and
what
that'll
do
is
that'll.
Allow
you
to
go
then
go
back
and
look
up
that
that
job
at
a
later
time
right.
C
C
C
C
These
jobs
will
auto
update
themselves.
So
we
can
see
this
one
completed
and
then
all
we're
going
to
do
is
go
back
here
and
get
the
Run
command.
So
this
upon
that
name
that
we
created
and
we're
going
to
get
our
results
back,
never
see
that
the
output
view
is
the
name
of
the
box
and
if
there's
any
errors,
those
would
would
all
show
up
in
there
right
on
the
Linux
side,
pretty
much
the
same
exact
thing
there
we
go.
We
have
our
Azure
Linux
server.
C
Now
when
it
comes
to
Arc,
it's
it's
a
little
different
because,
as
mentioned,
there
is
no
command
for
running
in
Arc.
So,
as
you
see
here,
it's
getting
a
little
a
little
hairier,
but
it's
you.
You
write
this
once
and
this
essentially
becomes
your
command
right
and,
as
you'll
see
we'll
we'll
turn
it
into
a
function
here
in
a
little
bit.
But
some
of
the
some
of
the
differences
here
are
the
the
name
here
has
to
be
custom.
Script
extension,
that's
just
the
name
of
the
extension
in
Azure.
C
C
So
with
the
force
update
tag,
does
is
you
know,
but
it
says:
oh
well:
I
have
to
do
tags,
so
that
means
I
need
to
rerun.
It
really
simple,
quick
and
easy
way
to
do.
That
is
get
date
file
time.
That
is,
you
know.
The
number
of
text
instance
I,
hope,
1601
or
whatever
Microsoft
time
starts
at
so
you
know
unless
you're
running
that
command
within
the
same
milliseconds
of
each
other
you're
not
going
to
have
any
collisions
on
that.
C
Another
thing
to
take
into
consideration
here
is
that
you
know
the
command
again
like
similar
to
the
Linux.
It
runs
through
the
shell.
It's
not
running
directly
into
Powershell,
so
you
have
to
include
the
Powershell
Dodge,
exe
or
pwsh,
depending
on
which
version
your
machine
has,
and
then
you
have
to
pass
the
command
well
in
the
in
the
Azure
vm1
they're,
you
know
you
just
pass.
C
A
string
file
is
command,
but,
as
you
saw
here,
we
had
to
you
know,
start
doing
some
Escape
characters
and
things
like
that,
because
it
started
getting
kind
of
you
know
hairy
because
I'm
creating
a
string,
that's
really
a
script,
those
type
of
things
that
could
get
even
worse
because
we
now
have
to
convert
this
into
Json
so
best
way
to
handle.
That
is
to
just
convert
it
to
base
64.
C
right
and
that
that's
going
to
do
is
you
know,
we'll
create
the
string
here,
all
right,
our
system,
environment,
name,
converted
to
a
base64
string
which
is
becomes.
You
know
essentially
an
alphanumeric
there's
pluses
equals
and
things
that
you'll
get
in
there,
but
essentially,
what
you're
not
going
to
get
is
you're,
not
you're,
not
going
to
get
any.
You
know.
C
Single
quotes,
double
quotes,
dollar
signs,
other
other
things
that
will
cause
issues
inside
of
your
command
right
and,
if
you're
not
aware,
Powershell
does
have
the
ability
to
run
base64
encoded
scripts
directly
without
having
to
do
anything
to
decode
them.
So
we
build
our
Json,
they
are
built
into
a
hash
table
and
then
it
converted
into
a
Json-
and
it
looks
like
this-
so
we
have
our
command
to
execute.
C
This
becomes
this
long
alphanumerical
and
no
matter
how
long
or
complicated
your
script
is.
You
know
you're
using
hear
strings
or
any
other
things
that
may
cause
issues
when
trying
to
convert
to
strength.
That's
gonna
take
care
of
it
right
there
for
you,
so
you
don't
have
to
worry
about
any
Escape
characters
or
anything
along
those
lines.
C
Just
convert
that
sucker
to
base64.
and
then
we're
going
to
submit
it
up
to
azure
I'll
get
a
simple
202
telling
us
that
you
know
and
accepted
the
command.
And
again,
you
know
if
we
look
at
the
Linux
side
by
side.
It's
some
slight
differences
in
here
from
the
from
the
windows
side,
but
not
much.
It's
gonna
has
a
different
type
name,
but
everything
else
is
the
same
as
on
this
one:
I'm
using
Windows
7
still
using
the
encoded
command
and
I'm,
submit
that
out
and
I
got
my
202.
C
all
right.
So
now
there
is
a
command
to
be
able
to
return
the
information
that
you
add.
So
there's
this
get
a
z
connected
machine
extension.
So
essentially,
what
this
does
is
it
didn't?
Is
it?
Is
it
installs
an
extension
on
that
Arc
server,
all
right?
So
if
I,
if
I,
take
a
look
at
this
Arc
box
here,
this
is
one
I
just
ran
it
against
and
I
go
into.
My
extensions
I
see
this
custom
script
extension
that
I
just
created
right.
So
it
is
what
it
says
it's
going
to
do.
C
Is
it's
going
to
contain
all
the
information
once
that
yeah
there's
our
there's
our
output
from
the
from
the
command
right
there
all
right?
So
ours
is
our
machine
name
all
right.
So
what
what
this
commandlet
does?
Is
it
you
can
get
back
that
information,
that's
in
there
through
here
right
and
it's
going
to
come
back
in
on
the
status
message
now.
Unfortunately,
if
you
notice
this
latest
message,
this
is
this:
isn't
the
entire
string,
it's
ugly,
they
put
a
bunch
of
other
stuff
in
here.
C
So
unfortunately,
with
the
with
The
Arc
agent,
there
is
some
in
the
string,
manipulation
we
have
to
do,
but
it's
not
too
difficult
to
be
able
to
get
that
built
out
there
right
and
then
the
same
did
the
same
thing
on
the
Linux
side,
for
whatever
reason
they
decided
to
format
it
differently,
it'll
fix
so
but
again,
just
a
couple,
quick,
substrings
and
indexes
and
there's
our
output
data
all
right.
So
you
know
how
can
you
know
we
use
this?
You
know,
there's
there's
a
lot
of
steps.
C
You
know
a
lot
of
you
know
Linux
or
Arc,
and
you
know
all
those
type
of
things
that
kind
of
go
with
it.
So
basically,
let's
take
a
look
at
you
know
how
we
can
kind
of
combine
this
together
into
some
functions,
to
ease
our
life
right
and
this.
So
this
right
here
is
just
a.
This
is
a
script.
This
is
actually
from
a
chapter
of
my
book
on
getting
just
gets
System
Info
right.
It
works
on
Windows.
It
works
on
Linux.
C
So
this
is
what
would
be
returned
from
there,
because
if
you
remember
in
in
all
these
situations,
whether
it's
the
arc,
one
where
you
do
kind
of
have
to
pick
out
your
your
strings
or
the
the
Azure
one
where
it
is
returning
a
string
it
it
is,
is
returning
a
string.
It's
not
returning
an
object.
So
if
you
want
to
be
able
to
parse
the
data
that
you're
returning
all
right,
you
want
to
gonna
go
ahead
and
put
that
in
as
a
Json
or
XML,
or
you
know
other
participle
materialized
text
all
right.
C
So
this
so
I'm
just
going
to
take
this
get
System
Info
script
and
we're
just
going
to
you
know,
use
this
to
run
against
our
other
devices
here
in
a
moment.
So
so
what
we've
done
or
what
I've
done
here
is
just
created,
a
kind
of
a
universal
command
for
the
invoke
VM
command
right.
So
our
difference
between
Windows
analytics
was
not
much.
You
know
it
was.
C
C
D
No
matter
question:
you
aren't
actually
doing
some
intelligence
and
branching
based
on
one
job
versus
the
other
you're
just
running
them
both
against
the
appropriate
OS.
Yes,
that's
correct!
Okay,
because
would
there
be
a
way
in
which
you
would
Envision
that
you
would
Branch
your
code
based
on
the
OS,
so
you
could
do
an
OS
test
and
then
run
one
versus
the
other.
C
So
our
Windows
one
finished
and
we
pulled
back
our
data
on
there
all
right.
So
now
we
can
come
down
here
and
we'll
do
a
similar
thing
again
with
the
with
The
Arc
right
so
again,
Arc
makes
it
easier
because
Arc
actually
has
the
OS
name
built
into
it.
I
don't
know
if
anybody's
ever
tried
to
find
the
actual
OS
information
from
an
Azure
VM,
it's
not
the
prettiest
way
to
be
able
to
to
get
it,
but
there
there
are
certain
ways.
C
If
you're,
you
know,
if
it's
a
Marketplace
one,
what
have
you
but
again
we'll
take
a
look
at
that
here
in
just
a
minute,
so
the
get
as
the
AZ
connected
machine
is
what
gets
your
Arc
devices
right
as
opposed
to
the
get
hash,
get
a
z,
VM
right,
so
Arc
functions
the
same
process
again
here
right.
This
is
that
same
thing
that
we
saw
earlier
for
Windows.
C
You
know
basically,
this
hype
changes,
but
our
Command
execute
changes
and
then
we're
going
to
submit
our
request
added
in
a
little
extra
bit
in
here.
So,
as
I
mentioned,
when
you
do
this
custom
script
extension,
it
has
to
be
named
custom
script
extension
it
it's
just
the
way
that
it
is.
It
is
if
it
already
exists,
all
right
if
I
send
this
put
command
and
then
I
automatically
come
back
out
and
say:
okay,
I'm
done
right
chances.
C
C
So
what
we're
doing
what
I'm
doing
here
is
doing
a
quick
get
the
VM
machine
extension
and
then
checking
if
we
are
in
update,
creating
or
waiting
right,
because
what
happened?
What
will
happen
is
if
this
already
existed,
and
you
check
this-
you
know
the
millisecond
after
this
runs.
It's
going
to
say
success.
C
Then
you're
not
going
to
know
whether
or
not
it
actually
succeeded,
because
that
was
the
previous
run
that
you're
seeing
so
what
you're
doing
here
is
you're
checking.
That
might
say
this
has
changed
to
something
that
sure
of
is
telling
me
that
it
is
processing
it
right
and
then,
of
course,
as
always,
if
you
ever
build
a
a
while
loop
have
some
sort
of
way
to
to
exit
out
of
that.
You
know
if
the
if
it
becomes
on
that
table
right.
C
So
if,
for
whatever
reason
this
doesn't
ever
return
anything,
we
know
that
we're
going
to
go
ahead
and
we're
going
to
exit
after
30
seconds
right
and
then
again
here
we're
just
going
to
have
another
function
to
get
our
state,
so
we
can
check
our
status
and
then
we're
going
to
again
do
some
string
manipulation
to
be
able
to
get
out
our
errors
and
our
our
return.
Data
is
in
any
particular
areas.
Right
I
mean
I'm
sure
most
of
you
on
the
call
are
more
than
familiar
with.
You
know
substrating
index
of
right.
C
C
C
This
is
our
arc
when
22
server
all
right,
so
that's
I
mean
that's
really
it
so
you
can
take
these
three
commands
and
then
you
know
build
out
a
way
to
get
it
to
run
across
everything
that
that
you
could,
particularly,
you
could
potentially
want
right.
So
you
know,
as
you
saw,
you
have
the
get
AZ
connected
machine
for
Arc
boxes.
You
had
the
the
get
a
z
VM
for
virtual
machines.
C
They
both
contain
different
information
in
them
when
they
come
back
so
and
yeah,
as
I
mentioned
before
you
know,
with
the
with
the
the
get
a
z
command
if
you've
ever
looked
at
this
thing,
trying
to
figure
out
what
a
what
OS
something
is
running
is
more
of
a
pain
than
it's
worth
right.
So
yeah
you
have
the
OS
profile,
which
is
the
Linux
configuration
which
works
if
it's
a
Marketplace
machine.
But
if
it's
your
own
custom
machine,
then
it's
not
going
to
work
it.
You
know
I
could
go
on
Ad
nauseam
at
that.
C
I
have
no
idea.
Why
why
they
didn't
do
that,
but
to
to
get
around
that
we
can
use
Azure
resource
graph,
all
right.
So
for
those
of
you
who
aren't
familiar
with
Azure
resource
graph,
it
is
a
it's
another
way
to
be
able
to
query
Azure
resources.
It's
the
uses,
the
causto
query
language,
just
like
Cosmos
and
data
Explorer
and
log
Analytics,
and
you
know
if
you've
ever
noticed
in
a
lot
of
azure
Windows.
Now
you
have
this
open
query
button,
which
will
now
open
an
azure
resource
graph.
C
D
C
It's
not
doing
it
just
to
say
that
it's
SQL
like
because
it
is
actually
a
lot
more
powerful,
but
this
the
syntax
is
fairly
similar
to
writing
a
SQL
query.
All
right-
and
you
see
some
some
of
these
ones
from
Microsoft
get
a
tad
insane,
but
that
allows
you
to
do
here
is
I.
Just
have
a
simple.
You
know:
resources
where
my
resources
are.
C
C
Okay,
unquote-
and
you
get
this
all
the
data
back
on
all
your
machines.
If
you
can
actually
drill
down
into
the
full
details
of
these
and
see
all
the
information
on
these.
Oh
hey
look,
there
was
where
it
actually
says
that
at
the
windows
all
right,
so
what
that
allows
me
to
do
is
just
to
write
a
quick
thing,
and
this
I
mean
this
looks
like
a
lot,
but
it's
not
all
right.
So
if
we,
if
we
actually
break
this
down
real
quick,
we
we're
still
going
on
time.
C
C
C
It
is
the
case
sensitive
language
too,
just
to
be
aware,
but
you
know
in
the
end,
what
it's
going
to
do
is
here's
here's
all
my
VMS
and
and
my
arc
servers
and
everything
you
know
all
in
together
and
I
have
you
know
normalized
data
between
them?
So
if,
if
you
notice,
when
we
when
I,
showed
these
functions
here,
so
the
arc
execution
I
I
kept
these
parameters
the
same
between
them
right.
So
then
it
becomes
even
easier.
C
So
now
there
is
the
search
AZ
graph,
commandlet
I,
don't
know
if
this
commandlet
is
included
in
AZ.
Yet
so
you
know,
if
you
do
the
install
module,
hey
Z,
it
will
install
the
majority
of
the
Azure
modules
this
one
last
time.
I
checked
it
wasn't,
but
it
could
be
by
now,
but
you
can
take
any
resource
graph,
query
running
against
that
and
get
your
return
data.
C
We
want
to
go
ahead
and
pick
it
off.
So
you
know
here's
my
virtual
machines.
Here's
my
arc
devices
I,
don't
need
I,
don't
care.
If
it's
windows
or
Linux
it's
going
to
split
out
on
there.
You
could
even
create
yourself.
Another
wrapper
function
on
top
of
this
to
do
that
automatically
for
you,
because,
as
you
can
see,
the
parameters
are
the
same
right
if
our
job
runs
submitted.
If
we
get
an
error,
we'll
throw
an
error
and
then
essentially
another
little
Loop
down
here
to
get
the
status.
C
So
what
this
is
going
to
allow
us
to
do.
The
big
thing
here
is
that,
if
our
ones
that
are
in
a
running
state
honor
greater
than
our
concurrent
number
we're
gonna
wait.
So
you
know
we're
not
gonna
kill
our
system
trying
to
run
all
of
these
at
once
right.
So
we
can
load
balance.
Keep
this
thing
kind
of
smart
as
it
goes
through.
It'll
kick
off.
You
know
the
different
jobs
on
each
the
different
machines
and
then
at
the
very
end,
as
it
goes
through.
Those.
C
C
Should
I
should
probably
finish
through
this
time,
but
also
all
six
machines
are
all
running
the
same
exact
script.
They're
all
going
to
get.
You
know
their
data
returned
yeah.
However,
that
particular
you
know
whether
it's
a
Linux
Arc,
whether
it's
a
you,
know,
Azure
BMR.
What
have
you
right?
We
see
order,
we've
succeeded
in
all
of
them,
so
we
can
just
go
loop
back
through
them
all
and
say
give
me
the
output
and
it's
going
to
go
back
and
get
the
output,
and
we
can
then
flip
through
each
machine.
C
So
now
we
see
every
single
one
of
our
machines
here
we
got
the
data
back
or
them
right.
So,
as
I
mentioned
this,
this
originally
came
out
or
I
originally
wrote
this
for
log4j.
This
is
a
lot
fancier
version
of
that,
but
it
is
out
there
on
on
my
gist
this
this
log
for
Jay-
and
this
has
some
additional
things
built
in
to
be
able
to
record
when
it
runs
it'll
fiddle
right
to
a
CSV
file
to
keep
track
of
when
it
ran,
so
that
if
you
restart
it,
it's
not
gonna.
C
You
know
it's
not
going
to
re-hit
the
machines
that
it's
already
hit
before,
because
you
know
we
ran
this
at
some
places
with
thousands
of
machines
right,
one
one
other
caveat,
I
will
say
with
Arc
and
this
particular
extension
is.
We
have
had
some
issues
when
running
it
behind
a
proxy,
for
whatever
reason
it
didn't
like
a
proxy,
it
was
still
in
preview
at
that
time.
I
haven't
been
able
to
retest
it
since,
but
you
know,
if
you're
behind
a
proxy,
there
may
be
some
issues,
the
rest
of
the
arc
functionality
works
great.
C
A
C
C
A
C
What's
in
the
book,
so
so
I
I
wrote
this
book.
God
is
it's:
it's
been
he
a
year
in
the
making.
Now,
when
I,
when
I
first
started,
writing
it
and
I
wrote
it
from
the
from
the
point
of
view
of
you
know
what
what
I
do
in
my
day-to-day
at
work
is,
you
know,
is
automating
it
life
cycles
right
and
I,
often
find
a
lot
of
people
are
hesitant
to
get
into
automation
right
most
automations.
Are
you
know
some?
You
know
Assist
admin
or
a
devops
guy.
C
You
know
I've
been
to
a
Fortune
500
company
that
had
a
desktop
that
had
a
big
stickers
that
do
not
turn
off,
because
there
was
some
automation
running
on
it
that
broke
when
that
thing
turned
off
right.
So
so
what
this
book
does
is
it
is
it
breaks
down
Automation
and
it's
it
it's
written
in
Powershell
because
you
know
basically
I
live
in
Powershell,
but
the
the
content
and
the
philosophy
is
behind.
C
It
are
are
Universal
right,
so
it
goes
through
a
concept
of
of
building
blocks,
of
how
to
create
modular
automations
that
you
can
maintain
and
that
you
can,
you
know,
improve
upon.
You
know
an
example
that
I
always
give.
Is
you
know
you
have
you
know
user
provisioning
request
right,
so
you
need
to
onboard
a
user.
Your
typical
AED
Azure
ad
Salesforce.
What
have
you
right?
You
write
all
of
that
in
Powershell
with
all
of
the
functionality
and
stuff
like
that
in
Powershell,
then
it
doesn't
matter
where
your
data
is
coming
from
right.
C
So
if
you're
using
you,
know
servicenow,
and
then
you
just
you
switch
to
Salesforce
right,
all
you
have
to
do
is
repoint
that
script
from
one
you
know
to
another,
maybe
redo
a
couple
mappings
things
like
that,
but
nothing
is
set
inside
of
that
platform.
And
that's
that's
what
you
know.
That's
where
Powershell
is
great.
You
know,
as
we
were
talking
about
before
on
this
call,
is
you
know
using
Azure
functions
right,
Azure
functions,
I
could
easily.
C
You
know
pick
that
same
exact
script,
that
I'm
running
in
a
function
and
run
it
in
Azure,
automation
or
I-
can
run
it
on
my
local
box
or
I
could
run
it
in
Jenkins
or
ansible.
Or
what
have
you
so
it's
it's
building
those
modular
requests
and
then
and
then
making
them
in
such
a
way
that
you
can
maintain
them
right
so
really
kind
of
going
through
showing
examples
of
you
know
how.
How
do
you
get
secure
data
inside
your
scripts?
How
do
you
you
know
that?
That's
that's
the
biggest
thing
right
there.
C
You
know.
If
you
look
at
automation,
you
know
you
they
need
to
be
secure.
You
can't
go
to
a
CSO
and
say:
oh
yeah,
I,
just
hard-coded
a
password
in
there.
No,
you
know,
that's
that's
not
going
to
work
right,
you
know
so
and
then
you
know,
building
things,
don't
don't
Excel
is
not
a
database.
You
know,
and
you
know,
with
with
tools
like
DBA
tools,
you
don't
need
to
use
Excel
right,
you,
you
can
set
your
foundation
and
your
groundwork
and
then
your
automations
become
a
click
of
a
butt.
C
You
know
this
Arc
is
is
a
great
example.
Here.
Do
a
little
bit
of
leg
work
get
those
agents
installed,
and
then
you
can,
you
know,
manage
all
of
your
machines
with
a
with
a
single
script
right.
You
don't
have
to
go
back
every
single
time.
You
know
the
next
log
for
J
comes
out.
You
don't
have
to
worry
about
it
right.
You,
you,
hey,
I,
have
I,
have
this
set
up
now.
All
I
gotta
do
is
just
plug
in
this
script
and
yo
executed
on
all
these
machines
and.
C
So
I
would
say
you
know:
I
tried
to,
it
is
I,
wouldn't
say
a
beginner
right,
so
you
know.
But
if,
if
you've
read
you
know
Powershell
in
a
month
of
luncheons,
then
you
have
everything
that
you
need
to
be
able
to
stop
in
here
and
start
doing
this.
As
long
as
you
can
understand
how
to
write
functions.
You
know
simple
things
like
splatting
and
you
know,
then
that's
pretty
much
about
it
right
from
there
forward.
It's
just
it's
just
pure
Powershell.
A
And
so
it's
it's
good
for
people
who
want
to
learn
the
concepts
of
automation
if
they
don't
know
all
the
code,
because
they're
not
up
to
the
skill
skill
level,
yet
they
can
develop
that.
But
if
you
have
some
level
of
Powershell
knowledge
prior
to
purchasing
this
book,
you
should
be
able
to
rock
on
the
concepts
that
are
in
there
without
much
issue.
A
You
can
do
with
it
and
so
I
hope
you
guys
enjoyed
this
if
you're
joining
us
on
YouTube
and
it's
first
time
check
out
the
YouTube
channel,
we
have
about
120
other
videos
on
Powershell
and
Cloud
related
topics,
I'm
sure
you
can
find
something
that
is
interesting
to
you.
If
you
like
this
presentation
tonight
and
you
like
to
join
us
in
person,
you
can
find
us
on
Meetup
meetup.com,
the
Research
Triangle
Powershell
user
group,
or
you
can
go
to
rtpsug.com.
We
meet
on
the
first
and
third
Wednesday
month.