The Microsoft “certutil” command line tool is included in Windows 7*, and in Windows Server 2008 R2. For vSpace 6.6.2.3 and above, use the file labeled 'NC-code-signing-vSpace 6.zip' for vSpace 8.4 and above use NC-Code-Signing-vSpace8.zip from the file NC-code-signing-vSpace_certs attachment. Article: 303.

Hi John We are seeing the exact same error after committing to install NComputings M300 product in 3 separate schools. Massively frustrating as we have another prospective school who are interested in this technology and are going to be given a demo of Multipoint working with the M300's in one of the schools who are seeing this problem. Whatsapp sniffer download no root 7.

In all 3 schools, we see this message. Are you running WMPS 2011? If so, have you tried increasing the timeout for the login screen refresh?

There is a registry key setting for this which stops the login screen from cycling. By default, this refresh takes place every 30 seconds I think. Setting this to something like 18,000,000 seconds does circumvent this to some exatent, however it hasn't resolved the problem fully as we still see this 'Unknown Error' from time to time, sometimes on as many as 2 out of the 3 stations per M300 Kit. This registry key is detailed in the release notes for the latest version of vSpace.

Ati mobility radeon hd 5650 drajver windows 7. AMD and ATI drivers for Microsoft Windows. AMD/ATI Mobility Radeon HD 5650: 39378× AMD/ATI Mobility Radeon HD 5470: 34977×. Auto-Detect and Install Radeon™ Graphics Drivers for Windows© For Radeon™ Graphics and Processors with Radeon™ Graphics Only. For use with systems running Microsoft® Windows 7 or 10 AND equipped with AMD Radeon™ discrete desktop graphics, mobile graphics, or AMD processors with Radeon graphics.

I sincerely hope that this is resolved in the next vSpace / firmware release. Too often we see products that promise to deliver, however fail through a rush to get them to market without thorough testing.

Good luck, best regards and let me know how you get on. Hi Matthew, Thanks you for the reply. I have just sent Ncomputing another support request asking them for a date when this problem will be fixed. I have the latest firmware but Ncomputing support told me that this would not stops the 'Unknown Error' problem so they are fully aware of it. I have not increased the timeout yet. Could you post the details on here with a little more information on how to enter the keys. I'm sure it would be useful to a number of other people.

I will let you know what Ncomputing says about a fix. Regards, John. Hi John I certainly can. First, take a look at page 6 in the release notes for. Read the section at the top of the page titled 'Windows Multipoint Server 2011'. You will see that there is a reference to the login screen refresh timeout there.

This involves making changes to the registry manually, so follow all the usual precautions before hand (make a backup of the registry in its current state / test on a machine that isn't important first). Open the registry editor 2. Browse to HKLM System CurrentControlSet Control TerminalServer WinStations 3. You will see that the key 'RDP-Tcp' that is referenced in the release notes doesn't exist. Go ahead and create this. Under this new key, create the following DWORD: LogonTimeout, Value: 18000000 (Decimal).

Once done, restart the host machine. You should now find that the login screen will no longer refresh every 30 seconds. We found that the 30 second timeout was causing the stations to drop like flies with this 'Unknown Error' message. It seems as though it is at the login screen where this issues occurs, nowhere else. At least with this lengthly timeout in place, the stations have a good chance of remaining in a useable state for a longer period of time. What this doesn't do however is fully resolve the problem. You will probably find that when a user logs a session off, you may see the 'Unknown Error' once the station returns to the login screen. This can happen very intermittently.

My theory is that during the logoff process, the stations briefly disconnect from the host, then re-establish the connection. It is at this point where this message will appear. Hopefully this will get you out of trouble for the time being. If we can't get a good enough answer out of NComputing as to when a fix will be implemented, we will be looking for a refund. I find it simply unacceptable that a product can be shipped with a 'known issue' as serious as this.