Hi,
I'm pretty new to the whole Windows server thing. I have been assigned to set up a new network for my company, to run a new ERP solution. We have ordered 2 servers, which I currently have in my possession. Now I need to purchase operating systems, licenses, and SQL database software/licenses. The ERP solution calls for Windows server 2003 R2, and I plan on purchasing the x64 edition for our xeon servers. I will need 2 copies of this, one for the database server and one for the server that will run Terminal Services. However, I am told that I now need to purchase Windows server 2008 server AND Client licenses, and then downgrade these licenses so I can use them for windows server 2003. I have read up a lot on this topic, especially on Microsoft's website, but I am still very confused. Mainly I just want to make sure that I don't go out and spend 5500 dollars on the wrong stuff. We will have 10 users accessing the ERP system.
I will need to purchase the following:
2 windows server x64 licenses
10 user cals to access the servers
10 terminal server cals
1 SQL server 2005 x64 server license
10 SQL server 2005 user cals
I'm hoping someone can clarify the following... Based on the above list I am assuming I will need...
- 2 Windows Server 2008 no hyper-V licenses - Open Business (Then downgrade to win2k3 R2)
- 10 Windows server 2008 User CALs - Open Business (Do i need to downgrade these as well to work with win2k3?)
- 10 Windows server 2008 TS CALS - Open Business (Do i need to downgrade these as well to work with win2k3?)
- 1 SQL server 2005 x64 server license
- 10 SQL server 2005 user licenses
- 1 Windows server 2003 R2 x64 Media Only
- 1 SQL Server 2005 x64 Media Only
Or instead, can I buy a Windows server 2008 package including media + 5 or 10 cals, and downgrade all of this for use with 2003? If so, retail or OEM? Or do I need to purchase all licenses separately and then the win2k3 media?
I know these are annoying newbie questions, but its been driving me nuts.
Any insight would be greatly appreciated.
Thank you,
Kyle
I'm pretty new to the whole Windows server thing. I have been assigned to set up a new network for my company, to run a new ERP solution. We have ordered 2 servers, which I currently have in my possession. Now I need to purchase operating systems, licenses, and SQL database software/licenses. The ERP solution calls for Windows server 2003 R2, and I plan on purchasing the x64 edition for our xeon servers. I will need 2 copies of this, one for the database server and one for the server that will run Terminal Services. However, I am told that I now need to purchase Windows server 2008 server AND Client licenses, and then downgrade these licenses so I can use them for windows server 2003. I have read up a lot on this topic, especially on Microsoft's website, but I am still very confused. Mainly I just want to make sure that I don't go out and spend 5500 dollars on the wrong stuff. We will have 10 users accessing the ERP system.
I will need to purchase the following:
2 windows server x64 licenses
10 user cals to access the servers
10 terminal server cals
1 SQL server 2005 x64 server license
10 SQL server 2005 user cals
I'm hoping someone can clarify the following... Based on the above list I am assuming I will need...
- 2 Windows Server 2008 no hyper-V licenses - Open Business (Then downgrade to win2k3 R2)
- 10 Windows server 2008 User CALs - Open Business (Do i need to downgrade these as well to work with win2k3?)
- 10 Windows server 2008 TS CALS - Open Business (Do i need to downgrade these as well to work with win2k3?)
- 1 SQL server 2005 x64 server license
- 10 SQL server 2005 user licenses
- 1 Windows server 2003 R2 x64 Media Only
- 1 SQL Server 2005 x64 Media Only
Or instead, can I buy a Windows server 2008 package including media + 5 or 10 cals, and downgrade all of this for use with 2003? If so, retail or OEM? Or do I need to purchase all licenses separately and then the win2k3 media?
I know these are annoying newbie questions, but its been driving me nuts.
Any insight would be greatly appreciated.
Thank you,
Kyle