Re: Deployment - Active Directory and SQL Server

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Sorry, I should have specified. SQL probably does not have to be
reinstalled. I can't imagine it has any per user settings that need to be
copied. It comes down to this, any application that has per user settings
needs to be reinstalled.

You will want to check the resource usage of the server before installing
TS. If that server is heavily used, then adding TS may very well wreck
performance. as well, when you install TS it will require users being
logged off because it will minimally require a reboot. when you are
installing applications as well you do not want users logged into the box
even through SQL.

Jeff Pitsch
http://www.sbcgatekeeper.com
Your Terminal Services Security Website

"Giles Keen" <GilesKeen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ED5E635B-39E6-4BF0-98C0-F6EAF2CA2A5F@xxxxxxxxxxxxxxxx
> Thanks for your email.
>
> I am a little confused.
>
> The client only has 2 servers :
>
> SBS 2003 Server - Active Directory, Exchange, DNS
> W2K3 Server - SQL Server + A Few Apps
>
> I have read advice that Terminal Services should not be installed on a
> Domain Server and therefore I agree that the only option is to install TS
> on
> the W2K3 Server
> but I am very worried about having to reinstall SQL etc...
>
> I understand per your advice that it is a bad idea to load TS on the same
> server as SQL but I dont think I have any other option. Is it just the
> applications that would need to be reinstalled (which is no big deal) OR
> SQL
> Server would have to be completely uninstalled too ?
>
> The client is using SQL heavily i.e. 30 users logged in and if I have to
> uninstall and reinstall SQL then I will have to get all users logged out
> of
> SQL for however long which may require me to reschedule my visit until a
> more
> convenient time for the client to have all users sitting around doing
> nothing.
>
> Hope this makes sense. Sorry if I have repeated myself or not understood
> your reply correctly.
>
> Many Thanks in advnace for your time.
>
> Giles
>
>
>
> "Jeff Pitsch" wrote:
>
>> See inline
>> "Giles Keen" <GilesKeen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:88698450-416C-4141-AF7D-F27B7B0FB736@xxxxxxxxxxxxxxxx
>> > Hi
>> >
>> > I have a couple of silly questions which someone will probably answer
>> > easily........
>> >
>> > I am going out to a clients on Friday to install and setup Terminal
>> > Services
>> > on a Windows 2003 Server which has SQL Installed.
>> >
>> > The Server in question is NOT a domain controller and does not have
>> > Active
>> > Directory installed.
>> >
>> > The client has another server (SBS 2003) which has Active Directory,
>> > DNS,
>> > Exchange running on it.
>> >
>> > My questions are :
>> >
>> > 1) Can I install TS and the TS Licence Server on the Windows 2003
>> > Server
>> > which does not have Active Directory ? This is what I would like to
>> > do.
>>
>> yes that is the preferred way. Put TS on a member server.
>>
>> >
>> > 2) When I try to install TS on the Windows 2003 Server it warns me that
>> > there will be a problem with all programs already installed and they
>> > will
>> > not
>> > work correctly. Does this include SQL Server ? Will SQL Server stop
>> > working
>> > and have to be reinstalled ?
>>
>> Yes, you do NOT want to install TS on a SQL server. Both are resource
>> and
>> memory intensive applications. You will get a very very limited number
>> of
>> users (yes I know only four but I will guarantee you it will grow and
>> then
>> everyone will be unhappy) on the server and performance will suffer for
>> both. Really bad idea. You will also have to reinstall all applications
>> when you put TS on the server. The shadow key needs to be populated
>> properly.
>>
>> >
>> > There will only be 4 users (max) using the Terminal Server and
>> > therefore
>> > the
>> > demand will be very low. The Windows 2003 Server is dual processor and
>> > 4GB
>> > Memory.
>> >
>> > I have all the TS CALS Purchased and just want to have a successful
>> > install
>> > on Friday.
>> >
>> > Many Thanks for any advice
>> >
>> > Giles
>> >
>>
>>
>>


.

Relevant Pages

  • Re: WSUS Client not yet reported
    ... You tried to install R2 as a user that is not the built-in ... The monitoring component on SBS server was corrupted. ... Step 3: Reinstall SBS monitoring component: ...
    (microsoft.public.windows.server.sbs)
  • Re: Sharepoint re-install failure - FINAL RESULTS
    ... > between Sharepoint services and its SQL database. ... > I than selected to reinstall the intranet (not uninstall & install, ... > Also they both have a subdirectory called INSTALL. ... > MSSQL$SHAREPOINT directory and reinstalling Microsoft SQL Server Desktop ...
    (microsoft.public.windows.server.sbs)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... After you uninstall SQL 2005, the instance which you upgraded will not go ... Uninstall and then reinstall ISA server. ... Uninstall and then reinstall the Monitoring component. ... Tools to Maintenance, change Monitoring component to Install, and then ...
    (microsoft.public.windows.server.sbs)
  • RE: How do I get back to base SQL server on my SBS 2003 server?
    ... What's the error message you see when installing SQL? ... the easier way is to restore the server from recent backup. ... Screen shot of the error when you install SQL 2005 Workgroup edition. ... <The server-based applications that were running fine are: McAFee EPO, ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Sql Server ~ Client Install
    ... I've found the client tools and have now ... A word mail merge document could access a SQL database via ... We want to install to gain an understanding. ... Once we've managed to install the SQL Server Client we can start to ...
    (microsoft.public.backoffice.smallbiz2000)