July, 2007 - Imagine Think Create Share - Site Home

| |

Imagine Think Create Share

Rich Text Content Control and Custom XML Part

Posted over 5 years ago

by carlos.hm
- 0 Comments
Hi,

Maybe you have used the Word 2007 Content Control Toolkit, and after mapping a Rich Text Content Control with a XML node, you have noticed that it turns into a plain text content control.

This is something that Word 2007 Content Control Toolkit manages, as it is not expected behaviour of the current implemented version of content controls.

You can check at http://msdn2.microsoft.com/en-us/library/bb226172.aspx that the expected action would be a run-time error.

The same way when you map a XML node to a picture content control, it stores the base-64 binary representation; it would be great to include the rich text representation (Ecma 376) of the text.

Cheers!
Imagine Think Create Share

Configuring LDAP Provider with MOSS 2007

Posted over 5 years ago

by carlos.hm
- 5 Comments
Hi,

Today I wanted to show you the neccessary steps to configure MOSS with the LDAP Provider (we will actually query Active Directory). First you can find at technet2 information about the process and its implications
- Authentication samples (Windows SharePoint Services)->LDAP membership provider http://technet2.microsoft.com/WindowsServer/WSS/en/library/91035419-980e-4230-b3ae-67253b94af4a1033.mspx#section3
- Plan authentication methods (Windows SharePoint Services) http://technet2.microsoft.com/windowsserver/WSS/en/library/b6bc8fec-c11c-4ed7-a78d-3ad61c7ef6c01033.mspx
- Plan authentication settings for Web applications in Office SharePoint Server
- Persistent cookies are not shared between Internet Explorer 7 and Office applications in Windows Vista http://support.microsoft.com/default.aspx/kb/932118
- Configuring Multiple Authentication Providers for SharePoint 2007 http://blogs.msdn.com/sharepoint/archive/2006/08/16/702010.aspx
With all this information it will be easy to set up our job.
Turn on ASP.NET forms authentication
In order to create this task you weill need access to the web.config of the web application under change. You will find it opening Internet Information Services (IIS) Manager, WebSites, and context menu over the web application (open). My example bring me: C:\Inetpub\wwwroot\wss\VirtualDirectories\moss.litwareinc.com80

Then I edit the web.config file and change <authentication mode="Windows" /> with <authentication mode="Forms" /> inside system.web node.

With no other change you will find that if you try to log in your site, it will throw a 404 error and redirects you to the default login page: http://moss.litwareinc.com/login.aspx?ReturnUrl=%2fPages%2fDefault.aspx

Register the membership provider

In the next step we should register the memebership provider for LDAP, and change hte Auth Provider in the Central Admin.

This will involved changing web.config again (remember that changing web.config will reset the AppPool).

The change will affect membership node:

<membership defaultProvider="LdapMembershipProvider">
<providers>
    <add
      name="LdapMembership"
      type="Microsoft.Office.Server.Security.LDAPMembershipProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
      server="MOSS.LITWAREINC.COM"
      port="389"
      useSSL="false"
      userDNAttribute="distinguishedName"
      userNameAttribute="sAMAccountName"
      userContainer="CN=Users,DC=litwareinc,DC=com"
      userObjectClass="person"
      userFilter="(|(ObjectCategory=group)(ObjectClass=person))"
      scope="Subtree"
      otherRequiredUserAttributes="sn,givenname,cn"
      />
</providers>
</membership>

In order to fill in the userContainer attribute (we changed serverto match our environment [SingleServer]), I will use ADExplorer http://www.microsoft.com/technet/sysinternals/utilities/adexplorer.mspx.

Then You will need too browse to Authentication Providers in the Central Administration, Edit Authentication of your Web Application, and include the name of the provider. In the sample: LdapMembershipProvider

Then if you go back to your site, it will show you the login page.

Register the role manager (optional).

Finally you can add information for the role manager:

<roleManager defaultProvider="LdapRoleProvider" enabled="true" cacheRolesInCookie="true" cookieName=".PeopleDCRole">
<providers>
    <add
name="LdapRoleProvider"
type="Microsoft.Office.Server.Security.LDAPRoleProvider, Microsoft.Office.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71E9BCE111E9429C"
server="DC"
port="389"
useSSL="false"
groupContainer="DC=litwareinc,DC=com"
groupNameAttribute="cn"
groupMemberAttribute="member"
userNameAttribute="sAMAccountName"
dnAttribute="distinguishedName"
groupFilter="(ObjectClass=group)"
scope="Subtree"
/>
</providers>
</roleManager>

And update the authentication provider central admin.

More references to solve some issues
Namaste ;)
Imagine Think Create Share

Running Best Practice Analyzer for WSS and MOSS 2007

Posted over 5 years ago

by carlos.hm
- 1 Comments
Hi,

Today I wanted to share howto use the "Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System"

available from http://www.microsoft.com/downloads/details.aspx?familyid=cb944b27-9d6b-4a1f-b3e1-778efda07df8&displaylang=en in your environment.

As you may have read this BPA collects settings and values from data repositories including Microsoft SQL Server, Registry, and Performance Monitor.

It is nice to see the core BPA to extend to others products, although they do not leverage the same interface/help/guidance nor installation process:
1. BizTalk Server 2006 Best Practices Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=dda047e3-408e-48ba-83f9-f397226cd6d4&displaylang=en
2. SQL Server 2005 Best Practices Analyzer http://www.microsoft.com/downloads/details.aspx?familyid=DA0531E4-E94C-4991-82FA-F0E3FBD05E63&displaylang=en
3. Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System http://www.microsoft.com/downloads/details.aspx?FamilyId=CB944B27-9D6B-4A1F-B3E1-778EFDA07DF8&displaylang=en
4. Microsoft Exchange Best Practices Analyzer v2.8 http://www.microsoft.com/downloads/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&DisplayLang=en
5. Microsoft Internet Security and Acceleration (ISA) Server Best Practices Analyzer Tool http://www.microsoft.com/downloads/details.aspx?FamilyID=d22ec2b9-4cd3-4bb6-91ec-0829e5f84063&DisplayLang=en
6. Best Practice Analyzer for ASP.NET http://www.microsoft.com/downloads/details.aspx?FamilyID=d2717206-e804-415e-9173-c7b7327289e4&DisplayLang=en
7. Microsoft Commerce Server 2007 Best Practices Analyzer http://www.microsoft.com/downloads/details.aspx?FamilyID=6be6a088-d613-471a-b1a6-e80dc5050494&DisplayLang=en
8. Microsoft Systems Management Server 2003 Desired Configuration Monitoring 2.0 http://www.microsoft.com/downloads/details.aspx?FamilyId=A867FC14-DAA3-4C2A-9E65-4FBCBEC60AAA&displaylang=en
This could bring you a little confusion when using different BPAs, as there is no common UI.

Microsoft Best Practices Analyzer for Windows SharePoint Services 3.0 and the 2007 Microsoft Office System
1. First of all, download the bits from the url above.
2. execute it, this will ask for a path in order to extract the files.
3. Prepare the files
4. execute sharepointbpa.exe
There are 3 important files:
1. sharepointbpa.config.xml, Configuration file for the BPA process.
2. FormatXslTransform.xsl and ReportXslTransform.xsl, XSL Transformations to generate the report.
In order to execute sharepointbpa.exe you can first ask for the neccessary parameters:
- sharepointbpa.exe -? for general help
- sharepointbpa.exe -help analyze for specific run help.
This will bring you this information:
```
Microsoft Best Practices Analyzer for Microsoft(R) Windows(R) SharePoint(R) Services 3.0 and the 2007 Microsoft(R) Office System version 12.0.4518.1016

Copyright (C) Microsoft Corporation 2007. All rights reserved.

sharepointbpa.exe -cmd analyze 

[-rulefile <\\server\share\rules.xml>]

[-outputdirectory <\\server\share>]

[-reportformat <xml|html>]

[-substitutions <name value>[< ...>]]

Performs analysis against the specified Xml file.

rulefile: This file contains the set of rules to be run. If not specified, a default rule file located at C:\Blog Entry BPA\sharepointbpa.config.xml will be used.

outputdirectory: Specifies the directory where analysis report output files will be created. If not specified, all report files will be saved to the C:\Blog Entry BPA directory.

reportformat: Specifies the format of the report that will be generated during an analysis run. If the specified format is xml, the report format will be in xml. If the specified format is html, the report format will be in html. If a format is not specified, then html is used.

substitutions: A list of name value pair combinations that are used as substitution variables in the specified rule file. For example, substitution variable names in a rule file use the format %somevariable%. To replace all occurrences of %somevariable% in a rule file, specify 'somevariable somevalue' on the command line. Note that variable names are case sensitive; the case of the variable specified in the rule file must match the case used on the command line.
```
Running BPA

So you can start running sharepointbpa.exe -cmd analyze -servername <servername>

This will generate a log file, called spbpatrace_<unique identifier>.log and the report

sharepointbpa<number>.report.htm

If you include the third parameter -reportformat xml, this file will be sharepointbpa<number>.report.xml

After that you will be provided with a report with the results. After reading the report you will have specific instructions in order to fix them or just be aware of.

Here we can explode other rules and configurations as Bill Baer wrote about at http://blogs.technet.com/wbaer/archive/2007/04/17/understanding-the-microsoft-best-practices-analyzer-for-windows-sharepoint-services-3-0-and-the-2007-microsoft-office-system-rule-file.aspx

The point I wanted to surface is the other options we can use in the config file as:

Substitution in the Configuration node, where a node like this

<Substitution Name="SERVER_NAME">MOSS.litwareinc.com</Substitution>

will give us the option to run with sharepointbpa.exe -cmd analyze

I have attached a sample from the SQL Server BPA.

Cheers!

No results found