New-Shortcut -Path " $ env:ProgramData\Microsoft\Windows\Start Menu\IBM i Access Client Solutions\RegisterAssociations.lnk " -TargetPath " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe " -Arguments "=true /PLUGIN=fileassoc dttx dtfx hod bchx ws " -Description "Repair file associations IBM i Client Access Solutions " -IconLocation " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.Until just a few years ago, the IBM i and its predecessors were used almost exclusively in a closed environment, and their operating systems provided the strongest data and system security in the world. # A workaround we use is to just create a shortcut that the end user can launch manually to re-register them If deployed as required but there is no user logged on - it will fail to register. # Known issue - the associations are only registered for the currently logged on user. $installPhase = 'Post-Installation 'Įxecute -ProcessAsUser -Path " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe " -Parameters "=true /PLUGIN=fileassoc dttx dtfx hod bchx ws " -Wait New-Shortcut -Path " $ env:ProgramData\Microsoft\Windows\Start Menu\IBM i Access Client Solutions\ACS Session Mgr.lnk " -TargetPath " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe " -Arguments "/plugin=sm " -Description "IBM i Access Client Solutions - Session Manager " -Hotkey "CTRL+ALT+SHIFT+B " -IconLocation " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe " -IconIndex "5 " -WorkingDirectory " $ env:PUBLIC\IBM\ClientSolutions\ "
New-Shortcut -Path " $ env:ProgramData\Microsoft\Windows\Start Menu\IBM i Access Client Solutions\Access Client Solutions.lnk " -TargetPath " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe " -Description "IBM i Access Client Solutions " -Hotkey "CTRL+ALT+SHIFT+A " -IconLocation " $ env:PUBLIC\IBM\ClientSolutions\Start_Programs\Windows_x86-64\acslaunch_win-64.exe " -IconIndex "0 " -WorkingDirectory " $ env:PUBLIC\IBM\ClientSolutions\ " # You don't need to include all the files from the IBM package, here's the bare minimum folder structure:Ĭopy-File -Path " $dirFiles\* " -Destination " $ env:PUBLIC\IBM\ClientSolutions\ " -Recurse -ContinueFileCopyOnError $true
If 3010 is passed back to SCCM, a reboot prompt will be triggered.Ĭhanges to "user install mode" and back to "user execute mode" for installing/uninstalling applications for Remote Destkop Session Hosts/Citrix servers.ĭisables logging to file for the script.
NonInteractive mode is automatically set if it is detected that the process is not user interactive.Īllows the 3010 return code (requires restart) to be passed back to the parent process (e.g. Options: Interactive = Shows dialogs, Silent = No dialogs, NonInteractive = Very silent, i.e.
Specifies whether the installation should be run in Interactive, Silent, or NonInteractive mode.
The script dot-sources the AppDeployToolkitMain.ps1 script which contains the logic and functions required to install or uninstall an application. The install deployment type is broken down into 3 main sections/phases: Pre-Install, Install, and Post-Install. The script either performs an "Install" deployment type or an "Uninstall" deployment type. The script is provided as a template to perform an install or uninstall of an application(s).