Re: Why setup two servers with same name

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.


On Feb 3, 7:00 pm, "Jeff Teel" <jdt...@xxxxxxxxxxxxxxxxxxx/com> wrote:
If the consultant that configured/installed SBS 2003 on the new server
didn't complete the install.........which makes it a domain controller
.............it won't run long (if I recall I've heard maybe a week) until
it begins to shut down (turns off). I've not experienced it first hand
since I complete the installs when I do them,

Jeff

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

news:1170545517.765520.92040@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



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

We did not setup the following and are trying to resolve some issues.

One of my clients has a SBS 4.5a server (192.168.1.106) and a new SBS
2003 (192.168.1.101) server.
Since they have some XP Home workstations, a domain has not been
created.

You have to run a domain / AD to run SBS 2003. The server will begin
shutting down on you. Just upgrade the workstations to XP Pro or get rid
of
them. Home means....well, home.

On a XP PRO computer, the new server *does not* appear in the
Microsoft Windows Network but other workstations and the old server do
appear.
The only way that I can map a drive to the new server is to right
click on 'My Network Places', click on 'Search for Computers' and then
search for 192.168.1.101.
Is this normal?

No, but so far, your setup is not normal - so I doubt you have WINS in
place, or properly configured DNS.

The mapping that I need to do is for a SQL application. I have been
reading that SQL 2000 (which we must use) can have issues under
certain circumstances when mapping to an IP address (as opposed to a
server name). This is one of my concerns.

The other concern that I have is that generally the individual who
installed and configured the new server is incompetent and somewhat
dishonest. I am wondering if he is somehow circumventing licensing
regulations.

Can't speak to that, but
a) how many licenses do you have compared to your users/devices?
b) if he set up SBS 2003 as anything other than a DC, the incompetent
part
definitely stands. Where'd you find him?

You may need to scrap your current build and start over. If you aren't
confident in your own skills with regard to this. find good consultant,
the
kind who can give you references. Word of mouth referrals are an
excellent
way to go.

Thank you in advance.- Hide quoted text -

- Show quoted text -
We provided a quotation to sell, install and configure the new server
as well as moving our accounting application over to the new server.
We won the bid to move the accounting app but another vendor obtained
the order for server portion .

The client ordered 15 CALS. We noticed a message in event viewer
something to the effect that 'you are about to exceed your licenses'.
We checked licensing in admin tools and the display said 5 licenses
installed and 8 maximum used. This did not make a lot of sense to me
as I would have thought that the purpose was to prevent too many
logins.
I checked all the paperwork that the other vendor left and could not
find additional physical certificates.
I have advised the client yesterday and he will contacting the other
vendor on Monday.

Can you please expand on 'The server will begin shutting down on
you.'?

TIA.- Hide quoted text -

- Show quoted text -


.

Relevant Pages

  • Re: SBS2008 install from my MS Action Pack
    ... match Standard and Premium CALs depending on if the users will need access to ... SQL servers on the domain or not... ... is all is needed to access any SQL server on the domain... ... Server license and a License for SQL, which is included in the AP, ...
    (microsoft.public.windows.server.sbs)
  • Re: Standard v Premium ?
    ... Price-wise, I believe Premium is cheaper than Standard + ISA, so not using ... SQL isn't a factor. ... But IMO one of the best deals, if you've got customers ... >> us the new version of ISA Server I believe. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 test question explanation needed please
    ... You need SQL so ... Premium is required so B is correct Only one SBS is allowed so the other SBS ... server, can you install the SQL server that comes with SBS 2003 premium ...
    (microsoft.public.windows.server.sbs)
  • Re: upgrade question
    ... Sure, you can upgrade from standard to premium, technically it's quite simple: just run the SQL and/or ISA setup from the premium installation CD. ... You have SBS 2k3 Standard SP1, so your path would be one of these: ... The transition pack doesn't really factor in here, unless you want to install any or all of Exchange, SQL, or ISA on server(s) other than your SBS server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Why setup two servers with same name
    ... I would also confirm exactly what the vendor selling/installing the server ... did he purchase SBS 2003 premium but didn't know that he had to install SQL ...
    (microsoft.public.windows.server.sbs)