[CRWJumper]

Originally Posted by ZeroKool

pushed patches to 20+ devices last night on 2 different BES servers. All but 1 device came back successfully. An 8700 on 4.1.0.194. Have multiple devices that are the same and the patch applied successfully on them. This is the second device that I've got the error on so far. One 8700 and one 8703e. Get error:

Configuration Status: Device State invalid.

How late did you push? Could the device have been off?

[x14]

Originally Posted by chrbes

I am having the same issue and I have waited 24 hours. Did they give any clue as to how long we need to wait?

You'll get the update on March 11 when the users call.

[ts937km]

I talked to RIM and there are several cases reporting the issue with an IT policy not allowing deletion of apps with an 8100. They added me to the list and he said they are actively working on it and can recreate the problem.

[CRWJumper]

Originally Posted by ts937km

I talked to RIM and there are several cases reporting the issue with an IT policy not allowing deletion of apps with an 8100. They added me to the list and he said they are actively working on it and can recreate the problem.

All of the 8100s (Cingular only) in our system have o/s versions that don't need the update.
Are the TMobile and other ones using an older o/s?

[ZeroKool]

Originally Posted by CRWJumper

How late did you push? Could the device have been off?

Both devices have been on / charged / active / rebooted / policy and Service books sent / re-created and re-applied software config. Waited 48 hours for one and 24 hours for the other. Even shortened the time for the BES to push the app. Not too short though. Just test.

There has to be a reason that only I am experiencing this error and with 2 handhelds. I'm gunna keep digging. Let ya know.

[Mark_Venture]

Originally Posted by |||||||

It "should" work with The Internet browser, but it's probably not set to default. Basically it "will" work with MDS and that's why it's suggested..

Small problem for me is that my MDS uses our PRoxy server (which requires authentication) for internet access, and the blackberry isn't prompting the user to authenticate... so our proxy server wont allow access out...

anyway around this?? can i set something in the Policy we push down to all devices so they use internet (via wireless carrier?) instead of MDS (which goes thru our company's proxy)?

On my Pearl, I've gone Options -> Advanced Options -> Browser, and set default browser to Internet Browser. But that didn't help :(

[JRV]

Originally Posted by Mark_Venture

Small problem for me is that my MDS uses our PRoxy server (which requires authentication) for internet access, and the blackberry isn't prompting the user to authenticate... so our proxy server wont allow access out...

Two possible alternatives: Set proxy credentials in MDS Properties, in which case all users authenticate as the account you set in MDS. Or, make your BES server a SecureNAT client to the proxy, in which case MDS traffic is unauthenticated.

Caution: This advice from one who has not yet started the DST patch push, but it should work...I think...It will definitely work for web browsing because we've used both configs here.

[Mark_Venture]

Originally Posted by JRV

Two possible alternatives: Set proxy credentials in MDS Properties, in which case all users authenticate as the account you set in MDS. Or, make your BES server a SecureNAT client to the proxy, in which case MDS traffic is unauthenticated.

Thanks, but I don't think I can do either.

I'm at a federally regulated account (FDA)... so authentication with ONE account is not an option...

And since i don't have access to the proxy server, I can't make any changes there... plus, since its federally regulated, I have to follow the change management process... get approvals, etc... no way that will be done so I can patch all the handhelds BEFORE march 11.

I'm screwed.

Rim pointed me to Doc ID : KB12286 -> BlackBerry Search Results which requires me to change the proxy server. It might be my only option... that is.. if the security team here will allow it

[|||||||]

Originally Posted by juwaack68

Anyone?

If you read the first post it says no you don't.

[centrekin]

What is the easiest way to keep up with what devices have been patched? I was able to successfully push the patch to several test devices, but I would like to keep up with who has been upgraded... Any thoughts?

[Hatchy]

Originally Posted by jmanford

I pushed out my DST updates to a few handhelds. How can I tell if they installed on the device? Is there a way to check on the handheld?

On the Handheld just go to Options. The first value listed should be "2007 DST Patch". I pushed to several handhelds and it worked, however...

All meetings from March 11 to March 31 are displayed as ONE HOUR AHEAD on these devices?? Meetings outside these dates appear fine. My BES is patched, but I'm not sure this is relevant. This is also the case with a client who tested the push to their device.

[halflife78]

Stupid question.

I setup everything and succesfully pushed the patch to a test device, but when I run the DSTquery program it just pops up for a split second and then disappears, anyone know why this is?

[CRWJumper]

Originally Posted by centrekin

What is the easiest way to keep up with what devices have been patched? I was able to successfully push the patch to several test devices, but I would like to keep up with who has been upgraded... Any thoughts?

RIM has created a tool (DST2007Query.exe) that can be run to automatically determine which devices/users have the patch applied correctly.

[CRWJumper]

Originally Posted by Hatchy

On the Handheld just go to Options. The first value listed should be "2007 DST Patch". I pushed to several handhelds and it worked, however...

All meetings from March 11 to March 31 are displayed as ONE HOUR AHEAD on these devices?? Meetings outside these dates appear fine. My BES is patched, but I'm not sure this is relevant. This is also the case with a client who tested the push to their device.

Our users aren't seeing the discrepancy that you are.
Have your desktops been patched?
(The patch was pushed by Gatesrosoft yesterday).

[x14]

Originally Posted by Hatchy

All meetings from March 11 to March 31 are displayed as ONE HOUR AHEAD on these devices?? Meetings outside these dates appear fine. My BES is patched, but I'm not sure this is relevant. This is also the case with a client who tested the push to their device.

I see the same thing for my repeating calendar entries in March. We also haven't deployed the fix for repeating calendar entries.

[jibi]

Originally Posted by CRWJumper

All of the 8100s (Cingular only) in our system have o/s versions that don't need the update.
Are the TMobile and other ones using an older o/s?

It depends on what version of BES you are running. Obviously 4.0.6, which is DST compliant, has been available for a while. For those of us running 4.1.x, SP3 has only recently been made available to support customers. For all current 4.1.x installations of BES, the Pearl requires the device patch.

[jibi]

Okay, so any luck on figuring out this whole mess?

DST2007Query_SERVER.csv:
1.5,Error,0x88,0x00,200

DST2007Query_Log.txt:
'Time Zone Patch' DB found for [14] [user@domain.com]
...but no 'Time Zone Patch' is patched based on Tag 3 [1.0] entry

[20000] (02/14 15:11:48.948):{0xFA8} Summary of results:
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users: 16
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users requiring patch: 14
[20000] (02/14 15:11:48.948):{0xFA8} 4 upgraded
[20000] (02/14 15:11:48.948):{0xFA8} 10 not upgraded [8 errors]
[20000] (02/14 15:11:48.948):{0xFA8} (10 helper installed)
[20000] (02/14 15:11:48.948):{0xFA8} (4 helper not installed)
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users not requiring patch: 1
[20000] (02/14 15:11:48.948):{0xFA8} 1 upgrade not required
[20000] (02/14 15:11:48.948):{0xFA8} 0 no device info
[20000] (02/14 15:11:48.948):{0xFA8} (0 helper installed)
[20000] (02/14 15:11:48.948):{0xFA8} (1 helper not installed)
[20000] (02/14 15:11:48.948):{0xFA8} Total number of users with unsupported device code: 1

Device:
2007 DST patch applied.

So according to the device, the patch IS applied. According to DST2007Query, it's not. According to DST2007Query, the patcher (not the patch) has been installed on the device.

Now the thing that REALLY pisses me off is that the damn thing won't retry, it appears, because it thinks it's installed.

I just removed the patch from a user's device, enabled MDS, pushed the application back to the user, and now it's reporting as installed/applied in DST2007Query.

For the record, it sucks that MDS is pushing out a service book and applying itself as the default browser and MDS browser even though the damn service is disabled in Windows services, in BlackBerry Manager at the top-level, and for the individual users. I guess it just doesn't get the point that I don't want to use it!

[ZeroKool]

Originally Posted by ZeroKool

pushed patches to 20+ devices last night on 2 different BES servers. All but 1 device came back successfully. An 8700 on 4.1.0.194. Have multiple devices that are the same and the patch applied successfully on them. This is the second device that I've got the error on so far. One 8700 and one 8703e. Get error:

Configuration Status: Device State invalid.

FYI. All the devices that I pushed the patch to had to be rebooted. All 8700's with 4.1.0.194 and on with .344.

[juwaack68]

Originally Posted by |||||||

If you read the first post it says no you don't.

Well, F...iddle.

I created the software config exactly as described and assigned it my BB and it still does not appear under Options.

Guess I'll call RIM when I have a few days to spare on hold.

[x14]

Originally Posted by juwaack68

Well, F...iddle.

I created the software config exactly as described and assigned it my BB and it still does not appear under Options.

Did you give it 4 hours?