►
From YouTube: SharePoint Sandbox Solution Scanner
Description
This short session gets you started with the SharePoint Sandbox Solution scanner tool which you can download from https://github.com/OfficeDev/PnP-Tools/tree/master/Solutions/SharePoint.SandBoxTool.
The main purpose of this tool is to give you a detailed view on the sandbox solutions in your environment. You'll not only be able to see which sites do have sandbox solutions, whether they've an assembly and are activated, but the tool also can download and analyze the solution for you giving you information about what's inside (is it an InfoPath solution, does it contain web parts, does it contain event receivers,...). This information will be helpful in finding the needed transformation guidance and it will help assessing the sandbox remediation needs.
A
A
So
what's
this
all
about,
so
he
you
most
likely
already
have
heard
that
we
have
stopped
support
for
code
base
sandbox
solutions,
so
these
are
obviously
packages
which
contain
an
assembly
and
we,
this
is
certainly
something
really
new.
It
was
already
announced
back
in
2014,
but
now
we
really
made
it
happen.
Well,.
A
So,
which
Senshi
means
it's
time
for
you
to
transform
your
sandbox
solution
that
you
still
have
two
alternative
solutions,
not
all
sandbox
solutions
that
we
have
are
relevant.
What
all
of
them
have
to
be
fixed?
You
will
Morgan
in
the
coming
slides
and
then
the
demo,
but
there
will
be
cases
where
you
all
have
to
fix
yourself
solutions
and
for
doing
so
the
recommended
approach
is
using
the
SharePoint
added
model
in
general.
A
Actually,
a
rule
of
client-side
API
is
that
you
can
use
to
build
rich
assertions
on
SharePoint
and
this
that's
the
pattern
to
use
to
transform
your
sandbox
solutions
before
you
can
transform
your
sandbox
solutions.
You
actually
need
to
know.
Where
are
they
and
how
many
do
you
have
and
what?
How
many
of
those
do
we
need
to
fix,
etc.
So,
a
lot
of
questions
to
get
answers
for,
and
we
have
two
tools
for
you
available.
So
we
announced
a
PowerShell
sandbox
solution.
Scanner
script,
I
think
this
about
10
days
ago.
A
Like
that
and
that
that
was
our
first
session
and
in
the
meanwhile,
we've
been
working
on
a
slightly
more
enhanced
scanner
solution,
which
you
are
now
seeing
with
this
in
this
session,
and
so
we
have
this
boat
tools
and
you
can
see
the
URLs
over
here
and
they
are
also
repeated
again
in
the
later
on
and
slides.
But
since
the
totals,
you
probably
want
to
know,
what's
difference
between
two
tools.
Why
do
we
have
two
tools
and
the
main
reason
why
we
have
the
new
two
versus
the
PowerShell
tool
is
twofold.
A
First
of
all
this
new,
it
will
also
support
SharePoint,
on-premises
environments,
2016
2013.
So
if
you're
migrating
your
SharePoint
2016
2013
environments
to
SharePoint
line,
for
example,
you
can't
migrate
your
sandbox
solutions
which
are
living
in
on-premises.
So
at
that
point
you
you're
definitely
interested
in
knowing
where
they
are
and
how
to
tackle
them,
and
a
second
big
thing
that
was
not
available
in
the
previous
solution
is
only
so
the
script
and
the
tool
they
both
will
check
the
site
collection
and
see
what
sandbox
solutions
are
active
in
that
site.
A
Collection
to
be
able
to
do
so.
We'd
have
four
missions
to
look
inside
the
site
collection.
You
might
wonder,
like
okay,
I
have
turned
admin,
permissions
and
I
created
like
I.
Have
my
tenant
admin
account
actually
and
I,
give
that
to
the
tool
and
that's
what
the
approach
used
in
the
disposal.
Script.
Error
works
typically
for
smaller
environments
with
large
environments.
A
There
is
not
one
admin
account
that
has
permissions
to
all
site
collections
and
wait
up
only.
You
can
actually
achieve
that
by
cutting
that
only
talking
with
the
tenant
level.
Permissions
will
show
you
how
to
do
that
in
the
demo,
which
is
coming
after
this
slide
some
other
advantages
of
this
tool.
Is
it
also
scans
onedrive
for
business
or
my
sites
it
by
default,
uses
multi-threading
so
by
default
that
will
use
10
threads,
which
will
definitely
give
you
a
boost
in
performance.
A
It
also
will
help
you
detect
empty
assemblies.
So
when
you
create
the
receipt
package
for
sandbox
tuition,
filter
studio
by
default
is
always
an
assembly,
even
if
you
haven't
written
any
line
of
code
now.
Those
sandbox
solutions
are
the
ones
which
you
call
having
an
empty
assembly
and
those
can
be
easily
fixed
by
simply
dropping
the
empty
assembly.
So
what
the
tool
will
do
for
you
is.
A
And
finally,
the
tool
will
also
give
you
a
few
one.
What's
inside
your
sandbox
solution
package,
so
it
will
tell
you,
like
your
Kedar
web
paths,
inside
let's
list
them
Pleasant
site
as
a
workflow
custom
action.
There
is
a
feature,
receiver
event,
receiver.
All
those
details
are
listed
for
you
and
this
information
is
useful.
If
you
want
to
s
cope
the
work
that
you
need
to
to
transform
your
solutions.
B
So
really
what
you're
saying
Bert
and
what
we're
saying
with
the
scanner
tool
is
that
this
is
targeted
for
larger
enterprises,
where
you
might
have
even
thousands
of
sample
solutions,
and
since
we
don't
have
a
let's
say,
UI
in
that
menu
is
whether
the
central
are
where
the
administrator
can
go
and
see.
What's
there
and
what's
the
details,
this
is
no
doubt.
B
A
A
A
A
A
Well,
let's
copy
this
one
as
well
like
this.
Well,
principals
has
been
created,
but
doesn't
have
any
permissions
yet
now,
since
we
won't
have
a
principle
that
can
scan
all
site
collections,
probably
tenant,
we
need
to
give
it
10,
scoped
permissions
and
in
order
to
give
a
telescope
permissions,
you
have
to
use
this
set
the
tenant
administration
Center
and
to
grant
those
permissions
so
I,
just
navigated
to
my
tenant
admin
center
SharePoint
at
the
center.
A
I
get
a
page
which
I
can
paste
the
previously
created
app,
ID
or
client.
Id
I
can
do
lookup
and
everything
went
well
and
it
does.
It
shows
you,
the
data
that
you
entered
previously
when
you
create
it
to
the
principal.
The
final
step
here
is
giving
it
an
permission
XML,
which
describes
what
kind
of
emissions
that
you
need
and
for
doing
this
I
would
recommend
going
to
the
two
location.
A
B
A
Actually,
you
need
indeed
be
tenant,
administrator
and
I
would
also
want
to
emphasize
that
the
the
client,
ID
client
secret
combination
that
you
use
that
you
grant
these
permissions
must
be
safeguarded
like
being
your
admin
credentials,
because,
with
that
combination
of
client,
client
secret,
you
can
access
all
data.
So
it's
crucial
that
you
correctly
manage
the
client
secret
for
this
particular
principle.
You.
B
Just
wanna
additional
know
what,
while
you're
clicking
the
create
and
giving
the
permissions
for
it.
So
one
thing
to
notice:
that
was
that
we
went
to
the
admin
URL
and
this
is
a
relatively
new
chain.
So
in
the
past
you
might
have
been
able
to
register
a
tenant
level
permissions
within
using
the
normal
model,
SharePoint
URLs,
but
it's
a
relatively
recent
change
since
spring
2016,
where,
if
you
are
requesting
a
tenant
level
permissions,
you
need
to
go
to
this
admin
URL
and
up
in
aspx,
underneath
there
to
make
that
happen.
B
A
A
The
principal
is
asking
full
control
and
noting
its
shape
when
she's
with
all
the
users
we
just
enough
of
a
pony.
So
in
this
case
there's
only
one
answer
thrust
it.
If
you
don't
trust
it,
it
will
not
work
so
click
interested
at
this
point-
our
client,
ID
client
secret
combination-
has
been
granted
with
talent
level
permissions,
so
we
can
use
it
in
the
tool.
So,
let's
move
to
the
next
step,
that's
used
to
do
so.
First
step
is
downloading
the
tool.
If
you
go
to.
A
A
A
We
can
drop
the
zip,
so
we
have
the
tool
extracted
over
here.
I'm
going
to
start
the
PowerShell
window,
sandbox
a
lot
easy.
If
you
do
that,
you
will
get
the
hell
up
of
the
tool,
it's
quite
a
lot
of
options.
Well,
all
of
them
are
immediately
needed.
They're
all
sold
and
documented
in
detail
in
the
hell
of
text
on
get
up.
A
So
I'm
gonna
specify
a
mode
scan
and
analyze
there
are
three
modes
is
also
a
scan
mode,
which
is
this
basic
scan
outputting,
giving
you
basically
both
scan
and
download.
There's
the
basics
can
pull
down
the
rescue
packages?
Let's
can
analyze
there's
the
basics.
Can
we
learn
the
packages
and
analyze
the
packages
look
inside
and
give
you
information
about
what's
inside
and
offer
you
packages
which
are
fixed,
so
this
is
the
recommended
mode
to
use
not
specified
my
tenant,
so
my
tenant
was
best
online
thought.
She
opened
my
SharePoint
URL.
B
A
Let's
hit
enter
to
start
the
scanning,
so
what
the
tool
now
will
do
is
it
will
collect
first
of
all,
a
list
of
all
side
collections
in
your
tenant.
This
case
is
the
regular
site
collections,
bloser
it
the
wonderful
business
side
collections.
So
once
we
have
collected
the
list
of
site
collections
that
this
will
be
divided
by
a
number
of
threads,
so
by
default
the
student
will
use
10
threads.
So
each
of
the
10
threads
takes
one
tenth
of
the
site
collection
list
and
starts
processing
it.
So
it
will
then
go
to
the
site.
A
Collection
have
a
look
into
the
solution
gallery
checks
which
solutions
are
there.
If
there
is
a
solution
with
an
assembly,
it
will
be
downloaded
once
downloaded,
we
will
open
up
the
solution
package.
Look
inside
African
site
assembly
have
a
look
inside
what
kind
of
artifacts
are
defined
in
solution?
All
of
that
is
then
I'll
put
it
by
the
tool,
so
the
tool
just
finished
and
it
took
47
seconds,
which
is
pretty
ok.
Sometimes
performance
is
slightly
faster,
sometimes
slightly
slower.
It
kind
of
depends
a
bit
on
the
sharepoint
online
performance
of
the
moment.
A
Now,
let's
have
a
peek
at
what
it
will
generate
it
for
us,
so
I
switched
now
back
to
the
sandbox
all
over
to
was
residing
and
in
there
UCSF
folder.
So
we
create
a
subfolder
tool
execution.
You
will
never
have
overwrite
previous
output
data.
So
if
we
go
inside
the
folder-
and
there
is
a
report
which
is
the
main
dribble
of
this
tool,
if
there
are
arrows
they're
logged
as
well
and
report
and
separately
profile-
and
then
there
is
a
set
of
folders
on
which
I'll
explain
later
on.
A
So
let's
first
have
a
look
inside
of
the
report,
so
the
easiest
way
to
show
this
is
go
to
Excel
and
import
the
results.
So
the
text
data
it's
on
the
C
sandbox,
then
a
folder
and
repo
file
it
import.
This
is
the
limited
data
where
comma
SS
default
delimiter,
it
finish:
okay
and
the
format
as
a
table.
A
At
this
point
we
have
a
proper
clean
table.
So
what
does
it
show?
First
of
all,
it
shows
all
the
sandbox
solutions
that
it
encountered
if
if
they
have
been
in
assembly,
well,
actually
that's
it's.
It
gives
detailed
information
if
they're
an
example
assembly
but
have
a
list
of
all
of
them.
So
these
are
all
the
assemblies
all
the
same
exclusions,
sorry
in
my
environment,
so
it's
20
pieces
and
when
I
look
at
the
further
data,
I
see
an
activated
column
and
has
assemblies
column.
So
what
support
of
you
to
know?
A
Solutions
which
are
not
activated
might
not
be
a
business
robot
anymore
and
can
be
skipped
in
your
further
remediation
activities.
Sandbox
solutions
without
assemblies
keep
on
working,
there's
no
problem
with
those
guys,
so
only
the
ones
having
assembly
are
to
be
investigated.
If
the
semuc
solution
has
an
assembly
we're
also
showing
you
a
site
owner
column,
because
you
might
want
to
reach
out
to
the
business
party
owning
the
particular
site
collection.
A
A
We
use
this
in
the
tool
to
only
analyze
a
solution
once
so,
if
you
download
it
analyze
the
particular
solution
and
we
encounter
the
same
solution
in
another
site
collection
somewhere-
we
just
list
it
in
here,
but
we're
not
downloading
it
anymore.
We
have
the
site
ID,
which
is
the
the
site
ID
of
the
site
collection.
So,
and
this
corresponds
to
the
you
see
in
the
output
which
we'll
discuss
in
a
minute,
then
we
have
set
of
important
fields
Becky
like
this,
so
we
will
indicate
whether
this
is
an
empty
assembly
or
not.
A
So
when
you
create
a
sandbox
solution
using
video
by
default,
there's
always
an
assembly.
Even
if
you
haven't
written
a
line
of
code,
there
is
an
assembly
now
with
those
guys
they
can
be
easily
fixed.
My
repackaging
the
solution
wrote
assembly
and
redeploying
it.
So
I
was
important
to
be
able
to
distinguish
those
which
is
this
code
when
you
deploy
in
InfoPath
form
with
code
behind
a
share
point
will
create
a
sandbox
solution
for
you,
and
this
with
this
column,
is
indicating
whether
the
semuc
solution
is
coming
from
InfoPath
or
it's
a
regular
sandbox
solution.
A
In
the
case
of
in
spots,
we
can
also
have
empty
assemblies
and
if
that's
the
case,
they
will
be
listed
over
here
and
then
we
have
a
set
of
columns,
giving
you
a
bit
more
insight
in
the
solution.
So
whether
the
solution
has
webparts
web
templates
feature
receivers,
event
receivers
in
these
definitions
and
workflow
actions.
This
data
is
useful
for
you.
If
you
want
to.
B
A
Scope
and
plan
your
transformation
work
now,
let's
switch
back
to
the
folder.
So,
as
already
mentioned
in
the
report,
there
is
a
subfolder
bro
site
collection
which
contains
the
same
exclusion
having
an
assembly,
because
we
download
the
sandbox
solutions
and
we
want
every
unique
place
to
store
them.
So
this
folder
name
corresponds
with
the
site
collection
ID.
A
You
will
notice
a
number
of
things.
First
of
all,
we
downloaded
the
solution
package,
cds
solution
package.
We
also
generate
an
XML
file,
prostitution
like
a
chip
describing
the
inside,
so
we
have
a
solution.
Analyzer
component
that
looks
inside
the
solution
package
and
tells
you
like
it
that
there
are
five
features,
a
feature
one
as
a
web
birth
feature,
two
as
a
workflow
custom
action,
etc.
All
this
information
that's
helpful
for
you
to
screw
up.
A
Your
work
is
inside
this
XML
file
and
finally,
if
the
solution
contains
an
assembly
and
if
we
detect
that
particular
assembly
is
empty
and
we
flag
that
in
the
report
as
you
saw
before,
but
we
will
also
generate
a
new
solution
package
without
the
assembly.
So
we
just
repackaged
the
original
one
without
assembly
and
those
guys
are
called
have
an
underscore
fixed
suffix.
A
Session
here
we
go
if
I
launch
the
tool
without
parameters,
it
will
give
the
hell
up.
Text
and
I'll
show
the
options.
You
will
notice
that
there
on
premises
there
are
less
options
and
the
main
reason
is
because
the
premises
will
not
supporting
a
pony.
We
only
allow
you
to
use
a
username
kamesh
word
with
its
domain
and
the
password,
and
the
reason
is
because
you
can
grant
a
particular
user
access
to
all
site
collections
using
web
application
policy.
A
B
A
So
we
again
have
the
mode
scan
and
analyze,
and
then
we
have
to
are
relative,
which
stands
for
your
results,
we're
just
listing
a
set
of
wildcard.
You
are
else
that
you
want
to
scan
so
well,
you
know,
whine
you
specified
t
and
then
the
the
tenant
name
and
the
sits
here.
You
have
to
really
specify
the
wildcards
results
that
you
want
to
scan.
We
specify
a
username,
a
password
and
domain
of
that
particular
user,
hitting
Enter
launches
the
tool
same
procedure.
We
build
a
list
of
site
collections
and
then
we
scan
them.
A
In
this
case
it
went
really
really
quick,
because
it's
on
premises
and
there's
not
that
many
site
collections
as
well.
Now,
looking
at
the
output,
you
see
the
similar
output,
the
reports
and
a
folder
containing
in
this
case
one
of
the
sandbox
solutions
which
contains
an
assembly.
So
we
have
to
note
it
that
one
all
right.
So
this
concludes
this
demo.
So
let's
switch
back
to
slides
I.
B
And
just
to
reinforce
the
kind
of
a
message:
what
are
we
doing
this?
So
all
of
the
Poisson
Box
solutions
which
have
assembly
within
a
SharePoint
Online
can
no
longer
be
activated,
so
existing
ones
are
still
up
and
running.
At
some
point,
we
will
actually
shut
down
the
code
based
execution
of
those
templates
as
well,
so
you
do
as
a
tenant
administrator.
You
want
to
know
how
much
sandbox
solutions
are
used.
Where
are
they
and
which
of
them
happen
simply
so,
which
of
them
are
actually
impacted
by
this
chance?
B
This
doesn't
apply
for
sample
solutions
which
only
contains
xml-based
customizations
or
assets,
and
the
the
removal
of
sample
solution
code
based
support
doesn't
apply
for
own
premises.
But
again,
like
Bert
mentioned
when
we
started
the
webcast,
if
you're
planning
to
move
from
our
own
premises
to
sharepoint
online,
you
absolutely
need
to
understand
if
you
have
a
dependence
and
sample
solution
in
on
Prem
and
how
to
can
replace
them,
but
I
think.