Apache WM6 Kitchen CE OS 5.2.1908 (Build 18508.0.7.0) 071117_1 Bugs/Patches

[jsavin]

Originally Posted by ajgalbraith98

Special thanks to jsavin

Glad I could help, and awesome job on the OEM -- about to test it out here...

Just to check though on putting the registration key into the registry -- The value of "Application" is different on my PPC, using Pocket Plus 4.0.1. You said:

"Application"=dword:a9401b68

But I've got:

"Application"=dword:a938e898

It's just a guess, but it may be the case that the value of Application actually comes from some calculation based on Owner Info, and that your registration code will only work with the correct value here as well.

Not sure if it makes any difference though. FWIW, I'm going to test using my value instead of the one in your post. I'll post here again if I run into any problems.

Cheers, and thanks again!
-Jake

[ajgalbraith98]

Originally Posted by jsavin

Glad I could help, and awesome job on the OEM -- about to test it out here...

Just to check though on putting the registration key into the registry -- The value of "Application" is different on my PPC, using Pocket Plus 4.0.1. You said:

"Application"=dword:a9401b68

But I've got:

"Application"=dword:a938e898

It's just a guess, but it may be the case that the value of Application actually comes from some calculation based on Owner Info, and that your registration code will only work with the correct value here as well.

Not sure if it makes any difference though. FWIW, I'm going to test using my value instead of the one in your post. I'll post here again if I run into any problems.

Cheers, and thanks again!
-Jake

You are probably right, I use the same Owner on my wife's and mine phone for that kind of issue, also i notice if I left that in the OEM the trial expired immediately so it could be a date code also... It has been SO long since I origianlly purchased SPB plus that I can't rememember if they asked for Owner field.

I guess to be sure one would have to quickly bake with my OEM, then Install from cab, register, then record what they found at that registry setting, then add that info to their RGU and bake again. Luckily for me I have that hahahaha....

--ajgalbraith98

[obsidian440]

I want to say thanks to everyone who worked on the wm6 upgrade and the kitchen, I really appreciate your work in bringing this update to those of us who love our phones but our carriers don't.

That said, I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.

To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone. Any ideas ? Are there any new registry tweaks that can be done ?
Or is this just a case of having a self-signed cert and I should buckled down and buy a real one ?

[PRSPower]

Originally Posted by obsidian440

I want to say thanks to everyone who worked on the wm6 upgrade and the kitchen, I really appreciate your work in bringing this update to those of us who love our phones but our carriers don't.

That said, I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.

To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone. Any ideas ? Are there any new registry tweaks that can be done ?
Or is this just a case of having a self-signed cert and I should buckled down and buy a real one ?

I previously used a self signed cert on my exchange box, and ran into all sorts of head aches. I am not sure how to fix the problem you are having, but I can tell you that GoDaddy's $20 per year SSL cert is the best $20 you could ever spend. Especially if you are supporting multiple people using WM5 or WM6 with direct push. I have users that are using Motorola Q's and self-signed certs are terrible when trying to make a Q happy.

[phuangk]

Originally Posted by obsidian440

I want to say thanks to everyone who worked on the wm6 upgrade and the kitchen, I really appreciate your work in bringing this update to those of us who love our phones but our carriers don't.

That said, I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.

To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone. Any ideas ? Are there any new registry tweaks that can be done ?
Or is this just a case of having a self-signed cert and I should buckled down and buy a real one ?

Certificate issue mainly happened on WM5 Smartphone device (correct me if i am wrong). I think there are 2 ways to load the certificate onto your phone.
1. Load certificate with the certificate loader (you can download certificate loader from Microsoft website) http://technet.microsoft.com/en-us/l.../aa997575.aspx
2. Load certificate manually by using cab method. http://blogs.msdn.com/windowsmobile/..._cab_file.aspx

However, your problem looks like you can load certificate, but you are loading the wrong certificate onto your phone. Maybe try to request a new certificate and load it again? Sorry I am not expert on this...

[obsidian440]

Originally Posted by phuangk

Certificate issue mainly happened on WM5 Smartphone device (correct me if i am wrong). I think there are 2 ways to load the certificate onto your phone.
1. Load certificate with the certificate loader (you can download certificate loader from Microsoft website) http://technet.microsoft.com/en-us/l.../aa997575.aspx
2. Load certificate manually by using cab method. http://blogs.msdn.com/windowsmobile/..._cab_file.aspx

However, your problem looks like you can load certificate, but you are loading the wrong certificate onto your phone. Maybe try to request a new certificate and load it again? Sorry I am not expert on this...

Thanks for the try guys! I figured it might be an easy registry fix like wm5. I tried updating the self-signed last night before posting, I even double check ed that it was a certified trusted root , right from the server, but still no good. I guess I gotta convince the company to buy certs, or just go back to 5.

[schettj]

Originally Posted by obsidian440

To be more specific, without the registry change, I get a message stating the server is the wrong name, with the registry it just tells me the certificate is wrong. I have checked all date/time settings on both my server and my phone, both match exactly. I have full access to the exchange server and phone. Any ideas ? Are there any new registry tweaks that can be done ?
Or is this just a case of having a self-signed cert and I should buckled down and buy a real one ?

Did you select the enterprise protocols OEM? I have no idea if it comes into play there or not, but its something to try - I use a self-signed cert for ssl via email/imap, and my ROM build (with that oem included) was able to handle it as usual by popping up the warning and proceeding when I hit OK.

[StarDestroyer]

Originally Posted by obsidian440

That said, I'm having trouble getting my direct push to work again with my exchange server. We are using 2007 with a self-signed ssl cert. On wm5 I was able to use the registry changes along with importing the cert manually to make it work. With my new upgrade I am now getting the message "server cert is wrong". I was unable to find any real answer searching google and these forums. I have tried to manually import the cert and doing the registry change but I'm still running into the same problem.

I run Exchange 2003 and use CAcert for my certificates. Unfortunately, CAcert's root certificates aren't included in mainstream browsers or in Windows mobile by default. So I found a way around it... I found instructions on an MS blog about how to create a .cab file for importing a certificate. I also managed to make an OEM for the CAcert root certificates. You can either sign up with CAcert and put one of the certificates on your exchange server or use the instructions to create a .cab or OEM of your self signed cert and try that... I am using the OEM method successfully on the latest kitchen.

[obsidian440]

Originally Posted by schettj

Did you select the enterprise protocols OEM? I have no idea if it comes into play there or not, but its something to try - I use a self-signed cert for ssl via email/imap, and my ROM build (with that oem included) was able to handle it as usual by popping up the warning and proceeding when I hit OK.

I'll give this a shot, didn't even notice it when I was building the OS.

Originally Posted by StarDestroyer

I run Exchange 2003 and use CAcert for my certificates. Unfortunately, CAcert's root certificates aren't included in mainstream browsers or in Windows mobile by default. So I found a way around it... I found instructions on an MS blog about how to create a .cab file for importing a certificate. I also managed to make an OEM for the CAcert root certificates. You can either sign up with CAcert and put one of the certificates on your exchange server or use the instructions to create a .cab or OEM of your self signed cert and try that... I am using the OEM method successfully on the latest kitchen.

This is just another way of adding the cert into the phone right ? Because I have had success in past versions by just dumping the cert onto my SD card and then opening it in file explorer. I checked where it installed on the device and it was put into the trusted root certs.

I moved back down to the 3.5 AKU but I'll give it another shot today. Gives me an excuse not to answer emails at night!

[StarDestroyer]

Originally Posted by obsidian440

This is just another way of adding the cert into the phone right ? Because I have had success in past versions by just dumping the cert onto my SD card and then opening it in file explorer. I checked where it installed on the device and it was put into the trusted root certs.

I moved back down to the 3.5 AKU but I'll give it another shot today. Gives me an excuse not to answer emails at night!

Yes, it is just another method of getting the cert installed. I've used the .cab version successfully on every version of Windows Mobile I've had on my phone (including the original Sprint ROM and updated official Sprint ROM) with the exception of the latest (1117) kitchen. I can't personally vouch that it works in that kitchen as I now use the OEM method (I started using that in the 1108 kitchen).

Though I guess if the cert if properly installed as a trusted cert in Windows Mobile, then this may not be the solution. Have you tried accessing your exchange server using Pocket IE? Active Sync and Pocket IE are supposed to use the same APIs for accessing the server so if you can't access it from IE w/out SSL errors, it won't work in Active Sync.