PPM Tricks

In Project Server - PSI it should be very fast to assign a new value to a custom field with a lookuptable. However this usually takes a lot of time for me mainly because I never can remember extactly how the field should be updated. That is why i created this post to show how a custom field (assigned to a lookuptable) can be assigned a new value. The biggest issue is that I can't remember how the different entities are connected together. The binding between the project and the lookuptable values are shown in the picture below. There are a number of steps to assign a value to a custom field with a lookuptable.  - Read the project dataset  - Find the custom field; MD_PROP_UID and MD_LOOKUP_TABLE_UID  - Find the ProjectCustomFieldRow with the same MD_PROP_UID  - Find the LookupTable with the same MD_LOOKUP_TABLE_UID  - Find the LookuptableTreesRow with the LT_VALUE_TEXT you want to assign.  - Assign the LT_STRUCT_UID from the LookupTableTreesRow to the ProjectCustomFiel

Firewall port open list Every time I have to install a new instance of Project Server I forget which ports have to be open. The ports are divided into 3 lists, one list for the web front end servers, one list for the application server and one list for the SQL server. These ports are based on a 2013 installation of SharePoint/Project Server. the 2010 installation defer a little bit. Web Frontend Server When a range is specified all ports between the range must be opened.      Port(s)            Protocol         Bound Description -        80                    TCP                   In          http -        443                  TCP                   In          https/ssl -         25                    TCP                   In          SMTP for e-mail integration -         16500-16519       TCP                   In          Ports used by the search index component -        22233-22236     TCP                   In/Out   Ports required for the AppFabric Caching Service -

How to move web front end server in SharePoint When i install a new SharePoint farm i often make the mistake to run the configuration wizard on the application server first. this results in the Central Administration and all web applications to be hosted on the application server instead of the web front end server. follow this guide to solve the issue. The solution consists of 4 steps. 1. Unprovision the Central Admin from the application server 2. Provision the Central Admin to the web front end server 3. Update alternative access mappings And in more detail: 1. Unprovision the Central Admin from the application server Log in to application server and start the SharePoint Configuration wizard. Click Next/Yes and make sure you do not desconnect from the farm.    Click Yes to remove the Central Admin and web sites from the machine. If you do not see the above screen click "Advance Settings" on the summary page.   Run the wizard. 2. Provision