UGH! User's workstation keeps locking up in Sage (only), so Outside IT thought he would uninstall the Sage client (v2017 Standard) and because he wanted to remove the registry entries, he used his own 'little program' to remove the client and ultimately removed the Sage 100 Directory on the server, yes on the server! He needs to rethink this 'little program' he has. I did advise him of workstation removal!
So he calls (after he restored from last night) and asks what permissions are needed on the directory and in addition they want to stop users from being able to delete the directory (via browsing or uninstalling with a 'little program') - he immediately wanted to call Sage. Yeah...they'll tell you 'full control'. I told him he could maybe get by with Modify and he kept saying he was going to 'remove delete'. Didn't argue, as some days you just can't fix Stupid! Not sure what he did but he broke Sage with that change and so put it back to Full.
Again he is telling the client he needs to call Sage (which I'm about to let him do, just to make him pay for his little 'program') but wondering if anyone has a document as to the permissions needed on the Sage Directory.
On the same note, how does IT keep users from going into the mapped drive and deleting the directory? I've never really paid attention or tested if users were able to delete and nobody has asked.
N
------------------------------
Nancy Hanson
Blytheco LLC
Eagan MN
------------------------------