Linked by Thom Holwerda on Tue 10th Jul 2007 22:50 UTC
Windows "Today at the Worldwide Partner Conference in San Francisco, Microsoft's chief operating officer, Kevin Turner, announced that Windows Server 2008 (previously known as Longhorn), Microsoft SQL Server 2008, and Visual Studio 2008 will be officially launched on February 27, 2008. This may come as a surprise to those following the Windows 2008 Server news closely, since most sources at Microsoft have been insisting that the next version of its server operating system will released at the very end of 2007. Apparently in Redmond there is a difference between releasing the OS and the extravagant product launches, which are more of a pep rally for the product then a technical presentation."
Thread beginning with comment 254408
To read all comments associated with this story, please click here.
Release vs Launch
by kad77 on Wed 11th Jul 2007 00:52 UTC
kad77
Member since:
2007-03-20

My first impression would be that Microsoft is allowing a 90 day bug hunt between going gold and official launch. We saw something similar with business licenses and general release for Vista.

Server admins are likely to be less forgiving in regards to bugs, instability, driver problems, and software incompatibilities. Stability trumps gee-whiz for me...

Given Vista SP1 is likely to be released around the time of Server 08, and both OSs benefits from the updates, this watch and see approach would make sense for them.

I may upgrade some licenses before their software assurance benefits run out -- at this point Server 2003 R2 is doing what it needs to without any problems.

RE: Release vs Launch
by kaiwai on Wed 11th Jul 2007 02:11 in reply to "Release vs Launch"
kaiwai Member since:
2005-07-06

My first impression would be that Microsoft is allowing a 90 day bug hunt between going gold and official launch. We saw something similar with business licenses and general release for Vista.

Server admins are likely to be less forgiving in regards to bugs, instability, driver problems, and software incompatibilities. Stability trumps gee-whiz for me...


I think the biggest problem is the delay with SQL server (and their other middleware); all the Microsoft software need to be up to scratch and working 100% perfectly on Server 2008.

Driver problems are third party problems, along with software maintained by lazy, money hungry third party vendors who refuse to release updates. What Microsoft can do is make sure their products are up to snuff and then able to be stand on the high horse and condemn those vendors who don't have their act together.

Given Vista SP1 is likely to be released around the time of Server 08, and both OSs benefits from the updates, this watch and see approach would make sense for them.


True - there are also some cool features which end users will benefit from. With that being said, so far, defender has been useless for my brother - he was infected with malware, thats ok, ran the scanner, thats ok, it found it, cleared it, but it still remained; it never actually removed it!

Whats the point of bundling 'defender' if it fails to defend?

I may upgrade some licenses before their software assurance benefits run out -- at this point Server 2003 R2 is doing what it needs to without any problems.


Just out of curiosity, what do you use your servers for - is there a particular role which demands that you use Windows over using a *NIX of some sort?

Reply Parent Bookmark Score: 1

RE[2]: Release vs Launch
by kad77 on Wed 11th Jul 2007 04:17 in reply to "RE: Release vs Launch"
kad77 Member since:
2007-03-20

I think the biggest problem is the delay with SQL server (and their other middleware); all the Microsoft software need to be up to scratch and working 100% perfectly on Server 2008.


Sure, that would be an important component. Updating their middleware and giving the largest vendors ample time to get their software in the same position.

Driver problems are third party problems, along with software maintained by lazy, money hungry third party vendors who refuse to release updates. What Microsoft can do is make sure their products are up to snuff and then able to be stand on the high horse and condemn those vendors who don't have their act together.


Driver problems are also end-user problems. Some devices or custom software may not ever be updated to a new system, and somewhere in an organization, that part of the system may just be maintained as is. NT/2000 installations still exist.

Just out of curiosity, what do you use your servers for - is there a particular role which demands that you use Windows over using a *NIX of some sort?


Yes - third party MIS/EHR software used in medicine. Competing systems are always emerging, some web based (internal or hosted), or using a SQL system that is OS agnostic. Many systems in the field (like the ones I'm responsible for), are Windows based though, and are written to non-portable DB products like MS SQL Server. One uses Advantage (iAnywhere) and another uses Oracle, but the supported configuration requires they be installed on Windows.

At first glance, the main benefits I can see coming from this new MS server OS are in the areas of security. Outside of AD, the rest of our business related 'software services' are provided by non-Microsoft software.

Reply Parent Bookmark Score: 3

RE[2]: Release vs Launch
by MamiyaOtaru on Wed 11th Jul 2007 13:53 in reply to "RE: Release vs Launch"
MamiyaOtaru Member since:
2005-11-11

so far, defender has been useless for my brother - he was infected with malware, thats ok, ran the scanner, thats ok, it found it, cleared it, but it still remained; it never actually removed it!

Whats the point of bundling 'defender' if it fails to defend?


Failing to remove a particular malware doesn't make Defender useless. Failing to remove any malware would. Some malware is just a tougher nut to crack than others, and if it is relatively new, there probably won't be any programs capable of rooting it out completely.

Fun with semantics: I'd say the spot where Defender failed to defend was when it let the malware in in the first place rather than when it couldn't remove it. Prevention ought to be easier to do (the instructions for preventing malware are never "reinstall windows" ;) ).

Reply Parent Bookmark Score: 3