Ok, so I've been trying to solve this issue since starting with my first Android phone, the Hero...
I work for a large enterprise corporation & our security policies are quite strict. I have used Blackberries, Palm Pre, WinMo all successfully with my employer, but Android just does not work! Ok, yes, I've been using TouchDown & it kind of works, but only with Exchange 2003 support running, ActiveSync will not connect.
I know our policies require simple PIN & remote device wipe, so is that what is blocking me from using the built in client? I read somewhere that someone has some sort of patch they applied that tricks Exchange into thinking it is a different type of device trying for ActiveSync & bypasses the simple PIN & remote wipe. Has anyone heard of anything like this?
Any guidance would be so very appreciated! Thank you!
Check reply to your post on Android forums ... I'd put the link in but am prevented ...
Related
I have followed the Blackberry-related threads, but a couple of questions remain. Forgive me if I missed an answer that's already posted.
First, I'm using the PDA2K with a Cingular SIM. I have the the "unlimited PDA data" plan, which a Cingular data support technician tells me should qualify me for Blackberry service. In fact, I used that plan when I had a Blackberry 7290 through Cingular before I got the i-Mate device.
I installed the O2 version of the Pocket PC Blackberry client software- with no problem (even though after the install a message appeared telling me that the client software might not display properly because it was meant for an earlier device).
Question 1: When the Blackberry client is running on the Pocket PC, the handheld won't sync with ActiveSync. Is this to be expected?
Question 2: My company's BES redirector software on my desktop doesn't see my Pocket PC even when the Blackberry client software is running on the handheld, the handheld's in its cradle and the cradle's connected via the USB port to my desktop. Is this because of some conflict with ActiveSync perhaps?
Question 3: In checking the settings on the Blackberyy client software on my handhled, I see no PIN #. Is this because Cingular's ROM doesn't serve up a PIN # for the device - because, in turn, Cingularl doesn't support Blackberry connect software? I take it there's no other way to load my old Blackberry PIN # (from my Blackberry 7290 days - it's still "alive" on the Cingular Blackberry website) short of through a ROM update of some sort?
Many thanks.
Charlie
We are in the same exact boat except for i am on AT&T. I tried the O2 version and had the same problem. That is because the PIN on blackberry devices are harcoded into the device it self and the PIN from blackberry connect is generated by the software(most likely in association with IMEI, which is the truly globally unique ID for mobile devices). Then I installed the .CAB file extracted from the German T-Mobile III(same device as ours) and the desktop software. Except for the Connect software on the device is in German, there is no problem. The software generated PIN when I opened it, and talkes to the desktop, so the BES side also get the new PIN. Seems like evrything should be working now but no--I think the blackberry APN and IP need to be changed from the BB Connect settings but I don't know how, since those are carried over from the German T-Mobile settings. I will try to contact German T-Mobile to see if T-Mobile US supports it or not, if yes, I will switch.
I know of Blackberry, but I never heard about a client on the PocketPC. I currently have the $19.99 Media Works Unlimited plan, can I use that application as well? What benefits would I have in using it? If I could use it, where can I download it? Thanks.
Hi I'm using the JasJar/Universal and I am trying to figure out how to disable the use of certificates when navigating to certain sites on PIE (I get an error code). I am 99.98% the problem is with the certificates and how IE uses them because when I installed Opera for SmartPhones 2003, I could access the sites with no problem. Also my old hp iPaq 4155 (running WM2003) was able to navigate to them without any problem either. Does anyone know how to disable certificates in WM5.0? I've tried to use the DisableChkCert from Microsoft's website, but that's only good for WM2003 products. Any guidance would be GREATLY appreciated. Thanks
Dear All
Please help: I have an O2 XDA IIs which MS Activesync 4.1 does not detect, despite all my efforts during the last few days (I also have an old iPAQ 1940 which Activesync detects fine).
The XDA is from work, so could it be that it is somehow locked, and if so, how can I unlock it?
Also, as an alternative, can I sync the XDA with my PC via Bluetooth through the iPAQ's?
Any ideas will be gratefully received!
Many thanks in advance,
L
Hi there,
I've Looked through hundreds of forums and although I have seem similiar I haven't found a resolution to my exact problem.
Due to the fact that I've been trying to resolve this issue on and off all day it's probably something really simple... :roll:
HISTORY
PDA
Was running WM2003SE on a Xda IIS.
PC
ActiveSync 3.8 on Laptop with Windows 2000 SP4 and all updates. Laptop on a home LAN with router. No firewall software and have since removed all Spyware removal software, (after doing one last scan).
My Task \ Issue \ Problem
I wanted to to the upgrade to WM2005 and followed all the usual procedures. The one mistake I may have made was to install the very very latest 4.1 Activesync without removing 3.8. However at this stage my XDA was still on 2003SE and synced perfectly with 4.1 Activesync.
I performed the upgrade to WM2005 including patches and as far as the XDA is concerned everything appears to be working.
Activesync however doesn't work. Via the USB cradle Windows 2000 detected a device and under device properties it's was listed as Generic RNDIS, it's now listed as a windows mobile based-device. I don't have an entry in my network connections, although I think this only happens with Windows XP. I've tried uninstalling Activesync, removing the rapi.dll file, reinstalling etc, I even did the former and removed entries within the registry and running a registry fixer but to no avail.
I then decided the Bluetooth route but cannot sync via this method either. I can actually succesfully connect from PC to XDA and vice versa but cannot use these connections for Activesync.
I have another Hard Drive for this Laptop which I use for testing. I can simply shut down, swap drives and boot again to another build. The other build is also Windows 2000 with SP4 and pretty much nothing else. I've installed Activesync 4.1 onto this machine, plugged in the cradle and everything works fine.
So..... I know the XDA is fine, The cradle's okay and Activesync 4.1 actually works with my XDA OS. The problem is it doesn't work on one particular build. I believe this is actually a Activesync issue but due to some form of conflict with my build. It's currently out of the question for me to rebuild so my mission is to find out what's conflicting.
Just to summarise though..... Activesync 4.1 was working fine, I upgraded XDA to WM2003 to WM2005 and then it stopped. The other harddisk proves that Activesync does actually work with my XDA.
Pheeeew...... I hope somebody doesn't suggest lack of information.... :lol: :lol:
So the reason for the post?? Well if anybody else is having frustrations, (which I'm sure I'm not the only one judging my my searching), your not alone.
I think a lot of people's problems have actually been resolved by the latest version of Activesync, (4.1), and other people have resolved by sorting out the main culprit of firewalls.
For me though I'll keep searching..... if any of you can think of any other ideas I can use for diagnosing the problem I'll appreciate it.
Thanks in advance..... sorry for the waffle.....
RESOLVED
Okay.... During further searching I noticed people mentioning VPN clients interfering.
I did have SecureRemote VPN installed which I use for work purposes.
I uninstalled SecureRemote but had to uninstall & re-install Activesync again. This time it's working.....
I will, (but not tonight), re-install the VPN client and see what happens. If Activesync countinues to work then, apart from being happy, it's worth making a note of.
If it doesn't work then I'll start to investigate why...... I know the new active sync does some form of IP connection but I cannot accept that it won't work with VPN's installed.
use windows XP (SP2) ...
first install the activesyn and then restart your computer.
then attach your pocket pc with usb cable.
and try to connect.
its works for me...
Please forgive me if this was already addressed at some other point. I searched, but could not find the answers I needed. I found the BlackBerry Connect software (after a while on the forums) and installed it on my BA. The software runs, generates a PIN, etc...
Right now, I do not have BB service on my plan, and I am wondering - will this client only work on BB Exchange Connector, or will BB Web Connect work also? I want to make sure I get the service that best suits my needs...
If a PIN is generated w/o sync, do I still need to sync it w/ BB software on a Win PC? I use *nix and that would be inconvinent to say the least...
Also... How the hell do you uninstall BB software if you decide not to use it? There is no entry in the remove programs app...
Thanks!
Does anybody have any practical experience with this peice of software for other than BES connectivity?
Does anybody know if this can be used for PIN messages or other Blackberry push services?
Anyone know of a way to get a pda phone such as an i-mate ultimate 9502 to pretend to be a smartphone?
We have corporate email at work which needs an initial setup - which works fine with smartphones ( used to use a blackjack i600). would like to use my ultimate 9502 instead but the setup fails.. am thinking that this is due to the phone being more than a smartphone.
any ideas, anyone?
My problems appear to be caused by the applications that the ultimate 9502 auto insytalls after a hard reset. Is anyone familiar with a way of preventing or delaying this autoinstall? I have upgraded the 9502 to the new windows mobile 6.1 thinking that this may resolve the problem.