What's going on, guys? It is Bernardo and today is all about
creating a Nvidia application package to deploy to your 9 to 5 job. So let's get right into
it. All right. So the first thing that we need to do is basically download whatever
Nvidia, you know driver you need to get, you know for your 9 to 5 job.
For this example, I am downloading the Quadro K1200 drivers
and I'm just going to basically select search it's going to give me this,
I'm going to click on download and I'm going accept and download it. It's going to download.
It's about, I would say 639 megabytes. Once that's completed. We're going to
the download folder now within the download folder, it's an EXE file,
so you are able to right click on the file and if you have seven zip installed,
you're able to select seven zip and then pick extract files and just click.
Okay. So it's going to extract all the files that you need
is going to give you this nice little folders, a double click on it. And all
these files inside this folder is what we need to create our package within SCCM.
So within SCCM, I went into this particular path
which is my server name sources. I have a folder called Drivers. I broke it down
to Nvidia and then the particular version of the card that I'm going to be pushing out the drivers.
Right? So I copy everything in here. Once you copy over the drivers, we are going to open
up our SCCM console and we're going to click on software. Within software we're going to
open up the app management node and within the app management node we're going to open up the apps.
Now I'm going to select application and I'm going to right click on it and I'm going to go to folder
and create a new folder. Now this folder name, I'm going to give it Nvidia because
I'm going to be updating and importing more Nvidia drivers and different styles.
So I definitely want to keep everything nice and organized. So we're going to click okay here
now within the folder, we're going to basically right click on it and then create a application
now rather than doing the first option.
Because this works well with MSI, we're going to select the second option. We're
going to specify the apps information. So we're going to click next here. We need to provide
information for this app. So I provided the following the publisher, the name
and the version, and we're going to click next here for the software center entry.
I just left everything as the default, so I click next here and this is where the magic
happens. So we're definitely going to click on Add within the deployment types section and we
are going to basically pick the second option because again, we're doing everything manually.
So we're going to click next here. We're going to provide a name
and make sure that you provide the language type for this package.
Click next here for the content location. I'm just basically giving it the UNC path of
where I copied those drivers into and for the installation program, I am going to call out
that setup dot exe file with the following parameters of no reboots
clean, no EULA no finish and passive from there we're going to click on next
this right here is important for this particular setup to work correctly.
A colleague of mine at my 9 to 5 job actually help me out on this. He was able to figure
it out and work with no problem. So from here we are going to click on Add clause
and we are going to change the following settings.
Now the settings type is going to be a registry for the hive. We're going to focus on the HKEY
local machine. And for the key we're going to give it the following. Now, for the value we're going
to do driver version, we're going to make sure we enable the registry key is associated to a 32 bit
application or 64 bit system. And for the data type, we're doing version now for the last
option we're going to enable this registry setting must satisfy the following rule.
So the operator is going to be greater than or equal to the following value, right?
And once you do all that, click okay. And we're going to click
next here for the installation behavior. We're going to pick install for system,
make sure the login requirement is only when a user is logged on installation
program visibility I'm going to keep it as normal for the maximum allowed runtime.
I change this to 60 once you do all of that, we're going to click on next. We don't need any
requirements, so we're going to click next here for the dependencies. There's none. So click next.
You're going to get a nice little summary next here.
You should get all green checkmarks, which is always a good thing and we're going to
close it. And it takes you back here once it takes you back here. Click next. It's
going to give you another summary. This is basically finishing up the wizard
of creating an application within SCCM and click next there.
Green Checkmarks Always a good thing and we're going to close it. From there,
pick your collection, deploy it, test it out, and hopefully this works out within your environment
and that's it. Hopefully guys enjoy and I catch you guys on the next one peace out.