Go Back   The Unofficial BlackBerry Support Forum > BlackBerry Enterprise Server > General BES Discussion

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-06-2009, 01:35 PM
Member
BlackBerry Device: 8100
 
Device Firmware: 4.2.1.101
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Optus
 
Join Date: Apr 2009
Posts: 32
Microsoft Live Communications Server - Office Communicator for Blackberry

does anyone have a guide they used to successfully implemented OCS for blackberries?

uor environment:

MS Exchange 2003
BES 4.1.6
dedicated LCS server on windows 2003 - currently have Office Communicator deployed through PCs in the organisation.


i've followed the Deploying the Communicator Web Access Server guide on TechNet (Deploying the Communicator Web Access Server) and deployed the application to my handheld (8100) but i get the error:
"your password was not accepted by the system. Please check your Windows account, whether the password has changed or whether the spelling is correct."

i'm using the sign-in name as i would when logging into Office Communicator on my PC.
User name is left blank
Password is the domain login password (again as is used when logging into Office Communicator)
Reply With Quote
  #2 (permalink)  
Old 11-06-2009, 02:04 PM
GaryCutri's Avatar
Moderator
BlackBerry Device: Bold 9700
 
Device Firmware: 5.0.0.371
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Telstra - Australia
 
Join Date: Sep 2006
Location: Melbourne
Posts: 9,240
Images: 221
Hi,

Have you installed and configured the "BlackBerry Collaboration Service" for OCS? What Enterprise Messaging Client version did you install on the devices? And to confirm you will need to enter both a user name and password when you logon using the client.

Thanks,

Gary
Reply With Quote
  #3 (permalink)  
Old 11-06-2009, 02:30 PM
Member
BlackBerry Device: 8100
 
Device Firmware: 4.2.1.101
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Optus
 
Join Date: Apr 2009
Posts: 32
Hi Gary,

yes, during setup of 4.1.6, selected Microsoft Office Live Communications Server 2005 (Office Communicator). Confirmed Blackberry Collaboration Service is running on BES

Device version is Blackberry instant Messaging for Micrososft Office Live Communications Server 2005 v 1.1.18


with regards to usernames:

on the login page on the blackberry you have:

Sign-in name: user@domain.com
User name: [left blank; but also tried domain\user]
Password: *****



thanks

Last edited by dallandra; 11-06-2009 at 02:34 PM.
Reply With Quote
  #4 (permalink)  
Old 14-06-2009, 11:53 PM
GaryCutri's Avatar
Moderator
BlackBerry Device: Bold 9700
 
Device Firmware: 5.0.0.371
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Telstra - Australia
 
Join Date: Sep 2006
Location: Melbourne
Posts: 9,240
Images: 221
Quote:
Originally Posted by dallandra View Post
Hi Gary,

yes, during setup of 4.1.6, selected Microsoft Office Live Communications Server 2005 (Office Communicator). Confirmed Blackberry Collaboration Service is running on BES

Device version is Blackberry instant Messaging for Micrososft Office Live Communications Server 2005 v 1.1.18


with regards to usernames:

on the login page on the blackberry you have:

Sign-in name: user@domain.com
User name: [left blank; but also tried domain\user]
Password: *****



thanks
After you install the BlackBerry® Enterprise Server with the BlackBerry Collaboration Service, you can verify that the
BlackBerry Collaboration Service can connect to your organization's instant messaging server.

1. Browse to the Microsoft® Office Communicator Web Access web client using a web address in the following format:

<protocol>://<cwahostcomputername>.< domainname>:<portnumber>. (For example, https://server01.test.rim.com:
444) Use the same host name, transport protocol, and port number that you specified for the instant messaging server
when you installed the BlackBerry Collaboration Service. The port number might be optional if your organization's
instant messaging server uses port 80 or port 443.

2. Log in to the Microsoft Office Communicator Web Access web client.

If you log in to the Microsoft Office Communicator Web Access web client successfully, the BlackBerry Collaboration Service
can connect to your organization's instant messaging server.
Reply With Quote
  #5 (permalink)  
Old 15-06-2009, 02:51 PM
Member
BlackBerry Device: 8100
 
Device Firmware: 4.2.1.101
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Optus
 
Join Date: Apr 2009
Posts: 32
Hi Gary,

the quick answer to your previous post is, no, i couldnt connect. i got an error from when trying to log in:
"The session was ended. Communicator Web Access Server cannot log the user on to the Live Communications Server. (Error Code: 1)" (see attached: img.jpg)

i started over, and used the following guide to setup:
Download details: Microsoft Office Communicator Web Access Planning and Deployment Guide


i'm installing CWS on the same machine as we have our existing LCS server(lets call my server LCS01), as described in doco pg10: One Server for Both Internal and External users.

from pg 31, of doco:

steps
*(pg33)* download the CA certificatiojn path - DONE

*(pg34)* install the CA certification path - DONE

*(pg34)* Request the certificate -
step 5. In Certificate Template. select Web Server
> there was no Certificate template menu, nor was there the option to chose "web server" (see attached img01.jpg)
so i used "Server Authentication Certificate"
*(pg34)* install the certificate on the server - DONE
step 6. in Identifying information for Offline Template, type the FQDN of the Communicator Web Access server
> again no such field, so i put the FQDN under the Identifying Information field, under "Name" (again see (see attached img01.jpg))

*(pg34)* Install the certificate on the server
step 11. confirm that the certificate that you requested ... with it's FQDN is listed. if not, copy it from Personal\Certificates folder to the Trusted Root Certification Authorities\Certificates folder
> had to do manual copy as instructed as it was not in Trusted...\Certificates folder


*(pg36)* I then installed Communcator web access

*(pg36)* activated communicator web access
> created CWAservice AD account
> selected certificate (as just created above)

*(pg38)* created virtual server
> Internal server (accessible by users who are within the corporate network - chose this option first to test that i could access CWA from internal network ie ensure connections were listening and communicating ok etc. before creating external server for I assume Blackberries? or do Blackberries still use Internal server?)
> selected same certificate as created above for HTTPS connection
> IP=(all unassigned), port=443

and thats all i've done

i checked that the virtual server is connected (see attached img03.jpg)

even tried initiating a CWA connection from the CWA server itself to ensure no f/w/network issues and got the same error, as listed at the top.

hoping you can provide some guidance

cheers
Ben
Attached Images
File Type: jpg img02.jpg (32.7 KB, 9 views)
File Type: jpg img03.jpg (42.7 KB, 10 views)
File Type: jpg img.jpg (21.2 KB, 11 views)
File Type: jpg img01.jpg (59.7 KB, 12 views)

Last edited by dallandra; 15-06-2009 at 03:06 PM.
Reply With Quote
  #6 (permalink)  
Old 15-06-2009, 11:28 PM
GaryCutri's Avatar
Moderator
BlackBerry Device: Bold 9700
 
Device Firmware: 5.0.0.371
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Telstra - Australia
 
Join Date: Sep 2006
Location: Melbourne
Posts: 9,240
Images: 221
Regarding your question "or do Blackberries still use Internal server?" I can confirm that the BES Collaboration Service accesses the server internally. As this is an error with LCS I would recommend that you call in a Microsoft expert as this is outside my area of expertise.
Reply With Quote
  #7 (permalink)  
Old 03-07-2009, 02:17 PM
Member
BlackBerry Device: 8100
 
Device Firmware: 4.2.1.101
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Optus
 
Join Date: Apr 2009
Posts: 32
Quote:
Originally Posted by GaryCutri View Post
After you install the BlackBerry® Enterprise Server with the BlackBerry Collaboration Service, you can verify that the
BlackBerry Collaboration Service can connect to your organization's instant messaging server.

1. Browse to the Microsoft® Office Communicator Web Access web client using a web address in the following format:

<protocol>://<cwahostcomputername>.< domainname>:<portnumber>. (For example, https://server01.test.rim.com:
444) Use the same host name, transport protocol, and port number that you specified for the instant messaging server
when you installed the BlackBerry Collaboration Service. The port number might be optional if your organization's
instant messaging server uses port 80 or port 443.

2. Log in to the Microsoft Office Communicator Web Access web client.

If you log in to the Microsoft Office Communicator Web Access web client successfully, the BlackBerry Collaboration Service
can connect to your organization's instant messaging server.


Hi Gary,

i managed to get the connection working (issue with certificates first time round). i can confirm your above two steps work for our environment. ie CWA connection launched from BES is successful.

however i am still unable to connect via my blackberry


i use the following credentials:

Sign-in name: user@domain.com
User name: domain\user
Password: *****

but is still get the error message returned almost instantly:
"Your password was not accepted by the system. please check your Windows account, whether your password has changed or whether the spelling is correct"


any ideas? any logs i can check to see where the failure point is?
Reply With Quote
  #8 (permalink)  
Old 03-07-2009, 05:06 PM
GaryCutri's Avatar
Moderator
BlackBerry Device: Bold 9700
 
Device Firmware: 5.0.0.371
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Telstra - Australia
 
Join Date: Sep 2006
Location: Melbourne
Posts: 9,240
Images: 221
Quote:
Originally Posted by dallandra View Post
Hi Gary,

i managed to get the connection working (issue with certificates first time round). i can confirm your above two steps work for our environment. ie CWA connection launched from BES is successful.

however i am still unable to connect via my blackberry


i use the following credentials:

Sign-in name: user@domain.com
User name: domain\user
Password: *****

but is still get the error message returned almost instantly:
"Your password was not accepted by the system. please check your Windows account, whether your password has changed or whether the spelling is correct"


any ideas? any logs i can check to see where the failure point is?
What credentials are you using when you log onto the "Microsoft Office Communicator Web Access web client"? e.g. “DOMAIN\username” or just “username”
Reply With Quote
  #9 (permalink)  
Old 03-07-2009, 05:15 PM
Member
BlackBerry Device: 8100
 
Device Firmware: 4.2.1.101
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Optus
 
Join Date: Apr 2009
Posts: 32
sign-in name = email address (user@domain.com)
then i'm prompted for authentication to connect to the lcs server , to which i use my domain credentails: DOMAIN\username

i read elsewhere that if CWA is installed after BES, it could be wise to reinstall BES again -recementing the MDSS server settings.

when i installed BES i didnt use the FQDN for the LCS server. however i've since changed it to the FQDN in Blackberry Server Configuration-Collaboration Service. then restarted the Blackberry Collaboration Service-service on the server. still to no avail.

Last edited by dallandra; 03-07-2009 at 05:17 PM.
Reply With Quote
  #10 (permalink)  
Old 03-07-2009, 05:20 PM
GaryCutri's Avatar
Moderator
BlackBerry Device: Bold 9700
 
Device Firmware: 5.0.0.371
 
Email Configuration: BlackBerry Enterprise Server (BES)
 
Mobile Carrier & location: Telstra - Australia
 
Join Date: Sep 2006
Location: Melbourne
Posts: 9,240
Images: 221
Quote:
Originally Posted by dallandra View Post
sign-in name = email address (user@domain.com)
then i'm prompted for authentication to connect to the lcs server , to which i use my domain credentails: DOMAIN\username

i read elsewhere that if CWA is installed after BES, it could be wise to reinstall BES again -recementing the MDSS server settings.

when i installed BES i didnt use the FQDN for the LCS server. however i've since changed it to the FQDN in Blackberry Server Configuration-Collaboration Service. then restarted the Blackberry Collaboration Service-service on the server. still to no avail.
Is your BES configured to use a proxy? Please ensure that your BES has direct access to connect to your LCS server.
Reply With Quote
Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Perform basic troubleshooting steps for Novell GroupWise BESadmin Novell GroupWise 3 12-01-2010 11:31 PM
Service failed to start, generating error 5305 BESadmin Microsoft Exchange 0 18-02-2009 10:11 PM
Unlisted message error or Desktop email program unable to submit message BESadmin General BES Discussion 13 21-01-2009 02:10 PM
Move X amount of users from one environment to another with diff SQL versions. Live2Ride General BES Discussion 3 12-09-2007 11:43 AM
MSDE to SQL Server 2005 migration JeffreyK Microsoft Exchange 1 28-08-2007 08:07 PM


All times are GMT +11. The time now is 08:04 AM.

Copyright ©2006 - 2010 BLACKBERRYFORUMS - This website and its members are not affiliated with Research in Motion (RIM). RIM and BlackBerry are Registered Trademarks of Research In Motion


Search Engine Friendly URLs by vBSEO 3.5.0 RC2