Month: November 2006

Microsoft shipped Windows Sharepoint Services 3.0 today.  There’s an X86 and an x64 edition.  I’m a fan of Sharepoint.  I really think an organisation can change the way shared storage is provisioned and can take the concept to a nother level.  Storage becomes a shared workspace where dynamic teams can work together independant of the involvement of IT.  The platform can be customised to their needs and becomes an interactive web application that is very simple to maintain and develop.  This technology is slowly gathering momentum.  It appears to have taken hold abroad but has been slow to garner attention here in Ireland, unfortunately.

The FAQ states that the following are new features in WSS 3.0:

• Improvements to collaboration workspaces: SharePoint sites now offer e-mail and directory integration, alerts, RSS publishing, templates for building blogs (also known as weblogs) and wikis (Web sites that can be quickly edited by team members—no special technical knowledge required), event and task tracking, improved usability, enhanced site navigation, and more.
• Enhancements to content storage: SharePoint lists and libraries now provide per-item security for better data control and integrity, a recycle bin, and enhanced flexibility for storing more types of content. Row and column capacity has also been increased, as has retrieval speed. Windows SharePoint Services 3.0 can be easily integrated with smart client tools. In particular, close integration with Microsoft Office Outlook 2007 provides offline access to events, contacts, discussions, tasks, and documents.
• Easier provisioning of workspaces: Windows SharePoint Services 3.0 provides more sophisticated and flexible security, as well as greater control over security settings and permissions.
• A more robust foundation for Web applications: Windows SharePoint Services 3.0 provides greater flexibility for customization and development of Web-based services and applications built on the Windows SharePoint Services platform.

For me the key things in there are:

• RSS: it ties in nicely with IE7 and Outlook 2007.  RSS is a fantasitc way to gather information from disperate locations.
• Blogging is here to stay.  Having a blog template makes WSS 3.0 more friendly not only to the small business but it can be excellent for internal communications in a corporation.
• Recycle Bin: WSS 3.0 backup/recovery without the aid of an agent from the likes of Commvault is painful.  Having a recycle bin is excellent.

If you’ve not heard of WSS or seen it in action, I strongly encourage you to check out the MS virtual labs for Sharepoint technologies.  Don’t be scared, you do not need to be a "web slinger" to get great functionality out of this product.

I’ve seen some people asking about this, even on the day IE7 released.  MS has released Group Policy ADM templates for configuring IE7.

I just received the below in the mail.  Remember to check out my document on W2003/XP x64 SP2.

Windows Serviceability is pleased to announce the release of the Release Candidate (build 2825) of Service Pack 2 for Windows Server 2003 and Windows XP Professional x64 Edition.
This build contains:

Roll up of hotfixes released to date
Roll up of security updates released to date Fixes for bugs reported by Beta customers and other known issues on previous Service Pack 2 builds This build should be used for full deployment purposes, including pre-production testing or general compatibility testing. In order to have a stable test environment we strongly recommend un-installation of any previous SP2 builds from your machines before installing build 2825.

If you previously installed an integrated build of SP2, you cannot upgrade your system to build 2825 with this refresh; you will need to re-install a released version (RTM, SP1, or R2) of Windows Server 2003 before upgrading to build 2825. Go to https://connect.microsoft.com/content/content.aspx?SiteID=98&ContentID=1799 to find an evaluation copy of Windows Server 2003 Service Pack 1.

Release notes for this build can be found at https://connect.microsoft.com/content/content.aspx?ContentID=3881&SiteID=98.

With SP2, Windows Server 2003 x64 Editions will start supporting 9 new languages: Chinese Simplified, Chinese Traditional, French, German, Italian, Korean, Portuguese (Brazilian). Russian, and Spanish. With RC, Windows Server 2003 x64 Edition is available in German for the first time.

Additionally, with RC, a MUI servicing package is available, which is specific to 3 components (Microsoft Management Console (MMC) 3.0, Windows Deployment Services and Microsoft File Server Management). This is not a re-release of the Windows Server 2003 MUI Pack. This MUI servicing pack is designed to increase the compatibility between MUI and localized languages for these 3 components. More information about this pack can be found at https://connect.microsoft.com/content/content.aspx?ContentID=3890&SiteID=98.
The list of releases is as follows:
x86:

– Windows Server 2003 Service Pack 2 ISO image
– SP2 32-bit x86 standalone updates
– SP2 Standalone x86 check build (for debugging)
– Windows Server 2003, Web Editions with SP2 (32-bit x86)
– Windows Server 2003 R2, Standard Editions with SP2 (32-bit x86)
– Windows Server 2003 R2, Enterprise Editions with SP2 (32-bit x86)
– Windows Server 2003 R2, Datacenter Editions with SP2 (32-bit x86)

x64:

– Windows Server 2003 Service Pack 2 for x64 Editions ISO Image
– SP2 x64 standalone update
– SP2 Itanium Standalone check build (for debugging)
– Windows Server 2003 R2, Standard x64 Edition with SP2
– Windows Server 2003 R2, Enterprise x64 Edition with SP2
– Windows Server 2003 R2, Datacenter x64 Edition with SP2
– Windows XP Professional x64 Edition with SP2

Itanium:

– SP2 Itanium standalone updates
– SP2 Itanium standalone check build (for debugging)
– Windows Server 2003 Service Pack 2 for Itanium-based Systems ISO image
– Windows Server 2003, Enterprise with SP2 for Itanium-based Systems
– Windows Server 2003, Datacenter with SP2 for Itanium-based Systems

Tools:

– Windows Server 2003 Service Pack 2 symbols
– MUI Servicing Pack

We encourage you to continue WS03 SP2 Beta testing with this build and provide feedback.

This full length session discusses how Microsoft sees virtualisation in the market place.

Some highlights:

• Virtual Server 2005 R2 Service Pack 2 is expected to RTM in Q1 2007.
• A commitment to release the Windows "Longhorn" Hypervisor within 180 days of WIndows "Longhorn" RTM.
• The Hypervisor will be around 700KB in size … that’s the entire OS that will run on the physical host!
• 64bit CPU’s with Intel/AMD virtual technology are required.
• There will be support for 32bit and 64bit VM’s.
• VM’s can have up to 8 CPU’s.
• A VM will be able to have 32GB+ RAM.
• You can hot-add RAM, CPU, storage and network.
• You can run more than 64 VM’s on a host, depending on host hardware.
• An MMC 3.0 snap-in will be used to manage Windows "Longhorn" Hypervisor.
• A tunable MOM 2005 management pack is on the way for automatically identifying virtualisation candidates.

Mark Minasi has just published a new newsletter on his site.  In there, Mark talks about BitLocker, how to edit the hosts file and how to configure Vista to respond to pings without using GPO.

That’s the first thing I asked myself when I heard about the ADMX migrator.  Simply put, it’s the new version of Group Policy ADM templates but in an XML format.  Jeremy Moskowitz (consultant, speaker, trainer, author and AD whiz) briefly describes the new format for Vista and "Longhorn" in a recent newsletter.

Seeing as Office 2007 is now available via MSVL, MSDN and TechNet, I thought I’d post a reminder that I have documented the custom installation process via System Center Configuration Manager 2007.  This document was written while I still worked for 4sol.  The process of preparing your installation point is the same as it would be for SMS 2003/2003 R2 and Group Policy so check it out if you need to deploy Office 2007.  The process is different from the process we used with Office 2003 but it’s not totally alien and it is probably a bit easier to use.

This document was based on a beta release of Office 2007.  It will also be applicable to the other Office 2007 products such as Visio 2007, InfoPath 2007, etc, which also went RTM along with the core Office 2007 product.

I didn’t post anything earlier today because I wanted this one to be pretty clear and mistake free.  I read some contradicting articles online about the fate of good old Software Update Services.  The first post I read state it’s end of life had been extended.  I was then fluting about on microsoft.com and noticed an article about imminent end of life for SUS.  I’d tend to believe a MS source before an independant one, especially on MS support issues, so I was confused.

Before I go any further, lets get SUS/WSUS versions out of the way.  SUS was the first of the Microsoft solution for updating Microsoft products.  It only updated Windows operating systems, 2000, XP and 2003.  Internally, it is known as SUS 1.0.  It’s successor was Windows Server Update Services (WSUS) and internally it is known as WSUS 2.0.  WSUS 2.0 supported an extendible catalogue and thus is capable of supporting Windows, Office, SQL Server, Exchange, Forefront Client Security, etc.  WSUS 2.0 also feature better reporting, group targetting and granular control of updates.  WSUS 3.0 is currently in beta.  It supports the extendible catalogue but adds other features such as delegated reporting, even more granualr control of updates, multiple group membership for targetting and a more flixible download architecture.  I’ve documented the current beta release of WSUS 3.0.

This evening I checked the WSUS team blog.  They’ve cleared up the end of life issue of SUS 1.0.  It was due to end but due to customer demand, support for SUS 1.0 has been extended until July 10th, 2007.

It should be noted that SUS 1.0 can only be upgraded via a migration process to WSUS 2.0.  WSUS 2.0 can be "inplace upgraded" to WSUS 3.0.  So, anyone holding on to SUS 1.0 will litely need to consider either going through a 2 step upgrade to get to the latest release next year or just do a rip and replace.