Finally upgrading from 4.1.7 to 5.0.3
 

....and...BAS....wowsers....lots to learn.

A couple of questions for those who have gone thru this upgrade:

• Did you modify any of the Roles or use the default settings?
• Did you continue to use your existing IT Policy that was brought over, or did you switch to use one of the canned IT Policies (i.e., Basic Password Security)?
• Anyone using the Individual-Liable Devices IT Policy?
• When adding a new user, is there a way to assign the IT Policy to them at creation? If not, is there a way to make a specific IT Policy the one that is assigned by default?

I'm just starting to dig thru the documentation and the online BAS tutorial (which is not bad, actually).

TIA for any replies (unless they are snarky replies :razz: )

Re: Finally upgrading from 4.1.7 to 5.0.3
 

1. Yes. How? It all depends on your organization.
2. Yes, must use my existing policies. Not believer in one fits all solutions when it comes to roles or it policies. Unfortunately you can not delete built in policies out of the box. Have a script that would allow mw to delete them but they will re-appear again after next SP is applied.
3.Nope
4.None but you can modify Default one to your liking as that will be assigned by default. can't assign other to be default.

Re: Finally upgrading from 4.1.7 to 5.0.3
 

I actually have the default policy set more restrictive than the one we assign to users (we use the same one for 99% of the users). Was hoping with 5.0.3 it would be possible to change which one is the 'default' policy. Oh well.

Re: Finally upgrading from 4.1.7 to 5.0.3
 

I mean that wasn't possible in any BES version but at least in 4.1 you could pick the IT policy while creating user. They've changed lots of things that I liked in 4.1 but at some point you make piece with it and learn to live with less... As a matter of fact the only thing I like in BES 5.0 is the web UI... :-(

Re: Finally upgrading from 4.1.7 to 5.0.3
 

Did you modify any of the Roles or use the default settings?
Just used default settings. Roles not needed in our organization as I am the Supreme Overlord regarding all things BlackBerry.

Did you continue to use your existing IT Policy that was brought over, or did you switch to use one of the canned IT Policies (i.e., Basic Password Security)?
I used the IT Policy Import/Export tool in the BRK. Saved a lot of work. The canned Policies were okay, but didn't cover everything we wanted to do.

Anyone using the Individual-Liable Devices IT Policy?
Not yet, but we're considering it in the near future. I might have to edit the canned policy to suit out needs a bit.

When adding a new user, is there a way to assign the IT Policy to them at creation?
Actually, there is. If you assign an IT Policy to a group and then assign the person to the group when adding the new user.

If not, is there a way to make a specific IT Policy the one that is assigned by default?
You can also modify your Default policy to be as restrictive as you want. (Just be sure to make a copy of it BEFORE you start fiddling with it.)

Re: Finally upgrading from 4.1.7 to 5.0.3
 

1. No
2. I have re-created the policies we already had on the old system and cleaned them up (we don't use the default policy).
3. No
4. We use groups, which we assign at user creation time. Users get the correct policy automatically through the group.

We used transporter and it worked very well. I migrated users in batches of 20. We also had to re-create our pushed apps, but the process has got easier with version 5.

I first hated the new web admin console, but got used to it. We enabled SSO for it so I don't have to login all the time.

Good luck!

Re: Finally upgrading from 4.1.7 to 5.0.3
 

SSO is very nice feature unless you have BAS pool setup. It does not work as well then since I kept getting "Page can not be displayed" if I click on some users tab etc. Then we disabled it and issue was gone.

Re: Finally upgrading from 4.1.7 to 5.0.3
 

We have a BAS pool setup (two servers) and SSO and there are no issues. We initially had a problem that the local firewall on each server was blocking ports used for the BAS services in the pool to communicate. Once we have allowed all traffice between the two servers, the problem was gone.

Re: Finally upgrading from 4.1.7 to 5.0.3
 

Are you using DNS round robin load balancer or hardware one? We have DNS one in place and I assume it has something to do with that.

Re: Finally upgrading from 4.1.7 to 5.0.3
 

We are doing DNS round-robin for the BAS pool.