Export odbc connection windows 10 code#

Export odbc connection windows 10 code#

ItвЂ™s a little bit more code, but itвЂ™ll run on the remote computerвЂ™s CPU and I myself believe this is a more stable way of executing code against a remote computer.Дocumentation for Invoke-Command can be found here: (v=wps.630).aspxДЄnd documentation for New-PSSession (and others) can be found here: (v=wps.630). For information about setting the Use Only SSPI advanced option, see Configuring Advanced Options on Windows on page 17. DonвЂ™t forget to remove the session in the end by using Remove-PSSession. Then you can use Invoke-Command to locally run Add-ODBCdsn on the remote computer through a ps remote session. reg file (s) to import the DSN data sources to the registry (select Yes and OK when. reg file (or files if you have both User and System DSN data sources) to any location Computer B. So thereвЂ™s also this option: create a new- PSSession to the remote computer (In this case you can also specify the account youвЂ™d want the script to be ran as, which can be very handy if you need to use another user account). Right-click on the ODBC.INI folder, choose Export, and save the. Sometimes working against a remote computer will return a different result than when you run it locally. So you should be able to just enter the remote computer name after this command and if the account youвЂ™re running the PS script from has the correct access rights on the remote computer, it should create it. The default is the current session on the local computer. Enter a computer name or a session object, such as the output of a New-CimSession or Get-CimSession cmdlet. Runs the cmdlet in a remote session or on a remote computer. IвЂ™ve not ran this against a remote computer myself, but according to documentation provided by MS, you should use the -CimSession switch: -CimSession