Orchestrate Lite minn ScreenBeam

Parti I Ippjanar

Din il-gwida għall-iskjerament tkopri l-mudell tal-iskjerament fejn il-brawżer fil-mira huwa Microsoft Edge jew Google Chrome.
Din it-taqsima tipprovdi sommarju tar-rekwiżiti għall-apparati, il-ġestjoni tal-apparati u n-netwerk.

Bażiku
Follow these guidelines for Orchestrate Lite deployment:

• Ensure that Internet access is available.
• Ensure that no firewall is blocking the Orchestrate WebApp port (on receiver) TCP 8080.
• Microsoft Edge or Google Chrome is installed on the teacher and student PCs.
• ScreenBeam 1000EDU G2 receiver is installed with firmware 11.2.17.17 or later.

Azure Active Directory mhuwiex meħtieġ għall-funzjonalità ewlenija. Madankollu, huwa meħtieġ jekk l-installazzjoni tas-softwer hija ġestita permezz ta' Microsoft Intune.

• An Azure domain and an Azure Global Admin user are created. Users for students and teachers are created.
• Teacher and student PCs and user accounts have joined Microsoft Entra ID (or Azure Active Directory) on these PCs.

Fluss tal-Implimentazzjoni
A typical flow for deploying Orchestrate Lite by ScreenBeam is as follows:

1. Install ScreenBeam receiver, student PCs, and teacher PC, and ensure network access to one another.
   The following are only necessary if the installation is managed through Microsoft Intune.
2. L-utent tal-Azure Global Admin jidħol fil-kerrej tiegħu, https://portal.azure.com/. If necessary, create new groups for students and teachers (your tenant Home > Manage > Users).
3. Teacher and student PCs join Microsoft Entra ID (or Azure Active Directory).
4. Register the Orchestrate Window Assistant app with the Azure Global Admin user.
5. Idħol https://endpoint.microsoft.com with the Azure Global Admin user and create installation profiles għall-installazzjoni tal-app Orchestrate Windows Assistant għall-istudenti u l-għalliema rispettivament.

Topoloġija
Il-PCs tal-għalliem u tal-istudenti jistgħu jiġu konnessi ma' Azure Active Directory (AAD) jew Active Directory (AD) biex jiksbu l-Isem Sħiħ tagħhom biex jintwera fl-app. Madankollu, dan mhux meħtieġ għal funzjonijiet oħra. Qabbad ir-riċevitur ScreenBeam, il-PC tal-għalliem u l-PCs tal-istudenti man-netwerk (jew subnet) fejn huma aċċessibbli għal xulxin.

Rekwiżiti tas-Sistema Rakkomandati
Ir-rekwiżiti tas-sistema rakkomandati għall-installazzjoni u t-tħaddim ta' ScreenBeam Orchestrate Lite huma elenkati hawn taħt:

End User Windows Device 

• OS: Windows 10/11 Pro/Edu/Ent (64-bit) or higher or Chrome OS 81.0.4044.103 or later
• CPU (teacher): 10th Gen Intel Core i5 or AMD equivalent/better
• CPU (student): 10th Gen Intel Core i3 or AMD equivalent/better
• Wi-Fi: Intel WiFi6 AX series or better
• MEMORY: Teacher – 8GB (or more), Student – 4GB (or more)
• HDD: 64GB (or more)

 Riċevitur ScreenBeam
The following ScreenBeam receivers are compatible with Orchestrate Lite:

• ScreenBeam 1000 EDU G2 (Firmware 11.2.17.17 or higher)

Rekwiżiti tan-Netwerk
Jekk in-netwerk tiegħek huwa maqsum f'diversi subnets/VLANs, allura jridu jiġu applikati regoli tal-firewall biex jippermettu li t-traffiku jiċċirkola bejn in-netwerks.
Common multi-VLAN configurations separate the Teacher, Student and Receiver devices.

• 2 VLAN – 1) Teacher + Receiver, 2) Student
• 3 VLAN – 1) Teacher, 2) Student, 3) Receiver

Servizz	Protokoll	Sors	Destinazzjoni	Port
Għall-każijiet kollha
WebRTC – Video/Audio	TCP/UDP	Student	Għalliem	49152-655353478534944319302
WebRTC – Video/Audio (between teacher and student)	TCP/UDP	Għalliem	Student	49152-655353478534944319302
Għal 2 setups tal-VLAN
Orkestra l-API tal-Klijent	TCP	Student	Għalliem	8080
Miracast fuq LAN (Infracast)	TCP/UDP	Student	Għalliem	72502503072362303049152-655352403019134
Għal 3 setups tal-VLAN
Orkestra l-API tal-Klijent	TCP	Teacher/Student	Riċevitur	8080
WebRTC – Video/Audio (to receiver)	TCP/UDP	Teacher / Student	Riċevitur	49152-655353478534944319302
Miracast fuq LAN (Infracast)	TCP/UDP	Teacher / Student	Riċevitur	72502503072362303049152-65535

2403019134

• If using a Windows PC, open local TCP port 49542, used for communication between the Orchestrate Windows Assistant and the Orchestrate Extension running on the PC.

Oħrajn
HDTV/proġettur b'port HDMI disponibbli

Part II Setting up the ScreenBeam

Riċevitur
Orchestrate Lite is not enabled on ScreenBeam 1000EDU G2 receiver by default and must be enabled for use.
Note: When Orchestrate Lite is enabled then only connections through the Orchestrate Lite app will be allowed. Native wireless display connections will be disabled.

Enable Orchestrate Lite on a ScreenBeam 1000EDU G2 receiver with this procedure:

1. Access the ScreenBeam receiver’s Local Management Interface (LMI) and go to the Features tab page. Refer to the receiver’s user manual for details on how to access a ScreenBeam receiver’s LMI.
2. On the Orchestrate section, set OrchestrateLite to Enable.
3. Click on Apply to save your settings.
4. The ScreenBeam receiver will change to Orchestrate Lite mode and the connection instructions on the screen will change.

Parti III L-Implimentazzjoni ta' Orchestrate Lite

Orchestrate Lite jista' jiġi skjerat mill-bogħod permezz tal-MDM.

Deploying Orchestrate Lite via Intune
Microsoft Intune is efficient for deploying Orchestrate Lite across a Windows deployment. The Orchestrate Extension and the Orchestrate Windows Assistant apps can be remotely installed onto the devices managed by Microsoft Entra ID.
Note: This section is only necessary if the installation is managed through Microsoft Intune.

Creating a Tenant for Your Deployment
It is required to create an Azure Active Directory tenant to manage teacher and student devices.

1. Idħol https://portal.azure.com with an Azure Global Admin account.
2. Select Microsoft Entra ID (previously Azure Active Directory) under Azure services and create a dedicated tenant for managing your teacher and student devices.
3. Note down the Tenant ID.
4. Create users for your teachers and students under Manage > Users and group these users under Manage > Groups. Ensure that teachers and students are in different groups.
   Note: You can also use the bulk import feature via Manage > Users > Bulk operation > Bulk create to import your users by batch. Refer to this link for details.
5. Join teacher and student PCs to Azure Active Directory via Settings > Accounts >

Aċċessa x-xogħol jew l-iskola > Qabbad > Ingħaqad dan l-apparat mal-Microsoft Entra ID (qabel Ingħaqad dan l-apparat ma' Azure Active Directory).

 Registering the Orchestrate Windows Assistant App
Follow this procedure to register the Orchestrate Windows Assistant app for your deployment:

1. First find your tenant ID. Find it in the Overview page of your tenant on Microsoft Entra ID. Refer to section 3.1.1 Creating a Tenant for Your Deployment for details.
2. Modify the following URL. Replace the section ”{tenant_id_here}” with your tenant ID. https://cloud.screenbeam.com/orchestrate/api/aad/app/register/{tenant_id}
   Per example, if your tenant ID is 01fdc4d2-4a13-0000-1111-09a5eec7d805, the modified URL se jkun: https://cloud.screenbeam.com/orchestrate/api/aad/app/register/01fdc4d2-4a13-0000-1111-09a5eec7d805
3. Paste l- URL created in Step 2 into your browser, and press Enter.
4. Sign in with your Azure Global Admin account.
5. On the Permissions requested dialog box, click Accept.
6. Go to your Microsoft Entra ID portal > your tenant > Manage > Enterprise applications and verify that the Orchestrate Win Assistant has been registered.

Deploying Orchestrate Windows Assistant to Student and Teacher  PCs
The Orchestrate Windows Assistant app works with the Orchestrate Extension and must be deployed on all end user Windows PCs. Ensure that teacher accounts (or devices) and student accounts (or devices) are assigned to different groups on Microsoft Entra ID. An app installation policy should be created on Intune for deploying Orchestrate Windows Assistant to each, teachers and students, respectively.

Deploy the Orchestrate Windows Assistant app with this procedure:

1. Go to the ScreenBeam support website and download the latest Orchestrate Windows Assistant app. Unzip the file (l-OrchestrateWindowsAssistantInstaller_#.#.#.msi file) to your local drive.
2. Log into Intune on https://endpoint.microsoft.com with an Azure Global Admin account.
3. On Microsoft Intune Admin Center, select Apps and the select By platform > Windows.
4. On the Windows apps page, click Create.
5. On the Select app type panel, select Line-of-business app from the App type drop-down box. Click Select.
6. On the Add App page that appears, click Select app package file fil-paġna tat-tab tal-informazzjoni tal-App.
7. On the App package file panel, ikklikkja l-pakkett tal-App file kaxxa tal-għażla u agħżel l-app Orchestrate Windows Assistant file that you have unzipped (the Orchestrate Windows Assistant Installer_#.#.#_msi file). Ikklikkja OK.
8. The Orchestrate Windows Assistant app will be added to the App information tab page. Now enter configuration options into the Command-line arguments field. Choose based on the browser that you want to install the Orchestrate extension to.
   • LITE_MODE
   • Options: NO (default), YES (it must be set to YES)
   • NO – Orchestrate Lite mode will not be enabled
   • YES – Orchestrate Lite mode will be enabled
   • EXT_BROWSER
   • Mira web browser biex tinstalla l-estensjoni Orchestrate
   • EDGE – Microsoft Edge
   • CHROME – Google Chrome
   • RWOL
   • Options: TEACHER (default), STUDENT
   • TEACHER – The target device will be set to use as a teacher
   • STUDENT –The target device will be set to use as a student
     Per example, the following string would be used to enable Orchestrate Lite mode, set the target devices to be used as Student, install the extension to Microsoft Edge and pin the extension to the toolbar. Note that each option is separated by a space and order does not matter.
     LITE_MODE=YES EXT_BROWSER=EDGE ROLE=STUDENT
9. On the Assignment tab page, select Add groups in the Required section for the targets that Orchestrate Windows Assistant app is to be installed. The app will be force-installed onto the devices in the selected groups.
   • Add groups: When selecting Add groups, the Select groups panel will appear. Select your group(s) and click Select. The devices (users) in the group(s) will be selected.
     Note: Select the students’ groups or the teachers’ groups only. Ikklikkja Li jmiss biex tkompli wara li tkun lesta l-konfigurazzjoni tal-assenjazzjoni tiegħek. Biex tneħħi l-Orchestrate Windows Assistant mit-tagħmir tal-istudenti u tal-għalliema tiegħek, agħżel Żid gruppi, jew Żid l-utenti kollha, jew Żid it-tagħmir kollu fit-taqsima Iddiżinstalla biex iżżid gruppi ta' utenti tal-AAD għat-tagħmir (utenti) li fuqhom trid li l-app Orchestrate Windows Assistant tiġi diżinstallata.
10. Fuq ir-Review + oħloq tab page mill-ġdidview is-settings tiegħek u kklikkja Oħloq biex toħloq l-app tiegħek profile.L-app Orchestrate Windows Assistant magħżula se tittella' fuq Intune.
11. Repeat steps 4 to 10 to create another app installation profile for teachers (or students).
    NOTA:
    • It may take a while for Intune to deploy the Orchestrate Windows Assistant to all your student and teacher’s laptops.
    • Go to Control Panel > Programs > Programs and Features, and check if the Orchestrate Windows Assistant application has been installed on the target devices.
12. The end users may be reminded to restart their browser to complete the Orchestrate
    Extension installation.
    Note: Restart your device if Orchestrate Extension is not installed to your browser after you have restarted the browser.
    • Once the policies and applications are pushed onto the end user devices it is highly recommended to reboot the systems to ensure that Windows loads them properly.
    • Go to edge://extensions on your Edge browser (or chrome://extensions on Chrome) to check if the Orchestrate Extension has been installed.
    • Go to edge://policy on the Edge browser (or chrome://policy on Chrome) to check if the policy has been received. Try the Reload policies feature if your device hasn’t received the policy yet.
13. (Optional) The Orchestrate by ScreenBeam Extension icon may be hidden after the Extension is installed. If so, click the Extensions icon on Edge/Chrome and then click the Pin to toolbar / Pin button next to Orchestrate Extension.

Deploying Orchestrate Extension via Google  Workspace 

• Proper Google Workspace configurations can help an organization manage users and devices efficiently for Google and ChromeOS deployments.
• The Orchestrate Extension can be remotely installed with Google Workspace.
  Note: This section is only necessary if the installation is managed through Google Workspace.

Managing API Client Access
Kull kont ta' Google Workspace għandu d-dejta tiegħu stess salvata. Estensjoni trid titlob permess biex taċċessa d-dejta. Hemm żewġ modi kif tagħti permessi:

• User grants permissions to Extensions.
• Admin grants permissions globally to every user under a particular domain.
• Granting permissions globally is more efficient for an organization to manage at scale.

To grant permission globally, follow this procedure: 

1. Log into Google Workspace (admin.google.com) with a G Workspace account.
2. Go to Admin Console > Security > Access and data control > API Controls > Domain wide delegation > Manage Domain Wide Delegation. Or click this link.
3. Click Add New and the Add a new client ID box will appear.
4. Enter the client ID shown below in the Client ID field. 325501850954-sjte9h825ebj1m0jcm092tjrbpkhg14n.apps.googleusercontent.com
5. Enter scopes required by the extension in the OAuth scopes field. The scopes are provided by the application/software developer.
   • email: jippermetti lill-Estensjoni taċċessa l-email tal-utent li daħħal is-sistema.
   • profile: jippermetti lill-Estensjoni taċċessa l-profile of the user that has signed in, such as names, avatar, etc…
   • openid: jippermetti lill-Estensjoni taċċessa l-ID uniku tal-utent li daħħal is-sistema.
   • https://www.googleapis.com/auth/classroom.courses.readonly: Extension to access the list of courses the user is assigned or joined to.
   • https://www.googleapis.com/auth/classroom.rosters.readonly: Extension to access the teacher’s class rosters in Google Classroom.
     L-ambitu ta' Orchestrate Extension huwa: email, profile, openid, https://www.googleapis.com/auth/classroom.courses.readonly, https://www.googleapis.com/auth/classroom.rosters.readonly
     Note: Separate scopes with comma.
6. Click Authorize. The API client is authorized to access the users’ data.

Ġestjoni ta' Utenti
To add a new user, follow this procedure:

1. Log into Google Workspace (admin.google.com) with a G Workspace account.
2. Go to Admin Console > Directory > Users. Or click this link.
3. Click Add new user and the Add new user box appears. Fill in the required fields and click ADD NEW USER to add a new user.

To manage organizational units, follow this procedure:
Create an organizational unit for teachers and one for students.

1. Log into Google Workspace (admin.google.com) with a G Workspace account.
2. Go to Admin Console > Directory > Organizational units. Or click this link.
3. Click Create organizational unit to create a new unit or select a unit name and add a subsidiary unit (the + sign), move this unit (the right arrow), edit, or delete the unit.

To change a user to another unit, follow this procedure:

1. Log into Google Workspace (admin.google.com) with a G Workspace account.
2. Go to Admin Console > Directory > Users. Or click this link.
3. Select one or more users, then select More options > Change organizational unit.

Deploying Orchestrate Extension
To deploy Orchestrate Extension, follow this procedure per Organization Unit:

1. Log into Google Workspace (admin.google.com).
2. Go to Admin Console > Devices > Chrome > Apps & extensions > Users & browsers. Or click this link.
3. Select an organizational unit on the left pane.
4. Click the yellow + sign at the bottom right corner and then select the Add Chrome app or Extension by ID option.
5. The Add Chrome Extension by ID box appears. Enter the ID of the Orchestrate Extension in the Extension ID box and select From Custom URL. Ikklikkja Save.
   • The ID of the Orchestrate Extension is bdgflbkkgedengcnmmbijghkpdpdlkfb
     Custom URL – https://cdn.screenbeam.com/assets/orchestrate/manifestv3/upgrade_ext_v3.1.2.xml
6. The extension is added to Google Admin Console.
7. Select the Orchestrate extension and then the Extension setup panel appears on the right.
8. Enter JSON configuration in the Policy for extensions box. Or click the up-arrow icon next to the Policy for extension box and then upload a json file (.txt/.text). Click SAVE.
   Full text of the JSON configuration is shown below Example of the JSON:
   • {
   • “lite_mode”: {
   • “Value”: true
   • },
   • “role”: {
   • “Value”: “STUDENT”
   • }
   • }
9. Set the variables in the JSON based on the Organization Unit being configured
   • LITE_MODE
   • Options: FALSE (default), TRUE (it must be set to TRUE)
   • FALSE – Orchestrate Lite mode will not be enabled
   • TRUE – Orchestrate Lite mode will be enabled
   • RWOL
   • Options: TEACHER (default), STUDENT TEACHER – The target device will be set to use as a teacher STUDENT –The target device will be set to use as a student
10. Select the Orchestrate Extension, and then select Force install or Force install + pin on the Installation policy column. Do the same for Orchestrate Chrome App. Click  SAVE.
    Users can’t remove the extensions or apps that are force installed.

To uninstall an extension or app installed by Google Workspace, follow this procedure:

1. Log into Google Workspace (admin.google.com) with a G Workspace account.
2. Go to Admin Console > Devices > Chrome > Apps & extensions > Users & browsers. Or click this link.
3. Select an organizational unit on the left pane. This organizational unit should include the users from whose devices the extension or app are to be uninstalled.
4. Select the extension that you want to uninstall, and then click the trash bin icon. Click Delete on the confirmation box.
5. The Orchestrate Extension will be removed from the managed devices shortly. Go to chrome://extensions on Chrome and check whether the extension is uninstalled.

Drittijiet tal-Awtur ta' Dokumenti u Softwer
Dan id-Dokument ta' ScreenBeam u s-softwer kollu offrut permezz ta' jew użat fuq dan id-Dokument ta' ScreenBeam huma proprjetà tagħna jew proprjetà tal-fornituri, sponsors, liċenzjaturi jew affiljati tagħna (kollettivament, "Imsieħba fin-Negozju"), u huma protetti mil-liġi tad-drittijiet tal-awtur tal-Istati Uniti u internazzjonali, il-liġi tat-trademarks, u l-liġi tas-sigrieti kummerċjali, kif ukoll liġijiet, regoli u regolamenti oħra. Aħna sidien ta' drittijiet tal-awtur f'dan id-Dokument ta' ScreenBeam u fl-għażla, il-koordinazzjoni u l-arranġament tal-kontenut disponibbli permezz ta' dan id-Dokument ta' ScreenBeam. Ħlief kif espressament previst hawnhekk, la aħna u lanqas l-Imsieħba fin-Negozju tagħna ma nagħtuk xi drittijiet taħt xi privattivi, drittijiet tal-awtur, trademarks jew informazzjoni dwar sigrieti kummerċjali. Għaldaqstant, l-użu mhux awtorizzat ta' dan id-Dokument ta' ScreenBeam jew kwalunkwe kontenut disponibbli fuq dan id-Dokument ta' ScreenBeam jista' jikser il-liġijiet tal-privattivi, il-liġijiet tad-drittijiet tal-awtur, il-liġijiet tat-trademarks, il-liġijiet tas-sigrieti kummerċjali, u l-liġijiet relatati mad-drittijiet tal-privatezza u l-pubbliċità jew liġijiet jew regolamenti oħra. Copyright © 2025 ScreenBeam Inc. Id-Drittijiet kollha Riżervati. ScreenBeam, u l-logo ta' ScreenBeam u l-intestaturi tal-paġni kollha, il-grafika tad-dwana u l-ikoni tal-buttuni huma l-marki tas-servizz, it-trademarks, u/jew id-dehra kummerċjali ta' ScreenBeam ("Trademarks"). Il-marki tas-servizzi, it-trademarks, l-ismijiet tal-prodotti u l-ismijiet tal-kumpaniji jew il-logos l-oħra kollha murija f'dan id-Dokument ta' ScreenBeam huma l-proprjetà tas-sidien rispettivi tagħhom. Ma tistax tuża, tikkopja, tirriproduċi, tippubblika mill-ġdid, ittella', tibgħat, tittrażmetti, tiddistribwixxi jew timmodifika xi waħda mit-Trademarks bl-ebda mod, inkluż fir-reklamar jew fil-pubbliċità relatati mad-distribuzzjoni ta' materjali f'dan id-Dokument ta' ScreenBeam, mingħajr il-kunsens bil-miktub minn qabel tagħna.

FAQ

Is Azure Active Directory required for using Orchestrate Lite?

Azure Active Directory is not required for core functionality of Orchestrate Lite. However, it is necessary if the software installation is managed through Microsoft Intune.

What are the recommended system requirements for Orchestrate Lite?

The recommended system requirements include End User Windows Device, ScreenBeam Receiver, Network Requirements, and other specifications as outlined in the deployment guide.

Dokumenti / Riżorsi

ScreenBeam Orchestrate Lite minn ScreenBeam [pdfGwida għall-Utent Orkestra Lite minn ScreenBeam, Lite minn ScreenBeam, minn ScreenBeam

Referenzi

• Manwal għall-Utent