By default, WSS3.0 automatically purges workflow history after 60 days. The purge doesn't technically delete the history but it deletes the association that ties the document to the workflow history. And it also deletes any tasks that were created by the workflow.
I have 1 workaround and 3 solutions:
Workaround:
============
If you will ok with Workflow history option then please use this systex after your site name for finding all the deleted workflows:
/lists/Workflow%20History/AllItems.aspx
Example:
===========
http://xyz.com/sites/abc/lists/Workflow%20History/AllItems.aspx
Solution:
========
1. Disable the Workflow Auto Cleanup timer job completely
2. We can include a specific xml tag in workflow feature.xml file that controls the number of days retained for the workflow history (max days = 9999)
3. Run a job nightly to force all the workflow history retention settings to a certain number of days (max days = 9999)
But it may be possible that youwill face some performance issues if you make these changes.
Thursday, May 14, 2009
Tuesday, May 12, 2009
Configure Sharepoint 3.0 on "Active Directory Account Creation Mode"
This document is intended to help those that need to configureSharepoint 3.0 on "Active Directory Account Creation Mode". It is basedon real experience but it may not guarantee success on all cases.
1. Initially Follow the procedure described on the following MicrosoftTechNet Article (Install Windows SharePoint Services 3.0 for a serverfarm environment)http://technet2.microsoft.com/windowsserver/WSS/en/library/700c3d60-f394-4ca9-a6d8-b597fc3c31b1033.mspx?mfr=true
2. Before running "SharePoint Products and Technologies ConfigurationWizard" Prepare the Domain Controller.3. Now it's necessary to follow part of the process described onSharepoint 2.0 Documentation.http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsc05.mspx?mfr=true<http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsc05.mspx?mfr=true>
- Create an organizational unit (OU) for the user accounts
- Delegate permissions to the organizational unit
- Stop there; these are theonly steps necessary!!!
4. Start "SharePoint Products and Technologies Configuration Wizard".Follow the Farm Installation instructionsa. When you arrive at: "Completing the Sharepoint Products andTechnologies Configuration Wizard", select Advanced.b. On Advanced Settings Page select "Enable Active Directory AccountCreation Mode" and enter the Domain name and the organizational UnitCreated before (Sharepoint_ou for example).
5. Now you can go back to the Server Farm installation documentand continue the configuration steps.
6. After creating a "New Sharepoint Application" remember to usethe command "iisreset /noforce" so that you leave your environment readyfor the next step.
7. Now you may click on the link "Create site Collection" and theresult should be an ERROR: "The Page cannot be displayed because yourserver's current configuration does not support it. To perform thistask, use the command line operations in Stsadmin.exe." and that is agood sign... Now you have to execute the following command:
C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\WEB SERVEREXTENSIONS\12\BIN>STSADM -O CREATESITE -URL HTTP://servername
- Substitute Servername, e-mail, WindowsDomain and WindowsAccountaccording with your implementation.
- It's important to notice that this command will effectively send ane-mail, so you should already have configured the SMTP Server on the"Operations/Outgoing E-mail Settings" Page.
8. That's it!!!! You should have a working Sharepoint instance on"Active Directory Creation Mode".
Issues with Survey in Sharepoint
Issue:
========
The number of total responses count is different than tabulated response.
Cause:
========
After further technical investigation, I found that when a user responds to a survey, it is necessary for him to click on Finish at the end of the survey to complete the response.
If a user does not click on Finish, the response is not completed, but the incomplete response is saved anyway:
The number of responses is updated in the view Overview of the survey
In addition, the response does not appear in the view Graphical Summary of the survey.
In the view All Responses of the survey, the response is visible only to the user who began to respond. Others users only see the completed responses.
Solution:
=========
Only the user who began to response can solve this issue. Other users (including users with "Full Control" permissions, the owners of the TeamPlace and even the administrators of the TeamPlace servers) cannot solve it as they can't show the incomplete responses.
This user has to go the view All Responses of the survey, to find the response that is not completed, and to select Edit Response in the drop-down menu.
Then the user has to complete the response and to click on Finish at the end of the survey.
This is a by design behavior.
========
The number of total responses count is different than tabulated response.
Cause:
========
After further technical investigation, I found that when a user responds to a survey, it is necessary for him to click on Finish at the end of the survey to complete the response.
If a user does not click on Finish, the response is not completed, but the incomplete response is saved anyway:
The number of responses is updated in the view Overview of the survey
In addition, the response does not appear in the view Graphical Summary of the survey.
In the view All Responses of the survey, the response is visible only to the user who began to respond. Others users only see the completed responses.
Solution:
=========
Only the user who began to response can solve this issue. Other users (including users with "Full Control" permissions, the owners of the TeamPlace and even the administrators of the TeamPlace servers) cannot solve it as they can't show the incomplete responses.
This user has to go the view All Responses of the survey, to find the response that is not completed, and to select Edit Response in the drop-down menu.
Then the user has to complete the response and to click on Finish at the end of the survey.
This is a by design behavior.
MOSS 2007 SP2 issues
After Microsoft releases Service Pack 2 for the WSS and MOSS (SharePoint 2007 SP2) I tried to update my Sharepoint environment to SP2.
There are no issues when you update clean environment, but for customized application there are few things you should be aware about.
Error 1:
=======
[SPDatabaseGbwSequence] [ERROR] Upgrade object too new (build version = 12.0.0.6341, schema version = 2.0.0.0). Current server (build version = 12.0.0.4518, schema version = 3.0.1.0).
When installed SP2 and run Configuration Wizard
This error tells you nothing what relates to the actual problem. You could think that you installed any hotfixes that changed your database schema or content database might be not in right state. I had the same thoughts but this didn't help at all.
The root of the problem lies in other side.
Cause:
======
Investigating this issue I found that free SharePoint template from Microsoft cause you such issue, especially GroupBoard. If you have this template installed - that's the problem, because it interacts with the database schema and doesn't allow SharePoint SP2 to be installed.
Solution:
========
Uninstall GroupBoard template
Install SharePoint SP2
Install GroupBoard template.
Error 2:
========
“Feature '20477d83-8bdb-414e-964b-080637f7d99b' is not installed in this farm, and can not be added to this scope.”
If you get an error during the psconfig phase and you find this entry in the update.log file
“Feature '20477d83-8bdb-414e-964b-080637f7d99b' is not installed in this farm, and can not be added to this scope.”
Cause:
========
A timer Job is missing.
Resolution:
===========
You need to install this feature to be able to proceed with the update.stsadm -o installfeature -name PublishingTimerJobs
There are no issues when you update clean environment, but for customized application there are few things you should be aware about.
Error 1:
=======
[SPDatabaseGbwSequence] [ERROR] Upgrade object too new (build version = 12.0.0.6341, schema version = 2.0.0.0). Current server (build version = 12.0.0.4518, schema version = 3.0.1.0).
When installed SP2 and run Configuration Wizard
This error tells you nothing what relates to the actual problem. You could think that you installed any hotfixes that changed your database schema or content database might be not in right state. I had the same thoughts but this didn't help at all.
The root of the problem lies in other side.
Cause:
======
Investigating this issue I found that free SharePoint template from Microsoft cause you such issue, especially GroupBoard. If you have this template installed - that's the problem, because it interacts with the database schema and doesn't allow SharePoint SP2 to be installed.
Solution:
========
Uninstall GroupBoard template
Install SharePoint SP2
Install GroupBoard template.
Error 2:
========
“Feature '20477d83-8bdb-414e-964b-080637f7d99b' is not installed in this farm, and can not be added to this scope.”
If you get an error during the psconfig phase and you find this entry in the update.log file
“Feature '20477d83-8bdb-414e-964b-080637f7d99b' is not installed in this farm, and can not be added to this scope.”
Cause:
========
A timer Job is missing.
Resolution:
===========
You need to install this feature to be able to proceed with the update.stsadm -o installfeature -name PublishingTimerJobs
Tuesday, April 28, 2009
Installation of Certificate Server on Windows Server 2003 enterprise
Here are some easy steps for Installation of Certificate Server on Windows Server 2003 enterprise
- Click Start, point to Control Panel, and then click Add or Remove Programs.
- In Add or Remove Programs, click Add/Remove Windows Components.
- In the Windows Components Wizard, under Components, select Certificate Services.
- Read the warning about domain membership, and then click yes.
- Click Next.
- On the CA Type page, click Enterprise root CA, and then click next.
- On the CA Identifying Information page, in the Common name for this CA box, type Server Name (CERT-CA1), and then click next.
- On the Certificate Database Settings page, accept the defaults in the Certificate database box and the Certificate database log box, and then click next.
- When prompted to stop Internet Information Services, click yes.
- When asked if you want to enable Active Server Pages (ASP), click yes.
- After the wizard completes the installation, click Finish.
Office 2003 documents Open in Read-Only Mode
If you click on an Office document in SharePoint to open it - it loads it in the relevant application, but in Read-Only mode. The way to open a document to edit - is to access the context menu and select "Edit in Microsoft Office Word. This is especially annoying when searching for documents, since the search results does not show the context menu and does not provide a link to the document library containing the document. So the only option is to load the document in Read Only mode but then to save it - the user needs to know which document library it belongs to and then manually navigate to it.
There is however a workaround as detailed in http://support.microsoft.com/?kbid=870853. It involves adding a new registry key on every desktop as follows:
1. Quit all Office 2003 programs that are running.
2. Click Start, click Run, type regedit in the Open box, and then click OK.
3. Locate and then right-click the following registry subkey: HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Internet
4. Point to New, and then click DWORD Value.
5. Type OpenDocumentsReadWriteWhileBrowsing, and then press ENTER.
6. Right-click OpenDocumentsReadWriteWhileBrowsing, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. On the File menu, click Exit to quit Registry Editor.
If you like, you can paste the following into a command box:
If you like, you can paste the following into a command box:
reg add HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\Internet /vOpenDocumentsReadWriteWhileBrowsing /t REG_DWORD /d 1 /f
SharePoint Content Database Tables
Here are some importent tables of SharePoint Content Database
- Features Table that holds information about all the activated features for each site collection or site.
- Sites Table that holds information about all the site collections for this content database.
- Webs Table that holds information about all the specific sites (webs) in each site collection.
- UserInfo Table that holds information about all the users for each site collection.
- Groups Table that holds information about all the SharePoint groups in each site collection.
- Roles Table that holds information about all the SharePoint roles (permission levels) for each site.
- AllLists Table that holds information about lists for each site.
- GroupMembership Table that holds information about all the SharePoint group members.
- AllUserData Table that holds information about all the list items for each list.
- AllDocs Table that holds information about all the documents (and all list items) for each document library and list.
- RoleAssignment Table that holds information about all the users or SharePoint groups that are assigned to roles.
- SchedSubscriptions Table that holds information about all the scheduled subscriptions (alerts) for each user.
- ImmedSubscriptions Table that holds information about all the immediate subscriptions (alerts) for each user.
Configuring Usage Analysis Processing using stsadm
I ran into a problem recently when attempting to enable and configure Usage Analysis Processing (UAP)using stsadm, I needed to do this as part of a fully scripted installation of MOSS 2007 that I was assisting a customer with. Looking at the stsadm documentation, the following commands are available:
stsadm -o setproperty
-propertyname usageprocessingenabled
-propertyvalue {Yes | No}
stsadm -o setproperty
-propertyname job-usage-analysis
-propertyvalue {Yes | No}
I then ran the following two commands to configure UAP:
stsadm -o setproperty -pn job-usage-analysis -pv "daily between 08:00 and 09:00" To configure the time that the process runs.
stsadm -o setproperty -pn usageprocessingenabled -pv "Yes” To enable Usage Analysis Processing.
However when I browsed to Central Administration – Operations – Usage analysis processing the following was displayed
If you look closely you can see that the time has been set correctly but it hasn’t enabled usage analysis processing. As you can see this is grayed out meaning that Enable logging must be selected before it can be enabled – but how do I enable logging? After much investigation I eventually found out (from a colleague- thanks Kirk) that the following stsadm can be used to enable this.
stsadm -o setproperty -pn loggingenabled -pv "Yes”To put this all together I need to run the commands in this order to achieve my objective:
• stsadm -o setproperty -pn loggingenabled -pv "Yes”
• stsadm -o setproperty -pn job-usage-analysis -pv "daily between 08:00 and 09:00"
• stsadm –o setproperty -pn usageprocessingenabled -pv "Yes”
stsadm -o setproperty
-propertyname usageprocessingenabled
-propertyvalue {Yes | No}
stsadm -o setproperty
-propertyname job-usage-analysis
-propertyvalue {Yes | No}
I then ran the following two commands to configure UAP:
stsadm -o setproperty -pn job-usage-analysis -pv "daily between 08:00 and 09:00" To configure the time that the process runs.
stsadm -o setproperty -pn usageprocessingenabled -pv "Yes” To enable Usage Analysis Processing.
However when I browsed to Central Administration – Operations – Usage analysis processing the following was displayed
If you look closely you can see that the time has been set correctly but it hasn’t enabled usage analysis processing. As you can see this is grayed out meaning that Enable logging must be selected before it can be enabled – but how do I enable logging? After much investigation I eventually found out (from a colleague- thanks Kirk) that the following stsadm can be used to enable this.
stsadm -o setproperty -pn loggingenabled -pv "Yes”To put this all together I need to run the commands in this order to achieve my objective:
• stsadm -o setproperty -pn loggingenabled -pv "Yes”
• stsadm -o setproperty -pn job-usage-analysis -pv "daily between 08:00 and 09:00"
• stsadm –o setproperty -pn usageprocessingenabled -pv "Yes”
Enterprise Content Management (ECM)
Hi All These are some good blogs and links for Enterprise Content Management
Blogs
==============
blogs.msdn.com/ecm/
blogs.msdn.com/ecm/archive/2006/06/09/624520.aspx
blogs.msdn.com/sharepoint/archive/2008/01/03/new-beta-extranet-collaboration-toolkit.aspx
blogs.msdn.com/.../30/announcing-the-first-release-of-the-microsoft-sharepoint-administration-toolkit.aspx
Sites
==============
office.microsoft.com/en-us/sharepointserver/HA101747881033.aspx
office.microsoft.com/en-us/sharepointserver/HA102063591033.aspx
msdn.microsoft.com/en-us/library/aa830818.aspx
YouTube
==============
www.youtube.com/watch?v=8zT4NsSSa6g
Other resources
===============
www.andrewconnell.com/blog/articles/MossWcmResources.aspx
www.microsoft.com/downloads/details.aspx?FamilyID=6D94E307-67D9-41AC-B2D6-0074D6286FA9
www.1stafftraining.com/b2b/outlines/1Staff_50003.pdf
Blogs
==============
blogs.msdn.com/ecm/
blogs.msdn.com/ecm/archive/2006/06/09/624520.aspx
blogs.msdn.com/sharepoint/archive/2008/01/03/new-beta-extranet-collaboration-toolkit.aspx
blogs.msdn.com/.../30/announcing-the-first-release-of-the-microsoft-sharepoint-administration-toolkit.aspx
Sites
==============
office.microsoft.com/en-us/sharepointserver/HA101747881033.aspx
office.microsoft.com/en-us/sharepointserver/HA102063591033.aspx
msdn.microsoft.com/en-us/library/aa830818.aspx
YouTube
==============
www.youtube.com/watch?v=8zT4NsSSa6g
Other resources
===============
www.andrewconnell.com/blog/articles/MossWcmResources.aspx
www.microsoft.com/downloads/details.aspx?FamilyID=6D94E307-67D9-41AC-B2D6-0074D6286FA9
www.1stafftraining.com/b2b/outlines/1Staff_50003.pdf
Monday, February 16, 2009
PRESCAN KB Articles
If you you are not able to run Prescan or receive errors in Prescan logs please follow these KB Articles. They will help you to resolve issue
Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.0 and SharePoint Portal Server 2003
http://support.microsoft.com/kb/918744
You receive an error message when you run the pre-upgrade scan tool (Prescan.exe) to scan Windows SharePoint Services 2.0 sites before you upgrade to Windows SharePoint Services 3.0
http://support.microsoft.com/kb/937291/en-us
Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.0 and SharePoint Portal Server 2003
http://support.microsoft.com/kb/918744/en-us
Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit"
http://support.microsoft.com/kb/923904/en-us
Problem: migrate frontend of wss2 to moss2007
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2605512&SiteID=1
Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.0 and SharePoint Portal Server 2003
http://support.microsoft.com/kb/918744
You receive an error message when you run the pre-upgrade scan tool (Prescan.exe) to scan Windows SharePoint Services 2.0 sites before you upgrade to Windows SharePoint Services 3.0
http://support.microsoft.com/kb/937291/en-us
Description of a new command-line operation that you can use to repair content databases in Windows SharePoint Services 2.0 and SharePoint Portal Server 2003
http://support.microsoft.com/kb/918744/en-us
Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit"
http://support.microsoft.com/kb/923904/en-us
Problem: migrate frontend of wss2 to moss2007
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2605512&SiteID=1
Connecting SQL SSEE to SQL Management Studio
If you are using SQL 2005 SSEE & wants to edit permission or take SQL backup
Actual place where the database is Stored.
C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data
You can See the databases in SQL by Downloading Microsoft SQL Server Management Studio Express from the below link
https://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
After you install this application Copy & paste
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
On the Authentication Window Under server name. & you will be able to See all the databases
Actual place where the database is Stored.
C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data
You can See the databases in SQL by Downloading Microsoft SQL Server Management Studio Express from the below link
https://www.microsoft.com/downloads/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
After you install this application Copy & paste
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
On the Authentication Window Under server name. & you will be able to See all the databases
Install Application Template(.WSP) in WSS 3.0 & MOSS 2007
Before install any application template, First you install Application Template Core
Windows SharePoint Services 3.0 Application Template: Application Template Core
Download URL: http://www.microsoft.com/downloads/details.aspx?familyid=C1039E13-94DA-4D7D-8CAE-3B96FA5A4045&displaylang=en
To Download All Templates
URL: http://www.microsoft.com/downloads/details.aspx?familyid=5807B5EF-57A1-47CB-8666-78C1363F127D&displaylang=en
Pull the core file, ApplicationTemplateCore.wsp, from the extracted distribution in C:\PROGRAM FILES \common files\microsoft shared\web server extensions\12\bin
Installing the core:
Go to C:\PROGRAM FILES\common files\microsoft shared\web server extensions\12\bin and run these 3 commands
1) stsadm -o addsolution -filename ApplicationTemplateCore.wsp
2) stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment
3) stsadm -o copyappbincontent
Removing the core:
1) stsadm -o retractsolution -name ApplicationTemplateCore.wsp
2) stsadm -o deletesolution -name ApplicationTemplateCore.wsp
To Install All WSP Files in one single Script, please create a .bat file (Install.bat) and paste these codes in that
for %%f in (*.wsp) do stsadm.exe -o addsolution -filename %%f
for %%f in (*.wsp) do stsadm.exe -o deploysolution -allowgacdeployment -immediate -name %%f
stsadm -o copyappbincontent
Save the batch file in C:\PROGRAM FILES\common files\microsoft shared\web server extensions\12\ and copy all .WSP file on the same location.
Then Run the Install.Bat file and enjoy :)
Windows SharePoint Services 3.0 Application Template: Application Template Core
Download URL: http://www.microsoft.com/downloads/details.aspx?familyid=C1039E13-94DA-4D7D-8CAE-3B96FA5A4045&displaylang=en
To Download All Templates
URL: http://www.microsoft.com/downloads/details.aspx?familyid=5807B5EF-57A1-47CB-8666-78C1363F127D&displaylang=en
Pull the core file, ApplicationTemplateCore.wsp, from the extracted distribution in C:\PROGRAM FILES \common files\microsoft shared\web server extensions\12\bin
Installing the core:
Go to C:\PROGRAM FILES\common files\microsoft shared\web server extensions\12\bin and run these 3 commands
1) stsadm -o addsolution -filename ApplicationTemplateCore.wsp
2) stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment
3) stsadm -o copyappbincontent
Removing the core:
1) stsadm -o retractsolution -name ApplicationTemplateCore.wsp
2) stsadm -o deletesolution -name ApplicationTemplateCore.wsp
To Install All WSP Files in one single Script, please create a .bat file (Install.bat) and paste these codes in that
for %%f in (*.wsp) do stsadm.exe -o addsolution -filename %%f
for %%f in (*.wsp) do stsadm.exe -o deploysolution -allowgacdeployment -immediate -name %%f
stsadm -o copyappbincontent
Save the batch file in C:\PROGRAM FILES\common files\microsoft shared\web server extensions\12\ and copy all .WSP file on the same location.
Then Run the Install.Bat file and enjoy :)
PSConfig.exe (Command Line operations) for Configuration
PSConfig.exe (Command Line operations) for Configuration
The PSConfig.exe command line tool is used to configure the product after setup has completed. The default location of the tool: c:\program files\common files\microsoft shared\web server extensions\12\bin.
To create a new server farm or connect to an existing server farm the following steps will need to be run in the following order:
1. Create the ConfigDB:
PSConfig.exe -cmd configdb -create -server -database
-dbuser -dbpassword
-user -password
-addomain -adorgunit
-admincontentdatabase
Note that if you wish to connect to an existing configuration database and join the server to an existing server farm you will need to perform the ConfigDB command with the -connect parameter
2. Install all HelpCollections
psconfig.exe -cmd helpcollections installall
3. Perform resource security enforcement
psconfig.exe -cmd secureresources
4. Register the services in the server farm
psconfig.exe -cmd services -install
Note that before you can provision we will need to start and configure the Search service via the STSADM.exe command (more information about STSADM.exe later on):
Start the Windows SharePoint Services Search:
stsadm -o spsearch -action start -farmserviceaccount Redmond\user -farmservicepassword MyPassword
Start the Office SharePoint Server Search service:
stsadm -o osearch -action start -role IndexQuery -farmserviceaccount Redmond\user -farmservicepassword MyPassword -farmcontactemail user@ms.com
psconfig.exe -cmd services –provision
5. Register all features
psconfig.exe -cmd installfeatures
6. Provision the SharePoint Central Administration Web application
psconfig.exe -cmd adminvs -provision -port -windowsauthprovider onlyusentlm
7. Install shared application data
psconfig.exe -cmd applicationcontent –install
The PSConfig.exe command line tool is used to configure the product after setup has completed. The default location of the tool: c:\program files\common files\microsoft shared\web server extensions\12\bin.
To create a new server farm or connect to an existing server farm the following steps will need to be run in the following order:
1. Create the ConfigDB:
PSConfig.exe -cmd configdb -create -server
-dbuser
-user
-addomain
-admincontentdatabase
Note that if you wish to connect to an existing configuration database and join the server to an existing server farm you will need to perform the ConfigDB command with the -connect parameter
2. Install all HelpCollections
psconfig.exe -cmd helpcollections installall
3. Perform resource security enforcement
psconfig.exe -cmd secureresources
4. Register the services in the server farm
psconfig.exe -cmd services -install
Note that before you can provision we will need to start and configure the Search service via the STSADM.exe command (more information about STSADM.exe later on):
Start the Windows SharePoint Services Search:
stsadm -o spsearch -action start -farmserviceaccount Redmond\user -farmservicepassword MyPassword
Start the Office SharePoint Server Search service:
stsadm -o osearch -action start -role IndexQuery -farmserviceaccount Redmond\user -farmservicepassword MyPassword -farmcontactemail user@ms.com
psconfig.exe -cmd services –provision
5. Register all features
psconfig.exe -cmd installfeatures
6. Provision the SharePoint Central Administration Web application
psconfig.exe -cmd adminvs -provision -port
7. Install shared application data
psconfig.exe -cmd applicationcontent –install
Wednesday, January 7, 2009
How to install SharePoint Server 2007
Pre-Install
There are several things that you must do before you even insert the SharePoint 2007 CD they are:
• Install Windows 2003 R2 with the latest service pack (2 at time of writing) and all of the latest Windows Updates.
NOTE: Please do not use NewSID to change the SID of the machine if you are using a copy of another VM, this breaks things in SharePoint. My advice is to build Windows from fresh or to use Sysprep if you are using a copy of a VM.
• Join your machine to a domain or create a domain by running DCPromo.exe from the Start > Run dialog.
• Install the .net frameworks v3.0 and v2.0 from Windows Update. You can also download the full redistributable packages if your server is not online.
• Install Windows 'Application Server' from Add/Remove Programs in Control Panel with default settings
• Prepare a service account in your active directory domain to use for all Sharepoint services.
NOTE: Do not use the main domain\administrator account. This causes a problem if ever you wish to install Project Server 2007 on the same machine.
• Give your service account local administrator rights and logon as this account throughout the entire installation process.
• Install SQL 2005 (and latest service pack) with typical settings.
• Assign your service account to the 'Security Administrators' and 'Database Creators' server roles in SQL server (You will need to use SQL Server Management Studio).
Base SharePoint Server Install
You are now ready to install SharePoint 2007 itself, follow these steps:
• Login as your service account
• Insert your CD (or attach your ISO image) and run setup.exe if it does not autorun.
NOTE: If you get an error about web service extensions here, ensure that 'ASP.net V2.0.50727' web service extension is allowed in IIS. If it is not in the list, perform a 'repair' on .net 3.0 framework using add/remove programs and then the web service extension will appear in the list. This is caused when IIS is installed after the .net framework
• Enter your CD key and accept the license agreement.
• Choose 'Advanced' on the installation type dialog.
NOTE: The definition of 'Advanced' means that you are using full SQL server (which may or may not be on the same machine). If you had selected 'Basic' then it would have installed the cut down version of SQL (MSDE).
• Select 'Complete' on the Server Type screen and click 'Install Now'. The setup will now commence and you'll get a blue progress bar.
• Once installed you will get a screen with a check box that reads "Run the SharePoint products and Technologies Wizard now". Ensure this is ticked and click 'Close'.
• After a short pause, you'll get a 'Welcome' screen. Click 'Next'.
• You will get a warning that the wizard is about to reset several services, click 'Yes'.
• You'll be asked about the farm configuration, select to 'No, I want to create a new server farm'.
• Provide the database server (your server name) and your account details (account in the domain\user format). Leave the database name as the default. Click 'Next'.
• Leave the authentication mode as 'NTLM', set a specific port number is desired (not required) and click 'Next'.
NOTE: In a production environment, you would most likely use Kerberos where possible (if your infrastructure supports it).
• You'll get a summary screen; click 'Next' to kick-off the process.
NOTE: If it fails here, it is most likely that you do not SQL setup correctly. Ensure your service account is in the right groups. Please also note that this section can take a very long time, especially step 2 (up to 45 minutes).
• You'll get a success screen at the end, click 'Finish'.
• The wizard will attempt to load the central administration window. You may need to login here, use your service account. You may also get prompted to add the site to your trusted sites; go ahead and do that.
NOTE: This authentication prompt is caused by the secure version of IE on Windows 2003 Server. You can turn if off by modifying the security settings in IE.
Services on Server Configuration
The first bit of configuration to do is set your server to host all services. You do not strictly have to enable all of these services, but I find it helps if you are using the machine to test / investigate functionality.
• When the Central Administration screen appears, go to 'Operations' tab, then 'Services on Server'.
• Start the 'Document Conversions Load Balancer Service'.
• Start the 'Document Conversions Launcher Service', you'll have to choose the 'Load Balancer Server'; there should only be one option. If there are no options, ensure that the 'Document Conversions Load Balancer Service' has been started.
• Start the 'Excel Calculation Services'.
• Start the 'Office SharePoint Servers Search' service, observing the following guidelines:
o Tick both Query and Indexing check boxes
o Specify a contact email address (this can be any address)
o Enter your service account in the 'Farm Search Service Account' section
o Accept all other defaults and click 'Start'
• Leave all remaining services in their default configuration
Web Application Setup
The next stage is to create the 3 web applications that will be required to host the basic set of sites for a typical deployment, these are:
• Shared Service Provider Administration Site (Recommended to be called 'SSPAdmin')
• My Site Host (Recommended to be called 'MySite')
• The Main Intranet (or 'Portal') Site (Recommended to be called 'Intranet')
It is much simpler if all of these sites are on port 80 in IIS; this means that you do not have to remember to enter the ports all of the time. However having all three sites on port 80 means that each needs their own Host Header (required by IIS to differentiate between sites on the same port). The simplest way to do this is to create new 'Host (A)' records in DNS for each of your three sites. These should point to the IP address of your server; to do this follows these steps:
• Open the DNS Management tool from Administration Tools on your domain controller
• Navigate to your DNS zone
• Create new 'Host (A)' record
• Enter the Host header (i.e. 'SSPAdmin', 'MySite' or 'Intranet') for the site and the IP address of your server
• Click 'Add Host' and repeat for each of the three sites
Now the DNS entries are configured, we can create the three web applications in SharePoint; follow these steps for all three of your web applications (i.e. 'SSPAdmin', 'MySite' or 'Intranet'):
• In Central Administration, go to the 'Application Management' tab
• Click 'Create or Extend Web Application' and then click 'Create a new Web Application'
• Fill out the new web application screen observing the following points:
o Change the New IIS Site description to read something like 'SharePoint – 80 -' where is the name of the web application your are creating (i.e. 'SSPAdmin', 'MySite' or 'Intranet')
o Ensure the 'Port' is set to 80
o Set the 'Host Header' to match the DNS record you created (i.e. 'SSPAdmin', 'MySite' or 'Intranet')
o Change the 'Application Pool Name' to match the 'New IIS Site Description'
o Enter your service account for the Application Pool account settings
o Change the 'Database Name' to read something like 'WSS_Content_' where is the name of the web application your are creating (i.e. 'SSPAdmin', 'MySite' or 'Intranet')
o Leave all other settings on default and click 'OK'
• Repeat for all three web applications (i.e. 'SSPAdmin', 'MySite' or 'Intranet')
Shared Service Provider Setup
The next stage is to create the Shared Service Provider (SSP). The SSP is required in order to provide several key services such as Search or My Site. To configure the SSP, follow these steps:
• In Central Administration, go to the 'Application Management' tab
• In the 'Office SharePoint Server Shared Services' section, click 'Create or Configure This Farms' Shared Services'
• Click 'New SSP'
• Fill out the 'New Shared Services Provider' screen observing the following guidelines:
o For the 'SSP Administration Site' web application (the first one you get asked for), choose the web application that you created earlier (suggested name was 'SharePoint – 80 - SSPAdmin')
o For the 'My Site Location' web application (the second one you get asked for), choose the web application you created earlier (suggested name was 'SharePoint – 80 - MySite')
o Enter your service account for the 'SSP Service Credentials'
o Leave all other settings on default and click 'OK'
• The creation of an SSP can take some time (up to 1 hour on a virtual machine). When it is finished you will see a 'Success!' screen, Click OK.
Collaboration Portal Site Collection Setup
The next stage is to create a collaboration portal which is one of the more feature-filled site types and represents a typical intranet environment. To do this, follow these steps:
• In Central Administration, go to the 'Application Management' tab
• In the 'SharePoint Site Management' section, choose 'Create Site Collection'
• Fill out the 'Create Site Collection' observing the following guidelines:
o Ensure you have selected the 'Intranet' web application you created earlier (suggested name was 'Intranet')
o Give your site a title ('Intranet' is suggested)
o In the 'Template Selection' section, choose 'Collaboration Portal' from 'Publishing' tab
o Enter you service account for the 'Primary Site Collection Administrator'
o Leave all other settings on default and click 'OK'
• When the 'Top-Level Site Successfully Created' message appears you have created the site, simply click the link that is provided (something like http://intranet)
Configure Indexing
The final step of the process is to configure indexing so that you have some search results. Though this step is optional, it is recommended as it will enable you to use the powerful search capabilities of SharePoint. To configure the index, follow these steps:
• In Central Administration, click the 'SharedServices1' link on the left-side navigation (or whatever you name your SSP)
• When the SSP Administration site appears, click on 'Search Settings' in the 'Search' section
• On the 'Configure Search Settings' page, click 'Content Sources and Crawl Schedules'
• Edit the 'Local office SharePoint Server Sites' content source by hovering your mouse over it and choosing 'Edit'
• Fill out the 'Edit Content Source' observing the following guidelines:
o Set a full crawl schedule to be at least once a day
o Set a incremental crawl schedule for every 10 minutes
o Tick the 'Start Full Crawl of this Content Source' tick-box
o Click 'OK'
• A crawl will now start. Initial crawls normally take up to 10 minutes.
The process is now complete. User should be able to access the main collaboration portal from http://intranet (or whatever you called the DNS record).
There are several things that you must do before you even insert the SharePoint 2007 CD they are:
• Install Windows 2003 R2 with the latest service pack (2 at time of writing) and all of the latest Windows Updates.
NOTE: Please do not use NewSID to change the SID of the machine if you are using a copy of another VM, this breaks things in SharePoint. My advice is to build Windows from fresh or to use Sysprep if you are using a copy of a VM.
• Join your machine to a domain or create a domain by running DCPromo.exe from the Start > Run dialog.
• Install the .net frameworks v3.0 and v2.0 from Windows Update. You can also download the full redistributable packages if your server is not online.
• Install Windows 'Application Server' from Add/Remove Programs in Control Panel with default settings
• Prepare a service account in your active directory domain to use for all Sharepoint services.
NOTE: Do not use the main domain\administrator account. This causes a problem if ever you wish to install Project Server 2007 on the same machine.
• Give your service account local administrator rights and logon as this account throughout the entire installation process.
• Install SQL 2005 (and latest service pack) with typical settings.
• Assign your service account to the 'Security Administrators' and 'Database Creators' server roles in SQL server (You will need to use SQL Server Management Studio).
Base SharePoint Server Install
You are now ready to install SharePoint 2007 itself, follow these steps:
• Login as your service account
• Insert your CD (or attach your ISO image) and run setup.exe if it does not autorun.
NOTE: If you get an error about web service extensions here, ensure that 'ASP.net V2.0.50727' web service extension is allowed in IIS. If it is not in the list, perform a 'repair' on .net 3.0 framework using add/remove programs and then the web service extension will appear in the list. This is caused when IIS is installed after the .net framework
• Enter your CD key and accept the license agreement.
• Choose 'Advanced' on the installation type dialog.
NOTE: The definition of 'Advanced' means that you are using full SQL server (which may or may not be on the same machine). If you had selected 'Basic' then it would have installed the cut down version of SQL (MSDE).
• Select 'Complete' on the Server Type screen and click 'Install Now'. The setup will now commence and you'll get a blue progress bar.
• Once installed you will get a screen with a check box that reads "Run the SharePoint products and Technologies Wizard now". Ensure this is ticked and click 'Close'.
• After a short pause, you'll get a 'Welcome' screen. Click 'Next'.
• You will get a warning that the wizard is about to reset several services, click 'Yes'.
• You'll be asked about the farm configuration, select to 'No, I want to create a new server farm'.
• Provide the database server (your server name) and your account details (account in the domain\user format). Leave the database name as the default. Click 'Next'.
• Leave the authentication mode as 'NTLM', set a specific port number is desired (not required) and click 'Next'.
NOTE: In a production environment, you would most likely use Kerberos where possible (if your infrastructure supports it).
• You'll get a summary screen; click 'Next' to kick-off the process.
NOTE: If it fails here, it is most likely that you do not SQL setup correctly. Ensure your service account is in the right groups. Please also note that this section can take a very long time, especially step 2 (up to 45 minutes).
• You'll get a success screen at the end, click 'Finish'.
• The wizard will attempt to load the central administration window. You may need to login here, use your service account. You may also get prompted to add the site to your trusted sites; go ahead and do that.
NOTE: This authentication prompt is caused by the secure version of IE on Windows 2003 Server. You can turn if off by modifying the security settings in IE.
Services on Server Configuration
The first bit of configuration to do is set your server to host all services. You do not strictly have to enable all of these services, but I find it helps if you are using the machine to test / investigate functionality.
• When the Central Administration screen appears, go to 'Operations' tab, then 'Services on Server'.
• Start the 'Document Conversions Load Balancer Service'.
• Start the 'Document Conversions Launcher Service', you'll have to choose the 'Load Balancer Server'; there should only be one option. If there are no options, ensure that the 'Document Conversions Load Balancer Service' has been started.
• Start the 'Excel Calculation Services'.
• Start the 'Office SharePoint Servers Search' service, observing the following guidelines:
o Tick both Query and Indexing check boxes
o Specify a contact email address (this can be any address)
o Enter your service account in the 'Farm Search Service Account' section
o Accept all other defaults and click 'Start'
• Leave all remaining services in their default configuration
Web Application Setup
The next stage is to create the 3 web applications that will be required to host the basic set of sites for a typical deployment, these are:
• Shared Service Provider Administration Site (Recommended to be called 'SSPAdmin')
• My Site Host (Recommended to be called 'MySite')
• The Main Intranet (or 'Portal') Site (Recommended to be called 'Intranet')
It is much simpler if all of these sites are on port 80 in IIS; this means that you do not have to remember to enter the ports all of the time. However having all three sites on port 80 means that each needs their own Host Header (required by IIS to differentiate between sites on the same port). The simplest way to do this is to create new 'Host (A)' records in DNS for each of your three sites. These should point to the IP address of your server; to do this follows these steps:
• Open the DNS Management tool from Administration Tools on your domain controller
• Navigate to your DNS zone
• Create new 'Host (A)' record
• Enter the Host header (i.e. 'SSPAdmin', 'MySite' or 'Intranet') for the site and the IP address of your server
• Click 'Add Host' and repeat for each of the three sites
Now the DNS entries are configured, we can create the three web applications in SharePoint; follow these steps for all three of your web applications (i.e. 'SSPAdmin', 'MySite' or 'Intranet'):
• In Central Administration, go to the 'Application Management' tab
• Click 'Create or Extend Web Application' and then click 'Create a new Web Application'
• Fill out the new web application screen observing the following points:
o Change the New IIS Site description to read something like 'SharePoint – 80 -
o Ensure the 'Port' is set to 80
o Set the 'Host Header' to match the DNS record you created (i.e. 'SSPAdmin', 'MySite' or 'Intranet')
o Change the 'Application Pool Name' to match the 'New IIS Site Description'
o Enter your service account for the Application Pool account settings
o Change the 'Database Name' to read something like 'WSS_Content_
o Leave all other settings on default and click 'OK'
• Repeat for all three web applications (i.e. 'SSPAdmin', 'MySite' or 'Intranet')
Shared Service Provider Setup
The next stage is to create the Shared Service Provider (SSP). The SSP is required in order to provide several key services such as Search or My Site. To configure the SSP, follow these steps:
• In Central Administration, go to the 'Application Management' tab
• In the 'Office SharePoint Server Shared Services' section, click 'Create or Configure This Farms' Shared Services'
• Click 'New SSP'
• Fill out the 'New Shared Services Provider' screen observing the following guidelines:
o For the 'SSP Administration Site' web application (the first one you get asked for), choose the web application that you created earlier (suggested name was 'SharePoint – 80 - SSPAdmin')
o For the 'My Site Location' web application (the second one you get asked for), choose the web application you created earlier (suggested name was 'SharePoint – 80 - MySite')
o Enter your service account for the 'SSP Service Credentials'
o Leave all other settings on default and click 'OK'
• The creation of an SSP can take some time (up to 1 hour on a virtual machine). When it is finished you will see a 'Success!' screen, Click OK.
Collaboration Portal Site Collection Setup
The next stage is to create a collaboration portal which is one of the more feature-filled site types and represents a typical intranet environment. To do this, follow these steps:
• In Central Administration, go to the 'Application Management' tab
• In the 'SharePoint Site Management' section, choose 'Create Site Collection'
• Fill out the 'Create Site Collection' observing the following guidelines:
o Ensure you have selected the 'Intranet' web application you created earlier (suggested name was 'Intranet')
o Give your site a title ('Intranet' is suggested)
o In the 'Template Selection' section, choose 'Collaboration Portal' from 'Publishing' tab
o Enter you service account for the 'Primary Site Collection Administrator'
o Leave all other settings on default and click 'OK'
• When the 'Top-Level Site Successfully Created' message appears you have created the site, simply click the link that is provided (something like http://intranet)
Configure Indexing
The final step of the process is to configure indexing so that you have some search results. Though this step is optional, it is recommended as it will enable you to use the powerful search capabilities of SharePoint. To configure the index, follow these steps:
• In Central Administration, click the 'SharedServices1' link on the left-side navigation (or whatever you name your SSP)
• When the SSP Administration site appears, click on 'Search Settings' in the 'Search' section
• On the 'Configure Search Settings' page, click 'Content Sources and Crawl Schedules'
• Edit the 'Local office SharePoint Server Sites' content source by hovering your mouse over it and choosing 'Edit'
• Fill out the 'Edit Content Source' observing the following guidelines:
o Set a full crawl schedule to be at least once a day
o Set a incremental crawl schedule for every 10 minutes
o Tick the 'Start Full Crawl of this Content Source' tick-box
o Click 'OK'
• A crawl will now start. Initial crawls normally take up to 10 minutes.
The process is now complete. User should be able to access the main collaboration portal from http://intranet (or whatever you called the DNS record).
Tuesday, January 6, 2009
How to find the versions of SharePoint
Using SharePoint Central Administration Web site SharePoint HTML Site Setting’s admin pages or IIS Manager, on the web sites properties HTTP Headers tab, virtual servers once extended will show the following version numbers:
MOSS 2007* or WSS 3.0 Cumulative update (KB956056 & KB956057) 12.0.0.6327
MOSS 2007* or WSS 3.0 Infrastructure Update (KB951695 & KB951297) 12.0.0.6318
MOSS 2007* or WSS 3.0 post-SP1 hotfix (KB948945) 12.0.0.6303
MOSS 2007* or WSS 3.0 post-SP1 hotfix (KB941274) 12.0.0.6301MOSS 2007* or WSS 3.0 post-SP1 hotfix (KB941422) 12.0.0.6300
MOSS 2007* or WSS 3.0 SP1 12.0.0.6219
MOSS 2007* or WSS 3.0 October public update 12.0.0.6039
MOSS 2007* or WSS 3.0 August 24, 2007 hotfix package 12.0.0.6036
MOSS 2007* or WSS 3.0 RTM 12.0.0.4518
MOSS 2007* or WSS 3.0 Beta 2 TR: 12.0.0.4407
MOSS 2007* or WSS 3.0 Beta 2: 12.0.0.4017
Office 12 (PDC image - pre-beta): 12.0.0.3111 (This version of Office does not have a support link in the Add/Remove programs dialog box).
*To confirm that a particular service pack is install on SharePoint Server you must either check the version numbers of specific dlls as specified in the related Microsoft Knowledge Based article or select the Show Updates check box in Add and Remove Programs.
WSS 2.0 SP3 6.0.2.8165
WSS 2.0 SP2 KB900929 + KB924881 6.0.2.8117
WSS 2.0 SP2 rollup KB900929 6.0.2.8000
WSS 2.0 SP2 6.0.2.6568
WSS 2.0 SP2 Beta = R2: 6.0.2.6551
WSS 2.0 SP1 + KB887981 6.0.2.6411
WSS 2.0 SP1: 6.0.2.6361
WSS 2.0 Unservice packed: 6.0.2.5530
To confirm that service packs are installed, especially with SharePoint Server 2007, go to Control Panel -> Add and Remove Programs
Select the product and then click: Click here for support. The versions will
be displayed as follows:
For WSS 3.0 & MOSS 2007
WSS 3.0 MOSS 2007
post-SP1 hotfix (KB948945) 12.0.6303.5000 12.0.6303.5000
SP1 12.0.6219.1000 12.0.6219.1000
RTM 12.0.4518.1016 12.0.4518.1016
Beta 2 TR 12.0.4407.1005 12.0.4407.1005
Beta 2 12.0.4017.1006 12.0.4017.1006
For WSS 2.0 & SPS 2003
WSS 2.0 SPS 2003
SP3 11.0.8173.0 11.0.8168.0
post SP2 rollup 11.0.8000.0 11.0.8126.2
SP2 11.0.7969.0 11.0.8126.0
R2 WSS SP2 beta 11.0.6551.0
SP1+KB887981 11.0.6411.0
With Service Pack 1 11.0.6361.0 11.0.6715.0
Unserviced pack 11.0.5608.0 11.0.5704.0
Note: If you have a version number starting with 10, then it is either SharePoint Team Services (SPTS) or SharePoint Portal 2001 (SPS 2001).
SPTS, 10.0.2627.01 is the version with no service packs. In the Administrative Tools menu, you will see a link to Microsoft SharePoint Administrator. This will display a web page, where you can see the version number of the virtual server(s), e.g., 5.0.2.2623. The ISAPI filter is fpexedll.dll.
For SPS 2001, 10.145.4629 is the version number with no service packs. There will be no ISAPI filter, and from the Administrative Tools menu you will see a link to SharePoint Portal Server Administrator which launches mmc snap-in.
MOSS 2007* or WSS 3.0 Cumulative update (KB956056 & KB956057) 12.0.0.6327
MOSS 2007* or WSS 3.0 Infrastructure Update (KB951695 & KB951297) 12.0.0.6318
MOSS 2007* or WSS 3.0 post-SP1 hotfix (KB948945) 12.0.0.6303
MOSS 2007* or WSS 3.0 post-SP1 hotfix (KB941274) 12.0.0.6301MOSS 2007* or WSS 3.0 post-SP1 hotfix (KB941422) 12.0.0.6300
MOSS 2007* or WSS 3.0 SP1 12.0.0.6219
MOSS 2007* or WSS 3.0 October public update 12.0.0.6039
MOSS 2007* or WSS 3.0 August 24, 2007 hotfix package 12.0.0.6036
MOSS 2007* or WSS 3.0 RTM 12.0.0.4518
MOSS 2007* or WSS 3.0 Beta 2 TR: 12.0.0.4407
MOSS 2007* or WSS 3.0 Beta 2: 12.0.0.4017
Office 12 (PDC image - pre-beta): 12.0.0.3111 (This version of Office does not have a support link in the Add/Remove programs dialog box).
*To confirm that a particular service pack is install on SharePoint Server you must either check the version numbers of specific dlls as specified in the related Microsoft Knowledge Based article or select the Show Updates check box in Add and Remove Programs.
WSS 2.0 SP3 6.0.2.8165
WSS 2.0 SP2 KB900929 + KB924881 6.0.2.8117
WSS 2.0 SP2 rollup KB900929 6.0.2.8000
WSS 2.0 SP2 6.0.2.6568
WSS 2.0 SP2 Beta = R2: 6.0.2.6551
WSS 2.0 SP1 + KB887981 6.0.2.6411
WSS 2.0 SP1: 6.0.2.6361
WSS 2.0 Unservice packed: 6.0.2.5530
To confirm that service packs are installed, especially with SharePoint Server 2007, go to Control Panel -> Add and Remove Programs
Select the product and then click: Click here for support. The versions will
be displayed as follows:
For WSS 3.0 & MOSS 2007
WSS 3.0 MOSS 2007
post-SP1 hotfix (KB948945) 12.0.6303.5000 12.0.6303.5000
SP1 12.0.6219.1000 12.0.6219.1000
RTM 12.0.4518.1016 12.0.4518.1016
Beta 2 TR 12.0.4407.1005 12.0.4407.1005
Beta 2 12.0.4017.1006 12.0.4017.1006
For WSS 2.0 & SPS 2003
WSS 2.0 SPS 2003
SP3 11.0.8173.0 11.0.8168.0
post SP2 rollup 11.0.8000.0 11.0.8126.2
SP2 11.0.7969.0 11.0.8126.0
R2 WSS SP2 beta 11.0.6551.0
SP1+KB887981 11.0.6411.0
With Service Pack 1 11.0.6361.0 11.0.6715.0
Unserviced pack 11.0.5608.0 11.0.5704.0
Note: If you have a version number starting with 10, then it is either SharePoint Team Services (SPTS) or SharePoint Portal 2001 (SPS 2001).
SPTS, 10.0.2627.01 is the version with no service packs. In the Administrative Tools menu, you will see a link to Microsoft SharePoint Administrator. This will display a web page, where you can see the version number of the virtual server(s), e.g., 5.0.2.2623. The ISAPI filter is fpexedll.dll.
For SPS 2001, 10.145.4629 is the version number with no service packs. There will be no ISAPI filter, and from the Administrative Tools menu you will see a link to SharePoint Portal Server Administrator which launches mmc snap-in.
Importing User pictures from Active Directory to MOSS 2007
In MOSS 2007 you’ll notice that users are able to upload pictures to there personal My Sites. These pictures also get propagated to the Contact Details web part as well as People Search Results.
So it’s actually a common practice for many companies to standardize on employee photos and disable everyone from uploading their glamour shots. To do this, first go to your Active Directory Management Console and hopefully you have the Exchange AD Management Plug in installed also.
You’ll know if you have it installed if you see all the tabs below:
1. Click on the Exchange Advanced Tab
2. Click Custom Attributes
3. Use one of those extension Attribute values to store any kind of link to your picture.
4. OK out of AD.
Now you want to go to your MOSS Central Admin and do the following:
5. Go to your Shared Services Provider
6. Under User Profiles and My Sites click on User profiles and properties
7. Click on View Profile Properties at the bottom of the page.
8. Edit the Picture Property
9. Select “Do not allow users to edit values for this property”
10. In the Property Import Mapping Section change the Data source field to map: to your corresponding extension Attribute# and hit OK.
Do a full user import and all the pictures should get populated into SharePoint!
So it’s actually a common practice for many companies to standardize on employee photos and disable everyone from uploading their glamour shots. To do this, first go to your Active Directory Management Console and hopefully you have the Exchange AD Management Plug in installed also.
You’ll know if you have it installed if you see all the tabs below:
1. Click on the Exchange Advanced Tab
2. Click Custom Attributes
3. Use one of those extension Attribute values to store any kind of link to your picture.
4. OK out of AD.
Now you want to go to your MOSS Central Admin and do the following:
5. Go to your Shared Services Provider
6. Under User Profiles and My Sites click on User profiles and properties
7. Click on View Profile Properties at the bottom of the page.
8. Edit the Picture Property
9. Select “Do not allow users to edit values for this property”
10. In the Property Import Mapping Section change the Data source field to map: to your corresponding extension Attribute# and hit OK.
Do a full user import and all the pictures should get populated into SharePoint!
Subscribe to:
Posts (Atom)