script to check the last 3 characters of the registry entry
Hi Team,
We are planning to distribute the device drivers according to the model of the machine, from SCCM. Device drivers are placed in the SCCM share.Device driver folders are named in such a way that only model number will be there.eg E6410. So we need a script to check the last 3 characters of the registry [HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemProductName.] eg:Dell Latitude E6410 ;Last 3 characters =410. so that it will compare the share and download the corresponding device driver folder to the local machine.
Any thoughts on this..?
regards
Anphi
We are planning to distribute the device drivers according to the model of the machine, from SCCM. Device drivers are placed in the SCCM share.Device driver folders are named in such a way that only model number will be there.eg E6410. So we need a script to check the last 3 characters of the registry [HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS\SystemProductName.] eg:Dell Latitude E6410 ;Last 3 characters =410. so that it will compare the share and download the corresponding device driver folder to the local machine.
Any thoughts on this..?
regards
Anphi
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
It might be more robust to build collections based on a query for the relevant string in hardware details and have your package targetted at the various collections.
Posted by:
anphi
13 years ago
Thanks VBScab for your quick response...
I think collection based query can be done only through SCCM..client wants a content apps kind of procedure so that whenever the client put some additional files, it must be copied to the local machine according to the model number...their main intension is a kind of automation...
I think collection based query can be done only through SCCM..client wants a content apps kind of procedure so that whenever the client put some additional files, it must be copied to the local machine according to the model number...their main intension is a kind of automation...
Posted by:
anonymous_9363
13 years ago
I think collection based query can be done only through SCCMEr...
We are planning to distribute the device drivers according to the model of the machine, from SCCM. Device drivers are placed in the SCCM share.So....your client is using SCCM but isn't using SCCM. Bizarre...
A scripted solution - or even a proper tool as an EXE - is going to be a nightmare. How will you control failed downloads? Failed installs? It doesn't bear thinking about...
Posted by:
anphi
13 years ago
Option Explicit
' Open the WScript.Shell object to read the registry key.
Dim objWS, strKeyValue, strKeySuffix
Set objWS = CreateObject("WScript.Shell")
strKeyValue = objWS.RegRead("HKLM\HARDWARE\DESCRIPTION\System\BIOS\SystemProductName")
' Get last three characters of the key value.
strKeySuffix = Right(strKeyValue, 3)
msgbox strKeySuffix
' Open the WScript.Shell object to read the registry key.
Dim objWS, strKeyValue, strKeySuffix
Set objWS = CreateObject("WScript.Shell")
strKeyValue = objWS.RegRead("HKLM\HARDWARE\DESCRIPTION\System\BIOS\SystemProductName")
' Get last three characters of the key value.
strKeySuffix = Right(strKeyValue, 3)
msgbox strKeySuffix
Posted by:
anonymous_9363
13 years ago
That takes care of the part dealing with the last 3 characters but what about the driver installation? Where's the rest of the script (didn't you say that the client doesn't want to use SCCM?)
Posted by:
anphi
13 years ago
Hi VBScab,
As I mentioned earlier, client wanted to use Content App for the driver, so that in future if a new machine is introduced in the network, it will download the corresponding drivers to a specific location in the local machine.We are using robocopy.exe for downloading the drivers(it will download only if there is any differences in the source location and the target location)
regards
Anphi
As I mentioned earlier, client wanted to use Content App for the driver, so that in future if a new machine is introduced in the network, it will download the corresponding drivers to a specific location in the local machine.We are using robocopy.exe for downloading the drivers(it will download only if there is any differences in the source location and the target location)
regards
Anphi
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.