please advice

[marcink99]

I have one server 2003 sbs that is a dns/active directory/file/application/router/exchange/ias server
I plan on upgrading to a newer hardware as this one is already 5 years old. Luckily I never had a problem with it.

questions

1) since I’ll be upgrading to a new hardware should I migrate to new server2011 considering the fact all my licenses are for 2003?(12 workstations)

2) How can I minimize down time if something to go wrong. Mail and QuickBooks access is crucial to the business. I am considering purchasing second server for backup (cluster) from my understanding I would need enterprise edition of the server os. Not sure if there is a better option.

3)I plan on upgrading 4 or more workstations should I wait for the release of the windows 8? I read somewhere that it will be released in april 2012.

 

[krtechsolutions]

if you don't want to upgrade your cals and such and what to keep down time down to a min

go with a esxi server and do a p2v on the sbs server, this will keep you down time down to about 30mins to 1.5 hrs.

but me personally i would upgrade to SBS2011, however you will need a standalone router/firewall as sbs2011 does not have ISA, i can do an SBS move with little downtime really as long as it takes to reboot your sbs 2003 box after the mirgration setup, then after that i move user data all at once, then point the folder redirections and mapped drives to the new share, then mover printers, then i move all the exchange mailboxes, then install any 3rd party applications such quickbooks or peachtree then move that data, i move all the data after hours

and yes for clustering you need enterprise, which would be a whole other beast from a sbs move

i would go away and just buy the workstations now no need to wait, windows 7 and windows 8 will be about the same OS in the background just the interface will be different

 

[marcink99]

hmm thats a very good idea but if hardware fails I will be down for much longer time. Any ideas?

Do you have any idea if quickbook would work on virtual clients I looked into ncomputing x300 pc station.

Are their any free vmware versions that I could use for deployment of virtual clients? Iam not very familiar with vmware licencing. When purchasing vmware license do I still need to purchase separate os licenses?

Thank you for helping out

 

[wimwauters]

hmm thats a very good idea but if hardware fails I will be down for much longer time. Any ideas?

The days of dual-socket motherboards and hardware RAID cards are long gone. Build 2 ESXi machines: DDR3 and single-socket boards are cheap

Basically, all you need is plenty of RAM and some half-decent storage (software) driver that can handle stripes of RAID1 mirrors, aka RAID10.

I'm a XenSource/Server/Cloud guy, but the principles stay the same.

Are their any free vmware versions that I could use for deployment of virtual clients? Iam not very familiar with vmware licencing.

https://www.vmware.com/tryvmware/?p=free-esxi&lp=1

Also, this will help you to understand the difference between a 'virtualisation sever' and a 'hypervisor':

http://www.vmware.com/products/server/faqs.html

When purchasing vmware license do I still need to purchase separate os licenses?

If you are stuck with Mickeysoft, then yes. On top of that, don't forget them lovely CALs. Obviously, the server license does not include actually connecting to clients...

Tip: for medium size businesses, shop around for an OEM license with 25 or 50 CALs.

With Solaris/Linux/BSD on the other hand, you don't even have to type in a license

 

[marcink99]

I need some more info if you guys don’t mind. I plan on purchasing before end of the year.

So far I will be getting
vostro workstations with i3 and 4gb ram
For server I will go with t110 or t310 not sure yet.

What would I need to set up esxi server. Should I get some sort of external storage so that when something happens I could connect another computer to the storage and lunch it as a server?

Not sure how it work but if my server dies how would I transfer data onto another computer if it’s not using external backup?
I guess I could schedule daily backups but is that the best way?

Thank you for all the help

 

[YeOldeStonecat]

I've done plenty of SBS migrations to new hardware, but keeping the install, by doing a VMWare "P2V"....it's quite easy...assuming you're familiar with VMWare/ESXi....and how to work with it. No more local console on that server.

But you may want to take into consideration having your client opt for a more full upgrade...as SBS2k3 is getting old, they may consider upgrading to the latest version of SBS. This way you could do a typical bare metal install of the new SBS on the new server, and do the migration off-hours.

And get them being a proper firewall...ack..running SBS as their router...YIKES!!! Exposed Windows box = danger unless you're very comfortable with stripping down Windows and locking it down..which renders it useless for a network.

I would suggest a "real" server....starting in the 300 range, stay away from those barely glorified desktops trying to act like a server in the 100 model range. SBS on RAID 1 OS and RAID 5 or 10 for the data. SAS drives...stay away from SATA on servers...especially something as heavy as SBS. SATA is for desktops. 16 gigs of RAM. Quad core or higher.

 

[marcink99]

I've done plenty of SBS migrations to new hardware, but keeping the install, by doing a VMWare "P2V"....it's quite easy...assuming you're familiar with VMWare/ESXi....and how to work with it. No more local console on that server.

But you may want to take into consideration having your client opt for a more full upgrade...as SBS2k3 is getting old, they may consider upgrading to the latest version of SBS. This way you could do a typical bare metal install of the new SBS on the new server, and do the migration off-hours.

And get them being a proper firewall...ack..running SBS as their router...YIKES!!! Exposed Windows box = danger unless you're very comfortable with stripping down Windows and locking it down..which renders it useless for a network.

I would suggest a "real" server....starting in the 300 range, stay away from those barely glorified desktops trying to act like a server in the 100 model range. SBS on RAID 1 OS and RAID 5 or 10 for the data. SAS drives...stay away from SATA on servers...especially something as heavy as SBS. SATA is for desktops. 16 gigs of RAM. Quad core or higher.

Please read post above you I never planned with not going with real server. Thanks for helping out.

 

[YeOldeStonecat]

Please read post above you I never planned with not going with real server. Thanks for helping out.

I did read it....
Aren't these your words?

For server I will go with t110 or t310 not sure yet.

So..to me, that makes me think that you are considering a T110, or a T310.

If that is indeed correct, my reply will be the exact same that I typed above..."please read above reply".
Lemme re-word...The T-300 range are decent servers...s'long as you get SAS drives.
The T-100 range are glorified desktops, poor warranty, poor hardware, usually SATA drives which only belong in desktops.

I think I see what confused you...when I said "300 range"..that means MODEL range...not dollars. Clearly you cannot get a "server" in the 300 dollar range. Servers, when properly spec'd out, usually start well over 3,000 dollars...not 300. When I said in the "100 range"..that meant those poor PowerEdge T110 models....not 100 dollar range.

 

[marcink99]

When you said "real server" I thought that you were under impression that I was building one my self with desktop parts instead of geting one prebuild.

So t310 is not a real server in your eyes with quad core and 16gb?

I would greatly appreciate if you could help me with bellow questions.

What would I need to set up esxi server. Should I get some sort of external storage so that when something happens I could connect another computer to the storage and lunch it as a server?

My understanding is that if for some reason server breaks I should be able to lunch one of the workstation as a server. How would I get to the data if I was not using external storage? What would be your proposed solution?

What server specs would you recommend for 2011 sbs for 30 employees. I do not expect more than 12 connections at any given time. 6 people would be using quickbooks at the same time the rest email/internet

Storage wise company does not need more than 500gb will go with 1tb.

 

[YeOldeStonecat]

When you said "real server" I thought that you were under impression that I was building one my self with desktop parts instead of geting one prebuild.

So t310 is not a real server in your eyes with quad core and 16gb?

I knew exactly what you meant when you said T110 and T310...I do lots of Dell servers. And IMO the T310 is a real server. The T110 is ...too entry level, too desktop computer grade...IMO...yes not a real server. I prefer the T410 due to more RAID options...but the 310 is still nice, 3 year warrant by default.

SBS puts a good load on the hard drives...you don't want an entry level server trying to run SBS...even if for an office of just 8 or so. SBS needs high performance disks, on separate volumes, and SBS needs lots of memory.

I usually do a pair of 80 in RAID 1 for the OS..and a pair of larger drives in RAID 1 for DATA...or better yet...3 or more in RAID 5..or even more..in RAID 10. I do the installation to have the exchange infostore, and users shared folders, WSUS, and Sharepoint..and Company Data shares on that second volume. Pagefile on both volumes, system managed. This greatly increases performance of SBS.

Quickbooks itself is not a ball of fire, for good Quickbooks performance on a network....you want some good disk speed on your server...plus RAM on the workstations. .NET Frame on the workstations eats RAM like crazy.

I've seen all too many times...SBS on a SATA powered server....and complaints of slowness. The money saved up front is quickly wasted by reduced production, and longer time spent by the consultant doing things..thus higher bills by the consultant.

Antivirus exclusions need proper adjustment for good Quickbooks performance too.

 

[marcink99]

I would greatly appreciate if you could help me with bellow questions.

What would I need to set up esxi server. Should I get some sort of external storage so that when something happens I could connect another computer to the storage and lunch it as a server?

My understanding is that if for some reason server breaks I should be able to lunch one of the workstation as a server. How would I get to the data if I was not using external storage? What would be your proposed solution?

 

[YeOldeStonecat]

ESXi server...pretty much same hardware. Except organize the disks in a way to best serve any other guests. If this will only be for the 1 guest...I'd set it up the same as far as RAIDs. If it will be for several guests....I'd consider those in setting up the LUNs and presenting the volumes to the guests through ESXi.

VMWare guests just run as .VMDK files....you can move them around.

If you're not comfortable or versed in VMWare yet...I'd hesitate on jumping into using it for a client with a production server...spend some time using it on your own first.