Saturday, November 21, 2009

Welcome home Luke!


For those of you that have been following my search for a dog, meet "Luke", my new Siberian Husky. He turned 10 weeks old yesterday and is already 20 pounds! He loves to eat, play, run, and whine like crazy when he has to go in his crate. He is sleeping next to my chair right now while I work on the last chapter for my E2K10 book.

Luke descends from top champions on both sides of his family. His mother Laney is, a beautiful black-and-white with blue eyes in her family. His father, Quinn, is where the red comes from. Quinn's grandfather is Am/Can Ch Innisfree's Fire and Frost CGC, the only Siberian Husky to win the Westminster dog show. He came to Jes Kennels in Hawaii from Innisfree, probably the most famous Siberian Huskey kennel in the world.

Luke, of course, is just my pet. I am not going to show nor breed him. That is my agreement with Nikki, the breeder. Though I have had many dogs in my life including 3 Alaskan Malamutes, I feel like a kid with his first dog.

Thursday, November 12, 2009

Using a specific domain controller with the Exchange Management Shell

Someone asked me today if it was possible to configure the Exchange 2007 Management Shell to use a specific domain controller rather than just picking the closest one. I have been unable to find a way to get all cmdlets within the PowerShell to use a specific domain controller, but most of the EMS cmdlets do support the -DomainController option. So, update a mailbox's display name and use a specific domain controller, you could use a command like this:

Set-Mailbox -DisplayName "Jim McBee" -DomainController hnldc01.somorita.local

Labels:

Exchange 2010 DAG latency between members

A question came up today in a Connections session as to what was the maximum *supported* latency between Exchange Server 2010 Database Availability Group (DAG) members. According to this TechNet article, it is 250ms.

"Database copies aren't supported between Mailbox servers with round trip network latency greater than 250 milliseconds (ms)."

I'm guessing that it would *work* with higher latencies, but I don't recommend ever exceeding the support boundaries.

Labels:

Wednesday, November 11, 2009

Exchange 2010 Storage Calculator

Thanks to the efforts of Microsoft's Ross Smith, the Exchange 2010 Storage Calcuator is now available. This is a very useful tool when planning things such as storage requirements, i/o, Mailbox servers, Hub Transport, and Client Access servers.

Tuesday, November 10, 2009

Microsoft Exchange Server 2010 Unleashed

Props to Rand Morimoto, Michael Noel, Chris Amaris, Andrew Abbate, and Mark Weinhardt for their timely release of Microsoft Exchange Server 2010. It actually came out last month; I have not yet had an opportunity to review it, but congrats to Rand and his team for getting this out with the release of the product. That is not a simple undertaking.

Monday, November 09, 2009

Exchange Server 2010 available for Volume Licensing customers

Exchange 2010 was made available for download on the volume licensing site today!

Monday, October 12, 2009

Exchange Server and the software business

In an Exchange Team blog, I saw a really interesting tidbit of information. If Exchange Server was a standalone business, it would be the 9th largest software company in the world!

The other interesting tidbit was that, according to a Ferris research, the Lotus Notes market share within enterprise businesses has dropped to 10% while Exchange is at 65%.

Sunday, September 20, 2009

AOL is not accepting e-mail...

"AOL is not accepting e-mail from my server" "Road Runner is not accepting mail from my server".... etc Sound familiar? This is a pretty common question in the newsgroups. I have been battling this issue myself with one of my own customers.

Some ISPs (Time Warner's companies are notorious for this) check to see if your mail server has a PTR record. Does your server have an PTR record for it's public IP address? You can easily check here:
http://www.mxtoolbox.com/diagnostic.aspx

Plug in your IP address in here to see a fairly comprehensive test. Ideally, your PTR record name (eg mail.somorita.com) should match the HELO or EHLO banner that your mail server sends out. Some mail servers will even reject your message if the EHLO banner does not match your PTR record. Fortunately, most don't.

Now comes the hard part: how do you assign a PTR record for your public facing IP address? You usually don't. The owner of the IP address must do that. That is almost always your ISP. Contact your ISP, tell them that you need a PTR record for your public IP and tell them what you want it to be, such as mail.somorita.com.

Tuesday, September 08, 2009

Enphase Inverter demo and management software demo

One of the solar photovoltaic inverters I'm considering has some pretty neat software that lets you monitor the system as well as individual panels. Take a look at the Enphase software demo.

Monday, September 07, 2009

Sending e-mail as an SMS or text message

Really useful answer by Michael W. on the Microsoft TechNet forums. If you want to send a text message from an e-mail client, most carriers allow you to do this. You send an e-mail message to number@emaildomain. For example, if you want to send a message to a T-Mobile user whose phone number is (808) 555-1234, then you would address the message to 8085551234@tmomail.net Keep in mind that the recipient may have to pay a "per text message" charge. Below are the US carriers. For more, see this link.

UNITED STATES
n@teleflip.com Teleflip
n@message.alltel.com Alltel
n@paging.acswireless.com Ameritech
n@txt.att.net ATT Wireless
n@bellsouth.cl Bellsouth
n@myboostmobile.com Boost
n@mobile.celloneusa.com CellularOne
n@mms.uscc.net CellularOne MMS
1n@mobile.mycingular.com Cingular
n@sms.edgewireless.com Edge Wireless
n@messaging.sprintpcs.com Sprint PCS
n@tmomail.net T-Mobile
n@mymetropcs.com Metro PCS
n@messaging.nextel.com Nextel
n@mobile.celloneusa.com O2 / Orange
n@qwestmp.com Qwest
n@pcs.rogers.com Rogers Wireless
n@msg.telus.com Telus Mobility
n@email.uscc.net US Cellular
n@vtext.com Verizon
n@vmobl.com Virgin Mobile

Sunday, September 06, 2009

Unable to Remove Exchange Mailbox Database or Exchange Server

"I can't remove an Exchange mailbox database" or "I can't remove an Exchange server".
I have seen this question a few times in the online forums recently and this is something that I frequently see myself as I move mailboxes around an Exchange 2003 organization. I usually use the Exchange System Manager to move the mailboxes around. However, one we

Microsoft has a good TechNet article on the process of removing an Exchange Server (or the last old Exchange Server): How to Remove the Last Legacy Exchange Server from an Organization

Another good KB article is You receive a "c1034a7f" error message when you delete a mailbox store: "One or more users currently use this mailbox store"

What I usually do is to add the mailbox database as a column in Active Directory Users and Computers, the go through each of the OUs that contain users and sort by that column. That is the quick and dirty way to do locate the mailbox.You could also perform a Find in ADUC and search for the old mailbox database name, but you do need the DN of the database to do that. Amit Tank recommends this custom query for ADUC:
(&(mailnickname=*)(msExchHomeServerName=*ServerName*))

Worst case, of course, you can navigate to the Mailbox Database using ADSIEdit and delete it. The following is an example of the path, but you would need to substitute your own organization, admin group, server name, etc...
Configuration -> CN=Services -> CN=Microsoft Exchange -> CN= -> CN=Administrative Groups -> CN= -> CN= -> CN=InformationStore,CN -> CN=

Key error messages:
The component 'Microsoft Exchange Messaging and Collaboration Services cannot be assigned the action "Remove" because: -One or more users currently use a mailbox store on this server. These users must be moved to a mailbox store on a different server or be mail disabled before uninstalling this server.

Or
You cannot remove the mailbox database because there are still mailboxes on that store.

Saturday, September 05, 2009

My home project - Using less electricity

I'm now on a kick to use less electricity. Well, at least, to "buy" less electricity. On average, my house uses about 45KWH per day (around 1400KWH per month). Current electricity cost is around US$0.20 per KWH but this time last year I was paying closer to US$0.33 cents per KWH.

A few years ago, I put in a solar hot water system on my roof. At the time, that saved me about $50.00 per month, but is probably saving me more now.

Here is some guesses as to the major power consumers in my house:
  • 2 Dell T605 Servers - 6KWH per day
  • 4 Desktop computers - 5KWH per day
  • Pool pump (8 hrs/day) - 14KWH per day
  • Refrigerator - 5KWH per day
  • Air Conditioning (22 SEER rated at 7 hours day) - 3KWH
The electric bill itself does not bother me as much as the dependency on oil. Not that I'm an environmentalist or anything (I don't even recycle cans!), but from a political perspective I think the dependency on oil is a really bad thing.

I am planning 2 separate projects:
  • Replace the pool pump with an Intelli-Flow pump. These are supposed to use 75% less electricity. They run continuously, but at a signficantly lower horse-power/amperage.
  • Install a photo-voltaic system. I have proposals to install systems that produce between 6 and 32KWH per day. I'm probably going to go with a system that produces around 15KW per day, but can be expanded the second year with an additional 20KW of capacity. So the second year capacity would be around 35KWH per day. The initial system's cost is $28,000 but there are almost $19,000 in tax incentives to do this. At the current cost of electricity, the payback on this system is around 7 years.

If any of you did the math and are asking, wait a minute, if you are producing 35KWH of electricity per day, you are only producing that much during the sunny hours of the day (peak production for these systems in Hawaii is 9AM - 3PM though they will produce some outside of those periods. Your house is using electricity 24 hours per day.

Quite right. The final system that I'm looking at will produce around 8.3KWH (per hour). However, I'm not using THAT much an hour. In that case, my power meter runs backward and I feed electricity back out "on the the grid". The electric company can then use that electricity and (by law) has to give me credit for it. Then, at night, when I'm not producing electricity I can use back up the credits.

My ultimate goal is to produce about as much per day as my house uses. I can do that if I can improve the pool pump's efficiency. The initial investment is pretty high, but the system lifetime is 25+ years so the payback is tremendous.

Sunday, August 30, 2009

Connections Online goes live!


Do you like conferences, but can't get the funding to travel? The Connections folks have a solution for you in the form of the Connections Online conference. You can pick and choose the sessions you want to attend (they are US$39.95 per session or you can buy a package) and once you purchase the session you can watch it as many times as you want during a specific period of time.

A few examples of the many sessions that are available includes:
  • Active Directory Security Best Practices by Sean Deuby
  • ESX and Hyper-V Comparison by Alan Sugano
  • Eradicating PSTs by Martin Tuip
  • Administrators' Idol: The Coolest Session Ever by Dan Holme
  • Exchange and Certificates by Ilse Van Criekinge
  • Group Policy: The New Hope -- Vista and the GP Preferences by Jeremy Moskowitz
  • Get ready for Exchange 2010 : Why this release is the most important yet! by David Elfassy
  • Exchange Management Shell – Beyond the One Liner by Glen Scales
  • A Close Look Inside the SharePoint Engine by Randy Williams
  • VSS Backup and Exchange by Michael B. Smith
  • SYSVOL Replication Can Wreak Havoc in Your Network by Rhonda Layfield
  • What’s New in Active Directory: Windows Server 2008 R2 by Brian Desmond
  • Pragmatic ASP.NET (Tips, Tricks) And Tools by Steven Smith
  • Clustering in SQL Server by Ronald Yenko
  • All That You Can Learn About LINQ in One Hour by Dino Esposito

Monday, August 24, 2009

Public folders on a CCR cluster

Microsoft has long stated that locating a public folder database on a CCR cluster in an organization where there is more than public folder database is no supported. Bharat Suneja summarizes this nicely in Cluster Continuous Replication and Public Folders. As with many things that Microsoft says are unsupported but that actually works, I took this to be more of a guideline than a hard and fast rule.

In one of my Exchange environments, we have a lot of regional offices with between 1,000 and 3,000 users. In the 1,000 user location, we did not want to invest additional hardware in a dedicated public folder server so we threw the public folder database on the CCR cluster. During testing that we move the clustered mailbox server (CMS) from node to the other, the public folder database moved just fine.

You guessed it, the active node failed a few weeks ago and the public folder database did not remount. We could not get it to mount at all. Period. End of story. Kaput. Dead database. I had a PSS engineer sitting right next to me and he could not rescue it either. Exchange Server 2007 SP1 is apparently hard coded not to allow the database to be recovered, even if you accept a lossy failover.

So, the moral of the story. If you have more than one public folder database in your organization, do NOT put it on a CCR cluster.

Labels:

Friday, August 07, 2009

Symantec Endpoint Security Fan Club - Not!!!!

Over the past 3 months at work, we have came across a number of performance issues and other weird problems related to Symantec Endpoint Security. We finally made the decision to remove it entirely and go with McAfee. Yes, it was THAT bad.

I had a new issue today with Symantec Endpoint Security running on an IIS Server. Every time I made a change such as enabling ASP.NET or deleting the Default Web Site, when I ran IISRESET, I would look back in IIS Manager and the change would have reverted back to the original setting. I deleted the Default Web Site five times and it kept coming back. (Insanity can clearly be demonstrated by the person who does the same futile thing over and over again but expects a different result.)

Once I stopped all of the Endpoint service, I was able to make the necessary changes to IIS. Unfortunately, that is 2 hours of troubleshooting time that I will NEVER get back.

Wednesday, August 05, 2009

Ilse van Criekinge rocks!

As many people are aware, I am working on the Mastering Exchange Server 2010 book for Sybex. Ilse Van Criekinge jumped in and helped me out with the Exchange Management Shell chapter by providing an informal technical review as well as some new content with respect to the remote shell and the new PowerShell 2.0 GUI feature. Thanks Ilse! You are much appreciated! And, if you don't have Ilse's Exchange Management Shell book, well... what are you waiting for???!!!!