Allan Choiniere

I also considered speeding up the clean up by deleting the object via the command line. But that is to dangerous for me to do. The GUI will stop you from deleting a object like a server that is still bound to a Service Group. From what I read if you deleted the server in the command line it will delete the Service Group too.

The above was achieved by extracting the "Service" object name from all config lines for that VPX add them to a Hash Table. Creating another Hash Table for all Lines starting with "add *" and "set *'. If I had a Service objects name as String that was not on any add or set config lines then it was considered to be unbound. The "Netscaler ADNS" and "NetScaler ADNS_TCP" service objects are an exception to this. Rinsed and repeated for ServiceGroups which we primary use and the list was way to small. There are Monitor binds and SSL binds and Sets that needed to be excluded to get a better picture of unbound service groups.

I'm attempting to do a clean-up of my NetScaler environment as well. Using PowerShell I can backup all my configurations to a folder. I process all the files in that folder. So far I have found all unbound "Service" objects. I'm here because "Netscaler ADNS" and "NetScaler ADNS_TCP" have no binding listed that are no references in the config files other than the creation of the service. Darn good thing I didn't delete them. They are refenced as a binding for ADNS in "GSLB Virtual Server". These must be hard coded and required names not to have bindings in the config files. This leads me to a bigger question what other objects are hard coded and static that I need to worry about???