Sage 200 with SBS 2011 Premium Add-on

Liquidfox

Liquidfox

Liquidfox

Soldato
Joined
26 Sep 2007
Posts
4,141
Location
Newcastle
Morning guys,

We're trying to quote on a server install, and have realised that the competitor has provided a solution that physically cannot work:
Physical Server: HL ML350 G6 (Dual Xeon E5520 @ 2.26GHz, 16GB, 4x 146GB, 4x 300GB) running Server 2008 R2 with Hyper-V running as DC, File & Print, Exchange 2010.
Virtual Server: Server 2008 R2 running SQL 2008.

From what i've seen:
Exchange needs to be spread over at least 2 servers (Hub+CAS, then Edge on a separate server). So you think fine, put one of the roles on the virtual server. Except the below states you can't:

http://technet.microsoft.com/en-us/library/aa996719.aspx said:
Only management software (for example, antivirus software, backup software, or virtual machine management software) can be deployed on the physical root machine. No other server-based applications (for example, Exchange, SQL Server, Active Directory, or SAP) should be installed on the root machine. The root machine should be dedicated to running guest virtual machines.
Click to expand...

So we were planning on the following:

Host: SBS 2011 Std
Virtual: SBS 2011 Premium Add-On (ie Server 2008 R2 + SQL 2008)

So my question is this, is Sage 200 supported on our proposed solution?

I phoned Sage, but they got stuck up on the fact i mentioned SBS 2011 which isn't supported (as you'd expect, as SQL needs to be on a separate machine).

Useful Facts:
Currently only have 11 users. Planning to expand slightly soon, but nowhere near the 75 user limit for SBS.
 
Last edited:
Surely the most important thing is to convince Sage that its supportable?

Doesnt really matter if we all chime in and say it will work if you fall at the first hurdle trying to get support from Sage.

Ring them back and tell them that you are installing on a virtualized SQL server and see if they will support that. I'm not surprised that they got nervous when you mentioned SBS, lots of vendors do so without any real justification. They just dont understand the product well and there has been a lot of hot air expended about it in the past.

I'm also pretty certain that Exchange 2010 will work on a single server. It might not be a text book MS approach, but in reality thats not unusual.
 
I'm sitting on hold to Sage now and going to go with your suggestion of mentioning a virtualised SQL server and leave SBS completely out of it :)

I've heard that Exchange can be combined onto 1 server, but if MS don't put it in a white paper, we're reluctant to do it in case we have to call up for support and have them laugh at us and tell us to GTFO.

UPDATE: Sage support the virtualised solution, so long as the host is one of their support OS's. SBS is supported, just not 2011, which leaves us with 2008.
 
Last edited:
To all intents and purposes though, the physical host will report as Server 2008 R2.

They will only know its SBS on top if someone tells them.
 
To be fair, it's not something we could risk as if we ever do need Sage Support, they may just come straight back at us and say SBS 2011 isn't supported even though as you say it reports itself as R2...
 
You should not run VM's on an SBS Server.

Host: Windows 2008 R2 with Hyper-V - Do not setup as a DC.
VM1: SBS 2011 Std - Exchange 2010 & Sage 200
VM2: Server 2008 R2 + SQL 2008

Install Sage onto the SBS2011 machine and connect it to the SQL Server on VM2.
 
I know this is a bit of a Necro, but going off your setup Marin, can the Host be added as a member server to SBS2011 on VM1?
 
No the Hyper-V host should not be added as a Member Server to SBS2011 on VM1.

It should be kept as a workgroup, I usually have a NIC per VM and a seperate one for the host, which I give a static IP on the same subnet as the SBS on VM1 so that I can communicate to Host & VM's if required.
 
Are there any side-affects if the host is added as a member server? We're trying to keep licensing costs to a minimum at the moment, so we may have to resort to ESXi as the host platform, otherwise we have to have 3 Server OS licenses, something the customer is probably not too happy about :(
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom