Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 818
  • Last Modified:

ODBC VBS Scripts not showing in ODBS Administrator

I have three VBS scripts that run when a user logs into a workstation. The scripts enter in values for ODBC Drivers that are needed for our ERP system.

The problem I am having is the scripts run, the registry entries are enter into the registry but the they do not show in the ODBC Administrator so our ERP system does not see them.

What changes do I need to make for when the script executes the entries will show in the ODBC Administrator?

'This is the code for the .vbs script that run at user login
'File name is CRGUP.vbs
 
Const HKEY_LOCAL_MACHINE = &H80000002
 
strComputer = "."
 
Set objReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & _ 
    strComputer & "\root\default:StdRegProv")
 
strKeyPath = "SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources"
strValueName = "CRGUP"
strValue = "CR SQLBase"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strKeyPath = "SOFTWARE\ODBC\ODBC.INI\CRGUP"
 
objReg.CreateKey HKEY_LOCAL_MACHINE,strKeyPath
 
strKeyPath = "SOFTWARE\ODBC\ODBC.INI\CRGUP"
 
strValueName = "Database"
strValue = "CFI"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "Description"
strValue = "Visual"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "LogonID"
strValue = "SYSADM"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "Driver"
strValue = "C:\WINDOWS\system32\crgup13.dll"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "InputMessageSize"
strValue = "0"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "Timout"
strValue = "300"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "NoRecovery"
strValue = "0"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "ReleasePlan"
strValue = "0"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "ServerName"
strValue = "server1"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "Servers"
strValue = ""
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "ApplicationUsingThreads"
strValue = "1"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
strValueName = "CursorCacheSize"
strValue = "6"
objReg.SetStringValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,strValue
 
'Below are the registry entries
'File name is CRGUP.reg
REGEDIT4
 
[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\CRGUP]
"Database"="CFI"
"Description"="Visual"
"LogonID"="SYSADM"
"Driver"="C:\\WINDOWS\\system32\\crgup13.dll"
"InputMessageSize"="0"
"Timout"="300"
"NoRecovery"="0"
"ReleasePlan"="0"
"ServerName"="server1"
"Servers"=""
"ApplicationUsingThreads"="1"
"CursorCacheSize"="6"

Open in new window

0
TheMetrix
Asked:
TheMetrix
  • 3
  • 2
1 Solution
 
RobSampsonCommented:
Hi, if you have the CRGUP.reg file already created (and tested whether just importing this allows the connection to appear in ODBC), then you should only need that reg file located on a network share, then use the following VBS:

Set objShell = CreateObject("WScript.Shell")
objShell.Run "cmd /c regedit /s \\server\share\CRGUP.reg", 0, True

Regards,

Rob.
0
 
TheMetrixAuthor Commented:
That worked great Rob, Thanks!!!!!

One more thing though. This is a domain system, I have users that are not local admin or Power Users so the .reg file is not imported. I've allowed the use of registry tools but those logins still do not let the .reg file import. Any suggestions?
0
 
TheMetrixAuthor Commented:
I guess what I am trying to find is to still leave the user as normal user but run the logon scripts with a higher priv level.
0
 
TheMetrixAuthor Commented:
I put the script in the computer configuration script start up instead and it works great!!!

Again thanks Rob, you are a life save bro.
0
 
RobSampsonCommented:
Hi, no problem!  Sorry I couldn't get back to you earlier, that's the problem with being on the other side of the world I suppose!

Anyway, yes, making this a StartUp script would work for two reasons:
1) A StartUp script runs under the local System account, meaning it has full control over the local computer, and can access only the NetLogon share of a domain controller, in terms of Network Access.
2) The registry keys are HKLM, and *not* HKCU.  This means that the keys apply to the whole computer.  If the keys had to be HKCU, the System account would not know which user to apply it to, because no user has logged in yet.

Regards,

Rob.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now