Great catch Jim. There's nothing here specific about NOD. This is a problem generally with ALL customers.
Jim alludes to needing to write to the filesystem but in fact that's not necessary. Users should use the GUI's rather than fallback to editing config files and so forth.
So a windows user (like a NOD user) who is NOT an windows admin can infact perform this work around as follows:
This is probably a defect in distsrv and is not NOD-specific. This case should be escalated to R&D not to NOD operations. There's nothing that NOD operations can do about this. needs to be fixed in the product. Based upon Jim's comments, the issue can be worked-around by 1 -stopping distsrv 2 - use raw configure (via infrastructure manager) to remove the batch jobs (instead of editing the cfg file by hand) 3 - use windows explorer to copy any probe packages one wishes to save over to a temporary windows folder.
4 - Start distsrv 5 - use distsrv GUI to delete the unwanted/unnecessary probe packages as well as the ones that you may have copied to a temp windows folder
6 - After the upgrade, then the packages that were saved in the temp folder can be imported into distsrv using the infrastructure manager.All of the above can be performed by the customer via Infrastructure manager. There's no need to engage NOD operations to do this.