I’ve posted similar information before, but my colleague Lakshmana Rao (Laksh) has come up with a great document on the steps required when you want to move Project Server 2007 between domains. As Laksh points out at the end – please make sure you test this process in a non-production environment first – Hyper-V is perfect for these kind of tests. On with the document…
How to Move Project Server 2007 from one domain to another:
Considerations in this Article:
1. In this setup, the Project Server 2007 Farm has two servers (One Project Server 2007 SP2 Server box and one SQL Server 2005 SP3 Server box.) For multiple servers set up, please see the Note at the end of this article.
2. Current domain name is APAC and new domain name is NORTHAMERICA.
3. In the current set up, user account used for installing Project Server 2007 and as service account where ever is required is APAC\PsvrSrvcAcct
Prior to changing the Servers to the New Domain:
1. In the new domain, ensure that you have same account IDs and names as that of the domain account IDs and names in Project Server and the service accounts used for Project Server 2007.
Otherwise, after migration; we experience issues with user mappings and unknown issues related to resource assignments/ work/Actual work etc.
2. Take Full Farm back up from SharePoint Central Admin, Operations, Perform a back up. (For more details ,please refer to “Back up and restore the Project Server 2007 farm” at http://technet.microsoft.com/en-us/library/dd207295.aspx
3. Create a user in PWA using the Local Administrator ID or any local User and add to Project Server Administrators group.
For example, if Application Server host name is PSVRPROD, create a user (PSVRPROD\Administrator) in PWA, Server Settings, Manage Users, New User and assign to Administrator group. (After domain migration, we use this account to login to PWA and perform administrative tasks).
4. Stop the WWW service in Project Server.
5. In SQL Server 2005, note the permissions of Service Accounts used on the SharePoint and Project Server databases. (Note the Server roles and User Mappings of the Service Accounts)
Steps to Move the Servers to New Domain:
Moving SQL Server 2005 box:
1. Join the SQL Server to the new domain.
2. Restart the Server.
3. Login to the server with Admin Privileges and add the respective service accounts to the Local Admin group.
In this scenario, I have added NORTHAMERICA\PsvrSrvcAcct. (Before domain change, APAC\PsvrSrvcAcct was present in Admin group.)
4. Open Services.msc and ensure that the MS SQL Server service is running. You may need to change the ‘Log on’ Account name if the service is using a domain account. Specify the correct service account and start the service.
5. Connect to the SQL Server using SQL Server Management Studio.
6. Expand the Security. Click on Logins.
7. Create Service accounts used in Project Server and provide proper permissions to the SharePoint and Project Server databases. (You need to refer to notes in step 5 in section “Prior to changing the Servers to the New Domain:” and give the same permissions ( Server roles and User mappings to the new service accounts)
In this scenario, I have created NORTHAMERICA\PsvrSrvcAcct in SQL Server and provided the same server roles and user mappings as that of APAC\ PsvrSrvcAcct
8. In MSP_RESOURCES table of Published database, change the domain name of the users.
Use the following query
SET WRES_ACCOUNT = REPLACE(LTRIM(WRES_ACCOUNT), '<Current Domain Name>', '<New Domain Name>');
In this scenario, I used,
SET WRES_ACCOUNT = REPLACE (LTRIM(WRES_ACCOUNT), 'APAC', 'NORTHAMERICA');
Moving Project Server 2007 box:
1. Join the Project Server to the new domain.
3. Login as local Administrator and add the respective service accounts to the Local Admin group.
4. Ensure that you are able to connect to SQL Server box. (You can use UDL connection test).
5. Follow the KB article, http://support.microsoft.com/kb/934838 and change the farm service accounts and passwords.
6. Ensure that the Project Server Queue, Event, SharePoint Timer services are using the new domain service account. These should have been set by the actions in step 5 so should not need changing manually (worth noting just in case they didn't do step 5 right and think manually changing will put things right),
7. Open IIS Manager and ensure that all the service accounts are changed to the new domain service accounts. If not change them and restart the IIS.
8. Login to SharePoint Central Admin site.
9. Click on Operations, Service Accounts.
10. Select Web Application pool. For Web Service, select “Windows SharePoint Services Web Application”.
11. For each Web Application pool, verify whether the user name is correct. If not update them and restart IIS.
In this scenario, I have checked whether it is NORTHAMERICA\PsvrSrvcAcct.
(Steps 8 -11 are to make sure that the SharePoint reflects the changes)
12. Log in to PWA using local Administrator ID ( created in step 3 of section “Prior to changing the Servers to the New Domain:” )
13. To initiate “User Synchronization for Project Web Access App Root Site and Project WSS Workspaces”, create a new Category (say “TestSync”) from on Server Settings, Manage Groups add users to this group ( do not add the currently logged in user ) and click save. Again, revert back the changes. Delete the newly created category.
14. Once, “User Synchronization for Project Web Access App Root Site and Project WSS Workspaces” is succeeded, synchronize the Project Workspaces from Server Settings, Project Workspaces.
15. Test the server by publishing a new project and existing project as well.
16. Ask users to access the PWA and Project workspaces and test.
Note: If that farm has multiple Application Servers and WFEs, you have to detach all the servers from the farm, except the server that host Central Admin site. Follow the above steps. The, move other servers to new domain and then connect to the farm one after another.
You can also use PSI functions “SynchronizeMembershipForPwaAppRootSite ()” to update PWA WSS Root Site information and “QueueSynchronizeMembershipForWssSite “to update each WSS Workspace. This requires writing a custom code.
As with any major changes, please test in your own environment to ensure these steps work for you before moving a production system.
Thanks again Laksh!
I posted a short while ago about this topic, but wanted to make clear how you can continue working with time phased tracking for normal projects if you have got used to it since the IU. Brief re-introduction to the problem for new readers – we introduced a time-phased grid for time entry with the Infrastructure Update, but this opened a back door for time phased entry where the project manager was trying to enforce a different tracking method. SP2 closed this back door. So if you have been enjoying this loophole between IU and SP2 then you can continue working in this way with your projects (I’ll come to activity plans and proposals later ***Update*** - the activity plan and proposals behavior is reverted in June 2009 CU http://blogs.msdn.com/brismith/archive/2009/07/16/project-server-2007-office-system-june-2009-cumulative-update-is-now-available.aspx) by the correct application of settings in PWA, Server Settings, Task Settings and Display – and also Project Professional, Tools, Options, Collaborate. First the PWA settings.
If you only want to have time phased task entry for all projects then you should also check the “Force” option. If you want to have time phased for some projects then you can select the default method here as required, and not set the “force” option – and then in Project Professional you can set the option on a project by project basis, on the Collaborate tab under Tools, Options.
If you have set the “force” option on PWA then your Collaborate tab will show these options grayed out – and you will not be able to enter time phased work if either the Percent of work complete or Actual work done and work remaining are the Tracking Method options being “forced”. In the following case we are forcing Hours of work done per period – so time phased entry will be possible.
Also if you have changed from either the Percent of work complete or Actual work done and work remaining tracking methods to allow time phased entry again, you will need to re-publish all active projects to re-enable the time phased entry. You might also need to make a project change to convince Project Pro that there is data that does need to be published.
I mentioned Activity Plans and Proposals earlier – and there is no way to change settings currently to get back to the time phased entry that many customers have enjoyed between IU and SP2 – but we have heard you and are hoping to revert the change as it applies to these light weight projects. More news soon on this one. ***Update*** - the activity plan and proposals behavior is reverted in June 2009 CU http://blogs.msdn.com/brismith/archive/2009/07/16/project-server-2007-office-system-june-2009-cumulative-update-is-now-available.aspx
Thanks to Gary and Eric for the prod to get another posting out to add some clarity to these changes and potential workarounds.
I haven’t posted for a little while – it has been really busy here – but fortunately for you the sort of busy that doesn’t need blogging about! Do you really hate it when people say in their blogs “I’m working on some really cool stuff but I can’t blog about it”? So do I – so I’m not going to say that…
Just in case any of these recent postings passed you by:
Jan did an excellent webcast on the internal workings of the Active Cache in Project Professional and the way it links to server – with some great demonstrations using Fiddler to see what traffic was going on. Catch the recording on demand here. If you didn’t attend you will need to register, then you will be given the option to watch online or download the recording. I prefer downloading the wmv version as then you can use Windows Media Player and use the option to watch at a faster speed. Doesn’t always work well if the presenter speaks quickly – but a great time saver as you can watch a one hour presentation in 40 minutes! Another tip – if you download the high fidelity Live Meeting version the demonstrations are in the res\AppSharing folder as individual wmv files.
Great Gartner Magic Quadrant placement for both Microsoft Dynamics AX and Project Server/Portfolio Server. Links go to Christophe’s summary.
And finally under the “boys and their toys” section, Christophe did an excellent review of running demonstration Hyper-V images on a Solid State Disk. I want one!
Almost forgot – I didn’t do a Bing posting when it launched but I do use it and am very impressed. Worth setting as your home page just for the daily photos! And I’m already seeing more traffic to my site from Bing than I used to get from Live so others are finding it useful too. Just need to get Bing to put me a bit higher than all those other Brian Smith’s…
The KB article in now live at http://support.microsoft.com/kb/971620 and localized versions will be following along. One thing to mention is that if you have multiple SKU’s installed and you try and re-license you may get a message saying your key is not valid. This can happen if for instance you try and use a Project Server 2007 key and you have both Microsoft Office SharePoint Server 2007 and Project Server 2007 installed. The key is not really invalid – just not the key the server is expecting. The Q&A in the KB addresses this:
Q: When I try to follow the steps in the "Resolution" section, I am notified that my product key is not valid. A: If multiple SKUs are installed, you have to provide the product key for the most inclusive product. Use the product key from the highest-listed product in the following ordered list: Microsoft Office SharePoint Server 2007 Search Server 2008, Search Server 2008 Express, or Microsoft Office SharePoint Server 2007 for Search Microsoft Office Project Server 2007 Windows SharePoint Services 3.0 is not affected.
Q: When I try to follow the steps in the "Resolution" section, I am notified that my product key is not valid. A: If multiple SKUs are installed, you have to provide the product key for the most inclusive product. Use the product key from the highest-listed product in the following ordered list:
Windows SharePoint Services 3.0 is not affected.