You’re offline. This is a read only version of the page.
We recently upgraded a large client (almost 400 users) to GP2013 on new servers. They are keeping their old GP10 server and terminal server up and running for awhile and have requested that we make the old GP 10 installation "Read Only" for everyone except one user (and sa of course). Specifically they have asked that users have access to the same functions and roles they had before, except that they cannot create any new transactions, they can only VIEW.
So in my analysis, I have come to realize this is not as easy as it would seem. For individual users the recommendation has been made to create a security role that only has access to the INQ tasks, which works fine. But I want to make sure this would be the recommended method for ALL USERS before I write a script or use the Support Debugging Tool to change everyone's security role.
Is there a better way to do this? Should I perhaps focus on modifying the Default User Role? Can this be done with the Support Debugging Tool?
*This post is locked for comments
Jonathan, you have missed the one comment from the post
"make the old GP 10 installation "Read Only" for everyone except one user (and sa of course)"
This makes your suggestion a little to restrictive.
Leslie still has the correct answer in using the Limited Users.
The other thing you can do is set your Dynamics GP databases to Read-Only mode. Here is a link to a guide that shows how to do this. ask.sqlservercentral.com/.../set-a-database-to-read-only-mode-in-sql.html
Leslie, my thought was similar, but did you have to apply a different set of security rights to the limited users, or does that happen automatically?
I like all the options above, but Frank and Mahmoud your solution will shut everyone out of the system - including SA and the one user as requested by DynBear.
If Leslie is correct and the limited user works as she says, this is the best answer to the problem.
Hi,
Isn't this exactly what the 'limited user' is supposed to accomplish? My clients got a certain number of 'limited users' when they upgraded to GP 2013. I don't sell the software, so I'm not sure how all of that works. But we changed the 'executives' from Full users to Limited users and that seemed to do the trick.
Kind regards,
Leslie
That's a great idea Mahmoud. I was also thinking of turning off posting in all modules . . .
That would definitely be the best way, revoking the access to any transaction entry window while keeping the inquiry, reports and smart lists accessible. But I was just thinking, how about closing all the periods for all the modules ? That will prevent users from entering any transaction in any module.
I believe you may consider this as a quick solution, meanwhile, having the entry windows revoked is definitely more professional method.
Let us know if you need any further inquiries,
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (