I'm not a big fan of OCS for a whole pile of reasons, beginning with the inflexible, lacking UI and ending with restrictions on the specific deployment I use that force me to VPN to connect. Mostly issues I wouldn't have with Jabber.
With our configuration (and possibly by default) URLs were shown as plain text and not as clickable hyperlinks. You can enable this with a Group Policy - download the OCS Policies documentation and edit and import communicator.adm, or with a registry edit.
Changing the Registry
Registry edits are quick and easy, and I was only concerned about myself, so I took that route.
Save the code code below into a text file with a .reg suffix and import it, or right click the following link and and Save As to download .reg file to enable clickable URLs in OCS. Once the registry changes have been made or imported you will need to restart your OCS client.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]
"EnableURL"=dword:00000001
If you'd prefer to manually make the registry changes:
- Open regedit.ext and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator
- Create a new DWORD value called EnableURL and set the value to 1 to make the URLs clickable. Set the value to 0 to have the URLs appear as plain text.
Due Diligence
Checking in with an employee at Jabber to see if hyperlinks are enabled in MomentIM.
Good to know.
I had to resort to this after upgrading to the leaked beta of BlackBerry OS 4.5 on my Curve the email-import method did not work. It's a perfectly legitimate method of importing a SecurID token on your handheld, and now I actually prefer it because it is significantly less problematic than emailing the seed file to yourself. For more information see the RSA BlackBerry Soft Token page.
What you need
- RSA SecurID Token for BlackBerry Utilities (bb300_utils.zip)
- SecurID Soft Token for BlackBerry - the app itself, if not installed (bb300.zip)
- Your soft token seed file (.SDTID file)
- BES 4.1.3 or newer
- BB OS 4.2.2 or newer
- Java Runtime Environment 1.4 or newer
If your BES' MDS Connection Service port (default is 8080) is open you do not need to run this on the BES. Mine is not, so I pushed my soft token out from my BES.
Preparing your BlackBerry
Install the SecurID 3.0 software. Launch it, accept the EULA and open the Settings. Make sure that Listen for Token is set to Yes. When the security prompt appears choose Yes to allow the application to run as a server.
Pushing out the Soft Token with PushToken
- Download and unzip bb300_utils.zip
- Make sure your .SDTID is on the same disk
- Open a command prompt (Start > Run > cmd)
- From the command prompt:
java -classpath <path_to_bb300utils>\PushToken.jar PushToken -e<email address or pin> -h<BES address> <path to .sdtid file>
In my case I ran:
java -classpath bb300_utils\PushToken.jar PushToken -ecorey@mydomain.com -hlocalhost x-rimdevice-xxxxxxxx.sdtid
- If the .sdtid file was valid and you gave the SecurID application permission to run as a server on your BB you should see a prompt on your handheld about receiving a token.
- You may be prompted for a password, if so enter the password you were given with the token.
- If you entered the correct password you will receive notification of the token being imported. You can rename the token by choosing Manage Tokens from the menu.
- That's it. When you open the application you'll be prompted for your passphrase and PIN, and then be shown the generated token. One nice change between versions 2.x and 3.x of the SecurID application is that the numbers are much larger and split into two groups. Think 14 point font instead of 10.
PushToken Command Line Options
java -classpath PushToken.jar PushToken [options] file
Options:
-e E-mail or device ID of BlackBerry
-h Address of BES host (default: localhost)
-p
Port on which BES is listening (default: 8080)
Examples:
java -classpath PushToken.jar PushToken -h123.45.67.89 -p8765 -ejsmith@company.com token.sdtid
Have you ever received a slew of messages on your BlackBerry, none of which you want or need? One of my BIS accounts receives a moderate amount of spam, all of which is flagged by SpamAssassin with [SPAM] in the subject line. I've tried setting filters at BIS, but they never seem to work. Fortunately there's an easy way to quickly delete all of the offending messages at once.
Step 1 - Searching
From the Mail window open the menu and choose Search. Enter parameters that will find all of the messages you want to delete, and only the messages you want to delete. In my case it's anything with [SPAM] in the subject.
Step 2 - Search Results
Review the search results and make sure they don't contain any messages you do not want to delete. If the results do contain messages you don't want to delete you will need to refine the search parameters to exclude them.
Step 3 - Delete Prior
This is where the magic happens. Select a date heading, open the menu and choose Delete Prior. If a message is highlighted and not a date heading you will not have a Delete Prior option.
In the context of search results, Delete Prior will only delete messages that were found by the search, not everything prior to the date of the first result.
Wait, what about BES users?
No guts, no glory. Go ahead and try it.
If you're more timid, Delete Prior only removes messages from the handheld, not the desktop. I've never tested this with any of the bi-directional sync BIS email options like GMail or Yahoo, so if you're using one of those services you should test first.
Confirm that you want to delete the messages and after a moment you'll see that all of the messages have been deleted and you're free of spam, printer notices or emails from Wiskus. Let's see your iPhone do this!
Lately I've been working a few days a week downtown using my MacBook Pro running Leopard and VMware Fusion. The MBP is off to the right on an iFold stand, and Fusion is full-screen in front of me on a 30" monitor. For input devices I'm using a generic HP USB keyboard and a Logitech MX900 mouse.
By default VMware emulates a generic PS/2 mouse with two buttons and a wheel, which meant that the mouse software I'm using in OS X, ControllerMate, was essentially useless in Fusion.
Luckily there is a hidden setting available for VMware Fusion version 1.1.2 and newer that will enable a virtual USB mouse that passes through up to 6 buttons. The same setting works with VMware Workstation 6, but I'm not sure about older versions. According to VMware this device will be preferred over the PS/2 mouse by the VM.
Edit your Virtual Machine Config
Before making any changes, shut down the virtual machine and quit VMware Fusion. Virtual Machines may be stored in ~/Documents/Virtual Machines.
Command Line
- Open a new terminal (Finder, Go menu, Utilities, Terminal)
- Change directories to ~/Library/Application Support/VMware Fusion/Virtual Machines
cd ~/Library/Application Support/VMware Fusion/Virtual Machines
- Begin editing the .vmx file. With my Boot Camp configuration this is inside of Boot Camp/%2Fdev%2Fdisk0/Boot Camp partition.vmwarevm
nano Boot Camp/%2Fdev%2Fdisk0/Boot Camp partition.vmwarevm/Boot\ Camp\ partition.vmx
- Add the following line anywhere in the file
mouse.vusb.enable = "TRUE"
- Save and exit nano
CTRL+o, Enter, CTRL+x, Enter
- Restart the VM
From the Finder
- Browse to your Virtual Machine folder
<your home directory>/Library/Application Support/VMware Fusion/Virtual Machines
- Open the folder for your VM and drill down through folders until you see a single file (in my case it's called Boot Camp Partition)
- Right click on the file and choose Show Package Contents.
- Right click on the .vmx file and choose Open With, and then Other.
- Select TextEdit to open the file.
- Add the following line anywhere in the file
mouse.vusb.enable = "TRUE"
- Save and close the file
- Restart the VM
