Sharepoint Table Of Contents Limit Web.Config Change

http://community.sharepointproconnections.com/forums/thread/27307.aspx

<add description=”CMS provider for Global navigation” NavigationType=”Global” EncodeOutput=”true” DynamicChildLimit=”75″ />

I would add that this adjustment to the XML is done in the IIS web.config (C:\inetpub\wwwroot\wss\VirtualDirectory\something.site.com80) for EACH front-end server, not the SharePoint web.config file (C:\Program Files\Common Files\Microsoft Shared\web server extension\12\CONFIG\).  Because the server will now detect that the files have been changed, an IISReset will happen and each user will get a ‘fresh copy’ of the SharePoint site.

Sharepoint Move a SubSite to A Site Collection

http://stsadm.blogspot.com/2007/09/convert-sub-site-to-site-collection.html

Sharepoint FullMask Removed By Base Permissions Customisation

http://www.cjvandyk.com/blog/Lists/Posts/Post.aspx?List=744536f4%2D127e%2D4c4a%2Dbcff%2Db85408e7e7e5&ID=225

LDAP User Fields

http://www.computerperformance.co.uk/Logon/LDAP_attributes_active_directory.htm#Hall_of_fame_LDAP_attribute_-_DN__distinguished_name_

LDAP Attribute	Example
CN – Common Name	CN=Guy Thomas.  Actually, this LDAP attribute is made up from givenName joined to SN.
description	What you see in Active Directory Users and Computers.  Not to be confused with displayName on the Users property sheet.
displayName	displayName = Guy Thomas.  If you script this property, be sure you understand which field you are configuring.  DisplayName can be confused with CN or description.
DN – also distinguishedName	DN is simply the most important LDAP attribute. CN=Jay Jamieson, OU= Newport,DC=cp,DC=com
givenName	Firstname also called Christian name
homeDrive	Home Folder : connect.  Tricky to configure
name	name = Guy Thomas.  Exactly the same as CN.
objectCategory	Defines the Active Directory Schema category. For example, objectCategory = Person
objectClass	objectClass = User.  Also used for Computer, organizationalUnit, even container.  Important top level container.
physicalDeliveryOfficeName	Office! on the user’s General property sheet
profilePath	Roaming profile path: connect.  Trick to set up
sAMAccountName	sAMAccountName = guyt.  Old NT 4.0 logon name, must be unique in the domain.  Can be confused with CN.
SN	SN = Thomas. This would be referred to as last name or surname.
userAccountControl	Used to disable an account.  A value of 514 disables the account, while 512 makes the account ready for logon.
userPrincipalName	userPrincipalName = guyt@CP.com    Often abbreviated to UPN, and looks like an email address.  Very useful for logging on especially in a large Forest.   Note UPN must be unique in the forest.

Infopath Logged On User Function

http://blogs.msdn.com/infopath/archive/2006/05/26/608092.aspx

Configure .NET For Fiddler

Clients that do not follow the Winlnet API will  bypass fiddler This includes .net. To ensure .net goes via Fiddler set the proxy as follows in web.config

<system.net>

  <defaultProxy>

  <proxy proxyaddress=”http://127.0.0.1:8888″   bypassonlocal=”False” autoDetect=”False” />

  </defaultProxy>

</system.net>

Sharepoint Web Service Communication And Ports

http://blogs.msdn.com/uksharepoint/archive/2009/01/05/sharepoint-ports-proxies-and-protocols-an-overview-of-farm-communications.aspx

One of the main type of Inter-Server communication is based around Search and Indexing. Interestingly, the communications channels used are primarily SMB which means that SMB must be allowed through firewalls if different servers are on different network segments.

Search & Index has 3 main types of activity, they are as follows:

• Search Administration. This is simple HTTP traffic to the Office SharePoint Server Web Services which occurs on ports TCP:56737 and TCP:56738 (SSL). This is used to administer the Search service.
• Search Crawling: This is the process of eth Index server crawling SharePoint and external content. During a crawl there is heavy traffic both between eth Index server and the content and the Index Server and SQL
• Search Index Propagation: During an crawl, the Index Server will propagate the indexes to the Query server. This occurs throughout the indexing process (it does not wait until indexing has complete to propagate). This communication occurs over SMB which means that an SMB channel must be open between eth Index and Query servers.
• Search Query Execution: This is the process of a user executing a query on eth Web Front End Server and it being passed to the Query server for execution. This also occurs over SMB which means that an SMB channel must be open between you Web Front End and Query Servers.

http://blogs.msdn.com/uksharepoint/archive/2009/01/12/ports-protocols-and-proxies-part-2-search-communication.aspx

The Search administration web service is specified in the file SearchAdmin.asmx. The full path to the search admin web service is therefore (for http traffic):

http://<FQDN>:56737/<SharedServiceProviderName>/Search/SearchAdmin.asmx

The administration service provides all the methods necessary to control the Search service, such as starting content source index crawls, updating scopes, etc. The web service is available to be called by custom applications as well as by the system.

BDC Quick Start

http://sharepointmagazine.net/technical/administration/everything-you-need-to-know-about-bdc-part-1-of-8

http://sharepointmagazine.net/technical/administration/everything-you-need-to-know-about-bdc-part-2-of-8

MOSS Logging For Incident and Baseline

http://blogs.msdn.com/mmcintyr/archive/2009/08/18/troubleshooting-moss-wss-performance-issues.aspx

http://blogs.msdn.com/ketaanhs/archive/2008/08/12/performance-testing-and-performance-counters-for-sharepoint-2007-moss.aspx

Office Server Search Gatherer Projects(2~Portal_Content)\Processed Documents Rate

Office Server Search Gatherer Projects(2~Portal_Content)\Document Add Rate

View The Assembly Cache

Disabling the Assembly Cache Viewer

WARNING: The following steps involve modifying the Windows Registry. If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. The author as well as Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

If you want to disable the Assembly Cache Viewer and see the GAC in all its naked glory within Windows Explorer, you can set HKLM\Software\Microsoft\Fusion\DisableCacheViewer [DWORD] to 1.

This is applicable for any assembly which is installed in the GAC. If you use the Windows Explorer, you can see those assemblies in the Windows\Assembly\GAC folder, but cannot copy them out of there. To access the internal structure, use the command shell, by typing cmd in the Start->Run menu. Navigate to the GAC folder and you will see all installed dll’s as folders, which inturn will contain the corresponding folders for each version. Just copy the dll’s from there to some other location and you have successfully extracted the dll’s from the GAC.

map the gac folder as a network drive from your local machine … it’s easier.

There you can enter the server name and the folder: \\SERVERNAME\FOLDER. In my case it is: \\moss2007\c$\windows\assembly. You don’t need to share the folder if you are an administrator. After the mapping you can browse the GAC and extract an assembly.