On Wed, Jul 30, 2008 at 5:29 PM, Adam West <adamster@xxxxxxxxx> wrote:
Leaving aside the cost of the software which is higher to begin with. I am looking for the hardware, communications, training, personel, etc. that if you have done this or considered this option you can speak of.
Well, the answer is: It depends. the more details you provide, the
more detailled answers you will get.
What do you have right now in terms of Windows infrastructure? What
does the application require in terms of Windows infrastructure?
In general, you'll need a Windows Server license per server you run
Windows on. You'll also need a Windows CAL per device or user
accessing the Windows Server. Additional Microsoft applications like
SQL Server can be licensed for example on a per Socket or a per User
base.
For the hardware, it depends on what the application requires - there
are simple 1U, 1 socket servers like the IBM x3250 up to 32 socket
machines like the x3950 M2. Depending on the hardware you need, you
might need different Windows licenses. For example, you can't run
Windows Server Standard on a 32 socket machine. Remember that you also
need for example a management card for lights out management similar
to the HMC on the i.
Communications - well, network connectivity is either Gigabit
Ethernet, which is standard for all servers or 10GE which you need to
buy separately. Depending on the applications, you might need a SAN
for storage.
Regarding personnel - you'll need to hire someone with the necessary
qualifications or get someone in training - which will probably take
around a year to get someone from "0 windows knowledge" to "knows the
basics of a windows infrastructure".
midrange.com
