Wednesday, April 15, 2009

End of free support for some Microsoft products…

This April, 14 marks the end of free support for Windows XP and Office 2003, so in the same way to Windows Server 2003 SP1, “meaning it will no longer provide support for that four-year-old release”.

Microsoft is offering paid, extended support for XP Professional users (who also have Software Assurance licensing contracts) until April 8, 2014. It also will provide paid, extended support for Office 2003 through August 4, 2012.

In case you’re wondering about support deadlines for other Windows and Office products, here is the link.

So according some calculations of Mary Jo Foley, about the support deadlines, the following list is a good start if you’re interested:

Windows 2000: Free support ended June 30, 2005; paid support ends on July 13, 2010. Service Pack 3 was retired on June 30, 2005. No more SPs planned.

Windows XP SP2: Service pack will be retired on July 13, 2010.

Windows XP SP3: Service pack due to be retired two years after SP4 (if there is one) releases or in  April 2014, whichever comes first.

Windows Vista Business: Free support ends on April 10, 2012; paid support ends on April 11, 2017.

Windows Vista SP1: Service pack will be retired two years after the release of SP2 (which is expected in April 2009), so likely in April 2011 (?).

Office 2003 SP3
: Service pack will be retired one year after SP4 (if there is one, which is doubtful) is released or in August 2014, whichever comes first.

Office 2007: Free support ends on April 10, 2012; paid support ends on April 11, 2017.

Office 2007 SP1: Service pack will be retired a year after SP2 debuts, so likely in April 2010 (?).

Windows Server 2008: Free support ends September 7, 2013; paid support ends October 7, 2018.

This month also marks the final release for Vista SP2 and Office 2007 SP2.

Among the new features slated for Office 2007 SP2 are previously announced file-format changes — specifically support for Open Document Format (ODF), Microsoft’s own XML Paper Specfication (XPS) and PDF. SP2 also is expected add improvements to Outlook calendaring reliability and improved Outlook performance overall; improvements to Excel’s charting mechanism; the ability for Visio to export UML models to an XML file compliant with the XMI standard; and an uninstall tool for Office client service packs.

Vista SP2 is anticipated to include a new capability for recording data on to Blu-Ray media natively in Windows Vista; the addition of Windows Connect Now for simpler wifi configuration; fixes for DRM issues from WMP upgrades; the Vista Feature Pack for Wireless; functionality for reducing resources required for sidebar gadgets; and more.

So I hope this information extracted of a post of Mary Jo Foley should be interested for you…

Best regards…

Tuesday, April 07, 2009

Forcing Sharepoint Server 2007 Uninstallation

Hello everyone...

This is a hot post...a few minutes ago I was trying to forcing a SharePoint Server 2007 uninstallation, the reason...well the farm totally crashes...well I have all the responsibility over the fault, because I detach the ContentDB for the Central Administration Site, I tried to attach it again, but with no success.

So in my test environment I decided to restart the process, but for my surprise I can’t remove the MOSS installation, well the reasons are so clear, I destroy the farm, but why the uninstallation program fails...?

Surfing over the internet, I found a post a little strange for my, but after a while of thinking on it…is so logical, the way to force the uninstall…

To force the uninstallation of both products to get back to a stable state, this is what I did.

I had no data to save, this was only a test environment, I’m so lucky!!

I renamed the DSN in the registry for a moment:

HKLM >> Software >> Microsoft >> Shared Tools >> Web Server extensions >> 12 >>Secure >> ConfigDB >> DSN to DNS1,for example…the name is not important.

Then you can:

- Uninstall MOSS 2007.
- Delete the web applications and their respective AppPools.
- Delete the SQL databases.

After this you can rebuild the farm as you desire.

As a little note related with this, in some cases this problem occurs after the installation of KB 932091, update to WSS 3.0. The system was rebooted (by mistake) before the update was finished.

After that the system was unstable:

- I could not run the SharePoint Products and Technologies Configuration Wizard (Upgrade in progress).
- I could not uninstall Project Server 2007 or MOSS 2007, they both failed.

Log files indicated that the operations could not be completed because an update was in progress…

I hope that this helps, as I tested this procedure works in any case that the program fails or the system becomes unstable.

Best regards…

Paúl…

Sunday, April 05, 2009

Office 14, will be available in 64 bits version

Anyone who made the change to a 64 bits operating system, can told you, that most of the applications still don’t have native support for this kind of systems.

However during the last years, the number of people who made the change, is still growing. The computer manufacturers offers 64 bits systems with more and more RAM and Microsoft expects that the most of Windows 7 installations will be of 64 bits. Is for this reason that the company has decided to take this road with these applications.

As we saw in previous Office applications Microsoft will offer 32 & 64 bits editions with their respective upgrades from Office 2003 or 2007 with a single installation package.

This Office version surely will be available in the first months of 2010.

Friday, April 03, 2009

MVC Pattern for ASP .NET RC2

Hello…

So a quickly post, a few weeks ago I told about Oxcite an open source CMS, ASP .NET & MVC based solution.

Well now Microsoft releases the RC2 with a little corrections and enhancements for design and developed large business sites.

Give an eye on this…

Bye…

Internet Explorer 8 is finally here…!!!

Well an older post said…IE 8 was coming up, but I leave you with some questions, like IE 8 was part of Seven…?

Well apparently is true, Windows 7 Beta, already have IE 8 as default browser, and of course as a separate download for XP, Server 2003 & Server 2008.

Is so fast, more secure, and many improvements that are most welcome for this version of the popular browser.

But that doesn't mean users and developers are satisfied. Instead, many are champing at the bit to get Microsoft to commit to their favorite missing features for IE 9.

Well the updates maybe include some improvements….

Regards…

Paúl

Wednesday, April 01, 2009

Removing Visual SourceSafe Bindings

Hi everyone, in the early years of .NET platform Visual SourceSafe rules, concerning with ensure the code and version management. Now we have Team Foundation Server and the things are so much better in some aspects, on the other hand no, nothing and nobody is perfect.

Today I have a little problem, remove the SourceSafe bindings, and really I can’t remember how to do it, so after a little while here is the solution.

Some of you maybe told me that SourceSafe is no longer the best solution in our days, but believe me…SourceSafe really does the job…Here is the workaround the source code consists of a solution (MySolution) containing a single project or projects (MyProject). 

You attempt to open the solution and find that it has SourceSafe dependencies.  You need to remove all the VSS stuff from the solution/project files, follow these steps:

1 - Go to the folder containing the solution files and delete the following:
          mssccprj.scc
          MyProject.vssscc
          vssver.scc

2 - Open MyProject.sln in your favorite text editor and remove the following section:
          GlobalSection(SourceCodeControl) = preSolution
                     ...
          EndGlobalSection

3 - Go to the folder containing the project files and delete the following:
          MyProject.vbproj.vspscc
          mssccprj.scc
          vssver.scc

4 - Open MyProject.vbproj in your text editor and remove the following lines:
          SccProjectName = "SAK"
          SccLocalPath = "SAK"
          SccAuxPath = "SAK"
          SccProvider = "SAK"

Now you can open the solution/project with no source control errors.

Hope it helps for the fans of source safe…jejeje :P