Before i begin let me inform you that I've already gone through other threads here regarding the same issue, none of them seems to have helped, therefore creating my own.
The issue started recently, by the very least i think it started happening 3 weeks ago. we have a custom build application that is deployed on our Network share, the exe is lightweight program, nothing too heavy.
The EXE can be ran manually or through our a shortcut but doesn't run either ways, a window about the same size as the app pops up and disappears immediately if you constantly double click on the exe.
All our Client computers are Windows 10 1909 build. All our servers are VMs running on a Hyper-V host and Windows Server 2019 latest version as well. only the Hyper-V Host is Server 2016 and the application runs fine on that server only.
Infact all other EXEs can be opened through the network share (not on the same server but on a VM) on that 2016 host but none of the exe's open on any other client computer or VM's.
The respective GPO to trust UNC paths is enabled and applied, there are no errors or warning whatsoever when launching any of the exe's, the files just don't open no matter how many times you click on it.
Any Ideas?
Azure offers a pre-installed Windows Server 2016 DataCenter, but so far I wasn't able to activate remote audio recording on this machine.
All guides I found say that the "Desktop experience" feature has to be installed, but there is no such feature in the Server 2016 feature list.
The Windows audio service is running, audio recording is being configured inside the .rdp file, but I only get Remoteaudio playback.
What do I have to do to activate remoteaudio recording on this machine?
TIA
I just got my problem resolved with the help of Microsoft Azure support.
The .rdp file you can download from Azure when you try to connect to the virtual machine contains the setting
administrative session:i:1
This is equivalent to calling mstsc with the /admin switch.
In this mode, the microphone is not being mapped.
After changing the 1 to 0, microphone redirection worked immediately.
So for reference purpose here are the complete requirements you need to get audio recording inside an RDP session:
Remote Desktop Session Host role is installed
On a server < 2016, the Desktop Experience feature is installed. Windows Server 2016 already contains this feature (unless you have a core installation, of course)
You're either still inside the grace period OR have the Remote Desktop Licensing role installed and a valid CAL
The remote desktop group policy allows audio recording
The .rdp file contains audiocapturemode:i:1 ("Record audio from this machine" is checked)
The RDP session has NOT been started as an admin session (using /admin or the administrative session:i:1 entry)
With these settings, audio playback and recording should work inside an RDP session.
I am interested in downloading the Internet Explorer on my SUSE-linux server which is telnet'd from my local linux machine.
I need to install the Wireshark and SNMP browsing tools on the server and would like to therefore have an internet explorer installed on the server.
Please help me with the installation.
Internet Exploder only runs on Windows machines. You might be wanting to install all of this on a Windows Server and then run these tools against a Linux machine, but you're not going to natively be successful loading IE on a Linux Server.
There is an option that I'll mention you can check out Crossover Office from Codeweavers, it's got the ability to run the appropriate WINE drivers and environment so that you could do what you are asking, but there is no guarantee that the overall scheme of running Wireshark will work.
I am trying to install Remote Tools on a Surface RT running Windows 8.1 preview. I downloaded update 2 of remote tools from Microsoft's site and when I try to run it I get the error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
This is confusing because I downloaded the file directly from MS website and when I look at the .exe properties it says digital signatures by Microsoft Corporation.
Any insight would be greatly appreciated.
Thanks!
Update: It seems like my Microsoft Root Authority certificate is "not valid for the selected purposes" I've tried exporting a "good" certificate from another machine and importing it into the Surface machine but it still gives the same issue.
This is because your downloading the 2012 tools. You can download the 2013 preview tools here at the following link! (Be sure to choose ARM)
http://www.microsoft.com/en-us/download/details.aspx?id=40781
Would have been nice if Microsoft had given us a heads up.
Also, when I go to the 2013 download on my Surface RT running 8.1 preview, and I click on Download, no matter which option I pick (x86, x64, or ARM) it downloads the x86 version, which obviously won't work. I had to download it on a PC and copy it over using a USB drive.
This problem exists on the released version of 8.1 too.
If you previously had the vs2012 tools installed, they appear to be uninstalled during the upgrade.
Attempting to reinstall gives the above error.
That means, it's now impossible to connect to the 8.1 Surface RT from VS2012 Pro to debug an 8.0 app running on 8.1. Instead, you need to connect with the VS2013 tools and remote debugger.
For anyone who is just trying to test their App updates a surface device running Windows 8.1 RTM, I have at least found a workaround.
You can manually deploy your package to your device by coping the package content to a USB memory stick and running a already defined powershell deployment script.
Basically you need to run the normal package creation process you would do to deploy to the app store to create a package, then copy the contents of the package folder (Not the compress package itself) to your USB stick. There should be a file named Add-AppDevPackage.ps1 in this folder.
Open your USB device from your Surface RT system, right click the Add-AppDevPackage.ps1 file and select "Run with powershell". You will receive several confirmation prompts at the command line and a popup window prompting you to run with admin privileges.
This is by no means a convenient or speedy process but it worked for my purposes.
This link has more detailed information on manually deploying your app package.
I am trying to find out a tool to remote control a Motorola MC3190 device running Windows CE 6.0 from a Windows 7 machine.
I have already used Mymobiler with Intermec CN3 device so I tried the answers in this question but I am unable to get it to work.
I have tried both remote.exe.40 and remote.exe.50 in the Mymobiler folder
Using Task Manager on CodeProject mentioned in a question on superuser it seems remote.exe completes execution very quickly (or is crashing silently).
My Start/Programs menu has a MyMobiler entry, so somewhere along the line something seems to have got installed
But when I run Mymobiler on desktop it cannot connect, its icon in system trey remains gray and on mouse hover says Not Connected/
In Proof MyMobiler works for WinCE video the processor is ARM920T-PXA270M while my device has a Marevell, PXA32X-P (link to image) processor could that be the reason?
I have also tried ActiveSync Remote Display from Windows Mobile Developer Power Toys. It installs but at start up it shows an error box with message "The OS or CPU of this device is unknown to this application"
How do I get MyMobiler to work with Motorola MC3190 device running Windows CE 6.0?
Is there any other tool, preferably free, to remote control this device?
EDIT: I came across EveryWAN and found an installer. It works out of box, but it is not available for commercial use and the web-site seems defunct.
PS: I realize the tags are not accurate but I wanted to use something that will attract attention of experts in these similar tags.
I want to clarify one answer to the above which is correct. When using the Microsoft PowerToy activesync remote display, there must be an application on both sides - host(the phone) and remote (the pc). The same is true for MyMobiler.
Install the powertoy on the pc.
For the original Poster: This is what your error message means:
In the case of Activecync Remote display, for newer devices (anything above ARM4 cpus - which means, 2008 and up, or over 200mhz cpus - as a very general guide), the display software cannot detect what type of device you have (it's too new, and not in the list).
For the motorola mc3190, your cpu is arm5 compatible,
and should work with software that has arm4 compliant components. ARD does have arm 4 options. see here...
To Fix it:
You must use file explorer on your pc, and navigate into the application folder: c\Programs...\Windows Mobile Developer...\ActiveSync...\Devices\wce400\armv4t and copy the two files.
While still on the pc, you must then navigate to the Windows folder of the device (with activesync running, OR the phone configured to be seen as a hard disc), use explorer on the PC to navigate to the device.
Vaguely, it will look like this:
Explorer. > Device (such as HTC Phone:)
Or, X:\ , where x is a drive letter.
The first subfolder your select should be Windows. Paste the two files there.
The two files are now copied onto the phone.
At that point, you must, using the phone, load it's file explorer and navigate to that Windows folder on internal memory and manually run cerdisp2.exe that you have now copied there.
With activesync running, and the phone connected to the pc,
You can now run the powertoy active remote display on the pc, and it will communicate with the exe that is running on the phone.
ActiveSync on Xp, or Windows Mobile Device Center on Windows Vista/7/8 must be running for this all to work.
Alternately, the app allows for a networking ip connection instead of activesync, but I have not used it.
When you are done using this app, you must run the kill.exe on the phone, in the windows folder (the second file you copied), to unload the dll that is running.
I can verify this setup works on Xp, Win7 and Win8 - with an Xscale ARM11 528mhz cpu phone.
For MyMobiler, visit their site and get the newest version.
It WILL fix connections that fail, if you have the older version. It's free. They don't support it anymore.
My Mobiler must have activesync running and showing the device connected.
My Mobiler is vastly superior to ActiveSyncRD.
* It will automatically install the pc side app, and push the remote app to the phone, via activesync.
*Further, when activesync is running and anytime you connect the phone, the MyMobiler app will autoload on the phone as well.
That way, whenever you run MyMobiler on the desktop, it will connect to the phone and load right up.
*My Mobiler allows full resolution display, while ARD is limited to 320x400 or similar. 640x800 looks much better.
*MyMobiler also allows full mouse gesture sends, and copy and paste. ARD offers very limited mouse gesture compatability.
MyMobiler also allows IP connections, but they indicate this is slower.
I am now using MyMobiler with Win8 and a touchpad w/ multitouch, and the mouse gestures send very well.
For Windows V/7/8, you might need to run compatability mode on the Mymobiler.exe file. Navigate to the MyMobiler folder, which might be on your desktop. Drill down til you find the exe. Right Click and chose properties. Compatability. Run Compatability Mode for this file, and select XP.
More Notes:
These apps are slow, because USB is slow.
If you enable Fast USB on the phone, it will help speed up any Remote Display noticeably - however Fast USB is unstable, and doesnt work on some configurations. For me, it doesnt work on XP, but does on Win8 - though slightly unstable at times.
On the device: Start> Settings Icon>Connections icon >USB to PC icon. Tick box to enable.
Also, MyMobiler on Win8 will sometimes refuse to connect. Fully unload mymobiler, disconnect the phone, reconnect the phone and watch for activesync to confirm connection. Then reload mymobiler. Sometimes full system reboots are needed, but that's rare.
Windows Mobile Remote Controller app on CodeProject - as linked above, looks excellent. It's for Windows Mobile 7 and 8 - which is fantastic. He provides a rapi enabler to allow use with WinMo 6 / 6.5 devices, which also looks promising.
I've never used MyMobiler, so I can't help there, but how about other options?
Did you look at the Windows Mobile Remote Controller app on CodeProject?
I've had good luck in the past with SOTI's Pocket Controller. It once was free, or had a free version anyway. Not sure if they still do.
Windows CE came with a tool called CERDISP (short for CE Remote Display), which could be built with Platform Builder. I've seen it available as a binary download (like here, for example) on the web before, so no need to actually build it yourself.
I've used MyMobiler (remote.exe.50) on my Windows Mobile 6.5 handheld. It sounds like you got it running. Did you run the MyMobiler client on your Windows 7 box and connect to your handheld by IP address? (Right click on the icon in the Notification Area on Windows 7 and choose "Connect IP...".)
It defaults to the ActiveSync address (169.254.2.1?), so if you're not docked and running ActiveSync, it will fail to connect initially (but manually connecting should work). Misread -- you were able to run the client, but not the server.
You can also elect to run a VNC server on your handheld and use a regular VNC client to connect to it. I've built this one for Windows Mobile 2003 without much of a hitch on Visual Studio 2008. You might have similar luck with Windows Mobile 6.5.
EDIT: If you get the message that reads:
'%s' is not a valid Pocket PC application.
when running the MyMobiler client, then that means that your CPU type (or OS) is incompatible with the application -- so I don't think your PXA32X-P is to blame; especially since the MC3190 appears to be able to run Windows Mobile 6.5 (i.e. the CPU should be "fairly" modern, with support for armv4i). But since you haven't mentioned an error that looks like that, I'd suspect that your build of Windows CE 6.0 doesn't contain all the required dependencies.
The first thing I'd check is if all of the dependencies of MyMobiler are present in your build of Windows CE 6. Windows CE is highly customizable; as such, not all software components will be the same across different builds of Windows CE. MyMobiler is built targeting Windows Mobile, not Windows CE, so there's a good chance that your build of Windows CE on the MC3190 doesn't have what's required, while the video you linked does.
With regards to the ActiveSync Remote Display Power Toy, the message that you received sounds like the desktop application didn't know what version to deploy to your device.
Per readme.txt in the ActiveSync Remote Display package:
If you see error message "The OS or CPU of this device is unknown to
this application", it usually means the CPU type of the current
device, typically a Windows CE device, is not recognized by this tool.
The workaround is
1. Find the CPU type of the device (from the manual or the manufacturer).
2. Copy \Devices\wce400\\cerdisp2.exe to the \windows folder of the device.
3. Run "cerhost2.exe -m" on the desktop/laptop.
4. Run cerdisp2.exe on the device.
5. When the remote display is no longer needed, terminate cerdisp2.exe on the device.
You should be able to choose the armv4t version; if not, use the armv4 version.