Windows Forum

Ask something
Discussion Locked

server inventory metrics analysis

0 helpful
7 replies

by jscherer

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My company is embarking on an enterprise wide Windows 2000 server implementation project. In support of this initiative, we are compiling an inventory of our "server farm". The inventory will include detail information about each server (location/size/apps running/etc.). Once completed, we had hoped to compile a summary of key information points (metrics) that would assist us in scheduling/planning the Win2000 rollout. Are samples of this type of analysis available that would show what type of information one needs to know? I'm sure others have needed this type of information, for this purpose,before??

7 replies

by timthetoolman

Hi,

If your installation is big enough, then you'll probably want to consider Microsoft's SMS (Systems Management Server) which can do audits of both hardware and software right across your network.

It can also be configured to remotely install software... not a bad tool really, but expensive.

I last used it several years ago and it was a little clumbsy and awkward but I'm sure its improved ten-fold since then.

http://www.microsoft.com/smserver/default.asp

(remove spaces from theabove URL)

Also as an aside, Microsoft's Visio for the Enterprise is now capable of analysing your network and producing a network diagram for you.

I've never used this feature or even seen it used, but if you check it out, I'd like to know whether you think its any good!?

Cheers,
Tim.

by jscherer

"Sorry Tim" but what I am looking for is help on how one goes about analyzing the server inventory to determine how the information can be used in the win2K server implementation project.

by timthetoolman

Hi,

You mean that you already know whats kicking around on your network - you already have that information - but now you need to know how to progress to the next step to roll out the new servers in a phased implementation?

If I've got your requirements this time.... then its more a case of putting together a matrix of applications, their resource requirements and their dependencies on each other.

From that will come an order in which you can address the rollout and hopefully which applications can and should co-exist on the same servers.

Its always best to leave the server you're upgrading "intact" and to install on a fresh server. With careful planning, you should be able to buy one new server... start with that... and then do a "hand-me-down" to all the other servers.

This way its trivial and quick to rollback to the working server if anything should go wrong. Of course if you cant afford that, then comprehensive backups will just have to do.

Before I go on.... isthat the kind of thing you were after?

Cheers,
Tim.

by jscherer

Thanks again Tim-I'll try one more time. I've got all this server inventory related "data". The question is, how can I turn it into actionable information that I can use to develope/define a win2k server implementation strategy? What are the metrics I should be looking at, other than the obvious? (i.e. mission critcal apps/server interdependices/network configuration,etc.)? In other words, I need a list of the kind of information "points" about my hardware/network that I need to know tojustify sizing/scheduling/costing/and, ultimately, executing the project/implementation in a certain manner. Clear as mud? Thanks, from the poor schnook Project Manager that has to make it happen-somehow!

by timthetoolman

Hi,

So in a nutshell you want a list of all the items you'd be considering for the rollout? ...in order to come up with "sizing/scheduling/costing/and, ultimately, executing the project/implementation in a certain manner" ...but hopefully within the scope of the inventory data you mentioned in your original question.

I think I'll get a coffee! Oh well, here's an attempt... but not from a text book so you might want to read up too... Sorry for the /'s but TechRepublic doesn't handle tabs.
Application

/Resources
//CPU
//memory
//Disk IO
//Disk storage
//Network utilization

/OS requirements
/Software component requirements (for example a specific MDAC version or requires IIS)
/Software version upgrade requirements (Maybeonly a newer version of a package will be supported on Win2K)
/Patches and upgrades to the base version from "Software version upgrade requirements"
/Projected growth (not directly from the "data" but applicable to it...)

....and am I on the right track this time?

Cheers,
Tim.

by jscherer

Yes, I'm on my 6th cup-maybe even a few Fosters thrown in! I'm looking for a list of the types of questions that need to be asked and answered to help formulate a strategy. For example: From the inventory, I know the applications running on the servers-so, that tells me what vendors to contact to determine their level, if any, of compatibility with win2k server. I will then know what servers to migrate, based on software compatibiliy, and which ones that I must wait to upgrade,until I can get new, win2k server compliant versions of their software. In this way, analysis of the inventory will help me define my migration scope and content.
Now, what other kinds of questions, like my example, need to get asked?

Would it be helpful if I listed all of the column headings from our server inventory spreadsheet?

Thanks.

by timthetoolman

Hi,

Yes.... it would help to get that list. That'll give me some much need bounds for answering the question!!

Cheers,
Tim.

This discussion is closed to new replies.