Welcome to our community!

Digitally signed pkg files for MDM deployment to macOS systems

Andrea Rochira

5 years ago
updated 2 years ago
Pending Review

Our company recently transitioned to ConnecWIse Control. A great product, although on macOS systems, Gatekeeper dislikes the "unidentified developer" property of the pkg file.

This poses two problems:

many times, the support technicians have to guide end-users through multiple System Preferences settings in order to successfully establish a connection
when the pkg file is deployed through an MDM platform (and it's not internally signed by the company), the installation fails

It would be much appreciated to include one of the following features in Control:

pkg files automatically signed by ConnectWise
upload a company developer certificate that can be used to sign the pkg files

Thanks

Duplicates 3

Allow upload of developer certificate for signing mac installers

Watchman Monitoring

Unsigned packages are particularly hard to deal with on a remote session.

Developer Identities are $99 a year and easy enough to purchase. It would be great if a screenconnect server could store ours, and allow for on-the-fly signing of packages.

add version number in MacOS pkg file for MDM deployment.

Marco

Currently the .pkg package does contain a buildNumber (eg. 6.6.18120.6697) but not a VersionNumber. We just had a Microsoft PSS call regarding not installing this package through intune and their conclusion was the missing version number.

To quote MS "his is limited by what is supported by the Mac OS MDM. The version is not in the intunemac file but in the actual application packaging. To make such a change will require contacting the person/company that created the app and suggest they make the necessary changes."

Please add the VersionNumber property to the .pkg installer for connectwise control.

Kind regards,

Marco

have the .pkg installer signed

scott

Replies 19

Newest first
Newest first Oldest first

John Case

2 years ago

Can you please just make a .mobileconfig file that we can use with MDM solutions? I believe everything else is in place, but a .mobileconfig file would make setting the Mac permissions SO MUCH easier. The software updates continue to cause updates for our managed Macs.

Reply Link

John Case

3 years ago

I just got off a chat session and was told to submit a feature request. Obviously after 5 years, they could care less.

Reply Link

Andrea Rochira

5 years ago

Since it doesn't seem a priority for the ConnectWise dev team to provide the digital signing of the pkg files, this feature would be a very much appreciated (and maybe easier to implement) alternative.

Reply Link

Caitlin M Barnes Team Member

6 years ago

Hi Marco,

Are you still having problems deploying the MacOS .pkg?

Caitlin

Reply Link

George Oosthuizen

7 years ago

Yes please, just moved from Teamviewer and our ad-hoc support sessions have visibly increased in times to close and it's just due to end-users struggling to override gatekeeper.

And it's not an easy attack vector but not as secure as it could be.

Reply Link

anonymous

7 years ago
Under Review

Reply Link

Marc L. Mintz

7 years ago

one more vote for Apple signing. We love CONNECT, but it cannot be used with many of our clients due to regulatory or security issues. The other developers in this category have found ways for customization AND still qualify for signing.

Reply Link

Ian

8 years ago

I support a LOT of Macs and having a signed installer would be much better. Right now, I direct my Mac users to Team Viewer because your app is too much for them to install.

Reply Link