Trustworthy Messaging Get Started is new technical document from the Microsoft IT Showcase collection, which covers some security methods to protect email messages.
Topics in this guide:
- •Protect an E-mail Message (IRM)
- •Set a Message to Expire (IRM)
- •Digitally Sign a Message (S/MIME)
- •Encrypt Messages (S/MIME)
- •Get a Digital ID (S/MIME)
The Microsoft Junk E-mail Reporting Tool version 1.0 for Microsoft Office Outlook is a neat add-in for Outlook that allows a user to report an e-mail message as junk. This kind of mechanism is already used in Hotmail.
"The Junk E-mail Reporting Tool submits e-mail to Microsoft when you explicitly choose to do so. If you receive a junk e-mail and want to report it to us for analysis, first select the e-mail in Outlook and then click the junk e-mail button on your tool bar. You will see a pop-up window asking whether you want to report the selected e-mail to Microsoft and its affiliates. When you click “Yes” to confirm that you’d like to report the selected e-mail as junk e-mail, the junk e-mail will be deleted from your Inbox and sent to FrontBridge, a Microsoft company, for analysis to help us improve the effectiveness of our junk e-mail filtering technologies."
The messages reported this way will be sent to email@example.com, where probably they will be used to more accurately define what is or what is not unsolicited commercial email
So, what is "Centro" you ask………..?
I am glad you asked….
We are looking for a few good testers to help influence the direction of this new Microsoft® Windows Server Solutions Product. Do you have three 64 bit machines that you can spare to test some of the most exciting technology Microsoft is working on? I know the system requirements are a daunting one, but this is the only way we can test "Centro". So, if you are already on the Longhorn Beta or the Exchange Beta, then you are already two thirds of the way there.
The "Centro" Product team is looking to you to help test the Beta of "Centro". “Centro” is the code name for a new Microsoft® infrastructure solution that will help midsize businesses with less than 250 PCs in their environment. Centro will bring together key server products for midsize businesses, including Windows Server “Longhorn,” Exchange Server 2007 and security technologies, plus a new, integrated management experience. Centro is designed for IT professionals in midsize companies, helping them with server technologies that are easier to purchase, install and manage.
If you are interested in joining the "Centro" Beta please go to http://connect.microsoft.com click on Invitations sign in with your Windows Live ID (Passport ID) and enter the following invite ID; Extr-GHBC-JCJM. You will be asked to take a short Survey. Once you complete the survey look for an email from MsftConn@microsoft.com. If you don't already trust this address, please add it to your trusted email addresses.
Source: The SBS and Centro Community Lead Blog
published once again the list of webcasts for November. Here are the links for the ones we really like:
In an attempt to promote the use of Sender ID, Microsoft is making this e-mail security technology available under its Open Specification Promise (OSP) program. This means that users will be able to implement, commercialize and modify Microsoft's patented e-mail authentication technology without having to sign a licensing agreement.
"REDMOND, Wash. — Oct. 23, 2006 — Microsoft Corp. today announced that its Sender ID Framework specification for e-mail authentication is now available under the company’s Open Specification Promise (OSP), an irrevocable promise to every individual in the world that they can make use of the covered Microsoft® technology easily and for free. This is another step forward in the company’s commitment to delivering interoperability by design."
Related links:Microsoft Promotes Interoperability for E-Mail Safety Solutions With Sender ID Framework Microsoft's Sender ID Spec Now Freely Available Microsoft sets Sender ID free
Internet Explorer 7, which was released last week, can cause a little problem when used with Outlook Web Access (OWA). To resolve this issue, there's a new patch available to download for Exchange Server 2003 SP2.
"This update resolves an issue where the Outlook Web Access (OWA) form would stop responding when you compose a message using the S/MIME control on a client running Internet Explorer 7.0 and accessing a mail server running Exchange Server 2003."
Here are the links for the patch and for the corresponding KB article:
Microsoft has just released the October update for the Outlook 2003 Junk E-mail Filter.
"This update provides the Junk E-mail Filter in Microsoft Office Outlook 2003 with a more current definition of which e-mail messages should be considered junk e-mail."
The update is available here
or you can use Microsoft Update
. As usual the update comes with the corresponding Knowledge Base article:
Technorati : outlook, junk email, spam
Del.icio.us : outlook, junk email, spam
Going 64-Bit with Microsoft Exchange Server 2007 is a Microsoft IT Showcase that Microsoft has made available recently.
"Almost two years prior to the Microsoft® Exchange Server product group's decision to support Microsoft Exchange Server 2007 on the 64-bit platform only, the Microsoft Information Technology (Microsoft IT) group began to migrate from 32-bit to 64-bit server hardware. All server computers purchased for messaging purposes after the year 2004 are 64-bit systems and suitable for Exchange Server 2007. By running the new Exchange Server version on the 64-bit platform, Microsoft IT can keep pace with ever-increasing performance expectations, raise mailbox quotas by up to a factor of 10, lower storage costs, and eliminate tape backups to save an additional $5 million U.S. per year."
Windows PowerShell Week, a series of five Webcasts to be held November 6 – 10, 2006 on TechNet. These Webcasts will provide you with a thorough introduction to Windows PowerShell.
|And Now for Something Completely Different:|
Introducing Windows PowerShell
You’ve probably heard by now about this new technology from Microsoft first called “Monad” and now officially named Windows PowerShell. What is this? Do I want to learn this? Do I have to learn this? Where do I get it? How does it work? Not to worry, the Scripting Guys are here to answer your questions. In this first of five Webcasts you’ll be introduced to Windows PowerShell and given an overview of how it works and what it’s all about.
Monday November 6, 2006
|One Cmdlet, Two Cmdlet, Three Cmdlet, Four:|
An Introduction to Windows PowerShell Commands
"Doeth the Eagle mount up at thy commaund?" No, that’s not a typo; apparently, that's how the word command was spelled back in the 1700's. Boy, how things have changed: the word is now spelled Cmdlet, or at least it is if you're a Windows PowerShell user. In this webcast the Script Guys explore these new beasts known as Cmdlets, the heart and sound of Microsoft’s new command shell/scripting technology.
Tuesday November 7, 2006
|Objects, Objects Everywhere:|
Working With Objects in Windows PowerShell
One of the coolest new features introduced by Windows PowerShell is the ability to work with objects directly from the command line. Although WSH scripters are somewhat familiar with the concept of objects, as a Windows PowerShell user you need to live and breath objects. In this webcast, the Scripting Guys explore all things object in Windows PowerShell. If you listen carefully and don't speak out during the presentation, they’ll even help you instantiate an itty-bitty .NET object for you to call your own.
Wednesday November 8, 2006
|New Kid on the Script Block:|
Writing Scripts with Windows PowerShell
Yes, Windows PowerShell is a great tool for working at the command line; however, it’s an equally good tool for writing scripts. In day 4 of Windows PowerShell week, the Scripting Guys introduce you to the fine art of writing scripts with Windows PowerShell.
Thursday November 9, 2006
|Amazing But True:|
Things You Never Dreamt You Could Do With Windows PowerShell
In this, this fifth and final Windows PowerShell Week webcast, you’ll see definitive proof that the Loch Ness monster exists; you’ll meet a man who was abducted by aliens; and you’ll hear from a real, live ghost. But that’s nothing: just wait until you see some of the incredible things that can be done with Windows PowerShell.
Friday November 10, 2006
Some time ago, I participated in a project where I had to do a domain rename. Domain renames are possible since the release of Windows Server 2003, although it was not possible to perform the rename operation if an Exchange Organization was deployed in the AD Forest. This constraint was soon dropped with the release of XDR-Fixup, a tool that fixes Exchange attributes in the AD after a rename operation.
But there are still some pre-requisites:
- The functional level of the AD Forest must be Windows 2003;
- You must have Enterprise Admin privileges;
- All the DFS Root Servers must have Windows 2000 SP3 or above;
- Exchange must not be installed on a DC;
- Exchange 2003 SP1 or later.
In my case, we found that we had an Exchange Server running on a DC. The solution is to install a separate Exchange server, move all the mailboxes and public folders and then to uninstall the old server. Just running DCPROMO isn't supported.
After correcting that, the rename operation went really smoothly. But don't be fooled, a domain rename operation shouldn't be taken lightly. Although I wouldn't call it complex, please make sure you read all the documentation provided with the rename tools. Also consider all the other possibilities before deciding to do a domain rename.
As a curiosity let me tell you that when I told Microsoft Portugal I was going to do a domain rename, they didn't show much confidence on their own tools.
Here are the links with the tools and documentation. Try this in a test environment, it's fun [;)]