DefinIT Because if IT were easy, everyone would do it…

22May/080

Exchange 2007 and Outlook 2007 remove categories from emails, tasks, calendar etc.

Posted by Sam McGeown

It seems that the nice people at Microsoft were looking out for us, lest the evil people in the world see how we categorise our email, and decided to strip away any category information from sent and received objects by default. Sure, I understand if you were categorising emails from someone as "sneaky git" or "numbnuts" then you might not be too happy about sending those out...but really it should be your choice right?

Did you know, for example, that In your Outlook 2007 rules there is a sneaky little enabled by default rule that clears the categories?

DefaultRuleOL2007

Removing that is an obvious first step!

The next step involves editing the registry, so make sure you know what you are doing before editing, always back the registry up first

There are also some registry keys you'll need to add, so open up Regedit and in HKCU\Software\Policies\Microsoft\Office\12.0\Outlook\Preferences, create DWORD keys SendPersonalCategories and AcceptCategories with values of 1. You'll need to restart Outlook for them to apply.

Finally, as per this TechNet article,  log on to your Exchange server as an Exchange Organisation Administrator and run the following command in the Exchange Management Shell

Set-TransportConfig -ClearCategories $False

You should be able to send and receive emails, appointments, tasks and any other Exchange object that supports categories, complete with category intact.

20May/082

VMWare Server 2 Beta fails to connect to virtual machine with “Error opening the remote virtual machine [machine] The host name could not be resolved.”

Posted by Sam McGeown

I've just upgraded my VMWare Server install to the latest version of the VMWare Server beta, which I have to say, is looking pretty good! One slight niggle that I had was that when I opened the VMWare Remote Console it would tell me that I could not connect, with the error:

Error opening the remote virtual machine SM-00109:8333\16:  The host name could not be resolved.

Clearly THAT's a pain in the proverbial. A quick trawl through VMWare's forums reveals two solutions, one that is clunky and stupid, the other that works. For brevity, the one that works is...

Use the fully qualified domain name of the computer to connect to the VMWare console, so for me, that mean using:

https://SM-00109.domain.dom:8333

instead of

https://SM-00109:8333

Simple!

Tagged as: 2 Comments
12May/081

Code syntax highlighting in BlogEngine.Net

Posted by Sam McGeown

I've just added some code syntax highlighting to this blog using SyntaxHighlighter and a great how-to article by Scott Dougherty this means that any code I post should look like this:

public static string SayHello(string name){    return String.Format("Hello, {0}!", name);}

There are a few bugs at the moment, one being that tiny_mce is stripping linebreaks from the code posting (just a minor one) and the theme somehow removes the line numbers, but I'm sure I'll find a way around them...somehow.

Tagged as: 1 Comment
9May/081

Posting to BlogEngine using Windows Live Writer

Posted by Sam McGeown

One of my unpublished gripes with the DotNetNuke blog was that it was a pain to make work with WLW. One of the cool things with BE.Net is that it does work with WLW, not only that but it works well. Setup was a breeze and within 2 minutes I'm now writing my first post, including tags and categories (hit F2 if you're trying to do that in WLW).

Now this is cool! :)

9May/085

Force BlogEngine.Net to update its cache after an import

Posted by Sam McGeown

Well my first real post on BlogEngine.Net is...about BlogEngine.Net!

After running the import program from my old DotNetNuke blog I found that the importer had worked, but that the blog entries had not shown up. This was because the cache that BE.Net uses for the XML data files. Since I'm on a shared hosting I couldn't just run an IISReset.exe, so I obviously needed a work around, and here it is:

  1.  Open default.aspx.cs in Visual Studio (or just a text editor)
  2. Add the following to the Page_Load function:

    BlogEngine.Core.Post.Reload();

  3. Save and upload default.aspx.cs, refresh your blog.

Et voila, posts will appear. Phew.

Tagged as: 5 Comments
8May/081

Lament for WordPress and a call for a .Net WordPress killer

Posted by Sam McGeown

I miss WordPress. I miss the fact that it would save my work periodically, and that if my session timed out while the I was writing a blog, it would be there when I logged back in as an unpublished daft. I miss having my categorised posts. I miss having tags to tell me what I've written about. Even Google seems to prefer my old blog, old pages that don't exist are returned where these ones sit in anonymity.

It's not that DotNetNuke isn't good, because it is. It's powerful and has a load of really good add-ons and...it just isn't WordPress when it comes to blogging.

All that said, I've burned my bridges - my web host is .NET only. Somehow I need to find some blogging software in .NET that is free, open source and comes close to WordPress.

Perhaps it portends a slightly fruitless search when my first result takes me to a blog post from 2005 with the same lament, why can't I find some .NET blogging software that's as good as WordPress?

Ever the optimist, here's my (very) shortlist I am going to look at:

BlogEngine.Net - The most promising bit of .Net blogging software I have seen, could it be a WordPress equivilent for MS junkies?

Community Server Express - Certainly mature, certainly powerful, but I get the feeling I'll end up with the same frustrations and a sledgehammer to crack a walnut.

dasBlog - Not even sure if this is still developed, it's written in .Net 1.1 but it looks quite mature.

Tagged as: 1 Comment
8May/080

Menus in MOSS (or WSS) open and disappear

Posted by Sam McGeown

We were integrating a 3rd party product's web parts with MOSS the other day and came accross an interesting problem. In site editing mode, all the drop down menus would appear for a flash and then go blank. The actual admin pages we were trying to get to would work if you entered them into the browser directly, but that isn't an easy way to manage the site!

The problem turned out to be that in the process of getting the 3rd party web parts to work, the support team had added a MIME type to the IIS installation.

Image showing the MIME type dialogue, with the additional mime type.

This is obviously not what you'd do in a production environment, but the support team put it in to rule out the MIME type in the integration problems. Once the rogue "catch all" MIME type was changed to a more specific extension, and of course the arbitrary IISReset.exe was performed, the menu's came back to life.

The relating MS KB article is support.microsoft.com/kb/939311/en-us

 

 

 

2May/086

Windows Vista shows black screen and the cursor before log in.

Posted by Sam McGeown

Had an interesting one yesterday, my bosses Vista laptop booted as per normal, making all the right pictures until just before the log in prompt popped up, then a black screen in what looked to be VGA graphics with the white default arrow cursor.

Corrupted graphics drivers, I thought. A quick boot into safe mode...but no, the same black screen and over-sized pointer.

No problem, Last Known Good Configuration will save my day...except that LKGC points are set when the OS manages a successful boot, and Vista had, in it's own opinion, successfully booted. The same problem occurred.

Googling around I found hundreds of posts describing similar problems, fewer, but still quite a lot had the same problem. There were no solutions for the symptoms that I was facing; that always begins to worry me because it's very unlikely that I can fix something that no-one else can!

After several more hours Googling and trying various different recovery options, I came accross a very succinct and to the point technet article - KB946532. Apparently Vista's fairly unknown Transactional NTFS has a bug which, if you're unlucky enough to see, will "occur because of file system corruption within the $Txf directory. This corruption causes a deadlock condition between the Transactional NTFS (TxF) process and the Autocheck process." In short, you're screwed.

System Restore points don't fix this problem. There's no way of preventing this error, which will render your Vista install inoperable. Helpfully, MS suggest you reinstall Vista in parallel to your current install. They also mention that it's fixed in SP1, which is the most compelling reason to install SP1 that I've heard.

Right now I feel a little like I'm playing Russian roulette with my fleet of Vista laptops, but do I really want to force an early adoption of SP1?