Re: Test Virtual Server with SBS 2003

Thanks to you both,

Dave



"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23aaGPyzgGHA.3456@xxxxxxxxxxxxxxxxxxxxxxx
Didn't we just answer this?

The one caveat that the OP needs to remember is that he can't have the
test SBS running on the same network segment as his real SBS. It must be
on its own network segment. His LAN NIC for the test SBS should probably
be local to the Virtual Server box only, and not part of his overall
network.


--
Charlie.
http://msmvps.com/xperts64


Cris Hanna [SBS-MVP] wrote:
"DW" <dw@xxxxxx> wrote in message
news:%23BVLyAzgGHA.1520@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

What is the best practice for creating a test Virtual Server with SBS
2003. This would be purely for test and evaluation purposes only.

I already have SBS as part of the Action Pack running as my main
production server.

Do I ideally build another box with Win 2003 Server on it, install VS
then SBS?

Or install VS on my XP SP2 desktop machine (2gb ram) and put SBS on it.

What are the security risks (IIS on the XP machine)etc and where do I
get
another copy of SBS 2003 for testing purposes? A 180 day trial perhaps?

The Action Pack has Release Candidate SBS 2003 and OEM for install with
the Pre-Install kit only. Would the Release Candidate version be
licensed
as the EULA of Action Pack gives one SBS Server license?

On that note, what happens when the Action Pack updates come with newer
versions of software? For example, I have about three versions of XP.
Does that mean that the latest one with the update is the only licensed
one and I have to get rid of the older surplus copies? (As there is a
license for 10 installs of XP?) Getting myself confused now :-)

Thanks



Dave Whyte

101 Digital Services

Edinburgh UK



You could install VS R2 on an xp box or another Win2k3 box...really
doesn't matter

The IIS running as part of the SBS on VS doesn't really impact your XP
per
se. Obviously if you are going to expose the SBS part to the world then
best practices for security are a must.

180 day trial is probably your best bet




.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... slip stream SBS you would have had it ages ago. ... How did they buy this Server? ... My main reason for slipstreaming the install is because I cannot get the ...
    (microsoft.public.windows.server.sbs)
Loading