Now that Exchange Server 2013 is available, some of you may well be wondering how to publish it to the Internet using Microsoft Threat Management Gateway (TMG) or perhaps the Microsoft Unified Access Gateway (UAG).
The first thing to know is that there is no Exchange Server 2013 publishing wizard, but do not panic as you can instead use the 2010 wizard, and then make some changes described here…Read the blog article from exchange team blog
A new spam campaign using UPS (United Parcel Service) as a social-engineering draw was initiated this week.
The spammed message contains an attachment, detected as TrojanDownloader:Win32/Chepvil.I.
The spam campaign actually started around March 16th 2011. The threat was originally detected as Backdoor:Win32/Hostil.gen!A (was Backdoor:Win32/Hostil.F).
More specific signatures (TrojanDownloader:Win32/Chepvil.I and TrojanDownloader:Win32/Chepvil.J) were added on March 22nd 2011.
Encyclopedia entry – Microsoft Security Portal Updated: Mar 26, 2011 | Published: Mar 25, 2011..Click here for more info
Since Exchange server 2010 SP1 has been released on the 1st of September 2010, its too early for me to roll out on my production environment. “Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBAs. The administrator experience when initially downloading these hotfixes may be a little odd. However, once you download the hotfixes, and receive two of the hotfixes from CSS, you can use the same for subsequent installs on other servers. In due course, all these updates may become available on the Download Center, and also through Windows Update.”. Good to know that Exchange team is closely working on all the issues and updating it. I will wait for another 1 to 2 months for my rollout. For more information http://msexchangeteam.com/archive/2010/09/01/456094.aspx
Also another helpful blog for the SP1 installation… click here
Microsoft Exchange Server 2010 SP1 accepts only ten devices per account – iOS4..more info click here
Problems when installing Exchange 2010 Service Pack 1 on a TMG configured for Mail protection..Click here (Update: A fix for this problem is now available for download as part of Software Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1.)
• The new User Activity report displays the sites and site categories accessed by any user.
• All Forefront TMG reports have a new look and feel.
Enhancements to URL Filtering
• You can now allow users to override the access restriction on sites blocked by URL filtering. This allows for a more flexible web access policy, in that users can decide for themselves whether to access a blocked site. This is especially useful for websites that have been incorrectly categorized.
• You can now override the categorization of a URL on the enterprise level; the override is then effective for each enterprise-joined array.
• Denial notification pages can now be customized for your organization’s needs.
Enhanced Branch Office Support
• Collocation of Forefront TMG and a domain controller on the same server, which can help reduce the total cost of ownership at branch offices.
• When installed on a computer running Windows Server 2008 R2, SP1 simplifies the deployment of BranchCache at the branch office, using Forefront TMG as the Hosted Cache server.
Support for publishing SharePoint 2010
• Forefront TMG SP1 supports secure publishing of SharePoint 2010.
If you have not already done so, I highly recommend you create an SPF record for your domain as this will make it much more difficult for spammers to forge your domain in order to spam domains in other organizations.
Sender Policy Framework..WikiPedia Definition
Creating your own SPF record is a relatively simple process, Microsoft even provides a web-based GUI wizard that will help you do this.. Domain holders need to complete an inventory and publish all IP addresses of their outbound e–mail servers in the DNS zone file. This is an administrative step that requires no changes to an organization‘s e–mail or DNS software. Even if your domain has no outbound e–mail servers, you can help protect your domain from spoofing by publishing an SPF record in the DNS that states this. Microsoft Safety Home Page click here
Implementation Tips for the Sender ID Framework—Creating Your SPF Record..Click here
Sender ID Overview Click here