Yesterday I cloned a terminal server to another server. I used ghost 8
to do the cloning. After cloning I used newsid to rename the server and
generate a new sid. After that I adjusted the settings in nlb (cluster
IP address, priority, dedicated host address, etc.)
When a single server is up the clients can connect to the load
balancing IP adres. When both are up clients cannot connect to the load
balancing address.
When both servers are up and running no errors are shown in the event
log and nlbmgr shows the status as normal.
Re: Load balancing problem in w2k3 ... > resource based load balancer for Terminal Services. ... >>I guess you are using NLBS (Network Load Balancing Services) for you TS ... >> redirected to the same server in a cluster. ... >> Microsoft MVP Windows Server - Terminal Server... (microsoft.public.windows.terminal_services)
Re: Best Practices deployment Terminal Services incl. Applications ...cloning methods and products are best suited to pure operating ... parameters relating to application installations, whether these are server... Microsoft MVP Windows Server - Terminal Server... (microsoft.public.windows.terminal_services)
Re: Ghost 2003 and Server 2003 ...cloning and imaging (for backup purposes) Windows 2000 Server ... I was hoping Ghost it would work with Server... (microsoft.public.windows.server.general)
Re: Microsoft Clustering and NLB ...Web Server, Standard, and Enterprise (and DataCenter/SBS but who would ever ... use them for NLB) all have NLB in them with Server 2003. ... > So does NLB include Load balancing as well as Failover ... (microsoft.public.windows.server.clustering)
RE: Windows Server 2003 - Cloning/Mirroring/Clustering 2 identical ... protection on the server in question? ...clustering is obviously the way to go but it is expensive. ..."Fyrestryke" wrote: ... somesuch) by cloning to a USB external drive and then cloning that back to ... (microsoft.public.windows.server.networking)
