With Arduino being an open-source electronics platform, their PCB designs freely available which means it is possible to get a generic Arduino board for much less than the branded boards.
Like when I purchased a 4WD chassis. Which also came with an unbranded Arduino UNO SMD. What’s the difference with Arduino UNO SMD?
The Arduino UNO SMD, uses a surface mount version of the ATmega328P instead of the though hole version.
But I noticed when I came to use the board that I wasn’t able to communicate with the board via the Arduino IDE.
When I opened Device manager to double-check I was connecting using the correct COM port, it became clear that there was a missing driver as it was showing as “USB Serial”.
For any missing drivers that Windows isn’t able to automatically find and install, and it isn’t clear where to get the drivers from as this was an unbranded board.
The first step is to find the Hardware IDs of the device by right-clicking on the device > Details and Selecting Hardware IDs. In this instance I could search for the Hardware ID and see that it was for a “CH340 Serial to USB Adapter” which had the Hardware ID “USB\VID_1A86&PID_7523”.
It turns out it is very common for the generic Arduino UNO SMD’s to require this driver. For convenience please see below for a download of the driver.
To install this driver, right-click on the missing device and select “update driver”. Then select “browse my computer for drivers” and select the folder where you have downloaded and extracted the above download.
Once installation is complete the device is ready to use.
Please get in touch if you have any comments or suggestions via email: [email protected]
The HTML 5 Remote Desktop Web-Client is available for Windows Server 2016/2019 that is configured as a Remote Desktop Services Deployment at no additional cost.
This allows for devices with a modern web browser to access an RDS server without having to use any additional apps. Which is a perfect solution for Mac and Chrome Book users as it will allow them to use the deployment without needing to install the Microsoft RDP App.
Prior to installation of the HTML 5 Web-Client, please ensure that the RDS infrastructure meets the requirements below:
RDS deployment has an RD Gateway, RD Connection Broker, and RD Web Access roles are installed on Windows Server 2016 or later.
RDS licensing must be configured for per-user client access licenses rather than per-device.
Ensure the RDS Deployment servers have the latest Windows updates installed.
RDS deployment must have valid SSL certificates issued by a trusted CA on the server containing the Gateway and Web Access roles. (Self-signed certificates do not work!)
Before starting the installation, we need to export the SSL certificate that is used by the RD Web Access role.
Launch MMC as an administrator and add the certificates “Snap-In” and select “Computer Account” as shown below.
2. Once the Snap-In has loaded, navigate to > Certificates > Personal > Certificates.
3. On the valid certificate that is used for the Web Access role, right-click and select All Tasks > Export.
4. Export the certificate using the following options: Select the format you want to use > “DER Encoded Binary X.509 (*.cer)” File Name > Save in an easy to reference location i.e. C:\Temp\webaccesscert.cer
Now that we have exported the certificate as a .cer file, we can begin the installation of the HTML 5 Web-Client.
1. Open a Powershell console as Administrator (Right-click run as Administrator) and run the command:
Install-Module -Name PowerShellGet –Force
2. Restart your Powershell console for this to take effect. (Close the console and re-launch it as Administrator and run the command:
Install-Module -Name RDWebClientManagement
4. Run the command below which will download and install the latest version of the Remote Desktop Web-Client.
5. Using the certificate we exported earlier, run the command below and include the full path and name of the certificate.
Import-RDWebClientBrokerCert "C:\Temp\<Path to file>.cer"
6. Now that the client has be installed, run the command below to publish the client.
Publish-RDWebClientPackage -Type Production –Latest
7. The HTML 5 Web-Client is now accessible by using the URL below.
8. This step is completely optional however, for ease of use for the end-user you can configure IIS to redirect users to the HTML 5 Web-Client.
Launch IIS Managnger on the server that has the RD Web Access role installed and select Sites > Default Website. Once selected then select the “HTTP Redirect” option located under the IIS Section.
Once selected, configure the HTTP Redictet using the options below:
Enable the option for “Redirect requests to this destination” In the destination field enter the following URL: https://<Your FQDN>/RDWeb/webclient/index.html Enable the option for “Redirect all requests to exact destination”
Once the options have been saved you can test the redirect is working as expected by navigating to your FQDN. You should then be presented with the HTML5 Web-Client and the installation is completed.