If possible, I’d love to see a global install for EClinicalWorks. I’ve tried to create one for myself manually, but it won’t take for some reason. I even converted the .exe to a .msi, but couldn’t get it to install.
@Gav I have a client with this, last time I looked at this was probably 2 years ago and Immy didn’t have the features it does now. Willing to take a crack at this if it makes your list?
Hey James,
This is not something we’d be able to put in Global due to the installer being client-specific.
You need to contact eCW support via a ticket and ask for a bulk-deployment MSI. They have a specific version that allows you to easily mass-deploy. It will only take them 2-3 weeks to respond to you 
@Anthony_Birone
@DimitriRodis
@ Everyone willing to help
I know this topic is like 3 years ago. There has been a lot has changes in immy since then. My company is about to start using eCW. Is there any way I can install it using immybot? I have tried using the eCW provided MSI, Exe and script. they all work out of immybot. But I can’t get it to work through immybot.
A server URL parameter is also required.
I have tried using the script editor and following this metascript template as it is in the immy documentation
Invoke-ImmyCommand {
<# add powershell to run on the comptuer #>
}
I created a deployment to install it on a computer but i keep getting “The Test script did not return any output. Please ensure you output at least one $true or $false value to indicate compliance”
I am not sure what I am missing. I have been pulling my hair forever over this lol. I will appreciate your help.
Thanks
1 Like
We deploy ecw to multiple clients with a single Immybot ecw Software.
For version detection we used the upgrade cost Immybot suggested from uploading the MSI file
For installation we used #1877 Default MSI Install - with LogStream (Global)
The only difference with the eCW exe is it will install 2 pre-reqs Visual C++ 2013 x86 and x64 which is simple to do with Immybot
The real trick is we have an eCW configuration task, based loosely on the Immybot Global Task “Desktop URL Shortcut Template Task”. Our ecw configuration task has the following parameters: ShortcutName, TargetPath, WorkingDirectory, Arguments, Icon. Everything but Arguments has the default for eCW saved in the configuration task. TargetPath and WorkingDirectory are hidden.
The script for this configuration task is a generic local task script we have for creating shortcut icons in the public directory under the “Set” script category, Test and Get are disabled
$TestResult = $true
if(!$WorkingDirectory)
{
$WorkingDirectory = $TargetPath
}$ShortcutParams = @{
TargetPath = $TargetPath
ShortcutName = $ShortcutName
Arguments = $Arguments
WorkingDirectory = $WorkingDirectory
Icon = $Icon
}Write-Host “ShortcutName: $ShortcutName”
Write-Host “TargetPath: $TargetPath”
Write-Host “WorkingDirectory: $WorkingDirectory”
Write-Host “Arguments: $Arguments”Enforce-ShortcutAllUsersDesktop @ShortcutParams
In this way we install eCW with the same MSI but then add a desktop shortcut that is customizable from the deployment parameters. In this way Shortcut Name, Arguments and Icon can be changed per deployment.
Shortcut Name : When an org or doctor has multiple eCW server connection so there is clarity on which shortcut to use
Arguments: Is typically the server address you want to connect to, this is the only user specific configuration I have ran into thus far.
Icon: if you want to distinguish shortcuts by Icon
I have not seen any eCW specific install script from eCW, maybe that leads to a better method. That said our clients have been using a shortcut with URL link method to launch eCW before we started using Immybot so this has worked great.
Obviously past me was dummy for starting a script with $TestResult = $true, i don’t know why that is there, maybe it was just for testing and is no longer needed, maybe it is critical. Either way it probably is not desirable, but it seems to work.
2 Likes