Re: Install 3 times (triple crown)
- From: PWT24 <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 19 Mar 2007 12:05:08 -0700
Thanks Phil but I would prefer not to take that approach at this time. This
server needs to go out in about 2 weeks and I don't have time to learn VS and
R2 let alone understand everything you just stated. :) I appreciate the
instructions though. I will save them for another time. Bottom line, are you
saying I can't do the complete install without affecting my current
production server.
My thoughts were to run through the installation exercise with the customers
server before deploying at their site. So yes I have another server aside
from mine. (The customers)
As far as the software is concerned; I am an Action Pack subscriber so there
is no need to buy anything on ebay.
Open for other ideas!
"Phil E." wrote:
Do you have a spare machine around with enough memory and processor speed to.
install a base OS and Virtual Server on top? If you do, the following
assumes a little bit of experience with VS 2K5 R2 as that is what we run our
virtual environments on.
You could run your install; install some XP desktops, Vista desktops, and
another server or servers if you like.
You could run the entire project virtually, start to finish, without
impacting your production environment. If need be, all operating systems can
be Eval versions so as to not impact licensing issues.
Running things virtually requires nothing special. To get RWW on the virtual
SBS domain do the following:
Virtual SBS: Create an internal network accessible only by the workstations
and SBS NIC 1. Add a second NIC to the virtual SBS box that is attached to
the machine's physical NIC so it can pull an IP from your internal DHCP
server.
On your internal DHCP server, create a reservation for the MAC address of
the virtual SBS NIC 2.
On your internal DNS server, add an (A) record to the IP address reserved
above: virtualsbs.mydomain.local = IP 192.168.xxx.xxx
Run the SBS setup on your virtual server, complete stage 1, post stage 1
install and configure the base installation as you normally would and then
continue on with stage 2 for the complete SBS install.
Internet Wizard URL: same as your internal DNS (A) record:
virtualsbs.mydomain.local
You will be able to send e-mail from the virtual domain, only SMTP e-mail
coming in will not happen if you already have an SBS server, or Exchange
server on your internal network. POP3 Connector solution could be
implemented here if you want full e-mail functionality on the virtual
domain. RWW will be accessible via your Web browser internally.
Install the workstation OSs. This can be done at the same time as the SBS
installs.
Once you have the SBS install and ToDo list finished, you can go ahead and
create some virtual users and computers and then run through the Add
Computer wizard for the XP and/or Vista workstations.
The above will give you a complete install, start to finish. Mess up? No
worries, start again. You will be able to run Eval versions for about 6
months give or take from the install date. This is more than enough time to
play with the virtual SBS environment to get comfortable with the look and
feel of installing SBS.
You can get SBS 2K3 Premium SP1 on eBay without a problem, and SBS 2K3
Premium R2 by purchasing the R2 Eval pack which is little more than
shipping. XP Pro can be had via eBay, as can Office, and others.
This setup also gives you the opportunity to explore Group Policy settings
without creating havoc on a production SBS environment. Need to figure out
how to install software to certain machines via GP? Then this is the place
to do it! Office 2003, 2007, Windows Defender for XP, and more can be
distributed via GP (OLP versions for Office).
Let me know if I missed anything!
Philip E.
"PWT24" <PWT24@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3E4CB3DE-399D-4177-93F6-DB2B9F8616E8@xxxxxxxxxxxxxxxx
I have read some interesting posts regarding how newbies should install SBS
3
times before deployment and I have a question that has always concerned
me.
With my home based business, like many, I have an SBS Network on a dynamic
address. I am about to build a new server for a customer and have never
completed 3 installs before deployment but intend to this time. (Past
experience; built 4 SBS servers with one installation and launched, which
are
in production now, different locations obviously. Thankfully they all
have
been running well for about 2 years)
My question is; how far can you go with the installation? There is a
point
when the server starts needing domain names and IP addresses. How will
that
affect what is running in my office now? Should I just not complete the
setup? I would really like to go completely through the setup and test
the
server with workstations and then reload but I am unsure of the impact it
will have since it will need the same IP address (I think?). Do I need to
have a seperate address, maybe another ISP account?
I learned not to completely install and then deliver to the customers site
from my last deployment. As I had nothing but IP problems for about 2
weeks
until I had an ex-microsoft employee walk me through correction. However
I
would like to install twice and test then the 3rd time install but not go
through the connection portion until I am on site.
Thanks in advance for any help you can provide.
- Follow-Ups:
- Re: Install 3 times (triple crown)
- From: Phil E.
- Re: Install 3 times (triple crown)
- References:
- Re: Install 3 times (triple crown)
- From: Phil E.
- Re: Install 3 times (triple crown)
- Prev by Date: LaunchNTBackup failed. (0x8007007a)
- Next by Date: Re: Is it possible to have server on DSL and network on Cable?
- Previous by thread: Re: Install 3 times (triple crown)
- Next by thread: Re: Install 3 times (triple crown)
- Index(es):
Relevant Pages
|
Loading
