In reference to my last post about Small Business Server I have the solution and have found a few pitfalls that I think other people should be aware of.<br>
<br>
First of all we all know that Microsoft Operating systems don't play well with third party partitions during setup. It is best to start with a freshly formatted drive.<br>
<br>
Second during install you should accept whatever modem setup finds until the setup completes. Changing the driver to a third party driver can cause setup to freeze during DHCP installation.<br>
<br>
Finally setup boot disk #2 has a file called winnt.sif. This file tells setup how to perform. It apparently defaults to an unattended install which is fine assuming that setup finds the right drivers for your nic and other hardware. If setup does not find the right drivers you will receive a BSOD when setup starts the networking components. My work around was to edit the following section in the winnt.sif file:<br>
<br>
The original was:<br>
<br>
[Network]<br>
DetectAdapters=""<br>
InstallDC=*<br>
InstallProtocols=InstallProtocolsSection<br>
InstallServices=InstallServicesSection<br>
InstallInternetServer=InstallIISSection<br>
<br>
My edit was:<br>
<br>
[Network]<br>
Attended=Yes<br>
InstallDC=*<br>
InstallProtocols=InstallProtocolsSection<br>
InstallServices=InstallServicesSection<br>
InstallInternetServer=InstallIISSection<br>
<br>
<br>
After working around these 3 pitfalls the setup worked perfectly. I appreciate the help offered by my fellow tek tippers and I wanted to alert people to these situations so that others can hopefully avoid my misery.<br>
<br>
<br>
First of all we all know that Microsoft Operating systems don't play well with third party partitions during setup. It is best to start with a freshly formatted drive.<br>
<br>
Second during install you should accept whatever modem setup finds until the setup completes. Changing the driver to a third party driver can cause setup to freeze during DHCP installation.<br>
<br>
Finally setup boot disk #2 has a file called winnt.sif. This file tells setup how to perform. It apparently defaults to an unattended install which is fine assuming that setup finds the right drivers for your nic and other hardware. If setup does not find the right drivers you will receive a BSOD when setup starts the networking components. My work around was to edit the following section in the winnt.sif file:<br>
<br>
The original was:<br>
<br>
[Network]<br>
DetectAdapters=""<br>
InstallDC=*<br>
InstallProtocols=InstallProtocolsSection<br>
InstallServices=InstallServicesSection<br>
InstallInternetServer=InstallIISSection<br>
<br>
My edit was:<br>
<br>
[Network]<br>
Attended=Yes<br>
InstallDC=*<br>
InstallProtocols=InstallProtocolsSection<br>
InstallServices=InstallServicesSection<br>
InstallInternetServer=InstallIISSection<br>
<br>
<br>
After working around these 3 pitfalls the setup worked perfectly. I appreciate the help offered by my fellow tek tippers and I wanted to alert people to these situations so that others can hopefully avoid my misery.<br>
<br>