You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Documentation/Administration/preferences.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ These can be managed in the individual tenant, or from Show More > Preferences a
53
53
|| Computers Excluded From Maintenance | Add/Remove computers that should be excluded from sessions. An excluded computer cannot have any software or tasks deployed to it. However, inventory will still be run on it. | Drop Down Selection |
54
54
|| Exclude From Cross-Tenant Deployments and Schedules | When enabled, this tenant and its computers will not be considered when resolving cross-tenant deployments and schedules. | Bool |
55
55
|| Onboarding | Enabling this feature will allow newly synced computers to be onboarded. | Bool |
56
-
|| Onboarding Patching | Enabling this feature will allow for patching during onboarding. This currently only works when the CW Automate integration is enabled.| Bool |
56
+
|| Onboarding Patching | Enabling this feature will allow for patching during onboarding. This currently only works when the ConnectWise Automate integration is enabled. | Bool |
57
57
| Users | User Affinity Sync | Logs the current logged in user to determine who uses a computer. The System User Affinity Sync setting must be enabled for this to take effect. | Bool |
58
58
| Maintenance | Business Hours | Set the business hours. | Time Selection |
59
59
|| Default Time Zone | Set the timezone to be used for this tenant. | Drop Down Selection |
Copy file name to clipboardExpand all lines: Documentation/FAQ.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -352,7 +352,7 @@ Yes, we welcome feature requests and contributions from our community! Please su
352
352
353
353
#### Domain Join didn’t work, what gives?
354
354
::: details It's likely that the DC is missing entirely, or ImmyBot hasn't identified the agent as a DC
355
-
Make sure there is a Domain Controller in ImmyBot for the machine. If you are using a supported RMM like CW Automate/Control setup the integration so the Domain Controller is imported automatically. Otherwise, you’ll need to install the ImmyAgent on a domain controller for that customer.
355
+
Make sure there is a Domain Controller in ImmyBot for the machine. If you are using a supported RMM like ConnectWise Automate/Control setup the integration so the Domain Controller is imported automatically. Otherwise, you’ll need to install the ImmyAgent on a domain controller for that customer.
356
356
357
357
If the Domain Controller doesn’t have the red “Domain Controller” designation, press “Run Inventory”. This may happen if it was recently added to ImmyBot.
Copy file name to clipboardExpand all lines: Documentation/HowToGuides/Tasks/ConfigureDirectory.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ An active ImmyBot subscription or [trial](https://www.immy.bot/pricing/)
17
17
18
18
Permissions to configure Deployments
19
19
20
-
You will need to set up a DEM user for each of your tenants if you're planning on joining to AzureAD
20
+
You will need to set up a DEM user for each of your tenants if you're planning on joining to AzureAD.
21
21
22
22
If you need to add the computers to AzureAD, you need to set up automatic [Intune Enrollment](https://learn.microsoft.com/en-us/intune/intune-service/enrollment/quickstart-setup-auto-enrollment)
Copy file name to clipboardExpand all lines: Documentation/Integrations/connectwise-control-integration-setup.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,21 @@
1
-
# ConnectWise Control
1
+
# ConnectWise ScreenConnect
2
2
3
3
Setting up this integration allows you to
4
-
1. Import customers from Control
5
-
2. Import computers from Control
6
-
3. Manage all computers in Control without deploying the ImmyBot Agent
7
-
4. Remote into computers from the ImmyBot interface using Control (Note: We default to requiring customer consent, you can disable this under Settings->Preferences)
8
-
5. Fix the Automate agent using the Control agent (by creating a cross-tenant deployment for the Automate Agent and creating a schedule for your customers)
4
+
1. Import customers from ScreenConnect
5
+
2. Import computers from ScreenConnect
6
+
3. Manage all computers in ScreenConnect without deploying the ImmyBot Agent
7
+
4. Remote into computers from the ImmyBot interface using ScreenConnect (Note: We default to requiring customer consent, you can disable this under Settings->Preferences)
8
+
5. Fix the Automate agent using the ScreenConnect agent (by creating a cross-tenant deployment for the Automate Agent and creating a schedule for your customers)
By default most ConnectWise ScreenConnect instances you would select 1 for the ClientName CustomProperty field, this is the "Company" property in ScreenConnect.
28
+
Secondary group is any number between 1-8 that you would like to group from based on ScreenConnect groups.
29
+
You can find more infomation about ScreenConnect custom propertys here;
@@ -43,9 +43,9 @@ When you map a customer from an RMM, the computers will undergo Identification
43
43
44
44
## Troubleshooting
45
45
46
-
ConnectWise Control uses Sqlite under the hood, making it vulnerable to performance issues unless aggressive Database Maintenance Tasks are enabled.
46
+
ConnectWise ScreenConnect uses Sqlite under the hood, making it vulnerable to performance issues unless aggressive Database Maintenance Tasks are enabled.
47
47
48
-
While ImmyBot only uses Control (and other integrations) to spawn an out-of-band connection, over the course of time the database can grow as ImmyBot establishes this connection on each machine once every 24 hours to collect inventory.
48
+
While ImmyBot only uses ScreenConnect (and other integrations) to spawn an out-of-band connection, over the course of time the database can grow as ImmyBot establishes this connection on each machine once every 24 hours to collect inventory.
49
49
50
50
Commands go into the SessionEvent table with EventType = 44
51
51
Responses go into SessionConnectionEvent with EventType = 70
@@ -62,14 +62,14 @@ Access Sessions: Purge records of session connections older than 7 days for Host
62
62
63
63
### Manual Cleanup
64
64
65
-
If you host Control yourself, you can restore performance by doing the following
65
+
If you host ScreenConnect yourself, you can restore performance by doing the following
66
66
67
67
Download and Install [DB Browser for SQLite](https://sqlitebrowser.org/) on your server
68
68
Open `C:\Program Files (x86)\ScreenConnect\App_Data\session.db`
69
69
Navigate to SQL Editor
70
70
Paste in the following SQL
71
71
72
-
#### Soft delete all commands and responses (This usually solves the problem without kicking everyone out of Control)
72
+
#### Soft delete all commands and responses (This usually solves the problem without kicking everyone out of ScreenConnect)
73
73
```sql
74
74
update SessionEvent set EventAttributes =1where EventType =44;
75
75
update SessionConnectionEvent set EventAttributes =1where EventType =70;
Copy file name to clipboardExpand all lines: Documentation/Reference/terminology.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -226,9 +226,9 @@ To ImmyBot, an RMM is a system that provides a list of computers, and a mechanis
226
226
227
227
228
228
229
-
To avoid having to deploy the ImmyAgent to existing machines, ImmyBot optionally integrates with RMMs like ConnectWise Automate and ConnectWise Control and uses their agents instead. These systems are not as performant as the ImmyAgent, but can supplement ImmyBot functionality.
229
+
To avoid having to deploy the ImmyAgent to existing machines, ImmyBot optionally integrates with RMMs like ConnectWise Automate and ConnectWise ScreenConnect and uses their agents instead. These systems are not as performant as the ImmyAgent, but can supplement ImmyBot functionality.
230
230
231
-
For example, if you add an RMM Link for ConnectWise Control, you can open a remote session to the computer directly within ImmyBot:
231
+
For example, if you add an RMM Link for ConnectWise ScreenConnect, you can open a remote session to the computer directly within ImmyBot:
232
232
233
233
234
234
@@ -238,7 +238,7 @@ You can even add multiple RMMs of the same type, which is often useful in merger
238
238
239
239
## Identification
240
240
241
-
Because the same computer often exists in multiple RMMs (Like how CW Automate typically installs CW Control Automatically), ImmyBot prevents duplicates by identifying the computer by a unique id. We DO NOT use MAC Address! This unique id persists even if you wipe and reload the machine.
241
+
Because the same computer often exists in multiple RMMs (Like how CW Automate typically installs ConnectWise ScreenConnect Automatically), ImmyBot prevents duplicates by identifying the computer by a unique id. We DO NOT use MAC Address! This unique id persists even if you wipe and reload the machine.
242
242
243
243
When a new machine is detected, it first goes to New Computers->Actively Identifying
0 commit comments