The folks over at the ISO group are none too happy with Microsoft’s implementation of the OOXML document specification in the upcoming version of Microsoft Office 2010. Due to delays in the final approval and recent changes to the strict specification, Microsoft was not able to include full support for creating new OOXML documents in 2010, and will only include transitional support. However, Redmond has stated that they intend to have full support for the creation of OOXML-Strict documents by the next version of office… what is not clear is if that means Office 2010 will be patched for full support or it will not be 2010 at all and users will need to wait until Office “15″ for support.
Microsoft has released MED-V 1.0 SP1 and App-V 4.6. The big update to MED-V is full support for 32-bit & 64-bit Windows 7 hosts, but it also includes support for Japanese versions of Windows. Chances to App-V are mostly centered around language support. MED-V is an enterprise desktop virtualization management system that allows administrators to deploy and control Windows XP or Windows 2000 deployments running inside Windows 7 or Windows Vista host operating systems.
For all five of our readers with a Zune HD, you’ll be happy to know the Zune 4.5 firmware was released last week. It features an new Smart DJ mix with personalized recommendations, Zune Marketplace for TV, and better video codec support. Microsoft will also be releasing a new Zune HD 64GB model soon. To get the update, plug it in and sync with the Zune software on your desktop.
For all five of our readers running Windows Server on Itanium processors, you’ll be disappointed to know that after Windows Server 2008 R2, Microsoft will no longer be releasing versions for Itanium processors, and will focus on the x64 platform going forward. There was no 2008 R2 version released for 32-bit processors, either. Microsoft will no longer develop other software for Itanium, and SQL Server 2008 R2 and Visual Studio 2010 are also the last versions to support it. Mainstream support for Windows Server 2008 for Itanium-Based Systems (and R2) will end, in accordance with that policy, on July 9, 2013, while extended support will continue until July 10, 2018. That’s roughly eight more years of support.
Just so that our entire update isn’t focused on Microsoft today… If you’ve been living under a rock since last week, we just wanted to remind you that the iPad came out on Saturday. It’s magical, especially when you watch Harry Potter on it.
The number of businesses still using Internet Explorer 6 is painful to see. Coupled with the fact that all of them are on Windows XP or Windows 2000, it turns from pain into terror, especially when it comes to security.
For a lot of system administrators, the reasons to stay outweigh the reasons to upgrade. Websites that break, plugins that won’t load, old software that isn’t updated anymore. Trust me, I’ve been there. However, a lot of it boils down to lazy and poor practices of system administration.
Yes, you’re lazy and you’re bad at your job. Internet Explorer 6 was released in 2001. Yes, 2001, most of us don’t even drive cars that old, let alone unleash people on the “information superhighway” with a browser that old. It was designed at a time when security was not the issue it is today. It was designed to work on operating systems like Windows 98 and Windows ME. Would you let people use Windows ME on your network? No! So why are you letting them use a browser that was built for it?! (more…)
Just a reminder, Windows 2000 will reach it’s end of life in July. Microsoft has outlined July 13, 2010 as the date Windows 2000 will no longer be supported by Microsoft. There are already a variety of security threats in the wild where Microsoft has said they will not be releasing updates to protect Windows 2000 because they say it is not feasible. After next July, no support or new updates (except for online self-help) will be available.
In a related bit of news, Microsoft is addressing an issue latest Forefront antimalware client update won’t install on Windows 2000 when the installation is run via Automatic Updates. When this issue occurs, the update uninstalls the previous version of the antimalware client, and then tries to install the new version and fails, leaving the system without the antimalware service. Microsoft’s published workarounds are to decline the updates for Windows 2000 systems (976669 is the FCS slipstream client) and make sure that the previous FCS antimalware updates are approved (971026 and original FCS client), or run the install interactively as a logged on user.
My workaround… stop using a 11 year old operating system and upgrade to at least Windows 2003.
This patch Tuesday will be one of the lightest ones for security in recent memory. According to the Security Bulletin Advance Notification for this month, Microsoft will only be releasing one patch for Windows, and none for Internet Explorer or Office. The patch will be issued on Tuesday, January 12, and will be followed on January 13 by a 90 minute webcast at 11:00 AM Pacific. In addition to the one patch for Windows, Microsoft will also release an updated version of the Malicious Software Removal Tool.
The patch is considered critical for Windows 2000 users, and low for all other versions, and relates to a remote code execution venerability. Effected operating system versions include every currently supported edition both on the client and server side:
- Windows 2000 Service Pack 4 [Critical]
- Windows XP Service Pack 2 & Service Pack 3
- Windows XP x64 Edition Service Pack 2
- Windows Server 2003 Service Pack 2 (32-bit, 64-bit & Itanium)
- Windows Vista Service Pack 1 & Service Pack 2 (32-bit & 64-bit)
- Windows Server 2008 Service Pack 2 (32-bit, 64-bit & Itanium – except Server Core installs)
- Windows 7 (32-bit & 64-bit)
- Windows Server 2008 R2 (64-bit & Itanium – except Server Core installs)
Microsoft will still be releasing one or more non-security but high-priority update through Windows Update and Windows Server Update Services, but has not yet disclosed details.
If you couldn’t get a chance to watch the Microsoft CES pre-show keynote last night, you didn’t miss much. If you were actually at the event, I feel sorry for you, it must have been hard to stay awake.
After starting late due to power issues (which fried one of the Microsoft demo units on stage) the keynote got off to a rather boring start with Steve Ballmer, Microsoft CEO, giving various statistics about how well recently released products like Windows 7 and Bing are doing. For the first half hour, the audio stream for the webcast was so bad, it kept cutting out and then required constant volume adjustment. Note to Microsoft, hire a decent sound engineer next time.
If you’d like to watch the keynote for yourself, you can see the saved version on the Microsoft website.
It was all pretty much downhill from there. The much discussed “Courier” tablet that many in the tech press was excited they would announce never came, and there were no details about Windows Mobile 7… at all. Only “we’ll have more about mobile at Mobile World Congress.” So overall, the keynote failed to deliver much of anything that we didn’t know or have not seen already. But, here is a breakdown of what was covered, after the break.
(more…)
There are many less than glamorous roles that a Windows server can take on. Not all of them are born to be an Exchange server, a domain controller, or even a web server. Some are destined to take on the role of managing printers. And for every role in Windows server, there is a team of programmers and engineers behind it, and they need your help.
If use the Print Server role in your environment, Microsoft is looking for your feedback, especially if you’re using the print server management packs for System Center Operations Manager 2007. Your input will help form the future manageability plans for the print server role in Windows Server. If you deal with printers like I do, you probably know how frustrating they can be so you’ve probably got a lot of feedback to give. (Although truthfully none of my issues are really Microsoft’s fault — I’m looking at you Xerox)
Head over to the OpsMgr public site on Microsoft Connect and fill out the “Print Server Management Survey” You’ll need to login to Connect using your Windows Live ID but Microsoft claims the survey is anonymous and should take about 5 minutes to fill out the 11 questions.
Microsoft has posted a little bit of light reading, a document titled Changes in Functionality in Windows Server 2008 R2 that outlines exactly that, the differences between the R2 release and the original 2008 release. It only weighs in at 1.1MB and 211 pages. You can grab it from the Microsoft Download Center in Microsoft Word format or browse the document online through Technet.
Topics such as new features in Active Directory, DNS (including DNSSEC), Group Policy, iSCSI, IIS, clustering, Windows Deployment Server and many other elements are all covered in great detail. If you’re looking at a server wondering if you’d see any significant benefit to upgrading, other then getting the latest guts of Windows, this is a helpful guide.
Windows Server 2008 was released in February 2008, followed by R2 which was released in October 2009. R2 is Microsoft’s first 64-bit only operating system release and is based on many of the same core programming as Windows 7.
Microsoft CEO Steve Ballmer and Robbie Bach, president of the Entertainment & Devices Division, will deliver the pre-show keynote address in Las Vegas to kick off the 2010 International Consumer Electronics Show (CES). You’ll be able to watch the keynote live starting tonight, at approximately 6:30 p.m. PST. If you can’t make it, check back here tomorrow for a break down of what was covered. Expected topics include Windows Mobile 7, as well as a possible announcement about a new tablet developed with HP. Even if they don’t cover that, you can at least watch Ballmer jump around the stage for a while.
Take a trip over to the Microsoft CES website tonight to be able to watch their live stream.

Windows administrators, mark your calendar for the drop dead date to get those old servers upgraded. Microsoft has outlined July 13, 2010 as the date Windows 2000 will no longer be supported by Microsoft. There are already a variety of security threats in the wild where Microsoft has said they will not be releasing updates to protect Windows 2000 because they say it is not feasible. After next July, no support or new updates (except for online self-help) will be available.
These changes were posted by Crissy House, the Windows Server operations manager, on their team’s blog.
House also announced that there would be no more service packs for Windows 2003 or Windows 2003 R2. Both 2003 releases will move to extended-support on July 13, 2010, which means only security updates will be published for these operating systems. Non-security hotfixes developed during this phase will be provided only to customers who enroll in Extended Hotfix Support (EHS).
Microsoft released Windows Server 2000 in February 2000, Windows Server 2003 was released in April 2003 and Windows Server 2003 R2 was released in February 2006. In February 2008, Microsoft released Windows Server 2008 which was developed along side Windows Vista, but will quickly supplant it with Windows Server 2008 R2 which was developed along side Windows 7 and will be released along side the client OS on October 22, 2009.
Windows Server 2008 R2 will only be avaliable in x86-64 and Itanium editions, so administrators needing to run 32-bit implementations of 2008 will need to use the original 2008 release.
Microsoft has begun pushing out Windows Internet Explorer 8 via Windows Server Update Services, as it announced back in June that it would start doing. The package is published as an update rollup, so WSUS administrators who have their systems set to automatically approve such packages will want to be careful after synchronizing if they’re not ready for a full IE8 deployment.
Only systems with Windows XP, Windows Server 2003, Windows Vista, and Windows Server 2008 will be able to upgrade to Internet Explorer 8. Systems still running Windows 2000 will be stuck on Internet Explorer 6.
Internet Explorer 8 was released to the general public in March 2009.