Hi everyone, Phil Smail from the Project Product Group here. Just wanted to announce the news that I know a lot of you out there have been waiting for. The Project Resource Kit for Project 2007 has released!! It’s available for x86 and x64 in English only
The PRK consists of the following tools:
Full documentation on the tools is expected shortly. In the meantime try them out and feel free to post comments
Hello, I just wanted to point everyone to our other team blog: http://blogs.msdn.com/project/archive/2008/01/25/project-2007-project-resource-kit.aspx
Hello, I just wanted to point everyone to our other team blog: http://blogs.msdn.com/project/archive
I have been playing with Playbooks, and it is going to solve a lot of longstanding migration issues for us. However, I get the following error trying to backup the server security settings:
ERROR: Could not load file or assembly 'Microsoft.Office.Project.Server.Library, Version=126.96.36.199, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. The system cannot find the file specified.
The "Portfolio Analyzer Views Migration" utility works well, but the database pick list is so narrow I couldn't tell what I was choosing until I got to the summary screen. Also, view names can be very long and it's nice to see their current database setting which is only shown at the end of the view name in the Select Views screen.
Any plans to create a utility to migrate views from one instance of Project Server to another?! That would be super handy.
If tried out the Playbooks, but it seems it doesn't transfer all client global settings. I created a fresh instance and restored a configuration, but then all the client views/tables/filters/groupings were missing. Only the macros had been transferred.
So it runs pretty well, but still is not complete.
Also a nice feature for further development would be the selection of single items from item groups to restore, e.g. Restore only lookup table "xyz"
I downloaded the resource kit and I installed it on my app server. I'm able to use the effective rights feature but every time I want to use the Playbook it keeps asking me for correct URL, user name and password. I see there is a config file but I do not the format...Please help as I need to copy production data to a development server.
I Tried out the Playbooks with a customized install. Enterprise Global settings (client views, tables, etc) were missing. Enterprise custom fields with lookup, PWA views and settings were restored correctly. But enterprise custom fields with formula were absolute wrong (Mixed Enterpise Custom field names in the formula etc.)
Server settings and PWA views migration works great.
But no Project Professional views will be migrated !
You'll need a copy of Microsoft.Office.Project.Server.Library in the same directory as the PRK tools. It ships in the Project SDK
Thanks for the feedback on the tool
We do have a tool to migrate views from one instance to another, it's called Playbooks and it ships in the PRK!
To cesar cruz:
Having to enter the username/password when running playbooks should prevent you from migrating data from production to environment
The formula custom fields issue is known and we are looking into how we will resolve that. No ETA unfortunately
Is there any plan to be able to backup/restore the following?
These unfortunately are probably the two of the biggest things that we would like to use the tool for.
I downloaded the tools and tried beginning with the view effective rights because I currently have an issue where this could be very handy. I don't seem to be able to run the utility. I tried on my workstation & when that didn't work, I tried to run it directly from the application server. This netted better results, but with no database server information, it showed that it was connecting. When I added the database server name, it said 'disconnected' and it didn't appear I could get it to try again. Any ideas?
Thanks, R Halbach
I have been trying to get the "View Effective Rights" tool working and this had been failing.
The Technet site that describes this tool (http://technet.microsoft.com/en-us/library/cc197528.aspx) states that read access into the _Published database is required. However, after much gnashing of teeth we got the tool working by granting dbo rights.
I would rather not have the people using this tool having dbo access. Is there any known work around for this? Has anyone else had similar issues?
We are using SQL Server 2005 SP1.