Re: Installation of a test server - licensing requirements
- From: Graysailor <Graysailor@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Oct 2007 08:30:03 -0700
Thanks for the advice. I will check these resources out, I already use them a
lot. I guess what I really wanted to know was what is the licensing
requirements of creating a test system, one that will not be used for
production but only to test new technologies and modifications to the ISA
Firewall or Exchange, etc. I have a spare Server so I don't need to go
virtual (and don't want to put ANYTHING on my production system that could
impact response or the system itself). Is it allowable to do an install of
SBS on a system that will not be used as a production system? I wouldn't be
installing the CAL's (except the one's included with the base install), but
since you have to register SBS to keep it operational (plus I'll have the
same issues with the Symantec and probably a few other infrastructure type
softwares that I'll have to install in order to test it).
It would seem like this a basic part of an SBS installation and should be
addressed in the core documentation becuase nearly every Tech article begins
by saying "please test this on a non-production system, yada yada yada". OK -
if this is the case then why isn't a test system set up part of the core
package? I have the SBS 2003 R2 Administrators Companion by Russel, et al and
I can find no mention of an 'off line' testing platform. Having been in
banking and now in the medical field, we don't do anything to a production
system without testing it on another system first but I've not found a cost
effective way for a small business to do that. I have used virtual systems
and I assume that the software you mentioned can reproduce a production
server setup and do this - so that would be a solution. I will check into
this. I was hoping I could just install SBS R2 onto the test server, hook up
a spare workstation and test away. What about a developer? If I wanted to set
up an SBS R2 server at the house so I could learn on it instead of using my
clients production boxes - how would I accomplish this? Is there an avenue
for that? Thanks again - I appreciate how quickly you guys respond and also
the wealth of information available to the Microsoft community through the
knowledgebase and these forums - great tools - in fact searching the
community is my first tool now when solving problems!
"Lanwench [MVP - Exchange]" wrote:
Graysailor <Graysailor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:.
I'm tired of blowing up my Production box. I have an old server we
just replaced with the new server. Can I load SBSR2 on it and use it
as a test box? Won't it eventually 'time out' and die because it's
unregistered? What if I need to hook it to the internet for upgrading
and test (it's this crazy ISA and different security protocols that
have me scratching my head). How can I have a functioning long term
test box?
I agree with Jason's advice - and will also add that for testing, you should
look into VMWare or Virtual PC for this purpose. Then it won't matter when
you've completely hosed your test install. Another option would be Acronis
TrueImage server ...so you can blow away your botched setup & go back to the
one that works.
- Follow-Ups:
- Re: Installation of a test server - licensing requirements
- From: Lanwench [MVP - Exchange]
- Re: Installation of a test server - licensing requirements
- References:
- Installation of a test server - licensing requirements
- From: Graysailor
- Re: Installation of a test server - licensing requirements
- From: Lanwench [MVP - Exchange]
- Installation of a test server - licensing requirements
- Prev by Date: Re: VPN Wizard Fails
- Next by Date: Re: Adding new hard drive(s) to improve exchange performance
- Previous by thread: Re: Installation of a test server - licensing requirements
- Next by thread: Re: Installation of a test server - licensing requirements
- Index(es):
Relevant Pages
|
