Skip Ribbon Commands
Skip to main content

RouttLogics

:

Quick Launch

 

 Error ‭[1]‬

 
Web Part Error: One of the properties of the Web Part has an incorrect format. Microsoft SharePoint Foundation cannot deserialize the Web Part. Check the format of the properties and try again.
Home
October 24
Missing Server file or server configuration issues

Server side files are referenced in the content databases, but are not installed on the server. Without these files, the sites may not function completely or the content may not render correctly. Also, upgrade or post upgrade issues may occur if these files are not available in the new version environment.The following web part(s) are referenced by the content, but they are not installed on the web server

  • Id = 25319d82-349e-c5d9-a8df-d2fefede591b, Type = Unknown, Reference = 54, Status = Missing = LightningConductorWebPart
  • Id = 2345be2b-72ed-c0c6-a5af-98e0430849d5, Type = Unknown, Reference = 8, Status = Missing = WorldClockandWeatherWebPart

The following event receiver assembly(s) are referenced by the content, but they are not installed on the web server

  • Assembly = UniqueColumnEventHandler, Version=1.0.0.0, Culture=neutral, PublicKeyToken=511d215e7c3011a4, Count = 2, Status = Missing
October 24
Removing Invalid SharePoint 2007 Features due to a Failed, Missing, or Unsuccessful Activation SharePoint WSP

Errors that could be shown in SharePoint when installing or activating a feature "An unexpected error has occurred", "Failed to compare two elements in the array" or various other error messages may be shown while activating, deactivating, or browsing to a recently failed deployment of a WSP solution .

To check or remove invalid features on SharePoint 2007 site:

  1. First, run the WssAnalyzeFeatures tool and view the Problems Log for invalid feature id (guids)
  2. Try running STSADM -o deactivatefeature -id %featureIdFromLogFile% -force
  3. Run the WssAnalyzeFeatures tool and see if the problems we're resolved.
  4. If feature can't be removed or is in a subsite for a failed WSP solution uninstall...try running the WssRemoveFeatureFromSite to forcefully invalid old features.
  5. Remove the feature ID's until WssAnalyzeFeatures shows no errors.

Here is a snippet of Scott's Blog for more information:

The usual reason for this problem is that some sites in the site collection have features assigned where the feature is not installed in the server farm. The main problem here is that you cannot easily identify which features are missing as the missing features are not reported in the error message.

To overcome this problem I have written a tool which allows to identify all features used in a site collection which are missing on the server: WssAnalyzeFeatures.

To resolve the problem you then have to install the identified missing features on the exporting server. In case that this is not possible you have to remove the features from the site collection or the affected sites. Usually this can be done using STSADM -o deactivatefeature but sometimes fails if the feature definition is not installed on the server. In this case you can use WssRemoveFeatureFromSite.

October 24
Migrate SharePoint farm that is SSRS integrated to SharePoint 2010

Backup SharePoint Content DB

Backup ReportServer and ReportServerTempDB db

Backup Encryption key on old SSRS config

Restore all three to 2010 sql backend on 2008 R2

Configure SSRS to use the restored db's

Restore Encryption Key, delete old record in keys table in ReportServer pointing to old SSRS config server

Restore Content DB

http://blogs.msdn.com/b/prash/archive/2010/05/26/steps-to-consider-when-upgrading-from-sharepoint-2007-to-2010-with-reporting-services-in-sharepoint-mode.aspx

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/aff2c04a-e9e8-4e37-8a3a-041237eaa384/

http://www.sqlservercentral.com/Forums/Topic651732-147-2.aspx

October 24
Application Pool/Web App warm up using IIS7.5 App Warm-up Module

Install the module on the W2K8r2 machine which hosts the SharePoint 2010 web applications

To configure this module with the SharePoint 2010 web application, Launch IIS Manager and click on one of your SharePoint Sites. In the middle pane, you will notice a new item listed under IIS titled, Application Warm-Up.

Double Click on Application Warm-Up.

Under Actions located on the far right pane, select Settings and enable both options.

Now we need to add a request which is usually the main page of your SharePoint Site (necessary for each Site Collections in the farm). This is under Actions, Select Add Request and enter the URL of your SharePoint Site:

At last you will need to specify your Authentication settings, otherwise the module will not work and generates errors in the event log. Under setting you can specify the user to be used by the module.

Now you are done and after an IIS reset, server reboot or application pool recycle the SharePoint 2010 in nicely warmed-up when used again.

October 24
Access is denied. Verify that either the Default Content Access Account has access…

Procedure carried out was:

1. Check the search service and content account (sp_search newly created) had full read access to the web applications in Manage Web Applications -> Select each web application required to crawl and click administrator icon, in the popup check the search service account has read permission.

2. Check the search service account had read permissions on the content databases in SQL Server.

3. Disabled loop back security check on SharePoint Web Front End server which has the search service application installed on it, I used PowerShell and the following command:

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name "DisableLoopbackCheck" -Value "1"

4. Added the hostnames used to the BackConnectionHostNames registry entry detailed in http://support.microsoft.com/kb/896861/en-gb. (make sure the FQDN and the aams are used.)

5. IISRESET

October 24
Automate PDF configuration for SharePoint 2010 via PowerShell

Configuring PDF related stuff for SharePoint 2010 (and 2007) is very simple, yet annoying and often forgotten SharePoint configuration step. There are nice articles (link, link) to help you configure it but when you do it manually chances are you will miss configure something.

I wrote a simple PowerShell script to automate this, and it will do everything for you > configure PDF Icon and PDF crawling.

Here is what you need to do:

  • Download and install the Adobe PDF iFilter
  • Configure SharePoint Foundation search service via Central Admin (or PowerShell)
  • Download the Adobe PDF icon (select Small 17 x 17) and save it to a folder on your SharePoint server as pdficon_small.gif
  • Download the script below and place it to the same folder as Adobe PDF Icon
  • Run the script as administrator from Powershell shell

Special thanks to Agnes Molnar for testing this script. If you want to learn more about PowerShell and SharePoint 2010 check SharePoint 2010 Unleashed.

cls

function Get-FileFormatDate {

param( [DateTime]$Date = [DateTime]::now )

return $Date.ToUniversalTime().toString( "yyyy-MM-dd_hh-mm-ss" )

}

if((Get-PSSnapin | Where {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) {

Add-PSSnapin Microsoft.SharePoint.PowerShell;

}

$continue = Read-Host "This script will change SharePoint configuration files, registry and will restart your IIS! Would you like to continue (Y/N)"

if($continue -eq "Y")

{

Write-Host -ForegroundColor Yellow "Configuring PDF Icon..."

$SharePointRoot = "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14";

$DocIconFolderPath = "$SharePointRoot\TEMPLATE\XML";

$DocIconFilePath = "$DocIconFolderPath\docicon.xml";

Write-Host "Creating backup of DocIcon.xml file..."

$dateNow = Get-FileFormatDate

$backupFile = "$DocIconFolderPath\Backup_DocIcon_" + $dateNow + ".xml"

Copy-Item $DocIconFilePath $backupFile

$pdfIcon = "pdficon_small.gif";

while((Get-Item $pdfIcon) -eq $null)

{

Read-Host "$pdfIcon is missing. Download it from http://www.adobe.com/misc/linking.html and place it to this folder. Press any key to continue...";

}

Copy-Item $pdfIcon "$SharePointRoot\Template\Images";

$pdfNode = select-xml -path $DocIconFilePath -xpath "/DocIcons/ByExtension/Mapping[@Key='pdf']" | select-object -expandProperty Node

if($pdfNode -eq $null)

{

$xml= [xml] (Get-Content $DocIconFilePath)

$a = $xml.selectSingleNode("/DocIcons/ByExtension")

$addnode = $xml.createElement("Mapping")

$a.AppendChild($addNode)

$keyAttribute = $xml.CreateAttribute("Key")

$keyAttribute.set_Value("pdf")

$addNode.SetAttributeNode($keyAttribute)

$valueAttribute = $xml.CreateAttribute("Value")

$valueAttribute.set_Value("pdficon_small.gif")

$addNode.SetAttributeNode($valueAttribute)

$xml.Save($DocIconFilePath)

}

Write-Host -ForegroundColor Yellow "Configuring search crawl extension..."

$searchServiceApp = Read-Host "Type the name of your search service application (e.g. Search Service Application)"

$searchApplicationName = Get-SPEnterpriseSearchServiceApplication $searchServiceApp

if($searchApplicationName -ne $null)

{

if(($searchApplicationName | Get-SPEnterpriseSearchCrawlExtension "pdf") -eq $null)

{

$searchApplicationName | New-SPEnterpriseSearchCrawlExtension "pdf"

}

}

Write-Host -ForegroundColor Yellow "Updating registry..."

if((Get-Item -Path Registry::"HKLM\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\Filters\.pdf") -eq $null)

{

$item = New-Item -Path Registry::"HKLM\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\Filters\.pdf"

$item | New-ItemProperty -Name Extension -PropertyType String -Value "pdf"

$item | New-ItemProperty -Name FileTypeBucket -PropertyType DWord -Value 1

$item | New-ItemProperty -Name MimeTypes -PropertyType String -Value "application/pdf"

}

if((Get-Item -Path Registry::"HKLM\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf") -eq $null)

{

$registryItem = New-Item -Path Registry::"HKLM\SOFTWARE\Microsoft\Office Server\14.0\Search\Setup\ContentIndexCommon\Filters\Extension\.pdf";

$registryItem | New-ItemProperty -Name "(default)" -PropertyType String -Value "{E8978DA6-047F-4E3D-9C78-CDBE46041603}"

}

Write-Host -ForegroundColor Yellow "Restarting SharePoint Foundation Search Service..."

Restart-Service SPSearch4

Write-Host -ForegroundColor Yellow "Restarting SharePoint Search Service..."

Restart-Service OSearch14

Write-Host -ForegroundColor Yellow "Restarting IIS..."

iisreset

Write-Host -ForegroundColor Green "Installation completed..."

}

October 24
Configure incoming e-mail (SharePoint Server 2010)

This article describes how to configure incoming e-mail for a server farm for Microsoft SharePoint Server 2010. This article also describes how to install and configure the SMTP service that you must use to enable incoming e-mail.

In this article:

Overview

When incoming e-mail is enabled, SharePoint sites can receive and store e-mail messages and attachments in lists and libraries. This article describes two scenarios, one basic and one advanced. The basic scenario applies to a single-server farm environment and is recommended if you want to use default settings, whereas the advanced scenario applies to a single-server farm or a multiple-server farm and contains several advanced options from which to choose. For more information, see Plan incoming e-mail (SharePoint Server 2010).

Before you perform these procedures, confirm that:

  • Your system is running SharePoint Server 2010.
  • You have read Plan incoming e-mail (SharePoint Server 2010).
  • If you are using the basic scenario, each SharePoint front-end Web server must be running the Simple Mail Transfer Protocol (SMTP) service and the Microsoft SharePoint Foundation Web Application service.
  • If you are using the advanced scenario, you can use one or more servers in the server farm to run the SMTP service and to have a valid SMTP server address. Alternatively, you must know the name of a server outside the farm that is running the SMTP service and the location of the e-mail drop folder.

If you have not installed and configured the SMTP service and do not choose to use an e-mail drop folder, you must perform the following procedures before you configure incoming e-mail:

  • Install and configure the SMTP service.

Install and configure the SMTP service

Incoming e-mail for SharePoint Server 2010 uses the SMTP service. You can use the SMTP service in one of two ways. You can install the SMTP service on one or more servers in the farm, or administrators can provide an e-mail drop folder for e-mail that is forwarded from the service on another server. For more information about the e-mail drop folder option, see Plan incoming e-mail (SharePoint Server 2010).

Install the SMTP service

If you are not using a drop folder for e-mail, the SMTP service must be installed on every front-end Web server in the farm that you want to configure for incoming e-mail. To install the SMTP service, use the Add Features Wizard in Server Manager. After the procedure is complete, a default SMTP configuration has been created. You can customize this default SMTP configuration to meet the requirements of your environment.

To install the SMTP service

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the local computer.
  • Click Start, point to Administrative Tools, and then click Server Manager.
  • In Server Manager, click Features.
  • In Features Summary, click Add Features to open the Add Features Wizard.
  • On the Select Features page, select SMTP Server.
  • In the Add Features Wizard dialog box, click Add Required Features, and then click Next.
  • On the Confirm Installation Selections page, click Install.
  • On the Installation Results page, ensure that the installation finished successfully, and then click Close.

Install IIS 6.0 Management tools

To manage the SMTP service on Windows Server 2008 and Windows Server 2008 R2, you must use Internet Information Services (IIS) 6.0 Manager.

To install IIS 6.0 Manager

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the local computer.
  • Click Start, point to Administrative Tools, and then click Server Manager.
  • In Server Manager, click Roles.
  • In Role Services, click Add Role Services.
  • On the Select Role Services page, select Management Tools and IIS 6 Management compatibility, and then click Install.

Configure the SMTP service

After you install the SMTP service, you configure it to accept e-mail from the mail server for the domain. You can decide to accept relayed e-mail from all servers except those that you specifically exclude. Alternatively, you can block e-mail from all servers except those that you specifically include. You can include servers individually, or in groups by subnet or domain.

After you configure the service, set it to start automatically.

To configure the SMTP service

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the local computer.
  • Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) 6.0 Manager.
  • In IIS Manager, expand the server name that contains the SMTP server that you want to configure.
  • Right-click the SMTP virtual server that you want to configure, and then click Start.
  • Right-click the SMTP virtual server that you want to configure, and then click Properties.
  • On the Access tab, in the Access control area, click Authentication.
  • In the Authentication dialog box, verify that Anonymous access is selected.
  • Click OK.
  • On the Access tab, in the Relay restrictions area, click Relay.
  • To enable relaying from any server, click All except the list below.
  • To accept relaying from one or more specific servers, follow these steps:
  1. Click Only the list below.
  2. Click Add, and then add servers one at a time by IP address, or in groups by using a subnet or domain.
  3. Click OK to close the Computer dialog box.
  1. Click OK to close the Relay Restrictions dialog box.
  2. Click OK to close the Properties dialog box.

To set the SMTP service to start automatically

  1. Click Start, point to Administrative Tools, and then click Services.
  2. In Services, right-click Simple Mail Transfer Protocol (SMTP), and then select Properties.
  3. In the Simple Mail Transfer Protocol (SMTP) Properties dialog box, on the General tab, in the Startup type list, select Automatic.
  4. Click OK.

Configure incoming e-mail in a basic scenario

You can use the following procedure to configure incoming e-mail in a basic scenario by selecting the Automatic settings mode and using the default settings. After the procedure is complete, users can send e-mail to lists and libraries.

To configure incoming e-mail in a basic scenario

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the computer that is running the SharePoint Central Administration Web site.
  • In Central Administration, click System Settings.
  • On the System Settings page, in the E-Mail and Text Messages (SMS) section, click Configure incoming e-mail settings.
  • If you want to enable sites on this server to receive e-mail, on the Configure Incoming E-Mail Settings page, in the Enable Incoming E-Mail section, click Yes.
  • Select the Automatic settings mode.
  • In the Incoming E-Mail Server Display Address section, in the E-mail server display address box, type a display name for the e-mail server, for example, mail.fabrikam.com.
  • Use the default settings for all other sections, and then click OK.

After you configure incoming e-mail, users who have Manage Lists permissions can configure e-mail–enabled lists and document libraries.

Configure incoming e-mail in an advanced scenario

You can use the following procedure to configure incoming e-mail in an advanced scenario by selecting the Advanced settings mode and additional options that you want to use for your incoming e-mail environment. After the procedure is complete, users can send e-mail to lists and libraries.

Note:

You can also use the Automatic settings mode in an advanced scenario. The main difference is that in the Automatic settings mode, you can select to receive e-mail that has been routed through a safe-e-mail server application, whereas in the Advanced settings mode, you can instead specify a drop folder. For more information, see Plan incoming e-mail (SharePoint Server 2010).

Several of these steps mention pre-requisite procedures that are documented in the Prepare your environment for incoming e-mail in an advanced scenario section of this article.

To configure incoming e-mail in an advanced scenario

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the computer that is running the SharePoint Central Administration Web site.
  • In Central Administration, click System Settings.
  • On the System Settings page, in the E-Mail and Text Messages (SMS) section, click Configure incoming e-mail settings.
  • If you want to enable sites on this server to receive e-mail, on the Configure Incoming E-mail Settings page, in the Enable Incoming E-Mail section, click Yes.
  • Select the Advanced settings mode.

    If you select Advanced, you can specify a drop folder instead of using an SMTP server.

Note:

You can also select the Automatic settings mode and select whether to use Directory Management Service and whether to accept e-mail from all e-mail servers or from several specified e-mail servers. For more information, see Plan incoming e-mail (SharePoint Server 2010).

  • If you want to connect to Directory Management Service, in the Directory Management Service section, click Yes.

    If you select this option, you must first configure Active Directory Domain Services (AD DS). If you use Exchange Server, you must also configure the DNS Manager and add an SMTP connector. For more information, see the "Configure AD DS to be used with Directory Management Service", "Configure DNS Manager", and "Add an SMTP connector in Exchange Server 2010" sections later in this article.

    • In the Active Directory container where new distribution groups and contacts will be created box, type the name of the container in the format OU=ContainerName, DC=domain, DC=com, where ContainerName is the name of the OU in AD DS, domain is the second-level domain, and com is the top-level domain.

Note:

The application pool identity account for Central Administration must be delegated the Create, delete, and manage user accounts task for the container. Access is configured in the properties for the OU in AD DS.

  • In the SMTP mail server for incoming mail box, type the name of the SMTP mail server. The server name must match the FQDN in the A resource record entry for the mail server in DNS Manager.
  • To accept only messages from authenticated users, click Yes for Accept messages from authenticated users only. Otherwise, click No.
  • To enable users to create distribution groups from SharePoint sites, click Yes for Allow creation of distribution groups from SharePoint sites. Otherwise, click No.
  • Under Distribution group request approval settings, select the actions that will require approval. Actions include the following:
    • Create new distribution group
    • Change distribution group e-mail address
    • Change distribution group title and description
    • Delete distribution group
  • If you want to use a remote Directory Management Service, select Use remote.

    If you select this option and you are using Exchange Server, you must configure the DNS Manager and add an SMTP connector. For more information, see the "Configure DNS Manager" and "Add an SMTP connector in Exchange Server 2010" sections later in this article. The AD DS has most likely already been configured, so you do not need to do this.

    • In the Directory Management Service URL box, type the URL of the Directory Management Service that you want to use. The URL is typically in the following format: http://server:adminport/_vti_bin/SharePointEmailWS.asmx.
    • In the SMTP mail server for incoming mail box, type the name of the SMTP mail server. The server name must match the FQDN in the A resource record entry for the mail server in DNS Manager on the domain server.
    • To accept messages from authenticated users only, click Yes for Accept messages from authenticated users only. Otherwise, click No.
    • To allow creation of distribution groups from SharePoint sites, click Yes for Allow creation of distribution groups from SharePoint sites. Otherwise, click No.
  • If you do not want to use Directory Management Service, click No.
  • In the Incoming E-Mail Server Display Address section, in the E-mail server display address box, type a display name for the e-mail server (for example, mail.fabrikam.com). You typically use this option together with the Directory Management Service.

Tip:

You can specify the e-mail server address that is displayed when users create an incoming e-mail address for a list or group. Use this setting together with Directory Management Service to provide an e-mail server address that is easy to remember.

  • In the E-Mail Drop Folder section, in the E-mail drop folder box, type the name of the folder from which SharePoint 2010 Timer service retrieves incoming e-mail from the SMTP service. If you select this option, ensure that you configure the necessary permissions to the e-mail drop folder. For more information, see the "Configure permissions to the e-mail drop folder" section later in this article.

    It is useful to have a dedicated e-mail drop folder if the default e-mail drop folder is full or almost full.

    Ensure that the logon account for the SharePoint 2010 Timer service has Modify permissions on the e-mail drop folder. For more information, see "To configure e-mail drop folder permissions for the logon account for the SharePoint 2010 Timer service" procedure later in this article.

Note:

This option is available only if you selected Advanced settings mode.

  • In the Safe E-Mail Servers section, select whether you want to accept e-mail from all e-mail servers or from several specified e-mail servers.

Note:

This option is available only if you selected Automatic settings mode.

  • Click OK.

After you configure incoming e-mail, site administrators can configure e-mail–enabled lists and document libraries.

If you selected Directory Management Service, contact addresses that are created for document libraries appear automatically in Active Directory Users and Computers. The addresses are displayed in the OU of AD DS for SharePoint Server 2010 and must be managed by the administrator of AD DS. The AD DS administrator can add more e-mail addresses for each contact. For more information about AD DS, see Using Active Directory Service (http://go.microsoft.com/fwlink/?LinkId=151348).

Alternatively, the Exchange Server computer can be configured by adding a new Exchange Server Global recipient policy. The policy automatically adds external addresses that use the second-level domain name and not the subdomain or host name for SharePoint Server 2010. For more information about how to manage Exchange Server, see Recipient Configuration Node (http://go.microsoft.com/fwlink/?LinkId=151348).

Prepare your environment for incoming e-mail in an advanced scenario

Before you configure incoming e-mail in an advanced scenario, you need to perform additional procedures depending on how you want your incoming e-mail environment to work.

If you want to use Directory Management Service, you must first configure AD DS, and if you use Exchange Server, you must also configure the DNS Manager and add an SMTP connector.

If you want to use a specific e-mail drop folder, ensure that you configure the necessary permissions to the e-mail drop folder.

In this section:

  • Configure AD DS to be used with Directory Management Service
  • Configure DNS Manager
  • Add an SMTP connector in Microsoft Exchange Server 2010
  • Configure permissions to the e-mail drop folder

Configure AD DS to be used with Directory Management Service

If you plan to use Directory Management Service you should first create an organizational unit (OU) and make the necessary configurations in AD DS.

To use Directory Management Service on a SharePoint farm or on a remote server farm, you must configure the application pool identity account for the SharePoint Central Administration Web site to have the Create, delete, and manage user accounts user right to the container that you specify in AD DS. The preferred way to do this is by assigning the right to the application pool identity account for the SharePoint Central Administration Web site. An AD DS administrator must set up the OU and assign the Create, delete, and manage user accounts right to the container. The advantage of using Directory Management Service on a remote server farm is that you do not have to assign rights to the OU for multiple farm service accounts.

The following procedures are performed on a domain controller that runs Windows Server 2008 with DNS Manager. In some deployments, these applications might run on multiple servers in the same domain.

To create an OU in AD DS

  • Verify that you have the following administrative credentials:
    • You must be a member of the Domain Administrators group or a delegated authority for domain administration on the domain controller that is running DNS Manager.
  • Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  • In Active Directory Users and Computers, right-click the folder for the second-level domain that contains your server farm, point to New, and then click Organizational Unit.
  • Type the name of the OU, and then click OK.

    After you create the OU, you must delegate the Create, delete, and manage user accounts right to the container of the OU to manage the user accounts.

To delegate the right to the application pool identity account for Central Administration

  • Verify that you have the following administrative credentials:
    • You must be a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration.
  • In Active Directory Users and Computers, find the OU that you created.
  • Right-click the OU, and then click Delegate control.
  • On the Welcome page of the Delegation of Control Wizard, click Next.
  • On the Users and Groups page, click Add, and then type the name of the application pool identity account that the Central Administration uses.
  • In the Select Users, Computers, and Groups dialog box, click OK.
  • On the Users or Groups page of the Delegation of Control Wizard, click Next.
  • On the Tasks to Delegate page of the Delegation of Control Wizard, select the Create, delete, and manage user accounts check box, and then click Next.
  • On the last page of the Delegation of Control Wizard, click Finish to exit the wizard.

To create and delete child objects, you must also delegate Create all Child Objects and Delete all Child Objects control of the OU to the application pool identity account for Central Administration. After this procedure is complete, the application pool identity account for Central Administration has Create all Child Objects and Delete all Child Objects control on the OU, and you can enable incoming e-mail.

To delegate Create all Child Objects and Delete all Child Objects control of the OU to the application pool identity account for Central Administration

  • Verify that you have the following administrative credentials:
    • You must be a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration.
  • Right-click the OU, and then click Delegate control.
  • In the Delegation of Control Wizard, click Next.
  • Click Add, and then type the name of the application pool identity account for Central Administration.
  • Click OK.
  • Click Next.
  • On the Tasks to Delegate page of the Delegation of Control Wizard, select Create a custom task to delegate, and then click Next.
  • Click This folder, existing objects in this folder, and creation of new objects in this folder, and then click Next.
  • In the Permissions section, select Create all Child Objects and Delete all Child Objects.
  • Click Next.
  • On the last page of the Delegation of Control Wizard, click Finish to exit the wizard.

Delegating Create all Child Objects and Delete all Child Objects control of the OU to the application pool identity account for Central Administration enables administrators to enable e-mail for a list. After these controls have been delegated, administrators cannot disable e-mail for the list or document library because the Central Administration account tries to delete the contact from the whole OU instead of from the list.

To avoid this problem, you must add Delete Subtree permissions for the application pool identity account for Central Administration. Use the following procedure to add these permissions. After this procedure is complete, you can disable incoming e-mail for a list.

To add Delete Subtree permissions for the application pool identity account for Central Administration

  • Verify that you have the following administrative credentials:
    • You must be a member of the Domain Administrators group or the Enterprise Administrators group in AD DS, or a delegated authority for domain administration.
  • In Active Directory Users and Computers, click the View menu, and then click Advanced Features.
  • Right-click the OU, and then click Properties.
  • In the Properties dialog box, click the Security tab, and then click Advanced.
  • In the Permission Entries area, double-click the application pool identity account for Central Administration.

Note:

If the application pool identity account is listed more than once, select the first one.

  • In the Permissions area, select Allow, for Delete Subtree.
  • Click OK to close the Permissions dialog box.
  • Click OK to close the Properties dialog box.
  • Click OK to close Active Directory Users and Computers.

After you add these permissions, you must restart Internet Information Services (IIS) for the farm.

For more information, see Active Directory Users, Computers, and Groups (http://go.microsoft.com/fwlink/?LinkId=151331).

Configure DNS Manager

If you are using Exchange Server and are routing e-mail internally in your organization, you must create a host (A) resource record in DNS Manager to associate DNS domain names of computers (or hosts) to their IP addresses. Your organization might have already configured DNS Manager and created an A resource record. If not, then use the following procedure.

To create an A resource record for a subdomain

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the local computer.
  • In DNS Manager, select the forward lookup zone for the domain that contains the subdomain for SharePoint Server 2010.
  • Right-click the zone, and then click New Host (A or AAAA).
  • In the New Host dialog box, in the Name text box, type the host or subdomain name for SharePoint Server 2010.
  • In the Fully qualified domain name (FQDN) text box, type the FQDN for the server that is running SharePoint Server 2010. This is typically in the format subdomain.domain.com.

Note:

Ensure that the domains that are listed under the SMTP server in IIS match the FQDN of the server that receives e-mail. If they do not match, you must create a local domain, which is described in the following procedure.

  • In the IP address text box, type the IP address to which you want the FQDN to resolve.
  • Click Add Host.
  • In the message that confirms the creation of the host record, click OK.
  • In the New Host dialog box, click Done.

    The A resource record now appears in DNS Manager.

If you use the E-mail server display address option and if the e-mail address to which you are sending e-mails is not the same as your machine name, you must create a local domain.

To create a local domain

  1. Click Start, point to Administrative Tools, and then click Internet Information Services (IIS) 6.0 Manager.
  2. In IIS Manager, expand the SMTP server.
  3. Right-click Domains, and on the Action menu, point to New, and then click Domain.
  4. In the New SMTP Domain Wizard dialog box, select Alias, and then click Next.
  5. In the Domain Name area, in the Name box, type the address of the mail that is to be received by this domain.

    This address must be the same as the one that you specified in step 4 in the "To Create an A Resource Record for the Subdomain" procedure, and in step 6b in the "To Configure Incoming E-Mail in an Advanced Scenario" procedure.

  6. Click Finish.
  7. In the message that confirms the creation of the host record, click OK.

Note:

Restart the SMTP server so that any e-mail messages that are still in the Queue folder move to the Drop folder. The messages are then sent by the SharePoint 2010 Timer service to their destination list or library.

Note:

If you are routing e-mail from outside your organization to an SMTP server, you must use an MX record. For more information, see Add a mail exchanger (MX) resource record to a zone (http://go.microsoft.com/fwlink/?LinkId=150827).

Add an SMTP connector in Microsoft Exchange Server 2010

An SMTP connector gives you more control over the message flow in your organization. Other reasons to use an SMTP connector are to set delivery restrictions or to specify a specific address space. If you use Exchange Server to route incoming e-mail to SharePoint lists and libraries, you must have an SMTP connector so that all mail that is sent to the SharePoint Server 2010 domain uses the SharePoint Server 2010 servers that are running the SMTP service.

Use the following procedure to add an SMTP connector in Exchange Server. After the procedure is complete, the SMTP connector ensures that incoming e-mail messages are sent to the correct list and library in the farm.

To add an SMTP connector in Exchange Server

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the computer that is running Exchange Server.
  • In Exchange Management Console, expand the Organization Configuration group, right-click Hub Transport, point to New Send Connector.

    The New Send Connector wizard appears.

  • On the Introduction page, do the following and then click Next:
  1. In the Name box, type a name for the SMTP connector.
  2. In the Select the intended use for this Send connector box, select the Custom usage type for the connector.
  1. On the Address Space page, click Add, and then click SMTP Address Space.
  2. In the SMTP Address Space dialog box, do the following:
    1. In the Address box, type an e-mail domain for the connector.
    2. In the Cost box, assign an appropriate cost. By default, the cost is 1.
  3. Click OK to return to the Address Space page, and then click Next.
  4. On the Network settings page, select Use domain name system (DNS) "MX" records to route mail automatically, and then click Next.
  5. On the Source Server page, click Next.

    The Source server page only appears on Hub Transport servers. By default, the Hub Transport server that you are currently working on is listed as a source server.

  6. On the New Connector page, review your options and then click New to create the new send connector.
  7. On the Completion page, ensure that the send connector was created, and then click Finish.

    In the Hub Transport pane, you can see that the send connector has been enabled automatically.

For more in-depth information, see Create an SMTP Send Connector (http://go.microsoft.com/fwlink/?LinkId=195321).

Configure permissions to the e-mail drop folder

You can specify a particular e-mail drop folder, which enables SharePoint Server 2010 to retrieve incoming e-mail from a network share on another server. You can use this option if you do not want to use an SMTP service. However, the drawback of using this option is that SharePoint Server 2010 cannot detect configuration changes on the remote e-mail server that is delivering e-mail to the drop folder. The result is that SharePoint Server 2010 cannot retrieve e-mail if the location of the e-mail messages has changed. However, this feature is useful if the default e-mail drop folder is full or almost full.

If you specified an e-mail drop folder, you must ensure that the application pool identity accounts for Central Administration and for the Web application have the required permissions to the e-mail drop folder.

Configure e-mail drop folder permissions for the application pool identity account for a Web application

If your deployment uses different application pool identity accounts for Central Administration and for one or more Web applications, each application pool identity account must have permissions to the e-mail drop folder. If the application pool identity account for the Web application does not have the required permissions, e-mail will not be delivered to document libraries on that Web application.

In most cases, when you configure incoming e-mail and select an e-mail drop folder, permissions are added for the following worker process groups:

  • WSS_Admin_WPG, which includes the application pool identity account for Central Administration and the logon account for the SharePoint 2010 Timer service, and has Full Control permissions.
  • WSS_WPG, which includes the application pool accounts for Web applications, and has Read & Execute, List Folder Contents, and Read permissions.

In some cases, these groups might not be configured automatically for the e-mail drop folder. For example, if Central Administration is running as the Network Service account, the groups or accounts that are needed for incoming e-mail will not be added when the e-mail drop folder is created. Check to find out whether these groups have been added automatically to the e-mail drop folder. If the groups have not been added automatically, you can add them or add the specific accounts that are required.

To configure e-mail drop folder permissions for the application pool identity account for a Web application

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the computer that contains the e-mail drop folder.
  • In Windows Explorer, right-click the drop folder, click Properties, and then click the Security tab.
  • On the Security tab, under the Group or user names box, click the Edit button.
  • In the Permissions for Windows Explorer dialog box, click the Add button.
  • In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the worker process group or application pool identity account for the Web application, and then click OK.

Note:

This account is listed on the Identity tab of the Properties dialog box for the application pool in IIS.

  • In the Permissions for User or Group box, next to Modify, select Allow.
  • Click OK.

Configure e-mail drop folder permissions for the logon account for the SharePoint 2010 Timer service

Ensure that the logon account for the SharePoint 2010 Timer service has Modify permissions on the e-mail drop folder. If the logon account for the service does not have Modify permissions, e-mail–enabled document libraries will receive duplicate e-mail messages.

To configure e-mail drop folder permissions for the logon account for the SharePoint 2010 Timer service

  • Verify that you have the following administrative credentials:
    • You must be a member of the Administrators group on the computer that contains the e-mail drop folder.
  • In Windows Explorer, right-click the drop folder, click Properties, and then click the Security tab.
  • On the Security tab, under the Group or user names box, click the Edit button.
  • In the Permissions for Windows Explorer dialog box, click the Add button.
  • In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the logon account for the SharePoint 2010 Timer service, and then click OK.

Note:

This account is listed on the Log On tab of the Properties dialog box for the service in the Services console.

  • In the Permissions for User or Group box, next to Modify, select Allow.
  • Click OK.

Are attachments missing from e-mail messages that are sent to a SharePoint document library?

If attachments are missing from e-mail messages that are sent to a SharePoint Server 2010 document library, it might be because you associated the document library with an e-mail address. When you do this, Directory Management Service may not add the following two attributes:

  • internet Encoding = 1310720
  • mAPIRecipient = false

You must use Active Directory Service Interfaces (ADSI) to manually add these two missing attributes.

Note:

On servers that are running Windows Server 2008 or Windows Server 2008 R2, ADSI Edit is installed when you install the AD DS role to make a server a domain controller. You can also install Windows Server 2008 Remote Server Administration Tools (RSAT) on domain member servers or stand-alone servers. For more information, see Installing or Removing the Remote Server Administration Tools Pack (http://go.microsoft.com/fwlink/?LinkId=143345).

To add attributes by using ADSI Edit

  1. Click Start, and then click Run.
  2. In the Run dialog box, type Adsiedit.msc, and then click OK.
  3. In the ADSI Edit window, expand ADSI Edit, expand Domain [DomainName], expand DC=DomainName, DC=com, and then expand CN=Users.
  4. Right-click the user name to which you want to add the missing attributes, and then click Properties.
  5. In the Properties dialog box, double-click internet Encoding on the Attribute Editor tab.
  6. In the Integer Attribute Editor dialog box, type 1310720 in the Value box, and then click OK.
  7. In the Properties dialog box, double-click mAPIRecipient on the Attribute Editor tab.
  8. In the Boolean Attribute Editor dialog box, click False, and then click OK two times.

See Also

Concepts

Plan incoming e-mail (SharePoint Server 2010)

October 24
Install and Configure SharePoint 2010 with no Database GUIDS (except PerformancePoint)

This is a blog post I've been meaning to write for a long time and have been slowly revising the content and steps. I also can't take credit for all the steps below, I gathered them from various resources, blogs, etc. At the end of the post I will list all of the places I gathered these steps from. This is also not the only way to do this, it's just the way I have documented and how I go about configuring a SharePoint farm.

Server Installation and Prep Work

1. Decide on your SQL Server you will use

2. Configure SharePoint Accounts in AD. The minimum you will need is 6:

  • SPAdmin (admin)
  • SPService (services)
  • SPApp (Web Application App Pools)
  • SPSearch (search service)
  • SPCrawl (crawl service)
  • SP_UPS (user profile synchronization service)

3. Make sure the SPAdmin has the following rights:

  • Local Admin on the SharePoint Servers (just for the Installation)
  • SQL Rights: dbcreator, public, securityadmin

4. Log into your SharePoint Servers and Install the SharePoint 2010 Bits

5. If the latest Cumulative Updates haven't been install, download those and install those right after installing the bits.

6. Disable the Loopback Check (http://support.microsoft.com/kb/896861)

7. Restart the server

Configure Central Administration

1. Right-click on "SharePoint 2010 Management Shell" and "Run As Administrator" – I just created a shortcut on my desktop

2. In Powershell Run:

New-SPConfigurationDatabase –DatabaseName "SP2010_Config" –DatabaseServer "[ServerName]" –AdministrationContentDatabaseName "SP2010_Admin_Content" –Passphrase (ConvertTo-SecureString "[YourPassPhrase]" –AsPlaintext –Force) –FarmCredentials (Get-Credential)

**Notes**

  • For [ServerName] localhost will NOT work if you are running SQL on your SharePoint box (usually only likely in a dev environment)
  • Since not everyone that install/configures SharePoint is always a DB Expert, when using a SQL Named Instance:
    • A common error you may get if using a named instance will be something like: "Connot connect to database master at SQL server at [SQLServer\Instance]. The database might not exist, or the current user does not have permission to connect to it."
    • SQL Name Instances use Dynamic Ports, before running the command above, open up SQL Configuration Managers and assign a static port to your Named Instance – http://msdn.microsoft.com/en-us/library/ms177440.aspx
    • Modify the command above slightly…for the [ServerName] use: [ServerName]\[InstanceName],[PortNumber] as an example: "SQLServer2008\SP2010,1433"
    • Create an Incoming Rule on your SQL Server to allow connections through the port you specify for your instance.Install-SP

3. Enter domain\SPAdmin and the associated password in the resulting Credential Request box.

4. Close the PowerShell Window

5. Re-Open PowerShell again as administrator

6. Run the following PowerShell Commands

  • Install-SPHelpCollection –All
  • Initialize-SPResourceSecurity
  • Install-SPService (If you install a standalone server, something I never recommend, run 'Install-SPService –Provision' instead.
  • Install-SPFeature –AllExistingFeatures
  • New-SPCentralAdministration –Port 9999 –WindowsAuthProvider "NTLM" (you can pick any port here you want to)
  • Install-SPApplicationContent

7. Central Administration is now configured. You can got to the shortcut in your start menu or run "start iexplore http://[servername]:9999" from PowerShell.

Configure the User Profile Service

I'm not even going to try to type out the steps or guide you in the right direction here. Just follow Spence Harbar's steps EXACTLY that he posted here – http://www.harbar.net/articles/sp2010ups.aspx

You may have a few minor tweaks to the steps based on user accounts, but the process for getting the profile synchronization service is solid!!

Once your done with this, you may have an error that starts showing up in your event log about the Taxonomy Picker, to eliminate this error do the following:

  1. Navigate to \14\Template\ControlTemplates
  2. Rename TaxonomyPicker.ascx to TaxonomyPicker.ascx.broken
  3. Remember you did this incase it is actually used in an update to SharePoint 2010 in the future.

***I used the same Application Pool for all my services (the same Application Pool Account I set up when configuring the User Profile Synchronization Service). In my case it is SharePoint Web Services Default. So I will use this Application Pool for all Service Applications going forward. Wherever you see this application pool name used in the future, you can replace it with your own application pool name or a new one if you want separate application pools for every service. Also, wherever you see –Name "[somename]" or –DatabaseName –"[somename]" going forward you can replace [somename] using your own naming conventions. ***

Configure Search Services

  1. Open up SharePoint 2010 Management Shell as an Administrator again.
  2. Enter the following commands in PowerShell:
  3. $searchapp = New-SPEnterpriseSearchServiceApplication –Name "Search Service Application" –ApplicationPool "SharePoint Web Services Default" –DatabaseName "SP2010_Search_Service"
  4. $proxy = New-SPEnterpriseSearchServiceApplicationProxy –name "Search Service Application Proxy" –Uri $searchapp.uri.absoluteURI
  5. $proxy.status *It should return "Online", if not enter $proxy.status = "online"*
  6. $changestatus.update
  7. $si = Get-SPEnterpriseSearchServiceInstance –local
  8. $si.status *If it's disabled run Start-SPEnterpriseSearchServiceInstance –identity $si*
  9. Set-SPEnterpriseSearchAdministrationComponent –SearchApplication $searchapp –SearchServiceInstance $si
  10. $ct = $searchapp | New-SPEnterpriseSearchCrawlTopology
  11. $csid = $searchapp.CrawlStores | select id
  12. $CrawlStore = $searchapp.CrawlStores.item($csid.id)
  13. $hname = hostname **hostname is for a single server, this is the servername were you want the crawl component to reside**
  14. New-SPEnterpriseSearchCrawlComponent –CrawlTopology $ct –CrawlDatabase $CrawlStore –SearchServiceInstance $hname
  15. $ct | Set-SPEnterpriseSearchCrawlTopology –active
  16. $qt = $searchapp | New-SPEnterpriseSearchQueryTopology –partitions 1
  17. $p1 = ($qt | Get-SPEnterpriseSearchIndexPartition)
  18. New-SPEnterpriseSearchQueryComponent –IndexPartition $p1 –QueryTopology $qt –SearchServiceInstance $si
  19. $PropDB = $searchapp | Get-SPEnterpriseSearchPropertyDatabase
  20. $p1 | Set-SPEnterpriseSearchIndexPartition –PropertyDatabase $PropDB
  21. $qt | Set-SPEnterpriseSearchQueryTopology –Active

Usage Application and Usage Analysis Service

  1. Your Usage Application may have already been provisioned in one of the previous steps, if it was, go into "Manage Service Applications" and delete it. Check the box to delete associated data as well.
  2. Once again in your SharePoint 2010 Management Shell enter the following:
  3. New-SPUsageApplication –Name "SharePoint Usage Application Service" –DatabaseName "SP2010_Usage"
  4. $App = New-SPSubscriptionSettingsServiceApplication –ApplicationPool "SharePoint Web Services Default" –Name "Subscription Service Application" –DatabaseName "SP2010_Subscription"
  5. $proxy = New-SPSubscriptionSettingsServiceApplicationProxy –ServiceApplication $App
  6. Get-SPServiceInstance | where {$_.TypeName –eq "Windows SharePoint Services Subscription Settings Service"} | Start-SPServiceInstance
  7. $StagingDB = "<StagingDatabases><StagingDatabase ServerName='[SQLServerName]' DatabaseName='SP2010_Web_Analytics_Service_Staging'/></StagingDatabases>"
  8. $ReportingDB = "<ReportingDatabases><ReportingDatabase ServerName='[SQLServerName]' DatabaseName='SP2010_Web_Analytics_Service_Reporting'/></ReportingDatabases>"
  9. $webanalytics = New-SPWebAnalyticsServiceApplication –ApplicationPool "SharePoint Web Services Default" –ListOfReportingDatabases $ReportingDB –ListOfStagingDatabases $StagingDB –Name "Web Analytics Service Application"
  10. New-SPWebAnalyticsServiceApplicationProxy –Name "Web Analytics Service Application Proxy" –ServiceApplication $webanalytics
  11. . $Usage = Get-SPServiceApplicationProxy | where {$_.TypeName
    -eq "Usage and Health Data Collection Proxy"}
  12. $Usage.Provision()

At this point in time, navigate to "Services on Server" and start all the service you want running on their respective servers.

State Service Application

  1. While still in the SharePoint Management Console enter the following PowerShell Commands:
  • $serviceapp = New-SPStateServiceApplication –Name "State Service Application"
  • New-SPStateServiceDatabase –Name "SP2010_State_Service" –ServiceApplication $serviceapp
  • New-SPStateServiceApplicationProxy –Name "State Service Application Proxy" –ServiceApplication $serviceapp –DefaultProxyGroup

Secure Store Service

At this point in time, navigate to "Services on Server" and make sure the Secure Store Service on the Server you wish it to run on.

The secure store service is implemented in SharePoint 2010 to replace SSO. Rather than get into all the details of it here, there are several good resources on TechNet explain the Secure Store and how to configure it. The Secure Store Service Application can be initially configured through Central Administration allowing you to create the custom named database (without any GUIDs). However, once this has been created, there are some additional management/configuration tasks that have to take place within the Service Application. I use these three TechNet articles as reference when performing the rest of the configuration tasks.

PerformancePoint Service Application

Again, make sure you the the PerformancePoint Service has been started before creating the PerformancPoint Service Application.

From everything I can find, right now this can either be done via PowerShell or Central Administration, but unfortunately, no matter which way you provision PerformancePoint, there is no way to set a custom name for that database. If I discover a way I'll update this post with the steps.

The Rest of It

That should take care of everything that needs to be done in your SharePoint 2010 Management Shell. The rest of the services can be configured through Central Administration. Once you've reached this point, open up Central Administration. Go to "Services on Server" and start the rest of the services you need. This includes the Foundation Search Service that can be set up through the GUI.Next go to "Manage Service Applications" and add the rest of the Service Applications here that you need.

**As you go through setting everything up the GUI make sure to pay attention to where you can name your databases so you can continue keeping your consistent naming without the GUIDs**

Now you should have something that looks a lot like these screen shots below:

Once I got to this point, I ran the PowerShell script found here – http://www.sharepointconfig.com/2011/01/instant-sharepoint-health-analysis/ in order to instantly see any issues I still had with my farm configuration. From this report I went in and took care of a few remaining issues. Some of the issues I encountered were things that should have been done initially and thus resulted in some updates to this blog post.

If you get an error similar to: "WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa] is referenced [6] times in the database" after running the SharePoint Health Analyzer, there is a simple "fix" to get rid of this error here – http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2009/12/09/Missing-Server-Side-Dependencies-_2D00_-8d6034c4_2D00_a416_2D00_e535_2D00_281a_2D00_6b714894e1aa.aspx.

If you want to skip the link, it is a simple process of:

  1. Go to "Manage Service Applications"
  2. Select "Search Service Application" and click Manage in the Ribbon
  3. Click on "Farm Search Administration" in the Quick Launch
  4. Rerun the SharePoint Health Analyzer and this error should be gone

If anyone runs across any typos or problems with the steps PLEASE let me know so I can correct the issues. Also, I can't take credit for all of the content above, as I gathered most of the info from several different locations, they all deserve credit for their work so here are the references used for this post, these links are posted in the order I used them for the steps above:

October 24
How to create a SharePoint 2010 farm with no GUIDs using PowerShell

If your Central Admin content database has a GUID at the end, that means you used the Configuration Wizard (psconfigui.exe) to build your farm. There's no shame in that at all, it's how 90% of the SharePoint farms are built. Unfortunately it does create that one bad database. We can fix that though.

Like SharePoint 2007, all of the tasks that PSConfigUI.exe do can be replaced by various command line tools. In SharePoint 2010 we can do it all with PowerShell. First, we have to NOT run the Configuration Wizard after you install SharePoint. When you get to this screen, uncheck the box to run the Configuration Wizard and click "Close."

After the box has closed, open up the SharePoint Management Shell from the Start button.

When it opens you'll get an error like this:

That's completely expected, as there is no farm to access yet. No worries though, we'll remedy that. We will run the commands below to build our farm. I'll include the text for easier copying and pasting:

New-SPConfigurationDatabase -DatabaseName SharePoint_Config -DatabaseServer sharepoint -AdministrationContentDatabaseName SharePoint_Admin_Content

Install-SPHelpCollection -All

Initialize-SPResourceSecurity

Install-SPService

Install-SPFeature -AllExistingFeatures

New-SPCentralAdministration -Port 1234 -WindowsAuthProvider "NTLM"

Install-SPApplicationContent

Here's what the first command looks like:

The point of this blog post isn't to automate the install, so I didn't provide a couple of pieces of information. When you run the New-SPConfigurationDatabase cmdlet you'll be prompted for the Farm account username and password as well as the farm passphrase. After you enter those, it will churn a bit and then you're the proud owner of a new SharePoint farm. The cmdlet above creates a config db named "SharePoint_Config" on the database server "SharePoint." It also creates the central admin content database and names it "SharePoint_Admin_Content" That's the whole reason we did all this. If we create the farm with PSConfigUI it will generate an admin database with a GUID at the end. Creating the farm with PowerShell gets us around that.

At this point you have two options, you can continue to build your farm with the PowerShell commands above. The rest will run without any other intervention. Or, you can run PSConfigUI and finish up the machine configuration. Either way is fine and gets you the same GUIDless farm. The PowerShell cmdlets above will create Central Admin on port 1026 and set it to use NTLM.

October 24
DVWP "New" image

<xsl:if test="ddwrt:IfNew(string(@Created))"><IMG SRC="/_layouts/1033/images/new.gif" alt="New" /></xsl:if>

1 - 10Next
 

 Error ‭[2]‬

 
Web Part Error: One of the properties of the Web Part has an incorrect format. Microsoft SharePoint Foundation cannot deserialize the Web Part. Check the format of the properties and try again.
 

 Error ‭[3]‬

 
Web Part Error: One of the properties of the Web Part has an incorrect format. Microsoft SharePoint Foundation cannot deserialize the Web Part. Check the format of the properties and try again.