This is a weird one, so hold on....and one of the oddest problems i've ever run into.
So for some of our clients, we run their GP in a "locked down" state -- they log into their remote desktop session and we run a batch file that just starts great plains. They have access to the desktop, but an absolute minimal. Back in the day, we used the "Environment" tab in AD to just start GP when the logged it.
Been working fine for 15 or so years until this week.
This week, when the users click on a link they've setup in GP (say, to their bank website), chrome, the default browser, will launch and hang. If we setup a shortcut to run chrome, it also hangs.
If they start chrome outside of GP, but still in session, it works fine.
Here's where it gets weird.
If we start chrome before GP starts, and leave chrome open, everything works as expected. But if we close that inital browser, nothing else works.
If we use, edge, it does the same thing (because it's chrome)
If we use firefox, does the same thing.
chrome logs shows that it's the chrome network service stopping and restarting about once every 2/10 of a second, which makes the processor go bananas.
As a very awful workaround, i made a batch file to start powershell, then launch chrome, and then launch the bank website, but that's kind of kludgey, and i'm worried that i'm going to break other 3rd party integrations that may shell out to a website from inside of GP.
Just wondering if anyone has seen anything like this...ever.