I've been very loyal to NetNewsWire for a long time. Whether it be NewsGator (a RSS plugin for Outlook), FeedDamon (an RSS feedreader app for Windows, NetNewsWire on the iPhone, or NetNewsWire on the Mac.

I needed a quick and dirty method to add database copies to other servers in an Exchange 2010 Database Availability Group (DAG).  I had three servers, each with 10 databases.  Each one of those databases should have a copy on the other two servers. 

Now, this is painful if you have to use the GUI to do it – not that it takes a lot, but it’s time consuming.  The Add-MailboxDatabaseCopy cmdlet is very helpful in PowerShell, but still I wanted to automate it since my naming conventions were pretty standard.

So, I wrote a PowerShell script to automate this process.  Essentially, the script has a few variables and I dome some loop magic to drop everything into place. 

$servers = "E2K10MBX01", "E2K10MBX02", "E2K10MBX03"

$databases = "DB1", "DB2", "DB3", "DB4", "DB5", "DB6", "DB7", "DB8", "DB9", "DB10"

foreach($database in $databases)

{

       foreach($server in $servers)

       {

              foreach($copyserver in $servers)

              {

                     "Adding mailbox copy for $server-$database to $copyserver..."

                     Add-MailboxDatabaseCopy -Identity $server-$database -MailboxServer $copyserver -ErrorAction "Continue"

              }

       }

}

This script is quick and dirty for a lab environment.  Keep in mind that this doesn’t do any error checking and there is no validation to see if a database is already homed to a server.  This just uses the cmdlet to try to create the database copy; if it is successful, you’re good to go.  If it fails, the script just keeps on rolling.  No harm, no foul.

A couple of months back I wrote a post on how to automatically install pre-requisites for Exchange 2010 on a Windows 2008 (including R2) server.

I specifically talked about a method for doing this with ServerManagerCmd.exe, which is included with Windows Server 2008.  However, in Windows Server 2008 R2, ServerManagerCmd is deprecated and the recommended method is to use PowerShell (as pointed out by my buddy, Josh). 

The Add-WindowsFeature cmdlet in PowerShell provides the capability to add individual Windows features directly from a script.  You can use Get-WindowsFeature to obtain a detailed list of available features, ones that are installed, and their “official” name if you wish to install them via PowerShell.

To install the required pre-reqs for Exchange 2010, from a PowerShell prompt, be sure to add the Server Manager module so the Add-WindowsFeature and Get-WindowsFeature cmdlets are available.

Import-Module ServerManager

Once you have imported the module, then you can use Add-WindowsFeature to take care of the rest.

Add-WindowsFeature -Name RSAT-ADDS-Tools, RPC-over-HTTP-proxy, NET-HTTP-Activation, Web-Dyn-Compression, Web-Windows-Auth, Web-Digest-Auth, Web-Basic-Auth, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-ISAPI-Ext, Web-Server -Concurrent

I don’t normally follow politics, but my own Senator from the state of Minnesota, Amy Klobuchar and other senate colleagues introduced a bill today that would limit the amount of cell phone service provider could charge in early termination fees.

The timing is perfect since Verizon recently announced that their customers who were smartphone users would have to pay in upwards of $300 if they prematurely ended their relationship with the provider.  How ridiculous!

Several years ago, I did pay Verizon $175 to end our relationship. 

“Changing your wireless provider shouldn’t break the bank,” said Klobuchar. “Forcing consumers to pay outrageous fees bearing little to no relation to the cost of their handset devices is anti-consumer and anti-competitive.”

I have to agree.  Instead of spending the money on litigation with AT&T, both carriers should put that money towards getting their networks in better shape, especially AT&T.  The iPhone has been a goldmine for AT&T, but their network has subsequently suffered and become unbearable to use.  Between dropped calls and general coverage issues, I can barely stand to keep their service at this point.  Most customers can’t afford to switch carriers – and I’m not talking about those who bought an iPhone.

According to Senator Klobuchar’s website, the bill would:

- Prevent wireless carriers from charging an ETF that is higher than the discount on the cell phone that the wireless company offers consumers for entering into a multi-year contract.  For example, if a wireless consumer enters into a 2-year contract and receives a $150 discount with the contract, the ETF cannot exceed $150.

- Require wireless carriers to pro-rate their ETFs for consumers who leave their contracts early so that the ETF for a two-year contract would be reduced by half after one year and pro-rated down to zero by the end of a contract term.

- Require wireless carriers to provide “clear and conspicuous disclosure” of the ETF at the time of purchase.

- Require monthly billing statements to clearly state the pro-rated fee customers would be charged if they terminate their contracts before the end of the next billing cycle.

I think most customers are pretty loyal to their carriers.  Most customers see an average bill between $90-$200/month.  Your customers are paying plenty to stay connected – if you as a carrier can’t get the job done, then the customer should have the right to go somewhere that can.

If you’re interested in more about the bill, check out Senator Klobuchar’s press release.