Installer download does not register organization input 6.4

franklinian 4 years ago updated 4 years ago 12

The installer does not properly register the organization entered when the download is built. All hosts are registered without an organization. This worked fine in previous versions.

ConnectWise Control Version:
Server Affected:
Host Client Affected:
Guest Client Affected:

Good afternoon,

Thank you for reporting this behavior. I had previously registered this issue with development, and it's currently under investigation.

I will update this thread as more information becomes available.



Further, the dropdown populated with existing organisations does not scroll and thus can not display all the options available.  This is on both the Installation Builder and when the installed session is edited in the host portal.

Good morning,

On what browser are you noticing that the organization list doesn't scroll? I tested with Chrome and found that it scrolls as expected.



Glad I found this, I thought I was going crazy...

I discovered this bug following upgrade to 6.4.15002.6500 yesterday. For me this affects MSI builds, EXE is working with Organization populated but not with a second Custom Property.


Yep, I can confirm this same Bug, building an msi today.

I don't seem to be able change the organization from the "All machines" menu.

I can see the deployment exists but organization field is blank.

Thank you everyone for submitting details about this behavior. Development has implemented a fix for this, and it should be available soon.


Good morning,

As of 6.4.15083 (the latest stable release of 6.4), clients should call back with the organization specified in the Build Installer modal.



looks fixed...


In an effort to test, since my server had been rolled back to version 6.4.15002, I uninstalled a RA Client 6.4.15083 to reinstall from a freshly downloaded installer.  Now I can't install because of an apparently missing DLL.  Error log:

Product: ScreenConnect Client (79fe5a42284c9743) -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.  Action FixupServiceArguments, entry: FixupServiceArguments, library: C:\Users\NIGEL~1.FAB\AppData\Local\Temp\MSIB6C0.tmp 

This occurs when trying a .msi or .exe

This legacy client installation requirement has been raised elsewhere for slightly different reasons, but is no less required.

After updating our on-premise server, the issue seems resolved with 6.4.15083.  Thank you.

Commenting disabled