Tuesday, September 29, 2009

552 552 Message exceeds fixed maximum message size



A client sent a 6MB email to one of my users and got the following message:
This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

Username@MyDomain.com

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 Message exceeds fixed maximum message size (state 18).

Checking my Trend Micro IMSS log I couldn't find any reference to this email.
Now I know IMSS will not send a notification anyway even if the size limit exceeds my 10MB limit per message and it should log it. 2 points that sent me off track with this.
I asked the client to contact her email provider (she is using an Exchange based hosting solution) and they sent me the following response:
Title: NDR: Message rejected; too large
Created: 09/29/2009 12:03:36
Summary of issue(s): Receiving a NDR that states that the recipient is rejecting the message because of its size.

Steps taken: Had her send the message to our test account. It works. The email is about 6 MB. The limit of outgoing on our servers it around 52 MB's. It is an issue on the recipients end. She will get in contact with them.

At this point I asked her to forward the original email to a test GMAIL account I hold. From there I forwarded the email to my user and got a similar failure message.
Calling Trend Micro was the next step. I had a technician on the line in no time and he Webex'd my IMSS server to find no logs and tell me that it must be something before IMSS, maybe my firewall. The only way to prove him wrong was bypassing IMSS and forwarding all SMTP directly at my Domino server. yeah, exactly what I need...

Googling gave me nothing. It was all around Exchange 2007.
So I was thinking again about IMSS settings and started playing with the settings. When I doubled the message size limit from 10MB to 20MB I was able to receive the email and see it in the log.
I guess that is a bug in the IMSS software. Great product but it is the 2nd bug I found in it this year...
following Gmail's problems of last week I must share this comic from Rosscott.

Friday, September 25, 2009

HP Printers backorder


This is one of those unbelievable recession stories.
One of my users called in with a broken printer. His HP 2015P stopped rolling paper and since new printers cost just like a technician's visit (the printer is over a year old and its warranty already expired) we have a no fix policy for this type of printers.
I buy most of my equipment via CDW and when I placed the order for a new HP 2035 (HP2015 is not at the make any more) I was struck to see a shipping date for the end of September. That was late August.
Stunned by the obvious mistake I called my CDW sales rep and he told me that there is a national shortage of HP printers. They shutdown a line last summer because they expected reduced demand. Well, I would check their analysts...
CDW had a waiting list, a back order for this specific item for over 1500 pieces!!!

Thursday, September 24, 2009

Google fail. Again...


Google is aware that some people are experiencing an e-mail outage. This is becoming a quarterly or even bi-monthly event...

at 10:29AM this message was posted:
We're aware of a problem with Google Mail affecting a small subset of users. The affected users are unable to access Google Mail, but we've provided a workaround below. We will provide an update by September 24, 2009 11:29:00 AM UTC-4 detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.
You can access Gmail via IMAP


at 12:58PM, after few additional messages they posted the following message:
The problem with Google Mail should be resolved. We apologize for the inconvenience and thank you for your patience and continued support.


My users had problem with both Gmail contacts and Gtalk (or Gmail chat). At few points they couldn't log in or refresh their Gmail mailbox.
I had users both in NY & London complaining and I doudt it was just a "small subset of users" as Google claim.

Wednesday, September 23, 2009

Recovering a file from Backup


Earlier today I've received a call from one of my users asking to recover a file from backup. He explained that last week's power shutdown caused some files mess up in his home directory.
Blame it on the network, that's the way to go!

I wrote down the file name and exact path and loaded Backup Exec's Restore wizard. Looking at all my weekly full backups I found the Friday prior to the power shutdown and restored the file he was looking for. He wasn't happy.

The explanation I received was that "the system" saved a second copy of that file under a different name!
I had to insist it is not possible since systems do not save files or rename them and no other user has access to the home folder of that user.
More to the fire he claimed that the recovered file is older then the one he was looking for. At this point I had to ask him how does it relate to the power shutdown if whatever happened more then a week earlier???

Went back to Backup Exec and located the file from previous week where the creation date and modified date where exactly identical, similar to the date he created the file. That file also was "wrong".

At this point I innocently suggested that he might have saved it in a different location. 10 minutes and a long lecture on his methodical file organization system later he called again: He found the file under a different folder.

One technical tip I want to share from my experience this morning relate to the recovered file.
I did not want to recover the file to the original location (and by now you understand why). I usually recover files to the local disk at c:\BE_Recovery
When the recovered file come from a home folder the NTFS permissions are still in affect and you can't access it.
In order to see the files at \\Home\DomainName\Username, copy them to any other location or delete the folder and files when you're done, you have to do 2 things:
Add the domain admin with modify permissions
Allow permission inheritance to sub folders

Tuesday, September 22, 2009

Advanced Group Policy Management 4.0

Advanced Group Policy Management (AGPM) is coming out next month and it is time to take a first look at this new exciting tool.
It will be released as part of Microsoft Desktop Optimization Pack (MDOP) 2009 R2.
The new release include 3 main features you should know about:
Multi Forest/Multi Domain Support
AGPM 3.0 does not support multi-forest/multi-domain environments and requires to use import/export which essentially breaks the change management workflow. AGPM 4.0 allow moving GPOs from one environment to another. Even in my shop I have 2 forests and few domains.
Check mark for the SMB environment usability!

Windows 7/Windows Server 2008 R2 Support
The new version will add support for Windows 7 & Windows Server 2008 R2 settings reporting and editing.
Microsoft recommend that if you edit policy with Windows 7, make sure you run Windows Server 2008 R2 on the back end.
Another check mark for the SMB environment usability!

Search and Filtering
Well, don't get too excited. You still can't search for settings.
The search feature allow you to locate a policy by it's name or partial name.
While it is a nice improvement it is not really useful for the average SMB.

You can download the Microsoft guide for AGPM 4.0 here.

Wednesday, September 16, 2009

It’s 3 a.m. Who Do You Want Answering the Phone?


Last night, just before 3AM most of our floor lost power.
The first to take the hit where PCs as they do not have any power backups.
My servers and routers kept going for additional 90-110 minutes based on the UPS they connected to.
I have a bunch of APC UPS systems both from the 2200 & 3000 series.

An hour and a half later, just few minutes after most UPS died, the power came back. For most servers it was too late...

When I received that phone call I had to connect to my ASA and I was happy when it worked. Poking around I verified all the critical routers and switches are up and the Domain Controllers for all 3 domains are running.
One server didn't want to be cooperative, it did reply to ping but wouldn't allow and RPC based connection to the Windows environment. I had to reboot it but I was home in my pajamas and 45 precious minutes away.
iLO saved me! lucky me, this one server had a working, connected & configured iLO.
In few minutes I had this server restart itself and this time it did. what a relief!


In less then an hour I was able to start all the services, run all the programs and test all the network components. 1 hour - that is the time it would take me get dressed and commute to the office...

The aftermath:
Coming to the office I found that some PCs and few server where up all night. The meaning is that it was not some general building outage but a more specific one. I called the building electrician and he found out that the meter box, which is as old as our building got too hot and caused this power outage. We're going to replace all 3 meter boxes tonight after hours.

Preparing to such a major shutdown is very important. Few things to remember:
This is the time to check all your procedures and backups.
This is when you use the contact list you've collected all those years, calling all your vendors so they know your network will be down.
Make sure the users are aware of the shutdown.
Call your phone system support and make sure they know about it, you might need them.