Prev: TEST -please ignore
Next: OWA and Documents
From: Jarryd on 5 May 2010 05:44
Hi all,

I know that with SBS 2008 Premium you would normally use the second Win Srv
2008 SE licence to install SQL 2008 SE on. I remember hearing years ago
that it is not recommended that SQL and Exchange be installed on the same
Windows instance (i.e. one Windows Server OS running both Exch and SQL).
Have things moved on? Is this not so much of an issue with Exch 2007 and
SQL 2008, and therefore it is not such a bad move to stick both SQL and Exch
on the SBS server?

The reason I ask is that I have bought the Backup Exec 2010 SBS bundle.
Really good value. However, you have to install all the agents on the one
machine. They still support this separate SQL box setup. To achieve this
you would install the BE Remote Agent (included in the bundle) on the
Premium server running SQL. This allows the SBS server running the BE SQL
agent to communicate with the MS SQL instance via the BE Remote Agent on the
Premium server.

Aha, but here is my snag. I want to set my SBS 2008 domain up in a virtual
environment running Hyper-V. The licencing for the Hyper-V Agent requires
that an SQL agent is needed for each application on each VM. And seeing as
it forces the SQL Agent to be installed on the same instance of Windows
server as the Exchange Agent... (Remote Agents don't help here, BTW)

So, it would seem to me that the only way to make use of this bundle would
be to install SQL on the SBS box.

TIA,

Jarryd

From: Joe on 5 May 2010 10:54
On 05/05/10 10:44, Jarryd wrote:
> Hi all,
>
> I know that with SBS 2008 Premium you would normally use the second Win
> Srv 2008 SE licence to install SQL 2008 SE on. I remember hearing years
> ago that it is not recommended that SQL and Exchange be installed on the
> same Windows instance (i.e. one Windows Server OS running both Exch and
> SQL). Have things moved on? Is this not so much of an issue with Exch
> 2007 and SQL 2008, and therefore it is not such a bad move to stick both
> SQL and Exch on the SBS server?
>
> The reason I ask is that I have bought the Backup Exec 2010 SBS bundle.
> Really good value. However, you have to install all the agents on the
> one machine. They still support this separate SQL box setup. To achieve
> this you would install the BE Remote Agent (included in the bundle) on
> the Premium server running SQL. This allows the SBS server running the
> BE SQL agent to communicate with the MS SQL instance via the BE Remote
> Agent on the Premium server.
>
> Aha, but here is my snag. I want to set my SBS 2008 domain up in a
> virtual environment running Hyper-V. The licencing for the Hyper-V Agent
> requires that an SQL agent is needed for each application on each VM.
> And seeing as it forces the SQL Agent to be installed on the same
> instance of Windows server as the Exchange Agent... (Remote Agents don't
> help here, BTW)
>
> So, it would seem to me that the only way to make use of this bundle
> would be to install SQL on the SBS box.
>

I think it was only ever a matter of resources, both Exchange and SQL
Server being of the heavyweight persuasion. I've put SQL Express 2005 on
SBS2003 without any issues other than performance.

Be prepared to buy more RAM...

--
Joe
From: Jarryd on 5 May 2010 12:55
Hi Joe,

Thanks for your reply. I am running into other problems here now though but
at least this SQL + Exch option isn't going to be an issue.

I have already posted a thread about this, but do you know if there is any
way to get the Exch 2007 mgmt tools (64 bit) off the SBS media? I need to
install the tools (only) on my backup server or half the features don't
work. Any ideas?

TIA,

Jarryd

"Joe" <joe(a)jretrading.com> wrote in message
news:OVRQpLG7KHA.5708(a)TK2MSFTNGP02.phx.gbl...
> On 05/05/10 10:44, Jarryd wrote:
>> Hi all,
>>
>> I know that with SBS 2008 Premium you would normally use the second Win
>> Srv 2008 SE licence to install SQL 2008 SE on. I remember hearing years
>> ago that it is not recommended that SQL and Exchange be installed on the
>> same Windows instance (i.e. one Windows Server OS running both Exch and
>> SQL). Have things moved on? Is this not so much of an issue with Exch
>> 2007 and SQL 2008, and therefore it is not such a bad move to stick both
>> SQL and Exch on the SBS server?
>>
>> The reason I ask is that I have bought the Backup Exec 2010 SBS bundle.
>> Really good value. However, you have to install all the agents on the
>> one machine. They still support this separate SQL box setup. To achieve
>> this you would install the BE Remote Agent (included in the bundle) on
>> the Premium server running SQL. This allows the SBS server running the
>> BE SQL agent to communicate with the MS SQL instance via the BE Remote
>> Agent on the Premium server.
>>
>> Aha, but here is my snag. I want to set my SBS 2008 domain up in a
>> virtual environment running Hyper-V. The licencing for the Hyper-V Agent
>> requires that an SQL agent is needed for each application on each VM.
>> And seeing as it forces the SQL Agent to be installed on the same
>> instance of Windows server as the Exchange Agent... (Remote Agents don't
>> help here, BTW)
>>
>> So, it would seem to me that the only way to make use of this bundle
>> would be to install SQL on the SBS box.
>>
>
> I think it was only ever a matter of resources, both Exchange and SQL
> Server being of the heavyweight persuasion. I've put SQL Express 2005 on
> SBS2003 without any issues other than performance.
>
> Be prepared to buy more RAM...
>
> --
> Joe

From: Joe on 5 May 2010 13:07
On 05/05/10 17:55, Jarryd wrote:
> Hi Joe,
>
> Thanks for your reply. I am running into other problems here now though
> but at least this SQL + Exch option isn't going to be an issue.
>
> I have already posted a thread about this, but do you know if there is
> any way to get the Exch 2007 mgmt tools (64 bit) off the SBS media? I
> need to install the tools (only) on my backup server or half the
> features don't work. Any ideas?
>

Sorry, I did reply to the other thread, but I installed the 32-bit tools
on a Vista workstation. As I said then, I have been led to believe that
part of a 32-bit Outlook installation was necessary for mailbox import,
which was the only function I needed then:

http://technet.microsoft.com/en-us/library/bb691363%28EXCHG.80%29.aspx

# To import data from a .pst file, you must use the 32-bit version of
the Exchange management tools. You cannot run the 32-bit version of the
Exchange management tools on a server that is running Exchange 2007
because it is a 64-bit computer. You must run the Import-Mailbox cmdlet
from a 32-bit computer that has the following installed:

* The 32-bit version of the Exchange management tools
* Microsoft Office Outlook 2007 or Outlook 2003 Service Pack 2 (SP2)

--
Joe


 | 
Pages: 1
Prev: TEST -please ignore
Next: OWA and Documents