Re: The SBS 2003 Network Configuration Wizard InOp



I don't know that you are but... You're not confusing wizards perchance?

The SBS itself must be installed using the full wizard process.

MS however support introduction of SBS into an existing AD. ie. a situation
where the workstations _could not_ have been connected using SBS' process.

I would however like to get to the bottom of your problem. You suggest that
many machines were installed using /connectcomputer and only two proved
problematic. Simly, I'm interested. Answer my question and I'll ask another,
or possibly comment.

"PCNS" <PCNS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9C315FC5-B3BB-4A0D-A5A6-04DCD01583CB@xxxxxxxxxxxxxxxx
Jim Behning -

Thank you for the response. Microsoft has stated several times in this
forum, along with several webinars that I have attended, along with
several
workshops that I have attended, that manually joining a SBS 2003 domain is
not supported. They, Microsoft, have explicitly stated, at these webinars
and
workshops that you must use the wizards to guarantee that all the hooks
are
installed. I have had two Microsoft support people at two different
workshops
tell me that if I did not use the wizards, and then called Microsoft for
support, that they would insist that I go back and re-do the entire
installation using the wizard(s) because bypassing the wizard(s) is not
supported. I can not risk an installation for a customer that is not
supported by Microsoft, just in case something happens.

What everyone here, in this forum, keeps missing is an ANSWER TO THE
PROBLEM!

Instead of work-arounds, or, short-cuts, how about an ANSWER!

1 - Microsoft, what is the answer to the SBS 2003 Network Connection
Wizard,
failing?

2 - Microsoft, to fix the SBS 2003 Network Connection Wizard failure, does
that require me to wipe the machine out and re-install the XP to get the
Network Connection Wizard to work correclty (like I had to on the one
computer)?

3 - Microsoft, is the MANUAL way of joining a computer to the SBS 2003
domain supported or not?...and if so, POST IT.

What I (and others here with the same problem) need is a supported answer
to
this problem.

Thanks for your input.
--
PCNS Support Team


"Jim Behning SBS MVP" wrote:

You can manually join the domain any time you want. Who says it is not
supported? It is more convenient to add with the wizard but sometimes
the wizard does not work. Make sure your NLA service is set to
automatic and reboot. NLA set to manual is know to cause issues.
Almost guaranteed to cause issues with Dells. Been there recently and
suffered greatly until Dave N. reminded me of the NLA service.

I do not see the ipconfig/all from the server? I guess I have tired
eyes and I need to go to bed.

On Fri, 2 Mar 2007 19:08:56 -0800, PCNS
<PCNS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

SuperGumby -

Wanted to thank you for your reply. Here is the IPCONFIG /ALL that I ran
on
the computer that was having the problem. This was done a few weeks ago,
so
the lease time will be wrong now, but other than that, all else is the
same.
Also, I did try static IP address on this machine and stil it did not
work.

Here is my internal IP settings on one of the machines ;

Windows IP Configuration


Host Name . . . . . . . . . . . . : 300-WPA

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : wpa.local



Ethernet adapter Local Area Connection:


Connection-specific DNS Suffix . : wpa.local

Description . . . . . . . . . . . : Intel(R) PRO/1000 CT
NetworkConnection

Physical Address. . . . . . . . . : 00-11-11-9F-0E-F5

Dhcp Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.118

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.0.1

DHCP Server . . . . . . . . . . . : 192.168.0.89
DNS Servers . . . . . . . . . . . : 192.168.0.89
Primary WINS Server . . . . . . . : 192.168.0.89

Lease Obtained. . . . . . . . . . : Sunday, January 28, 20074:38:19PM

Lease Expires . . . . . . . . . . : Monday, February 05, 2007 4:38:19 PM



.



Relevant Pages

  • Re: Modem settings in Remote Access wizard will not stick
    ... I had tested this wizard on several SBS 2003 servers on my side. ... another problem computer (a problem computer without used my steps in the ... Microsoft Online Partner Support ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and HP/Compaq Proliant ML370 dual-processor problem
    ... Thanks for using SBS newsgroup. ... For SBS 2003 installation, two physical processors are supported and each ... Select SERVER and set PROCESSOR RETEST to YES. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Re: ADP PC/Payroll database
    ... They don't support it because it doesn't fit the installation script they've ... I've had success with numerous SQL flavours on SBS, ... and ADP supports the installation on ... If ADP won't support this, don't do it, plain and simple. ...
    (microsoft.public.windows.server.sbs)
  • Re: Errors during SBS 2003 SP1 Installation
    ... The SBS installation wizard allows the program ... Please understand that in SBS 2K3, we do not support separate Program ... - partition for OS. ...
    (microsoft.public.windows.server.sbs)
  • Re: ConnectComputer not correctly setting up ClientApps on workstations
    ... The problem was If a user is added to a SBS Domain (Using the Add User ... SBS Domain (Using the Set Up Computer Wizard) then the User will not ... the connectcomputer wizard only make the client ... installation manually by double-clicking the shortcut. ...
    (microsoft.public.windows.server.sbs)

Loading