Windows 2003 TS load balancing

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi all, I have a client which has a performance problem with their
current TS server. The hardware is fairly new, and RAM is maxed out
(4GB). They run Windows Server 2003 Standard. I was thinking about
implementing some kind of load balancing, but after reading some on
Microsoft's site, I found out that Session Directory was out of
question because it would require Entreprise or Datacenter edition.

What I was thinking about was setting up a second server which I
currently have on hand, and set it up as a TS server. From there, I'd
setup some computers on the first server, then setup the others on the
other server. I was just wondering what that would require in term of
setting up, administration, and just general advice. Or if you have any
other suggestion, let me know.

Thanks

.

Relevant Pages

  • Re: Virtual Memory in use at 100%
    ... I just had a Hardware Malfunction again. ... I had to restart the server so I ... hardware problem but a software memory leak and they told me that the best ... > RAM compatibility, etc, can be the torture of anyone doing hardware/OS support. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server Recomendations
    ... An example for you is I have 1 small client that I is setup with the ... more users I would spec a MB supporting more RAM and better drives. ... In general with SBS 2008 you need at ... roaming profiles, VPN, will it also be the AV server? ...
    (microsoft.public.windows.server.sbs)
  • Re: Server stops responding
    ... And you might want to run a RAM tester and/or a utility that will ... but it sure looks like hardware as you suggest. ... but he's considering a whole new server anyway and is holding off. ... I'm not used to SBS doing bad things and not telling ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I turn on logging to troubleshoot consistent lockups ?
    ... I'd start with the server mfr's diagnostic utilities, especially RAM and possible overheating. ... You can almost rule out overheating if the server comes up normally right after having frozen up, but it's definitely worth a look. ... You have to ask yourself if there was any change in the server or its installed hardware, drivers, apps and so on just prior to this starting and determine if you can reverse that. ... The most likely thing to diagnose this kind of condition is to disconnect from the interent and do what MS calls a "clean boot", which is to run MSCONFIG and stop all non MS services and startup apps and see if the problem stops. ...
    (microsoft.public.windows.server.sbs)
  • XP & 2003 Disk I/O Differences
    ... Mind you these tests were setup with one constant, ... In both test scenario's the hardware never changed. ... Server 2003 gets about 250MB a sec writes. ... I'm "assuming" optimizations have been written into ...
    (microsoft.public.windowsxp.general)