Here’s how:

1. Open the Sametime administrative websphere console
(Start > Programs > IBM WebSphere > Application Server Network Deployment V7.0 > Profiles > stSTMDMProfile1)

2. Navigate to Servers > Server Types > WebSphere Application Servers.

3. Go to STMeetingServer

4. Under Communications, expand Ports and click on Details

5. Select WC_defaulthost and change it to whatever port you like, then click on save and restart the meeting server service.

Not sure if anyone else has experienced this but a customer reported that when they VPN’ed to their office they couldn’t ping a server unless the FQDN (ie: server.domain.local) was used. The customer wanted to reach a server by simply using the host name, exactly as he would when he’s at the office.

Luckily, this is an easy fix. Option 015 DNS Domain name which needs to be specified within DHCP.

So, if your internal domain is mydomain.local just put that domain name in option 015 within DHCP, under the scope options.

For the full compatibility list please see this link:
http://www-01.ibm.com/support/docview.wss?uid=swg27018725

Download it from here:
http://www-01.ibm.com/support/docview.wss?rs=899&uid=swg24025721#FP4

Release notes are here:
http://www-10.lotus.com/ldd/R5FixList.nsf/0/61f6dc55689d10b18525774d0055319a?OpenDocument

Just ran into that issue when I was configuring a BES 5.0.2 server for a customer. Even though the names.nsf replicated to the BES server it still didn’t see my newly created user. To fix this I had to refresh the user list within the BES 5.0.2 administrative console (BAS) — here’s how:

1. Open the BAS (ie: https://you.besserver.com/webconsole/app)
2. Under ‘ Servers and components ‘ expand ‘ BlackBerry Solution topology ‘
3. Navigate to Blackberry Domain -> Component View -> E-Mail
4. Make sure everything is correct under ‘ Domino Server name ‘ and ‘ Address book name ‘
5. Click on ‘ Refresh available user list from company directory ‘

Seeing we have a 10month old baby girl and using a 2.4GHz video baby monitor I’ve been asking myself that exact question.

The monitor was positioned, from her birth up until today, around 3ft from her mounted on the wall. Today I moved it to the opposite wall, which is about 11ft away. To be honest it still doesn’t sit well and I’m thinking about getting rid of it; perhaps I’ll just buy a 900MHz video monitor.

I’ve been doing a lot of reading and simply cannot come to a conclusion. There doesn’t seem to be enough data out there as this technology is fairly new. Just because something is sold at a big chain doesn’t mean it’s OK.

Look at cigarettes, they’re everywhere. Think about when everyone used to smoke, and it was even allowed on airplanes — now you can barely smoke outside a public building.

What do I think you ask. I believe they’re dangerous, period. I don’t want to find out 5-10 years from now that people who used to use 2.4GHz+ (or DECT) baby monitors have increased the chances of (insert one of many diseases here) in their children — would you?

Just to add, please keep your babies away from cell phones, and for the love stop buying your kids cell phone. A child’s skull doesn’t fully develop before they’re 21 years old and will absorb an unsafe amount of radiation. Unfortunately I feel we’re going to have a epidemic on our hands in a few years which is caused by cell phones. I recall reading somewhere it’s going to be around 2030. Makes me really sad that our desire to advance technologically is going to hurt some of us.

Ok, I’m done. It’s late, I’m tired and I’ve already made countless corrections.

Additional reading

http://www.emfacts.com/papers/rncnirp_children.pdf

http://www.emfacts.com/papers/dect.pdf

Please feel free to comment. I’d really like to know what you think.

Please feel free to comment and let me know what you think of this new theme!

Although when I tried to run the VMlite wizard I received this error:

VMLite.exe – Entry Point Not Found
The procedure entry point RTMemCacheDestroy could not be located in the dynamic link library VBoxRT.dll.

To resolve this issue copy the file VBoxRT.dll from “C:\Program Files\Sun\VirtualBox” and put it in “C:\Program Files\VMLite\VMLite Workstation” — easy enough?