Word 2010 Exam login - remove right-click context menu
We're looking to upgrade our Office version in our school from 2003 to 2010.
As part of that I need to recreate the account we use for exams / controlled assessments that restricts use of Spellcheck, Thesaurus, translations etc within Word.
The task is almost complete (ribbon options locked, keyboard shortcuts removed etc) using mainly group policy with the odd thing locked with a mandatory profile. However, there is one problem that persists that I have yet not been able to solve - the right-click context menu within Word.
Ideally I'd like to remove just the "Look up", "Synonyms" and "Translate" options, but as a fallback we can lose the entire context menu if needed (or indeed possible).
I though the solution may lie in the disabling the contextMenu control ID's in the word 2010 Admin Template in Group Policy, but I can't seem to track down the ID's for these functions.
Anyone managed to resolve this problem by any means?
Make sure this registry key is applied to all concerned users (via log-on script or other means) since this a HKCU registry key. You can restrict access to registry editor to prevent users from changing these settings.
I didn't have any of the Key values below "Office", but if you manually create the keys and then add the String values listed all works perfectly.
@LSDWho That is awesome. I'd got as far as doing the toolbar menus, but couldn't work out how to adjust the context menu. Unfortunately, we're still not quite there as users can still Alt+Click on a word to open the Research Pane, even though that is disabled (Policy ID 7373 and 7387). Did you find a way around that one, too?
As it was a while ago I can't exactly remember what each of the disabled ID's that I entered into the policy do. In the hopes that it helps below is a full list of all the IDs I disabled. And below that all the disabled Shortcut Keys with modifiers.
@LSDWho - that is truly awesome, I've copied your settings and they work! I've read so many threads on this, and even contacted Microsoft themselves, without finding a solution. Thank you, thank you, thank you, [repeat until fade] :-)
The funniest / most annoying thing about this is that I even asked Microsoft, both via TechNet and also a contact I have who is quite senior within MS, and they were unable to offer a full solution! EduGeek FTW.