Today i had the chance to test out both of these new HD 720p cameras. The Tandberg one is a high end business camera targeting the same people and the Microsoft LifeCam cinema is targeting the consumer market, this is mainly seen in the physical world, like the package the camera is delivered in, the material, size and weight. The Tandberg cam is priced like 5,5 times higher though. And here are some screenshots from both of them to see if you think its worth it.
The LifeCam cinema is a lot smaller and not as heavy as the TB cam.
The first one is from the LifeCam cinema and as you can notice its in widescreen and the TB one is zoomed in and focused a little different so it might not look fair but this is the default settings for both of the cams.
For another more in detail test check out this blog post
Microsoft shows of a prototype of a next generation office wall computing, combining a fully interactive wall, a surface computer, a interactive assistant and some cool UC features to come.
Well this is a lot cooler then just a telepresence solution, but you have to check it out by yourself to believe it.
So check out the demo of it here at the istartedsomething website
I have newer really understand the Communicator Web Access Listening Port but iwe just put it to a random port above 1024 and it worked if the port wasn’t used.
And the setting didn’t get any good documentation either but finally Jeff Schertz blogged about it so check out his blog to know everything about it.
The PreCallDiagTool is an application that reports expected audio quality. The tool should be installed on any desktop or laptop PC that suffers from inconsistent network connection quality (i have heard that it has to be in the domain to work fine). The PreCallDiagTool provide a quick check of the current network conditions and also preserve a history of quality data.
Download the 32 bit version of the PreCallDiagnostic
http://www.microsoft.com/downloads/details.aspx?FamilyID=f16ab4c2-353f-4c9b-b353-22a656c03c9b&displaylang=en
The 64 bit version can be found in the Office Communications Server 2007 R2 Resource Kit.
http://www.microsoft.com/downloads/details.aspx?familyid=9E79A236-C0DF-4A72-ABA6-9A9602A93ED0&displaylang=en
When you install the communicator client on a workgroup machine you would like to save the password in the MOC client, right?
This option is available if you add the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator
“SavePassword”=dword:00000001
When you start the MOC client there is a checkbox enabled to save the password. The password is saved in the following registry key :
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Communicator\AccountPassword
So I’m not sure if you would like to have your password in the registry though…
Anderson Patricio writes in his blog about how to broadcast a message from OCS console, please look at his original blogpost to give credits to him.
But i steal the good stuff for my reference.
The first step is to make sure that the user belongs to the RTCUniversalServerAdmins group.
Second step is to open the command promtp and go to “C:\Program Files\Common Files\Microsoft Office Communications Server 2007 R2” folder and run the following syntax and hit enter.
LCScmd /Server /Action:BroadcastMessage /Role:SE /Message:"Type your message here"
Done, all logged in users will receive the message.