Project Server 2007 Version Finder

The table below maps each release of Microsoft Project Server 2007 to its version number and corresponding KB article number.   You can locate the latest version number for Microsoft Project Server, do the following:

In the Microsoft SQL Server Management Studio, run the following query. 

USE <PROJECTSERVERNAME>_Published

SELECT * FROM Versions

WHERE VersionId ='00000000-0000-0000-0000-000000000000'

ORDER BY Id DESC

In the query above, replace <PROJECTSERSVERNAME> with your naming schema.

Project Server Release Name	Project Server Version Number	KB Article
Initial Release	12.0.4518.1016
January 31 Hotfix Package	12.0.6300.5000	941426
April 3rd Hotfix Package	12.0.6309.5000	950816
April 22nd Hotfix Package	12.0.6312.5000	951169
April 29  Hotfix Package	12.0.6313.5000	952000
May 8th Hotfix Package	12.0.6314.5000	952289
June 2nd Hotfix Package	12.0.6316.5000	953136
June 9th Hotfix Package	12.0.6317.5000	953478
Service Pack 1	12.0.6218.1000	936134
Infrastructure Update	12.0.6318.5000	951297
August 2008 Cumulative Update	12.0.6327.5000	956061
October 2008 Cumulative Update	12.0.6331.5000	957696
December 2008 Cumulative Update	12.0.6335.5000	960313
February 2009 Cumulative Update	12.0.6341.5002	968271
Service Pack 2	12.0.6422.1000	953334
April 2009 Cumulative Update	12.0.6503.5000	968860
June 2009 Cumulative Update	12.0.6510.5003	971502
August 2009 Cumulative Update	12.0.6514.5000	973937

 

To locate the version number for Microsoft Office Project Standard 2007 or Microsoft Office Project Professional 2007, use one of the following methods:

Method 1

On the Windows desktop, click Start, and then click Control Panel.

In the Control Panel, click Programs, and then click Programs and Features.

If the Versions field is not displayed in the Programs and Features list, do the following:

Right click the field header for the Name field, and then click More.

In the Choose Details dialog box, click to enable Version, and then click OK.

In the Programs and Features list, scroll down to location Microsoft Office Project Professional or Microsoft Project Standard 2007.

Method 2

Start Microsoft Project.

In the Help menu, click About.

Project client Release Name	Project client Version Number	KB Article
Initial Release	4518.1016
January 28th Hotfix	6300.5000	941657
March 22nd Hotfix	6300.5000	950284
April 30th Hotfix	6312.5000	952067
May 8th Hotfix	6314.5000	952293
Service Pack 1	6215.1000	937154
Infrastructure Update	6318.5000	951547
August 2008 Cumulative Update	6327.5000	956060
October 2008 Cumulative Update	6331.5000	958138
December 2008 Cumulative Update	6334.5000	959643
February 2009 Cumulative Update	6341.5002	966308
Service Pack 2	6423.1000	953326
April 2009 Cumulative Update	6503.5000	969409
June 2009 Cumulative Update	6510.5000	971501
August 2009 Cumulative Update	6514.5000	973930

 
 

Removing MySite functionality from PWA

1. First, in order to follow these steps you will need administrator access to the SharePoint Central Administration site for your SharePoint installation.
   
2. Go to the Central Administration Web Page
   
3. Click on the link for Shared Services Administration
   
4. If you have more than one SSP, select the one that is running the My Sites functionality for your PWA instance.
   
5. Under "User Profiles and My Sites" click Personalization Services Permissions
   
6. Select the group you want remove the My Site/Links functionality from.  In most cases this will simply be NTAuthority\Authenticated Users
   
7. In the next screen you will see a list of checkboxes,
   
   1. To disable MySites uncheck "Create Personal Site"
      
   2. To disable MyLinks uncheck "Use Personal Features"
      

Migrating Monitoring Server data from a test environment

Migration of Monitoring Server from a test environment to a production environment is similar to the operation outlined in Backing up and restoring Monitoring Server databases.

Important:

Either Office SharePoint Server 2007 or Windows SharePoint Services must be installed in order to successfully install and use Monitoring Server. The terms Windows SharePoint Services and SharePoint Services are used collectively in PerformancePoint Server documentation to refer to Office SharePoint Server 2007 and Windows SharePoint Services 3.0.

Procedure

Install Monitoring Server on the target computer

• Before installing the Monitoring Server on the target computer, confirm that you have successfully completed the steps in Backing up and restoring Monitoring Server databases.
  
• Launch Monitoring Server Configuration Manager.
  
• Specify the imported database on the target instance of Microsoft SQL Server 2005 by clearing the Monitoring System Database check box in the configuration wizard. Click Next.
  
• Specify the name of the database you have exported.
  
• Using Notepad, update the Web.config file on the target computer to match the previous ConnectPerUser and CustomData settings on the source:
  
  • <appSettings>
    
  • <add Key="BPM.ServerConnectionPerUser" value="False" />
    
  • <add Key="BPM.UseASCustomData" value="False" />
    
• Use Dashboard Designer to export the existing dashboards to the Windows SharePoint Services server installation.
  

Where SharePoint’s Config database is located

Well, Here it is.  SharePoint actually stores the connection to the configuration database in the registry. 
HKLM\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB

Uninstalling Microsoft Office SharePoint Server 2007

There is a easy way to Perform "Uninstallation of MOSS" on a standalone/farm server. The only viable way of doing things in standalone is follow the order below; However, for Farm based MOSS installation there are few more steps to be followed, which can guarantee clean removal of the software.

Steps to remove MOSS from your System/Server.

1. Remove Server from Farm

In Central Admin, Operations tab, Server in farm -- Remove server.

A word of caution: Always remove the Database / SMTP Servers first before removing the SharePoint Farm as you would have less problems removing the DB from SQL later.

You'll probably get an error message after you click remove, since the server isn't able to render the page anymore.

2. Remove Databases

Content DB, Config, Search, SSP, Etc.

3. Remove Web Applications

Use the IIS Management Console, remove all web applications related to the MOSS site.

4. Rename the C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12 to 12_OLD

Now you can remove MOSS via add/remove programs.

-

Administering SQL Server 2005 Internal Database

Problem

Microsoft products such as Windows Server Update Services (WSUS) 3.0 and Windows Sharepoint Services (WSS) 3.0 ship with SQL Server 2005 Embedded Edition. Now called the Windows Internal Database, more and more system administrators charged with managing WSUS and WSS are faced with the challenge of managing these databases. Since most of these system administrators are not full-fledged DBAs, how do they manage the Windows Internal Database?

Solution

The Windows Internal Database is an embedded data service that can only be used by a handful of Windows Services. It is designed in such a way that you are not allowed to connect to and use this particular database service for non-Microsoft products. By default, installing either WSUS 3.0 or WSS 3.0 will create the databases on the C:\ partition and will cause administration issues such as insufficient disk space. It is quite confusing to manage this SQL Server instance as it does not appear as a SQL Server service nor are there management tools included with the products. The easiest way is to use SQL Server Management Studio Express. You can install a copy of SQL Server Management Studio Express on the server running your WSUS 3.0 or WSS 3.0. You then register this instance using Named Pipes as this is the only configuration for connectivity. Use this server name when you register this instance

\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

Once you've managed to register this instance in SQL Server Management Studio Express, you can now administer the WSUS 3.0 and WSS 3.0 databases like shrinking the database files or moving them to a different disk partition dedicated for them to avoid insufficient disk space issues.

If you prefer to use scripts to manage these databases, you can download and install the SQL Server 2005 Command Line Query Utility - sqlcmd . This tool will be installed, by default, on this directory

C:\Program Files\Microsoft SQL Server\90\Tools\binn

To connect to the database instance, you need to run the sqlcmd.exe utility, passing the instance name and your credentials

sqlcmd -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query –E

You can then run your administrative T-SQL scripts once connected to this database instance.

Considerations

While these are possible reasons to administer the Windows Internal Database, it is not recommended to do anything beyond performing backups, moving or shrinking the database files. Modifying database schema or database properties would break supportability of these products. Plus, any changes made to these databases can be overwritten by the products' service packs or cumulative updates.

Next Steps

• Install SQL Server Management Studio Express on your WSUS 3.0 and WSS 3.0 servers
  
• Take control of your WSUS 3.0 and WSS 3.0 databases
  

Finding SQL Server 2005 versions

How to determine which version of SQL Server 2005 is running

To determine which version of Microsoft SQL Server 2005 is running, connect to SQL Server 2005 by using SQL Server Management Studio, and then run the following Transact-SQL statement.

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

The following results are returned:

• The product version (for example, 9.00.1399.06)
  
• The product level (for example, RTM)
  
• The edition (for example, Enterprise Edition)
  

For example, the results resemble the following.

Collapse this tableExpand this table

9.00.1399.06

RTM

Enterprise Edition

The following table lists the Sqlservr.exe version number.

Collapse this tableExpand this table

Release	Sqlservr.exe
RTM	2005.90.1399
SQL Server 2005 Service Pack 1	2005.90.2047
SQL Server 2005 Service Pack 2	2005.90.3042
SQL Server 2005 Service Pack 3	2005.90.4035