@Nino Bilic Any update on multiple 3rd party monitoring tools now broken
by this update? Modifying powershell script on a 3rd party monitoring
platform is hidden inside of code and likely signed so not easy to
modify. This puts us in a very hard place - do we proceed with a
security update that look...
@Nino Bilic should this be read as ms is not gonna change it back to
ps.AddScript() will work again?our support tools is using AddScript to
run big scripts, and its a bit easyer to handle than having to mess with
addcommand on all those diffrent commands.
Nino BilicThank you for answer.We and a lot of sysadmins are HAPPY to
see these changes.We double happy, because this product is outdated and
EOL.Now we don't have working backup by Netapp.Thank you guys for your
hard work! ;-(
@Alternator - Please contact the vendor; they will need to modify how PS
code is called in this particular case - change from .AddScript() to
.AddCommand() and then it will work.
Latest Comments