Longhorn question.....

[butchrecon]

I am not sure where to post this question. I did not see a forum for Longhorn. Anyway...The next Windows OS, AKA Longhorn, does anyone know what the minimum requirements at this time will be for it?

James Collins
Systems Analyst
A+, MCP, MCSA, Network+

 

[Auger282]

Here are Microsoft's Longhorn hardware recommendations:

Desktop CPU: 3 GHz Intel Pentium 4 processor with HyperThreading Technology 530 (or higher) or 3 GHz Intel Xeon processor with 2 MB L2 cache, or AMD Athlon 64, Sempron, or Opteron 100, 200, or 800 processor, single or dual-core versions.

Mobile CPU: 1.86 GHz Intel Pentium M processor 750 (or higher), or AMD Turion 64 Mobile Technology, Mobile Sempron, or Mobile Athlon 64 processor.


Google is our friend.

 

[xkjdhdg]

Average Longhorn Requirements (Microsoft Recommends)
Processor: Dual-core CPU running at 4 to 6GHz
Memory: 2 GB to 4 GB (Double minimum is average)
Hard disk: Up to a terabyte
Networking: 1 Gbit, built-in, Ethernet-wired port and an 802.11g wireless link
Video: Graphics processor that runs three times faster than those on the market today
Longhorn's Expected Requirements (2006)

 

[butchrecon]

Thanks, Google gave a ton of info, however it seems nearly every site I went to had a different set of "Minimum" requirements. That is why I came here to ask other professionals for what they have seen.

James Collins
Systems Analyst
A+, MCP, MCSA, Network+

 

[bcastner]

My own two cents.
Microsoft specifies the following:

http://www.microsoft.com/whdc/device/display/graphics-reqs.mspx

Note that it matters greatly whether you are using Aero/Glass, Aero or Classic.

 

[xkjdhdg]

I think is going to be like most of the other windows OSs.
It will run on just about anything. There is always the recommend but you I know most people are running older machine and will try to update those as for as they can. It is basiclly a trial and erro thing.

 

[Auger282]

http://blogs.msdn.com/larryosterman/archive/2004/05/06/127305.aspx

"First off, Robert’s totally right about the developer machines here. Longhorn’s being developed for the most part on 3gHz or lesser machines – my test machine’s a year old hand-me-down 2gHz P4 (no HT) with 700M of RAM. Longhorn works just fine on it.

 

[butchrecon]

I am doing an assessment of potential needs for the future purchases of the company I am at. We have a lot of 1GHZ or less machines (Most of these machines are 650 - 933 MHZ) with a MAX of 512 RAM. We want to ensure these machines can run Longhorn when it is released, if not then we will have to begin replacing them before its release. Indications right now don't look good for us on this. Replacing 600+ machines wont be cheap or easy, hence why I am looking into the requirements of Longhorn.

James Collins
Systems Analyst
A+, MCP, MCSA, Network+

 

[LloydSev]

the last Longhorn build I tried ran fine on my old Athlon XP 2000+ system..


But that was without any of the graphical enhancements that will ship with the product.

Computer/Network Technician
CCNA

 

[bcastner]

butcrecon,

I have the same concerns.

I think your planning for Longhorn should include a toss of your installed Workstation base, and a complete replacement. In my Beta experience, you do not "get" the longhorn effort without Glass.

I wish Intel and AMD would help here. There is not yet available the dual-core promises by either, but this should ship in time to coincide with Longhorn final.

 

[butchrecon]

bcaster,

I wish it was that simple. I work for an Aerospace company with over 1500 users. 900+ of those users have machines that should do fine, however it is those 600+ I am concerned about. We live in a time when companies tighten up and budgets shrink by the minute. I would like to replace those 600 machines, but realistically that may not happen right away. We will more than likely have to get things to work with what we have. I would like to beef up these machines before Longhorn comes out. but without solid requirements, getting approval will be difficult for my management. We may end up playing catch up after Longhorns release, which as I am sure you know is always fun to do.

James Collins
Systems Analyst
A+, MCP, MCSA, Network+

 

[LloydSev]

Exactly.. Longhorn's requirements go up as it becomes more and more complete.. and the worse the video card you have, the higher the CPU requirement.. So you'll want to make sure that the systems you buy have 3D video cards.

Computer/Network Technician
CCNA

 

[bcastner]

butchrecon,

Longhorn is interesting for what it can possibly provide. Such as WinFS.

But you have to convince the users of the 600+ plus machines to stay with XP.

This is a perfectly valid business choice.

In my consultancy practice I have a very cheap longtime client, who always asks me "Why should I upgrade? Everything on this LAN works exactly as I want it to." The upgrade suggestion comes from the most recent computer magazine he has read. This guy is running Netware 3.12, and mostly Windows98 clients, and their primary need is to run an accounting program.

Chasing the latest and greatest in technology changes is not often a good choice.

My greatest concern at the moment for pre-XP and the question of Longhorn is security. If running XP, you should be at Service Pack 2. If pre-XP this is a bad decision long term for security reasons. Longhorn introduces additional features that will not be included in XP through a service pack. My own planning would be the planned toss of existing systems, and the use of Longhorn.

 

[butchrecon]

Users do not have a say in what OS they use. Since we utilize Microsoft's Volume Licensing and Corporate licensing, we will more than likely be required to go to Longhorn once it is released. I am fine with XP w/SP2. But it is not my decision. I can only make my recommendation.

James Collins
Systems Analyst
A+, MCP, MCSA, Network+

 

[bcastner]

butchrecon,

While your actual site policies and details are a little unclear to me, you will not by Micrsoft be "forced" to user Longhorn.

It certainly will not appear through Windows Update.

 

[butchrecon]

I not 100% clear on how we utilize the policies either, we have software licensing specialist for that. I was under the impression that, because of our agreement, we are required to change shortly after an OS release. Oh well, not my job to know I guess.
From what I have been told, we will deploying longhorn sometime after its release. I would rather stick with XP, but I am not part of the decision making process for that. My job is to ensure that what we have hardware wise will work. We had a similar issue when XP was released. Since al the machines that were running 2000 fine met the requirements for XP it was not an issue. However since Longhorns requirements may be much larger, I need to ensure we have what we need to run it. I appreciate all the discussion on this. It has been very helpful. This will be an ongoing task until MS officially releases Longhorns requirements. So much for being prepared.


James Collins
Systems Analyst
A+, MCP, MCSA, Network+

 

[LloydSev]

Remember that Longhorn is still a ways off yet.. you have plenty of time to get official specs.

Computer/Network Technician
CCNA

 

[jrbarnett]

To say that because your company has a Microsoft corporate license for its professional operating systems, you have to keep up with the latest is not true.

Where I work we have a similar agreement in place, and are on Windows 2000 throughout. We wipe manufacturer supplied XP and install 2000 for the sake of consistency across all machines.

John

 

[bcastner]

buthercon,

Because nothing is "written in stone"

I believe there will be a public release version of Longhorn for trial. It is my understanding that the public RC1 will be in July, 2005, RC2 in October, 2005 and LongHorn RTM in first quarter 2006.

The private Beta testers have to endure more frequent product changes.

It might be wise for your organization to have a paid subscription to MSDN or TechNet.

When the public Release Candidate for LongHorn ships, if someone else has not beaten me to the punch I will surely post a link.

 

[butchrecon]

We do have a MSDN Subscription. I know we will evaluate the RC when it arrives. As for licensing and being forced to move to new OS's, I agree it may not be MS's policy, it may be our own policy. As I have stated I do not have a say in that. I am just trying to evaluate our hardware needs, and come up with a viable strategy before Longhorn is released that way we are not trying to replace or update the older machines after the new OS release. I know we will be going to it. The IT management has already stated as much.

With the budget crunches and downsizes going on, replacing 600+ machines at the same time will not happen. But before I can suggest a strategy that states we begin to update those PC's now so when Longhorn is released all we will have to do is re-imaged all the machines, I will need to have justification and hard data to back up that justification in a couple of weeks. With no set requirements for Longhorn yet my task is difficult at best.

James Collins
Systems Analyst
A+, MCP, MCSA, Network+