Re: ISP scenario for AD and DNS



Read inline please.

In news:O$m3mF1uHHA.3356@xxxxxxxxxxxxxxxxxxxx,
Mike Sharp <rdcpro@xxxxxxxxxxx> typed:
Hi Kevin,

Thanks for your response...I'll have to digest all this a bit (I'm a
programmer more than a network engineer), but to answer your first
question, WSS needs a domain account to connect with a non-local SQL
Server. With WSS on the W2k3 web edition, licensing requires a
non-local SQL Server, so it has to be a member of a domain. Besides,
while using W2k3 Standard edition as the web front end and a local
SQL server would be easy to set up, it won't scale as well. The
other architecture allows me to scale to around 4-5 WFE per SQL
Server.

SQL doesn't require you to use domain accounts, it can use its own accounts
or Windows local machine accounts.

The issue with using a Web server being a member of a domain is when web
users have access to domain account it gives them a higher level of
Privileges because a domain account can be used to access and member of the
domain. Local accounts work only on the local machine and SQL accounts have
work within a specific application.


While Exchange is a future plan, I'm not thinking about it too much
about it as yet.

Exchange does require Active Directory, but if your thinking of Exchange
2007, it is a giant leap forward in technology with about ten years
backwards in ease of management. Just about all management on Exchange 2007
uses the new command shell with very long command lines.



--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps

===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


.



Relevant Pages

  • Re: Memory Issues
    ... Exchange and SQL Server. ... you identified memory problems and large amounts of paging. ...
    (microsoft.public.sqlserver.setup)
  • Re: Memory Issues
    ... Even MS recommends to run Exchange and SQL on different machines, ... small and there is always free RAM memory. ... Per Denny Cherry you are suggesting to limit SQL Server to under 1GB. ...
    (microsoft.public.sqlserver.setup)
  • Re: Seeking Suggestions for upgrading SBS 2003 to W2K3 Std + SQL &
    ... from 1 - 2 GB) with most of the resources going to the exchange store and SQL. ... However if any other aspect of the server ... After reading some of the posts I believe I can get a transition pack ...
    (microsoft.public.windows.server.sbs)
  • Re: Spliting applications from a SBS 2000 server
    ... would be to move the WHOLE LOT (SBS) to a new box. ... How do I move my server to new hardware ... I am going to purchase either Exchange or SQL seperately and stop ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: Upgrade / Transition to Full Product
    ... BTW, you already have _full_ products of both Exchange and SQL, what is the ... On the second server will I need a licensed seperate copy of Windows 2003 ... Then using the old SBS 2003 CDs and Transition pack how will I ...
    (microsoft.public.windows.server.sbs)