Unimus forum

For our use case one-time would be fine and definitely how we would use it most of the time. Of course the more general solution would be to allow one-time or recurring.

We upgraded to 1.7.0 and rebuilt our mass config push scripts which were completely lost in the upgrade. We have a simple script that we are pushing out to some devices (20 total) and after running the job experienced the following results. From the web based UI we see: unimusconfig.png Here are the...

This was from the beta discussion, just do not want it getting lost: One enhancement that would be AWESOME is if when you select devices that you could pick NetXMS container names and then it would maintain that list of devices that this applies to based on that. Would just help to provide us with m...

While the mass config push feature is nice, it does not really solve our needs without the ability to run this at a configured time. The use case for us is that we run a business where upgrades typically can only take place in the very early morning hours. Instead of having to get up and perform the...

Just a warning for any that were on the beta versions. While we were told the commands inside presets had to be cleared for some reason, our experience was that ALL of the presets were lost completely. Would make note of them if you had some built up so that you are not wasting time needing to recre...

We talked with the team today on how to best implement this. (since this needs to work not just for NetXMS, but also for Zabbix, and other future importers we want to add) We decided on this: - Importer will be able to Tag devices (using already present Tag features) that they import like with the ...

This morning that job was now IDLE, but nothing more got logged including the list of devices that were not updated. My guess is that the other standard backup jobs running pushed the status to IDLE. However, this brings me to another feature suggestion for this and that is the ability for Run Now t...

It remained and remains in the RUNNING state! Yes, I agree you need to show the log for the failed ones as well as the ones that do not fail so we have something to go on. Like I mentioned originally though the "failed" one actually succeeded and the commands ran as it was there if I looke...

Ok, so we are following the Mikrotik mass updater to get our feet wet and it is something we would want going forward anyhow. During the first step where you push out the upgrade-package-source after testing it on one device (and then deleting it) we selected a group of about 20 devices. After runni...

We are VERY excited for the features in this version and are starting to work on the mass config option for our network. One enhancement that would be AWESOME is if when you select devices that you could pick NetXMS container names and then it would maintain that list of devices that this applies to...