Welcome, Guest. Please login or register.

Login with username, password and session length

 
Advanced search

704 Posts in 214 Topics- by 630 Members - Latest Member: BYODre

May 18, 2012, 09:43:30 PM
RES Software User Group ForumGeneralFeature RequestsDispatcher Team
Pages: [1]
Print
Author Topic: Dispatcher Team  (Read 972 times)
rantpe
Newbie
*
Posts: 10



« on: July 13, 2009, 07:23:05 PM »

When deploying application or update that require reboot, it has to been done in 2 phases first dispatchers then rest of PC's. That is because if you boot dispatcher pc when installation is in progress in pc's that have connection to that dispatcher it will fail.
Now we have to add manually every dispatcher in Dispatcher Team, why i can just have a  automatic dispatcher team.
Logged
pkaak
Newbie
*
Posts: 35


Systems Engineer - Centric IT Solutions


« Reply #1 on: July 14, 2009, 04:29:22 PM »

I do not know if I got you right.

When you deploy an update to the Wisdom environment (by means of a WUP -Wisdom UPdate-) the environment will look after this for you. It will first update the components in the database, than update the consoles, update the dispatchers (one by one) and lastly update all active agents. That way the agents will never loose connection with the dispatchers (unless you have only one dispatcher).


But reading your text, I think you are trying to update an dispatchers software, other than Wisdom components. Can you clearify that a little?
I think best practise is to not install other services on dispatchers. If I look to what they have to do, most dispatchers are very busy doing the dispatcher tasks (with Wisdom 4 it was even unpossible to do other things on it as cpu was mostly 100% for the dispatcher service).

Logged
rantpe
Newbie
*
Posts: 10



« Reply #2 on: July 14, 2009, 09:29:22 PM »

Problems is that we have 280 sites, so we have to use PC's as Dispatchers. This was very reason Wisdom was bought. It is impossible to buy servers or extra PC's for sites that only have 2-5 PC's.
And you are right i was talking about application distribution not Wisdom components.
System has been up and runnig over a year (1350 pc's) so far no big problems. 
Logged
Airdeca
Newbie
*
Posts: 41



« Reply #3 on: July 15, 2009, 10:59:57 AM »

Hi Petri,

You got a point there. Normally 1350 agents only require about 10 dispatchers which can easily be put in a Team manually. But with 280 sites and probably as many dispatchers I can imagine you would like to have some automation.
Unfortunately the current Team Rules don't really give you an option (unless you want to rename all dispatcher machines so you can use the FQDN Rule). I suggest you put in a feature request at support@ressoftware.com explaining your situation. They might be willing to add 'RES Wisdom Dispatcher' to the list of Computer Functions in the Team Rules.

Good luck,

Rob
Logged
Pages: [1]
Print
Jump to: