When launching Communicator Mobile on Vista RTM with Windows Mobile Device Center Beta 3 you get this message –
Current version of ActiveSync is not supported. Please install Microsoft ActiveSync 4.1 ….
The workaround is to create an administrative install of Office Communicator like this –
msiexec /a CommunicatorMobile_PPC50.msi
set-psdebug -trace 1
# f1 is a normal function with a switch parameter
function f1([switch] $showOutput) {
if ($showOutput.isPresent) {
"f1"
}
}
# f2 is a function with a switch parameter defaulted to present
function f2([switch] $showOutput=[switch]::present) {
if ($showOutput.isPresent) {
"f2"
}
}
# f3 is a function with a switch parameter defaulted to true, this gives the same result
# as using [switch]::present
function f3([switch] $showOutput=$true) {
if ($showOutput.isPresent) {
"f3"
}
}
# run f1, no output shown
f1
# run f1, show output
f1 -showOutput
# run f2, show output
f2
# run f2, show output
f2 -showOutput
# run f2, no output
f2 -showOutput:$false
# run f3, same behavior as f2
f3
f3 -showOutput
f3 -showOutput:$false
# Show the acceptable values for a switch parameter
f2 -showOutput:no
# f2 : Cannot convert value "System.String" to type "System.Management.Automation.SwitchParameter",
# parameters of this type only accept booleans or numbers, use $true, $false, 1 or 0 instead.
# At line:1 char:16
# + f2 -showOutput:n <<<< o
The IM, Presence, Voice and Video functionality of the RTC 1.3 APIs work on Vista RTM. While audio and video quality are acceptable the quality level does not match what users using Communicator 1.0 have experienced in the past.
Application sharing and white boarding require Windows NetMeeting, which Vista has replaced with Windows Meeting Space so these features of the RTC 1.3 APIs will not function on Windows Vista.
This Support WebCast discusses the purpose of certificates in Microsoft Office Live Communications Server 2005 and describes how to appropriately deploy certificates for common scenarios. These scenarios include Remote Access, multiple pools, Director or Access Proxy arrays, Microsoft Office Communicator Web Access, and public instant-messaging (IM) connectivity (PIC).
This document identifies supported configurations for Microsoft® Office Live Communications Server 2005, Live Communications Server 2005with Service Pack 1 (SP1), and Microsoft Office Communicator Web Access.
IMPORTANT: Please read the update documentation, referenced in the "To install this download" section on this page, BEFORE applying this Beta 2 Technical Refresh update. The documents list several steps that you must complete prior to installation to ensure a successful update. This is NOT a single click update.
# The registry key
I have tried to figure out, how to either reorganize the entries or generate a new console based on data held in Excel - but failed so far pursuing this path.
One of my customers pointed me to an alternative: visionapp Remote Desktop from the German company visionapp. I have used it for a while now - and all the drawbacks are gone.
Thank you very much visionapp!
I "of course" use Vista as my primary OS by now, so I will have to wait for the soon-to-be released RC1 of Windows Vista.
You can check Paul Thurrot's review of RC1 here
This is a tutorial on how to setup calling to/from MS LCS 2005 using SER and Asterisk. In this case LCS is acting as the IM/Presence/VoIP server, SER converts protocols TCP2UDP and Asterisk is a SIP to ISDN gateway. This setup allows for outbound calls from Microsoft Office Communicator – OC to a normal telephone and inbound calls from a normal telephone to Microsoft Office Communicator - OC. This also allows you to access services provided by Asterisk such as Meetme Conferencing. You can also use Windows Messenger 5.1 instead of OC client.
function apod {
param([int] $days=1) # show latest picture by default
$baseurl="http://antwrp.gsfc.nasa.gov/apod/"
# create IE COM object
$ie = new-object -com internetexplorer.application
# create .net object
$webclient = new-object system.net.webclient
# date manipulation
$date=[datetime]::now
$date.AddDays(1) # start tomorrow as the loops starts by subtracting a day
$ie.fullscreen=$true
$ie.visible=$true
# You may have to press the window in the taskbar to make it appear
# An easy way to do a for loop - could have used for, but as said this is easier
1..$days | % {
# back one day
$date=$date.AddDays(-1)
# construct url
$url=$baseurl+"ap" + $date.tostring("yyMMdd") + ".html"
$url
# get HTML page
$html = $webclient.downloadstring($url)
$html.length
# Pick up the link the picture has - links to the high resolution version
# I want to display
# This is not idiot proff coding - but, hey, scripts are easy to change
$html -match '<a href="([^"]*)">\W*<img'
$matches.count
# get the value matching the pattern in parenthesis
$img=$matches[1]
$img
# show high resolution picture
$ie.navigate($baseurl+$img)
# wait for IE to load picture
while ($ie.busy) {sleep -s 1;"busy"}
# give me 10 seconds to enjoy the picture
sleep -s 10
}
# shutdown IE
$ie.quit()
$ie=$null
# wish list: load pictures overlapping (but keep presentation interval)
# wish list: include some kind of fancy transition
# wish list: pick out the explanation and present it in some way
# add our own...
}
function workpad {
$global:workpad = "$env:temp\workpad.ps1"
"Start workpad - execute with '. $workpad'"
notepad $workpad
}
function execute-workpad {
param([boolean]$executeFirst=$false) if ($executeFirst) {
$oldLastWriteTime=[datetime]"2000-01-01"
}
else {
$oldLastWriteTime=$(get-childitem $workpad).lastwritetime
"Waiting for change.."
}
while ($true) {
$lastWriteTime=$(get-childitem $workpad).lastwritetime
if ($lastWriteTime -eq $oldLastWriteTime) {
start-sleep -s 1
}
else {
"File changed - executing"
""
. $workpad
""
"Waiting for change.."
$oldLastWriteTime=$lastWriteTime
}
}
}
Designed for both beginners and advanced users, VistaBootPRO can be used to make "cosmetic" changes to the Windows Vista boot Menu such as changing the name of the Operating Systems shown in the boot menu and make advanced "functional" changes like adding an Operating System to the boot menu and repairing the Windows Vista boot configuration data. Advanced settings include backing up and exporting your boot loader configuration and modifying various details for the entries. Included in this latest release are additional features, including a built-in help file and more advanced boot configuration options. VistaBootPRO 2.0 has been completely rewritten using Microsoft C# for improved stability and performance.
When deploying Instant Messaging with Live Communications Server in your company you of course expect to get enterprise degree service levels out of it.
But what happens when you mix a consumer based service (Like Yahoo, MSN and AOL) with an enterprise level deployment of LCS with PIC federation?
Well for me the answer is obvious you get a Consumer degree service level out of it - and this is also what my experience shows me.
What is important here is that if you are a customer or a consultant talking to customers/decision makers, then its worth to emphasize the point that PIC isn't an enterprise level service.
Also if you are implementing and/or troubleshooting PIC then its worth to look at at the LCS PIC troubleshooting posting.
- Microsoft Outlook Improvements: Resolves issues relating to error code 85010014.
- Proxy/DTPT interaction Improvements: Improved auto configuration of device Connection Manager settings when desktop has no proxy path to the internet.
- Improved Desktop Pass Thru behavior with ISA proxy failures.
- Partnership improvements: Better resolution of multiple devices with the same name syncing with the same desktop.
- Connectivity Improvements: Better handling of VPN clients (resolve unbinding of protocols from our RNDIS adapter). New auto detection of connectivity failure with user diagnostic alerts.
Also there's a nice little troubleshooter tool, that will check your computer for problems and, given the pemission to do so, send the results to Microsoft.
It still seem to have a problem with setting up the synchronization of tasks directly with the Exchange Server from ActiveSync, this still needs to be setup from the device itself (On a new/wiped device that is, if it already has been setup, it recognizes it correctly).
For some reason, the default setup does not work. The default is to open up Pocket Internet Explorer with a file://, but then PIE does not show the picture and whenever you try to do something, focus is forced back to PIE. Battery out&itt seems the only solution out of that…
Well, if you associate JPG with the picture viewer used by the camera app, everything works.
To make the association, follow these steps -
Have fun!
The interesting development here is the move towards integration of the desk and mobile phone with Office Communicator and also the integration of Live Meeting into Live Communications Server (And also the Ringcam now called "Microsoft Office RoundTable" is pretty nifty. I will be back with further info in the upcoming days, depending on how much information is disclosed publicly this evening.
I was curious - not for the uncensored videos - I live in a country that liberated porn in 1969, so nothing is censored here - but for the funny graphics. Using the mouse, I realized that it was actually text, no a picture. The text is used for drawing larger letters, just like the banner pages on a line printer. I remember creating such a program once in Cobol...
Anyway I selected a line of text before taking the screen shot as you can see from the blue line. To get into more detail, I copied all the 'uncensored' lines, pasted them into notepad and isolated the U - to make this more readable for you -
As you can see, the picture is drawn from different letters. I wonder how a antispam product will be able to detuct this kind of message, containing no 'nasty' word. I fact, the big letters could be made up of non-spamish sentences.The company itself has turned into that thing it most hated (read:
IBM)
The bad news, then, is that UAP is a sad, sad joke. It's the most annoying feature that Microsoft has ever added to any software product, and yes, that
includes that ridiculous Clippy character from older Office versions.
On Media Center: It's a horrid update to a wonderful bit of software, an ugly stepchild of beautiful parents.
Feature complete, my butt
OK, let's not get silly here. I don't hate Windows Vista ... That's not
horrible. It's just not what was promised.
cscript lcsSendmsg.vbs administrator@managenet.com.au
"Hello world how are you doing”
You can find it hereA simple instant messaging (IM) client written in JavaScript.
A simple instant messaging (IM) client written in C#.
A C# application that receives events from Communicator Web Access and displays them, as well as the methods that are being sent to the server, in JSON format.
"What’s the deal with people you have never met before IMing you? This is analogous to interrupting a potentially important conversation (let’s not pretend all of my conversations are important but some of them are...some are even important AND interesting). In my opinion, IMing basically says, “I know you well enough to do this” (among friends) or “this is urgent” (among business associates). I cannot tell you how many times I receive IMs that fall into neither category. When a simple e-mail would suffice, IM is chosen for the immediacy (of the sender) without regard to the time of the receiver."
In this article we'll go over the following procedures: Create the HTTP/HTTPS Access Rule to Deny Access to MSN Messenger; Configure the User Group Exception and the HTTP Security Filter on the Deny Rule; Create the Allow Rule for the Excepted Users.
HMC 3.5 Feature Pack One includes additional resource management feature capabilities and some partner-requested solution fixes for the Hosted Messaging and Collaboration version 3.5 solution. It is strongly recommended that any service provider deploying Hosted Messaging and Collaboration version 3.5 download and install this feature pack, once they have installed HMC version 3.5.
