00:00:00
welcome everybody to this session we are
00:00:03
thank you we are going to discuss the
00:00:05
basics of scum upgrades and migrations
00:00:08
including migration to Azure monitor
00:00:11
scum managed instance which is a long
00:00:14
way of saying scum am I keep in mind we
00:00:17
only have 45 minutes for a topic that
00:00:19
can cover at least a whole day so let's
00:00:22
get
00:00:24
started just for those who do not know
00:00:27
me yet I'm Bob cornelison from the L
00:00:31
people from the community gave me the
00:00:33
nickname scum Bob so uh but I actually
00:00:36
do a lot more things than just that but
00:00:39
of course I am most known for my scum
00:00:42
stuff um currently I'm a 12-year
00:00:44
Microsoft MVP for cloud and data center
00:00:47
management and I am the technical
00:00:49
director for top core and inovis and
00:00:52
related
00:00:53
companies I do play carum Billiards
00:00:56
which is my hobby uh that is Billiards
00:00:58
without holes in the table and I'm also
00:01:01
a licensed referee for that and the
00:01:04
house of tales is a certified animal
00:01:06
charity looking after about 70 dogs and
00:01:09
a few cats in two locations in Thailand
00:01:12
so come and find us on Facebook for
00:01:17
example shortly about where I work
00:01:20
topcor is an it consultancy based in the
00:01:22
Netherlands with team members spread
00:01:24
across several countries and delivering
00:01:26
consultancy services to customers
00:01:28
worldwide doesn't matter to us where you
00:01:31
live we have a specialization in
00:01:33
Microsoft monitoring and management
00:01:35
tooling and are most welln for SC
00:01:38
Services some of our main services are
00:01:40
listed here being a scom health check to
00:01:42
view and confirm the current status of
00:01:45
your scum environment scum trainings at
00:01:48
different levels from operator to admin
00:01:50
to specialist and of course our
00:01:53
community efforts such as these free
00:01:55
webinars we do implementations
00:01:57
migrations upgrades and ex extending
00:02:00
monitoring and
00:02:01
dashboarding and we have a knowledge
00:02:04
partnership and we do also do
00:02:06
maintenance as a service to help to keep
00:02:08
your monitoring environment running and
00:02:11
healthy so let's get on to the topic at
00:02:15
hand so I made here a short overview of
00:02:19
scum versions from a while back to today
00:02:22
uh and also looking forward to the end
00:02:25
of this year so we have a column here
00:02:28
and the column has two halves of it
00:02:31
sometimes uh the bottom half is standing
00:02:33
for the mainstream support which is the
00:02:35
five first years after Microsoft
00:02:37
releases a product and the top half
00:02:40
stands for the extended support and when
00:02:44
that one ends if you have extended
00:02:46
support now mostly no update rollups are
00:02:49
expected after mainstream support ends
00:02:53
except for certain cases now if we look
00:02:55
at scum 2019 in the middle there it went
00:02:58
into extended support a few weeks ago
00:03:02
after it got update rollup six and now
00:03:05
we are sitting in extended support so
00:03:08
keep in mind to have a look and have a
00:03:10
have a ask if your organization has
00:03:13
extended support or not because
00:03:14
otherwise you might want to move faster
00:03:17
as well to a higher
00:03:18
version um we have here scum 2022 listed
00:03:22
as the current version and we have scum
00:03:25
Mii listed here as well to the right
00:03:27
which is today a version of SC 2022 but
00:03:31
living in the cloud and with a little
00:03:33
bit of changes in the
00:03:36
infrastructure and scum 2025 is expected
00:03:39
to be released with Windows Server 2025
00:03:43
in the last few months of this year as
00:03:46
you can see we want to be moving up to
00:03:49
2022 at least and we know many are on
00:03:52
versions lower than that actually let's
00:03:55
have a look so I asked uh Bruce
00:03:59
yesterday for a quick peek before the
00:04:02
big SC for survey actually ended to
00:04:04
already see what's in here um so
00:04:08
yesterday these were the
00:04:09
stats uh you can see here that the first
00:04:12
two are in mainstream support uh at a
00:04:15
little bit of over a third of the users
00:04:19
scum 2019 and 16 are nearly half of the
00:04:23
deployments put together and they are in
00:04:26
extended support now I'm almost sure not
00:04:30
everybody of in that group has extended
00:04:33
support so be careful there and have a
00:04:35
look at moving up as I said we don't
00:04:38
expect updates for those anymore and
00:04:40
remember that not everybody has it so we
00:04:43
see also 1807 2012 and 2007 they are
00:04:48
well out of support and they are about
00:04:50
10% as well and what is also interesting
00:04:53
is the 5% which is missing if you add up
00:04:56
all of those numbers but that's fine
00:05:02
so this brings us to why we upgrade well
00:05:06
we have to have a supported version so
00:05:09
this means that we get regular updates
00:05:11
as well which contain hot fixes book
00:05:14
fixes and new features as well along
00:05:18
with those updates and full version
00:05:20
upgrades come also security fixes and
00:05:24
features or we might be on a transition
00:05:27
path to hybrid infrastructure between
00:05:30
the data center and the cloud where we
00:05:33
could have the option of using scum
00:05:35
managed
00:05:36
instance so let us quickly pick up a
00:05:39
reminder of what was or is included in
00:05:42
the last few versions of scum and I'm
00:05:44
starting at
00:05:46
2019 and keeping it quite short so 2019
00:05:50
came with full HTML 5 dashboards without
00:05:54
Legacy dependencies added support for
00:05:57
newer SQL versions for running scum
00:06:00
maintenance mode improvements while also
00:06:03
starting it from the
00:06:04
agent we have new Linux and operating
00:06:07
systems supported with agents and
00:06:10
management packs we had the new Windows
00:06:13
operating system obviously supported
00:06:15
2019 back then uh for running scom and
00:06:19
the agent and we had performance
00:06:21
improvements which isn't always easy to
00:06:23
achieve without messing up the code of a
00:06:27
product now let's move on to the next
00:06:31
for scum 2022 I did a webinar at scaton
00:06:36
two years ago with a longer list of
00:06:38
updates and what they look like so you
00:06:40
can watch a recording of that if you
00:06:42
want to know more for now I just want to
00:06:45
highlight a few of the items here we
00:06:48
have a new set of builtin and custom
00:06:50
roles for the administrator arback roles
00:06:53
whereby we have a readon admin for
00:06:56
Auditors and several options for cust
00:06:59
admins who can be limited to do for
00:07:02
example only agent management or only
00:07:05
work with notification
00:07:07
subscriptions we have an updated option
00:07:10
for alert closure to be able to close an
00:07:13
alert from a monitor if that monitor is
00:07:16
still in an unhealthy State now this new
00:07:19
option would also update the health
00:07:21
State back to green while closing the
00:07:23
alert so that the dashboards and alert
00:07:26
lists both show the same thing so you
00:07:29
don't end up with an empty list of
00:07:31
alerts and still have a red
00:07:34
dashboard for the installations there
00:07:37
have been improvements as well
00:07:39
especially while deploying to clustered
00:07:40
SQL instances for these SC
00:07:43
databases in this version there's also
00:07:46
full group managed service Account
00:07:49
Support from RTM going
00:07:52
up and number of visual changes have
00:07:54
been done to some of the views here and
00:07:57
there throughout the product based on
00:07:59
the requests made by the community a
00:08:01
nice one is an additional column in an
00:08:03
alert view which points out if an alert
00:08:06
is from a rule or a monitor for
00:08:08
example and a teams notification channel
00:08:11
has been added uh instead of the old I
00:08:13
am Channel which was there before and of
00:08:17
course this version of scum can be run
00:08:19
on Windows Server 2022 for the
00:08:22
infrastructure components as well and of
00:08:24
course SQL 2022
00:08:30
looking ahead a little bit into what has
00:08:33
been released to public at this uh stage
00:08:37
about scum
00:08:39
2025 uh well of course the reason to
00:08:41
release scum 2025 is because of Windows
00:08:45
Server
00:08:47
2025 so it will be released with Windows
00:08:50
Server 2025 preferably at the same
00:08:53
time system center with the main
00:08:56
products and scum will work with the
00:08:59
other products of the same Suite of the
00:09:02
same version so SC needs to work with
00:09:04
orchestrator needs to work with DPM
00:09:08
Etc security is always a topic right now
00:09:12
my best guesses given the limited info
00:09:14
about SC 2025 and system center 2025 are
00:09:19
these so we want to try to reduce the
00:09:22
TLs 1.3 support uh no sorry we want to
00:09:27
introduce tls1.3 support
00:09:30
available in Windows 2022 and up and we
00:09:33
try to reduce or lower the Reliance on
00:09:37
ntlm and cred SSP as much as possible I
00:09:43
not sure if they can get rid of it
00:09:45
completely in this version um but they
00:09:47
are trying to get as far as possible at
00:09:50
least um and there will be other items
00:09:53
that we cannot talk about right now for
00:09:56
different reasons because well they are
00:09:58
not public yet
00:09:59
um in a few months time um this will be
00:10:02
the new Target to upgrade two or to
00:10:05
migrate two and I do not expect the
00:10:08
topic that I'm talking about today to be
00:10:10
very different uh for that version
00:10:13
either so when I'm talking today about
00:10:16
migrating towards SC
00:10:18
2022 then you can assume that most or
00:10:22
all will work towards the migration to
00:10:25
25 as well it's just a timing issue
00:10:30
all right so I've now talked you into
00:10:34
upgrading to a newer version of scum now
00:10:37
what well first we need to decide the
00:10:40
version of scum that we want to go to
00:10:43
however that also means we need to
00:10:45
select the windows and SQL versions
00:10:48
belonging to it except for SC manage
00:10:51
instance where this is already being
00:10:53
taken care for of for you right so it
00:10:56
will deploy a Windows in a SQL uh Mi for
00:10:59
you so that you don't care about but for
00:11:03
on Prem you do need to care about
00:11:05
these we will talk about the combination
00:11:08
of Windows and SQL with SC in the next
00:11:11
two
00:11:12
slides now we need to decide on how to
00:11:15
get to that new version or in short our
00:11:18
migration
00:11:20
scenario so do we have to do a
00:11:22
side-by-side Migration by setting up a
00:11:24
new scum and then moving everything
00:11:26
across to it or can we do an inplace
00:11:29
upgrade from the current setup to a
00:11:31
higher
00:11:35
version so this is what I call the scum
00:11:37
upgrade three you might have seen it
00:11:39
before it shows the scum versions in
00:11:42
their direct upgrade path including to
00:11:46
scum Mi I to the left hand side now as
00:11:49
you can see this is mostly a possible in
00:11:51
place upgrade by one version
00:11:54
up so we had a little side step to
00:11:57
semiannual channel to the right hand
00:11:59
side but we will ignore that in the next
00:12:01
slides because you should migrate off it
00:12:04
to a higher version as soon as possible
00:12:06
anyway it's no longer
00:12:08
supported and we see that we can
00:12:11
currently go to scum Mii from a scum
00:12:14
2009 and scum 2022 version at least
00:12:18
those are the supported path and of
00:12:20
course we will expect a line to be
00:12:22
coming later from 2025 towards Mi as
00:12:26
well
00:12:30
so here we have these conversions again
00:12:34
and now we will add the windows versions
00:12:37
that it can run
00:12:38
on where are they here they are a SC
00:12:42
version listed on the right supports
00:12:44
running on the windows and SQL versions
00:12:47
right above and below the red line so if
00:12:50
we take SC
00:12:52
2022 it will run on Windows 2019 right
00:12:56
below the line and windows 2022 right
00:12:59
above the
00:13:01
line now let's add some SQL to it
00:13:05
looking again at scum
00:13:08
2022 we will see that we have SQL 2017
00:13:12
and 19 below the line and of course we
00:13:16
also see SQL 2022 above that line as
00:13:19
well as supported within this
00:13:22
version now we need to pick a
00:13:24
combination of those to run scum 2022 on
00:13:28
as you can see we have two potential
00:13:31
Windows versions and three potential SQL
00:13:34
versions which apply if you want to
00:13:37
install SC 2022
00:13:40
today but if we want to be able to in
00:13:44
place upgrade next time to a higher
00:13:46
version of scum let's say
00:13:48
2025 we need to have the right
00:13:50
combination
00:13:52
prepared so in this case I would go for
00:13:55
the highest uh combination version which
00:13:58
is window
00:13:59
2022 with SQL 2022 and scum
00:14:03
2022 if you want to install a fresh new
00:14:06
SC today because it is likely most
00:14:11
likely that you can uh support SC
00:14:15
2025 on those platforms on Windows 2022
00:14:20
and SQL 2022 at the very least for
00:14:23
example support for SQL
00:14:26
2017 would be very uncertain at this uh
00:14:29
at this point because it's already 7even
00:14:32
years old going on eight so try to look
00:14:35
forward to make your best bet
00:14:38
here there is no newer SQL version being
00:14:41
released before windows and and system
00:14:44
center yet so I'm assuming that 22 is at
00:14:48
least going to be supported because
00:14:50
there's nothing newer than that
00:14:52
available all right so we have our
00:14:54
combination
00:14:59
so in bullets while we are deciding
00:15:02
which type of migration we are going to
00:15:04
do the decision which method to use
00:15:07
depends not just on this SC version but
00:15:10
also as you see on the windows and SQL
00:15:12
version as well if there are too many
00:15:15
upgrades of these three products
00:15:17
involved at the same time in production
00:15:20
there's a larger chance to mess things
00:15:22
up but also there will be many steps
00:15:25
involved in most of those cases but not
00:15:28
all I prefer to select a side by-side
00:15:31
migration because otherwise you would
00:15:33
have to first update Windows then SQL
00:15:36
then scum then windows again then SQL
00:15:38
again then scum again so you know there
00:15:40
are many steps to get upgraded in an in
00:15:44
place update scenario especially if your
00:15:46
windows and SQL versions are lower for
00:15:49
example
00:15:53
2016 when going for a side by side
00:15:56
migration I have a tip to set up your
00:15:59
new environment on the latest versions
00:16:00
of the supported products as we have
00:16:02
just discussed because again it gives
00:16:04
you the possibility to then do an impl
00:16:07
upgrade next time to the new version of
00:16:10
scum and since that's only half a year
00:16:13
away if you do a clean setup now uh in
00:16:17
order to move forward towards your new
00:16:19
scum environments get rid of the old
00:16:21
unsupported ones or out of mainstream
00:16:23
support get to 2022 first on the latest
00:16:27
versions of windows SQL and scum and
00:16:30
then you can easily in place upgrade
00:16:33
again
00:16:35
later next you will then copy over the
00:16:38
configuration multi-home the agents
00:16:41
migrate with less production impact if
00:16:43
you do a side by
00:16:47
side so when upgrading or migrating a
00:16:51
complex piece of infrastructure with
00:16:53
varying numbers of connections to other
00:16:56
systems we need to create a plan
00:16:59
what we always do when doing a migration
00:17:02
is to run our technical health check why
00:17:05
well because we have that one so this is
00:17:08
to find out if we are able to do a
00:17:10
direct upgrade or to find any existing
00:17:13
issues for example which we don't want
00:17:15
to carry
00:17:16
forward in order to avoid carrying those
00:17:19
forward we run these kind of checks or
00:17:23
to decide to go for a side-by-side
00:17:25
migration if something essential cannot
00:17:27
be fixed in the old system
00:17:29
for example SQL settings which are very
00:17:34
specific when we find out that
00:17:36
everything is ready for a simple in
00:17:39
place upgrade button um we can consider
00:17:42
throwing in the virtual scum DVD and
00:17:45
hitting the enter button several times
00:17:47
until the main update finishes and yes I
00:17:51
do have one of those huge enter buttons
00:17:54
right here and it actually
00:17:55
works so after a migration or
00:17:58
implementation we always again run the
00:18:01
SC health check both as a check if we
00:18:04
forgot something but also to service
00:18:07
documentation because we can spit out a
00:18:10
document based on
00:18:13
it so when we make a plan what needs to
00:18:17
be part of our
00:18:19
plan well we first include steps for
00:18:22
Windows and SQL
00:18:26
implementation and then next for scum we
00:18:29
have the major and the minor
00:18:31
steps and we would consider the
00:18:34
organization steps as well such as we
00:18:38
need to create designs and we need to
00:18:41
arrange cup changes for the change
00:18:43
Advisory
00:18:46
Board now put these steps in a somewhat
00:18:50
logical order granted some steps will
00:18:52
run simultaneously that doesn't matter
00:18:55
for each step determine how much time it
00:18:59
costs to get it
00:19:01
done who is going to do these steps Um
00:19:04
this can be a SC admin or a DBA somebody
00:19:08
on the networking or security team or an
00:19:11
external
00:19:13
consultant note if for example A change
00:19:16
is needed and approved by the change
00:19:18
board or if others such as monitoring
00:19:21
users need to be
00:19:23
notified that way you can work through
00:19:25
your worksheet and put check boxes or ch
00:19:28
change colors according to where you are
00:19:30
in each step and a timeline can be made
00:19:34
from this uh from this plan some
00:19:37
migrations may take hours to days and
00:19:40
others require a process spread across
00:19:42
several months it all depends on your
00:19:45
organization as
00:19:48
well now let's focus on scum again
00:19:53
starting with the in place upgrade
00:19:56
scenario a few of these items will be
00:19:59
true for the migration scenario as well
00:20:01
of course when you want to in place
00:20:04
upgrade we start the story again with
00:20:06
making sure your versions are up to date
00:20:09
for Windows SQL and
00:20:12
scum as we have talked about before but
00:20:15
I'm repeating this point because it is
00:20:17
important remember that SC upgrade three
00:20:21
slide also you need to be sure that the
00:20:23
current scum environment is healthy this
00:20:26
is because upgrading a half broken
00:20:28
system will result in a fully broken
00:20:35
system you must make sure that you have
00:20:37
an account with the correct rights this
00:20:40
account must be local administrator on
00:20:42
the scum info servers including the
00:20:45
management servers the SQL servers also
00:20:48
in a cluster scenario and the scum web
00:20:51
and Report
00:20:52
servers it must be a c admin in SQL and
00:20:56
it must be a scum admin as well
00:20:59
as a tip I prefer to temporarily use the
00:21:02
scum data access account for this or
00:21:05
maybe the one uh the account which did
00:21:07
the original scum
00:21:10
installation using a personal admin
00:21:13
account can sometimes result in
00:21:15
databases becoming owned by uh an owner
00:21:18
with a personal account so that is why I
00:21:20
usually use either a dedicated install
00:21:23
account for this or I use one of the
00:21:25
service accounts if it has the correct
00:21:27
rights for this or I temporarily give it
00:21:30
more rights in order to do it and then
00:21:32
take the rights away
00:21:36
again for an in place upgrade there are
00:21:39
a few steps generally that you need to
00:21:41
do to start such as making sure that you
00:21:45
have plenty of space in this com
00:21:47
database at 50% and that its transaction
00:21:51
log file is bigger than normal so this
00:21:55
is because the amount of data going
00:21:57
through it at the time of
00:22:00
upgrading we remove some Agents from
00:22:04
pending
00:22:05
management and we can disable the
00:22:07
notification
00:22:09
subscriptions we also disable connectors
00:22:12
from other
00:22:14
products we disable the IAS web console
00:22:17
site in
00:22:18
IAS and we can clean the ETL table with
00:22:22
a script now this script is listed on
00:22:24
the applicable documentation sites as
00:22:27
well Microsoft has that all documented
00:22:30
as well in step by
00:22:33
steps also make sure you have uh
00:22:36
complete backups of management servers
00:22:39
and all scum databases and have a copy
00:22:42
of applicable management packs if
00:22:44
possible or use software such as cect MP
00:22:48
Studio to have a repository of
00:22:50
management packs
00:22:55
ready I would start with the rmsse
00:22:59
server so we restart the rmsse emulator
00:23:05
server so that's the management server
00:23:06
which was installed first and this is to
00:23:09
remove pending restarts and avoid some
00:23:12
processes on the scum site getting stuck
00:23:14
during the upgrade so this is one of
00:23:16
those Lessons Learned From the Past
00:23:18
usually it's either the monitoring host
00:23:20
getting stuck or there is a pending
00:23:23
reboot from an other product but the SC
00:23:27
upgrade wizard is is uh made to honor uh
00:23:31
that waiting state for waiting for
00:23:33
pending reboot so it has to wait in that
00:23:36
case so just reboot the machine that
00:23:39
will clear everything
00:23:41
up then we stop all of the scum related
00:23:44
services on the other management servers
00:23:46
so they don't not interfere with us at
00:23:48
that
00:23:49
moment and we can start the upgrade
00:23:53
wizard so the SC installation wizard to
00:23:55
upgrade our rmse management server
00:24:00
please do not start the SC install
00:24:03
wizard on multiple servers at the same
00:24:05
time because I have seen this happen
00:24:08
where people say well let's just start a
00:24:10
wizard on every server and we do not
00:24:13
press you know the final uh Go Button
00:24:16
the Finish button uh if you do that it
00:24:19
will cause problems so in use that
00:24:24
install wizard only on one management
00:24:26
server at the same time same goes for
00:24:29
the
00:24:31
upgrades it's uh as easy as that to do
00:24:34
it please do not start it and then stop
00:24:36
it
00:24:38
halfway so I cannot list all of the
00:24:40
detailed steps here because there's not
00:24:43
enough time but in general if you move
00:24:46
through these scum infos servers one by
00:24:48
one while upgrading their scum
00:24:50
components so we have the management
00:24:52
servers with or without scum consoles we
00:24:56
have web and Report Services we have the
00:24:58
ACs component perhaps that you need to
00:25:01
update so we go through them one by one
00:25:05
not just one by one on the server
00:25:07
because a single server might have
00:25:08
several different roles and we need to
00:25:10
upgrade those as
00:25:13
well next you will enable the connectors
00:25:16
notification channels again which you
00:25:19
turned off at the
00:25:21
beginning you can upgrade the gateways
00:25:24
followed by scum agents and consoles
00:25:27
then depending on the timing and the
00:25:29
size of your environment you might be
00:25:31
able to do a few of these last steps
00:25:33
before enabling the connectors and
00:25:35
notifications
00:25:37
again it just depends if it's only a few
00:25:40
hours then you can just finish your work
00:25:41
first and then enable it and if you
00:25:45
expect for example that agent stuff and
00:25:47
the console stuff to take days or weeks
00:25:49
and of course you can already start
00:25:51
enabling scum to work as
00:25:56
normal um having a few agents and
00:26:00
consoles not upgraded yet should not
00:26:02
stop you from acting as if the main
00:26:04
upgrade is finished that is the point
00:26:07
here um keep in mind also one more thing
00:26:11
is that you also might have update
00:26:13
rollups so as you know SC 2019 has
00:26:17
update rollup six scum 2022 has update
00:26:20
rollup two and there actually also a few
00:26:23
post hot fixes after update rollup too
00:26:27
so this is something to keep in mind
00:26:30
what is advised to do is not to first
00:26:33
run an update and then immediately like
00:26:36
in a minute after start the update
00:26:38
rollup too because com needs to
00:26:41
initialize first it needs to First do an
00:26:45
hour or two or three or four of work to
00:26:48
get everything initialized and stable
00:26:51
again before going forward to the update
00:26:54
rollup to so that is the official advice
00:26:58
and and I would keep to that as well or
00:27:00
you can do it uh the SC upgrade in the
00:27:02
one day and then the next day do the
00:27:04
update roll up to and whatever else
00:27:06
comes with it it doesn't matter for the
00:27:08
agents by the way we are talking now
00:27:10
about the management servers back
00:27:15
end all right
00:27:18
so if we are not doing an impl upgrade
00:27:21
then we are likely going to do a side
00:27:22
bys side scenario where we migrate from
00:27:25
an existing older environment to a newer
00:27:28
SC environment which is built up next to
00:27:31
it so first of all you make a design of
00:27:34
the New Management Group consider the
00:27:36
versions as we talked about before for
00:27:38
scum windows and SQL very often your
00:27:42
existing scum design can be used as a
00:27:44
basis for the new one in the same uh if
00:27:48
the same considerations still apply
00:27:51
outside of you know version
00:27:53
numbers so thinking about high
00:27:56
availability think about security think
00:27:58
about the number of service required and
00:28:00
their
00:28:01
specifications are you going to use the
00:28:04
same service accounts as the old SC
00:28:06
environment or are you going to create
00:28:08
new ones so those are some things to
00:28:11
consider and put in your design and
00:28:14
sometimes an existing design can be
00:28:16
upgraded adjusted to become the new
00:28:19
design as
00:28:22
well so like we said before for a side
00:28:26
by side migration you need to to set up
00:28:28
a new scum infrastructure the existing
00:28:31
one just keeps running at the same time
00:28:33
in the
00:28:34
meantime we set up new windows
00:28:37
servers we install our SQL database
00:28:40
servers and SQL reporting whether that's
00:28:43
in clustering or not so that takes some
00:28:46
extra
00:28:47
steps we set up a new management group
00:28:50
with the first management server and
00:28:52
keep adding management servers as needed
00:28:54
keep in mind this one since it is a side
00:28:57
by-side migration it will be a different
00:28:59
Management Group with a different name
00:29:02
so there are some things to keep in mind
00:29:04
later on as
00:29:06
well this com reporting server will be
00:29:08
built up as well and we can look at this
00:29:11
SC web console server and or other web
00:29:14
consoles such as Squad
00:29:17
up and we can get gateways installed as
00:29:20
they are
00:29:21
needed in many cases this does take some
00:29:25
more steps with each within each item
00:29:27
and for that reason I again highly
00:29:29
recommend putting up a list of Main and
00:29:32
smaller steps for this so you don't
00:29:34
forget too many
00:29:37
things next when the scum infrastructure
00:29:41
has been set up you are looking at the
00:29:43
migration between two environments again
00:29:47
also here applies that it is good to
00:29:50
have a list of steps so this is just an
00:29:53
example um there is talk about
00:29:57
management packs in here we see third
00:29:59
party management packs and solutions we
00:30:01
talk about user roles notification
00:30:04
channels web Watcher notes and so on and
00:30:07
the agent migration story is there too
00:30:10
which might be more steps in your case
00:30:14
because you may want to create a script
00:30:15
and maybe an secm package to do the
00:30:18
agent upgrade in some of the
00:30:20
organizations instead of pushing an
00:30:22
agent through uh through scum and of
00:30:25
course at the end there are some steps
00:30:28
about cleaning up the connections to the
00:30:30
old scom and the old scom itself also
00:30:32
needs to be cleaned up but also don't
00:30:34
forget about the
00:30:36
documentation we can chat about these
00:30:38
steps further in another talk but again
00:30:41
we are limited in time here if you have
00:30:43
immediate questions about this or need
00:30:45
help please come and find me at topcor
00:30:49
and of course we have a booth for that
00:30:50
as
00:30:53
well once your infrastructure is there
00:30:57
you need to we need to step to the
00:31:00
management packs right because what's SC
00:31:04
is is basically we have an
00:31:06
infrastructure then we have the agents
00:31:08
talking to the infrastructure and then
00:31:10
we have the management packs for the
00:31:12
monitoring dashboarding and
00:31:15
everything so we need to talk about the
00:31:17
management packs you likely have backups
00:31:20
of management packs which we can use to
00:31:23
either recover management packs when
00:31:25
something goes wrong or to migrate to
00:31:28
another SC in case we start fresh well
00:31:31
this is exactly what we are talking
00:31:33
about otherwise make sure that you
00:31:36
download the third party packs that you
00:31:38
need and the other sealed management
00:31:41
packs from Microsoft and those
00:31:42
third-party
00:31:44
vendors and we need to grab of course
00:31:47
our unsealed management packs which
00:31:49
depend on the sealed
00:31:51
ones so once we have the whole list
00:31:55
downloaded and available somewhere we
00:31:57
can start by importing the sealed
00:31:59
management packs from Microsoft and the
00:32:02
third party vendors and Community packs
00:32:05
so this is a great time to consider
00:32:07
leaving out a few packs that you no
00:32:09
longer need for example all of the
00:32:12
windows 2003 and 2008 stuff and packs
00:32:16
for Hardware or applications you no
00:32:18
longer have consider that when moving to
00:32:21
a newer versions of some management pack
00:32:24
they can change a lot in this case you
00:32:26
may need to update references in
00:32:28
management packs connecting to it which
00:32:31
are usually the unsealed management
00:32:33
packs also when removing some management
00:32:36
packs we see a need to clean up the
00:32:38
management pack references that we no
00:32:41
longer have loaded so this is often a
00:32:44
little bit of manual work to do but once
00:32:47
you get the hang of it you will know
00:32:48
what to do and get it done also when we
00:32:52
move to a different Management Group we
00:32:53
need to repoint the web Watchers and
00:32:56
other types of Watcher notes
00:32:58
which are available in our environment
00:33:00
because they are likely using the
00:33:02
management server from the old
00:33:04
environment which is not living in your
00:33:06
new
00:33:07
environment and there are more of such
00:33:09
examples as well of course you will also
00:33:12
have scripts running in the back end
00:33:14
connectors running in the back end and
00:33:15
they also need to reconnect towards our
00:33:18
your new Management Group New Management
00:33:21
servers New Management Group
00:33:24
name so one of the approaches for Side
00:33:27
by migrations is also to set up a new
00:33:30
scum in test first and then you could
00:33:33
migrate the management packs to that
00:33:35
test environment first and figure out
00:33:38
what management packs you need what
00:33:40
prerequisite packs you need to download
00:33:42
which references to clean up once you
00:33:45
have your set of sealed and unsealed
00:33:47
management packs the way you want them
00:33:49
in that new test environment you can
00:33:52
simply copy and paste the whole stuff
00:33:54
and import everything in the new
00:33:56
productions com without messing about in
00:33:59
the new production too
00:34:01
much because the cleaning process and
00:34:04
finding packs online takes most of the
00:34:07
time sometimes and you can do that in
00:34:09
that first step and then from point two
00:34:12
to three in this uh in this slide is
00:34:15
very easy right because you have
00:34:17
everything already ready for
00:34:20
you talking about having things ready as
00:34:24
I said before there are several tools
00:34:26
and methods out there to facilit fa
00:34:27
itate the menion pack migrations ranging
00:34:31
from manual work in XML files which I
00:34:34
often run into to using tooling that can
00:34:37
help you like devops repositories
00:34:41
automation uh easy tune for example to
00:34:44
move the overrides across by using a
00:34:46
common
00:34:47
repository asking Bob to take care of it
00:34:50
who can then ask a colleague to take
00:34:52
care of it or using cect products for
00:34:56
this with their migration wizard from
00:34:58
any scum to any other scum which I will
00:35:01
show you in a bit there are also
00:35:03
combinations possible there and likely
00:35:06
of course for migrations to SC Mii
00:35:09
Microsoft has a migration wizard in the
00:35:11
portal available to you as well for
00:35:14
other items for moving to scum and my it
00:35:17
might be the same story as moving from
00:35:19
one scum to
00:35:21
another because that is largely the same
00:35:25
so in order to avoid
00:35:28
running a long demo we actually uh put
00:35:31
in a few screenshots for the SCT
00:35:34
migration wizard to save time so this is
00:35:36
one of the examples here it's also one
00:35:39
of the sponsors hanging around in the
00:35:41
booths um so the migration wizard is
00:35:44
part of the MP Studio product you have
00:35:47
the right version of it so it can be
00:35:49
used to migrate between SC management
00:35:51
groups of the same version and to higher
00:35:55
versions so for example like like I said
00:35:58
from an older scom to a test scom which
00:36:01
is 2022 and then from a 2022 test to
00:36:05
2022 prod as an example but also to SC
00:36:09
mind we see here A whole list of things
00:36:12
that this wizard will try to take care
00:36:14
of once we select the source SC and
00:36:17
destination SC we get to the selection
00:36:21
of what we want to use this wizard for
00:36:23
now in this case I selected a few common
00:36:25
ones such as management packs uh user
00:36:28
roles Administration settings and
00:36:33
agents now when we get to the management
00:36:35
Pack story there are a few screens
00:36:37
showing which management packs cannot be
00:36:39
migrated and for what reason and which
00:36:43
ones can be migrated I just selected one
00:36:46
of the packs here to migrate as an
00:36:48
example like the DHCP I think I selected
00:36:51
here next we can select some user roles
00:36:55
because that is one of the things that I
00:36:57
wanted to migrate run as accounts
00:37:00
resolution States also and over here we
00:37:03
see a small selection of the settings
00:37:05
this wizard can move across the list is
00:37:08
actually longer than
00:37:10
that now when we skip ahead to the agent
00:37:13
section where we can move agents across
00:37:15
as well the great thing is that this
00:37:17
wizard tells you about what works and
00:37:20
what does not work and if there's
00:37:22
anything you should do yourself for
00:37:24
example like I said uh we might need to
00:37:27
distribute a runess account again to the
00:37:29
new management servers or um connecting
00:37:34
a web Watcher again all of these kind of
00:37:37
things they are explained in the Wizard
00:37:39
as well and we can see for example one
00:37:42
of the agents here uh cannot be migrated
00:37:46
because actually it was already there in
00:37:48
the New Management
00:37:51
Group all right so that was select now
00:37:55
let's do the same thing
00:37:57
uh but for the scom Mii migration wizard
00:38:01
from Microsoft so if you install a new
00:38:04
scom managed instance so as your
00:38:07
monitors come managed instance um one of
00:38:10
the first things you will see on the
00:38:11
welcome screen is this One Import your
00:38:14
existing on premises settings in
00:38:17
scmi now um and to uh to help you move
00:38:23
forward right so the current version of
00:38:25
this one only picks up the management
00:38:27
pack migration so keep that in mind
00:38:29
there is documentation on the Microsoft
00:38:31
site for other items and how to do it if
00:38:36
there are like export commands that you
00:38:37
can use and import or if there are some
00:38:40
settings which you should manually do
00:38:42
they have it all documented and this is
00:38:45
another one uh to help you with the
00:38:48
management
00:38:49
packs so there is a migration wizard
00:38:52
download which is a management pack as
00:38:54
well we load that on the old and the the
00:38:57
new uh Management Group so in the old
00:39:00
Management Group which has to be at
00:39:02
least SC
00:39:03
2019 as supported We Run The export
00:39:07
configuration task so that's the big
00:39:09
blue button in the middle you copy then
00:39:13
that export file to the other machine
00:39:15
where your scum console is connected to
00:39:17
scmi and then you import with the other
00:39:22
button um we have to configure a run ass
00:39:25
account to uh to run as as well and
00:39:29
after we do that after waiting a little
00:39:31
bit we will see in the SC monitoring
00:39:34
plane
00:39:35
onmi a list of men packs with either a
00:39:38
green state so green is saying it's
00:39:41
already migrated it's already there
00:39:44
yellow is saying we are ready to
00:39:47
migrate we can then run a task in the
00:39:49
scum console as you see here in the
00:39:51
bottom right far bottom right of the
00:39:54
screen migrate management pack and
00:39:57
if you do that it will start moving it
00:40:00
across as well um and you can multi
00:40:04
select multiple at the same time as well
00:40:07
um if it's red State then it indicates a
00:40:10
management pack that cannot be migrated
00:40:12
and it also will show the reason it
00:40:14
could be for example a third party
00:40:16
Shield management pack that is not yet
00:40:18
loaded in the new scum environment and
00:40:21
scmi can also not grab it from the
00:40:23
Microsoft catalog because the third
00:40:25
party packs are not there
00:40:28
so in that case you would have to
00:40:29
manually import the seal management pack
00:40:32
and then move over the
00:40:34
rest all right so I'm running out of
00:40:38
time so I can't show you more about this
00:40:41
right now so we are talking about
00:40:44
creating a one-day workshop on this
00:40:46
whole topic so the migration and upgrade
00:40:48
story very soon so uh feel free to
00:40:52
contact us just remember most migrations
00:40:54
are not 20 minutes clicking in a few
00:40:56
items and hoping that everything is
00:40:58
migrated there is usually a lot more to
00:41:01
do and a lot more
00:41:03
complexity and um yeah we have discussed
00:41:06
in previous slides that things can get
00:41:08
more complex I just wanted to make a
00:41:11
quick reference to our scum training
00:41:13
offerings at the different levels we run
00:41:15
these trainings at very low cost so the
00:41:18
threshold to follow one is very low we
00:41:21
regularly monthly run operator and admin
00:41:23
trainings which lead to the
00:41:25
administrator certification badge
00:41:27
following that we have specialist topics
00:41:29
which range from designing complex
00:41:32
environments we Al also have a scum Mii
00:41:34
training for which we are running a
00:41:36
special promotion so come and visit us
00:41:38
at the booth if you are really
00:41:40
interested in that authoring management
00:41:43
packs in the scum console that's also
00:41:44
one which is finished about this month
00:41:47
so we will start next month to actually
00:41:50
run that uh in public um and we are also
00:41:54
looking into uh the next training which
00:41:57
we will build is about dashboarding with
00:41:59
square up we will uh combine forces with
00:42:03
the square up team to build something
00:42:05
for you there as well um so given the
00:42:09
many questions that we receive around
00:42:11
newest versions of scum in relation to
00:42:14
how to get there which is exactly the
00:42:16
topic for today uh for my session today
00:42:20
um we actually decided to create a
00:42:22
workshop day on this topic and repeat
00:42:25
that regularly as well
00:42:29
all right so there is a Q&A session
00:42:32
right after this in the area in the uh
00:42:35
exhibition Hall um my colleagues will be
00:42:38
hanging around there as well so find
00:42:40
anybody with top core in the name um I
00:42:42
believe I am also in the next session
00:42:45
here which is a panel session in about
00:42:47
five minutes so I can run out uh answer
00:42:51
one question and then run back into the
00:42:53
to see the panel um what I will do is I
00:42:56
will will be available also after the
00:42:59
panel in the Q&A area so uh if you
00:43:03
cannot get your questions answered
00:43:05
around this topic or any other topic
00:43:07
please let me know and uh and I'll be
00:43:11
back there after the panel session as
00:43:13
well and of course I want to thank you
00:43:15
for listening in this event and thank
00:43:18
you very much to the sponsors as well
