Pretty simple question here: Per the release notes: NetScaler restricts the explicit creation of services on the loopback address (127.0.0.1:80). The workaround recommended is to create a service group. I didn't do this though. I just found that there is an internal service nshttpd-gui-127.0.0.1-80 and bound my LB VS to it to get always up functionality. Question: Is there a reason not do to this binding and use a service group instead?

What's your use case Dennis? I create a service with a 169.254.x.x address and use this with monitoring disabled (so it's always up), as part of my setup to create a single http-https redirect for multiple vservers. I've always stayed away from 127.x addresses and leveraging internal services in case Citrix change something

Citrix changing things is how I got here, so your point is well taken. I like the 169.254.x.x address idea. The use case is the same http->https redirect Always-Up. Not that this is an excuse, but the original service was created before I started working here and I hadn't given it much thought until it broke during an upgrade and came across that internal thing that was added. Appreciate the feedback.