I'm new to my job and dealing with a setup that has some unique challenges. We use Microsoft Dynamics GP on a remote server, and our organization has two domains: one for users and one for servers. These domains are federated, allowing user domain accounts to access server domain resources. However, users find it confusing having to log in multiple times with different credentials. I'm trying to make it easier for them by allowing the use of their user domain credentials across the board.
The issue I'm facing is that I can log into the terminal server using my user domain credentials, but I can't see the GP installation folder. If I log in with a non-domain account, I can see the folder, but for my user domain account, it's completely empty. I've checked the Group Policy Objects and confirmed permissions are set correctly. The installation folders are supposed to be located at 'C:Program Files (x86)Microsoft DynamicsGP' and 'C:Program Files (x86)Microsoft DynamicsGP$GP2018FR', but they aren't visible when I log in with my user account. Has anyone else experienced this, and how might I resolve the issue without redeploying the terminal server?
3 Answers
Could you clarify what you mean by 'just can't see the folder'? Are you trying to access it through a shortcut or mapped drive? Differences like that could indicate a Group Policy is affecting what users in each domain can see, which won’t apply to a user logged in with a user domain account even if they can access the server.
It sounds like you've already narrowed it down quite a bit. Since you've checked the GPOs and confirmed that permissions are correct, I’d recommend checking if there’s anything else at the machine level that might be affecting visibility. Sometimes local policies or software settings can unintentionally restrict access to certain paths.
It sounds like you might be dealing with Access Based Enumeration (ABE), which hides files from users who don’t have permissions on them. This could be why your user domain account can’t see the GP installation folders even though permissions seem correct. You can check this by looking at your server's settings to see if ABE is enabled on the local file system.
That's an interesting suggestion! However, I believe ABE is mostly for shared resources—not for the local installation paths. It seems like the folder should be visible regardless of the domain used.