So finally after much anticipation RIM has finally released the OCS 2007 client for the blackberries. It looks like the official release occurred on July 28th. This was all after releasing SP6 for BES 4.1 on July 16th and not having the client available. Which while yes HTML email is nice I’ve been holding out for the OCS 2007 client for a looooong time now.
Anyway the nitty gritty:
So I had already installed SP6 for BES 4.1 and configured it to point to my OCS 2007 Web instance. All that is needed is to give BES the FQDN of the server and the port number. In our case we use https and port 444. This is configured in the Blackberry Manager console by going to the BBIM instance and editing properties and filling in the appropriate blanks.
This was the easy part the part that I ran into trouble with was being able to push OTA (Over The Air) the OCS 2007 client to the handhelds. I downloaded the OTA version of the client but to no avail it would not show when I would create a new software policy. So on a whim I decided to use the desktop version and that worked. Why RIM offers OTA versions of apps that don’t load I don’t know but then again BES admin is just a side gig for me out of my primary job duties.
The process to get OTA push of the client is as follows:
- Download oc2007_Desktop_2.1.10c.zip
- I created a folder called oc2007 in the following directory structure:
C:Program FilesCommon FilesResearch In MotionSharedApplications
- Extracted the contents of the zip file into that folder so that there are the following files:
- From a command prompt then run the following:
C:Program FilesCommon FilesResearch In MotionAppLoader>Loader.exe /index
This should add two files to the oc2007 folder called PkgDBCache.xml & specification.pkg. If you do not see these files then something has gone wrong and I recommend you look at the following article from RIM. Deploying OTA Applications
Under the assumption you do have these files then all that is left is to create the Software Configuration in the BES Manager and the Application policy.
- Open up the BES Manager
- At the BlackBerry Domain level select the Software Configurations Tab
- Click Add New Configuration
- In the Configuration Name identify the application in this case I used OCS2007
- In the Configuration Description I put Office Communicator 2007 client
- Under Device Software Location this is where you put in the UNC path to the share you created to distribute OTA Applications. Again if you have no idea what I’m talking about at this point see the link above.
- Once the UNC path is put in you should see a list of all the applications available in this case we want to only check the Enterprise Messenger under Application Software.
- Lastly create the policy
- Click on the Policies button.
- Click New
- Give the Policy a Name in my case I called it OCS2007
- I set the Disposition to Required and allowed the application access to all phone functions as this is a trusted application and I don’t want my users bothered with questions.
- At this point OK all the way out.
The application is now ready for deployment. Now because I’m impatient I went into the Users area and right clicked on myself and said assign software configuration and selected OCS2007 and low and behold OCS 2007 client is now on my phone and working.
That’s all I hope this helps anyone who ran into the application deployment situation like I did.