Robert Blissitt Posted July 14, 2020 Share Posted July 14, 2020 Every time I make a change within ADM (e.g. enabling AppFlow on a Virtual Server), my config is saved on the target ADC. Is there a way to prevent this? I often do not want to save every change on my NetScaler right away. Link to comment Share on other sites More sharing options...
Rhonda Rowland1709152125 Posted July 14, 2020 Share Posted July 14, 2020 The config appflow is one of those config "procedures" that does save when the ADM does it. If you were to implement the configs as a "job" that you script yourself, it will only "save ns config" if you include the command in the script (or potentially in the job properties...but I can't remember if that option is there.) The config appflow and some of the other procedures adm does, do autosave, like many of the "wizards" in the adc itself (like the unified gateway wizard). I don't think there is a way to prevent the ADM from doing this for the shortcuts for management that it uses. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now