Microsoft Support Lifecycle

I had a query from a customer regarding MS Office software support lifecycle. Below is some info from Microsoft that might be interesting.

Microsoft provides support on the current service pack, and in some cases the immediately preceding service pack, for the products listed below. See the Lifecycle Support Policy FAQ for details on the Service Pack Support Policy. As a convenience to you, Microsoft is providing a list of the currently supported service packs: Supported Service Pack List. If you have any questions regarding support for a product, please contact your Microsoft representative. If you need technical support, visit the Contact Microsoft Web site.

(click picture to enlarge)

Microsoft Support Lifecycle

Project and Workspace Archiving & Restore – Cool custom tools!!

Over the past couple of days we discussed how to Archive and Restore projects using OOB features, best practices and considerations for associated Workspaces.

The manual approach for archiving and restore may work for smaller deployments or instances with small number of ‘live’ projects. But, if we have a medium to large deployment or we are in a situation where we simply have very many ‘live’ projects we may need to start thinking about automating some of the processes to streamline our operations. Archiving your projects and workspaces will not only help with the system performance but more importantly, your SQL database backups and disaster recovery where you might be mirroring or log shipping to another site. Whatever approach you take whether manual or automatic…keep your system ‘lean and mean’.

Here is some info on an automated ‘Project and Workspace Archive & Restore’ custom utility for EPM2007 & SharePoint Workspace that I worked on earlier. The key features are;
    Archive Projects with and without workspaces. The associated workspaces can be configured to be automatically migrated to another site collection either within the same App Pool/Content DB or to a completely different farm!! Note: You can even leave the workspace in its original location and the restore tool will automatically figure out where the associated workspace is at the time of restore and re-link it automatically.

(click picture to enlarge)

    The above figure should give you an idea of the flexibility when it comes designing your archiving and restore strategy!! It is totally flexible.

    Archiving Projects based on custom attributes and whether the project is INDEED complete. How often do we see PMs simply closing a project with remaining work and duration? The archiving tool will enforce that policy. See attached fig below.

(click picture to enlarge)

    Restore Projects with and without associated Workspaces automatically including re-linking;

• Firstly, the associated workspace will be restored.
• Next, the project will be be restored from the archive and automatically published.
• Finally, the project will be automatically linked to the associated restored workspace. How cool is that!! 

(click picture to enlarge)

We can also add in capability for user controlled archiving based on Project Attribute.

If this has wet your appetite then I suggest you contact us to see how we can help you with a solution that will work within your organization.

Hope this series of archive and restore posts has been useful. Your feedback is always welcome (pj@projectsolution.co.uk ). Let me know what you think.

Author: PJ Mistry

EPM2007 Project Restore– Recommended Steps (OOB)

You have been diligently archiving projects following your organisational best practices. There will come a time when you will have to restore a particular project from the Archive DB, perhaps it was archived prematurely or there is an extension to the project that was earlier completed…whatever the reason might be, expect this. The steps to restore a project are very simple if you do NOT use associated SharePoint Workspaces. However, if you do, then there are some considerations…..

What steps should I follow?

1. Firstly, review the List of Archived Project (refer to best practices in earlier post regarding OOB Archiving Projects)
2. Next, restore Project from the Archive Db (via Server Settings > Administrative Restore). Remember that the Project will be restored to the Draft DB. At this point, it will not exist in the Publish or Reporting DBs.
3. Set the Project ‘Workspace Provisioning Settings’ to MANUAL (via Server Settings). Note: If you don’t do this, you will not be able to undertake steps 4 & 5 below. That is unless, you choose to create a new ‘dummy’ workspace first. But then, you have the hassle of deleting this ‘dummy’ site after remapping the correct workspace to the project.
4. Open the restored Project via Project Professional and Publish to the server.
5. Finally, for each project restored, add/map the workspace URL via Server Settings > Project Workspaces. Hopefully you will kept a record of the URLs and project names in the Archive LIST.

(click picture to enlarge)

And before you ask, yes! you need to do this manually for each project being restored.

I will be discussing the the custom Archiving Tools in the following post. For smaller deployments we could manage doing this manually, but for medium – larger deployments this may become a challenge.

Hope this helps for now!

EPM2007 Project Archiving – Recommended Steps (OOB) - Part II

This with ref to my earlier post regarding OOB Project Archiving.

Some of you wanted to you know what to do about Archiving associated SharePoint Project Workspaces. Well, there is no OOB automated solution for this. When an EPM project is Archived, the SharePoint Workspace will remain as is (unless selected to delete), i.e. the two are ‘decoupled’ when the Project is Archived. If you want to also move the workspace from the ‘live’ site collection to another (say Archive Site Collection), then you will need to do this manually by using the appropriate SharePoint STSADM tools.

If you are moving the Workspace then remember to jot down the ‘new’ URL in the list of projects archived. This will assist you when you restore the project and re-link to the workspace. I will cover the process and best practices of restoring projects in the following post.

EPM2007 Project Archiving – Recommended Steps (OOB)

You have been using EPM2007 for a while and have very many projects in the system. It now time to start thinking about archiving your projects. If you don't archive your completed projects on the regular basis then, over time time, the number of projects in the Draft and Published DBs will build up. This may start adversely impacting the system performance.  It is important to have a ‘rigid’ business process in place for archiving projects. Hope this helps if you are in the process of setting this up. If on the other hand, you have one in place, then hope this helps in strengthening your existing processes.

The out-of-box (OOB) Archiving process, is basically ensuring that your projects are copied/retained in the Archive DB and removed from Draft/Published DB.

You may wish to record the name of the Projects being archived with the URLs in a custom List within PWA or an admin SharePoint site. See example below. This is so that users can still access the project workspace(s) after the project schedule has been removed from the draft and published DB.

(click picture to enlarge)

Here are some recommended EPM Business Processes for archiving projects (without using automated EPM partner Add-on/enhancements). I will cover the custom automated solution (for archiving & restoring project schedules and associated workspaces) later in the following post.

(click picture to enlarge)

The actions undertaken by Project Managers and Administrators are indentified below.

    Set Project Attribute [PM]

- PMs to set appropriate project attribute e.g. Archive. Note: Appropriate Project Centre view(s) can be created to show projects that are ready for archiving.  Include fields e.g. Owner, % Work Complete, Project Status, Checked out, Check out by, Last Published etc. This view will be used by system administrators to assist with the archiving process.

    Ensure project tasks and assignment are 100% complete [PM]

- Set remaining work and durations as ‘0’ for tasks and assignments that are deemed to be completed but have not yet been marked as complete.

    Set task field ‘Publish’ value to No [PM]

For all tasks that are marked as complete, set Publish flag as No. (click picture to enlarge) This will ensure that completed tasks/assignments do not appears in users MY TASK and MY TIMESHEETs if the archived project is ever restored. Refer to previous post regarding this.

    Save and Publish project [PM]

    Save Enterprise project as mpp file [PM]

I would recommend that Project Managers include this step as part of their project closure process. Save Enterprise project as mpp file within the associated project workspace along with other documentation.

    Confirm projects are archived [Admin]

- Within Manage Queues, review any errors than may have occurred during automatic backup overnight. - You may wish to also confirm that the project(s) have been archived by checking the projects available to restore i.e. PWA > Server Settings > Administrative Restore.

    Record project name and associated project workspace URL in the Archive projects list previous setup [Admin]

(click picture to enlarge)

    Finally, delete Project from the Draft and Published DBs [Admin]   

Take due care when selecting the projects to delete. Do NOT select the option to delete the associated workspaces.

The above archiving process is not to be confused with SharePoint Farm or SQL Database backup for the purpose of disaster recovery.

Note: This posting is provided "AS IS" with no warranties, and confers no rights.

Project Server 2007 & MOSS – Issue with linking Risk/Issues with Tasks! Contd...

Here is an update to my earlier post regarding this issue....
I have just been doing some further testing with the MS support engineer. It looks like the issue affects only the farm/web administrators. Other 'mortal' EPM users are not affected. My testing confirms this. Phew!!

New EPM2007 Deployment with SP2 – Issues with Services not starting

If you setup a new deployment and upgrade to SP2, you may come across an warning message indicating that the services have not started.

If you then, try to launch SharePoint CA you get an error message stating that the page cannot be found. On further investigation, you may uncover the fact that the SharePoint Administration Service has failed to start.

Here are some steps that will help resolve the issue:

1. In registry editor add/modify the following values on "HKLM\System\CurrentControlSet\Control":

a) ServicesPipeTimeout DWORD 60000 (decimal).

b) WaitToKillServiceTimeout changed to "120000".

2. Reboot the server

Here is what your changes should look like before and after….

Before Changing the Registry

(click picture to enlarge)

After Changing the Registry

(click picture to enlarge)
Not: This posting is provided "AS IS" with no warranties, and confers no rights. Ensure that you have taken appropriate backups of your registry prior to making any changes.