After the package finishes expanding, it wills start activesync and will download to your device. For everyone who wants to install onto their windows mobile/pocket pc device - after you download the all processors package, you'll need to run it on a pc that has activesync. You just can't run the client installer from citrix as you will need to flash the firmware of your term. There are a couple of issues here: for everyone who wants to install onto a winterm - you will need to contact the maker of your hardware for a updated client. After all, it looks like the only thing to be changed is the version information in the other cabfiles, but that's something to be done by Citrix, you cannot do anything about it. So why does ActiveSync choose the x86-package instead of the one suitable for your processor? Strange thing again, the x86-cabfile is the only one that is set up to be compatible to ce 5.0, all the others will not even install on ce versions greater than 4.2. Hi Tommy, that's because for some reason you will get the x86-Client installed when using the ActiveSync installation procedure. com) tomtom 7, igo 8, sygic 10, miomap - Duration: 8:55. Medion PNA (150 200 220 240 250) con GPSPRO II (Data Recovery Pro License Keygen. >I installed the 'All processors'-package for windows >ce (.) >But when I try to start the ICA client on the windows >CE 5.0 terminal, i get the error message: >'ceicamgr' is not a valid Windows CE application.' If you can't wait, I suggest you firt run your tests using the device emulator you can get from the MSDN web site. In regards of the two above items, I would suggest that you wait until deploying the ICA client on Windows mobile 2005 devices. It's also impossible to uninstall: I had to clear the system memory to get my device back. However, the client itself is extremely unstable and it will randomly crash during usage but also when you're NOT using it. 2/ once installed, the client allowed me to connect to my server via the web interface (that's the only thing I tried). I'm no guru of Windows CE (yet) so I don't know how to fiy it beyond repackaging the application after signing it yourself and adding your root key to the device's CA. If that's the case, then it's possible your device is setup to silently reject all unsigned code. However, I suspect that this behavior is configurable, like in windows. Now, in my case, all this required was to click 'Ok' when installing the CAB and when first running the application. Since the ICA client and ICA installer aren't signed, they won't run unless the user accepts this. 1/ Apparently, MS has added code signing to the system which means that, by default, application do not run unless they are authorized. Ok, I just bought a Qtek 9100 smartphomne with windows mobile 2005 and installed the ICA client on it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |