Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- From: lpolling <lpolling.2psfzl@xxxxxxxxxxxxx>
- Date: Sun, 29 Apr 2007 11:47:42 +0530
I'm having a similar problem. I'm also using 884453 as a guide. Mine
involves HP setup disks. I thought it was very strange that i would
get not only the 4 install cd's and the 3 supplemental cds for SBS 2003
r2 from MS, but also a HP startup disk and an additional MS SBS disk
2...? i thought that was very strange. I originally tried the MS
disks first, but could not get disk1 to boot. Thats what lead me to
the try the HP disk, that would boot and start the install. And thats
where all my trouble started...
existing infrastructure overview
DN: torrance.main
DC: server1.torrance.main W2K server sp4 upgraded from NT4, DHCP, DNS,
AD
File server: Adelphia.torrance.main W2k server sp4 also upgraded from
NT4
Decision behind SBS choice
First off i would like to say that I was employed by this company
because the network became to complicated for the Civil drafter that
was taking care of it for the last 6 years. The company grew too large
for his capacity. i started 3 weeks ago, i rewired the whole network to
start ( too many hubs)
Small company, 45 network devices, File server is a IBM netfinity 5500
manufactured in 98 dual pentium 3 500s that was bought from an auction
site. the only manuals and software is in SWEDISH. DC is running on a
HP pavilion desktop from about 2000.... say no more, any way back to
the point
Now for the Problems
Install the OS and name the server Mercury
Restarted stopped the SBS component setup.
Ran Adprep on DC and Dcpromo on the SBS box, every thing completed no
errors
SBS restarted, I started the SBS setup again just to check for errors
and this is what i got
1. Admin account must be a member of Schema, Enterprise and Domain
admins groups. I checked the AD on both the DC and SBS box and it all
checked out.
2. Netbios name contains invalid characters. I racked my brain on
this one. I finally decided SBS didn't like the length of
mercury.torrance since its over 15 characters. I reinstalled again and
named it BETA. Same problem.
3. SBS must be the primary DC. I expected that one because i haven't
finished the 884453 article, i was just checking for errors with the
SBS setup.
I really don't know what could be wrong with the install, But its
sounding like maybe the HP disk has something to do with it maybe. I
don't know I'm grabbing at straws here. I could get the MS disk 1 to
boot, so maybe i will throw it in when the server is up and let it
reboot itself into the install. I'm about -->| |<--- that close to
just doing a migration or rebuilding the whole network from the ground
up. Ideally i would like to add it to the domain and take away the
roles of the other servers gradually because production time is at
utmost importance... Any one have any ideas???? much appreciated!
--
lpolling
------------------------------------------------------------------------
lpolling's Profile: http://forums.techarena.in/member.php?userid=25147
View this thread: http://forums.techarena.in/showthread.php?t=735097
http://forums.techarena.in
.
- Follow-Ups:
- References:
- How to install SBS 2003 in existing AD domain (one Win2K DC)
- From: ffroehn
- Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- From: Dave Nickason [SBS MVP]
- Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- From: kj
- Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- From: SuperGumby [SBS MVP]
- Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- From: kj
- How to install SBS 2003 in existing AD domain (one Win2K DC)
- Prev by Date: Re: sql server 2005
- Next by Date: Re: SBS server upgrade problems - BSODs
- Previous by thread: Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- Next by thread: Re: How to install SBS 2003 in existing AD domain (one Win2K DC)
- Index(es):
Relevant Pages
|