Hi,
No it does not get created in that path either. I have been using Active Setup for some time now with this tool, and coding it directly as needed in my CMD or VBS deployment files. Thanks for the tip on the REG vs REGEDIT but at this point REGEDIT does work in my environment quite nicely.
Set-ActiveSetup does NOT appear to be working in any of my tests, does it work for you?. I had been using version 3.5.0 for some time and had a work around for creating this key. It does work nicely but the Set-ActiveSetup function will be much easier to manage going foward.
Here is what I have been using all along as a work around. No issues are found with this method:
No it does not get created in that path either. I have been using Active Setup for some time now with this tool, and coding it directly as needed in my CMD or VBS deployment files. Thanks for the tip on the REG vs REGEDIT but at this point REGEDIT does work in my environment quite nicely.
Set-ActiveSetup does NOT appear to be working in any of my tests, does it work for you?. I had been using version 3.5.0 for some time and had a work around for creating this key. It does work nicely but the Set-ActiveSetup function will be much easier to manage going foward.
Here is what I have been using all along as a work around. No issues are found with this method:
Set-RegistryKey -Key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\DataLinkViewer_ODBC_UserSetup' -Name 'Version' -Value '1' -Type String
Set-RegistryKey -Key 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\DataLinkViewer_ODBC_UserSetup' -Name 'StubPath' -Value 'regedit.exe /S "%SystemDrive%\Program Files (x86)\DataLink Viewer 11\DesChampsLive_DataLink_Viewer.reg"' -Type ExpandString