If only there was a section on the support site that had "Announcements" for things like this.. hmm.....
http://support.nimsoft.com/Default.aspx?center=portal/announcement
But anyway I had to update 1400+ robots last night or I should say downgrade. We reverted back to v7.05 and will wait for v7.63 official.
Along these lines does anyone have any suggestions on doing this in a more efficient manner? We have 100+ Customer Hubs (tunnel) and I went about updating just the robots, not the hubs in the follwoing manner:
Within IM I have "Show Groups" enabled in the Tools Options.
I created a bunch of new Groups: All Robots, Set1, Set2, Set3, All Hubs
I then did a Ctrl+F (FIND) and did a search on ALL ROBOTS. Found the robots that has the bad build, selected those and dragged them in bunches into the different Set#.
I had to then make sure not to select the HUBs since the when distributing if I am updating the hub in the update, while its rebooting the machines that were queued up would fail since no communication could take place.
*Question, is there an easy way to select just the HUB or search by robot and specify just return HUBS. Initiall I don't see a way unless I populated the User Tags with "HUB".
Then after making sure that no hubs were in the SET groups I dropped the robot_update v7.05 from the Archive. 5 out of the 1400 were uncessful but it did take > 1 hour to deploy. I made sure to check off the [ ] Update Only check box. Can anyone explain what does that check box actually do and if you dont' check it what does it do then?
Anyone have a better method or suggestion when doing mass deployment updates like this? We are not utlizing the Admin Console as we found this not to be very reliable.