My Notification Server had its mind set on creating a second GUID. I'm not sure why, but it looked problematic. Here's what we did to solve the problem.
My Notification Server is creating a 2nd GUID for itself. After merging, it goes away, but after a config request it comes back.
NS 6.0.6074 Sp3 R1
This Notification Server had been upgraded from a previous virtual machine, and the NS database had reference for this machine. Combined with fact that a new alias for the server was developed, this confused the NS and caused the 2nd resource to be created and recreated.
Deleted both instances of this server in the NS. Updated Config, and the problem was resolved.