Webinar: How to Drive User Adoption When Migrating #Exchange Public Folders to SharePoint

This looks interesting

This webinar is for you if your organization has made the decision to move from Exchange Public Folders to SharePoint, but you’re still wondering: “how do we make this transition as painless as possible for our end users?” If you’ve started down this path, you may already realize that Microsoft Outlook does not support 2-way synchronization with SharePoint. So, how can you recreate the Exchange Public Folder experience for your users in SharePoint?

http://blogs.officezealot.com/legault/archive/2010/04/15/21725.aspx

#Powershell script to move #Exchange 2010 Databases back to Perference 1

#Exchange2010

So if you paying attention and saw in my previous post, you can check the database ActivationPreference. [#Powershell script to check #Exchange 2010 Database Perference]

Well this script goes one step further and actually moves a database back to ActivationPreference #1 it is not on it!

Again, it’s another one liner

get-MailboxDatabase | Sort Name | FOREACH {$db=$_.Name; $xNow=$_.Server.Name ;$dbown=$_.ActivationPreference| Where {$_.Value -eq 1};  Write-Host $db “on” $xNow “Should be on” $dbOwn.Key -NoNewLine; If ( $xNow -ne $dbOwn.Key){Write-host ” WRONG” -ForegroundColor Red; Move-ActiveMailboxDatabase $db -ActivateOnServer $dbOwn.Key -confirm:$False}ELSE{Write-Host ” OK” -Foregroundcolor Green}}

Enjoy

#Powershell script to check #Exchange 2010 Database Perference

#Exchange2010

So we all should know about Exchange Server 2010 Database Availability Groups (DAG).  Now when you add server to a DAG you assign an ActivationPreference number to each server.

The ActivationPreference parameter value is used to break ties during the automatic database activation process when multiple passive mailbox database copies meet the same criteria for activating. When multiple database copies meet the same criteria for activation the copy assigned the lowest activation preference number will be activated. The value for ActivationPreference is a number equal to or greater than 1, where 1 is at the top of the preference order. The position number cannot be larger than the number of database copies of the mailbox database plus 1.

You would also know that Exchange handles the DAG and will failover databases to other servers in the DAG that have a database copy.

Now this is cool and works like a dream, but what if, as in my case, you actually want the database to be on a preferred server?

Well I knocked up this one liner to check it!

Get-MailboxDatabase | Sort Name | FOREACH {$db=$_.Name; $xNow=$_.Server.Name ;$dbown=$_.ActivationPreference| Where {$_.Value -eq 1};  Write-Host $db “on” $xNow “Should be on” $dbOwn.Key -NoNewLine; If ( $xNow -ne $dbOwn.Key){Write-host ” WRONG” -ForegroundColor Red; }ELSE{Write-Host ” OK” -Foregroundcolor Green}}

Enjoy .. let me know what you think

Patch Tuesday come to #Exchange – Microsoft Security Bulletin MS10-024

#Exchange2010  Vulnerabilities in Microsoft Exchange and Windows SMTP Service Could Allow Denial of Service (981832)

http://www.microsoft.com/technet/security/Bulletin/MS10-024.mspx

This security update resolves one publicly disclosed vulnerability and one privately reported vulnerability in Microsoft Exchange and Windows SMTP Service. The more severe of these vulnerabilities could allow denial of service if an attacker sent a specially crafted DNS response to a computer running the SMTP service. By default, the SMTP component is not installed on Windows Server 2003, Windows Server 2003 x64 Edition, or Windows XP Professional x64 Edition.

The security update addresses the vulnerabilities by correcting the manner in which SMTP parses MX records and the manner in which SMTP allocates memory for interpreting SMTP command responses.

QUEST SOFTWARE SUPPORTS MICROSOFT COMMUNICATIONS SERVER “14”

#OCS Now this is ahead of the game

ORLANDO – VoiceCon 2010 – March 22, 2010 – Quest Software, Inc.  (Nasdaq: QSFT) today affirmed its commitment to Microsoft Corp.’s unified communications strategy as a Microsoft Gold Certified Partner by announcing that Quest MessageStats® will support Microsoft Communications Server “14.” MessageStats is a messaging reporting and analysis tool that reduces the complexity of unified communications reporting using a single interface.

MessageStats will extend the built-in Call Detail Record (CDR) capabilities of Microsoft Communications Server “14” by providing internal reporting for billing and chargeback. This will allow customers to calculate cost ownership of Microsoft Communications Server “14”, chargeback billing, and usage, which will enable easy trending and analysis.

#vmware vSphere PowerCLI Commandlet Poster

#Powershell

Funky  … http://d3planet.com/rtfb/2009/10/06/vsphere-powercli-commandlet-poster/

Pablo Roesch, VMware, has put out a poster that their marketing department did, that has a listing of the PowerCLI commandlets.  This is a very useful tool for anyone working in PowerShell using the VMware Toolkit for Windows.

http://d3planet.com/rtfb/files/2009/10/powercli-poster.pdf

#Exchange Server 2010: Administrator Audit Logging

#Exchange2010 #powershell

You seen this, it’s well funky, and give you the opportunity to “monitor” what people are doing to YOUR exchange system! .. Administrator audit logging in Microsoft Exchange Server 2010 enables you to create a log entry each time a specified cmdlet is run. Log entries detail what cmdlet was run, which parameters were used, who ran the cmdlet and what objects were affected.

What Gets Audited
Cmdlets that are run directly in the Exchange Management Shell are audited. In addition, operations performed using the Exchange Management Console (EMC) and the Exchange Web management interface are also logged because those operations run cmdlets in the background.

Get cmdlets aren’t logged. Audit logging is intended to show what actions have been taken to modify objects in an Exchange organization rather than what objects have been viewed.

Audit Configuration
Ideally you should create an audit mailbox to capture all these events

The following commands have been executed to enable auditing:

Set-AdminAuditLogConfig -AdminAuditLogCmdlets *
Set-AdminAuditLogConfig -AdminAuditLogParameters *
Set-AdminAuditLogConfig –AdminAuditLogMailbox Audit.Mailbox@nodomain.com
Set-AdminAuditLogConfig -AdminAuditLogEnabled $True

The Output
Using the mailbox you will see an email with this content:

Cmdlet Name: Update-MailboxDatabaseCopy
Object Modified: Mailbox Database 9999999999Exchange01
Parameter: Identity = Mailbox Database 9999999999Exchange01
Parameter: DeleteExistingFiles = True
Parameter: Network =
Caller: UserAccount
Succeeded: True
Error: None
Run Date: 08/04/2010 17:04:58 UTC

And remember, BIG BROTHER is always watching!