Showing posts with label recovery. Show all posts
Showing posts with label recovery. Show all posts

Wednesday, February 20, 2008

SBS 2003 Media, Service Packs, Repair Install - Oh My!

This has been a long-running battle I've had with Microsoft over the years - the inability to either roll my own slipstreamed SBS media, or obtain slipstreamed SBS media at reasonable cost (like the Volume License media kits).

Why would I want to roll my own or access low-cost SBS media, you ask?

Well, if you ever have to do a Repair Install of your SBS box and you've added a Service Pack, you're hosed. The Repair Install will undo the service pack applied to the once-working box, and on reboot will give you a lovely blue screen. The only way around this is to restore from the last full backup, or re-image from your favorite imaging tool of choice (two listed below if you're not already using one).

Thanks to the wonderful advances of products like Acronis True Image and ShadowProtect, performing Repair Installs are a thing of the past, especially if you're using Repair Install to migrate a Retail SBS install to new hardware. The hardware independent restore capabilities of these products makes a full backup / minimal install / full restore / repair install redundant, as well as a lot slower.

But it's a pain if you don't have these, so make sure you have SBS media from the same channel (OEM, Retail or Volume License) with the Service Pack you're running already slipstreamed. Or simply don't install Windows Server 2003 Service Packs to SBS 2003 boxes.

Tuesday, October 23, 2007

Recovering Public Folder Items Easily in Exchange Server 2003

I occasionally get requests from clients and colleagues asking me to recover Public Folder items from Exchange Server 2003.

Thankfully for me I performed the ultimate fubar while performing a test migration from NT4.0 + Exchange 5.5 to SBS 2003 Premium back when SBS 2003 first came out. That's right, I managed to blow away the majority of the Public Folder store in one fell swoop, simply because I wasn't following my own instructions properly and wasn't used to the new Exchange System Manager interface.

Thankfully, I had just been getting familiar with the new capabilities of Outlook Web Access and had used the Recover Deleted Items feature to get familiar with it and to be able to instruct clients on how to use it.

I didn't really want to have to spend the time re-copying the Public Folder store from the Exchange 5.5 install, so I looked for the Public Folder equivalent of the Recover Deleted Items feature for the mailbox. It appeared to be missing. Or was it?

I had noticed that the Recover Deleted Items window had essentially opened the Deleted Items folder in the mailbox and had set a URL variable. The variable and its setting was:

cmd=showdeleted

Being the lazy kind of guy I am - as well as being inquisitive - I thought I would give some link hacking a try. I opened up the Public Folders link, navigated to the parent folder of the folder I deleted, right-clicked on the parent folder and selected Open in new... This opened the folder in a new window. The URL of this folder was of the form:

https://server/public/Public%20Folder/?Cmd=contents

I then replaced contents with showdeleted. The URL then looked like:

https://server/public/Public%20Folder/?Cmd=showdeleted

Ta da! The folder I trashed was now visible and capable of being recovered, which saved me additional copying time. Sometimes screwing up a test environment is a great way to learn a new, lazy technique :-)

Tuesday, September 25, 2007

Desperately Awaiting Windows Vista SP1 (or why Power Users should use Firefox)

IE7 under Windows Vista (and also under XP) is driving me nuts.

I frequently have 20-30 browser tabs open. These tabs generally contain my reading list and I place them in reading order. I also have a second IE7 window open for general searches and Webmail.

About once a fortnight I have IE7 crash on me. What really sucks is a lack of built-in IE7 crash recovery. For that I use IE7Pro. It does a reasonable job.

Sometimes the crash recovery just doesn't work all that well. When it doesn't work, I use TravelLog to pull out my URL history, then use FileParse (with XP compatability enabled) to reformat the output so I can quickly process the URL history in Excel.

This is obviously time consuming.

The final nail in the coffin for IE7 on Vista for me is that when I have 32+ tabs open I get a Denial of Service on Windows Explorer. Yes, that's right. When I exceed 32 tabs and go to the Start Menu and click on Computer, Explorer opens and then immediately closes. If I reduce the tabs to less than 32 I get Explorer functionality back.

This is a serious regression from Windows XP. Under XP I don't get this DoS. Under XP, it takes about 64 tabs for the interface to screw up, but this only affects IE7. Windows Explorer in XP still remains functional. The obvious indication of exceeding the capabilities in IE7 is that tabs fail to render content and also losing the ability to bring up right-click menus. This also occurs under Vista, but at a tab count of about 32 and with the added bonus of a Windows Explorer DoS.

So I'm now installing Firefox 2.0 and will be using this as my primary browser. This will improve my browsing efficiency and will stop my blood from boiling when IE7 crashes, or Explorer stops loading.

I really, really hope Vista SP1 fixes this.

Monday, August 13, 2007

IE7 Crash Protection

After yet another IE7 crash caused by Adobe's Flash Player I decided to have one final look for an IE Add-on that could save tab state in the event of a crash. If I couldn't find one, then IE7 was going to be replaced with Firefox as my primary browser.
Thankfully - and without too much effort - I came across IE7Pro. This usful free add-on provides crash protection as well as a host of other useful features, such as Tabbed Browsing Management, Spell Check, Inline Search, Super Drag Drop, Proxy Switcher, Mouse Gesture, Tab History Browser, Web Accelerator, User Agent Switcher, Webpage Capturer, AD Blocker, Flash Block, and Greasemonkey like User Scripts platform (feature list copied from the afore-mentiond site).
So the combination Flash Block and Crash Recovery should lessen my IE7 frustrations.
Now if I only had a more feature rich tool than TravelLog IE URL History Tool to pull out browser history...