Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Everyone,
I'm having a bit of an urgent issue with some apps that I can't get to disappear from AccessPoint.
The server is using NTFS permissions, and the entire drive is hidden from excluded users, but the apps are still showing up in AccessPoint. The user I'm trying to hide these from has explicit Deny settings in the apps' permissions, and I've checked to make sure the user isn't in a group whose permissions might supersede.
Moving the apps to another folder is not an option in this case, because other users do need to see them.
Any ideas?
Thanks,
DJ
Hi Everyone,
It looks like it was a combination of complexity in NTFS permissions. We just removed the directory and rebuilt the structure. It was quicker and simpler that way.
Thanks for your assistance!
You may solve this by using subfolders (maps) in your production map.
QV shows also the submaps.
Ofcourse you need to set user rights on that submaps as required.
Regards,
Gerrit
I guess some other permissions or groups 's permission is overriding this deny option. This is definitely a logic issue.
Please revisit your permissions.
Regards,
Karthi
A great trick to check what NTFS permissions really apply to a QVW document is to use "Effective Permissions". See Properties->Security->Advanced->Effective Permissions.
Group membership easily twarths your assumptions about applicable NTFS rights, especially with a mix of domain and local groups.
Peter
Hi DJ,
It's nothing to do with the NTFS permission setting, you need to set it on QVMC which is under Document Setting.
Hoped it help.
Regards,
Kho
Hi DJ,
The NTFS permission only control the access rights of particular APP, it will not enable you to hide it from the AccessPoint. You're require to un-check the above three (3) options on particular APP to hide it from the Access Point.
This method will hide the particular APP from Access Point after user login without changing any other setting and it is easy to restore while required.
Regards,
Kho
Hi Everyone,
It looks like it was a combination of complexity in NTFS permissions. We just removed the directory and rebuilt the structure. It was quicker and simpler that way.
Thanks for your assistance!