The final session I attended was Deploying & Scaling OCS Group Chat services.
In summary, MS have acquired a product which provides a chatroom facility (similar to IRC), but provides security (AD based) and logging. Whilst does require a separate server to run on than the OCS Messaging server, there is no additional application licensing required.
At present, it does require a separate client, but it does coexist niceley with the OCS client and there is plans to combine the two clients in future.
Some of the examples cited as potential benefit cases is project discussion rooms (because an archive of discussions is made) and global support teams, as members can come online and read the previous 18-24 hours discussions to see what issues/topics were discussed.
-------------------
This is my final blog post from TechEd 2008. See you in Berlin in November 2009!
Friday, November 7, 2008
TechEd 2008, Day 5, 14:45
I attended a session called "A case of the unexplained", presented by Mark Russinovich.
If you've worked with Windows at the technical level for more that a few years, you've probabaly heard of Mark. Or, if not, you've used software he's written. Anything from SysInternals, and much of the stuff in the Resource Kits, he's had a hand in it somewhere.
The session today was demonstrating how to diagnose performance problems, application crashes and the dreaded blue screen of death. There's a useful toolset from MS SysInternals which (when used correctly) can help you identify which software package, even down to which DLL, is causing problems and why.
It's heavy techy stuff, and not something we'd expect lower level analysts to do. It also takes a good deal of time and patience. But if a problem occurs often enough, or is critical enough, there are steps we can take.
If you've worked with Windows at the technical level for more that a few years, you've probabaly heard of Mark. Or, if not, you've used software he's written. Anything from SysInternals, and much of the stuff in the Resource Kits, he's had a hand in it somewhere.
The session today was demonstrating how to diagnose performance problems, application crashes and the dreaded blue screen of death. There's a useful toolset from MS SysInternals which (when used correctly) can help you identify which software package, even down to which DLL, is causing problems and why.
It's heavy techy stuff, and not something we'd expect lower level analysts to do. It also takes a good deal of time and patience. But if a problem occurs often enough, or is critical enough, there are steps we can take.
TechEd 2008, Day 5, 11:45
The session I just attended was called "Connecting your world". Whilst it was mainly aimed at consumer grade people, it demonstrated a lot of the new features in Windows Live and LiveMesh, such as mobile blogging and photo tagging, synchronising files via the cloud (to dekstops and Windows Mobile devices, etc.
They also showed some of the new photo gallery and manipulation tools that Microsoft Labs are producing. Photosynth is already in production, but they are intending to have photo stitching and High-Def stitching and viewing intergrated into Vista very soon. If you want to know more about these, I will no doubt be demoing them to the Mars Photography club very soon.
Final part was a demo of the new features in Virtual Earth, and World Wide telescope, which have both recently been upgraded. For VE, it's mainly US data that has upgraded.
They also showed some of the new photo gallery and manipulation tools that Microsoft Labs are producing. Photosynth is already in production, but they are intending to have photo stitching and High-Def stitching and viewing intergrated into Vista very soon. If you want to know more about these, I will no doubt be demoing them to the Mars Photography club very soon.
Final part was a demo of the new features in Virtual Earth, and World Wide telescope, which have both recently been upgraded. For VE, it's mainly US data that has upgraded.
TechEd, Day 5, 10:15
Just attended a session on Certificate Management in Exchange.
Not much to report - it was predominantly about SSL certificates when publishing Outlook Web Access or Exchange RPC-over-HTTPS. Having our own certificate authority certainly makes it easier!
Not much to report - it was predominantly about SSL certificates when publishing Outlook Web Access or Exchange RPC-over-HTTPS. Having our own certificate authority certainly makes it easier!
Subscribe to:
Comments (Atom)
Posts
