Skip to content

Connect-ControlAPI command requires a ScreenConnect extension ID? #79

@crshovrd41

Description

@crshovrd41

I looked through a lot of the documentation but find no reference to anything about needing to have a ScreenConnect extension installed to make the connection. I looked through the code and can see that it is referencing CWCExtensionID, but when running Connect-ControlAPI, it doesn't ask for one.

I'm getting a 401 Unauthorized when attempting to connect. I tried another Control API from someone else and it doesn't reference an Extension ID, and it worked.

Is there something I'm missing?

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions