Jim,
Thanks for the reply. I am aware of the problems that arose from Microsoft's MS16-072 patch. They have been resolved on all of my networks. However, in my troubleshooting of this issue, I have found that uninstalling ESET from the computer resolves the problem. Re-installing brings the problem back. Also, I have found that when ESET is NOT installed on these problematic computers, running a gpupdate /force will cause the drive mappings from GPP to instantly populate. If ESET is installed the drive mappings don't populate immediately but will if I log off and back on.
As I stated, this is not happening on all computers. Just a few. But it is reproducible on those machines.
If there is a way to rule out ESET that I have not thought of I would be glad to try it. All signs right now are pointing towards it being the cause.
Thanks again,
Jake