BAT or VBS to open random file.

USF-Nealio

Limp Gawd
Joined
Jan 18, 2012
Messages
373
I recently got a new client at work that has several terminal servers that my users will need to connect to. There are 2 servers and I was asked to distribute the links to those servers in such a way to prevent overloading 1 or the other. My idea is to put the 2 RDP files in a network share, and create a BAT or VBS script that would randomly pick 1 or the other. Any ideas?
 
You'll have to use VBS, since the batch file language doesn't have a mechanism for generating a random number. Are you sure the approach is going to solve your problem, though?
 
I'm open to suggestions, but I don't see how else do to it.

They aren't my RDP servers, otherwise they'd be in my Citrix farm and XenApp would load balance the hell out of them.
 
"you 10 people get access to this server, and you 10 get access to this one"
 
First, random will not load balance. Second, will users be storing anything locally? If so random is bad. Third, this sounds more like a process issue with your client. They should assign users to a TS. Classify users as heavy, moderate, light or something (that doesn't sound like a commercial for a tampon) and try to distribute the load based on classification. Then just provide the appropriate RDP to the user.
 
First, random will not load balance. Second, will users be storing anything locally? If so random is bad. Third, this sounds more like a process issue with your client. They should assign users to a TS. Classify users as heavy, moderate, light or something (that doesn't sound like a commercial for a tampon) and try to distribute the load based on classification. Then just provide the appropriate RDP to the user.
Load balance can refer to number of connections, just as much as resource usage. Sounds like this application doesn't need resource based load balancing. As far as data storage, the could be utilizing net work storage, so no problems there.

Windows has basic capabilities for connection load balancing, which is why I asked after the server OS.
 
Except that random won't produce any type of load balancing, resource or connection count. Random creates a random amount of connections per server. Random "could" end up placing all connections onto a single server, although that's unlikely.
 
Except that random won't produce any type of load balancing, resource or connection count. Random creates a random amount of connections per server. Random "could" end up placing all connections onto a single server, although that's unlikely.
Which is why I was asking about the server version. 2008 has built in tools to do connection based load balancing. I think 2003 even has it too, but you might need additional software to pull it off.
 
Back
Top