For security reasons, I need to prevent the users from seeing the hard drives in the open dialog pop-up box. I wish to disable the "up one level" button and prevent users from typing full paths in the file field (i.e., c:winnnt). The NTconfig.pol file works for all my security except the above. The domain PDC (primary domain controller) is NT4 (SP6a) with Win2000 Pro clients.
I have installed the Office ADM files and found the control IDs for Office applications, so I can block certain menus (e.g., macros) but I cannot find the Open or Save As popup control IDs.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Thank you for any help given.
Sounds like you've done your homework and got the technique down for blocking user selections; the Word 2000 system template exposes settings under "disable items in user interface" that allow you to disable many predefined menu items. Another entry, one for "custom" entries like "Custom disable command bar buttons and menu items" and one for "Enter a command bar ID to disable," allows you to disable any command bar by entering its control ID. To find these IDs, the Office Resource Kit provides sample Visual Basic for Applications code. Command bars, by the way, are menus and toolbars, but also pop-ups and right-click menu item lists. Find the control ID and you can disable them.
Perhaps the best code example I've found is one in the Microsoft Office XP Resource Kit that allows you to print a Word document that lists all the possible command-bar names, controls within the command bar, all sub-controls and controls IDs for Microsoft Word. This code is example 6 in the chapter Using system policies, along with a discussion on control IDs and disabling interface objects. I'm unable to locate similar code for Office 2000 and am not sufficiently up on the differences between the two products to tell you if this code will work as is for Office 2000, but it should get you started.