Could you make it possible that when a automation script has been run we can put the output of the script into the body of an e-mail without having to mail it through a self defined smtp server. Now i use the Nofication Sussess Failed and Send task output file in Email. But this is in a zipped file and i would like to have it as the Body of the mail. Maybe you can make a output to body of nofication mail in the automation ...more »
It would be nice to be able to use booleans in an automation policy with the added effect of allowing certain input parameters to only show when certain boxes are checked. This would allow for more complex and user friendly Automation Policies without the need to give the user to many options when they are running specific Automation Policies. To give a small example, I have a disk cleanup script that has multiple sections ...more »
I often have trouble getting powershell and other scripts to work via automated tasks. I can run them directly on the server or workstation and they work just fine, but then I run into trouble when running it as a task. The frustration is that it takes a while to run the tasks through the dashboard, so you end up running and waiting. Then it errors out so you come back to it, modify your script or config, run it again... ...more »
Like it is possible to do SNMP Asset Discovery, it would be nice to have this also for PowerShell objects. You ask for a list of powershell objects, and this information will then be included in asset scan and can than be used as asset information for service templates:
Examples: different sheduled tasks, different DHCP scopes, ...
Starting with Windows Build Build 1497, Powershell is to replace the command prompt as the default shell and signalling the end is near for the command shell sub-system. Please change the shell to Powershell in the Remote Background feature before it becomes unavailable/unusable (or give us the option choose the shell via a policy). https://blogs.windows.com/windowsexperience/2016/11/17/announcing-windows-10-insider-preview-build-14971-for-pc/#3dUWruqyP1tX5x0V.97 ...more »
Now that PowerShell is open source and supported on Linux/Mac OS X, it would be nice to have this integrated to the Mac agent so we can re-purpose some of our existing scrips/use script manager to create new scripts that also target these platforms.
Would it be possible to allow the font and colour scheme to be customised per user for ALL servers I connect to? I am finding the defaults a little tiring on the eyes.
In addition, can we also set it to run powershell in preference to the legacy CMD?
Enable support for Powershell in remote command shell,
so we can remotely do infinite actions better then old dos commands,
and install software with http://chocolatey.org (now works, but sometimes goes in error)