Re: Why setup two servers with same name

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have the admin password to both the old and new servers.
He has had so many CDs floating in and out of the client's site that I
do not know *exactly* how he moved to SQL 2000 Premium. I have seen
the first CD for SBS 2003 Standard and the first CD for SBS Premium.

Actually, I have another client with SBS 4.5a running some old DOS
based apps and a newer SBS2003 server which is the DNC. There is no
issue there.

The goal at *this* client is to end up with *one* server. His Excel,
Word and Quickbooks have been moved to the new server. Our accounting
app. still resides on old (SBS 4.5a) server. We are trying to migrate
the accounting app. but are having an issue when we run the app on the
server (as opposed to on a workstation). SQL can extract the data
quickly but the application stalls for about 5 seconds (with an
hourglass) every 5 records or so.

In regards to the Domain Name Controller... as mentioned earlier, at
least one workstation is using XP HOME. We had nothing to do with the
purchase of these w/s or either server. Anyway, with the old server,
the logins are verified at the workstations. The same is true of the
new server.

If I may, I would like to list my concerns:
1. The vendor is definitely dishonest and incompetent.
2. There is only 2 Gb of RAM.
3. Only 1 NIC in the server is being used.
4. I do not know *exactly* what he did to go from SBS 2003 Standard to
SQL 2005 Premium to SBS 2003 Premium. I am referring to uninstalls,
etc.
5. The other vendor is of the opinion that the client 'does not need'
many of the features of SBS such as Exchange, etc and that all they do
is 'take memory'. As a result, I do not know to what extent these
features were installed, configured, deactivated, etc.
6. The vendor says that he does this type of setup frequently and does
not have issues.
7. The vendor says that he is willing to do the SBS install again as
it only takes 2 hours.
8. Based upon 3 and 4 above I do not know if everything will run
smoothly 'today'. I do not know what the absolute *essential* building
blocks of SBS are and if there are installed, enabled and configured
properly. Also, what will happen in the future if the client wants to
start using Exchange, etc.
9. How do I convince the client that a fully installed/configured SBS
2003 Premium server is necessary.


On Feb 7, 7:34 am, "Jeff Teel" <jdt...@xxxxxxxxxxxxxxxxxxx/com> wrote:
In your last post there are points of your description of the situation that
you are dealing with that sound like the server OS installer is in the
process of migrating things from the old server to the new one (I've not
actually done this but only read about it) but later it sounds like the
setup is permanent/finished. If your client is wanting both SBS servers to
remain available for everyone to use it is my understanding that that cannot
happen since both servers want to be the "head honcho" as far as being the
domain controller. Both can't exist in the same subnet permanently if they
are both complete/full installs.

Am I assuming correctly that you don't have admin access to the new server?
If you do you should be able to tell what version of SBS the vendor
installed. But as you have said not being able to see the new server in
MyNetwork Places does not seem standard. An easy way to see which machine
is the domain controller is when you are doing your search for computers
would be to sect "Role" from the dropdown box and choose Domain Controller.
If the old server is the only one that is found then it is still the DC and
the new server install is not complete.

It does sound very messy to me and I would be asking many questions too if I
were in your place. A proper server OS install is your business too since
your application/applications need certain conditions to function correctly.
Your client could very well take all of the problems that could be down the
road as being your fault and not the OS vendor.

"allanc" <allan.for.g.gro...@xxxxxxxxx> wrote in message

news:1170726986.550261.45960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



I cannot say for certain. He has been bringing CDs in and out of the
company.
Forgetting about the fact that he has installed 3 different versions
of SQL for a moment, he insists that he installs SBS this way on an
ongoing basis.

I really do not understand why I cannot see the new server in MS
Windows Network and have to search for a computer using its IP
address.
I asked him about the server not being a DNC and he is evasive and
says that the server would have crashed many times if the install
wasn't complete.

My partner and I have a definite distrust of him and we are stuck
between the client and this vendor and the client feels stuck between
the vendor and us.

To be honest, one of my concerns is that I may be overreacting and
perhaps everything will run fine, my SQL accounting application will
OK, etc. At this point, I do not know what to think.

On Feb 5, 8:01 pm, "Jeff Teel" <jdt...@xxxxxxxxxxxxxxxxxxx/com> wrote:
Do you know if the vender installed SBS 2003 R2? If it was R2 then SQL
2005
Workgroup Edition is what comes with that release of SBS 2003. I don't
know
for sure how you would go about getting SQL 2000 that would be licensed
as
being part of SBS 2003 R2 Premium. Maybe someone here could shed more
light
on that.

"allanc" <allan.for.g.gro...@xxxxxxxxx> wrote in message

news:1170644648.752018.315340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I know he purchased SBS 2003 Standard initially.
A couple of weeks after that I noticed the first CD from SBS 2003
Premium.
He charged my client $800 (CDN) being the difference.
Over and above everything else we (the client and my company) also
think that there is a communcation problem due to primary language
difference.
My company also thinks that there is a competence issue and lack of
integrity.
I think that the client also agrees with the last two assessments but
I hesitate to ask them.
My opinion is that there are also some 'irregularaties' but I really
do not know if it is a good idea to post the observations.

On Feb 4, 5:55 pm, "Jeff Teel" <jdt...@xxxxxxxxxxxxxxxxxxx/com> wrote:
I would also confirm exactly what the vendor selling/installing the
server
OS purchased for this client. Did he purchase SBS 2003 standard and
then
purchase SQL 2005 as a separate application thus needing extra
licensing
or
did he purchase SBS 2003 premium but didn't know that he had to
install
SQL
from the Premium Technologies disk. It would seem the bill from this
vendor is edging upwards as time passes!

"allanc" <allan.for.g.gro...@xxxxxxxxx> wrote in message

news:1170618196.339944.232100@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

On Feb 3, 7:47 pm, "Lanwench [MVP - Exchange]"
<lanwe...@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Innews:1170548978.211088.197240@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
allanc <allan.for.g.gro...@xxxxxxxxx> typed:

To make matters worse:
I quoted on SBS 2003 Premium since we need SQL 2000 Premium with
the
GUI.
The other vendor quoted 'SBS 2003' on his offer.
When we went on-site to migrate our accounting app. we noticed
that
the SQL Enterprise Manager was missing. The consultant had
installed
SBS 2003 Standard
We spoke to client and other vendor and said specifically that we
needed SQL 2000 Premium.
The other vendor then installs SBS 2003 Premium with SQL 2005
Premium
(not 2000).
I do not know *exactly* what steps he followed.
We complain again and he finally installs SQL 2000 Premium on the
third try.
Again, I do not know exactly what he did.
I am worried that the server might also be 'confused' because the
consultant is not trusworthy and is being vague.

I strongly suggest you flatten & reinstall....and get all
workstations
on
W2k/WinXP Pro.

<snip>- Hide quoted text -

- Show quoted text -
I will suggest that to my client.
Thank you.- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -- Hide quoted text -

- Show quoted text -


.

Relevant Pages

  • RE: trouble installing companyweb
    ... gone ahead and patched the server before continuing with step 13 of KB884453. ... sbs components that I could, ... install any 3rd-party software before you finish the installation. ... For the failed intranet component ...
    (microsoft.public.windows.server.sbs)
  • RE: Monitoring and Reporting
    ... I understand that you unable to get SBS ... monitoring report after you install Windows server 2003 sp2. ... To successfully install SBS 2003 SP1, ... Downloading and Installing Windows Small Business Server 2003 Service Pack 1 ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 R2 - Please Help
    ... computers be slow after you install the full SBS 2003 R2 components. ... log on slow is probably refer to incorrect DNS ... as the DNS server on the clients rather than the ISP DNS servers. ...
    (microsoft.public.windows.server.sbs)
  • RE: Sharepoint Service, company web reinstallation
    ... Welcome to SBS newsgroup. ... I understand that you want to reinstall the companyweb on your SBS 2003 ... Business Server 2003 (If you are in the middle of RC to RTM upgrade, ... If AV software install any extra IIS virtual directory, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)