![]() ![]() $link = $Shell.CreateShortcut($DesktopPath "\\ACS Session Mgr.lnk") ![]() $link.IconLocation = $target2 $win_exe ",0" $link.Description = "IBM i Access Client Solutions" $link = $Shell.CreateShortcut($DesktopPath "\Access Client Solutions.lnk") $Shell = New-Object -ComObject (" WScript.Shell") ![]() $Cmd_args = "/PLUGIN=fileassoc dttx dtfx hod bchx sql ws" $clCmd_args = "/PLUGIN=fileassoc dttx dtfx hod bchx sql ws /c" $win_exe = "\Start_Programs\Windows_x86-64\acslaunch_win-64.exe" $target2 = $InstallPath "\IBM\ClientSolutions" Registry: HKLM\SOFTWARE\JavaSoft\Prefs\com\ibm\iaccess Exists Powershell.exe -ExecutionPolicy Bypass -File Install.ps1 -Verb RunAs -WindowStyle Hiddenįolder: C:\Users\Public\IBM\ClientSolutions\Start_Programs\Windows_x86-64 Existsįile : C:\Users\Public\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe Exists Once I create an uninstaller script I will post that. When deploying I found that this needs to be run as the user, that was the cause of the hang, I had the deployment set to run as SYSTEM. I just copied my PS script to the root of the folder for content source and run from there.Įdit 8/2/18: Made changes to script and traced root of issue mentioned in my comment below. We initially ran install_acs_64_allusers.js with the /AdminConfig switch to create the AcsConfig.properties file. I use this to deploy iAccess Client Solutions via an SCCM Application. Here's a script I created based off of the install_acs_64_allusers.js file provided by IBM. As a general rule, if someone has flair, they almost definitely know what they're talking about. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |