Our ScreenConnect environment uses CustomProperties other than 1. We had to create custom deployment / task to set the other properties but would like to get away from using local items if possible.
Seeing as how the global CW Control integration allows choosing which property to use for identification, I think it makes sense to have the option to specify the other properties for deployment and/or maintenance tasks globally.
Totally agree, upvoted.
What needs to happen is the cmdlets need to be added on the ImmyBot side that will leverage the appropriate API calls to make those changes. Once that’s done, the rest is just a few lines of powershell in the existing scripts.
Go get some more votes!!
Hi, did you manage to create the custom tasks for the properties with scripts? If so, would you please share as we are trying to create scripts for this as well.
In the Install ScreenConnect task section where it’s building the install string, we tack on “&c=&c=&c=&c=&c=&c=$TenantName”;
Original
$DesiredParameters['p'] = $ControlInstanceInfo.Port
$DesiredParameters['c'] = $TenantName
$DesiredParameters['k'] = $ControlInstanceInfo.PublicKey
$Params = $DesiredParameters.ToString();
$DesiredParameters['p'] = $ControlInstanceInfo.Port
$DesiredParameters['c'] = $TenantName
$DesiredParameters['k'] = $ControlInstanceInfo.PublicKey
# Setting Custom Property 8 to Tenant Name
#$Params = $DesiredParameters.ToString();
$Params = $DesiredParameters.ToString() + "&c=&c=&c=&c=&c=&c=$TenantName";