 | | |
| | |
|
Spaces home  Applepark LtdProfileFriendsBlogMore |  Tools   |
Applepark LtdProject Server bloggers!
August 05 Microsoft Project Server 2007 Training<Brakspear Oxford Gold> If you've been looking out for training for Project Server or Portfolio Server training, there are now a few options... 1. Enterprise Project Management University - This has been running since Project Server 2003, and since that time has evolved from being a set of slide ware (though with lots of screen shots) to a full interactive course run in a virtual environment. There are now four courses to choose from... IT Professional - Technical Implementation and Configuration of Office Project Server 2007 Admin Professional - Functional Implementation and Configuration of Office Project Server 2007 Office Project Server 2007 Developer Training Deploying Office Project Portfolio Server 2007 Full details can be found at http://www.msepmu.com/courses.htm. The courses are delivered by trusted Microsoft Partners, and Applepark are pleased to say that they are delivering the IT Pro and the Admin Pro courses in the EMEA region. We also delivered the 2003EPMU courses in EMEA, and an earlier classroom based version of the 2007EPMU courses in EMEA too (using a virtual PC in a classroom environment), so we've already had a lot of experience in delivering these courses. 2. Microsoft Official Curriculum courses for Microsoft Certified Technical Specialists MCTS - Enterprise Project Management with Microsoft Office Project Server 2007 - course 5928 MCTS - Managing Projects with Microsoft Project 2007 - course 5927 MCTS - Microsoft Office Project Server 2007 - Configuration MCITP - Enterprise Project Management with Microsoft Office Project Server 2007 - course 5929 These courses are run by Microsoft Partner Learning Specialists (CPLS). Xpertise training are running these courses in the UK. June 12 Problems with Status Reports<dry again> Status reports have been around since Project Server 2003 (or even in 2002? - I can't remember), but I do know that I've had various problems with them in 2007, but haven't been able to specifically reproduce them in order to get a bug raised with Microsoft. My specific scenario was that when Status Reports where deleted users were still getting reminders to send the reports; in addition other Status Reports were successfully sent but actually never received by the Project Manager! Both of these issues started after a few false starts with Status Reports, we'd created quite a few for testing purposes and then deleted them. As part of the troubleshooting process I started delving into the published database and discovered that deleted status reports are not deleted, but marked as disabled. In order to clean up the Status Reports I decided to clean up the database using some SQL scripts. Here's the caveat - I'm no SQL guy, so though this worked for me there are no guarantees it'll work for you. Also it's a semi manual task involving two separate steps; someone smarter than me can probably create a single script that does the same job - if you can - I'd like a copy. The 1st stage finds all of the records that need deleting; the 2nd stage deletes them. 1st stage The 1st thing to do is to select the published database and then get the UID for the Status Reports that are set to False (i.e., deleted ones) - my DB is called project_live_published -- define the database ** yours will be different** -- get the SR_UID from SR_Reports that have been deleted Use this output to as part of the next select statement to find all of the Response UIDs (SR_RESP_UID) from the SR_RESPONSES database. -- get the SR_RESP_UID for the "deleted" reports The output from both select statements is then used to select the rows that need deleting in the database. 2nd stage The following tables are effected; SR_DISTRIBUTION; SR_SECTIONS; SR_RESPONSES; SR_REQUESTS; SR_REQUENCIES; SR_REPORTS My SQL script looked like this. -- define the database -- delete the records from SR_DISTRIBUTION -- delete the records from SR_SECTIONS --delete the records from SR_RESPONSES --delete the records from SR_REQUESTS --delete the records from SR_FREQUENCIES --delete the records from SR_REPORTS That worked nicely for me; however, we've just had a change of project managers so we might have to go through the whole process again! Good luck! May 01 How to set up permissions so that Project Managers can Save their own projects, and open all others in Read Only mode
This question comes up again and again, and I can't remember where I found this information from all those years ago (it applied to Project 2003), but I wrote it down and seem to use it for most clients. It's easily adaptable for Project Server 2007 - one day I'll write it properly and update it for 2007! Project Server Security (P2003) Overview Project Server Security is complex. There are two types of permissions, five places to set them, and three conditions for each permission (allow/deny/soft deny). Appendix C & D of the Project Server Administrators Guide should be used for further reference. Permissions There are two types of permissions, data permissions (what data the user can see) and use permissions (what features the user can use). Each permission is not readily identified as to its type. Microsoft use the terms global for use permissions and category for data permissions. Additionally, they use the term Organisational Permissions, which are a set of permissions set for the whole organisation, and encompasses all of the use (global) permissions plus the 14 data (category) permissions. The Roles of Security Templates, Groups & Categories A security template is a predefined list of all the permissions (data & use). This list is ordered by permission area (admin, collaboration etc). Templates should ideally be named the same as groups. A Group is a collection of users. A single user can belong to multiple groups. The use permissions are determined at the group level, and therefore group membership is the primary factor is determining the functionality that a user has within the system. A Category is used to define the data permissions (hence Microsoft’s term, Category Permissions), i.e. what data can a user see, what actions can they perform on that data, and which views can they use to see the data. Categories are applied to groups, a single group can have multiple categories applied to it, and a category can be applied to multiple groups. The permissions applied to each user is therefore a combination of the categories and the group membership. Alloy/Deny Three permissions are allowed for any permission. They are ALLOW, DENY, and soft deny. Soft deny (blank) is implicit if neither allow nor deny are selected. If a permission is set to deny in one place the system, then that becomes an absolute deny everywhere in the system, even if the permission has been set to allow elsewhere. If the permission is blank then the decision as to whether to allow or deny the permission is made elsewhere in the system. Server Configuration Features This is available in the PWA Admin tab, under server configuration, in the Select the Features That You Want to make Available to Users in Project Web Access section. Either set these use permissions to ALLOW or DENY. It is inappropriate to have blank here. The permissions lists here are the use permissions. Templates Use the templates to define a set of permissions for a particular role. The templates contain data and use permissions. Only change a use permission here to DENY if you want to deny a permission for a particular group, that has been globally allowed (via the Server Configuration Features) above. This is the 1st opportunity to set permissions, so these should be set here to allow/deny as appropriate. Categories Categories define data permissions, and are further enhanced by data restrictors. Categories are assigned to groups, and a group may have more than one categories assigned to it. Groups The use permissions are set by the group. Assign the use permissions by applying the relevant template. Users Users are placed in groups. Never assign permissions to a user, troubleshooting the security will become too complex. Recommendations Security should be established in the following order
See figure1. below for a graphical view of this.
Initial setup for Acme PLC The following was set up on the live system for Acme PLC and used as a basis for security. What I've done here is create categories called GROUP_NAME - See Everything. Within the category set up you need to select the button that says - See all future Projects/Resources in the Database.
Templates Resource managers - see everything Execs - see everything Portfolio managers - mod all (no admin) Project managers - see everything Team members - see everything except money Categories Resource managers - see everything Execs - see everything Portfolio managers - mod all (no admin) Project managers - see everything Team members - see everything except money Groups Resource managers -> CATEGORY = Resource managers - see everything Executives -> CATEGORY = Executives - see everything - Portfolio managers -> CATEGORY = Portfolio managers - mod all (no admin) Project managers -> CATEGORY = Project managers - see everything - *When you make this assignment for the category you need to enable the category permission to open all projects in the database, but not to save them* -> CATEGORY = Project managers Team members -> CATEGORY = Team members - see everything except money April 24 Changing the Project Manager
During the lifetime of a project it is sometimes necessary to change the Project Manager (due to a leave of absence). The process to do this has changed between 2003 and 2007. There are three areas to be concerned with 1. Changing the Project Manager; Changing the status manager; replacing any PM resources. Before you start on any of the above, make sure any updates to the project have been accepted, and that any changes have been fully published. This results in lots of emails too, so worth making team members aware of what is happening. 1. Change the Project Manager This is done in PWA. Select the project and Edit the Project Properties, and change the Owner to reflect the new Project Manager.
2. If necessary, change the Status Manager. As the new project manager, open the project in Project Professional. Insert the Status Manager Column, and change the status manager for each task to be the new project manager.
Note that it is not possible to change all the tasks at once, but it is possible to use CTRL-D to copy the changed status manager field down.
3. If the old PM has assignments on the task, then these need to be changed too. There are 3 scenarios for the task
The approach to replacing resources for all three scenarios is the same, and this should be done by using the Replace function within the Build Team from Enterprise Tool.
Here we are going to replace Ralls Kim with Allen Tony, by highlighting them both and clicking on the Replace button. If Ralls Kim already has actual work associated with a task, then the following information box appears.
If a task is 100% complete, Project asks if you want to move the work to the new resource. Note it doesn't tell you which task, and the correct answer is Cancel.
For Task 1 which already had actual work on it, Project assigns the remaining work to the new resource. This is shown in the split lower split window for the Task 1. (in our system here Allen Tony has limited availability so the task has been been split and automatically rescheduled). The actual work completed by Ralls Kim has remained in place.
Finally, Save and Publish the project to make Team Members aware of their new responsibilities. February 01 How to move a sub Project Workspace to another programme site.IntroductionThis blog details how to move the WSS workspace between sub-sites. This may occur if a project is moved between programmes (setting up a programme is discussed in this blog here http://appleparkltd.spaces.live.com/blog/cns!EB0688A7A6F04E1D!307.entry Process OverviewBy default, Microsoft Office Project Professional 2007 creates a project workspace site on Windows SharePoint Services 3.0 when it publishes a project. When a sub-project creates a workspace, the user has the option of also creating the project workspace as a sub-site of the programme. This creates a hierarchy of sites as shown in Figure 1, where Programme1 has two sub projects (A & B), and Programme2 has two sub projects (C & D).
Figure 1 - Programme and PRoject Workspace relationships If Project C is moved between programmes (due to reorganisation or setup issues) then the WSS site by default not moved. The following steps show how to move the WSS site. The example will show Project C moving to be part of Programme1 (Figure 2).
Figure 2 - Project C has become part of Programme1 In order to move the Project C sub-site to sit beside Projects A & B it is necessary to perform the following steps. 1. Export the original site to a file 2. Create a new site as a placeholder for the migrated site 3. Import the original site to the new placeholder site 4. Change the site address to reflect the new site in the Manage SharePoint Sites page 5. Delete the original site Export the original site to a fileOn the Project server, open a command window and navigate to the following location C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Type in the following command stsadm –o export –url <url> -filename <filename> The <url> is the url of the site that you wish to export and the filename is the output file. When the command has finished there should be a file called <filename>.cmp in the directory. Create a new site as a placeholderNavigate to the programme workspace where the new project is to be located, and create a new sub-site from the site actions tab. The site that you create must be a Project Workspace, and for ease, the URL name should match the original URL. Finally check the radio button so that the site is not displayed in the quick launch area.
Figure 3 - Create the new placeholder site Verify that the new site has been successfully created by accessing it.
Figure 4 - Verify The new site is created – Note the Breadcrumb showing Programme1
Figure 5 - The three subsites now show under the Programme1 workspace Import the original site into the new siteOnce the new site has been created, it is time to import the exported data from the original site. This is a similar process to the original export. On the Project server open a command window and navigate to the following location C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN Type in the following command stsadm –o import –url <url> -filename <filename> The <url> is the url of the site that you wish to import and the filename is the input file. When the command has finished, refresh the new project workspace site and check that the new content exists.
Figure 6 - Note the imported content on the new site Change the site address to reflect the new site in the Manage SharePoint Sites pageIn order to link the new site to the project, it is necessary to change the site address. In PWA, navigate to Server Settings | Project Workspaces. Select the relevant workspace and click on Edit Site Address. Modify the address so that it points to the new Project Workspace within the correct programme.
Figure 7 - Modify the site address to reflect the new site Once the site address has been modified, click on Synchronise to update the permissions on the new site. Delete the original siteThe original site still exists and so it needs to be deleted in order to remove it from the original programme. Navigate to the site, and within Site Actions | Site Settings and then Delete this site. Caution, ensure that you are deleting the right sub-site, and not the programme site.
|
|
|||||||||||||
|
|
Profile
Blog
Lists
Friends
