Home
> Work > Useful details and links when rolling out Microsoft Project 2010 #PS2010 #ProjectServer #SharePoint #SP2010 #MSProject #in
Useful details and links when rolling out Microsoft Project 2010 #PS2010 #ProjectServer #SharePoint #SP2010 #MSProject #in
In my current project where we are integrating SharePoint Server 2010 and Project Server 2010, we are starting to go into the details of rolling out the Microsoft Project 2010 client globally.
Some of the features we are implementing require VBA macros in MS Project 2010 which are brought down to the client application via the Enterprise Global Template from Project Server.
The following details and links have been useful during my investigations:
ADM Templates for Office 2010 – AD Policy Templates:
- Information: http://technet.microsoft.com/en-us/library/cc179176.aspx
- Download: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=64b837b6-0aa0-4c07-bc34-bec3990a7956
How to Digitally Sign a VBA Macro in Microsoft Project:
Registry Key to change:
- \\HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\MS Project\Security\VBAWarnings
Registry Option Values:
- 1 = Enable all macros (not recommended; potentially dangerous code can run)
- 2 = Disable all macros except digitally signed macros
- 3 = Disable all macros with notification
- 4 = Disable all macros without notification
- NB: The text in the options match those available in the Trust Center in File > Options of the Microsoft Project 2010 Client.
Categories: Work
Active Directory, ADM Templates, Macro, Microsoft Project 2010, Office 2010, Project Server 2010, SharePoint 2010, VBA
Hi,
I am using MS project 2007 , Can you Help me in suggesting which key need to me modified in Registry to make the Macro security level to medium.
Regards,
Kunthanraj
Hi Kunthanraj,
I would look here:
Path: software\policies\microsoft\office\12.0\ms project\security
Policy: Security Level
Options: Low (not recommended) | Medium | High | Very High
Value: 1 (Low) | 2 | 3 | 4 (Very High)
Please note you will need to log off and back onto the affected desktop before the changes will take affect.
You can also deploy this globally using the Admin Templates.
As a recommendation, can I suggest you do not change the security but sign your macro with a certificate instead (even with a local certificate authority). This keeps everything just a bit safer.
Kind Regards
Giles
PS. Template details for 2010 are here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18968 This includes a good spreadsheet of all settings across the office products.
The 2007 templates are here: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=22666