Microsoft

Office 2007 MIME types for Apache

An interesting bug came up in the OWN Forums over the weekend, when downloading Office 2007 Word (docx) document from an Apache hosted site, the file either comes up garbled (application/octet-stream) or opens up a zip folder. This is usually the case when you have a mime-type and content-type mismatch and can get even uglier.. so what’s the solution? You have to define new Office 2007 mime types in your web server (or more precisely, server-side mime type database) so it knows how to communicate the content properly to the web browser. Office 2007 uses the new zipped XML OpenDocument format. After Googling for a few minutes and not finding the solution on the first four pages of searches I came to my buddy David Overton’s page – Now I remember where I read about the new Office 2007 mime types! I’m sure David will be extatic to know his hard work (which applies to IIS6 by the way) is now going to help Apache users everywhere get Office 2007 documents easilly. Joke aside, truth is Apache is the dominant web server and there is at least 70% chance you’re browsing an Apache site (you are right now, it’s what powers Vladville!) or about 98% chance if you’re not in a corporate environment.

Office 2007 mime types from David Overton.

First you’ll notice that there are many different mime types associated with Office 2007 OpenDocument format for just Word documents and templates: .docx, docm, dotm, dotx:

.docm = application/vnd.ms-word.document

.docx = application/vnd.openxmlformats-
officedocument.wordprocessingml.document
.dotm = application/vnd.ms-word.template
.dotx = application/vnd.openxmlformats-officedocument.

wordprocessingml.template

You can hardcode in one of these at a time, however, there is a shortcut. Just open your /etc/mime.types and add this to the last line:

application/vnd.openxmlformats       docx pptx xlsx

Restart the Apache service and you’re set. This takes care of the top three popular Office 2007 formats. If you don’t have access to the system mime type configuration (you likely don’t) you can always override the settings using your .htaccess file. Enjoy and thank David! Here is the end result:

Office2007mime

Extra note: Above applies to Apache servers hosted on Linux, however, if you host your Apache server on Windows the server distribution is likely shipping a mime configuration database in a specific path, one that you may or may not be able to find easilly. No worries, you can always add the content types directly to the httpd.conf file which is very easy to locate in most popular Windows Apache distributions such as Vertrigo. To add the new mime type directly in Apache httpd.conf (for Linux fans, /etc/httpd/conf/httpd.conf):

AddType  application/vnd.openxmlformats  .docx .pptx .xlsx

Please note that httpd.conf definitions override the /etc/mime.types definitions and dependant on the directory configuration, htaccess can (and usually does) override both.

Groove vs. ESET/Nod32

So all my friends have been playing with Groove for about a month and I never joined the party. Frankly, I never could get Groove to work. I had a few hours to kill today so I figured I’d finally get this thing fixed and having been over a month since I last tried to get it to work I figured I’d take a shortcut (ie: IM to sbradcpa: “Hey, whats with ‘can’t find provisioning server’ thing in Groove) from which point I was redirected to PSS Canada. Apparently Dana had the same problem and the PSS reference is important for two reasons: First, it took him 20 minutes to answer my IM, followed by “They don’t have Google search in America?” and “I have to go, but if you have a problem later I’ll help again, SRX07…”

So what made me so “special” – well, apparently my antivirus software wasn’t playing along. I couldn’t get my Groove on (I know, I know) because I have a 64bit Vista workstation with way too much RAM and I can’t get a decent A/V solution for that so I have to deal with the third world software makers (ESET).

Bottom line — ESET/NOD32 hates GROOVE.EXE. If you’ve got the combo and you’re getting the “Groove 2007: Unable to contact provisioning server” you need to add GROOVE.EXE to the IMON exception list. Details here..

It’s all in the Relay Server URL configuration (which Groove gets on it’s own, its not modifiable as are other parameters on your Advanced Network Settings). Because Groove is being intercepted by IMON you’re not getting to the relay server and are instead stuck with the grooveDNS://backwardscompatibility.groove.net – but add GROOVE.EXE to the exception list and voila, you’re set with a *relay.groove.microsoft.com relay server.

As for NOD32. Open up your Control Panel > IMON > Setup > Miscelaneous > Exclusion > Edit > Add > C:\Program Files (x86)\Microsoft Office\Office12\GROOVE.EXE

Does Microsoft WSSG Just Not Get It?

So over a week after the surprise drop of Windows Server 2003 SP2, the product team blogs the following:

Rapid customer adoption of Windows Server 2003 SP2 continues.  In less than a week since release there were more than 400,000 successful downloads!  Interesting that some have commented that we "quietly" released SP2.  The trade press have certainly covered it, since November when we broadly publicized the Release Candidate and product details, and at launch last week. At last count there were several dozen news stories about SP2 over the last week, and many blog posts.  SP2 also required less advance education compared to SP1 or XP SP2, because (by design) it is generally much easier for customers to "consume."

You send an alert the Friday before saying there would be no security patches the next Tuesday. Any IT department larger than 1 person normally considers that a cancellation of the mandatory around-the-clock patch testing and deployment work cycle that you put your customers through every second Tuesday of the month.

Then you “quietly” release SP2, though I’m not sure why you’d quote a factual description but I’ll play along. Quietly means without announcing the release. At the time of it showing up on Microsoft Update there was no email. There was no announcement. There wasn’t even an announcement page on Microsoft Technet.

Even your own employees had no idea this was coming!

So after putting us through series of ineffective DST patches, after not following even your own procedures for publicizing the release date of service packs, after admitting that you messed up by pulling high priority classification from MU hours after it was placed there, after years of the “patch-or-die” security track record that leaves everyone not patching with an exploitable system with 0–day attacks… After all that you have the decency to poke fun at the people that alert the public when you mess up and pretend nothing went wrong? Here’s a quote for you Joel:

“Fuck you, you jackass!”

Sincerely,

Vlad Mazek, MCSE
CEO, Own Web Now Corp
Microsoft Partner whose 14 data center network wastes millions of dollars in overtime dealing with Microsoft security patches, hotfixes and service packs.

ALERT: Microsoft Windows 2003 Service Pack 2 Out

Microsoft has released Microsoft Windows 2003 Service Pack 2 for both 64–bit and 32–bit editions. It is flagged as a high priotity update meaning that if you have your box set to automatically apply updates you will likely be seeing this message just as your server is rebooting.

We got a bit blind-sighted by the decision to release SP2 today. Usually major service packs are announced well in advance. Will update when I find out more, in the meantime carry on with due dilligence and proceed carefully.

Update: SP2 has since been moved off the High Priority list.

Exchange Webcast Reminder

Just a reminder that the Exchange 2007 webcasts are on for today:

http://www.vladville.com/2007/02/vlad-does-microsoft-exchange-webcasts.html

One at noon, one at 7PM – both times are eastern. I’ve been traveling the country showing people the cool new stuff in Exchange 2007 so if you’re not fortunate to be near one of our data centers where I can swing by for a presentation this would be a good opportunity to check it out.

I had an argument going with Susan a little while back about whether Exchange 2007 was “bleeding edge and I’m waiting for Cougar, Centro” – absolutely false. Not only is it ready and stable but it puts Exchange 2003 to shame in a heartbeat from any angle you look at it –information worker, itpro, business owner. As for the fictional products of the future – we’ve been deploying Exchange 2007 and people that see the new stuff are switching now and not looking back. When someone shows you the benefits you really get the same feeling you get when looking at 5.5 vs 2003 – so come over and hear about it today.

Vlad does Microsoft Exchange webcasts

I’m doing two Microsoft webcasts covering Exchange 2007 this Wednesday: If you have any questions and such feel free to bounce them to me or come watch the webcasts and put your stuff in Q&A window. There are two events (not replays):

http://www.msreadiness.com/ws_abstract.asp?eid=15005101
http://www.msreadiness.com/WS_abstract.asp?eid=15005102

Title: Virtual Partner Briefing powered by TS2: Exchange Server 2007
Date: 2/21/2007
Live event start time: 12:00 PM
Duration: 90 min

Title: Virtual Partner Briefing powered by TS2: Exchange Server 2007 (PM Edition)
Date: 2/21/2007
Live event start time: 7:00 PM
Duration: 90 min

Anything short of NDA stuff (Cougar, Centro, etc) is fair game.

Virtual PC 2007 is out

Microsoft Virtual PC 2007 is out — must admit, that is one heck of a presentation in terms of a web site. In terms of what’s new:

  • Support for Windows Vista as a host
  • Support for Windows Vista as a guest
  • Support for Windows Vista 64–bit as a host
  • Improved performance compared to Virtual PC 2004

I think nearly everyone has moved over to Vmware Server by now but Virtual PC 2007 remains the lone free workstation version for cheap and easy emulation. Give it a spin.

(Virtual PC… not Virtual Server.. Yeah, I know, I’m a jackass.)

Upgraded to Windows Mobile 6 Today

Just finished upgrading my T-Mobile MDA (HTC Wizard) to Windows Mobile 6 (PDA Viet 4 rom) a few minutes ago. I’ve used the device less than ten minutes and I already absolutely love the new OS. I’ll do a video screencast later but suffice to say they have really put in a lot of work. The first time I got to play around with WM6 was during checkin at Mandalay Bay when I was speaking at Exchange Connections, one of the developers let me check it out on his device. And today, through the power of pirating community, I too have a WM6 device.

First glance: Improved device setup.

Upon startup, Windows Mobile 6 prompts you to setup the device, security and email. This used to take a bit of an effort before but Windows Mobile 6 makes it seamless by guiding you through the process. Calibration of the stylus is identical to WM5 but the next screen is a bit different. Instead of setting just the time zone (and then spending 2 minutes going around control panels to setup time and date) both time, date and time zone are put on the same screen. Password enabling is easy as well. The final step is E-Mail Setup

First glance: E-mail setup

You’re given an option of corporate Exchange server or other source, such as POP3/IMAP. Exchange server setup is seamless and has far more features. For example, you can sync all the usual items, but you have additional options with email – sync 20K, 50K, all text (no images) in addition to the previous offerings. You also have the ability to send HTML emails and further annoy your friends with oversized signature blocks Image unavailable

First glance: The coolest feature

By far the coolest Windows Mobile 6 feature and perhaps the #1 reason to take a chance: Encryption. Windows Mobile 6 allows you to encrypt storage cards. Ever since Exchange 2003 Service Pack 2 and AKU2 we’ve been able to remotely wipe PocketPC devices – but with Windows Mobile 6 we can go a step further and encrypt storage cards. This way only the device can access the storage card and the device can be remotely wiped. How’s that for improvement?

UAC: When you halfass technology theft

Much has been said, and ridiculed, about the UAC feature in Microsoft Vista. Aside from 2 security MVPs and a handful of Microsoft employees I have not met anyone else that either likes this feature or is not asking to have it removed.

Susan and Dana are on the pro side. The entire world seems to be against them.

Some background: UAC comes out of the years and years of no easy process priviledge escalation control in Microsoft Windows. While working on a Workstation in an Administrator mode (default for XP and below) any process can without permission modify the registry, install drivers, change system configuration, etc. This lack of control is the main contributor to the spread of viruses, spyware and rootkits on the Windows platform and perhaps the main reason why Windows gets the “insecure” label so easilly.

So after Microsoft tried and failed to conquer the anti-spyware market, after they tried and failed to conquer the anti-virus market, they decided to actually fix the problem. (ok, truth is these efforts were being made in parallel but lying makes it sound better) So how does one fix the problem? By lifting the technology from the people that have already solved it! So they dug up their Linux guy from the basement, chained him to the steering wheel, drove him through the mobile car wash a few times and then sat him at the table to explain su and sudo.

Long story short, they stole sudo (superuser do) technology that allows a regular user to escalate to the superuser priviledge to execute a single command as the Administrator. They wrote a wrapper so that every time a process requested a restricted object (install a driver, manage users, etc) the little window will pop up with Windows needs your permission to continue. And as they were stuffing their Linux guy back into the box of manure he said something about su but they were already well on their way to kicking him down the stairs back into the basement.

The ONLY thing thats wrong with UAC

Microsoft half-assed this big time. UAC does not, and likely will not, piss off home users during their regular computer use. However, during provisioning and system troubleshooting UAC becomes a total nightmare. 

All the Microsoft OEM partners know this – which is why they ship boxes with UAC disabled. No why, oh why, do they do this? Because they know that the first thing you’ll do with your shiny new system is to make it your own – add users, add hardware, install software, etc. Be prepared to approve the UAC half a dozen times. OEM’s know this, and they don’t want the support overhead. Thats why they ship boxes without UAC.

The troubleshooters and computer techs? They have no choice but to shut the annoying thing off? Why? Because Microsoft half-assed it. There has to be a way to permanently escalate priviledges to the superuser status while troubleshooting the system; The unix su equivalent – For example – I am installing a video card, yes, I know I am going to be escalating the priviledges over and over and over again until I tweak it completely so STFU and let me work. But no, you have to click over and over and over again. Was it so hard to allow a checkmark to not ask for permission during the next 5 minutes, or never to ask for permission when performing this kind of task or to just accept all access during the entire session? Apparently, it was.

Disabling UAC

I’ve held onto publishing this for a while but since everyone wants to point at the users as the problem here and not a Microsoft shortsightedness, let’s give this a spin shall we? If you need superuser priviledges during a session to perform a hardware maintenance, software installation or troubleshooting you should not be subject to Vista’s inability to cope with this. To disable UAC follow these steps:

Start> msconfig >  Tools > Disable UAC > Launch

Reboot and you can actually perform a maintenance task without being nagged to death. Once you’re done go back and Enable UAC the exact same way, reboot and you’re back to normal.

Microsoft: Get your head out your ass and recognize the ITPRO should not sit around the box and approve escalation more than two times to perform a hardware or system maintenance task. By the same token, don’t think that just because someone is an ITPRO they need permanent priviledge escallation. Just provide a way to put the system into the maintenance mode – more than two prompts are too many, the second permission ought to be smart enough to ask whether this escalation should be assumed for a few minutes or remainder of the session.  

New Microsoft Certification Framework

Got a chance to sit in on the Microsoft webcast outlining the changes they are making to the Certified Professional program.. I must say, way to go. Here is one of the slides from the webcast (click to enlarge) that literally explains what we’re looking for: Proven skills across multiple technologies vs. Validated comprehensive skill set in specific job role.

Expirationoftechnicalskills

Let’s face it, to survive not only do you need to be an expert at what you do you also need to be versatie. Gone are the days of a monkey in a bucket creating databases - you want 6 figures, you’ll have to earn them.

The best part?

Finally, Microsoft will be retiring certifications along with the product support as well as expiring technology specialist certifications every 3 years. That alone ought to kill paper MCSE’s.