What's going on guys, it is Bernardo from the BTNHD and today is all about SCCM 2002
and upgrading.
So let's get started.
First things first, I have my SCCM console up and running, I'm going to click on the
little tab on the upper left side.
And I'm going to go inside about Configuration Manager.
And I'm running 1910.
1910 is one of those requirements that you need to run 2002.
OK, so I'm going to close that up.
I typically like to go inside service manager it's going to ask me to connect to my site.
So I'm going to enter my SCCM site, click OK.
There's three components that I like to make sure that they are running successfully behind
the scenes, right.
So the first one is Configuration Manager update, selected, right click on it and click
on query and it's going to start running.
And the next tool that I like to make sure that it is running is the DMP downloader.
Again, right click on it, make sure that you click on query to run it and the last one
is the DMP uploader again, make sure that's running.
Those are the three components that I like to make sure that they are running.
With no issues, I'm going to provide this EXE file, and I'm going to upload it to my
GitHub and I'm going to place the link at the bottom or maybe at the comment section,
I'm going to right click on that EXE file, run it as an administrator, this is going
to load up I'm going to click on Browse.
I'm going to click on desktop, click OK.
Click on unzip, click OK.
And then I'm going to close that.
And then on the desktop, you're going to see your PowerShell power script, you know, which
is cool.
Now I'm going to click on the Start menu, and I'm going to type in Windows PowerShell,
or PowerShell.
And I'm going to right click on the PowerShell ISE because that's what I like to run and
I'm going to run it as an administrator and it's going to start loading up.
I'm going to click on file, click on open and I'm going to locate that PowerShell script
that we just unzipped together.
I'm going to select it click on Open is going to load up.
You're going to hit that power button to load up the PowerShell script and it's going to
ask you for your site server.
Now for the site server, I normally enter my full qualified domain name.
And that's what I entered, hit Enter, and then boom, if everything works well, you should
get the command completed successfully, which is always a good thing.
So we're going to close that up.
And the next thing that we need to do is click on your start menu, click on Configuration
Manager console, it's going to start loading up connecting to the site database.
And once you here, the next thing that we need to get into is administration and within
administration go to updates and servicing.
And then once you're in there, you're going to see your configuration manager 2002.
And the state is going to indicate ready to install.
We're going to select it, right click on it and install update pack.
And I'm going to leave everything as default.
I'm not even going to check ignore any prerequisites.
So I'm going to click on Next.
These are all the features that this particular update is going to provide.
You are able to go through the list and pick what you want within your testing lab or within
your environment.
Click on Next I'll leave the default as upgrade without validating and then click Next, accept
the license and terms and then click Next.
Nice little summary.
Next again is going to do the progress.
And then once everything is completed, you should get a green checkmark green checkmark
is always a good thing.
underneath the state column, it's going to start saying installing which is a good thing.
Now if you forgot to pick particular features within this update, you are able to still
pick it within updates and servicing.
If you kind of open that guy up and go inside features, you're going to see all the features
that that particular package or build for SCCM has, you're able to enable it here.
now back inside updates and servicing is still going to state installing if you want to like
you know see what's going on.
Just click on refresh and the state is going to change you are able to select it and then
click on show status is going to take you over here.
So select that right click on it and then click on show status, which will give you
a nice little bird's eye view of what's going on.
from here as you can see It's already done with the downloading part.
And it's going to start doing other steps that it needs to successfully install SCCM
2002.
If you go back inside updates and servicing, if you see the state is going to indicate
installing this process takes a while.
So I would say go to lunch, go grab a cup of coffee, read a comic book, read a book,
do something else.
And eventually, if you come back to it, and it still says installing, click on the button
that says refresh, and then you should get this, click OK.
The entire console is going to close.
You're going to get this it's going to start stating that downloading files and then you're
going to get preparing to install, right it's going to prepare itself to install the console
or upgrade the console for you.
I know a lot of issues upgrading my console.
But if you guys want to know behind the scenes, what's actually going on, if you go to the
C drive, there's two logs that you could look into, to actually tell you what's going on.
These are the two that you could open up and look at the status.
Eventually this popped up And I was like, okay, I've seen this before.
So I right clicked on my Taskbar went to task manager, I saw the Microsoft Configuration
Manager is still running.
So I right clicked on it end the task went back here, retry, and it did not work.
So like I said before, you're able to go inside the C drive, open up one of those log files,
I opened up the config manager admin UI set up, and I was checking out everything and
it was stating, installation failed, because in another program was installing.
So I'd say what's what this is the first installation.
Why is this happening?
I retry that again.
And eventually it kind of just gave me a red error and I was looking around and it looks
like the package to MSI package was downloaded successfully and as a bunch of parameters
that SCCM tries to use to install it for you.
So I said to myself, hmm, let me look into this.
Let me right click on it copy to clipboard, I opened up notepad and I paste everything
just to look at it clearly.
So automatically tells me the package path where the MSI is that, and it also gives me
the properties, the parameters that I need to run.
So I said, Okay, let me modify this a little bit, so I could run it manually.
So that's what I did.
I modified it, and I changed it.
So I could run it manually.
So I select that entire line that I created.
I right clicked on it,I copied it, right click on my start menu, and I ran command prompt
as an admin, what I did was I did a CD to the path where that MSI is located and I hit
Enter, because I need to be inside that folder.
So from here once I'm inside that folder, what I did was I called the admin console
dot MSI with the parameters that I got, I hit Enter, it started searching for the applications.
And eventually I got this, which is a good sign.
I clicked on next I clicked on next again, the default location for my installation stuff
was the D drive, which was good.
I clicked on next on that install, and started validating the installation.
Eventually I got this which was awesome.
So I clicked on Finish and I was like, and I waited.
And I waited.
I was like what the hell the console hasn't opened up.
I know I checked that little checkbox.
Once the wizard is done open up the console so it didn't open up.
So I clicked on Start Menu,
I located the Configuration Manager console, open it up, I started connecting to the site
database, I started praying to the SCCM Gods the deployment Gods like please, please nothing's
corrupted, please open up.
So eventually it did open up.
But I got a nice little warning at the top saying required components of the console
is out of sync with your site.
So I clicked on the little link that says install the new console version.
I was like, Okay, let me try it out.
See what happens.
I clicked on it.
The entire console closed on me.
I started seeing this I was like all boy, not this again.
So it started doing its magic.
And eventually my console opened up again.
I was like, Okay, this is a good sign.
It started connecting to the side database.
And again, I starting I started praying to the deployment gods like please, please nothing
corrupted just work and then bam, no problems, no errors.
Awesome.
So Click on the menu on the upper left corner, went to about Configuration Manager and boom,
the version was upgraded 1910 to 2002.
Now a couple of things that you could do is go inside administration, and within administration
going inside site configuration, going inside sites, highlight your site, right click on
it, go to properties.
And then if you look at your version and build number, it's changed.
That's an indication that kind of tells you Okay, your stuff was upgraded successfully.
Awesome.
Another way is to go inside software library.
go inside application management and packages, make sure that your configuration packages
are up to date, you're able to select one of them and at the very bottom, you should
see a status of success.
I got one failed because I actually have two sites right now within my network.
The primary one is the one that you guys see right here, the SCCM and my secondary is the
one that failed so I'm not too worried about the secondary one right now.
You are able to also go inside operating systems.
And then go to boot images and just make sure that your 64 bit and 86 bit boot images are
up to date.
If you select one of them and right click and go to properties, and if you go inside
data source, you should see within the source version that it's a new number as well as
the date and time when you upgraded your SCCM.
Last but not least, you are able to go on inside administration sites and select your
site and then click on hierarchy settings.
And then from here, click on client upgrades and then it will tell you your production
client version as well as your pre production client version it will give you It gives you
a nice little indication that is running 5.00.8968.1012 and it also gives you the date and the time
that you pushed out the upgrade to your SCCM. hopefully you guys enjoy make sure to hit
that like button also subscribe and share about the video and I catch you guys on the
next one.
Peace out!