[DarthBBerry]

Originally Posted by ladydi

The PPC's on the other hand, well that's a whole different story...one without a happy ending.

Yeah, had to do those too. Since we're a Notes shop and using mSuite for our synching platform, I used the wireless connection via the mSuite console and deployed the patch to the devices. No complaints so far. But then again, there's only like 13 of them.

[DarthBBerry]

Notice how there are more DST horror stories still creeping from the grave than success stories? It's just sad expecially since it's all a conspiracy by the golfers and candy manufacturers.

[chubby_nubby]

There are many horror stories, going into DST I thought we would have many issues, since our user's like to be spoon-fed. All in all, everything went pretty smooth, not to many Exchange Calendar issues reported, and a couple BB DST issues mainly because of getting replacement BB's. One help desk debacle where they confused a windows mobile for a BB (how dare them). But very smooth, I am now waiting for my bonus. . . . .. .LOL . .still waiting . . .


CB

[DarthBBerry]

Originally Posted by chubby_nubby

I am now waiting for my bonus. . . . .. .LOL . .still waiting . . .

Word.

[BBAdmin]

I sorted out 30 of my own users, and 5000 of other peoples that were split over 100 odd BES servers. I wrote a strategy for deployment and didn't have a single problem with a single user.

Pleasing!!!!

[afrazier5]

I'm glad to see that some had a good success story to share. I wish we could have had that much success. Based on my research here in the forums, I told our lead admins that it would fail and sure enough, we had about 1000 failures globally (out of 2000). What I'm curious about, is how are you all addressing this moving forward on newly deployed devices? I've heard that it can be pushed via policy but am concerned with the poor success rate with the 'Big Bang'. Right now, our mobile device team is doing a manual install on every device which obviously adds to their work load. Anything that the BES gods can suggest?

[dheida]

I must be the "BES Admin" with the fewest users. Pushed mine OTA with no problems so I sent it out to the other six with no problems. We did have the Outlook issue though.

[DarthBBerry]

Originally Posted by afrazier5

I'm glad to see that some had a good success story to share. I wish we could have had that much success. Based on my research here in the forums, I told our lead admins that it would fail and sure enough, we had about 1000 failures globally (out of 2000). What I'm curious about, is how are you all addressing this moving forward on newly deployed devices? I've heard that it can be pushed via policy but am concerned with the poor success rate with the 'Big Bang'. Right now, our mobile device team is doing a manual install on every device which obviously adds to their work load. Anything that the BES gods can suggest?

Since any Blackberry device has to go through me before it lands in the hands of a user, I have ultimate power. I update the device when activating it either by (1) website (2) USB patch or (3) policy push. Any way I do it, they get it.

In your situation, you may want to make it the default policy and push it out when activating the device.

[rliebsch]

Success here. 70 blackberry users.

Of course, I was reading here constantly for the weeks leading up, and through each mouse click in upgrades and policy push.

So, though my company thinks its me, it's really maybeline ^H^H^H^H^H^H^H^H^H^ BBF!

[afrazier5]

Originally Posted by DarthBBerry

Since any Blackberry device has to go through me before it lands in the hands of a user, I have ultimate power. I update the device when activating it either by (1) website (2) USB patch or (3) policy push. Any way I do it, they get it.

In your situation, you may want to make it the default policy and push it out when activating the device.

Darth, can you advise me how to set this up via policy? Our head BES Admins have advised that this is not possible and I'm convinced that they are not as well informed as yourself at this point (Want a job????).

[stuwhite]

Originally Posted by afrazier5

Darth, can you advise me how to set this up via policy? Our head BES Admins have advised that this is not possible and I'm convinced that they are not as well informed as yourself at this point (Want a job????).

Jobs in Utah you say.... I will let Darth answer though, he has so much more time on his hands than me.

[DarthBBerry]

Originally Posted by afrazier5

Darth, can you advise me how to set this up via policy? Our head BES Admins have advised that this is not possible and I'm convinced that they are not as well informed as yourself at this point (Want a job????).

Since this is a DST Success Story post, I'll reply to you in a PM.
So much for that idea... cant attach images in PM. pwnd. Answer below.
Anybody else who wants to chime with advice or corrections, please feel free to do so.
And thanks for the job offer, but you probably couldn't afford me.
*************
Hey dude,

Hope this will help with setting a default policy for new users. It's pretty close to creating the DST policy, but you just need to apply it to each new user. Plus, you can add new apps to it when you create them.

You will need to have the application files already downloaded, packaged and shared in a central location. Look back at the way it was done for DST and you'll get the idea.

There are 3 parts to this procedure.

Creating a Policy
Creating a Configuration
Applying a Configuration to a User

Creating a Policy
Under Handheld Management go to Software Configurations and click Manage Application Policies. (See img1)

Then click [New]. You can now create a new policy. Name it whatever you want. I named this one New User Policy. I set the disposition to Required to force all the applications under this policy to the devices. (see img2) Click Apply & OK.

Creating a Configuration
Click Add a Configuration. In the Name, Description and Location fields fill in the appropriate information. Make the Delivery Wireless and in the Policy field, apply the New User Policy created above. (see img3)

Applying a Configuration to a User
After you create a new user but before you activate the device, go back to Handheld Managment and click on Handhelds. Find your user and click on Assign Software Configuration. Select the New User Default policy we created and click OK. (see img4).

Lastly, click Update Configuration Check Status to force BES to contact the device at the next opportunity. Now activate the device. The policy and applications will go to the device with the Enterprise Activation.

Hope this helps!

[ladydi]

that is still on a per user basis and adds one more step. I was playing with groups last night and it looks like I can apply software configs to a group. I tried, but nothing appeard to happen, so I guess I need to do more reading, but if that works (4.1 BES) it would make my life so much simpler as my user count goes up. Does anyone else do this?

[stuwhite]

Originally Posted by ladydi

that is still on a per user basis and adds one more step. I was playing with groups last night and it looks like I can apply software configs to a group. I tried, but nothing appeard to happen, so I guess I need to do more reading, but if that works (4.1 BES) it would make my life so much simpler as my user count goes up. Does anyone else do this?

When you say "per user", obviously you can apply this to a group of users by CTRL-selecting so it isn't that much hassle really. I did all our DST stuff this way and it was really easy. Granted, it won't be fun for a specific 20% of 300+ users but our tend to be all or nothing

[autsoldnow]

Where do I get this patch from? I don't see any link here for it! :(

Thanks
Andrew

[DarthBBerry]

Originally Posted by ladydi

that is still on a per user basis and adds one more step. I was playing with groups last night and it looks like I can apply software configs to a group. I tried, but nothing appeard to happen, so I guess I need to do more reading, but if that works (4.1 BES) it would make my life so much simpler as my user count goes up. Does anyone else do this?

Using BES 4.0.6. No group for me yet. But I'm upgrading to 4.1 soon.
And like Stu says in his post, you can CTRL click or even SHIFT click and apply the config.

[DarthBBerry]

Originally Posted by autsoldnow

Where do I get this patch from? I don't see any link here for it! :(

Thanks
Andrew

You mean the DST patch? Dude, where ya been?
CLICK ME ---->RIM DST LINK<---- CLICK ME

[ladydi]

Originally Posted by DarthBBerry

Using BES 4.0.6. No group for me yet. But I'm upgrading to 4.1 soon.
And like Stu says in his post, you can CTRL click or even SHIFT click and apply the config.

I did do it that way to mass apply it. I meant for future, one or two at a time setups. It would be nice to have a group that has the software policies already set up and then as soon as I put the user into the appropriate group, everything applies. I have found one hitch in my plan because my security policy denies application installs, so I couldn't put it on the group that sends out software configs. I'm sure I will come up with something brilliant once I figure out the group stuff.

[stuwhite]

Originally Posted by ladydi

I did do it that way to mass apply it. I meant for future, one or two at a time setups. It would be nice to have a group that has the software policies already set up and then as soon as I put the user into the appropriate group, everything applies. I have found one hitch in my plan because my security policy denies application installs, so I couldn't put it on the group that sends out software configs. I'm sure I will come up with something brilliant once I figure out the group stuff.

This is gonna sound stupid but can't you just disable the app install deny like we did for DST, or is this a compliance thing for you guys?

[stuwhite]

Originally Posted by DarthBBerry

You mean the DST patch? Dude, where ya been?
CLICK ME ---->RIM DST LINK<---- CLICK ME

LOL