Hi all, this worked fairly well. We could not rename the classes with the geometric network present in the feature dataset. Fortunately, our network is small and not complicated. Before starting we reconciled and posted our edits. We create a back up of our sde geodatabase. We compressed the database (hoping this might resolve the original issue but it did not). The feature and map services were stopped. We made a copy of the feature dataset as described earlier ('_1'). Before continuing we confirmed we could add user and privileges in the '_1' feature dataset. Next, we deleted the geometric network in the original feature dataset and renamed the feature classes and dataset as '_orig.' We deleted the geometric network in the '_1' dataset, then renamed the classes by removing the '_1' in each class and the dataset. Thus, we returned to the original feature dataset, restoring the user/privilege add/update function, while preserving the class names and source. At this point we added a couple of fields/domains. The geometric network was rebuilt successfully in the "new" feature dataset. Services were restarted and the dataset was registered as versioned. We discovered had to republish the services as we should have (we think) registered the dataset as versioned before starting the services. Our working feature dataset (_orig)will be deleted along with any remaining '_1' items listed outside of the dataset in Catalog after we are satisfied we are back to normal. I believe I have documented the steps here in the order we performed them. Sigh.....
