Jump to content

Recommended Posts

Posted

As a lot of you know, I just use servers as file/print/dhcp/dns servers with XP home/Win7 Starter clients. I don't use AD.

 

I'm setting up a new school (new to me that is) 40 new Win7 clients with about 20 old XP Machines with a new physical server machine.

 

Should I go with w2k8 instead of my tried and tested w2k3. Will it give me any advantages for my non-AD setup.? All will it give me headaches?

 

regards

 

Simon

Posted
New build, newest OS - just makes sense from a maintenace perspective. Not sure if the services you use have many changes over 2k3, but some newer features are pretty cool.
Posted
Also take into account security updates finish for 2003 in 2 years. So when that time comes you will have to update anyway. You might as well do it now.
Posted

id go with a current os so 08r2

 

not to mention you might find it hard to get drivers for 2003 on current hardware

 

now granted if its just being used as a nas box with dhcp/printers most of the 08r2 extras are probably of 0 use

 

though depending on your printers you may have driver issues with them on 08r2 older hps are particularly prone to being poor imo

  • Thanks 1
Posted

Ta people :)

 

I'm thinking now I should install w2k8 on the new physical server and vm convert the old w2k3 server onto it and keep that as the printer server for the old printers (until I can persaude the head of having 2 networked photocopiers for printing (I love my schools that have this :) )

 

Simon

Posted

If you're going to continue to use a server just for File, Print, DHCP and DNS there are zero benefits between 2003 and 2008/2008 R2. Basic file services are the same, Print Management is great, although you couldn't use it, DHCP allows you to use IPv6 out the box and DNS is the same too.

 

If you were going to use Active Directory and Windows 7 Professional, then there are a lot of advantages to using 2008 R2. It allows you to control 7 to the max.

 

Extended support for 2003 Server is July 2015.

Posted
All will it give me headaches?

 

 

2003 > 2008 print server caused us a mass of headaches with drivers for XP/win7 64.

I avoided linux print servers because I thought the transition would be more simple with windows. I was wrong.

Once it was setup it ran fine, but with 50+ printers and papercut it was much more of a headache than I expected.

Posted
2003 > 2008 print server caused us a mass of headaches with drivers for XP/win7 64.

I avoided linux print servers because I thought the transition would be more simple with windows. I was wrong.

Once it was setup it ran fine, but with 50+ printers and papercut it was much more of a headache than I expected.

 

Depends on the printers and drivers, we had no issues with our HP gear, I know many like to hate on their drivers but they worked fine for us. Besides if you have any 64bit clients you need to get it sorted anyway.

 

If you are putting it in new go 2008 R2 simply because it is the current one and you are not installing something that is going to fall out of support so quickly in comparison. There is no point in investing an and installing old tech as you are just causing problems for the future by constraining yourself now. How well do you think 2003 will cope with Windows 8 PCs etc as your server will probably still be around at that time.

Posted
Depends on the printers and drivers, we had no issues with our HP gear, I know many like to hate on their drivers but they worked fine for us. Besides if you have any 64bit clients you need to get it sorted anyway.

 

If you are putting it in new go 2008 R2 simply because it is the current one and you are not installing something that is going to fall out of support so quickly in comparison. There is no point in investing an and installing old tech as you are just causing problems for the future by constraining yourself now. How well do you think 2003 will cope with Windows 8 PCs etc as your server will probably still be around at that time.

 

absolutely; it was entirely driver problems which we would have needed to sort anyway for 64bit. They were all HP laserjets, loads of different models.

Its all working now, just took about a week ironing out glitches.

Posted (edited)
absolutely; it was entirely driver problems which we would have needed to sort anyway for 64bit. They were all HP laserjets, loads of different models.

Its all working now, just took about a week ironing out glitches.

 

wouldn't have having hp laserjets actually made that side of things easier, what with the UPD ?

Edited by alttab
Posted
As a lot of you know, I just use servers as file/print/dhcp/dns servers with XP home/Win7 Starter clients. I don't use AD.

 

I'm setting up a new school (new to me that is) 40 new Win7 clients with about 20 old XP Machines with a new physical server machine.

 

Should I go with w2k8 instead of my tried and tested w2k3. Will it give me any advantages for my non-AD setup.? All will it give me headaches?

 

regards

 

Simon

 

in most areas w2k8 won't add anything revolutionary for basic things like dhcp, dns and print.

 

the improvements made in the areas of DFS and Quota management which come under the file services banner could be significant enough to make the difference should you choose to use them later on.

  • Thanks 1
Posted
wouldn't have having hp laserjets actually made that side of things easier, what with the UPD ?

 

depends on teh printer upd dosent support a lot of older gost driven printers and even those that have built in drivers the built in drivers are p poor in some cases (k5400 for example)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...