Appendix

1.1      Interpretation of Product Version Numbers

RCC product versions cover the hardwareversions, software versions, and system versions. The version namingconventions are as follows:

1.       Hardware versions:

Naming convention: Product name_Vx.yz. Forexample, the hardware versions of Thin Client include Rain100_1.0 and Rain200_1.1.

Rule description:

x: an integer ranging from 1 to 99. Theinitial value is 1. When major changes such as hardware change and upgrade areinvolved, the value of x is increased by 1. The change of this version numberalways comes with software version upgrade.

y: an integer ranging from 0 to 9. Theinitial value is 0. When major auxiliary component changes such as the changeof the power supply or PCB design are involved, the value of y is increased by1. Generally, the change of this version number does not trigger the softwareversion upgrade. (Additional instructions will be provided for specialcircumstances. For example, if thehardware specifications of the main body of the Rain100_1.0 or Rain100_1.1 arechanged, the corresponding software version is also changed. If the hardwarespecifications of the main body of the Rain100_1.0 or Rain100_1.1 keepunchanged, the corresponding software version remains unchanged.)

z: an integer ranging from 0 to 9. Theinitial value is 0. If non-functional hardware is changed, for example, thehardware PCB process is improved, the value of y is increased by 1. Generally,the change of this version number does not trigger the software versionupgrade.

2.       Software versions:

Naming conventions: Productname_Vx.y_Rx[PyTz].n [_Language ID_Customized product ID]. For example, thesoftware versions of the RCD Server include RCC_1.0.9_R0.10 andRCC_1.0.9_R1.24.

Rule description:

1)       x.y: software version number.

x indicates generation x and is an integerranging from 1 to 99. When functions are significantly changed or thearchitecture is changed, the value of x is increased by 1.

y indicates the function version. Whenfunctions are added or changed, the value of y is increased by 1.

For example, in version 1.0.9, x is 1 and yis 0.9. The later versions are 1.1, 1.2, and increase in sequence.

2)       Rx[PyTz].n: version feature code.

Rx indicates the trial or formal version, andthe options include R0 and R1.

PyTz indicates the patch or temporaryversion. P indicates a patch version, and T indicates a temporary version. yand z are integers ranging from 1 to 99. When the version is changed, the valueof y or z is increased by 1.

n indicates the internal compilation ID ofthe version. It starts from 1 and increase by 1.

Note: For Thin Clients,the name of a complete installation package contains the hardware and softwareversion information. Taking RG-Rain100V1.10_V1.1_R1.14_L.isoas an example, 1.1 indicates the hardware version, and V1.1_R1.14 indicates the software version.

3.       System versions:

Naming conventions: Product OSname_Software version_Feature code. For example, the software versions of theRCD Server include RG-Rain100V1.10_V1.1_R1.14_L and RCDOS_V1.0.9_R1.24.

Rule description:

1)       The product OS name is mainly determined basedon the system trademarks (Linux, Windows XP, and Android systems are allsupported since RCC1.1).

2)       The software version naming rules are the sameas the general software version naming rules.

3)       The feature code is mainly used to distinguishfeatures of the OS and is generally applicable to Thin Clients. Taking the ThinClient RAIN OS as an example, L indicates Linux, A indicates Android, and Xindicates Windows XP.

Note:For Thin Clients such as RG-Rain100V1.10_V1.1_R1.14_X, 1.10 indicates thehardware version, V1.1_R1.14 indicates the software version, and X/L/A indicates theplatform or system type. For RCDServers such as RG-RCDOS_Server_V1.1_R1.14, feature recognition is notrequired.

1.2      ClassManager Software License

The RCC supports the ClassManager Rainbowsoftware (CM2 for short) since RCC_1.1_R1. The CM2 license authorization modeis changed from the dongle mode in ClassManager1.x to file license mode. You need to apply for the license file from RuijieProduct Authorization System and import the license file to the RCD Server.

Ruijie Product Authorization (RG-PA) system

The RG-PA provides a variety of functionssuch as file license authorization, production, application, hardware change,expansion, and service query.

PA login address: https://www.ruijienetworks.com/support/licensing

Public account used for applying for theClassManager license is as follows:

User name:classmanager/classmanager1/classmanager2

Password: ruijie

Terms

Device identification number (SN)

The SN is a MD5 value calculated based onhardware information of Ruijie products, which refers to the RCD Server here.

You can obtain the SN in the following ways:

Method 1: Log in to the web management UI ofthe RCD Server. Choose System > License. Click Display SN.(Recommended)

You can also directly export the hardware SN(to avoid incorrect input during license application).

Method 2: Check the SN on upper cover of theRCD Server.

Product authorization code

TheClassManager Rainbow is delivered with a certificate of authorization thatprovides a unique product authorization code.

The following figure shows an example of thecertificate of authorization. You can obtain the authorization code from AuthorizationCode Info.

Note:For details about common authorization questions, see "FAQ: Usage – CommonQuestions About the ClassManager Rainbow license."

1.2.1     Generating the License File Using anAuthorization Code

Application scenario:

You can apply for a license file by using theauthorization code on the certificate of authorization after you purchase theClassManager Rainbow.

Prerequisites:

1.      You have upgraded the RCD Server to RCC_3.1_R1.11 or a laterversion.

2.      The ClassMananger 3.0 has been installed on the teacher PC.

3.      The ClassMananger Rainbow certificate of authorization has beenobtained.

PA login address: http://pa.ruijie.com.cn

Public account used for applying for theClassManager license is as follows:

User name:classmanager/classmanager1/classmanager2

Password: ruijie

The operation steps are as follows:

1.       Obtain the device SN.

2.       Obtain the authorization code from thecertificate of authorization.

3.       Log in to the RG-PA system by using the publicaccount.

4.      Click Apply. Enter the customer name, SN code, authorizationcode, and other customer information.

Note: RCC2.0 and earlier versions do notsupport hardware information export. You can manually input the hardware SN.

5.      After the license is generated, download the .lic file.

Note: If you forget to download the licensefile or lost the license file, you can download it from the home page of theRG-PA system.

6.      Log in to the RCD Server, and click Import License to importthe .lic file.

Ensure that the license file is successfullyimported.

1.2.2     Granting Temporary Authorization

Application scenario:

Temporary authorization is applicable tocustomers who do not purchase the ClassManager (there is no formalauthorization code). Temporary authorization is commonly used for pre-salestesting or demo projects.

Note: This operationrequires the after-sales personnel to submit an application and obtain theapproval from product managers.

1.2.3      Unbinding the Authorization

Application scenario:

In certain situations (for example, replacinga faulty RCD Server), you need to unbind the authorization code from the faultyRCD Server and bind it with another RCD Server.

Note:This operation requires the after-sales personnel to submit an application andobtain the approval from product managers.

1.2.4     Granting Authorization in Cluster or StackScenario

Authorization for RCD Servers in stack orcluster mode:

In stack mode, you can bind each RCD Serverwith one authorization code and then import the authorizationcodes to the master RCD Server.

In cluster mode, you can bind the master RCDServer with each authorization code and then import the authorization codes tothe master RCD Server.

Note:For details about common authorization questions, see "FAQ: Usage – CommonQuestions About the ClassManager Rainbow license.

1.3      RCD Server Commissioning

The following figure shows the startup screenof the RCD Server of RCC_1.1 and later versions (the command mode is availableonly under the SSH connection).

The upper part displays the server version information, and thelower part displays the technical support forum and service hotline. The bottomprompt bar displays the functional shortcut keys. F2is used to display the system configuration and logs. Ctrl+F isused to display the factory test program. F12 is used to shut down orrestart the system. For details about the login page and function description,see relevant manuals.

Note: It is highly riskyto log in to the RCD Server from the CLI. Customers are not recommended to login from the CLI independently, but under the guidance of customer serviceengineers or service hotline (4008).

In special scenarios,for example, when the IP address of the RCD Server is forgotten, you can viewthe IP address of the RCD Server in CLI mode.

You can log in to the RCD 6000 in Telnetmode. The default user name and password are admin.

         The default IP address is192.168.1.100/101. If you forget the IP address, you can access the RCD Servervia the serial port or display/mouse and keyboard run ifconfig-list tocheck the IP address.

Log in to RCD Server by connecting to theserial port on the rear panel and setting the baud rate to 115200. Then, checkthe corresponding command. (The default user name and passwords are admin.For details about the commands, see relevant documents.)

Youcan log in to the RCD Server by connecting to the VGA display interface on therear panel and connecting the keyboard andmouse (used for entering commands). Then, check the corresponding command. Thedefault user name and password are admin.

Note: Due to limitedwindows of the display, certain information cannot be completely displayed. youcan scroll up or down by pressing Shift+Page up or Shift+Page down to view thecomplete information.

1.4       Shortcut Keys for Rain Thin Client Commissioning

Entering the Windows back end: Shift+S+F8

Entering the Linux back end: Ctrl+Alt+T

Entering the Android back end: Alt+Shift+F7

Note: It is greatly riskyto log in to the back end and perform operations on the Thin Client. Improperoperations may damage the system and result in the Thin Client running failure.Exercise caution when you perform this operation.

Running the convergent computing program: Shift+R+F8

Switching between the server UI and the CLI:

Switching to the login page: Ctrl+Shift+Q

Switching to the TUI: Ctrl+Alt+F1

Switching between the window and the fullscreen of Admin-Tool: Shift+S+F11

Skipping the ThinClient selection during iPXE/PXE upgrade: Shift+F

1.5      PXE Upgrade Mode

The PXE an distribute created images to allThin Clients. Different from the iPXE, the PXE function requires hardwaresupport.

Note: Currently, the PXEfunction is configured through BIOS for all Rain Thin Clients, including theRain100 V1.0–1.3 and Rain200 V1.0. For Rain200 V1.1, after the Thin Client isstarted, you can directly press F11 to enable the PXE function. After the ThinClient is restarted, the PXE function is automatically disabled and no extraconfiguration is required.

Image files of the Thin Client need to be uploadedusing the Web-based upload system.

The upgrade operation steps are as follows:

1.      Ensure that DHCP is configured and the IP segment has sufficient IPaddresses. If the system remains at the DHCP page during startup, you can clearthe lease and expand the DHCP address segment. Then, perform the operationagain.

2.      Click Upgrade Wizard and press Shift+F to skipthe Thin Client selection. Select an image to be distributed, and click Next.Wait Thin Clients to connect to the RCD Server.

3.      Enable the PXE function and set it to the Onboard mode.

Motherboard setting mode ofRain100 V1.0:

Motherboard BIOS settingmode of Rain100 V1.1 and later versions:

Motherboard BIOS settingmode of Rain200 V1.0:

4.      Press F10 or F4. Select Yes to save thesettings and exit. Select Launch PXE OpROM on the Boot page andselect Enable to restart the Thin Client. The waiting page in a bluebackground is displayed.

After the Thin Client is restarted, itautomatically enters a page as shown in the following figure, waiting for thedistribution of images.

5.      After IP addresses of all Thin Clients are displayed, indicatingthat all Thin Clients are waiting for the image distribution, start thedistribution.

6.     The Thin Clients start copying theimages. After the images are copied, the system automatically disables the related services.

1.6       Fast Upgrade Mode

The premise for fast upgrade mode is thatThin Clients and RCD Servers are later than V2.0 r1p 2.25, and the targetversions must be later than V2.0 r1p 2.25.

The fast upgrade mode does not rely on theDHCP function of the RCD Server. Thin Clients are allowed to use staticaddresses. The fast upgrade can be implemented as long as the Thin Client andthe RCD Server can successfully interwork with each other.

1.      Upload the Thin Client system version (only the ISO file suffixedwith _X or _L supports the Rain100 and Rain200) through the Web system.

2.      Click Upgrade Wizard.

Select the Thin Client to be upgraded.

Select a target Thin Client version and clickNext.

Click Next.

Click Next to upgrade the Thin Client.

Click Prepare and OK. The ThinClient automatically implements the upgrade flow. Wait until the system issuccessfully upgraded.

1.7      iPXE Upgrade Mode

1.       Configure the DHCP address pool.

Ensure that the DHCP address pool is largeenough. Clear the lease. It is recommended that new address segments be usedfor upgrade.

Ensure that no other DHCP service has beenconfigured in the LAN and the IP address of the RCD Server is not contained inthe DHCP address pool.

Ensure that two network ports of the RCD Servers function properly.Ensure that the to-be-upgraded Thin Client can connect to the RCD Serversuccessfully. The preferred startup item of the Thin Client cannot be the PXEfunction.

2.       Choose Upgrade > Thin Client Upgrade. Upload thestandard Thin Client image to the RCD Server. For the Thin Client ISO file downloaded from thenet disk, check the MD5 value before uploading to ensure the image correctness.

3.       Click Config Wizard and add a Thin Clientto Selected Thin Client.

4.       Click Next to configure the Thin Clientsystem. Select an appropriate Thin Client and click Next to confirm theconfiguration.

5.       In the Upgrade Mode Config dialog box, select Complete,Unicast or Complete, Multicast.

6.       Click Next to start the upgrade.

7.       Wait till the Thin Client is displayed on theupgrade page. If unicast mode is selected, the Thin Client automaticallyperforms the upgrade operation. If multicast mode is selected, thesystem displays a button for starting the upgrade. Wait until all Thin Clientsare added to the Thin Client upgrade list and then click the start button.

1.8      OTA Upgrade Mode

1.       Configure the DHCP address pool.

Ensure that the DHCP address pool is largeenough. Clear the lease. It is recommended that new address segments be usedfor upgrade.

Ensure that no other DHCP service has beenconfigured in the LAN and the IP address of the RCD Server is not contained inthe DHCP address pool.

Ensure that two network ports of the RCDServers function properly. Ensure that the to-be-upgraded Thin Client canconnect to the RCD Server.

2.       Upload the Thin Client system upgrade package.

Choose Upgrade > Thin ClientUpgrade from the navigation tree, select Rain100S/200S/200C Series,and click Upload Firmware to upload a proper Thin Client system upgradepackage (suffixed with _A.zip) to the RCD Server.

Click the upgrade package to be uploaded andupload it to the RCD Server.

After the upload is complete, click Refresh.If information similar to the figure below, the upload is successful.

3.       Set the automatic or manual upgrade mode.

1)      By default, the RCD Server uses automatic upgrade mode, as shown inthe figure below.

The systemautomatically upgrades the Thin Client after the Thin Client is powered on andconnected to the RCD Server.

Switch the upgrade mode to the manual mode.

Wait for all Thin Clients to be upgraded toconnect to the RCD Server, and then click Upgrade.

If a Thin Client is not connected to the RCDServer, click Refresh for the Thin Client to connect to the RCD Server.

      Deployment

2.1      Installation and Configuration

2.1.1     Installing the RCD Server

This topology is applicable to the newdeployment scenario of the RG-RCC solution and includes the RG-RCD Server,RG-ClassManager, and RG-Rain Thin Client.

1.      Deploy the RCD Server.

Key configuration points:set IP addresses, create Cloud Desktop, and configure the network mode.

2.      Deploy the Rain Thin Client.

Key configuration points:set an IP address for the Thin Client and distribute images in PXE mode.

3.      Deploy the teaching PC.

Key configuration points:install the RG-ClassManager and complete deployment in one-click mode.

4.      Manage courses.

Key configuration point:create images.

5.      Verify functions.

Keyverification points: start a class, end a class, broadcast the screen, andbroadcast a video.

2.1.2     Installing the ClassManager_Teacher PC

Minimum hardware configuration:

1.       ClassManager_Teacher PC:

-      CPU: dual-core processor at 2.0 GHz or higher

-      Memory: 2 GB or higher

-      Hard disk: 128 GB or higher

-      Accessories: display, mouse, and keyboard

2.       Thin Client

-      Accessories: Thin Clients supporting RuijieCloud Class, mouse, display, and keyboard

3.       Workspace server

The workspace is used for accountmanagement, class management and homework management. The workspace server canbe deployed on an RCD Server (recommended) or an independent server. After RCDV2.1 is installed, the workspace will be automatically installed.

Minimum configuration of the independentserver (for only one classroom)

-      CPU: dual-core processor at 2.0 GHz or higher

-      Memory: 2 GB or higher

-      NIC: 100 Mbit/s or higher

-      Hard disk: 256 GB or higher

Software configuration:

OS of the ClassManager_Teacher andClassManager_Student:

   Note: The ClassManager_Teacher and ClassManager_Student providefull functions and support 32-bit and 64-bit OSs (64-bit images are supportedsince V2.1).

Keyconfiguration points:

1.      After installingthe ClassManager_Teacher on the teacher PC, authorize the software and installthe workspace server as required.

2.      If the voice broadcast function available in V3.0 is used, ensurethat the OS is Windows 7, Windows 10 Enterprise Edition, Windows 8, Vista, or ahigher version. Other OSs are not supported.

1.      By default, theClassManager_Teacher is integrated into the login page of the RCD Server. Youcan directly download and install the software.

2.      Click Licenseand read the license agreement of the software.

3.       Select I have read and accepted the licenseagreement and click Install.

Set IP addresses for the RCD Server andworkspace server, to ensure that the teacher PC can successfully connect to theRCD Server and workspace server. In addition, you can adopt the defaultinstallation path or click Change to select the required installationdirectory.

Note: if the workspace is deployed locally,no need to configure the workspace server in this step.

Note:

1)     If the deployment mode is Cloud Desktop Campus Networkand Thin Client Campus Network, the RCD Server IP is the LAN1 ip address, ifthe deployment mode is Cloud Desktop Campus Network andThin Client Private Network or Cloud Desktop Private Network and Thin ClientPrivate Network, the RCD Server IP address is the WAN ip address.

2)     The ClassManager and workspace can be usedindependently. Generally, the workspace server uses the RCD Server. In V2.1 andlater versions, after the ClassManager is installed, the workspace isautomatically installed. If the workspace is installed on an independentserver, you need to enter a correct IP address in System > Workspace> Parameter on the RCD Serverweb UI.

3)      In cluster mode, both the master and slave RCD Servers can providefunctions of the workspace server, depending on the RCD Server where theworkspace server is installed. The workspace server uses the IP address of theRCD Server where the workspace server is installed.

4.       After RCD Server IP is correctly set anda correct installation path is selected, click Next. The system startsto install the software. After the software is installed, the systemautomatically jumps to the finish screen.

5.       Finish.

6.      After the software is installed, some functions are available onlyafter the PC is restarted. As shown in the following figure, click Yes.You can normally use the ClassManager_Teacher after the PC is restarted.

Note: If the ClassManager_Teacher fails to scan Thin Clients after upgradebut can start or end a class, you can set the firewall to permit theClassManager_Teacher. Then, all functions become available.

Apply for an authorization file by referringto the Appendix "ClassManangerSoftware Authorization".

Log in to the RCD Server. Query and export the hardware SN, and makea license file in the back-end PA system (see 6.2.1      Generating the LicenseFile Using an Authorization Code below). Then, on the management page, click Importlicense to import the license file.

Ensure that the license file is successfullyimported.

Workspace is a component of the ClassManangerRainbow. It can be installed on an independent server or on an RCD Server. Ifthe workspace serves a large number of students (exceeding 200), it isrecommended that the workspace be installed on an independent server.

To install the workspace on the RCD Server, doas follows:

1.  Log in to the RCD Serveras an administrator. Note: In RCD V3.0 or later versions, the workspace isautomatically installed (the latest installation package is embedded into thenew version).

2.        Refresh the page and click Install.Note: To use the upload function, install the Admin-Tool first.

3.       After uploading the new upgrade package andclicking Refresh, click Install to install the workspace.

Note: please make sure the teacher PC canping RCD server LAN1 ip address before start the admin tool.

2.1.3     Installing the Thin Client

Unpack the chassis and connect the powercable, keyboard, mouse, display, and network cable. Ensure that all devices areconnected to a 1000M switch.

This section uses the Rain100 as an exampleto describe how to rack the RG-Rain Thin Client. The installation methods ofother Thin Clients are basically the same as the installation of the Rain100.For details, download the user manuals of related devices at Ruijie officialwebsite.

1.  Install the device base.

2.  Connect the power cable.

3.  Connect the display, keyboard, andmouse.

4.  Connect the network cable.

5.  Press the power button to start thedevice.

You can configure Rain Thin Clients in twomodes: configure them one by one or configure them in one-click mode (this modeis supported in V1.0.9 and later versions. For details, see "Typical Deployment Schemes – One-clickDeployment").

The following describes how to configure theRain Thin Client one by one:

1.  Start the Rain ThinClient. The RCC logo page is displayed.

2.  The Rain Thin Clientfails to connect to the RCD Server at your first login because no networkinformation is configured.

3.  Click Configure inthe upper right corner to access the configuration page.

Set the parameters as follows:

l  The default password for accessing the configuration page isruijie.com.

l  Generally, you do not need to modify the PC name. If you change thePC name, you need to restart the Thin Client.

l  RCD Server IP is the master IP addressof the RCD Server.

l  Click Obtain an IP address automatically or configure astatic IP address as the IP address of the Thin Client.

l  Note: If the switch is a NMS-type switch and the DHCP networksegment has been configured for the RCD Server, it is recommended to click Obtainan IP address automatically. For a non-NMS-type switch, it is recommendedto set a static IP address for the Thin Client. Otherwise, IP addressesallocated to Thin Clients in multiple classrooms may be disordered.

4.  After the configurationis complete, connect the Thin Client to the RCD Server. If a course isavailable, a page as shown in the following figure is displayed:

2.1.4      Installing Images

By default, there is no available image inthe RCD Server. Generally, you need to create images by using the ISOinstallation CD-ROM of the OS and the SN.

You can also directly access the image page.

Before installing images, ensure that thefollowing operations are completed:

1.       Install the Admin-Tool (download the softwarefrom the image page at your initial use, install the software, exit thebrowser, and log in to the system again).

2.       Obtain the OS ISO CD-ROM (Windows,CentOS/Ubuntu) for image creation or obtain Ruijie demo images (The demo imagesare in the base format and must be deleted within 24 hours after download).

3.       Enter share directory D disk, obtain theClassManager_Student (install it on the Cloud Desktop image).

4.       Obtain various types of professional software tobe installed in images (such as Office and Photoshop).

Note: Currently, Supported image systems include Windows XP,Windows 7, Windows 8, Windows 10, Windows 2003/2008/2012/Vista (Windows 8 is not recommended becauseit does not support the redirection function).

The RCD server and supports32-bit and 64-bit OSs (the RCD supports 64-bit images since V2.1).

Key installation steps:

1.   Uploadthe OS ISO image file (such as win7EnterpriseX64cn.iso) to the image directoryon the RCD Server.

2.       Create an image and setthe parameters.

3.       Completely install the OS.

4.       Install the RCC-Guest Toolto ensure that the Cloud Desktop driver is correctly identified.

5.       Install theClassManager_Student and various types of professional software.

6.       Power off the device. Then,the image is created completely

Note: Because the hard disk controller of the CloudDesktop is upgraded in V3.0, all images need to be edited using the Admin-Toolwhen the RCD Server is upgraded from an earlier version to V3.0. The Guest-Toolis automatically upgraded during image editing. You can normally use the imagesonly after the new hard disk driver is installed. You must restart the systemto access the new images and then install the Guest-Tool to validate thefunctions.

To create an image, do as follows:

Step 1: Download theAdmin-Tool. Choose Image on the navigation tree, and select ImageFile from the Upload drop-down list box.

Upload the OS ISO file or the demo image basefile to the RCD Server.

Step 2: Create an image andset image parameters.

         Image Name: The image name contains more than three characters. It cannotcontain special characters except the underline (_).

         ISO: Select the image fileuploaded by the Admin_Tool. Ensure that the capacity of the image file isconsistent with that of the uploaded image file. Otherwise, anomalies mayoccur.

         OS: The displayed icon varieswith the OS type.

Enable: Whenyou select this option, disabled images is not displayed on Thin Clients. Inopen mode, students can select the OS for login for testing.

System Config:

1)  When you set SystemConfig to Standard (recommended, supporting 60 Cloud Desktops), the systemdisplays different default configurations when you move the cursor here.

In standard mode, the number of CloudDesktops is balanced with the system performance. This mode is applicable toInternet surfing, office, and learning.

The default configuration is as follows: CPUcount: 1; memory: 1024 MB; hard disk: 20 GB

2)  High (supporting 30 CloudDesktops)

Theprocessing performance is doubled. This mode is applicable to Cloud Desktoprunning, graphics rendering, and code compilation.

The default configuration is as follows: CPUcount: 4; memory: 2048 MB; hard disk: 20 GB

3)  Custom

TheCPU count, memory capacity, and hard disk capacity can be customized. Themaximum configuration is as follows: CPU count: 8;memory: 4 GB; hard disk: 40 GB

Note: Select proper hardware configuration for the Cloud Desktop based onthe number of Thin Clients. Improper hardware configuration of the CloudDesktop may cause performance bottleneck of the Cloud Desktop and systeminstability. Generally, the defaultstandard configuration and high-performance configuration are recommended.

Step 3: Click OK.

Step 4: Install theRCC-Guest.

After the installation is complete, restartthe system. The virtual shared disk (drive D) is displayed.

Step 5: Check the networkconfiguration and set the DHCP mode.

Step 6: In cmd, runipconfig /release to release the IP address.

Step 7: Normally shut downthe PC and save the modified image.

         Generally,after you create an image and install the virtual drive, you can installprofessional software.

Step 1: Access the imagedirectory of the RCD Server, and select Shared File from the Uploaddrop-down list box.

         Selectthe software to be installed and upload it to the RCD Server (Note: Since V2.1,the ClassManager_Student is automaticallyuploaded and you can directly edit installed images).

Step 2: Select the image tobe edited and click the edit icon.

Step 3: Edit and enable theimage template.

Step 4: Start the image editmode and install or upload software. All software uploaded to the shareddirectory is in Drive D of the virtual system.

Step 5: After all software isinstalled, check the network configuration, and set the DHCP mode.

Step 6: In cmd, runipconfig /release to release the IP address.

Step 7: Normally shut downthe computer and save the modified image.

2.1.5      Installing Software in Images

Generally, after you create an image andinstall the virtual drive, you can install professional software.

Note: Software cannot beinstalled in the shared Drive D because the system restores Drive D aftershutdown or restart. Therefore, you are suggested to install software in anon-system disk. If you need to install software in Drive D, delete the driveletter of the shared Drive D and use another drive letter, add an image harddisk named Drive D, and then install software.

Step 1: Access the imagedirectory of the RCD Server, and select Shared File from the Uploaddrop-down list box.

Upload the software to be installed to theRCD Server.

2.2      Version Upgrade

2.2.1     Upgrading the RCD Server

The RCD Server can be upgraded in two modes:Web mode and USB flash drive mode. Both upgrade modes use the same upgradefiles. However, the upgrade using a patch package, such as the xxx.tar,supports only the Web upgrade mode.

The upgrade modes are described as follows:

1.     In Web upgrade mode,the software version can be directly upgraded while historical data isretained.

2.      InUSB flash drive upgrade mode, the RCD Server is actually restored to factorysettings. Once the system is restored to the factorysettings, all data on the RCD Server is lost (if you select the factory upgrademode, images will be formatted; if you select the online upgrade mode, theimage data will be retained).

Theoperation difficulties in both modes are similar. The upgrade process in Webupgrade mode is simple. The USB flash drive upgrade mode supports one-clickupgrade, but you need to prepare the USB flash drive in advance. You can select any upgrade mode and refer to the following suggestions:

1.       For in-use RCD Servers, theWeb upgrade mode must be used to retain existing data.

2.       For initially deployed RCDServers, either mode is acceptable. The Web upgrade mode is recommended. If theversion is earlier than V1.0.9, you can directly use the USB flash drive modeto avoid cross-version upgrade.

Note:

1.       You need to use Google Chrome browser to log into the RCD Server management UI in Web upgrade mode.

2.       Do not randomly modify the name of the Webupgrade package. After the Web upgrade package is downloaded, check theintegrity of files by using the MD5 tool.

3.       In cluster and stack scenarios, you arerecommended to upgrade the slave RCD Server and then the upgrade the master RCDServer.

1.  The RCD Server upgradeusing an ISO file takes about 25–30 minutes. Please wait patiently.

The following uses V3.1_R1.11 as an exampleto describe the operation steps:

Step 1: Upload the completeRCDOS package.

Step 2: Click Upgrade.The system runs the complete system package to start the upgrade.

    Note: Theupgrade takes about 25 minutes. You can connect a display to the RCD Server toview the upgrade progress. After upgrade is complete, wait until the systemrestarts.

After the upgrade, click About tocheck the version number of the RCD Server.

Preparations before upgrade:

1.       Prepare a display and a keyboard and a mousewith USB ports.

2.       Prepare a USB flash drive with a capacity of 8GB, and format the USB flash drive.

3.       Prepare the created ISO image for the RCDOS.

4.       Select a tool that supports ISO image recordingon the USB flash drive. In this example, the UltraISO is used.

Note: UltraISO in version 9.5.5.2960 (UltraISO_9.5.5.2960.zip) is recommendedbecause the UltraISO of other versions may result in a programming failure.

The upgrade process is detailedas follows:

1.       Install the UltraISO in the Windows system.Insert the USB flash drive (≥4 GB). Start the UltraISO, click File on the menubar, and open the downloaded image file.

2.       In the menu bar, click Bootable to writethe image into the hard disk. In the window as shown in the following figure,set Write Method to USB-HDD+, and click Write.

In the displayed dialog box, indicating thatthe data on the USB flash drive will be lost, click Yes.

3.       After the recording is complete, click Closeand remove the USB flash drive.

4.       For currently delivered RCD Servers, the systemis set to boot from the USB flash drive by default. Insert the USB flash driveand restart the RCD Server, and wait until a page as shown in the followingfigure is displayed.

5.       Select the upgrade installation mode or factoryinstallation mode according to actual situations. Press Enter, and wait untilthe RCD Server is completely installed.

6.       Remove the USB flash drive and restart thesystem. If the login page as shown in the following figure is displayed after 3minutes, the installation is successful. If the login page is not displayed,the installation fails, and you need to install it again.

2.2.2      Upgrading the ClassManager_Teacher

Note: Since RCC_1.1, the teaching software isformally switched to ClassManager Rainbow.

The version upgrade of theClassManager_Teacher involves the version switching between two sets ofsoftware. During the upgrade, you need to uninstall the RCC-Teacher Tool andthe ClassManager, and then install the ClassManager Rainbow.

Step 1:Upgrade the RCC-Admin-Tool.

1.       On the teacher PC or common management PC,choose Control Panel > Add/Remove Programs in Windows.Uninstall the existing RCC-Admin-Tool.

2.       On the Web management page of the RCDServer, select Image on the left navigation tree. Click Admin-Toolin the lower right corner, and download and install the RCC-Admin-Tool of thelatest version.

Step 2:Upgrade the RG-ClassManager_Teacher on the teacher PC.

Note: If an earlier version ClassMananger1.X isinstalled, uninstall the RCC-Teacher and RG-ClassManager of the earlierversions and restart the PC.

1.       Start the RG-ClassManager_Teacher installed onthe teacher PC. After it connects to the server, it automatically complete theupgrade.

2.       If the RG-ClassManager_Teacher program isnot installed on the teacher PC, you can download and install theRG-ClassManager_Teacher_V3.1_R1.11.

    Note:After you install or upgrade the RG-ClassManager_Teacher, you need to checkwhether the IP address of the teacher PC is set on the Web page.

Check whether the IP address of the teacherPC is configured on the Web page.

Installing the workspace: After the RCDServer is upgraded to V3.0, the workspace is automatically upgraded.

Set the parameters for the workspace server.

Note: For details about the installation of theRG-ClassManager Rainbow, see the "ClassManager_Teacher installation."You need to apply for a license and import the license.

2.2.3      Image Upgrade

The image upgrade mainly refers to theimage-related software upgrade.

The upgrade includes the following aspects:

1.      Upgrade the Guest-Tool and update the Cloud Desktop driver and otheroptimization schemes

2.      Upgrade the ClassManager_Student.

Step 1: Upgrade the RCC-Guest-Tool.

a)       Log in to the RCD Server. On the menu bar, clickImage. Click Edit. On the displayed page, click Modify andthen enable the image.

(In normal situations, the RCC-Guest-Tool isautomatically upgraded. If theautomatic upgrade fails due to factors such as network disconnection, and theautomatic upgrade prompt is not displayed, you can access Drive D and manuallyclick RCC_Guest_Tool_General_Setup.exe.)

2.       Access the Windows Cloud Desktop, choose ControlPanel > Add/Remove Programs, uninstall the RCC-Guest-Tool, andrestart the Windows Cloud Desktop.

3.       After the Windows Cloud Desktop is restarted,click Cancel in all displayed hardware discovery wizards.

4.       In Windows, choose Start > Computer> Drive D, click and run the RCC-Guest-Tool of the latestversion, for example, RCC_Client_3.1_R1.11_Setup.exe.

5.       Restart the Windows Cloud Desktop. After thedesktop is displayed, shut down Windows.

6.       If there are multiple images,repeat the preceding steps.

Step 2: Upgrade the ClassMananger_Student.

         (In normal situations, the RCC-Guest-Tool is automatically upgraded. If automatic upgrade fails due to factors suchas network disconnection, access Drive D and manually click the RG-ClassManager_Student_V3.1_R1.11.exe.)

Use the ClassManageras an example. You need to uninstall the existing ClassManager Rainbow andinstall the ClassManager_Student of the latest version.

1.       Before editing the image, upload the latestClassManager_Student version to the shared directory (after the RCD Server isinstalled, Drive D is automatically uploaded).

2.       Edit the image Cloud Desktop. Locate therelevant program and click Uninstall.

Enter the password to start theuninstallation. The default password is ruijie.com.

3.      After the ClassManager of the earlier version is uninstalled,restart the Cloud Desktop system. Access the shared directory of drive D, andinstall the latest version of the ClassManager_Student.

4.      If there are multiple images, repeat the precedingsteps.

2.2.4      Upgrading the Rain Thin Client

Log in to the RCD Server and perform thefollowing operations:

Rain Thin Clients are classified into thefollowing types by hardware architecture:

1.      Rain Thin Clients using the x86 architecture: Typical devices areRain100 and Rain200. The hardware architecture has no different from commonPCs. For devices using this architecture, adopt the iPXE/PXE upgrade scheme. For details, see the "iPXE/PXE Upgrade Schemefor Thin Clients" in the appendix.

2.      Rain Thin Clients using the ARM architecture: Typical devices areRain100S and Rain200S. The Android system is used as the underlying system.Common devices using the ARM architecture include Mi Box and HiWiFi. Fordevices using this architecture, adopt the OTA upgrade scheme. For details, see the "OTA Upgrade Scheme forThin Clients" in the appendix.

Pay attention to the following points if youuse the PXE upgrade scheme to upgrade Thin Clients using the x86 architecture:

l  In addition to batch upgrade using the PXE upgradescheme, you can use a USB flash drive to upgrade a single Thin Client. Fordetails, see step 3: Upgrade the Rain100/Rain200 using the USB flash drive inthis chapter. Because there are a large number of Thin Clients, it is notrecommended to upgrade the Thin Client one by one by using the USB flash drive.

l  Before upgrading a Thin Client, ensure that theDHCP service is enabled and IP addresses in the specified address segment aresufficient. When you upgrade a Thin Client and restart the system, if thesystem remains at the page for obtaining the DHCP service, try to clear thelease, expand the DHCP address segment, and upgrade the system again.

l  By default, the multicast upgrade mode is adopted.In scenarios with poor network conditions (such as the 100M networkenvironment), you can use the unicast upgrade mode.

Note: The followingdescribes how to upgrade the Thin Clients using the x86 architecture (Rain100and Rain200) and the Thin Clients using the ARM architecture (Rain100S andRain200S).

Step 1: Upload theThin Client OS to the Web page of the RCD Server, and start all Rain ThinClients.

All Thin Clients conduct automatic upgradeafter connecting to the RCD Server.

After all Thin Clients are upgraded, theimage selection page is displayed.

The upload scheme for Rain100 and Rain200series is as follows:

The upload scheme for Rain100S, Rain200, andRain200C series is as follows:

Choose Upgrade > Thin ClientUpgrade, click Upload Firmware and load the standard OTA upgradepackage to the RCD Server. Ensure that the OTA upgrade package to be upgradedis the package for upgrading the Thin Client to the target version.

Click the upgrade package to be uploaded andupload it to the server.

After the upgrade package is uploaded,refresh the OTA service tab page. If the latest OTA version number isdisplayed, the upgrade is successful.

Step 2: Implementthe iPXE/OTA image distribution function.

For details, see the "iPXE Upgrade forThin Clients, PXE Upgrade for Thin Clients, and OTA Upgrade for ThinClients" in the Appendix.

For the Rain100 and Rain200, the iPXE upgrademode is recommended. If certain Thin Clients fail to be upgraded, use the PXEor USB flash drive upgrade mode.

For Rain100S and Rain200S, the OTA upgrademode is recommended.

Step 3: ConfigureThin Clients by using the RG-ClassManager 3.1 in a unified manner, and re-numberthe Thin Clients.

For details, see the"One-click Deployment" in "Typical Deployment Schemes".

1.       Insert the USB flash drive into a Thin Clientand restart the Thin Client. For the Rain100, press F2 or Deleteto enter the BIOS. Set the startup items and press F4 to save thesettings and exit.

2.       After booting from the USB flash drive, thesystem displays a page as shown in the following figure. Press Enter toenter the default options.

3.       During the boot, the system displays twoprompts, indicating that the data in the hard disk will be overwritten. Enter yand press Enter. Then, the system enters the restoration process.

4.       After the system restoration is complete, thesystem displays a page as shown in the following figure. Select Poweroff andpress Enter. The system is shut down, and the installation is completed.

5.       Remove the USB flash drive, restart the system,and confirm the system version.

       Deployment Preparation

3.1       Information Collection

The RCC product relies on the infrastructureof the computer classrooms and the campus network. Therefore, before productdeployment, learn about the situation of the equipment room, cable layout inclassrooms, and network topology, to determine the project deployment schedule.

Single-classroom cluster deployment:

Multi-classroom cluster deployment:

Before product deployment, check whether thedevice list is complete. The following table lists devices and tools used inthe single-classroom deployment.

1.       Clarify customer requirements, and check thedevice list and software version.

2.       Determine the software used in current teachingand requirements for the version of the teaching software.

3.       Before deployment, confirm with teachers aboutthe list of software versions to be installed. It is recommended that thesoftware be provided by the customer. Help the customer learn how to create OSimages and install software.

4.       Get gigabit switches and Category 6 networkcables ready. Ensure that keyboard and mouse suites with USB ports areconfigured for Thin Clients.

5.       Check whether the customer uses teachingmanagement software such as Red Spider and Mythware. If the customer uses theRG-ClassManager, confirm the common functions used by the customer, such asscreen broadcast and document delivery.

6.       Get a separate PC ready for installing theRG-ClassManager.

3.2      Network Planning

3.2.1     Network Planning for the Cloud Class

1． Check theexisting network environment and IP address segment planning of the equipmentroom. It is recommended that an independent Class-C network segment beconfigured for each classroom.

2． Configure twoIP addresses for each Thin Client (one for Thin Client and one for CloudDesktop), two IP addresses for each RCD Server, and one IP address for eachClassManager_Teacher.

3． Clarify theplanned gateway, subnet mask, and DNS server of the school.

Network address policy: Cloud Desktop CampusNetwork and Thin Client Campus Network (This network address policy isrecommended. You can configure it on the configuration wizard of the RCD Servermanagement screen.)

For example, for a classroom containing 60Thin Clients, you can allocate network segment 192.168.1.0/24 (IPaddresses in this network segment can be used to directly access the network) to this classroom.

IP network segment forthe Rain Thin Client: 192.168.1.11–192.168.1.70

Virtual IP networksegment for the Cloud Desktop: 192.168.1.111–192.168.1.170

RCD Server: master IPaddress: 192.168.1.100; slave IP address: 192.168.1.101

ClassManager_Teacher: 192.168.1.10

Gateway IP address:192.168.1.1; mask: 255.255.255.0; DNS: 192.168.0.254 (subject to the actualconfigurations)

3.2.2     Deployment Planning for the Cloud Class

In local deployment mode, a single RCD6000supports 60 Thin Clients only in one classroom. If there are more than 60 ThinClients in one classroom, you need to configure additional RCD Servers.

In local stack mode, more Thin Clients can beconfigured in a single classroom and each Thin Client has higher performance.Currently, there are three models of RCD Servers: RCD3000, RCD4500, andRCD6000, which can be stacked together.

In cluster deployment mode, multiple RCDServers can be deployed in a cluster to serve multiple classrooms.

For example:

Scenario 1: Oneclassroom has 90 Thin Clients. You need to configure two RCD6000 Servers as acluster to work in active/standby mode, to satisfy teaching requirements.

Scenario 2: There aretwo classrooms and each classroom has 90 Thin Clients. You can configure threeRCD6000 servers in a centralized manner or set up two new classrooms.

Scenario3: A classroom can be deployed with 60 Thin Clients in the case of standardconfiguration. If high-performance virtual Cloud Desktops (2 GB memory) areused, one RCD6000 supports 30 Thin Clients at most. You can deploy two RCDServers in stack mode or cluster mode, to support 60 high-performance ThinClients.

      Deployment Strategy (Required)

1.      Preparations (including network address planning)

2.      Installation and racking (including the racking of the RCD Servers,Rain Thin Clients, and switches and software installation)

3.      Software upgrade

4.      Software configuration and image creation

5.      Data synchronization (mandatory in cluster mode)

If youneed to upgrade the version that has been deployed in classrooms, back up dataof the RCD Server (mainly RCD data, including image files and database data).

Note:

1.      The RCD Server upgrade using an ISO file takes about 25–30 minutes.Please wait patiently.

2.      Because the hard disk controller of the Cloud Desktop is upgraded inV3.0, all images need to be edited using the Admin-Tool when the RCD Server isupgraded from an earlier version to V3.0. The Guest-Tool is automaticallyupgraded during image editing. You can normally use the images only after thenew hard disk driver is installed. You must restart the system to access thenew images and then install the Guest-Tool to validate the functions.

The following figure shows the procedure forupgrading the RCD Server to V3.0.

1.     If a customer uses the convergent computingfunction, communicate with the customer to obtain the software and then upgradethe version, and ensure that the upgrade time is sufficient (because thesoftware installed in the Rain system needs to be recovered).

2.      Generally, version rollback (rollback between major versions is notsupported) is performed when the upgrade is abnormal. Do not perform versionrollback in normal situations. Especially if you use the current version for along period of time, version rollback may cause anomalies to cooperativeproducts such as Rain.

3.     The entrances for image distribution vary withhardware architectures of the Rain Thin Clients. Simply, the Rain100 andRain200 adopt the x86 hardware architecture and use the Windows or Linux OS asthe underlying system. Therefore, they adopt the iPXE technical solution. TheRain100S adopts the ARM hardware architecture and uses the Android OS as theunderlying system. Therefore, the Rain100S adopts the OTA technical solution.

4.      You can select the multicast or unicast mode for image distributionby the iPXE and OTA according to the network conditions. If the networkcondition is good (1000M switch + 1000M network cable), the multicast mode isrecommended; if the network condition is poor or the multicast mode isunavailable, the unicast mode is recommended. If you have no idea of thenetwork condition, use the multicast mode.

5.     Authorization must be performed after theversion upgrade. Otherwise, the ClassManager Rainbow is valid for 45 days bydefault. Then, the software becomes unavailable upon expiration.

      FAQs

5.1       Products

Q1: How to view the hardwareinformation of the RCD Server?

1.       Upgrade the RCD Server to V1.1R1.18 or a laterversion and connect a display and a keyboard to the RCD Server.

2.       On the login page of the RCD Server, press F2and enter user name admin and password admin.

3.       After you successfully log in to the system,switch to the View System Information page using the keyboard.

4.       The configuration of the RCD Server isdisplayed. Select PAGE DOWN to display the hardware information.

Q2:What are differences between Thin Clients using the Linux system and ThinClients using the Windows system?

The Rain Thin Clients are installed with theLinux system by default. The Linux system does support a few software.Therefore, the Linux system is not applicable to the convergent computingscenarios.

If the convergent computing function isrequired, you can load the Windows system to the Thin Client.

It is boring and tedious to re-install the OSfor Thin Clients one by one. You can use the simple solution provided by theRCC solution. The steps are as follows:

1.      Re-install the Windows system on a Thin Client.

2.      Press Shift+S+F8 to access the Windows XPsystem and install the required software. For details, see "ConvergentComputing" in the Appendix.

3.      On the management page of the RCD Server, select the Thin Client andcreate an image.

The firmware creationfunction is only applicable to the Rain100/Rain200 series. The operation stepsare as follows:

1)       Select Thin Client Firmware from thenavigation tree and click Wizard.

2)       Select the firmware creation mode.

a)       Clone System Partition

Set Target ThinClient, which is used as the base disk image.

The systemautomatically fills in the firmware name. You can also set the firmware namebased on the naming convention described above.

Click Next.The Thin Client is restarted and enters the firmware creation page. Wait untilthe creation is successful. You can view the firmware in the Firmware List.

b)       Clone Whole Disk

This creation mode dependson the DHCP service of the RCD Server. Therefore, you need to configure theDHCP first.

The system starts to clonethe whole disk.

Set the Thin Clientto start in PXE mode. Restart the Thin Client. A page in red background isdisplayed.

2)       The Thin Client uses the default configuration.Enter y. Enter the name of the image to be saved as prompted.

3)       The image clone starts. After the clone iscompleted, a prompt indicating whether to shut down or restart the system isdisplayed. Select the restart option and access the BIOS. Disable the PXEstartup item.

4.      Upgrade the Thin Clients in batches in iPXE mode by using thecreated image.

5.      Re-configure the Thin Client. The Thin Client has switched to theWindows system at this time.

Q3:What software and hardware does the RCC support?

RCD V3.0 supports the following hardware:

l  RCD Server V1.0 and RCD Server V2.0

l  All Rain Thin Client versions

The following models of the ClassManangerRainbow support remote wakeup after power failure:

l  Rain100 V1.21 and Rain100 V2

l  Rain200 V1.1 and later versions

5.2      Deployment

Q1: How to correctly plan theIP addresses for a classroom using the cloud class to avoid address conflict?

You can use the easy deployment function tocorrectly plan IP address ranges of the Cloud Desktops and Thin Clients, toavoid Thin Client login failure due to address conflict. The configurationmethod is as follows:

1.       Before configuration, plan the IP addresssegment. Ensure that IP addresses in this segment are not used. For example,set the address segment of 60 Thin Clients to 192.168.1.11–192.168.1.70, theaddress segment of Cloud Clients is 192.168.1.101–192.168.1.160, and theaddresses of RCD Servers are 192.168.1.200/201.

2.       On the web management UI of the RCD Server,click Cloud Desktop, click Batch Config, and set the start IP address of CloudClients to 192.168.1.101.

3.       For a newly deployed classroom or a classroomwith Thin Clients upgraded to V1.1, enable the DHCP service, and configurecorrect DHCP address pool (addresses in the DHCP address pool must be in thesame network segment as the addresses of the RCD Servers), to ensure that all ThinClients in this classroom can obtain IP addresses upon startup.

4.       Install the CM2_Teacher of the latest version onthe teacher PC, configure the correct RCD Server IP address, and connect theteacher PC to the RCD Servers (after the CM2_Teacher is successfully installed,you need to restart the teacher PC).

5.       Select Batch Config. Click Scan to scan all ThinClients in the classroom. If the number of scanned Thin Clients is inconsistentwith the actual number, click Renumber. A unified numbering window is displayedon a scanned Thin Client. Then, you can find out the Thin Clients that do notobtain IP addresses or are not properly connected with network cables. Rectifythe faults. After all Thin Clients are scanned, click Renumber and press Enter.Number the Thin Clients in the classroom in sequence.

6.       After renumbering is completed, click BatchConfig and configure the Thin Client name (optional. It cannot be the same asthe Cloud Desktop name. Otherwise, a name conflict occurs), resolution(optional), RCD Server address (set to the IP address of the RCD Serverdeployed in the classroom), and Thin Client address (you are stronglyrecommended to manually configure a static IP address and set the start IPaddress, subnet mask, gateway address, and DNS address). You can click the eyeicon to view the configured addresses.

7.       After the configuration is confirmed, clickApply.

8.       After the addresses of all Thin Clients areconfigured, adjust the range of the DHCP address pool to the address range thatis not occupied by the Cloud Desktops and Thin Clients, or directly disable theDHCP service.

Q2:What are differences between the local deployment mode and cluster deploymentmode?

The local deployment refers to the CloudClass deployment scheme for a single classroom. The Cloud Class can use one RCDServer or multiple RCD Servers deployed in stack mode. All Cloud Desktopservices are only used in the current classroom.

The cluster deployment refers to the CloudClass deployment scheme for multiple classrooms. The cluster deploymentsupports load balancing of Cloud Desktops as well as failover of computingnodes.

Q3:Why doesn't a license take effect after it is imported?

1.       Ensure that the RCD Server is upgraded to thelatest version.

2.       The license is valid but the license is notsuccessfully uploaded to the RCD Server due to browser issues.

Solution: For the Internet Explorer, it isrecommended to enable the compatible mode and then import the license file.Alternatively, you can import the license file using Google Chrome.

Q4:How to configure IP addresses for the ClassManager_Students if the IP addressesof two classrooms are in the same network segment?

To save IP address resources, a college mayallocate IP addresses in the same network segment to two classrooms. When deployingCM3.0, you need to configure a static IP address for the CM3.0_Teacher for Thinclients and Cloud Desktops.

1.       If the IP addresses of two classrooms are in thesame network segment, ensure that the Thin Client addresses, Cloud Desktopaddresses, and RCD Server names do not conflict.

2.       During the deployment, disconnect the switchesof two classrooms.

a.       Configure the ClassManager_Students in eachclassroom by using the CM3.0_Teacher. You need to manually specify the IPaddresses of teacher PCs in the classrooms.

b.       Edit the images and manually specify theClassManager_Teacher IP address for CM3.0_Student in the image. Save thesettings.

3.       After the configuration is completed,interconnect the two classrooms and test the interconnection.

Q5: How to configure convergentcomputing in batches for Rain100 or Rain200 Thin Clients?

If the convergent computing function isrequired, you can upgrade the Windows system.

It is boring and tedious to re-install the OSfor Thin Clients one by one. You can use the simple solution provided by theRCC solution. The steps are as follows:

1.      Re-install the Windows system on a Thin Client.

2.      Press Shift+S+F8 to access the Windows XPsystem and install the required software. For details, see "ConvergentComputing" in the Appendix.

3.      On the management page of the RCD Server, select the Thin Client andcreate an image.

The firmware creation function is onlyapplicable to the Rain100/Rain200 series. The operation steps are as follows:

1)       Click Thin Client Firmware from thenavigation tree and click Wizard.

2)       Select the firmware creation mode.

a)       Clone System Partition

Set Target ThinClient, which is used as base disk image.

The systemautomatically fills in the firmware name. You can also set the firmware namebased on the naming convention described above.

Click Next. TheThin Client is restarted and enters the firmware creation page. Wait until thecreation is successful. You can view the firmware in theFirmware List.

b)       Clone Whole Disk

This creation modedepends on the DHCP service of the RCD Server. Therefore, you need to configurethe DHCP first.

The system starts toclone the whole disk.

Set the Thin Client tostart in PXE mode. Restart the Thin Client. A page in red background isdisplayed.

3)       The Thin Client uses the default configuration.Enter y. Enter the name of the image to be saved as prompted.

4)       The image clone starts. After the clone iscompleted, a prompt indicating whether to shut down or restart the system isdisplayed. Select the restart option and access the BIOS. Disable the PXEstartup item.

4.      Upgrade the Thin Clients in batches in iPXE mode by using thecreated image.

5.     Re-configure the Thin Client. The Thin Clienthas switched to the Windows system at this time.

5.3       Upgrade

Q1: What is the RCC V3.0upgrade route map?

RCD Server upgrade:

Currently, the latest version of RCC V3.0 isRG-RCC_V3.0_R1.14. To upgrade an RCD Server from V1.0.9.36 or V1.1 to V3.0,load the patch package in Web mode, and then load the system package. An RCDServer of V2.0 or a later version can be directly upgraded to V3.0 in Web mode.

If the version of an RCD Server is V1.0.8.8,you are suggested to adopt the ISO upgrade mode using the USB flash drive(directly upgrade the current version to V2.0_R1.18 and then load theV2.0_R1P1.19 patch package or a later patch package).

Note: After the RCD Serveris upgraded to V3.0, you are recommended to perform deployment or configurationby using Google Chrome.

Thin Client upgrade:

The installation package for Android-basedThin Clients is already integrated into the installation package of RCD ServerV3.0.

Rain100V2: Thin Client V1.1 and laterversions adopt the installation package of Thin Client V3.0 for the upgrade.

Rain100(V1.0) inherits the system of ThinClient V2.0.

Rain200(V1.0) inherits the system of ThinClient V2.0.

Rain100(V1.1) and later versions inherit thesystem of Thin Client V2.1.

Rain200(V1.01) andlater versions inherit the system of Thin Client V2.1.

Q2: How to upgrade the ThinClients in iPXE mode without modifying the BIOS?

In V2.0_R1P1.19, you do not need to flash theBIOS of each Thin Client. You can rapidly upgrade the Thin Clients on the Webmanagement UI.

1.       After you successfully upgrade the RCD Server toV2.0_R1P1.19, power on all Thin Clients in the classroom. The RCD Serverautomatically upgrades the RCC Thin Clients to V2.0_R1P1.19. Ensure that allThin Clients are successfully upgraded and display the image selection screen.

2.       Upload images. On the Web management UI, choose ThinClient > Image > Upload. For classrooms that do notneed to install software in the underlying system or use the convergentcomputing software, it is recommended that the underlying be upgraded to theLinux system.

3.       Enable the DHCP address pool on the RCD Server,configure a sufficient address space (ensure that the address quantity is morethan twice the number of Thin Clients in the classroom), clear the lease, andrestart the DHCP service. (Assume that there are 60 Thin Clients in aclassroom, and the RCD Server address is 192.168.1.200. Set the subnet addressof the DHCP address pool to 192.168.1.0, the start IP address to 192.168.1.2,and the end IP address to 192.168.1.199. Clear the lease and restart the DHCPservice). It is recommended that youdisconnect the classroom from the external network to prevent other DHCPservers from affecting the upgrade in iPXE mode.

4.       After the DHCP address is configured, choose ThinClient Upgrade > Upgrade. Click Prepare for thecorresponding image. Set the distribution mode to the default multicast mode.Click Config Wizard. Addall online Thin Clients in the candidate list to the to-be-upgraded Thin Clientlist (ensure that all Thin Clients are successfully connected). Click Prepare.After all Thin Clients are ready, click Upgrade to install the ThinClient system installation.

5.       After the ROMs of the Thin Clients aresuccessfully upgraded, click About. The displayed system version isRainOS_V1.0_R1.8_X/L/A.

Q3: Common problems occurringin the upgrade of the Rain100 or Rain200 in iPXE mode

Phenomenon 1: After Kickoutis clicked on the Web page and the Thin Client is restarted, the Imagepage is displayed again. Check the size of the DHCP address pool. Clear thelease and check whether there are other DHCP servers and whether the DHCPserver is restarted.

After you click the upgrade in iPXE mode, theImage page is displayed again. Click Thin Client Preparation on theweb UI to prepare the Thin Clients again.

Phenomenon 2: An error shown in the followingfigure occurs. You need to manually restart the Thin Client. After restart, theThin Client automatically enables the iPXE function.

Phenomenon 3: If a page in red background isdisplayed, where Restart, Shut Down, Enter CMD, and Backare displayed, press Enter to select Enter CMD and enter /var/log/clonezilla.logto check whether the image is correct.

Phenomenon 4: The PXEfunction is available on the Thin Client, but the Thin Clients cannot obtain IPaddresses in iPXE mode. In this situation, you can use the PXE upgrade mode.

Q4:Why don't some non-Ruijie switches support iPXE?

Phenomenon: A classroom uses non-Ruijieswitches such as Huawei 57 series switches. The Thin Clients of the Cloud Classcannot be upgraded in iPXE mode.

Cause analysis: Generally, the UDP multicastpackage suppression function is enabled on these non-Ruijie switches bydefault. However, the iPXE uses the multicast mode to perform batch operations.

Solution: Log in to Huawei switch using aconfiguration cable and run stp disable for all ports of Huawei switch.

Q5:How to recover a Thin Client after upgrade failure?

After the upgrade for a Thin Client fails,you can use the following method for recovery:

1.       Upgrade a Thin Clientthat is ready to be upgraded. After the upgrade is successful, power off theThin Client.

2.       Disable the image distribution function, clearthe DHCP lease, restart the DHCP server, and enable the image distributionfunction again. If the upgrade of a Thin Client fails, replace the networkcable with a new one, enable the Thin Client, and try the upgrade again in iPXEmode.

3.       During the upgrade, if the power is interruptedor the image distribution is terminated accidentally, you can use only the PXEmode to upgrade.

Q6:Common causes for RCD Server upgrade failure in USB flash drive mode

1.       Ensure that the MD5 value in the ISO file usedfor RCD Server upgrade is correct. After the upgrade file is downloaded, verifythe MD5 value.

2.       For the USB flash drive that has been used,write 0s. Open the UltraISO and do not select any file. Write 0s, and formatthe USB flash drive.

3.       Replace the USB flash drive.

5.4      Use

Q1: Why is the screenbroadcast function of the ClassManager Rainbow unavailable?

1.       When installing the RG-ClassManager 3.0, it isrecommended to disable or exit the security guard or antivirus software. Afterthe RG-ClassManager 3.0 is successfully installed, restart theClassManager_Teacher PC. After the ClassManager_Teacher PC is successfullyrestarted, add the installation directory of RG-ClassManager 3.0 to thewhitelist of the security guard or antivirus software.

2.       Check whether the 360 Wi-Fi or VPN is enabled onthe ClassManager_Teacher PC. If yes, disable them because they will affect theobtaining of the ClassManager_Teacher PC IP address by the Thin Client.

3.       Check whether the switch model is as224-gt ores224-gt. If yes, run the no ip igmp-snopping command.

4.       Check whether the underlying system needs to beupgraded. On the Image page, check whether the system version number isconsistent with that in the release notes.

5.       Check whether the IP address of the Thin Clientand gateway address are correct and are in the same network segment as theClassManager_Teacher PC.

6.       Scan the Thin Clients on the CM3.0_Teacher PC.Check whether the addresses of the RCD Server and ClassManager_Teacher PC arecorrectly configured on the ClassManager_Student.

7.       To use the automatic scanning mode, you canuniformly set the IP address of the ClassManager_Teacher PC to 0.0.0.0(automatic scanning) on the Thin Clients.

Q2: Common ClassManagerRainbow authorization problems

Q1: How toperform authorization when RCD Servers are deployed in stack or cluster mode?

There are two authorization modes for RCDServers deployed in stack or cluster mode:

In stack mode, you can bind each RCDServer with one authorization code and then import the authorization codes tothe Master RCD Server.

In cluster mode, you can bind the masterRCD Server with each authorization code and then import the authorization codesto the master RCD Server.

Q2: How to unbindthe authorization when the RCD Servers are deployed in stack or cluster mode?Can each RCD Server be deployed in standalone mode?

If the first authorization mode describedin Q1 is used, you can directly release the cluster without unbinding theauthorization. Then, each RCD Server is changed to work in standalone mode.
If the second authorization mode described in Q1 is used, you need to unbindN-1 authorization codes (assume that there are N RCD Servers) from the masterRCD Server in the PA system. Then, independently authorize the original slaveRCD Servers and computing nodes.

Q3: If authorization A imported into the RCD Server isincorrect and it is unbound, and new authorization B is generated, do I need todelete the previously imported authorization A and how can I delete it?

You do not need to delete authorization A.The authorization detection function of the RCD Server is associated with thePA system. The RCD Server works normally as long as a correct authorizationcode is configured regardless of how many incorrect authorization codes areimported to the RCD Server.

Q4: How long can the ClassManager_Teacher be availablewithout a license by default?

A: 45 days

Q5: Is the ClassManager_Teacher completely unavailableafter 45 days?

A: Only some functions are available, forexample, start, screen broadcast, and remote shutdown

Q3:A static IP address is correctly configured for a Cloud Desktop. After theclass starts using the CMR, the IP address is abnormal. How to rectify thefault?

Perform the following steps to locate andrectify the fault:

1.      Check whether the IP address of the Cloud Desktop conflicts withthat of the Thin Client and whether the range of the DHCP address pool coversthe IP addresses in the Cloud Desktop list. If yes, adjust the range of theDHCP address pool.

2.      Log in to the Thin Client and check whether its IP address conflictswith the IP address of another PC in the current network environment. On theCloud Desktop, run cmd, and then run the ipconfig command. Recordaddress 169.254.x.x and the RCD Server name of the Cloud Desktop. End the classusing the CMR. Change the IP address of the Cloud Desktop. Start a class again.Check whether the Cloud Desktop can obtain a new IP address. (If an IP addresscannot be successfully pinged, it does not indicate that the IP address is notused, but the ping function may be disabled on the device.)

3.      Check whether the Guest-Tool in the image is upgraded to a versionmatching the RCD Server. Check whether processes vdagent.exe and vdservice.exeexist in the image and task manager. If not, the Guest-Tool may not be properlyinstalled. It is recommended to edit the image and re-install the Guest-Tool.

4.     Check whether any suspicious process (such asviruses or Trojan horse) exists in the image. Scan the software to be installedin the image to remove viruses and then upload it to the image. Check whetherthe image is normal. Use a clean image (a standard image without any software)to start a class. Check whether address conflict occurs.

Q4: How to expand thecapacity of drive C for an image?

1.       In the image, set System Config toCustom. Set Hard Disk Space(GB) to 30 or 40, which isappropriate.

2.       Enable the modified image and complete thememory capacity combination.

a)       In Windows 7, right-click Computer andselect Manage > Disk Management. Right-click drive C andselect Extend Volume. Click Next until the expansion iscompleted.

b)       In Windows XP system, download thePartitionMagic8.0. In the image, run the PartitionMagic8.0 and adjust thecapacity of drive C. After the adjustment is completed, uninstall the software.

Q5:Why does a Thin Client display only the teacher's shared directory but thestudent's shared directory is not displayed?

Phenomenon: Only the teacher's shareddirectory is displayed on the Thin Client.

Cause: The student's shared directory is cuton the ClassManager_Teacher.

Solution:

Solution 1: Shut down the CMR teacher PC. Onthe web UI of the RCD Server, choose Classroom > Policy.Disable and then enable the option for automatically mounting the network disk.Then, start the CMR teacher PC.

Solution 2: Inform the teacher to back up thestudent's shared directory in advance. If it is cut, copy the backup directoryand paste it back.

Q6:Why can't the teacher's shared disk and the student's assignment disk beaccessed on the ClassManager_Teacher PC?

Phenomenon: The teacher's shared disk and thestudent's assignment disk cannot be opened on the ClassManager_Teacher PC.

Cause: After the ClassManager_Teacher isupgraded, the function of automatically mounting network disks is not enabled.

Solution:

1.      In the end class state, on the web UI of the RCD Server, choose Classroom> Policy, and select the option for automatically mounting networkdisks.

2.      Check whether the security guard or antivirus software is installedon the ClassManager_Teacher PC. If yes, add the RCC_ClassManager_Teachdirectory to the trust zone or whitelist of the antivirus software. In Windows7 system, excessive default system permissions will cause a mounting scriptrunning failure on the CMR. You can modify the system permissions, and restartthe ClassManager_Teacher PC.

5.5      Maintenance

Q1: Why can't the RCD Serverstart up normally?

Phenomenon: After the RCD Server is poweredon, it cannot normally start.

Check whether the fault is caused by asoftware or hardware failure as follows:

1.      Connect a display to the RCD Server. Check whether the RCD Server isnormally started up. Press the Delete button to check whether you canaccess the BIOS normally. If you can access the BIOS, check whether the SSD iscorrectly identified. If the SSD cannot be identified, the SSD is faulty, andyou can call service hotline 4008. If the SSD can be identified, the RCD Serversoftware is faulty. You can re-install the RCC system software on the RCDServer by using the USB flash drive.

2.      If you cannot access the BIOS, perform the following steps:

a)       Check whether the memory module of the RCDServer is loose. Remove and then insert the memory module and button battery.

b)       If the RCD Server cannot be started yet, use aneraser to clean the edge connector (a protruding part of a memory module thatis inserted into an expansion slot) and insert it to the memory slot because exposededge connector may be oxidized and causes poor contact.

c)       If the RCD Server cannot be started yet, removethe memory modules until only one is left. If the RCD Server can be started,insert another memory module, and then boot the system again. If the systemcannot be booted after you insert a certain memory module, this memory moduleis faulty.

3.      If the fault persists, call service hotline 400 for DOA processing.

Q2:Why does the startup cost a long period of time after the RCD Server encountersa power failure?

Phenomenon: After the RCD Server encounters apower failure, it takes more than 20 minutes to start up.

Fault cause: The RCD Server V1.1.x has asoftware bug. In certain power failure scenarios, this bug is triggered,resulting in long startup duration. Upgrade the RCD Server V1.1.x to RCD V3.0to fix the bug.

In extremely few cases, after the RCD Serverencounters a power failure and is started up again, there is no output on theconnected display. In such cases, remove and insert the memory modules andbutton batteries.

Q3:Why are certain Rain Thin Clients stuck at the shutdown screen for about fiveminutes when they are remotely shut down using the CM2 teacher software?

Phenomenon: WhenThin Clients are remotely shut down using the CM2teacher software, certain Thin Clients are stuck at the shutdown screen.

Solution: Access theBIOS. In Advanced/ACPI Settings, set EUP Support to ENABLE.Save the settings and restart the system. Access the BIOS again, set EUPSupport to DISABLE. The fault is rectified.

Q4:How to correct the DNS configuration of a Cloud Desktop?

1.      The DNS configuration of the Cloud Desktop is synchronized from theDNS configuration of the RCD Server. Therefore, you need to only modify the DNSconfiguration on the RCD Server. To modify the DNS configuration, log in to theweb management UI of the RCD Server, and choose System > NetworkSettings > Edit. Modify the DNS configuration.

2.      On the Cloud Desktop, choose Classroom, add one Cloud Desktopto the Cloud Desktop list, delete the Cloud Desktop (trigger the Cloud Desktopsynchronization), and then start a class to check whether the DNS configurationis correct.

Q5: What are theoperation precautions after the motherboard of the RCD Server is replaced?

Context:

Because the system of theRCD Server is stored in the storage disk, the system data is retained after themotherboard is replaced. You do not need to upgrade the system. Pay attentionto following points:

1.      After the motherboard is replaced, the NIC hardware is changed. TheOS can identify the new NIC, but the information about the old NIC stillremains in the system, resulting in the network interruption. Therefore, youneed to reset the network.

2.      After the motherboard is replaced, the SN is null or is not acorrect Ruijie SN. You need to re-programthe SN. Otherwise, authorization problems may occur.

Key operation points:

1.       Manually record the IP address of the RCDServer, and record the original SN (or record device exterior information) sothat you can re-upgrade the original SN after the motherboard is upgraded.

2.       After the motherboard is replaced and the systemis started up, the configuration screen is displayed (if not, check thehardware).

3.       Access Management Network Recovery.Select Restore Network. In the displayed dialog box, click OK toreset the network.

4.       Restart the system and access the precedingscreen again.

5.       Access Management Network Recovery.Configure the backup IP address.

6.       After the system is restarted, the system isrestored to the state before motherboard replacement.

7.       Request professional personnel to re-program theoriginal SN. Otherwise, other SNs may encounter errors such as 00001. If a newSN is programmed, ensure that the SN has been recorded in Ruijie PA system.

Q6: What'sthe LAN1/LAN2 used for?  Load balance? If the lan1 down, can all switchover tolan2?

A:two NICs each one support half thin client service, if the lan1 down, only halfthin client will switch over to lan2.

Q7: In real deployment, is itneed to use both two ports?

A:Yes, we need to use both two ports of RCD server.

Q8: sounds likes there is nodifferent if we use LACP for LAN1/2 or separate it?

A：Summarizedlike this:   for separate's port,  if one is down, half thinclient will be gone, if aggregate port, still remain all thin client, but alittle bit slow. In other words, only onelan port for all thin clients, which may affect the performance.

Q9: What is the bandwidth required for each thin client?

A:About 3-4Mbps

Q10: If server down, all client will go down also?  How if hard disk onRCD broken? Can use external storage to store user/OS Data?

A:Yes, if server down, all client will go down also, we cannot support externalstorage for now.

Q11: If work on the mode 3, is it private mode completely?

A:Yes, except there is a virtual wan IP address of RCD server.

Q12: Can RCD server and thin client be in difference subnet?

A:No, cannot.

Q13: How to connect the port 1 and port 2?

A:Connect both Lan 1 and Lan 2 of RCD server to switch.

Q14: Can RCD run Raid?

A:We cannot support the Raid now.

Q15. What is the period we recommended for backup the RCD storage?Monthly?

A:Monthly.

Q16. Any gigabit switchesmanaged or unmanaged also can work right?

A:Yes. Any gigabit switches can work.

Q17: From what is understand the server can have share folder forstudent....what if the folder attack by virus

A:Recommend to disable the internet access and USB devices, so there will be lesschance for student upload virus to shared folder.

Q18: supports auto backupright? Or needs manual backup?

A:Needs manual backup

Q19: Just saw RCM's poster, it said support RAID and so on....is it thenext version of RCD?

A:Not support RAIN in current RCD version.

Q20: Normally, we just need to upgrade all from RCD, right?

A:Yes.

Q21: If the teach PC corrupted, the class manager need to reinstall?

A:Reconfiguring the teacher IP address on RCD server is ok.

Q22: How do we calculate the maximum resource for each thin client can getfrom the RCD server?

A:Check this info on image page.

Q23: Heard that RCD need to weekly reboot for clearing the cache?

A:  Yes.

Q24: Disable Internet isdisable layer 3 routing, including intranet network, right?

A:it will disable the internet access not including intranet network.

Q25: How many OS Linux and windows already tested so far?

A:XP, Windows 2003, Windows 2008, Window 7, Windows 8, Windows 10, Ubuntu,Centos, Fedora

Q26: Does the quiz can be random? Like in the examination each studentshould get difference sequence.

A:Not. The quiz can be random

Q27: The works only with office 2010 right? If we use new office versionthis workspace cannot support? When will have the fix?

A:Only Office 2003, Office 2007, Office 2010 are supported.

Q28: the prompt shows theassociated image files is in use, not response after click “save and enable”,how can we solve this issue?

A: Solution:  loginto RCD server à Home Page à More à login orshutdown

Note:when you edit the image again, remember to use the Windows OS’s shutdownfunction to end the Image Creation, the AdminTool window will disappearautomatically once the Image is shutdown

Q29: Why Thin Client showsconnecting fail?

A: The possiblecause is no cloud desktop created yet. We need to create cloud desktop on ConfigWizard or create it on classroom page.

Q30: Do we need to renumberthe cloud desktop after re add the cloud desktop on classroom page.

A: Yes It is.

Q31. How to add the studentaccount?

A: Recommend toimport the student account via workspace of RCD server, the password of theaccount is optional.

Log in to the RCDServer as an administrator, go to System à Workspace, and click “Confg” on the upper right corner

Q32. Why cannot enter theoperation after installing the image.

A: Solution: Requestto install the guest tool first, the guest tool is equivalent to the driver ofthe operating system

Q33. What is the possiblereason for upgrading fail via USB?

A: It is necessaryto burn the system file with UltraISO, otherwise it may cause unknownexception.

Q34: Why some features of theCMR-teacher cannot work?

A: Request toinstall the CMR-Student component on cloud desktop first. Once OS installation done,go to “My Computer” -> D:\ drive to install CMR-Student component

Q35: Why there is no OS forselection after completing the image installation?

A:only when the image is enable can it be displayed on the thin client.

Q36: How to check current IPaddress of the RCD server if we forget the configuration?

A:Connect the server to the display, press F2 to display the systemconfiguration.

Q37: How to apply fortemporary license for RCD server?

A:login to the PA system to apply for the temporary license

PAlogin address: http://pa.ruijie.com.cn

Publicaccount used for applying for the ClassManager license is as follows:

User name: classmanager or classmanager1 orclassmanager2

Password: ruijie

Q38: How to login to the RCDserver when it is used initially?

A:You could login to the web UI of RCD server. The default IP address of the RCDserver is 192.168.122.1/24 and 192.168.122.2/24. Both username and password areadmin. Remember to connect the NIC port.

Q39: Why no response whenclicking the account function on CMR-teacher?

A:The IP address of the workspace is wrongly configured, it should be RCD serverIP address. Log in to the RCD Server as an administrator, go to System à Workspace, and click “Parameter”on the upper right corner and change the workspace server IP address.

      Product Limitation

6.1      Translation problems

“Edit” means modify theoperating system parameters and won’t enter the system after clicking it.

“Save and Enable” means modifyand start, you can enter the landing system to complete the configuration.

6.2      Resolution problem

Due to theresolution problem, the scan interface is abnormal. According to the feedbackfrom the R & D team, there is no version plan to optimize.

6.3      Upgrade Time Limitation

There is noprogress bar when upgrading, the system prompts upgrade for only 5 minutes, butit takes at least 15 minutes.

Solution:connect the RCD Server to the display, check the current upgrading status.

6.4      License Limitation

ValidityPeriod of license is showing only minutes, but no showing specific expiry date.

Solution:there is no version plan to optimize it.

6.5      Progress Bar Limitation

No progressbar shows file uploading when select the homework material on Assignment page.

Solution: The progress barwill pop up when clicking on OK.

6.6      Quiz Function Limitation

The Quizfunction cannot work

Solution:Request to install the office on the cloud desktop first, only office 2003,office 2007, office 2010 are supported.

6.7      Passing Function Limitation

Issue: thePassing function cannot work.

Solution:Request to install the flash on cloud desktop first.

6.8      Display Limitation

Issue: Somerain terminals are not responding to the display screen.

Solution: SomeRain terminal needs to connect the display screen first and then power up therain terminal.

6.9      Image File limitation

Issue: Fail toupload the image

Solution: The imagefile format should be .iso or .base.

6.1      Login Limitation

When theadministrator logs out the RCD server, the password could be seen in a moment.

6.2      BMC Address Limitation

The server fails to configure the BMCaddress in the TUI interface, it is recommended to use Web for the configurationof the BMC address.

Ruijie Cloud Class Solution Implementation Cookbook(V1.0)

Copyright Statement

Ruijie Networks©2013

Ruijie Networks reserves all copyrights ofthis document. Any reproduction, excerption, backup, modification,transmission, translation or commercial use of this document or any portion ofthis document, in any form or by any means, without the prior written consentof Ruijie Networks is prohibited.

,,,,,,,,,  ,,  are registered trademarks of Ruijie Networks. Counterfeit is strictlyprohibited.

Exemption Statement

This document is provided “as is”. Thecontents of this document are subject to change without any notice. Pleaseobtain the latest information through the Ruijie Networks website. RuijieNetworks endeavors to ensure content accuracy and will not shoulder anyresponsibility for losses and damages caused due to content omissions,inaccuracies or errors.

Preface

This article provides a systematic approach to identifying andremedying problems that may arise as you use your cloud class product over aperiod of time. This guide is not intended to replace configuration guide or tobe an all-inclusive guide for every application. Rather, it is an attempt toprovide you with the knowledge and skills necessary to correct the most commonissues that you may encounter.

This article introduces the basic concepts,methodology, and general troubleshooting guidelines for problems that may occurwhen you configure and use cloud class product.

Audience

l  NetworkEngineers

l  NetworkAdministrator

Obtain Technical Assistance

l  RuijieNetworks Websites : http://www.ruijienetworks.com

l  RuijieService Portal : http://caseportal.ruijienetworks.com

Welcome to report error and give advice inany Ruijie manual to Ruijie Service Portal

Revision History

      Content

Preface. 0

1      Content 1

2      Preface. 2-1

3      Deployment Strategy (Required) 3-2

4      Deployment Preparation. 4-3

4.1           Information Collection. 4-3

4.2           Network Planning. 4-6

4.2.1        Network Planning for the Cloud Class. 4-6

4.2.2        Deployment Planning for the Cloud Class. 4-6

5      Deployment 5-7

5.1           Installation and Configuration. 5-7

5.1.1        Installing the RCD Server 5-7

5.1.2        Installing the ClassManager_Teacher PC.. 5-8

5.1.3        Installing the Thin Client 5-16

5.1.4        Installing Images. 5-20

5.1.5        Installing Software in Images. 5-28

5.2           Version Upgrade. 5-31

5.2.1        Upgrading the RCD Server 5-31

5.2.2        Upgrading the ClassManager_Teacher 5-39

5.2.3        Image Upgrade. 5-41

5.2.4        Upgrading the Rain Thin Client 5-43

6      Typical Deployment Schemes. 6-52

6.1           Local Deployment Mode. 6-52

6.1.1        Cloud Desktop Campus Network and ThinClient Campus Network. 6-52

6.1.2        Cloud Desktop Campus Network and ThinClient Private Network. 6-64

6.1.3        Cloud Desktop Private Network and ThinClient Private Network. 6-64

6.2           Stack Deployment 6-65

6.3           Cluster Deployment 6-86

6.4           One-click Deployment 6-93

6.5           RCD Server Binding. 6-101

6.6           Examination Scenario. 6-108

7      Appendix. 7-112

7.1           Interpretation of Product VersionNumbers. 7-112

7.2           ClassManager Software License. 7-113

7.2.1        Generating the License File Using anAuthorization Code. 7-116

7.2.2        Granting Temporary Authorization. 7-118

7.2.3        Unbinding the Authorization. 7-118

7.2.4        Granting Authorization in Cluster orStack Scenario. 7-118

7.3           RCD Server Commissioning. 7-119

7.4           Shortcut Keys for Rain Thin ClientCommissioning. 7-123

7.5           PXE Upgrade Mode. 7-124

7.6           Fast Upgrade Mode. 7-127

7.7           iPXE Upgrade Mode. 7-130

7.8           OTA Upgrade Mode. 7-132

8      FAQs. 8-136

8.1           Products. 8-136

Q1: How to view thehardware information of the RCD Server?. 8-136

Q2: What aredifferences between Thin Clients using the Linux system and Thin Clients usingthe Windows system?. 8-138

Q3: What softwareand hardware does the RCC support?. 8-141

8.2           Deployment 8-141

Q1: How to correctlyplan the IP addresses for a classroom using the cloud class to avoid addressconflict?. 8-141

Q2: What aredifferences between the local deployment mode and cluster deployment mode?. 8-143

Q3: Why doesn't alicense take effect after it is imported?. 8-143

Q4: How to configureIP addresses for the ClassManager_Students if the IP addresses of twoclassrooms are in the same network segment?. 8-143

Q5: How to configureconvergent computing in batches for Rain100 or Rain200 Thin Clients?. 8-144

8.3           Upgrade. 8-147

Q1: What is the RCCV3.0 upgrade route map?. 8-147

Q2: How to upgradethe Thin Clients in iPXE mode without modifying the BIOS?. 8-147

Q3: Common problems occurringin the upgrade of the Rain100 or Rain200 in iPXE mode. 8-148

Q4: Why don't somenon-Ruijie switches support iPXE?. 8-149

Q5: How to recover aThin Client after upgrade failure?. 8-149

Q6: Common causesfor RCD Server upgrade failure in USB flash drive mode. 8-150

8.4           Use. 8-150

Q1: Why is thescreen broadcast function of the ClassManager Rainbow unavailable?. 8-150

Q2: CommonClassManager Rainbow authorization problems. 8-150

Q3: A static IPaddress is correctly configured for a Cloud Desktop. After the class startsusing the CMR, the IP address is abnormal. How to rectify the fault?. 8-152

Q4: How to expandthe capacity of drive C for an image?. 8-152

Q5: Why does a ThinClient display only the teacher's shared directory but the student's shareddirectory is not displayed?. 8-153

Q6: Why can't theteacher's shared disk and the student's assignment disk be accessed on theClassManager_Teacher PC?. 8-153

8.5           Maintenance. 8-154

Q1: Why can't theRCD Server start up normally?. 8-154

Q2: Why does thestartup cost a long period of time after the RCD Server encounters a powerfailure?. 8-154

Q3: Why are certainRain Thin Clients stuck at the shutdown screen for about five minutes when theyare remotely shut down using the CM2 teacher software?. 8-155

Q4: How to correctthe DNS configuration of a Cloud Desktop?. 8-155

Q5: What are theoperation precautions after the motherboard of the RCD Server is replaced?. 8-155

Q6: What's the LAN1/LAN2 used for?  Load balance? If the lan1 down, canall switchover to lan2?. 8-157

Q7: In realdeployment, is it need to use both two ports?. 8-157

Q8: sounds likesthere is no different if we use LACP for LAN1/2 or separate it?. 8-157

Q9: What is thebandwidth required for each thin client?. 8-158

Q10: If server down,all client will go down also?  How if hard disk on RCD broken? Can use externalstorage to store user/OS Data?. 8-158

Q11: If work on themode 3, is it private mode completely?. 8-158

Q12: Can RCD serverand thin client be in difference subnet?. 8-158

Q13: How to connectthe port 1 and port 2?. 8-158

Q14: Can RCD runRaid?. 8-158

Q15. What is theperiod we recommended for backup the RCD storage? Monthly?. 8-159

Q16. Any gigabitswitches managed or unmanaged also can work right?. 8-159

Q17: From what isunderstand the server can have share folder for student....what if the folderattack by virus. 8-159

Q18: supports autobackup right? Or needs manual backup?. 8-159

Q19: Just saw RCM'sposter, it said support RAID and so on....is it the next version of RCD?. 8-159

Q20: Normally, wejust need to upgrade all from RCD, right?. 8-159

Q21: If the teach PCcorrupted, the class manager need to reinstall?. 8-160

Q22: How do wecalculate the maximum resource for each thin client can get from the RCDserver?. 8-160

Q23: Heard that RCDneed to weekly reboot for clearing the cache?. 8-160

Q24: DisableInternet is disable layer 3 routing, including intranet network, right?. 8-160

Q25: How many OSLinux and windows already tested so far?. 8-160

Q26: Does the quizcan be random? Like in the examination each student should get differencesequence. 8-160

Q27: The works onlywith office 2010 right? If we use new office version this workspace cannotsupport? When will have the fix?. 8-161

Q28: the promptshows the associated image files is in use, not response after click “save andenable”, how can we solve this issue?. 8-161

Q29: Why Thin Clientshows connecting fail?. 8-162

Q30: Do we need torenumber the cloud desktop after re add the cloud desktop on classroom page. 8-162

Q31. How to add thestudent account?. 8-163

Q32. Why cannotenter the operation after installing the image. 8-164

Q33. What is thepossible reason for upgrading fail via USB?. 8-164

Q34: Why somefeatures of the CMR-teacher cannot work?. 8-164

Q35: Why there is noOS for selection after completing the image installation?. 8-165

Q36: How to checkcurrent IP address of the RCD server if we forget the configuration?. 8-166

Q37: How to applyfor temporary license for RCD server?. 8-167

Q38: How to login tothe RCD server when it is used initially?. 8-167

Q39: Why no responsewhen clicking the account function on CMR-teacher?. 8-168

9      Product Limitation. 9-169

9.1           Translation problems. 9-169

9.2           Resolution problem.. 9-170

9.3           Upgrade Time Limitation. 9-171

9.4           License Limitation. 9-171

9.5           Progress Bar Limitation. 9-172

9.6           Quiz Function Limitation. 9-173

9.7           Passing Function Limitation. 9-173

9.8           Display Limitation. 9-174

9.9           Image File limitation. 9-174

9.1           Login Limitation. 9-174

9.2           BMC Address Limitation. 9-174

       Preface

With the maturation of the cloud computingtechnology and the increase of customer problems, fat access points (APs) arenot the most ideal solution for the PC equipment room. The RG-RCC Solution is aRuijie homegrown product that is committed to resolving management problemsoccurring in conventional traditional computer classrooms, and effectivelyenhancing the user experience. Ruijie Cloud Class (RCC) is a new-generationcomputer classroom construction solution developed according to the ideas ofcontinuous integrating and optimizing devices in the campus equipment rooms, incombination with the actual situations of numerous general education schools.The deployment of only one RCD Server in each classroom can provide dozens ofCloud Desktops that outperform common PCs. Students can experience vivid clouddesktop environment from the Thin Clients served by these Cloud Desktops. TheRCC provides a variety of teaching system images based on courses and closelyintegrates cloud technologies and education scenarios, thereby achievingcentralized teaching, intelligent management, and simple maintenance, andbringing the computer classroom into the cloud era.

The RG-RCC solution consists of the followingproduct components:

l  RG-RCD Server: It is a high-performance cloud desktop server. OneRCD Server supports 30–60 concurrent cloud desktops. RCD Servers can beindependently managed through the Web management UI.

l  RG-Rain Thin Client: It is the Thin Client used by a student. TheThin Client is embedded with the operating system (OS), ClassManager_Student, and ClassManagerRainbow. The Thin Client is interconnected to the RCD Server through a 1000Mnetwork and displays the teaching desktop pushed by the RCD Server. Currently,there are various models of Thin Clients such as Rain100 and Rain200.

l  RG-ClassManager_Teacher: It is teaching management software used byteachers. It provides various functions such as course preparation, classinstruction, class discipline, class interaction, exercise guidance, and reviewand testing.

This document, based on typical case sets,describes operation steps and precautions of each functional module by scenarioin the implementation and configuration of the RCC solution. Network engineerscheck the hardware and software according to requirement information collectedprior to network deployment, and select appropriate network scenarios andproduct deployment modes that cater to the requirements. After the deployment,network engineers need to check the running of the device.

The deployment includes the following steps:

1.      Preparations before deployment

2.      Typical scenario selection

3.      Scenario and function selection

4.      Function configuration

5.      Function configuration commissioning

6.      Device running check after deployment

      Deployment Strategy (Required)

1.      Preparations (including network address planning)

2.      Installation and racking (including the racking of the RCD Servers,Rain Thin Clients, and switches and software installation)

3.      Software upgrade

4.      Software configuration and image creation

5.      Data synchronization (mandatory in cluster mode)

If youneed to upgrade the version that has been deployed in classrooms, back up dataof the RCD Server (mainly RCD data, including image files and database data).

Note:

1.      The RCD Server upgrade using an ISO file takes about 25–30 minutes.Please wait patiently.

2.      Because the hard disk controller of the Cloud Desktop is upgraded inV3.0, all images need to be edited using the Admin-Tool when the RCD Server isupgraded from an earlier version to V3.0. The Guest-Tool is automaticallyupgraded during image editing. You can normally use the images only after thenew hard disk driver is installed. You must restart the system to access thenew images and then install the Guest-Tool to validate the functions.

The following figure shows the procedure forupgrading the RCD Server to V3.0.

1.     If a customer uses the convergent computingfunction, communicate with the customer to obtain the software and then upgradethe version, and ensure that the upgrade time is sufficient (because thesoftware installed in the Rain system needs to be recovered).

2.      Generally, version rollback (rollback between major versions is notsupported) is performed when the upgrade is abnormal. Do not perform versionrollback in normal situations. Especially if you use the current version for along period of time, version rollback may cause anomalies to cooperativeproducts such as Rain.

3.     The entrances for image distribution vary withhardware architectures of the Rain Thin Clients. Simply, the Rain100 andRain200 adopt the x86 hardware architecture and use the Windows or Linux OS asthe underlying system. Therefore, they adopt the iPXE technical solution. TheRain100S adopts the ARM hardware architecture and uses the Android OS as theunderlying system. Therefore, the Rain100S adopts the OTA technical solution.

4.      You can select the multicast or unicast mode for image distributionby the iPXE and OTA according to the network conditions. If the networkcondition is good (1000M switch + 1000M network cable), the multicast mode isrecommended; if the network condition is poor or the multicast mode isunavailable, the unicast mode is recommended. If you have no idea of thenetwork condition, use the multicast mode.

5.     Authorization must be performed after the versionupgrade. Otherwise, the ClassManager Rainbow is valid for 45 days by default.Then, the software becomes unavailable upon expiration.

       Deployment Preparation

7.1       Information Collection

The RCC product relies on the infrastructureof the computer classrooms and the campus network. Therefore, before productdeployment, learn about the situation of the equipment room, cable layout inclassrooms, and network topology, to determine the project deployment schedule.

Single-classroom cluster deployment:

Multi-classroom cluster deployment:

Before product deployment, check whether thedevice list is complete. The following table lists devices and tools used inthe single-classroom deployment.

1.       Clarify customer requirements, and check thedevice list and software version.

2.       Determine the software used in current teachingand requirements for the version of the teaching software.

3.       Before deployment, confirm with teachers aboutthe list of software versions to be installed. It is recommended that thesoftware be provided by the customer. Help the customer learn how to create OSimages and install software.

4.       Get gigabit switches and Category 6 networkcables ready. Ensure that keyboard and mouse suites with USB ports areconfigured for Thin Clients.

5.       Check whether the customer uses teachingmanagement software such as Red Spider and Mythware. If the customer uses theRG-ClassManager, confirm the common functions used by the customer, such asscreen broadcast and document delivery.

6.       Get a separate PC ready for installing theRG-ClassManager.

7.2      Network Planning

7.2.1     Network Planning for the Cloud Class

1． Check theexisting network environment and IP address segment planning of the equipmentroom. It is recommended that an independent Class-C network segment beconfigured for each classroom.

2． Configure twoIP addresses for each Thin Client (one for Thin Client and one for CloudDesktop), two IP addresses for each RCD Server, and one IP address for eachClassManager_Teacher.

3． Clarify theplanned gateway, subnet mask, and DNS server of the school.

Network address policy: Cloud Desktop CampusNetwork and Thin Client Campus Network (This network address policy isrecommended. You can configure it on the configuration wizard of the RCD Servermanagement screen.)

For example, for a classroom containing 60Thin Clients, you can allocate network segment 192.168.1.0/24 (IPaddresses in this network segment can be used to directly access the network) to this classroom.

IP network segment forthe Rain Thin Client: 192.168.1.11–192.168.1.70

Virtual IP networksegment for the Cloud Desktop: 192.168.1.111–192.168.1.170

RCD Server: master IPaddress: 192.168.1.100; slave IP address: 192.168.1.101

ClassManager_Teacher: 192.168.1.10

Gateway IP address:192.168.1.1; mask: 255.255.255.0; DNS: 192.168.0.254 (subject to the actualconfigurations)

7.2.2     Deployment Planning for the Cloud Class

In local deployment mode, a single RCD6000supports 60 Thin Clients only in one classroom. If there are more than 60 ThinClients in one classroom, you need to configure additional RCD Servers.

In local stack mode, more Thin Clients can beconfigured in a single classroom and each Thin Client has higher performance.Currently, there are three models of RCD Servers: RCD3000, RCD4500, and RCD6000,which can be stacked together.

In cluster deployment mode, multiple RCDServers can be deployed in a cluster to serve multiple classrooms.

For example:

Scenario 1: Oneclassroom has 90 Thin Clients. You need to configure two RCD6000 Servers as acluster to work in active/standby mode, to satisfy teaching requirements.

Scenario 2: There aretwo classrooms and each classroom has 90 Thin Clients. You can configure threeRCD6000 servers in a centralized manner or set up two new classrooms.

Scenario3: A classroom can be deployed with 60 Thin Clients in the case of standardconfiguration. If high-performance virtual Cloud Desktops (2 GB memory) areused, one RCD6000 supports 30 Thin Clients at most. You can deploy two RCDServers in stack mode or cluster mode, to support 60 high-performance ThinClients.

      Deployment

7.1      Installation and Configuration

7.1.1     Installing the RCD Server

This topology is applicable to the newdeployment scenario of the RG-RCC solution and includes the RG-RCD Server,RG-ClassManager, and RG-Rain Thin Client.

1.      Deploy the RCD Server.

Key configuration points:set IP addresses, create Cloud Desktop, and configure the network mode.

2.      Deploy the Rain Thin Client.

Key configuration points:set an IP address for the Thin Client and distribute images in PXE mode.

3.      Deploy the teaching PC.

Key configuration points:install the RG-ClassManager and complete deployment in one-click mode.

4.      Manage courses.

Key configuration point:create images.

5.      Verify functions.

Keyverification points: start a class, end a class, broadcast the screen, andbroadcast a video.

7.1.2     Installing the ClassManager_Teacher PC

Minimum hardware configuration:

1.       ClassManager_Teacher PC:

-      CPU: dual-core processor at 2.0 GHz or higher

-      Memory: 2 GB or higher

-      Hard disk: 128 GB or higher

-      Accessories: display, mouse, and keyboard

2.       Thin Client

-      Accessories: Thin Clients supporting RuijieCloud Class, mouse, display, and keyboard

3.       Workspace server

The workspace is used for accountmanagement, class management and homework management. The workspace server canbe deployed on an RCD Server (recommended) or an independent server. After RCDV2.1 is installed, the workspace will be automatically installed.

Minimum configuration of the independentserver (for only one classroom)

-      CPU: dual-core processor at 2.0 GHz or higher

-      Memory: 2 GB or higher

-      NIC: 100 Mbit/s or higher

-      Hard disk: 256 GB or higher

Software configuration:

OS of the ClassManager_Teacher and ClassManager_Student:

   Note: The ClassManager_Teacher and ClassManager_Student providefull functions and support 32-bit and 64-bit OSs (64-bit images are supportedsince V2.1).

Keyconfiguration points:

1.      After installingthe ClassManager_Teacher on the teacher PC, authorize the software and installthe workspace server as required.

2.      If the voice broadcast function available in V3.0 is used, ensurethat the OS is Windows 7, Windows 10 Enterprise Edition, Windows 8, Vista, or ahigher version. Other OSs are not supported.

1.      By default, theClassManager_Teacher is integrated into the login page of the RCD Server. Youcan directly download and install the software.

2.      Click Licenseand read the license agreement of the software.

3.       Select I have read and accepted the licenseagreement and click Install.

Set IP addresses for the RCD Server andworkspace server, to ensure that the teacher PC can successfully connect to theRCD Server and workspace server. In addition, you can adopt the defaultinstallation path or click Change to select the required installationdirectory.

Note: if the workspace is deployed locally,no need to configure the workspace server in this step.

Note:

1)     If the deployment mode is Cloud Desktop Campus Networkand Thin Client Campus Network, the RCD Server IP is the LAN1 ip address, ifthe deployment mode is Cloud Desktop Campus Network andThin Client Private Network or Cloud Desktop Private Network and Thin ClientPrivate Network, the RCD Server IP address is the WAN ip address.

2)     The ClassManager and workspace can be usedindependently. Generally, the workspace server uses the RCD Server. In V2.1 andlater versions, after the ClassManager is installed, the workspace isautomatically installed. If the workspace is installed on an independentserver, you need to enter a correct IP address in System > Workspace> Parameter on the RCD Serverweb UI.

3)      In cluster mode, both the master and slave RCD Servers can providefunctions of the workspace server, depending on the RCD Server where theworkspace server is installed. The workspace server uses the IP address of theRCD Server where the workspace server is installed.

4.       After RCD Server IP is correctly set anda correct installation path is selected, click Next. The system startsto install the software. After the software is installed, the systemautomatically jumps to the finish screen.

5.       Finish.

6.      After the software is installed, some functions are available onlyafter the PC is restarted. As shown in the following figure, click Yes.You can normally use the ClassManager_Teacher after the PC is restarted.

Note: If the ClassManager_Teacher fails to scan Thin Clients after upgradebut can start or end a class, you can set the firewall to permit theClassManager_Teacher. Then, all functions become available.

Apply for an authorization file by referringto the Appendix "ClassManangerSoftware Authorization".

Log in to the RCD Server. Query and export the hardware SN, and makea license file in the back-end PA system (see 6.2.1      Generating the LicenseFile Using an Authorization Code below). Then, on the management page, click Importlicense to import the license file.

Ensure that the license file is successfullyimported.

Workspace is a component of the ClassManangerRainbow. It can be installed on an independent server or on an RCD Server. Ifthe workspace serves a large number of students (exceeding 200), it isrecommended that the workspace be installed on an independent server.

To install the workspace on the RCD Server,do as follows:

1.  Log in to the RCD Serveras an administrator. Note: In RCD V3.0 or later versions, the workspace isautomatically installed (the latest installation package is embedded into thenew version).

2.        Refresh the page and click Install.Note: To use the upload function, install the Admin-Tool first.

3.       After uploading the new upgrade package andclicking Refresh, click Install to install the workspace.

Note: please make sure the teacher PC canping RCD server LAN1 ip address before start the admin tool.

7.1.3     Installing the Thin Client

Unpack the chassis and connect the powercable, keyboard, mouse, display, and network cable. Ensure that all devices areconnected to a 1000M switch.

This section uses the Rain100 as an exampleto describe how to rack the RG-Rain Thin Client. The installation methods ofother Thin Clients are basically the same as the installation of the Rain100.For details, download the user manuals of related devices at Ruijie officialwebsite.

1.  Install the device base.

2.  Connect the power cable.

3.  Connect the display, keyboard, andmouse.

4.  Connect the network cable.

5.  Press the power button to start thedevice.

You can configure Rain Thin Clients in twomodes: configure them one by one or configure them in one-click mode (this modeis supported in V1.0.9 and later versions. For details, see "Typical Deployment Schemes – One-click Deployment").

The following describes how to configure theRain Thin Client one by one:

1.  Start the Rain ThinClient. The RCC logo page is displayed.

2.  The Rain Thin Clientfails to connect to the RCD Server at your first login because no networkinformation is configured.

3.  Click Configure inthe upper right corner to access the configuration page.

Set the parameters as follows:

l  The default password for accessing the configuration page isruijie.com.

l  Generally, you do not need to modify the PC name. If you change thePC name, you need to restart the Thin Client.

l  RCD Server IP is the master IP addressof the RCD Server.

l  Click Obtain an IP address automatically or configure astatic IP address as the IP address of the Thin Client.

l  Note: If the switch is a NMS-type switch and the DHCP networksegment has been configured for the RCD Server, it is recommended to click Obtainan IP address automatically. For a non-NMS-type switch, it is recommendedto set a static IP address for the Thin Client. Otherwise, IP addressesallocated to Thin Clients in multiple classrooms may be disordered.

4.  After the configurationis complete, connect the Thin Client to the RCD Server. If a course isavailable, a page as shown in the following figure is displayed:

7.1.4      Installing Images

By default, there is no available image inthe RCD Server. Generally, you need to create images by using the ISOinstallation CD-ROM of the OS and the SN.

You can also directly access the image page.

Before installing images, ensure that thefollowing operations are completed:

1.       Install the Admin-Tool (download the softwarefrom the image page at your initial use, install the software, exit thebrowser, and log in to the system again).

2.       Obtain the OS ISO CD-ROM (Windows, CentOS/Ubuntu)for image creation or obtain Ruijie demo images (The demo images are in thebase format and must be deleted within 24 hours after download).

3.       Enter share directory D disk, obtain theClassManager_Student (install it on the Cloud Desktop image).

4.       Obtain various types of professional software tobe installed in images (such as Office and Photoshop).

Note: Currently, Supported image systems include Windows XP,Windows 7, Windows 8, Windows 10, Windows 2003/2008/2012/Vista (Windows 8 is not recommended becauseit does not support the redirection function).

The RCD server and supports32-bit and 64-bit OSs (the RCD supports 64-bit images since V2.1).

Key installation steps:

1.   Uploadthe OS ISO image file (such as win7EnterpriseX64cn.iso) to the image directoryon the RCD Server.

2.       Create an image and setthe parameters.

3.       Completely install the OS.

4.       Install the RCC-Guest Toolto ensure that the Cloud Desktop driver is correctly identified.

5.       Install theClassManager_Student and various types of professional software.

6.       Power off the device.Then, the image is created completely

Note: Because the hard disk controller of the CloudDesktop is upgraded in V3.0, all images need to be edited using the Admin-Toolwhen the RCD Server is upgraded from an earlier version to V3.0. The Guest-Toolis automatically upgraded during image editing. You can normally use the imagesonly after the new hard disk driver is installed. You must restart the systemto access the new images and then install the Guest-Tool to validate thefunctions.

To create an image, do as follows: