• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 544
  • Last Modified:

Blackberry handset account not synchronising with GroupWise 7.0.2 mailbox

Title:
I have a BB user who's mail is synchronised from GW. Having recently married, her name was changed in GW, her BB was wiped, her user account was removed from the BB server. Her new user credential were entered onto the Blackberry Enterprise Server, prior to the BB device being re-configured. All seems good with the exeption her "new" mailbox is not showing up in the PIM section in her BES properties. Therefore mail is not picked up.
Is there a method of forcing the update on BES, or should this be looked at in GW?
0
gavin_d
Asked:
gavin_d
  • 5
  • 2
1 Solution
 
MikeIT ProfessionalCommented:
this is a Groupwise issue i believe.  Check the settings in there.  There is no way to force the update on the Enterprise
0
 
gavin_dAuthor Commented:
Thanks this is kind of what I suspected.
0
 
MikeIT ProfessionalCommented:
No problem.  Good luck.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
gavin_dAuthor Commented:
Hi, I have checked out the device and BES. This works perfectly when wiped and another account associated with it. The issue must be in the settings in GW. Generally when we have a user name change, we add an alias to the account which captures and stores mail assigned to a pervious name. Could this be the issue. Is BES looking for an exclusive naming convention and the alias is not recognised. I have still to return to work to test this out.
0
 
gavin_dAuthor Commented:
I am picking this one up again. Have checked out phone using another account and it is synch'ing perfectly well. This points to GW as being the culprit. I have removed the mail alias and set the BB device to activate. When I check the PIMM settings in BES they are all picking up the correct "new" information, but the mailbox synch has <none>. Has anyone else come across similar issues with name changes.?
Cheers
0
 
gavin_dAuthor Commented:
OK, late but a solution...BES in it's infininte wisdom had refused to flush the original account from the system.  A manual removal allowed BES to pick up the changed account and all is good.
0
 
gavin_dAuthor Commented:
This is a solution I came across myself. I am posting thsi as soved for others to refer to: Check BES first
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now