Developer command to restart Senso (can take up to 2 minutes to appear online again)

senso?RestartClient

This command will end any Senso processes. The processes will then automatically restart and show the correct No User option.

taskkill /f /im "sensoclient.exe"

Command to set system proxy, activate Office and remove system proxy.

netsh winhttp set proxy wf1.thegrid.org.uk:80

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

cscript "C:\Program Files\Microsoft Office\Office16\ospp.vbs" /act

netsh winhttp reset proxy

Command to set system proxy, activate Windows and remove system proxy.

netsh winhttp set proxy wf1.thegrid.org.uk:80

cscript "C:\Windows\System32\slmgr.vbs" /ipk C4NMT-4QGYD-HX97J-PDBKF-6Q7Y3

cscript "C:\Windows\System32\slmgr.vbs" /ato

netsh winhttp reset proxy

Follow these instructions for first time deployment:

[ On a workstation ]

1. Download the latest Senso v2 client here. If this link does not work, please let Mark Whitman know.

2. Download Orca MSI Editor from the Interm IT Sharepoint here > extract the zip file > install by running the MSI file.

3. Open Orca > select File > Open > select the downloaded Senso Client MSI file > Open.

4. In the Transform Menu, select New Transform.

5. Left pane, under Tables, select Property.

6. Right pane, under Property, find LIC > edit the value from empty to the Senso v2 licence key (please contact Mark Whitman if you do not have this).

7. Right pane, under Property, find SID > edit the value from empty to IIT<SensoID>.

8. In the Transform Menu, select Generate Transform > enter the file name as IIT<SensoID><SchoolName> e.g. IIT987_St_Greggs_Primary_School.mst > Save.

9. Copy both the MSI and MST files to the K9Server under D:\ Software \ Deploy \ Tools \ Senso 2.0

10. Open Group Policy Management > right-click on Group Policy Objects > New > set the name to IIT Senso 2.0 > OK.

11. Right-click IIT Senso 2.0 > Edit > under Computer Configuration \ Policies \ Software Settings, right-click Software installation > New > Package > browse to \\K9Server \ Deploy$ \ Tools \ Senso 2.0 > select Senso_Windows_Client_setup_x64.msi > select Open > select Advanced > OK.

12. Select the Modifications tab > Add > browse to \\K9Server \ Deploy$ \ Tools \ Senso 2.0 > select the MST file > Open > OK.

For K9 schools:

12. 1. 1. Expand the Managed OU > right-click the Computers OU > Link an existing GPO > select IIT Senso 2.0 > OK.

       2. Remove any other linked GPOs and MDT installation tasks from the build task sequence as this will conflict with the GPO.

For CC4 schools:

1. Expand the Site OU > right-click the Establishments OU > Link an existing GPO > select K9 Deploy Senso > OK.

2. Remove any other linked GPOs and RMMC Senso packages that are automatically deployed via Default Assignments.

Follow these instructions to update the Senso deployment:

1. Download the latest Senso v2 client here. If this link does not work, please let Mark Whitman know.

2. Copy the MSI file to the K9Server under D:\ Software \ Deploy \ Tools \ Senso 2.0

3. Open Group Policy Management > expand Group Policy Objects > right-click IIT Senso 2.0 > Edit > under Computer Configuration \ Policies \ Software Settings\ Software installation > in the right pane, right-click Senso.Cloud.Client > All Tasks > Remove > select Allow users to continue to use the software... > OK.

4. Right-click Software installation > New > Package > browse to \\K9Server \ Deploy$ \ Tools \ Senso 2.0 > select Senso_Windows_Client_setup_x64.msi > select Open > select Advanced > OK.

5. Select the Modifications tab > Add > browse to \\K9Server \ Deploy$ \ Tools \ Senso 2.0 > select the MST file > Open > OK.

Follow these instructions for first time deployment:

1. From the iDrive, download a clean copy of Senso.

2. Extract the zip file to a known location on K9Server (e.g. D:\Interm IT)

3. Within the extracted folder, run Configure_Senso_GPO.bat as an Administrator and follow the on-screen instructions.

4. Open Group Policy Management > right-click on Group Policy Objects > New > set the name to K9 Deploy Senso > OK.

5. Right-click K9 Deploy Senso > Import Settings > Next > Next > Browse > select the GPO - K9 Deploy Senso folder > OK > Next > Next > Next > Finish > OK.

For K9 schools:

5. 1. 1. Expand the Managed OU > right-click the Computers OU > Link an existing GPO > select K9 Deploy Senso > OK.

      2. Remove any Senso installation tasks from the build task sequence as this will conflict with the GPO.

For CC4 schools:

1. Expand the Site OU > right-click the Establishments OU > Link an existing GPO > select K9 Deploy Senso > OK.

2. Remove any Senso packages that are automatically deployed via Default Assignments.

Follow these instructions to update the Senso deployment:

1. From the iDrive, download a clean copy of Senso.

2. Extract the zip file to a known location on K9Server (e.g. D:\Interm IT)

3. Within the extracted folder, run Configure_Senso_GPO.bat as an Administrator and follow the on-screen instructions.

4. Open Group Policy Management > expand Group Policy Objects > right-click K9 Deploy Senso > Import Settings > Next > Next > Browse > select the GPO - K9 Deploy Senso folder > OK > Next > Next > Next > Finish > OK.

5. For any K9 systems using MDT, remove any Senso installation tasks from the build task sequence as this will conflict with the GPO.

Notes about the deployment:

• For K9 systems using MDT, remove any Senso installation tasks from the build task sequence as this will conflict with the GPO.

• The install will perform a fresh install of Senso with exception of the device certificate (to avoid duplicates in the console).

• The install will skip over the entire command if it has already been installed.

• The install will allow the client to update via Senso's online updater.

There have been a number of changes that Google and Microsoft have made that impacted the service.

Microsoft have deprecated one of their technologies forcing Senso to change portals to improve the service.  Please be aware that we will be migrating portals this weekend.  The only clients that will be negatively affected are ones not showing as green (updated) - these will need to be reinstalled with the latest Senso 2019.7.14.0 while you are on-site.

In regards to clients appearing offline, this is a Microsoft bug from 2017.  The Senso devs have been working hard to created a fix, which shall be released in the new client within the next week.

Google have updated Chrome in the summer with a feature called Anonymize local IPs exposed by WebRTC.  As WebRTC is the main method for Senso clients to operate efficiently, browsers have been falling back to Senso's fallback TURN service meaning all traffic has to be routed out of the school and back in, putting a massive strain on their servers.

Action to take for Senso:

1. In your Chrome Omnibar type chrome://flags > seach for mdns > disable Anonymize local IPs exposed by WebRTC - this will massively improve performance!

2. Apply the above to any computers where staff remote control computers (i.e. ICT Suite teacher machines).

3. During your upcoming visits, please check that Senso clients are up-to-date - primarily on core devices such as servers, admin computers, head's computers, and teacher workstations.

Please follow the instructions here to apply viewing permission on request.

Please complete the following email template to set up safeguarding. An email will be sent to this account to complete the account setup.

Important: If the email address requested is not the school's DSP, please check with the DSP that this is okay to proceed with.

To: mark.whitman@intermit.co.uk

Subject: Senso safeguarding request for <schoolName>

Hi Mark,

Please configure a safeguarding login for the following:

School Name: 

School Town:

Designated email address: 

Set up priority 5 email alerts (yes / no):

Set up weekly email report (yes / no): 

Thank you!

Please complete the following email template to set up CPOMS integration with Senso.

1. Obtain the Subdomain and API key by logging into CPOMS and navigating to Admin > Overview > Integrations.

2. Complete the following email template:

To: mark.whitman@intermit.co.uk

Subject: CPOMS Senso integration request for <schoolName>

Hi Mark,

Please configure a safeguarding login for the following:

School name: 

Subdomain: .cpoms.net

API key:

Thank you!

Please complete the following email template to set up CPOMS integration with Senso.

1. Obtain the Subdomain and API key by logging into CPOMS and navigating to Admin > Overview > Integrations.

2. Complete the following email template:

To: mark.whitman@intermit.co.uk

Subject: CPOMS Senso integration request for <schoolName>

Hi Mark,

Please configure a safeguarding login for the following:

Tenant Code: 

API key:

Thank you!

Please complete the following procedure to configure Senso on iPads.

To: mark.whitman@intermit.co.uk

Subject: Senso safeguarding request for <schoolName>

Hi Mark,

Please configure a safeguarding login for the following:

School Name: 

Organisation ID: 1098613

Thank you!

Note: The organisation ID can be found in Apple School Manager Enrollement Information. Login > select the My Profile menu (bottom left) > Preferences > Enrollment Information.

To access the Logging module:

1. Navigate to the Senso portal - https://portal.senso.cloud

2. Login with your Senso credentials. If you do not have these, please contact your Interm IT consultant.

3. A Logging module should be visible along the modules bar at the top of the window. Select it to be taken the Logging Overview. You will see an overview of detected words and phrases. You can select a specific word to see where that instance has occurred.

Selecting Violation Logs will show all violations that have occurred within the date period specified. By default, this will be today's date, but can be modified to show violations within the last 7 days, last month, a custom date range, etc.

For each violation, this will include the following fields that may be useful:

• Screenshot - a screenshot will be taken if possible of the application in use at the time of the violation.

• Date - this will show when the violation occurred.

• Device - the device used at the time the violation was recorded.

• User - the user logged into the computer a the time the violation occurred.

• Phrase - the keypresses typed to trigger the violation.

• Info - shows the entire phrase typed to add context to the violation.

Selecting a violation will enlarge the screenshot and allow you to change the status of the violation. For example, this could be to mark the occurrence as a False Positive, if it's Under Investigation, or if it has been Resolved.