M
Mark
Project Server 2003
Disconnected Domain Setup
Displaimer: The security issues may exist and intengration with Share Point
may not be as seamless as before but it can work. There may be some
functionality with Share Point that may not function correctly. These are
instructions are intended for the use of a Project Server that is on a
domain but the client systems are not part of that domain and the user names
on the user computers exist in the domain already but contain different
passwords. It also cuts back on the work to duplicate the user accounts on
the project server.
* After project server has been installed
1. Create a Project Server user account for Project Professional 2003
clients to use to upload project files to the Project Server 2003.
2. Create a new Virtual Directory in IIS for Project Professional 2003
clients to usse when publishing new project files. Example used "psHack"
2.1. Copy files from Project Web Server to the new Virtual Directory
"psHack"
- Project Web Server files are found under "C:\Program Files\Microsoft
Office Project Server 2003\IIS Virtual Root"
3. Modify the IIS Virtual Directory properties
- Set application pool to "MSP2003AppPool"
- Directory/Configuration
1. Add
Executable Path: C:\Program Files\Common
Files\MSSOAP\BINARIES\SOAPIS30.DLL
Extension: .wsdl
Verb Limit To: GET,POST
Uncheck "Verify that file exists"
2. Click OK, Click OK
- Documents Tab
- Remove all default content pages
- Add LGNINT.ASP to content pages
- Properties complete click [Ok]
4. Modify Properties of the sub folder ISAPI
- change Execute Permissions to "Scripts and Executables"
5. Setup "psHack" to execute .dll file.
- Web Service Extensions
- Microsoft Office Project Server 2003 ISAPI properties
- Click [Add]
- Path: "C:\Inetpub\wwwroot\psHack\ISAPI\PJDBCOMM.DLL" Or the path to the
ISAPI\PJDBCOMM.DLL in your Virtual directory
5. Registry modifiactions
- Export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS
Project\WebClient Server\ProjectServer
- Modify the exported registry file to contain the name of the Virtual
Directory in IIS for the Project Professional Clients "psHack" in all
locations where the path
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS Project\WebClient
Server\ProjectServer exits.
- Save changes
- Merge the registry file.
6. Test web site.
- Go to http://yourServer/psHack and log in using a Project Server account.
- If the server fails to work use the hints below to track down the error.
7. Setup Project Profession 2003 Client
- Set the project server to be http://yourserver/psHack
- user is a Project Server account
- Test.
Hints:
* If you have trouble check the IIS log for file errors and fix
accordingly.
* Use a web browser to test regularly.
* Check Event Log for any errors.
Disconnected Domain Setup
Displaimer: The security issues may exist and intengration with Share Point
may not be as seamless as before but it can work. There may be some
functionality with Share Point that may not function correctly. These are
instructions are intended for the use of a Project Server that is on a
domain but the client systems are not part of that domain and the user names
on the user computers exist in the domain already but contain different
passwords. It also cuts back on the work to duplicate the user accounts on
the project server.
* After project server has been installed
1. Create a Project Server user account for Project Professional 2003
clients to use to upload project files to the Project Server 2003.
2. Create a new Virtual Directory in IIS for Project Professional 2003
clients to usse when publishing new project files. Example used "psHack"
2.1. Copy files from Project Web Server to the new Virtual Directory
"psHack"
- Project Web Server files are found under "C:\Program Files\Microsoft
Office Project Server 2003\IIS Virtual Root"
3. Modify the IIS Virtual Directory properties
- Set application pool to "MSP2003AppPool"
- Directory/Configuration
1. Add
Executable Path: C:\Program Files\Common
Files\MSSOAP\BINARIES\SOAPIS30.DLL
Extension: .wsdl
Verb Limit To: GET,POST
Uncheck "Verify that file exists"
2. Click OK, Click OK
- Documents Tab
- Remove all default content pages
- Add LGNINT.ASP to content pages
- Properties complete click [Ok]
4. Modify Properties of the sub folder ISAPI
- change Execute Permissions to "Scripts and Executables"
5. Setup "psHack" to execute .dll file.
- Web Service Extensions
- Microsoft Office Project Server 2003 ISAPI properties
- Click [Add]
- Path: "C:\Inetpub\wwwroot\psHack\ISAPI\PJDBCOMM.DLL" Or the path to the
ISAPI\PJDBCOMM.DLL in your Virtual directory
5. Registry modifiactions
- Export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS
Project\WebClient Server\ProjectServer
- Modify the exported registry file to contain the name of the Virtual
Directory in IIS for the Project Professional Clients "psHack" in all
locations where the path
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\MS Project\WebClient
Server\ProjectServer exits.
- Save changes
- Merge the registry file.
6. Test web site.
- Go to http://yourServer/psHack and log in using a Project Server account.
- If the server fails to work use the hints below to track down the error.
7. Setup Project Profession 2003 Client
- Set the project server to be http://yourserver/psHack
- user is a Project Server account
- Test.
Hints:
* If you have trouble check the IIS log for file errors and fix
accordingly.
* Use a web browser to test regularly.
* Check Event Log for any errors.