Archive for the ‘SharePoint’ Category

Thanks http://support.microsoft.com/kb/2293357

  1. Install PDF iFilter 9.0 (64 bit) from http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025 (http://www.adobe.com/support/downloads/detail.jsp?ftpID=4025)
  2. Download PDF icon picture from Adobe web site http://www.adobe.com/misc/linking.html (http://www.adobe.com/misc/linking.html) and copied at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES\
  3. Add the following entry in docIcon.xml file, which can be found at: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML
    <Mapping Key=”pdf” Value=”pdf16.gif” />
  4. Add pdf file type on the File Type page under Search Service Application
  5. Open regedit
  6. Navigate to the following location: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension
  7. Right-click > Click New > Key to create a new key for .pdf
  8. Add the following GUID in the default value
    {E8978DA6-047F-4E3D-9C78-CDBE46041603}
  • Restart the SharePoint Server Search 14
  • Reboot the SharePoint servers in Farm
  • Create a Test site (with any out-of-box site template) and create a document library upload any sample PDF document(s).
  • Perform FULL Crawl to get search result.

Edit this file :

C:\FASTSearch\etc\config_data\DocumentProcessor\formatdetector\user_converter_rules.xml

Add this :

<ConverterRules>
    <IFilter>
        <trust>
            <ext name=”.pdf” mimetype=”application/pdf” />
        </trust>
    </IFilter>
    <MimeMapping>
        <mime type=”application/pdf”>PDF File</mime>
    </MimeMapping>
</ConverterRules>

Run psctrl reset to reset all currently running item processors in the system.

  • Share/Bookmark

Follow these below instructions. Take close note to this line, especially the part in BOLD : Navigate to the directory where you copied the securefastsearchconnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service.

Configure SSL enabled communication

Ff381261.Warning(en-us,office.14).gifWarning:
Configuring SSL enabled communication is mandatory.

Secure Sockets Layer (SSL) communication is required to feed content from SharePoint Server 2010 to FAST Search Server 2010 for SharePoint. To enable secure communications, configure the Content SSA to use an SSL certificate for FAST Search Server 2010 for SharePoint. FAST Search Server 2010 for SharePoint generates a self-signed certificate during post-setup configuration. This section describes how to use this certificate to enable SSL communication using the self-signed certificate. It is recommended to use certificates issued by a proper Certificate Authority in production environments, refer to Manage certificates (FAST Search Server 2010 for SharePoint) for advanced instructions.

The following procedure has to be followed at least one time, to enable SSL communication between the SharePoint Server 2010 server that runs the Content SSA crawl component and the FAST Search Server 2010 for SharePoint back-end. If your environment contains additional SharePoint Server 2010 servers running a Content SSA crawl component, additional steps are required to enable SSL communication for those servers. Refer to Multiple server deployment of the Content SSA (FAST Search Server 2010 for SharePoint) for more information.

Ff381261.Important(en-us,office.14).gifImportant:
This procedure includes copying sensitive information. Ensure that the certificate information is kept private.

  1. Copy the script securefastsearchconnector.ps1 from the FAST Search Server 2010 for SharePoint admin server to the SharePoint Server 2010 server. The securefastsearchconnector.ps1 script is in the installation folder, under installer\scripts\.
  2. Copy the certificate file FASTSearchCert.pfx from the FAST Search Server 2010 for SharePoint admin server to the SharePoint Server 2010 server. The certificate file is in the installation folder, under data\data_security\cert\.
  3. Open a Microsoft SharePoint 2010 Administration Shell with the Run as administrator option on the SharePoint Server 2010 server.

    Navigate to the directory where you copied the securefastsearchconnector.ps1 script and run it, replacing the necessary parameters with the values for your environment. The domain and user name should reflect the details of the user running the SharePoint Server Search 14 (OSearch14) service.

    .\SecureFASTSearchConnector.ps1 –certPath “path of the certificate\certificatename.pfx” –ssaName “name of your content SSA” –username “domain\username”

    When prompted to enter the certificate password, enter the certificate password that you supplied when you ran the post-setup configuration of FAST Search Server 2010 for SharePoint.

    Ff381261.Important(en-us,office.14).gifImportant:
    The script verifies the connection to FAST Search Server 2010 for SharePoint. Therefore, make sure that all servers in the FAST Search Server 2010 for SharePoint farm are running before you run this script.
  • Share/Bookmark
  • NewsGator already implementing customers on 2010. We’re next! http://bit.ly/coiRvI
  • Proud to be a SharePoint 2010/NewsGator Social Sites 2010 early adopter! #NewsGator #sharepoint http://bit.ly/coiRvI
  • We’ve already been blazing the social computing trail with #SharePoint 2010 and early help from #NewsGatorhttp://bit.ly/coiRvI
  • We got an early jump on SharePoint 2010 with a little help from our friends at #NewsGator – social success! http://bit.ly/coiRvI
  • Happy #SharePoint 2010 launch, thanks #NewsGator for early help with our implementation http://bit.ly/coiRvI
  • Staying ahead of our competitors with social ROI thanks to #NewsGator innovations on #SharePoint 2010 http://bit.ly/coiRvI
  • Our #SharePoint 2010 collaboration with #NewsGator is a great example of social at work http://bit.ly/coiRvI
  • We got a jump on social #SharePoint by working with our good friends at #NewsGator – congrats on launch #Microsoft! http://bit.ly/coiRvI
  • Share/Bookmark

This is an example of a very simple multi thread script. All it does is output 2 user names per function.
But you can only imagine the power.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
#Create a function, or in this example create/split up a large job into multiple functions.
 
#Step 1 : Create threading.ps1
#Step 2 : Create function and add it to threading.ps1
 
#(Sample Function)
 
function one{
	$users1 = "CORP1\Bollasr1", "CORP2\aardeje1"
		foreach ($u in $users1){
			Write-Output "$u"
		}
}
one | out-File C:\lnl\oneresults.txt
 
 
#Step 3 : Wrap the function inside a function with (Write-Output ' ')  around each line. 
#(Sample Wrapped Function)
 
function createone{
Write-Output 'function one{'
Write-Output '	$users1 = "CORP1\Bollasr1", "CORP2\aardeje1"'
Write-Output '		foreach ($u in $users1){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'one | out-File C:\lnl\oneresults.txt'
}
 
 
#Now I will show an example of 5 threads. This file is called threading.ps1
 
##Create Multi Thread Script
function createone{
Write-Output 'function one{'
Write-Output '	$users1 = "CORP1\Bollasr1", "CORP2\aardeje1"'
Write-Output '		foreach ($u in $users1){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'one | out-File C:\lnl\oneresults.txt'
}
 
 
function createtwo{
Write-Output 'function two{'
Write-Output '	$users2 = "CORP1\dudlesu1", "CORP2\duerrma1"'
Write-Output '		foreach ($u in $users2){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'two | out-File C:\lnl\tworesults.txt'
}
 
 
function createthree{
Write-Output 'function three{'
Write-Output '	$users3 = "CORP1\khattpa2", "CORP1\khattsa1"'
Write-Output '		foreach ($u in $users3){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'three | out-File C:\lnl\threeresults.txt'
}
 
 
function createfour{
Write-Output 'function four{'
Write-Output '	$users4 = "CORP1\pellath1", "CORP2\pellian5"'
Write-Output '		foreach ($u in $users4){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'four | out-File C:\lnl\fourresults.txt'
}
 
 
function createfive{
Write-Output 'function five{'
Write-Output '	$users5 = "CORP1\trancu1", "CORP2\tranth8"'
Write-Output '		foreach ($u in $users5){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'five | out-File C:\lnl\fiveresults.txt'
}
 
 
#Step 4 : Create .ps1 scripts out of the functions.
#Take note that ..\..\ alows for a releative path.
 
createone | out-File ..\..\Threadone.ps1
createtwo | out-File ..\..\Threadtwo.ps1
createthree | out-File ..\..\Threadthree.ps1
createfour | out-File ..\..\Threadfour.ps1
createfive | out-File ..\..\Threadfive.ps1
 
 
#Step 5 : Launch threading script.
 
start-job -filepath ..\..\Threadone.ps1
start-job -filepath ..\..\Threadtwo.ps1
start-job -filepath ..\..\Threadthree.ps1
start-job -filepath ..\..\Threadfour.ps1
start-job -filepath ..\..\Threadfive.ps1
 
#Step 6 : Check Status of Jobs
#The Wait-Job cmdlet waits for Windows PowerShell background jobs to complete before it displays the command prompt.
 
get-job | wait-job
 
#Step 7 : Stop any Job that may be hung.
#The Stop-Job cmdlet stops Windows PowerShell background jobs that are in progress.
 
get-job | stop-job
 
#full Script called threading.ps1
##Create Multi Thread Script
 
function createone{
Write-Output 'function one{'
Write-Output '	$users1 = "CORP1\Bollasr1", "CORP2\aardeje1"'
Write-Output '		foreach ($u in $users1){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'one | out-File C:\lnl\oneresults.txt'
}
 
 
function createtwo{
Write-Output 'function two{'
Write-Output '	$users2 = "CORP1\dudlesu1", "CORP2\duerrma1"'
Write-Output '		foreach ($u in $users2){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'two | out-File C:\lnl\tworesults.txt'
}
 
 
function createthree{
Write-Output 'function three{'
Write-Output '	$users3 = "CORP1\khattpa2", "CORP1\khattsa1"'
Write-Output '		foreach ($u in $users3){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'three | out-File C:\lnl\threeresults.txt'
}
 
 
function createfour{
Write-Output 'function four{'
Write-Output '	$users4 = "CORP1\pellath1", "CORP2\pellian5"'
Write-Output '		foreach ($u in $users4){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'four | out-File C:\lnl\fourresults.txt'
}
 
 
function createfive{
Write-Output 'function five{'
Write-Output '	$users5 = "CORP1\trancu1", "CORP2\tranth8"'
Write-Output '		foreach ($u in $users5){'
Write-Output '			Write-Output "$u"'
Write-Output '		}'
Write-Output '}'
Write-Output 'five | out-File C:\lnl\fiveresults.txt'
}
 
createone | out-File ..\..\Threadone.ps1
createtwo | out-File ..\..\Threadtwo.ps1
createthree | out-File ..\..\Threadthree.ps1
createfour | out-File ..\..\Threadfour.ps1
createfive | out-File ..\..\Threadfive.ps1
 
start-job -filepath ..\..\Threadone.ps1
start-job -filepath ..\..\Threadtwo.ps1
start-job -filepath ..\..\Threadthree.ps1
start-job -filepath ..\..\Threadfour.ps1
start-job -filepath ..\..\Threadfive.ps1
 
get-job | wait-job
 
get-job | stop-job
  • Share/Bookmark

Posted by Isaac Blum at 21 January 2010

Category: Business, For The Greater Good, Free Help, MOSS 2007, PowerShell, SharePoint

Tags: , , , , , ,

The below links were used to create this script. Thanks

http://blogs.msdn.com/powershell/archive/2009/01/10/capture-console-screen.aspx

http://www.sharepointdevwiki.com/display/public/Updating+User+Profiles+in+SharePoint+SSP+using+PowerShell

http://blogs.flexnetconsult.co.uk/colinbyrne/PermaLink,guid,a332015d-c5dc-4433-a0f3-247fd37b0b04.aspx

Download the file here

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
[void][reflection.assembly]::Loadwithpartialname("Microsoft.SharePoint") | out-null
[void][reflection.assembly]::Loadwithpartialname("Microsoft.Office.Server.Search") | out-null
[void][reflection.assembly]::Loadwithpartialname("Microsoft.Office.Server") | out-null
 
#################################################################################################################
# Get-ConsoleAsText.ps1
# Thanks to http://blogs.msdn.com/powershell/archive/2009/01/10/capture-console-screen.aspx for Get-ConsoleAsText.ps1
# The script captures console screen buffer up to the current cursor position and returns it in plain text format.
#
# Returns: ASCII-encoded string.
#
# Example:
#
# $textFileName = "$env:temp\ConsoleBuffer.txt"
# .\Get-ConsoleAsText | out-file $textFileName -encoding ascii
# $null = [System.Diagnostics.Process]::Start("$textFileName")
#################################################################################################################
function Get-ConsoleAsText{
# Check the host name and exit if the host is not the Windows PowerShell console host.
if ($host.Name -ne 'ConsoleHost')
{
  write-host -ForegroundColor Red "This script runs only in the console host. You cannot run this script in $($host.Name)."
  exit -1
}
 
# Initialize string builder.
$textBuilder = new-object system.text.stringbuilder
 
# Grab the console screen buffer contents using the Host console API.
$bufferWidth = $host.ui.rawui.BufferSize.Width
$bufferHeight = $host.ui.rawui.CursorPosition.Y
$rec = new-object System.Management.Automation.Host.Rectangle 0,0,($bufferWidth - 1),$bufferHeight
$buffer = $host.ui.rawui.GetBufferContents($rec)
 
# Iterate through the lines in the console buffer.
for($i = 0; $i -lt $bufferHeight; $i++)
{
  for($j = 0; $j -lt $bufferWidth; $j++)
  {
    $cell = $buffer[$i,$j]
    $null = $textBuilder.Append($cell.Character)
  }
  $null = $textBuilder.Append("`r`n")
}
return $textBuilder.ToString()
}
 
################################################################
 
# Pause Script
function Pause ($Message="Script Complete. Press any key to continue...")
{
Write-Host -NoNewLine $Message
$null = $Host.UI.RawUI.ReadKey("NoEcho,IncludeKeyDown")
Write-Host ""
}
 
################################################################
 
function Get-UserProfileConfigManager([string]$siteUrl)
{
# Need to get a PortalContext object
# as we do not have a HttpContext we need to source one the hard way
$site=new-object Microsoft.SharePoint.SPSite($siteUrl)
$servercontext=[Microsoft.Office.Server.ServerContext]::GetContext($site)
$site.Dispose() # clean up
 
################################################################
 
# Return the UserProfileConfigManager
new-object Microsoft.Office.Server.UserProfiles.UserProfileConfigmanager($servercontext)
}
function Get-SPProfileManager([string]$siteUrl)
{
# Need to get a PortalContext object
# as we do not have a HttpContext we need to source one the hard way
$site=new-object Microsoft.SharePoint.SPSite($siteUrl)
$servercontext=[Microsoft.Office.Server.ServerContext]::GetContext($site)
$site.Dispose() # clean up
 
################################################################
 
# Return the UserProfileManager
new-object Microsoft.Office.Server.UserProfiles.UserProfileManager($servercontext)
}
function Get-SPUserProfile([string]$siteUrl, [string] $u)
{
$upm= Get-SPProfileManager([string]$siteUrl)
if ($upm.UserExists($u) -eq $false)
{
    $upm.CreateUserProfile($u)
 
$upm.GetUserProfile($u)
}
 
################################################################
 
# Create function
function Update-UserProfileProperty()
{
	PARAM
	(
		[string] $siteUrl = $( throw "You must provide a Site Collection Url e.g. 'http://moss/'"),
		[string] $userName = $( throw "You must provide a User Name e.g. 'DOMAIN\USERNAME'"),
		[string] $propName = $( throw "You must provide a User Profile Property Name e.g. 'WorkPhone'"),
		[string] $propValue = $( throw "You must provide a User Profile Property Value e.g. '0400 767 022'")
	)
	END
	{
		if ($propValue -eq "NULL" -or $propValue -eq "" -or $propValue -eq "None")
		{
			Write-Host "Property '$propName' is not set ('$propValue')"
		}
		else
		{
			$cm = get-userprofileconfigmanager $siteUrl
			$spm = Get-SPProfileManager $siteUrl
			if ($spm.UserExists($userName))
			{
				$userProfile = $spm.GetUserProfile($userName);
				$tempProp = $spm.Properties.GetPropertyByName($propName);
				if ($tempProp -eq $null)
				{
					throw "User Profile Property '$propName' does not exist!";
				}
				else
				{
					$userProfile[$propName].Value = $propValue;
					$userProfile.Commit();
				}
				write-host -foregroundcolor green "'$propName' User Profile Property updated to '$propValue' for '$userName'"
				Write-Output "'$propName' User Profile Property updated to '$propValue' for '$userName'"
			}
			else
			{
				Write-Host -ForegroundColor red  "User '$userName' does not exist in User Profiles!"
				Write-output "User '$userName' does not exist in User Profiles!";
			}
		}
	}
}
 
################################################################
 
function MySiteProUpdate{
$username = "IB\Admin", "IB\Guest", "IB\PowerShell"
 
# Set MySite URL
$siteUrl = "http://mysites:3000"
 
# Notifies
Write-Host "Working... Please Wait"
Write-Output " "
 
foreach($u in $username){
# Executes command for all users in this script
Write-Output "Executing this command :  Update-UserProfileProperty $siteUrl $u ActiveEmployee true"
Update-UserProfileProperty $siteUrl "$u" "ActiveEmployee" "true"
}
# Dump Console
$textFileName = "C:\IBLogs\ConsoleDump.txt"
Get-ConsoleAsText | out-file $textFileName -encoding ascii
#$null = [System.Diagnostics.Process]::Start("$textFileName")
pause
}
################################################################
 
MySiteProUpdate | out-File C:\IBLogs\Progress.txt
  • Share/Bookmark

Posted by Isaac Blum at 22 December 2009

Category: Business, For The Greater Good, Microsoft, SharePoint, WSS 3.0

Tags: , , ,

Thanks to http://blogs.msdn.com/sharepoint/archive/2007/03/02/be-wary-when-removing-or-replacing-the-my-site-link.aspx and http://suguk.org/forums/thread/6898.aspx.

I needed a way of adding a link back to the portal site, when in my MySite. I went to “Personalization site links”. Added a link but every time it would add the http://%yoururl%/default.aspx?MySiteView=1 . Made me crazy. Anyway thanks to the folks that bloged about it first.

  • Share/Bookmark

Thanks goes to the following people/sites: http://blogs.msdn.com/dansellers/archive/2005/11/09/491152.aspx & http://windowsitpro.com/Web/article/articleid/9738/extending-the-user-class-in-the-ad-schema.html 

Enable Password Question and Password Reset:

When these attributes are set to true in the web config file as seen below, the user is required to provide an answer to a Password Question when the password is first created.  When the user resets their password, they will also be required to provider the answer they supplied to the Password Question when the password was first created. 

<membership defaultProvider=”ADAMProvider”>
  <providers>
    <add
      connectionStringName=”ADCnString”
      connectionUsername=”CN=ADAdmin,OU=Users,O=ADAuth”
      connectionPassword=Pass@word1
      connectionProtection=”None”
      requiresQuestionAndAnswer=”true”
      enablePasswordReset=”true” …

Mapping Password Question and Answer Attributes:

Both the Password Question and the Answer will be saved in the SQL Server, Active Directory, or the Active Directory Application Mode (ADAM) depending upon the provider you are using. However, if you are using the Active Directory Provider you will be required to modify the schema of either the Active Directory or ADAM to store the Password Question and Password Answer.  Then in the web config file you will need map the Password Question and Answer’s attributes to the modified schema as shown below:

<membership defaultProvider=”ADAMProvider”>
   <providers>
      <add
         connectionStringName=”ADCnString”
         connectionUsername=”CN=ADAdmin,OU=Users,O=ADAuth”
         connectionPassword=Pass@word1
         connectionProtection=”None”
         requiresQuestionAndAnswer=”true”
         enablePasswordReset=”true”
         attributeMapPasswordQuestion=”PwdQuestion”
         attributeMapPasswordAnswer=”PwdAnswer” …
 

Example Schema Modification:

Creating the PwdQuestion and PwdAnswer attribute as defined above is not difficult in the ADAM ADSI Edit tool under the Schema configuration, but initially it takes a while to figure out what values required by the attribute schema wizard.  Below is an example of the values that you can use in your Active Directory or ADAM directory.

    cn:  PwdQuestion
    OMSyntax: 64 (for Unicode string)
    lDAPDisplayName: PwdQuestion
    isSingleValued: TRUE
    AttributeSyntax: 2.5.5.12 (Active Directory syntax type of Unicode)
    AttributeID: 1.2.840.113556.1.6.1.1.6221 (Unique Object Identifiers (OIDs))

    cn:  PwdAnswer
    OMSyntax: 64 (for Unicode string)
    lDAPDisplayName: PwdAnswer
    isSingleValued: TRUE
    AttributeSyntax: 2.5.5.12
    AttributeID: 1.2.840.113556.1.6.1.1.6222

Schema modifications:
Creating the Failed Password Count, Failed Password Answer Time and Failed Password Locked Out Time attributes–as defined below–is not difficult in the ADAM ADSI Edit tool under the Schema configuration, but initially it takes a while to figure out what values are required by the attribute schema wizard. Below is an example of the values that you can use in your Active Directory or ADAM directory.

cn: FailedPwdCount
OMSyntax: 2 (for type integer)
lDAPDisplayName: FailedPwdCount
isSingleValued: TRUE
AttributeSyntax: 2.5.5.9 (Active Directory syntax type of Unicode)
AttributeID: 1.2.840.113556.1.6.1.1.6223 (Unique Object Identifiers (OIDs))

cn: FailedPwdAnswerTime
OMSyntax: 65 (for Large integer/Interval)
lDAPDisplayName: FailedPwdAnswerTime
isSingleValued: TRUE
AttributeSyntax: 2.5.5.16
AttributeID: 1.2.840.113556.1.6.1.1.6224

cn: FailedPwdLockOutTime
OMSyntax: 65 (for Large integer/Interval)
lDAPDisplayName: FailedPwdLockOutTime
isSingleValued: TRUE
AttributeSyntax: 2.5.5.16
AttributeID: 1.2.840.113556.1.6.1.1.6225

Modify Web Config File:
When using the Active Directory Provider you will be required to modify the Web config to map the Failed Password Answer Count, Failed Password Answer Time and Failed Password Answer Lockout Time attributes to the appropriate User’s properties (as created above) in either your Active Directory or ADAM.

<membership defaultProvider=”ADAMProvider”>
   <providers>
      <add

connectionStringName=”ADCnString”
connectionUsername=”CN=ADAdmin,OU=Users,O=ADAuth”
connectionPassword=Pass@word1
connectionProtection=”None”
requiresQuestionAndAnswer=”true”
enablePasswordReset=”true”
attributeMapPasswordQuestion=”PwdQuestion”
attributeMapPasswordAnswer=”PwdAnswer”
attributeMapFailedPasswordAnswerCount=”FailedPwdCount” attributeMapFailedPasswordAnswerTime=”FailedPwdAnswerTime”
attributeMapFailedPasswordAnswerLockoutTime=”FailedPwdLockOutTime”

(Adding the attributes to the user clasee)

From the Schema Console, click the Class folder. Scroll down to the User class, right-click it, and select Properties. On the user Properties dialog box, click the Attributes tab, which Figure 7 shows. Click Add, then choose the Gender attribute. Click OK twice, and you’ve successfully added the Gender attribute to the User class.

  • Share/Bookmark

Here are the commands I used:

stsadm -o addcontentdb -url http://moss:1000 -databasename SharePoint_AdminContent_moss
stsadm -o enumsites -url http://moss:1000 > output.txt
stsadm -o mergecontentdbs -url http://moss:1000 -operation 2 -sourcedatabasename SharePoint_AdminContent_f58aa288-57e9-49ff-b953-9b4d53d50bfc -destinationdatabasename SharePoint_AdminContent_moss -filename output.txt
iisreset
stsadm -o deletecontentdb -url http://moss -databasename SharePoint_AdminContent_f58aa288-57e9-49ff-b953-9b4d53d50bfc
check with stsadm -o enumcontentdbs -url http://moss:1000

  • Share/Bookmark

Posted by Isaac Blum at 29 October 2009

Category: Business, For The Greater Good, Free Help, MOSS 2007, Microsoft, SharePoint, WSS 3.0

Tags: , , , , , , ,

Out of the box neither WSS 3 nor MOSS 2007 will index content located in Acrobat PDF files, so you need to set up the IFilter.  I’ve also found that that PDF files loaded prior to the installation of the filter won’t be re-crawled automatically, so to be on the safe side you might want to kick off a full crawl.

Here is what I’ve found works for WSS 3.0:

  1. First, you need to download the Adobe PDF IFilter 6.0, which you can find at this URL.  You should also get hold of a suitable Icon to use with PDFs, so that when they are listed in a document library they are easily recognisable.  There is a 17 x 17 one available on the Adobe web site here.
  2. Once you’ve downloaded the IFilter, install it on your WSS 3.0 server, and then follow the instructions on registry settings in Microsoft KB Article 927675.  I’ve always found that providing the Adobe IFilter installed properly, the only setting I need to add is the Search Extensions one listed in step 2.  Also note step 5 re stopping and re-starting the search service.
  3. Now you need to set up the Icon file.  If you downloaded the icon file in step 1 above, you will have a file called pdficon_small.gif.  You need to copy this onto your WSS 3.0 server, into drive:\Program Files\Common FIles\Microsoft Shared\Web Server extensions\12\TEMPLATE\IMAGES.
  4. Next you need to edit the XML file which WSS uses to link file extensions to icons.  This file is called DOCICON.XML and is located at drive:\Program Files\Common FIles\Microsoft Shared\Web Server extensions\12\TEMPLATE\XML.  Navigate to that folder and locate the file.  I would suggest making a backup copy first, then opening the file in NotePad.  You need to add a mapping key for PDFs at the bottom of the file, above the </ByExtension> closing tag.  The new key will be <Mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=”"/>  (note that XML is case sensitive so make sure you use same case as previous entries).  Then save the file.
  5. That’s pretty much it, but if you already have PDFs uploaded to your WSS server I would recommend starting a full crawl.  You can do the with STSAdm, the command syntax is Stsadm -o spsearch -action fullcrawlstart .  More on this on TechNet here.
  • Share/Bookmark
  • Archives

  • Pages

  • Tags

  • More

Get Adobe Flash playerPlugin by wpburn.com wordpress themes