"Site System Status Summarizer still cannot access storage object" after DB Move

Question

After our SCCM server was up and running, the DBAs moved the SQL Site Database to a new drive which is a supported SQL Operation according to this Support document:
https://support.microsoft.com/en-us/kb/2709082
Using the methods described by the above document we were able to restore functionality to SCCM but I am still seeing Informational messages in the SMS_SITE_SYSTEM_STATUS_SUMMARIZER component.
Site System Status Summarizer still cannot access storage object "\\<SQLServer>\S$\SMS_<SQLServer>" on site system "\\<SQLServer>". The operating system reported error 67: The network name cannot be found.
Possible cause: The site system is turned off, not connected to the network, or not functioning properly.
Solution: Verify that the site system is turned on, connected to the network, and functioning properly.
Possible cause: Site System Status Summarizer does not have sufficient access rights to connect to the site system and access the storage object.
Solution: Verify that the accounts are properly configured to allow the site to connect to the site system and access the storage object.
Possible cause: Network problems are preventing Site System Status Summarizer from connecting to the site system.
Solution: Investigate and correct any problems on your network.
Possible cause: You took the site system out of service and do not intend on using it as a site system any more.
Solution: Remove the site system from the list of site systems used by this site; this list appears under Site Systems in the Configuration Manager Console.
Possible cause: You accidentally deleted the storage object or took the storage object out of service.
Solution: The components will eventually detect that the storage object no longer exists on the site system and will either recreate it or choose a new storage object. Monitor the status messages reported by other site components to verify that this
occurs properly.
The storage object has been inaccessible since "14/03/2015 1:23:20 AM". When you correct the problem and Site System Status Summarizer successfully accesses the storage object, Site System Status Summarizer will set the storage object's status
to OK, providing that the storage object has sufficient free space.
I have run a site reset to try and fix this but the site server still seems to be trying to access files on the old drive. Is there a method to get SCCM to start looking for these files on the NEW DB drive (H$) in my case?

Answer 1

Was a site reset performed at all yet? This has to be done. 
Torsten Meringer | http://www.mssccmfaq.de
Yes, I tried a site reset prior to making this post. I was sure I had read that this should resolve the issue but unfortunately it seems a site reset did not resolve the issue.
Since we are running a virtualized environment, is it possible the old drive has to still exist prior to running the site reset? If we add a small "S" drive back to the server and run the site reset again, might that help?