tag:blogger.com,1999:blog-5838547336106925342024-03-13T13:19:56.584+00:00Ashkan's SharePoint LandWelcome to my Blog, here I will share from my experiences of the design, development, implementation and configuration of SharePoint. I will focus on SharePoint from a Technical perspective drawing information from my experience of implementing and managing a wide variety of end to end solutions.Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.comBlogger19125tag:blogger.com,1999:blog-583854733610692534.post-4782718799009833992013-05-24T01:42:00.001+01:002013-05-26T20:59:32.722+01:00Scripted Installation of SharePoint 2013 and Office Web Apps Server – From the Field (Part 3) This is third post in the Scripted Installation of SharePoint 2013 and Office Web Apps Server blog series, covering the following service applications deployment:<br />
<ul>
<li>User Profile</li>
<li>Search</li>
<li>Distributed Cache</li>
</ul>
For SharePoint farm topology, installation and provisioning of the basic service applications please see blog one and two of this series.<br />
<ol>
<li><a href="http://ashkanj.blogspot.co.uk/2013/02/scripted-installation-of-sharepoint.html">Farm Topology and Prerequisites</a></li>
<li><a href="http://ashkanj.blogspot.co.uk/2013/03/scripted-installation-of-sharepoint.html">SharePoint Installation, Configuration and Basic Service Applications Deployment</a></li>
<li><strong>User Profile, Search and Distributed Cache Service Applications Deployment</strong></li>
<li>Office Web Apps Server farm Implementation and Configuration</li>
</ol>
<h2>
Prerequisites and Assumptions</h2>
<ul>
<li>Please download and extract the <a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-10-42-10-29/SPServices.zip" target="_blank">attached files</a> onto a local directory on each SharePoint Server. For the purposes of this blog the directory is suggested to be: E:\Scripts\Install.</li>
<li>From the downloaded files, update the SPUserProfile.xml file with environment specific information such as, SQL server alias name, service account details, database name, service application name, etc. This will be self-explanatory once you open the file.</li>
<li>Also update the SPSearchService.xml file with environment specific information such as, SQL server alias name, service account name and password, database name, service application name, Index Location, etc.</li>
</ul>
<h2>
Configure Distributed Cache</h2>
The Distributed Cache service can be deployed in two modes: dedicated mode or collocated mode. In dedicated mode, all services other than the Distributed Cache service are stopped on the application server that runs the Distributed Cache service. In collocated mode, the Distributed Cache service runs together with other services on the application server. Dedicated mode is the recommended mode in which to deploy the Distributed Cache service if the total number of users exceed 10,000.<br />
When more than one server is used for Distributed Cache, all the servers must have the same cache size configured.<br />
Please see <a href="http://technet.microsoft.com/library/jj219572(office.15).aspx">Planning for Distributed Cache service in SharePoint Server 2013</a> for more information.<br />
<strong>Provision Distributed Cache Service in dedicated mode:</strong><br />
Launch <strong>SharePoint Management Shell</strong> as administrator and execute the following PowerShell script on all Application, Search and Web Application Servers (all servers <strong><span style="text-decoration: underline;">apart from</span></strong> Distributed Cache servers SPDCache01 and SPDCache02) to remove them from the Distributed Cache cluster and stop the services:<br />
<div>
<pre class="scroll"><code class="cplusplus"> $instanceName ="SPDistributedCacheService Name=AppFabricCachingService"
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}
$serviceInstance.Unprovision()
Stop-SPDistributedCacheServiceInstance -Graceful
Remove-SPDistributedCacheServiceInstance </code></pre>
</div>
<strong>Change the Memory Allocation of the Distributed Cache Service</strong><br />
When SharePoint Server 2013 is installed, it assigns the Distributed Cache service 10 percent of the total memory on the server. It is recommended to allocate sufficient amount of memory on each Distributed Cache server. Please see <a href="http://technet.microsoft.com/en-us/library/jj219613.aspx#memory">Change the memory allocation of the Distributed Cache service</a> to calculate how much memory can be assigned to the Distributed Cache service. It is important to note that the allocated memory on each server should not exceed 16 GB.<br />
Use the following procedure to update the memory allocation accordingly:<br />
Launch <strong>SharePoint</strong> <strong>Management Shell</strong> as Administrator on SPDCache01 and SPDCache02 and run the following scripts:<br />
Stop the Distributed Cache service:<br />
<div>
<pre class="scroll"><code class="cplusplus"> $instanceName ="SPDistributedCacheService Name=AppFabricCachingService"
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}
$serviceInstance.Unprovision() </code></pre>
</div>
Reconfigure the cache size of the Distributed Cache service:<br />
<div>
<pre class="scroll"><code class="cplusplus"> Update-SPDistributedCacheSize -CacheSizeInMB 7168 </code></pre>
</div>
Restart the Distributed Cache service:<br />
<div>
<pre class="scroll"><code class="cplusplus"> $instanceName ="SPDistributedCacheService Name=AppFabricCachingService"
$serviceInstance = Get-SPServiceInstance | ? {($_.service.tostring()) -eq $instanceName -and ($_.server.name) -eq $env:computername}
$serviceInstance.Provision() </code></pre>
</div>
<strong>Change Service Account </strong><br />
When the server farm is first configured, the server farm account is set as the service account of the AppFabric Caching service. The Distributed Cache service depends on the AppFabric Caching service. For security purposes it is advised to change the service account from the farm account. To change the service account of the AppFabric Caching service to a managed account, set the Managed account as the service account on the AppFabric Caching service.<br />
At the Windows PowerShell command prompt, run the following command:<br />
<div>
<pre class="scroll"><code class="cplusplus"> $farm = Get-SPFarm
$cacheService = $farm.Services | where {$_.Name -eq "AppFabricCachingService"}
$accnt = Get-SPManagedAccount -Identity DomainName\SVC_SPFabric
$cacheService.ProcessIdentity.CurrentIdentityType = "SpecificUser"
$cacheService.ProcessIdentity.ManagedAccount = $accnt
$cacheService.ProcessIdentity.Update() </code></pre>
</div>
Where the ‘DomainName’ is the NetBIOS domain name.<br />
<h2>
Configure User Profile Services</h2>
Login to SPAPP01 (Application Server hosting the Central Administration site) and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to start and configure User Profile Service:<br />
<div>
<pre class="scroll"><code class="cplusplus"> E:\Scripts\Install\SPUserProfile.ps1 -configLocation E:\Scripts\Install\SPUserProfile.xml </code></pre>
</div>
When prompted provide the My Site Application Pool account variable “$MySiteAppPool”<br />
<h2>
Start User Profile Synchronisation</h2>
<ol>
<li>Ensure that the Farm Admin account (SVC_SPFarm) is a member of local administrators group on SPAPP01.<br /><strong>Please note</strong> this is only required while configuring User Profile synchronisation Settings. However, when a backup of the User Profile application is initiated, the synchronization service provisions the User Profile application again. During the course of provisioning the User Profile application, the farm account must stop and start the synchronization service. To do this, the farm account must be a member of the Administrators group on the computer that is running the synchronization service. Due to this you may decide that the farm account will remain a member of the Administrators group on SPAPP01.</li>
<li>Ensure that the Farm account is able to logon locally on both SPAPP01 and SPAPP02 (Please see <a href="http://technet.microsoft.com/en-us/library/ff182925(v=office.15).aspx#permission)">http://technet.microsoft.com/en-us/library/ff182925(v=office.15).aspx#permission)</a></li>
<li>Reboot SPAPP01 after granting above permissions</li>
<li>Starting the user profile synchronisation service introduce the same challenge as we had in SharePoint 2010. This needs to be done under the farm account. There are a number of options:</li>
<ol>
<li>Login to SPAPP01 using the Farm Admin account (SVC_SPFarm). Navigate to Central Administration Site and click on Services on Server and start User Profile Synchronization Service.</li>
<li>Launch the SharePoint Management Shell as the SVC_SPFarm account and use <a href="http://technet.microsoft.com/en-us/library/ff608036.aspx">New-SPProfileServiceApplication</a> Cmdlet.</li>
<li>Use the third option described in: <a href="http://www.harbar.net/archive/2010/10/30/avoiding-the-default-schema-issue-when-creating-the-user-profile.aspx" title="Title of this entry.">Avoiding the Default Schema issue when creating the User Profile Service Application using Windows PowerShell</a> by <a href="http://www.harbar.net/articles/about.aspx" title="Title of this entry.">Spencer Harbar</a>.<strong></strong></li>
<li>Perform an IIS reset on SPAPP01 server</li>
</ol>
</ol>
The following activities are recommended however are out of scope of this blog post:<br />
<ol>
<li>Add a new synchronisation connection</li>
<li>Define exclusion filters for a synchronisation connection</li>
<li>Map user profile properties</li>
<li>Start profile synchronization and configure Import Schedules</li>
</ol>
<h2>
Configure Search Service</h2>
<div>
Login to SPAPP01 (Application Server hosting the Central Administration site) and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to start and Search Services and configure the search topology:</div>
<div>
<br /></div>
<div>
<pre class="scroll"><code class="cplusplus"> E:\Scripts\Install\SPSearchService.ps1 -configLocation E:\Scripts\Install\SPSearchService.xml </code></pre>
</div>
Please note the following Search post configuration steps are required to be carried out; however, are out of scope of this blog post:<br />
<ol>
<li>Provide the location of the global Search Centre</li>
<li>Setup People Search</li>
<li>Configure result sources</li>
<li>Configure Search Result Exclusions</li>
<li>Configure Search Alert Settings</li>
<li>Configure Search Crawling Schedule</li>
</ol>
Lookout for the next blog post, where we implement Office Web Application Components and its integration with SharePoint.Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com2tag:blogger.com,1999:blog-583854733610692534.post-52241047982804801822013-03-18T15:05:00.002+00:002013-05-24T01:51:58.162+01:00Scripted Installation of SharePoint 2013 and Office Web Apps Server – From the Field (Part 2)This is the second post in the Scripted Installation of SharePoint 2013 and Office Web Apps Server series. If you have not already done so, please see part one of this blog series: <a href="http://ashkanj.blogspot.co.uk/2013/02/scripted-installation-of-sharepoint.html">Farm Topology and Prerequisites</a>.<br />
<ol>
<li><a href="http://ashkanj.blogspot.co.uk/2013/02/scripted-installation-of-sharepoint.html">Farm Topology and Prerequisites</a></li>
<li><strong>SharePoint Installation, Configuration and Basic Service Applications Deployment</strong></li>
<li><a href="http://ashkanj.blogspot.co.uk/2013/05/scripted-installation-of-sharepoint.html">User Profile, Search and Distributed Cache Service Applications Deployment</a></li>
<li>Office Web Apps Server farm Implementation and Configuration</li>
</ol>
This blog post will cover:<br />
<ul>
<li>Installation of SharePoint 2013</li>
<li>Farm creation and configuration</li>
<li>Implementation of:</li>
<ul>
<li>Excel Services</li>
<li>Secure Store</li>
<li>Usage and Health Data Collection</li>
<li>Managed Metadata Services</li>
<li>State Services</li>
</ul>
<li>Configuration of services on servers</li>
<li>Configuration of usage and health data collection</li>
<li>Configuration of state service</li>
<li>Configuration of diagnostic logging</li>
</ul>
<h2>
Servers in Farm</h2>
The following table illustrates the server names and associated server roles for each server:<br />
<table border="1" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="top" width="123"><strong> Server Name</strong></td>
<td valign="top" width="477"><strong> Server Role</strong></td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPWEB01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Web Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPWEB02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Web Server 2</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPDCache01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Distribution Cache Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPDCache02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Distribution Cache Server 2</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPAPP01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Application Server 1 (CA)</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPAPP02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Application Server 2 (CA)</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPQuery01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Query Processing and Index Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPQuery02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Query Processing and Index Server 2</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPCrawl01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Admin, Crawl, Content Processing, Analytics Processing Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPCrawl02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Admin, Crawl, Content Processing, Analytics Processing Server 2</td>
</tr>
</tbody>
</table>
<h2>
Installation Prerequisites and Assumptions</h2>
<ul>
<li>Please download and extract <a href="http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-10-40-31-58/BasicServices_5F00_Blog02.zip" target="_blank">attached files</a> onto local directory. It has been assumed that this directory is local folder on all SharePoint serves created as E:\Scripts\Install</li>
<li>It is assumed that the SharePoint installation directory is D:\</li>
<li>Update the SilentConfig.xml file with SharePoint product key. Please see <a href="http://technet.microsoft.com/en-us/library/cc261668(v=office.14).aspx">Config.xml reference on TechNet</a> for more information.</li>
<li>Update the Config.xml file with environment specific information such as, SQL server alias name (To improve ease of maintenance, and make it easier to relocate the database if it is required in the future, create DNS aliases that point to the IP address for all instances of SQL Server), farm account details, admin database and configuration database. </li>
<li>Update the SPCredentials.xml file with service accounts and passwords information.</li>
<li>Update the SPServices.xml file with Usage and Health data collection log file location, Usage and Health data collection maximum file size, SQL server name, service application names and related database names.</li>
</ul>
<h2>
Install SharePoint</h2>
<ol start="1">
<li>Microsoft SQL Server 2008 R2 Native Client is installed as part of SharePoint 2013 prerequisites installer, however if you are using SQL Server 2012 to host SharePoint databases, Install <a href="http://go.microsoft.com/fwlink/?LinkID=239648&clcid=0x409">Microsoft SQL Server 2012 Native Client 64-bit edition</a> on all SharePoint servers.</li>
<li>Install SharePoint prerequisites and SharePoint binaries by executing the following script on all servers listed above (launch <strong>SharePoint Management Shell</strong> as administrator): </li>
</ol>
<div>
<pre class="scroll"><code class="cplusplus">Set-ExecutionPolicy Unrestricted –force
E:\Scripts\Install\SPInstaller.ps1 -installPath D:\ -offline "n"
Import-PSSession $session</code></pre>
Please note: Windows PowerShell execution policies let you determine the conditions under which Windows PowerShell loads configuration files and runs scripts. The execution policy is not a security system that restricts user actions. Instead, the execution policy helps users to set basic rules and prevents them from violating them unintentionally. Please see <a href="http://technet.microsoft.com/en-us/library/dd347641.aspx">About Execution Policy</a> TechNet article.</div>
This script will automatically restart servers as required. <strong>Do not run configuration wizard until installation is completed on all servers</strong><br />
<strong><span style="text-decoration: underline;">The following steps are performed on individual servers specified in each step:</span></strong><br />
<h2>
Create the Farm</h2>
Login to SPAPP01 (Application Server hosting the Central Administration site) using the installer account and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to create the farm:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPConfig.ps1 -configLocation E:\Scripts\Install\Config.xml -createJoin create -isCA "y"</code></pre>
</div>
<h2 class="CodeBlock">
Join Servers to the Farm</h2>
Login to SPAPP02 (The second Application Server hosting the Central Administration site) and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following PowerShell script:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPConfig.ps1 -configLocation E:\Scripts\Install\Config.xml -createJoin join -isCA "y"</code></pre>
</div>
Run the following script on the below SharePoint servers:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPConfig.ps1 -configLocation E:\Scripts\Install\Config.xml -createJoin join -isCA "n"</code></pre>
</div>
<br />
<table border="1" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="top" width="123"><strong> Server Name</strong></td>
<td valign="top" width="477"><strong> Server Role</strong></td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPWEB01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Web Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPWEB02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Web Server 2</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPDCache01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Distribution Cache Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPDCache02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Distribution Cache Server 2</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPQuery01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Query Processing and Index Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPQuery02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Query Processing and Index Server 2</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPCrawl01</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Admin, Crawl, Content Processing, Analytics Processing Server 1</td>
</tr>
<tr>
<td valign="top" width="123"><strong> SPCrawl02</strong><strong></strong></td>
<td valign="top" width="477"> SharePoint 2013 Admin, Crawl, Content Processing, Analytics Processing Server 2</td>
</tr>
</tbody>
</table>
<h2>
Register Managed Accounts</h2>
Login to SPAPP01 (Application Server hosting the Central Administration site) using the installer account and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to register managed accounts in the farm:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPCredentials.ps1 -configLocation E:\Scripts\Install\SPCredentials.xml</code></pre>
</div>
<h2>
Configure Basic Services</h2>
Login to SPAPP01 (Application Server hosting the Central Administration site) using the installer account and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to start required services and stop unwanted ones:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPServices.ps1 -configLocation E:\Scripts\Install\SPServices.xml</code></pre>
</div>
The above script will stop unnecessary services from servers and starts the following service:<br />
<ul>
<li>Excel Services</li>
<li>Secure Store</li>
<li>Usage and Health Data Collection</li>
<li>Managed Metadata Services</li>
<li>State Services</li>
</ul>
<h2>
Configure Usage and Health Data Collection</h2>
Login to SPAPP01 (Application Server hosting the Central Administration site) using the installer account and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to start and configure Usage Service:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPUsage.ps1 -configLocation E:\Scripts\Install\SPServices.xml</code></pre>
</div>
<h2>
Configure State Service</h2>
Login to SPAPP01 (Application Server hosting the Central Administration site) using the installer account and launch <strong>SharePoint Management Shell</strong> as administrator. Execute the following command to start and configure Usage Service:<br />
<div>
<pre class="scroll"><code class="cplusplus">E:\Scripts\Install\SPStateService.ps1 -configLocation E:\Scripts\Install\SPServices.xml</code></pre>
</div>
<br />
You should now have basic services started on all servers in the farm. It is recommended to check Servers in Farm page from Central administrations site to ensure that the correct services are started.<br />
By the end of this blog series the expected farm topology will be as illustrated below:<br />
<table border="1" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td valign="top" width="112"><strong> Server Name</strong></td>
<td valign="top" width="153"><strong> Server Role</strong></td>
<td valign="top" width="336"><strong> Services</strong></td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPWEB01</strong><strong></strong></td>
<td valign="top" width="153">Web Server</td>
<td valign="top" width="336"> Microsoft SharePoint Foundation Web Application<br />
Microsoft SharePoint Foundation Workflow Timer Service<br />
Managed Metadata Web Service</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPWEB02</strong><strong></strong></td>
<td valign="top" width="153">Web Server</td>
<td valign="top" width="336"> Microsoft SharePoint Foundation Web Application<br />
Microsoft SharePoint Foundation Workflow Timer Service<br />
Managed Metadata Web Service</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPDCache01</strong><strong></strong></td>
<td valign="top" width="153">Distribution Cache</td>
<td valign="top" width="336"> Distributed Cache<br />
Microsoft SharePoint Foundation Workflow Timer Service<br />
Microsoft SharePoint Foundation Web Application</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPDCache02</strong><strong></strong></td>
<td valign="top" width="153">Distribution Cache</td>
<td valign="top" width="336"> Distributed Cache<br />
Microsoft SharePoint Foundation Workflow Timer Service<br />
Microsoft SharePoint Foundation Web Application</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPAPP01</strong><strong></strong></td>
<td valign="top" width="153">Application Server</td>
<td valign="top" width="336"> Central Administration<br />
Excel Calculation Services<br />
Microsoft SharePoint Foundation Workflow Timer Service<br />
Secure Store Service<br />
User Profile Service<br />
User Profile Synchronization Service</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPAPP02</strong><strong></strong></td>
<td valign="top" width="153">Application Server</td>
<td valign="top" width="336"> Central Administration<br />
Excel Calculation Services<br />
Microsoft SharePoint Foundation Workflow Timer Service<br />
Secure Store Service<br />
User Profile Service</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPQuery01</strong><strong></strong></td>
<td valign="top" width="153">Search - Query Processing and Index</td>
<td valign="top" width="336"> Microsoft SharePoint Foundation Workflow Timer Service<br />
Search Host Controller Service<br />
Search Query and Site Settings Service<br />
SharePoint Server Search</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPQuery02</strong><strong></strong></td>
<td valign="top" width="153">Search - Query Processing and Index</td>
<td valign="top" width="336"> Microsoft SharePoint Foundation Workflow Timer Service<br />
Search Host Controller Service<br />
Search Query and Site Settings Service<br />
SharePoint Server Search</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPCrawl01</strong><strong></strong></td>
<td valign="top" width="153">Search - Admin, Crawl, Content Processing, Analytics Processing</td>
<td valign="top" width="336"> Microsoft SharePoint Foundation Workflow Timer Service<br />
Search Host Controller Service<br />
Search Query and Site Settings Service<br />
SharePoint Server Search</td>
</tr>
<tr>
<td valign="top" width="112"><strong> SPCrawl02</strong><strong></strong></td>
<td valign="top" width="153">Search - Admin, Crawl, Content Processing, Analytics Processing</td>
<td valign="top" width="336"> Microsoft SharePoint Foundation Workflow Timer Service<br />
Search Host Controller Service<br />
Search Query and Site Settings Service<br />
SharePoint Server Search</td>
</tr>
</tbody>
</table>
<br />
Lookout for the next blog post, where we complete the farm configuration by provisioning search, user profile services and distributed cache service.Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com1tag:blogger.com,1999:blog-583854733610692534.post-39892089257248483832013-02-18T13:31:00.000+00:002013-05-24T01:49:42.369+01:00Scripted Installation of SharePoint 2013 and Office Web Apps Server – From the Field (Part 1)<br />
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
This is the first in a series of posts where I will talk about my involvement in the TAP (<a data-mce-href="https://connect.microsoft.com/Main/help/help.aspx?Category=2#x_program" href="https://connect.microsoft.com/Main/help/help.aspx?Category=2#x_program">Technology Adoption Program</a>) and more specifically a project I was involved in to implement the SharePoint 2013 platform and<a data-mce-href="http://office.microsoft.com/en-gb/web-apps/" href="http://office.microsoft.com/en-gb/web-apps/">Office Web Apps</a> Server farm. I will be sharing my findings and experience that will hopefully help you to:</div>
<ul style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<li>Create a reusable SharePoint 2013 build and configuration guide</li>
<li>Implement SharePoint and Office Web Apps Server in a consistent manner using the scripts I will provide throughout this blog post series.</li>
</ul>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
The series is broken down into the following articles that I will write:</div>
<ol style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<li><strong>Farm Topology and Prerequisites (This article)</strong></li>
<li><a href="http://ashkanj.blogspot.co.uk/2013/03/scripted-installation-of-sharepoint.html">SharePoint Installation, Configuration and Basic Service Applications Deployment</a></li>
<li><a href="http://ashkanj.blogspot.co.uk/2013/05/scripted-installation-of-sharepoint.html">User Profile, Search and Distributed Cache Service Applications Deployment</a></li>
<li>Office Web Apps Server farm Implementation and Configuration</li>
</ol>
<h2>
Introduction</h2>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
This post will focus on providing an overview of the overall farm topology, the end to end build sequence from preparation to testing, recommended service accounts and the prerequisites.</div>
<h2>
Build Sequence</h2>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
The following diagram illustrates the high level overview of the steps required to implement and configure the SharePoint and Office Web Apps Server farms. The Office Web Apps server farm requires dedicated hardware and is no longer implemented as a SharePoint service application.</div>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<div class="separator" style="clear: both; text-align: center;">
<a href="http://2.bp.blogspot.com/-cOws37JDV7k/USIrNGvLq3I/AAAAAAAAAPc/657doxi2_T0/s1600/Build+Sequence.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="251" src="http://2.bp.blogspot.com/-cOws37JDV7k/USIrNGvLq3I/AAAAAAAAAPc/657doxi2_T0/s400/Build+Sequence.jpg" width="400" /></a></div>
<br /></div>
<h2>
Farm Topology</h2>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
The server farm topology will have multiple tiers and each tier will have redundant server instances, this is the most common topology that provides an efficient physical and logical layout to support scaling out or scaling up, and provides better distribution of services across the<br />
member servers.</div>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
</div>
<div class="separator" style="clear: both; text-align: center;">
<a href="http://3.bp.blogspot.com/-WYWaK_STX8w/USIrUD5bxuI/AAAAAAAAAPk/TOWWM40JKlo/s1600/Farm+Topology.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="http://3.bp.blogspot.com/-WYWaK_STX8w/USIrUD5bxuI/AAAAAAAAAPk/TOWWM40JKlo/s1600/Farm+Topology.jpg" /></a></div>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<br /></div>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
It is important to adopt an iterative design approach to analyse the architecture model, to verify that the model identifies all the elements that are required for the farm solution. </div>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
The <a data-mce-href="http://technet.microsoft.com/en-us/library/jj219701.aspx" href="http://technet.microsoft.com/en-us/library/jj219701.aspx">Plan for monitoring in SharePoint 2013</a> TechNet article provides great introduction on tools and scenarios on how to best use them. </div>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
Redundant member servers are hosted on different Hyper-V hosts and Anti-Affinity helps to eliminate single points of failure. It is worth noting that the <a data-mce-href="http://www.microsoft.com/en-gb/download/details.aspx?id=30384" href="http://www.microsoft.com/en-gb/download/details.aspx?id=30384">Deployment guide for SharePoint 2013 eBook</a>, provides great detailed information regarding recommended practices when implementing SharePoint 2013 on a virtualised platform such as: </div>
<ul style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<li>Leave adequate memory for the Hyper-V partitions - For SharePoint products virtual machines, we recommend 4 GB of RAM or more for host computer operations.</li>
<li>Use a minimum of two physical network adapters - For better network management and performance, dedicate one adapter to virtual machine network traffic and use the other adapter for virtualization host network traffic.</li>
<li>Do not oversubscribe the CPU on the virtualization host computer - Review the supported ratio of virtual processors per logical processor and avoid oversubscribing the host computer CPU. The optimum virtual processor:logical processor ratio is 1:1. For more information, see Configure the processors for the virtual machines in <a data-mce-href="http://www.microsoft.com/en-gb/download/details.aspx?id=30384" href="http://www.microsoft.com/en-gb/download/details.aspx?id=30384">Deployment guide for SharePoint 2013 eBook</a>.</li>
<li>Do not cross Non-uniform memory access (NUMA) boundaries - Hyper-V spans NUMA nodes to assign physical memory to a virtual machine; however, this does reduce performance on the virtual machine. For more information, see Configure the memory for the virtual machines in <a data-mce-href="http://www.microsoft.com/en-gb/download/details.aspx?id=30384" href="http://www.microsoft.com/en-gb/download/details.aspx?id=30384">Deployment guide for SharePoint 2013 eBook</a>.</li>
<li>Do not use snapshots in a production environment - Do not use snapshots for the virtual machines in a SharePoint products production environment. When you create a snapshot, Hyper-V creates a new secondary drive for the virtual machine. Write operations occur on the new drive and read operations occur on both drives, which has the same net affect as a differencing disk. Every snapshot that you add reduces disk performance further.</li>
<li>Do not use dynamic memory - The reason is that this implementation of dynamic memory does not work with every SharePoint feature. For example, Distributed Cache and Search do not resize their caches when the allocated memory for a virtual machine is dynamically changed. This can cause performance degradation, especially when assigned memory is reduced.</li>
</ul>
<h2>
Service Accounts</h2>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
The following service accounts are what I have used to create the farm. This list may vary for your implementation depending on Server resources management versus least privilege security recommendation, required service applications and in general what works for your implementation based on the organisations security guidelines and policies.<br />
<br /></div>
<table border="1" cellpadding="0" cellspacing="0" data-mce-style="width: 100%;" style="background-color: white; cursor: default; font-family: Arial, Helvetica, sans-serif;"><tbody>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>Account</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%"><strong>Purpose</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><strong>Requirements</strong></td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPInst</strong><br />
<strong>Setup user account</strong><br />
<strong>(Install Account)</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">The Setup user account is used to run the following:<br />
<ul>
<li>Setup</li>
<li>SharePoint Products Configuration Wizard</li>
</ul>
</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account.</li>
<li>Member of the Administrators group on each server on which Setup is run.</li>
</ul>
<ul>
<li>SQL Server login on the computer that runs SQL Server.</li>
</ul>
<ul>
<li>dbcreator and securityadmin</li>
<li>This account must be a member of the <strong>db_owner</strong> fixed database role for the content databases database.</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPFarm</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">The server farm account is used to perform the following tasks:<br />
<ul>
<li>Configure and manage the server farm.</li>
<li>Act as the application pool identity for the SharePoint Central Administration Web site.</li>
<li>Run the Microsoft SharePoint Foundation Workflow Timer Service.</li>
</ul>
</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account.</li>
<li>Additional permissions are automatically granted for the server farm account on Web servers and application servers that are joined to a server farm.</li>
<li>The server farm account is automatically added as a SQL Server login on the computer that runs SQL Server. The account is added to the following SQL Server security roles:</li>
<li><strong>dbcreator</strong> fixed server role</li>
<li><strong>securityadmin</strong> fixed server role</li>
<li><strong>db_owner</strong> fixed database role for all SharePoint databases in the server farm</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPSvc</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">A generic services account for grouped Service Applications</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPSvcPool</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">Application Pool Identity for SharePoint Web Services Default application</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPWeb</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">Application Pool Identity for the main web application</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPUPA</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">The User Profile Service account is used to run the following:<br />
<ul>
<li>User Profile Synchronisation with AD</li>
</ul>
</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
<li>AD Delegate rights for: <strong>Replication Directory Changes</strong></li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPSearch</strong><strong></strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">This is the Windows Service account for the SharePoint Server Search Service. This setting affects all Search Service Applications in the farm.</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPSrchPl</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">Search Admin Web Service application pool<br />
Search Query and Site Settings Web Service application pool</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPSrchCrl</strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">Windows user credentials for the Search service application to use to access content when crawling</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPFabric</strong><strong></strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">AppFabric Caching service</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPOWAPool</strong><strong></strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">Office Web App Application pool account</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="24%"><strong>SVC_SPOWASvc</strong><strong></strong></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="38%">Office web application Services Pool</td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
<tr><td style="cursor: text; margin: 8px;" valign="top" width="24%"><span style="font-size: 12px;"><b>SVC_SPSecStr</b></span></td><td style="cursor: text; margin: 8px;" valign="top" width="38%"><span style="font-size: 12px;">Secure Store application Pool account</span></td><td style="cursor: text; font-size: 12px; margin: 8px;" valign="top" width="37%"><ul>
<li>Domain user account</li>
</ul>
</td></tr>
</tbody></table>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<br /></div>
<h2>
Prerequisites</h2>
<ol style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<li>All SharePoint servers would require an additional drive to host Data, Log and Index flies.<ol style="list-style-type: lower-alpha;">
<li>An additional VHD is required</li>
<li>Bring the disk online</li>
<li>Format the drive as NTFS, label: Data</li>
</ol>
</li>
</ol>
<ol start="2" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<li>Ensure that the following are implemented:</li>
<ol start="1" style="list-style-type: lower-alpha;">
<li>Remote Registry Service started (or Automatic - Trigger Start) on all servers</li>
<li>Inbound firewall rules enabled on all SharePoint servers: (Please see <a data-mce-href="/b/uksharepoint/archive/2013/01/21/sharepoint-2013-ports-proxies-and-protocols-an-overview-of-farm-communications.aspx" href="http://blogs.msdn.com/b/uksharepoint/archive/2013/01/21/sharepoint-2013-ports-proxies-and-protocols-an-overview-of-farm-communications.aspx">SharePoint 2013 Ports, Proxies and Protocols - An Overview of Farm Communications</a> for more information)</li>
<ol start="1" style="list-style-type: upper-alpha;">
<li>ICMP v4</li>
<li>ICMP v6</li>
<li>Central Administration port number on the servers hosting the Central Admin Site only. It is recommend to use SSL for the central administration site.</li>
<li>Distribution Cache port 22233 on the Distribution Cache Servers only</li>
</ol>
</ol>
<li>Ensure that the Install account has SQL securityadmin and dbcreator roles and is member of local administrator group on all SharePoint servers</li>
<li>Ensure that the Farm account is a member of local administrators group on the server hosting the User Profile Service Synchronisation Service. This is only required during the User Profile Synchronisation Configuration defined in post #3 User Profile, Search and Distributed Cache Service Applications Deployment. These permissions are only required while configuring User Profile synchronisation Settings. However, when a backup of the User Profile application is initiated, the synchronization service provisions the User Profile application again. During the course of provisioning the User Profile application, the farm account must stop and start the synchronization service. To do this, the farm account must be a member of the Administrators group on the computer that is running the synchronization service.</li>
</ol>
<ol start="5" style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
<li>Ensure that the Farm account is able to logon locally on the server hosting the User Profile Service Synchronisation Service (Please see <a data-mce-href="http://technet.microsoft.com/en-us/library/ff182925(v=office.15).aspx#permission" href="http://technet.microsoft.com/en-us/library/ff182925(v=office.15).aspx#permission">Plan account permissions</a>).</li>
</ol>
<div style="background-color: white; font-family: Arial, Helvetica, sans-serif; font-size: 12px; text-align: -webkit-auto;">
Now we are ready to implement SharePoint and configure the basic services. Look out for part two for detailed step by step scripted deployment and configuration of the farm.</div>
Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-69956187624771537152012-05-11T02:15:00.001+01:002012-05-11T02:23:15.577+01:00The experiences of a new starter at Microsoft ServicesMy career life has always been focused on Microsoft products and services. Working for a Microsoft gold partner for almost 8 years, had given me an inkling of what life at Microsoft might be like. However once I moved to Microsoft in November 2011, it didn’t take me long to truly realise, the benefits of working at such an influential organisation.<br />
<br />
<h2>Investment in people</h2>
From the very first day it was very clear to me how much people are valued as individuals and "Putting People First" is not just an advertising campaign.<br />
I was given enough time to familiarise myself with the Microsoft way of consulting. This included a one week new hire onboarding programme in Redmond at Microsoft Services University. It was an incredible experience that definitely helped me with my soft skills and familiarised me with the resources and toolset available to do my day to day job more effectively and efficiently. I also had the opportunity to network with amazing people from around the globe. I made some great friends from all over the world which I'm still in touch with today.<br />
<br />
<h2>Personal development</h2>
I can honestly say that Microsoft is a sea of opportunity and development. Not only that, you are in fact encouraged and expected to take advantage of such opportunities. These include an onsite library with access to the vast number of technical and non-technical materials, free access to online materials and Microsoft courses, free exams, free MSDN subscription, regular opportunity to attend events such as TechReady (which is like TechEd for Microsoft field staff covering all the Enterprise products and technologies) and most of all, 'the time' that you would need to do all these.<br />
My manager works directly with me on regular basis to review my career development progress and provide support where necessary in order to help achieve my targets.<br />
<br />
<h2>Empowered</h2>
At Microsoft the emphasis is on the quality of work produced and the client satisfaction. We are empowered to manage our own schedules working within the needs of our customer commitments on projects, this allows me to plan the necessary development activities into my schedule to enable me to grow whilst still delivering high quality to our customers and the business.<br />
<br />
<h2>Making a difference</h2>
Not only am I encouraged to get involved and make a difference, but I am expected as part of my commitments to contribute to my team, community, partners, processes and the practice. The opportunity to influence the development of new processes, or to better current processes is an invaluable experience that not many organisations have in place.<br />
<br />
<h2>The team</h2>
I definitely feel like I am part of a team. People are extremely passionate, talented, experienced and go above and beyond their duty to help. The standard and reputation of the people at Microsoft was one of the primary reasons for me wanting to join. There is a diverse background of people at Microsoft but the one thing they all have in common is that they are leading individuals in their field of expertise and they are all more than willing to share their wisdom and experience.Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-9019336900158105662010-10-08T02:27:00.001+01:002010-10-08T02:33:11.500+01:00SharePoint Solution Generator is dead (for good) - Part 1<p>SharePoint Solution Generator, part of <a href="http://www.microsoft.com/downloads/en/details.aspx?FamilyID=FB9D4B85-DA2A-432E-91FB-D505199C49F6" target="_blank">Visual Studio 2008 extensions for Windows SharePoint Services</a> has been a fantastic tool in SharePoint 2007 development when I needed to create a list definition and list instance quickly. </p> <p>All you had to do was to create your content types,site columns, and list using SharePoint UI and apply the content types and site columns to your list, then customise your list and create views then finally point solution generator to your list and create your solution package.</p> <p> </p> <p>Combination of the new features of SharePoint 2010 and Visual studio 2010 means no more messing around with add-ons…. </p> <p>SharePoint 2010 allows you to save your site as a wsp package and Visual studio allows you to import the wsp package and select the required elements to include in your solution package! sounds easy? it is :)</p> <p> </p> <p>…so first you need to create your list as before with all required components and customisations:</p> <p><strong>1) Create your Site Content Type</strong></p> <p><a href="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zNTfTpTI/AAAAAAAAAE8/lGykH_TL-is/s1600-h/image%5B56%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5zOHDdl7I/AAAAAAAAAFA/G-7w06b_wwg/image_thumb%5B32%5D.png?imgmax=800" width="468" height="346" /></a> </p> <p><strong>2) Create your Site Columns</strong></p> <p><a href="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5zOgibbWI/AAAAAAAAAFI/RRKWe01m1Ak/s1600-h/image%5B57%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh5.ggpht.com/_d7HMZG1Hte0/TK5zPBuWhJI/AAAAAAAAAFQ/-vo7FUQZJ8A/image_thumb%5B33%5D.png?imgmax=800" width="471" height="395" /></a> </p> <p><strong>3) Assign your site columns to your content type</strong></p> <p><a href="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5zPnhzszI/AAAAAAAAAFY/GXxfipqJZ0o/s1600-h/image%5B58%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zQclvW8I/AAAAAAAAAFk/FJbYe6sjWxk/image_thumb%5B34%5D.png?imgmax=800" width="467" height="346" /></a> </p> <p><strong>4) Create your list/library and assign your content type to your list</strong></p> <p>To be able to do this you need to ensure you have selected “allow management of content types” from the list advanced settings</p> <p><a href="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5zQnfz5iI/AAAAAAAAAFo/3qKVNr2j_5E/s1600-h/image%5B59%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zRouyWNI/AAAAAAAAAFs/VqHW7vkqsKs/image_thumb%5B35%5D.png?imgmax=800" width="464" height="224" /></a> </p> <p><strong>5) Save your site as WSP package</strong></p> <p>Site Action –> Site Settings –> “Save site as template”</p> <p><a href="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zSjAiyuI/AAAAAAAAAFw/LsvLkwWZcUs/s1600-h/image%5B60%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5zTPjlfTI/AAAAAAAAAF0/SIG8vn4mB5I/image_thumb%5B36%5D.png?imgmax=800" width="468" height="428" /></a> </p> <p>provide a file name and a template name for your template</p> <p><a href="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zTpyCoHI/AAAAAAAAAGM/39ljoLaLoFg/s1600-h/image%5B62%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zULI8poI/AAAAAAAAAGQ/P1iAaXnYyWo/image_thumb%5B38%5D.png?imgmax=800" width="468" height="228" /></a> </p> <p>Download the WSP file and save locally</p> <p><a href="http://lh3.ggpht.com/_d7HMZG1Hte0/TK5zUn7-Q_I/AAAAAAAAAGU/ofuNAFiVccQ/s1600-h/image%5B63%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5zU24W-cI/AAAAAAAAAGg/du00rXaLCSk/image_thumb%5B39%5D.png?imgmax=800" width="468" height="236" /></a> </p> <p><strong>6) Import the WSP package into Visual Studio 2010</strong></p> <p>Create a Visual Studio SharePoint project and select “Import SharePoint Solution Package”</p> <p><a href="http://lh6.ggpht.com/_d7HMZG1Hte0/TK5zVddiX0I/AAAAAAAAAGk/Lc26qTord28/s1600-h/image%5B64%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh6.ggpht.com/_d7HMZG1Hte0/TK5zV6UUsSI/AAAAAAAAAGs/9Y20gDBjvqI/image_thumb%5B40%5D.png?imgmax=800" width="469" height="324" /></a> </p> <p></p> <p></p> <p></p> <p></p> <p></p> <p></p> <p></p> <p>Import the WSP file</p> <p><a href="http://lh5.ggpht.com/_d7HMZG1Hte0/TK5zWctNKTI/AAAAAAAAAG4/i1CwfJ3ovJM/s1600-h/image%5B65%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh6.ggpht.com/_d7HMZG1Hte0/TK5zXMH3xkI/AAAAAAAAAHA/nPozPwQ1wmw/image_thumb%5B41%5D.png?imgmax=800" width="471" height="373" /></a> </p> <p>Specify the project elements required in this case the list template</p> <p>The easiest way to do this is to highlight all items (Ctrl + A) and  deselect one item. this will uncheck all boxes</p> <p>Then select the “List instance” and “Content type” and click finish (You do not need to include the columns)</p> <p><a href="http://lh5.ggpht.com/_d7HMZG1Hte0/TK5zXSf9BpI/AAAAAAAAAHI/y5pKr7Xyfik/s1600-h/image%5B66%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh6.ggpht.com/_d7HMZG1Hte0/TK5zX6GMk_I/AAAAAAAAAHM/dsH1-S6DGDc/image_thumb%5B42%5D.png?imgmax=800" width="476" height="378" /></a> </p> <p>Say No to include all dependent items</p> <p><a href="http://lh6.ggpht.com/_d7HMZG1Hte0/TK5zYS9OxLI/AAAAAAAAAH0/F4CzTqWk9yw/s1600-h/image%5B73%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh5.ggpht.com/_d7HMZG1Hte0/TK5zYxMbZoI/AAAAAAAAAH8/87mC3HuZpS8/image_thumb%5B52%5D.png?imgmax=800" width="477" height="401" /></a> </p> <p></p> <p>Now you have all required components for your solution</p> <p><a href="http://lh5.ggpht.com/_d7HMZG1Hte0/TK50Q8brdsI/AAAAAAAAAHo/A0K9SuVpYMI/s1600-h/image%5B72%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh4.ggpht.com/_d7HMZG1Hte0/TK50RcxYlRI/AAAAAAAAAHw/OQl5wC4nj-w/image_thumb%5B46%5D.png?imgmax=800" width="480" height="561" /></a> </p> <p>There are a number of considerations which I will try to cover in the next posts such as including Lookup and Managed Metadata filed types in your solution.</p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com3tag:blogger.com,1999:blog-583854733610692534.post-40816191933811191872010-10-08T01:10:00.002+01:002011-03-13T22:17:39.931+00:00Automated SharePoint 2010 AD service accounts creation using PowerShellAs I don’t really enjoy repetitive tasks, I decided to put a quick PowerShell script together to create the AD service accounts required for SharePoint 2010.<br />
The required accounts are: <br />
<ul><li>svc_spFarm (Server farm account or database access account) </li>
<li>svc_spAdmin (Setup user account Install Account) </li>
<li>svc_caAppPool (Application Pool Identity for Central Administration web application) </li>
<li>svc_portalAppPool (Application Pool Identity for Portal web application) </li>
<li>svc_myAppPool (Application pool Identity for my sites host web application) </li>
<li>svc_spUPS (User Profile Synchronisation with AD) </li>
<li>svc_spUPAPool (User Profile Services Application Pool account) </li>
<li>svc_spSearch (This is the Windows Service account for the SharePoint Server Search Service. This setting affects all Search Service Applications in the farm) </li>
<li>svc_spCrawl (Content Access account) </li>
<li>svc_spSearchAP (Enterprise Search Application Pool Identity) </li>
<li>svc_spSearchAdmAP (Enterprise Search Admin component Application Pool Identity) </li>
<li>svc_fsSearch (Foundation server search account) </li>
<li>svc_fsCrawl (Foundation server crawl account) </li>
<li>svc_spSandbox (Sandbox service service account) </li>
<li>svc_WebAnalytics (SharePoint Web Analytics service account) </li>
<li>svc_SecureStore (Secure Store Application Pool service account)</li>
<li>svc_spSTSAcct (Security Token Service Application)</li>
<li>svc_spMetadata (Managed Metadata Service Account)</li>
</ul>(Other accounts may be required depending on services running on the farm such as InfoPath services, Visio, etc…) <br />
Please note The following additional domain , local and SQL permissions / roles are required: <br />
<strong>svc_spAdmin:</strong> <br />
Member of the Local Administrators group. <br />
SQL Server login on the computer that runs SQL Server. <br />
Member of the following SQL Server security roles: <br />
· securityadmin fixed server role <br />
· dbcreator fixed server role <br />
· sysAdmin fixed server role (during installation using PowerShell only) <br />
<strong>svc_spFarm:</strong> <br />
Member of the Local Administrators group during the user profile services configuration only. <br />
<strong>svc_spUPS:</strong> <br />
AD Delegate rights for Replication Directory Changes permissions <br />
The PowerShell command takes a csv file containing the following headings: <br />
<ul><li>samAccountName </li>
<li>userPrincipalName </li>
<li>cn </li>
<li>givenName </li>
<li>Password </li>
<li>description </li>
</ul>Copy and paste the following into a csv file called acc.csv (ideally this needs to be an XML):<br />
samAccountName,userPrincipalName,cn,Password,description <br />
svc_spAdmin,svc_spAdmin@domainName.FQDN,svc_spAdmin,accountPassword,The Setup user account is used to Setup SharePoint Products Configuration <br />
svc_spFarm, svc_spFarm@domainName.FQDN,svc_spFarm,accountPassword,The server farm account is used to Run the Microsoft SharePoint Foundation and workflow Timer ServiceWizard <br />
svc_caAppPool,svc_caAppPool@domainName.FQDN,svc_caAppPool,accountPassword,Application Pool Identity for Central Administration web application <br />
svc_portalAppPool,svc_portalAppPool@domainName.FQDN,svc_portalAppPool,accountPassword,Application Pool Identity for Portal web application <br />
svc_myAppPool, svc_spAppPool@domainName.FQDN,svc_myAppPool,accountPassword,Application pool Identity for my sites host web application <br />
svc_spUPS,svc_myAppPool@domainName.FQDN,svc_spUPS,accountPassword,User Profile Synchronisation with AD <br />
svc_spUPAPool,svc_spUPAPool@domainName.FQDN,svc_spUPAPool,accountPassword,User Profile Services Application Pool account <br />
svc_spSearch, svc_spSearch@domainName.FQDN,svc_spSearch,accountPassword,This is the Windows Service account for the SharePoint Server Search Service. This setting affects all Search Service Applications in the farm <br />
svc_spCrawl, svc_spCrawl@domainName.FQDN,svc_spCrawl,accountPassword,Content Access account <br />
svc_spSearchAP,svc_spSearchAP@domainName.FQDN,svc_spSearchAP,accountPassword,Enterprise Search Application Pool Identity <br />
svc_spSearchAdmAP,svc_spSearchAdmAP@domainName.FQDN,svc_spSearchAdmAP,accountPassword,Enterprise Search Admin component Application Pool Identity <br />
svc_fsSearch,svc_fsSearch@domainName.FQDN,svc_fsSearch,accountPassword,Foundation server search account <br />
svc_fsCrawl,svc_fsCrawl@domainName.FQDN,svc_fsCrawl,accountPassword,Foundation server crawl account <br />
svc_spSandbox,svc_spSandbox@domainName.FQDN,svc_spSandbox,accountPassword,Sandbox service application service account <br />
svc_WebAnalytics,svc_WebAnalytics@domainName.FQDN,svc_WebAnalytics,accountPassword,SharePoint Web Analytics service account <br />
svc_SecureStore,svc_SecureStore@domainName.FQDN,svc_SecureStore,accountPassword,Secure Store Application Pool service account <br />
svc_spSTSAcct,svc_spSTSAcct@domainName.FQDN,svc_spSTSAcct,accountPassword,Security Token Service Application <br />
svc_spMetadata,svc_spMetadata@domainName.FQDN,svc_spMetadata,accountPassword,Managed Metadata Service Account<br />
…and now the magical one-line PowerShell command, this needs to run using the Active Directory module for Windows PowerShell.<br />
<a href="http://lh6.ggpht.com/_d7HMZG1Hte0/TK5b9pXNkEI/AAAAAAAAADU/W2qKQYN-5CA/s1600-h/image%5B3%5D.png"><img alt="image" border="0" height="395" src="http://lh4.ggpht.com/_d7HMZG1Hte0/TK5b-KppkRI/AAAAAAAAADY/0wYYNO9Dq_4/image_thumb%5B1%5D.png?imgmax=800" style="border-bottom-width: 0px; border-left-width: 0px; border-right-width: 0px; border-top-width: 0px; display: inline;" title="image" width="331" /></a> <br />
The Active Directory module for Windows PowerShell in Windows Server® 2008 R2 is a Windows PowerShell module (named ActiveDirectory) that consolidates a group of cmdlets. You can use these cmdlets to manage your Active Directory® domains, Active Directory Lightweight Directory Services (AD LDS) configuration sets, and Active Directory Database Mounting Tool instances in a single, self-contained package. <br />
You can install the Active Directory module by using any of the following methods: <br />
<ul><li>By default, on a Windows Server 2008 R2 server when you install the AD DS or AD LDS server roles </li>
<li>By default, when you make a Windows Server 2008 R2 server a domain controller by running Dcpromo.exe </li>
<li>As part of the Remote Server Administration Tools (RSAT) feature on a Windows Server 2008 R2 server </li>
<li>As part of the RSAT feature on a Windows 7 computer </li>
</ul>Start Active Directory module for Windows PowerShell and type the following:<br />
<strong>Import-Csv acc.csv | ForEach-Object { New-ADuser -Path 'OU=Service Accounts,DC=dev,DC=local' -Name $_.samAccountName -samAccountName $_.samAccountName -userPrincipalName $_.userPrincipalName -GivenName $_.cn -description $_.description -PasswordNeverExpires $True -CannotChangePassword $True -Enabled $true -AccountPassword (ConvertTo-SecureString $_.Password -AsPlainText -force)}</strong><br />
in the above script I have an OU called “Service Accounts” and my domain name is “dev.local”Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com1tag:blogger.com,1999:blog-583854733610692534.post-90605487535873016342010-09-23T11:40:00.001+01:002010-09-27T11:25:52.771+01:00Security Advisory 2416728 (Vulnerability in ASP.NET) and SharePoint<p>** Updated 24/09/2010 4:30PM ** – Updated with additional defensive workaround published by the ASP.NET team valid for ALL affected versions of SharePoint listed below.</p> <p>Microsoft has recently blogged that the vulnerability in ASP.Net affects SharePoint and the workaround should be applied ASAP on every single SharePoint WFE server <a href="http://blogs.msdn.com/b/sharepoint/archive/2010/09/21/security-advisory-2416728-vulnerability-in-asp-net-and-sharepoint.aspx">http://blogs.msdn.com/b/sharepoint/archive/2010/09/21/security-advisory-2416728-vulnerability-in-asp-net-and-sharepoint.aspx</a></p> <p>Microsoft has recently released a <a href="https://www.microsoft.com/technet/security/advisory/2416728.mspx">Microsoft Security Advisory</a> for a vulnerability affecting ASP.NET.  This post documents recommended workarounds for the following SharePoint products: </p> <ul> <li>SharePoint 2010 </li> <li>SharePoint Foundation 2010 </li> <li>Microsoft Office SharePoint Server 2007 </li> <li>Windows SharePoint Services 3.0 </li> <li>Windows SharePoint Services 2.0 </li> </ul> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com1tag:blogger.com,1999:blog-583854733610692534.post-71843855603209908592009-12-13T23:36:00.001+00:002009-12-13T23:36:19.846+00:00ISA 2006, Forms, SharePoint 2007 Extranet and Client Integration<p>Anyone who has worked on SharePoint 2007 extranet project with ISA 2006 used as reverse proxy and to publish SharePoint Farm, knows about Client integration challenges…</p> <p>When users try to edit a document, they are challenged and required to authenticate and even after a successful authentication, it is not possible to check the document back in to SharePoint.</p> <p>This is because despite the existing session, office client initiate another session and ISA treats this as a new session.</p> <p>The short answer to this problem is to configure a Persistent cookie on ISA web listener (Under Forms –> Advance) </p> <p><a href="http://lh4.ggpht.com/_d7HMZG1Hte0/SyV55yfDOMI/AAAAAAAAACo/1d2nDCxq8BM/s1600-h/clip_image001%5B3%5D.jpg"><img style="border-right-width: 0px; display: inline; border-top-width: 0px; border-bottom-width: 0px; border-left-width: 0px" title="clip_image001" border="0" alt="clip_image001" src="http://lh3.ggpht.com/_d7HMZG1Hte0/SyV56ZIM0FI/AAAAAAAAACs/Es5iMQjvQEw/clip_image001_thumb.jpg?imgmax=800" width="244" height="186" /></a></p> <p>BUT there are several security issues that are highlighted by MS and need to be considered:</p> <ul> <li>A malicious attacker who obtains a persistent cookie may be able to perform a brute force attack to obtain user credentials from the cookie. </li> <li>On a public computer, if the user does not log off, the session cookie can be used by the next user to access published sites. This threat can be mitigated by not enabling persistent cookies for public computers. </li> <li>Spyware may be able to access the cookie. </li> </ul> <p>The important point to consider here is that the <strong>client </strong>needs to be making the decision between Security and User experience / functionality</p> <p>In a recent project I spent some times to identify few factors that the client needed to take into consideration when making this decision:</p> <table border="0" cellspacing="0" cellpadding="0"><tbody> <tr> <td valign="top" width="225"> </td> <td valign="top" width="174"> <p><strong>This is a public or shared computer</strong></p> </td> <td valign="top" width="256"> <p><strong>This is a private computer</strong></p> </td> </tr> <tr> <td valign="top" width="225"> <p><strong>Persistent cookie file on logout</strong></p> </td> <td valign="top" width="174"> <p>Deleted</p> </td> <td valign="top" width="256"> <p>Not Deleted but user is required to authenticate (Domain name and user name are saved)</p> </td> </tr> <tr> <td valign="top" width="225"> <p><strong>Persistent cookie file when user closes the browser</strong></p> </td> <td valign="top" width="174"> <p>Not Deleted - Session is available before cookie timeout</p> </td> <td valign="top" width="256"> <p>Not Deleted - Session is available before cookie timeout</p> </td> </tr> <tr> <td valign="top" width="225"> <p><strong>Temporary Internet Files </strong></p> </td> <td valign="top" width="174"> <p>Enabling persistent cookie has no effect</p> </td> <td valign="top" width="256"> <p>Enabling persistent cookie has no effect</p> </td> </tr> <tr> <td valign="top" width="225"> <p><strong>Temporary Draft Files </strong></p> </td> <td valign="top" width="174"> <p>Enabling persistent cookie has no effect</p> </td> <td valign="top" width="256"> <p>Enabling persistent cookie has no effect</p> </td> </tr> <tr> <td valign="top" width="225"> <p><strong>Ability to open documents on SharePoint within session time (browser closed)</strong></p> </td> <td valign="top" width="174"> <p>Yes</p> </td> <td valign="top" width="256"> <p>Yes</p> </td> </tr> </tbody></table> <p></p> <p>FAQ: <br />Q) Is the cookie hashed e.g. using Hashed MACs (HMACs)? <br />A) Yes </p> <p>Q) Are server tokens erased after session end? <br />A) Yes </p> <p>Q) Is the cookie transmitted via SSL? <br />A) It is highly recommended </p> <p>Q) Are Temporary Internet files deleted when session ends? <br />A) No, But this is not caused by the persistent cookie </p> <p>Q) Are copy of the draft documents deleted if the user fail to check in / overwrite checkout? <br />A) No, But this is not caused by the persistent cookie </p> <p>Q) are there any extra consideration when accessing the site though Kiosk Stations when using persistent cookies? <br />A) Yes the followings should be considered:</p> <ul> <li>Do not select “This is a private computer”. <br /></li> <li>Perform logoff on published applications. </li> </ul> <p>Additional consideration when accessing the site though Kiosk Stations (regardless of the usage of the persistent cookies):</p> <ul> <li>Delete cookies after you finish using published applications. <br /></li> <li>Delete temporary Internet files. </li> <li>Delete temporary files that Office created when working with Microsoft Office SharePoint® Portal Server. <br /></li> <li>Delete any files that were manually downloaded to the kiosk. <br /></li> <li>Close all browser windows. <br /></li> <li>Log off from Windows, if possible. </li> </ul> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-85637464162619949052009-12-13T22:42:00.004+00:002010-01-28T13:15:36.952+00:00Windows 7: Boot from VHDRecently I have been forced to look into available options to best utilise the amount of memory available on my laptop to be able to run SharePoint 2010 VMs. There are number of options available to do this, but I have tried to simplify this as much as possible to speed up the VHD file creation and imaging process.<br />
1) Create a partition to store the VHD; optional (I had to do this since my primary partition is BitLocker encrypted)<br />
2) Download the VHD tool box from <a href="http://cid-1dc3b1edb30aea44.skydrive.live.com/self.aspx/.Public/VHDToolBox.zip">http://cid-1dc3b1edb30aea44.skydrive.live.com/self.aspx/.Public/VHDToolBox.zip</a><br />
This tool box includes:<br />
<ul><li>WIM2VHD.wsf – WIM to VHD Converter</li>
<li>ImageX.exe 64-bit (32-bit available from <a href="http://depositfiles.com/files/4563922">http://depositfiles.com/files/4563922</a>)</li>
<li>Bcdedit.exe- Command-line tool for managing BCD stores</li>
<li>intlcfg.exe - The International Settings and Configuration tool (Intlcfg.exe) is used to configure the language and locale settings in a Windows image</li>
</ul>3) Copy the Install.Wim from the OS media to the VHDToolBox folder<br />
4) Now you are ready to create your VHD. Start command prompt and navigate to the VHDToolBox folder and run the script:<br />
There are a number of switches you will need to know:<br />
/wim: specifies the path to the WIM file <br />
/sku: OS version (ServerStandard, Ultimate etc…) <br />
/vhd: specifies the path and the name of the VHD to be created <br />
/size: specifies the size of the VHD in MB <br />
/disktype: specifies the type of disk, Dynamic or Fixed<br />
For example to create a Windows Server 2008 R2 Enterprise VHD on a 40GB Fixed disk we would use the following command:<br />
cscript wim2vhd.wsf /wim: C:\VHDToolBox\install.wim /sku:SERVERENTERPRISE /vhd:F:\2K8_R2_SP2010_01.vhd /size:40960 /disktype:Dynamic/Fixed<br />
<b>Note</b>: to find the sku you could run the following imagex command on your install.wim file:<br />
Imagex /info “<install.wim location>”<br />
5) Next you need to use bcdedit.exe to add an entry to the boot menu:<br />
<ul><li>bcdedit /copy {current} /d "My New VHD Description" (This will Return the GUID of the Loader Object that you will use to replace <guid> below)</li>
<li>bcdedit /set <guid> device vhd=[driveletter:]\<directory>\<vhd filename></li>
<li>bcdedit /set <guid> osdevice vhd=[driverletter:]\<directory>\<vhd filename></li>
<li>bcdedit /set <guid> detecthal on</li>
</ul>That’s it, enjoyAnonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-26777104480858414162009-11-24T23:25:00.001+00:002009-11-24T23:25:50.765+00:00Get Ready for Microsoft SharePoint 2010<p>Certification Path for IT professionals</p> <ul> <li> <p><b>70-667 TS: Microsoft SharePoint 2010, Configuring</b> <br />Microsoft Official Curriculum: Will cover configuration of SharePoint 2010 including deployment, upgrade, management and operation on a server farm. </p> </li> <li> <p><b>70-668 PRO: SharePoint 2010, Administrator</b> <br />Microsoft Official Curriculum: Will cover advanced SharePoint 2010 topics including capacity planning, topology designing and performance tuning.</p> </li> </ul> <p>Certification Path for Developers</p> <ul> <li> <p><b>70-573 TS: Microsoft SharePoint 2010, Application Development</b> <br />Microsoft Official Curriculum: Five-day instructor-led course designed for developers with six months or more of.NET development experience. Course covers what you need to know to be an effective member of a SharePoint development team using Visual Studio 2010. </p> </li> <li> <p><b>70-576 PRO: Designing and Developing Microsoft SharePoint 2010 Applications</b> <br />Microsoft Official Curriculum: Five-day instructor-led training course designed for development team leads who have already passed the Developing on SharePoint 2010 technical specialist exam. The course covers choosing technologies for and scoping a SharePoint project, best practices for SharePoint development, configuring a SharePoint development environment, advanced use of SharePoint developer features and debugging of code in a SharePoint project. </p> </li> </ul> <p><a title="https://partner.microsoft.com/40121316?msp_id=sharepoint2010ready" href="https://partner.microsoft.com/40121316?msp_id=sharepoint2010ready">https://partner.microsoft.com/40121316?msp_id=sharepoint2010ready</a></p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-25707061173731733062009-10-29T11:12:00.001+00:002009-10-29T11:12:16.191+00:00SharePoint 2010: Getting Started with Development on SharePoint 2010 Hands-on Labs in C# and Visual Basic<p><a title="http://www.microsoft.com/downloads/details.aspx?FamilyID=C010FC68-B47F-4DB6-B8A8-AD4BA33A35C5&displaylang=en#filelist" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=C010FC68-B47F-4DB6-B8A8-AD4BA33A35C5&displaylang=en#filelist">http://www.microsoft.com/downloads/details.aspx?FamilyID=C010FC68-B47F-4DB6-B8A8-AD4BA33A35C5&displaylang=en#filelist</a></p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-43611491570464064752009-10-29T11:10:00.001+00:002009-10-29T11:10:31.749+00:00SharePoint 2010 for Project Management Success<object width="400" height="300"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=7300710&server=vimeo.com&show_title=1&show_byline=1&show_portrait=0&color=&fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=7300710&server=vimeo.com&show_title=1&show_byline=1&show_portrait=0&color=&fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="300"></embed></object> <p><a href="http://vimeo.com/7300710">SharePoint 2010 for Project Management Success</a> from <a href="http://vimeo.com/dux">Dux Raymond Sy</a> on <a href="http://vimeo.com">Vimeo</a>.</p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-10952838068188277712009-10-29T11:07:00.001+00:002009-10-29T11:07:12.086+00:00Determine hardware and software requirements (SharePoint Server 2010)<p><a title="http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx" href="http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx">http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx</a></p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-55840950970733407152009-10-04T15:09:00.001+01:002009-10-04T16:26:52.495+01:00Install SharePoint Server 2007 on Windows Server 2008 R2<p>From: Microsoft SharePoint Products and Technologies Team Blog</p> <p>Starting from Service Pack 2, Windows SharePoint Services 3.0 and SharePoint Server 2007 support Windows Server 2008 R2 and Windows Server 2008 SP2. When you try to install SharePoint bits on Windows Server 2008 R2 directly, you may see the following dialogue:</p> <p><a href="http://blogs.msdn.com/blogfiles/sharepoint/WindowsLiveWriter/InstallSharePointServer2007onWindowsServ_DDC9/snap0011_2.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="clip_image001" border="0" alt="clip_image001" src="http://lh4.ggpht.com/_d7HMZG1Hte0/SsisqmCd0SI/AAAAAAAAABw/foQQQ9sSCE4/clip_image001%5B3%5D.png?imgmax=800" width="244" height="121" /></a></p> <p>This is because Windows SharePoint Services 3.0 and SharePoint Server 2007 bits without SP2 slipstreamed are not supported on Windows Server 2008 R2. The KB article 962935 is not live on the web site yet.</p> <p>To install on Windows Server 2008 R2, for Windows SharePoint Services 3.0 you can download the slipstream builds here:</p> <p>Windows SharePoint Services 3.0 with SP2 (x86) <br /><a href="http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en">http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en</a></p> <p>Windows SharePoint Services 3.0 with SP2 (x64) <br /><a href="http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en">http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en</a></p> <p>For SharePoint Server 2007, you can follow <a href="http://technet.microsoft.com/en-us/library/cc261890.aspx">Create an installation source that includes software updates (Office SharePoint Server 2007)</a> to create one. Or you can also read on, we will go through the complete steps to create a new slipstream build for SharePoint Server 2007.</p> <p><b>Installation Steps</b></p> <p>1. Copy the content of SharePoint Server 2007 setup files from the installation media to a folder on your hard drive. </p> <p>2. Delete everything inside <b>Updates</b> folder.</p> <p>3. Download <a href="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=79bada82-c13f-44c1-bdc1-d0447337051b">Windows SharePoint Services 3.0 SP2</a> and <a href="http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b7816d90-5fc6-4347-89b0-a80deb27a082">Office SharePoint Server 2007 SP2</a> to a folder.</p> <p>Make sure your Office SharePoint Server 2007 SP2 is downloaded after July 29<sup>th</sup>.</p> <p><a href="http://blogs.msdn.com/blogfiles/sharepoint/WindowsLiveWriter/InstallSharePointServer2007onWindowsServ_DDC9/snap0013_2.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="clip_image002" border="0" alt="clip_image002" src="http://lh5.ggpht.com/_d7HMZG1Hte0/Ssisqz85PZI/AAAAAAAAAB0/Vjgzl1DemeE/clip_image002%5B3%5D.png?imgmax=800" width="244" height="130" /></a></p> <p>4. Open a command prompt,  change directory to the folder you put the downloaded patches, and run the following two commands:</p> <p>wssv3sp2-kb953338-x64-fullfile-en-us.exe /extract:<b>[Path to installation bits]</b>\Updates /quiet</p> <p>officeserver2007sp2-kb953334-x64-fullfile-en-us.exe /extract:<b> [Path to installation bits]</b>\Updates /quiet</p> <p>Change <b>[Path to installation bits] </b>to where you put the bits. These will extract all the content from the two packages to <b>Updates</b> folder. SharePoint installation program will automatically read this folder to apply the patches.</p> <p>5. Delete <b>wsssetup.dll</b>. This is a very important step so please don’t miss it.</p> <p>6. If you also need the Cumulative Updates to be applied when install SharePoint, download the latest Windows SharePoint Services 3.0 and SharePoint Server 2007 Cumulative Update packages and extract them into <b>Updates</b> folder like step 4.</p> <p>7. Your slipstream build of SharePoint Server 2007 is done!</p> <p>8. Go and install it on your Windows Server 2008 R2 box, after the installation, the site version will show <b>12.0.0.6421 </b>or possibly a higher version if you added additional cumulative update files.</p> <p><a href="http://blogs.msdn.com/blogfiles/sharepoint/WindowsLiveWriter/InstallSharePointServer2007onWindowsServ_DDC9/snap0012_2.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="clip_image003" border="0" alt="clip_image003" src="http://lh3.ggpht.com/_d7HMZG1Hte0/SsisrUUpBdI/AAAAAAAAAB4/wJ71yzuTq3Y/clip_image003%5B3%5D.png?imgmax=800" width="244" height="95" /></a></p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-40622737858733010312009-08-20T10:57:00.001+01:002009-08-20T10:57:47.719+01:00Web Application, Site Collection and Sub-Site<p></p> <h3>SharePoint Terminologies and Hierarchy</h3> <p>Following diagram illustrates the SharePoint hierarchy:</p> <p><a href="http://lh6.ggpht.com/_d7HMZG1Hte0/So0eFNdU_QI/AAAAAAAAABU/k6jY4D3ifO4/s1600-h/clip_image002%5B6%5D%5B2%5D.jpg"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="clip_image002[6]" border="0" alt="clip_image002[6]" src="http://lh4.ggpht.com/_d7HMZG1Hte0/So0eFWft27I/AAAAAAAAABc/RuA77NXc728/clip_image002%5B6%5D_thumb.jpg?imgmax=800" width="244" height="211" /></a></p> <p><b> <br /></b></p> <h3>Web Application, Site Collection and Sub-Site</h3> <p>The following points are to be considered when deciding on an extranet site structure and usage of SharePoint Components.</p> <p>· Administration Overhead</p> <p>· Scalability</p> <p>· Upgrade Scope</p> <p>· Backup/Restore</p> <p>· Security</p> <p>· Search Settings</p> <p>· Audit/IRM Settings</p> <p>· Feature Scope</p> <p>· Recycle Bin</p> <p>· Usage Reporting</p> <p>· Branding</p> <p>· Navigation</p> <p>· Content Rollup and Aggregation</p> <p>· Content Type / Site Column Scope</p> <p></p> <a href="http://lh3.ggpht.com/_d7HMZG1Hte0/So0eFltnywI/AAAAAAAAABg/CkraDOqIJBQ/s1600-h/image%5B2%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh5.ggpht.com/_d7HMZG1Hte0/So0eF51IMDI/AAAAAAAAABk/_6tHPReSoaQ/image_thumb.png?imgmax=800" width="244" height="83" /></a> <p><a href="http://lh5.ggpht.com/_d7HMZG1Hte0/So0eGevSVhI/AAAAAAAAABo/XprZ_dAaPnQ/s1600-h/image%5B5%5D.png"><img style="border-bottom: 0px; border-left: 0px; display: inline; border-top: 0px; border-right: 0px" title="image" border="0" alt="image" src="http://lh5.ggpht.com/_d7HMZG1Hte0/So0eGkwZEWI/AAAAAAAAABs/DDQDCT_idms/image_thumb%5B1%5D.png?imgmax=800" width="212" height="244" /></a> </p> <h4>Backup and Restore</h4> <p>· Full fidelity backups are only possible at the site collection level</p> <p>· If a sub-site needs to be restored then the entire site collection must be restored</p> <p>· 3rd party solutions offer full fidelity recovery at more granular levels</p> <h4>Security</h4> <p>· Site Collections allow security groups and permissions to be isolated from other site collections</p> <p>· Management is more complex with site collections</p> <p>· Difficult to see what access a user has across site collections</p> <p>· No OOTB way to synchronize settings across site collections</p> <p>· Usage of Site collections can reduce the need to break security inheritance</p> <p>· Site Collections can be used to overcome SharePoint group limitations (Cannot go over 2000 users or AD groups in a single ACL)</p> <h4>Feature Scope</h4> <p>· Features can be scoped to a Site Collection or Web (or Farm or Web Application)</p> <p>· You can prevent access to certain functionality by using site collections</p> <p>o Some Features must be scoped to a site collection</p> <p>o You might have to activate a Feature thereby (potentially) making functionality available to all users/contributors/designers of a site</p> <h4>Search</h4> <p>· Search Scopes are defined at the site collection level (You can create shared scopes via the SSP but they must be “activated” at each site collection)</p> <p>· Best bets and keywords are site collection scoped (Use a single search centre)</p> <p>· Settings must be manually (or programmatically) synchronized across site collections</p> <h4>Scalability</h4> <p>The single most critical reason for using multiple site collections is scalability</p> <p>· Limit content databases to 100GB (50GB recommended, 100GB maximum)</p> <p>· If you must go over 100GB then use only 1 site collection in the content database</p> <p>· You will encounter performance issues and possibly deadlock conditions (if over 100GB)</p> <p>· Split content approaching 100GB in a site collection into a new site collection in a separate content database (STSADM)</p> <p>· Site collections cannot live across content databases</p> <p>· Web applications can have multiple content databases attached to them</p> <h4>Reporting</h4> <p>· Usage reports are scoped at the site collection</p> <p>· There is no out of the box mechanism to get cross site collection usage reports</p> <p>o SSP administrators can get search query reports which span site collections</p> <p>· Many 3rd party products produce much more useful/sophisticated reports for cross site collection reporting</p> <h4>Branding</h4> <p>· Master pages and CSS can be used to enforce a consistent branding experience</p> <p>· Use Themes for as much as possible so that the application/system pages will be branded</p> <p>· Use Feature Stapling to automatically apply the branding. This provides a seamless experience for the end-user</p> <h4>Content Types / Site Columns</h4> <ul> <li>Features could be used to deploy to consistent Content Type and Site Columns across multiple Site Collections </li> <li>It is important that the Content Type ID remains the same – creation via the browser does not allow setting the ID across site collections </li> </ul> <h4>Cross Site Configuration</h4> <ul> <li>Solution Accelerator from MSFT (http://www.codeplex.com/SPConfigurator) </li> <li>The tool automates the process of deploying site settings in all or selected sites in a server farm: <ul> <li>Applying Master Pages across a SharePoint server farm </li> <li>Setting up Web Titles for all or selected site collections across the farm </li> <li>Applying audit control settings to all or selected sites </li> <li>Adding advanced settings such as “Allow content type management” to all types of lists </li> <li>Adding a new Expiration Policy at the site collection level </li> <li>Adding a new Expiration Policy to content types, lists, and documents </li> </ul> </li> </ul> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-13403983888530783452009-06-18T17:00:00.001+01:002009-06-18T17:00:24.097+01:00Useful TechNet links for Planning, Designing; Securing an Extranet (SharePoint Server 2007)<p> </p> <p>Plan authentication methods (Office SharePoint Server) </p> <p><a href="http://technet.microsoft.com/en-us/library/cc262350.aspx">http://technet.microsoft.com/en-us/library/cc262350.aspx</a> </p> <p><b></b></p> <p>Design extranet farm topology (Office SharePoint Server) </p> <p><a href="http://technet.microsoft.com/en-us/library/cc263513.aspx">http://technet.microsoft.com/en-us/library/cc263513.aspx</a> </p> <p>Downloadable book: Planning an Extranet Environment for Office SharePoint Server </p> <p><a href="http://technet.microsoft.com/en-us/library/cc262400.aspx">http://technet.microsoft.com/en-us/library/cc262400.aspx</a> </p> <p>Planning, Designing; Securing an Extranet and Internet Facing WSSv3 and SharePoint Server 2007 Environments </p> <p><a href="http://blogs.msdn.com/sharepoint/archive/2006/08/08/planning-designing-amp-securing-an-extranet-and-internet-facing-wssv3-and-sharepoint-server-2007-environments.aspx">http://blogs.msdn.com/sharepoint/archive/2006/08/08/planning-designing-amp-securing-an-extranet-and-internet-facing-wssv3-and-sharepoint-server-2007-environments.aspx</a> </p> <p>External Collaboration Toolkit for SharePoint </p> <p><a href="http://technet.microsoft.com/en-us/library/cc268155.aspx">http://technet.microsoft.com/en-us/library/cc268155.aspx</a></p> Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-40187335675542608542009-06-16T16:57:00.000+01:002009-06-16T17:01:10.588+01:00Useful Sharepoint Links<p>A fantastic blog from <a href="http://blogs.msdn.com/user/Profile.aspx?UserID=14459">pareshj</a></p><p>Useful Links<br /><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/7bd43d63-26e9-45b7-b1bb-f8775a2607091033.mspx?mfr=true">MOSS Video Demos (Total 14 Modules)</a><br />· <a href="http://technet.microsoft.com/en-us/office/bb463251.aspx">Before You Begin with SharePoint Server 2007</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/301ed832-95da-4251-b266-7be6288f7ea01033.mspx?mfr=true">MOSS Tools for performance and capacity planning</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/64f7f9fb-3994-477f-9e6d-570812c3d5131033.mspx?mfr=true">Downloadable book: Planning and architecture for Office SharePoint Server 2007</a><br />· <a href="http://go.microsoft.com/fwlink/?LinkId=79552&clcid=0x409">MOSS 2007 - Planning and Architecture for Office SharePoint Server 2007</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/3e3b8737-c6a3-4e2c-a35f-f0095d952b781033.mspx?mfr=true">MOSS 2007 - Administrator Guide</a><br />· <a href="http://blogs.technet.com/josebda/archive/2008/03/15/complete-reference-of-all-stsadm-operations-with-parameters-in-moss-2007-sp1.aspx">Complete reference of all STSADM operations</a><br />· <a href="http://office.microsoft.com/en-us/groove/HA102164261033.aspx?pid=CL100604881033">Using the 2007 Microsoft Office system for disaster planning and response</a><br />· <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=d013465b-454a-4a18-8ec4-6a5a82c81fb3&DisplayLang=en">Planning and Designing SharePoint Products and Technology Solutions for Geographically Dispersed Sites</a><br />· <a href="http://blogs.technet.com/josebda/archive/2008/03/15/complete-reference-of-all-stsadm-operations-with-parameters-in-moss-2007-sp1.aspx">Complete reference of all STSADM operations</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/a59c4e8f-9b7f-4127-8199-1b9ab76991501033.mspx?mfr=true">Complete reference of all PSCONFIG operations</a><br /><br />Best Practices<br /><br />· <a href="http://technet.microsoft.com/en-us/office/bb463251.aspx">Before You Begin with SharePoint Server 2007</a><br />· <a href="http://www.microsoft.com/downloads/details.aspx?familyid=cb944b27-9d6b-4a1f-b3e1-778efda07df8&displaylang=en">Best Practices Analyzer for WSS 3.0 and MOSS2007</a><br />· <a href="http://msdn2.microsoft.com/en-us/library/bb219479.aspx">Writing SQL Syntax Queries for Relevant Results in MOSS2007</a><br />· <a href="http://office.microsoft.com/en-us/winsharepointadmin/HA011608261033.aspx">Backing Up and Restoring Web Sites with Stsadm</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/64f7f9fb-3994-477f-9e6d-570812c3d5131033.mspx?mfr=true">Downloadable book: Planning and architecture for Office SharePoint Server 2007</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/4d88c402-24f2-449b-86a6-6e7afcfec0cd1033.mspx?mfr=true">MOSS Hardware and Software Requirements</a><br />· <a href="http://office.microsoft.com/en-us/sharepointserver/HA101978031033.aspx">SharePoint 2007 products comparison download</a><br />· <a href="http://office.microsoft.com/en-us/sharepointtechnology/FX101758691033.aspx?mode=print">Which SharePoint technology is right for you?</a><br />· <a href="http://technet2.microsoft.com/Office/f/?en-us/library/6f03049f-5bfe-4807-b609-0e2d4a9ec3b51033.mspx">White Paper: Working with large lists in Office SharePoint Server 2007</a><br />· <a href="http://technet2.microsoft.com/Office/en-us/library/301ed832-95da-4251-b266-7be6288f7ea01033.mspx?mfr=true">MOSS Tools for performance and capacity planning</a><br /><br />How to Deploy updates for SharePoint 2007<br /><br />· <a href="http://technet.microsoft.com/en-us/library/cc288269.aspx">Deploy software updates for Windows SharePoint Services 3.0</a><br />· <a href="http://technet.microsoft.com/en-us/library/cc263467.aspx">Deploy software updates for Office SharePoint Server 2007</a><br />· <a href="http://support.microsoft.com/kb/944267">How to troubleshoot common errors that occur when you run the SharePoint Products and Technologies Configuration Wizard</a><br /><br />How to configure Alternate Access Mappings (AAM) successfully<br />· <a href="http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=8">http://sharepoint.microsoft.com/blogs/fromthefield/Lists/Posts/Post.aspx?ID=8</a><br /><br />What every SharePoint administrator needs to know about Alternate Access Mappings<br /><br />· <a href="http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx">http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx</a><br />· <a href="http://blogs.msdn.com/sharepoint/archive/2007/03/19/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-2-of-3.aspx">http://blogs.msdn.com/sharepoint/archive/2007/03/19/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-2-of-3.aspx</a><br />· <a href="http://blogs.msdn.com/sharepoint/archive/2007/04/18/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-3-of-3.aspx">http://blogs.msdn.com/sharepoint/archive/2007/04/18/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-3-of-3.aspx</a><br /><br />STSADM COMMANDS<br /><br />· <a href="http://blogs.technet.com/josebda/archive/2008/03/15/complete-reference-of-all-stsadm-operations-with-parameters-in-moss-2007-sp1.aspx">Jose Barreto's Blog Complete reference of all STSADM operations (with parameters) in MOSS 2007 SP1</a><br />· <a href="http://blogs.technet.com/josebda/archive/2007/03/22/complete-reference-of-all-stsadm-commands-with-options-in-moss-2007.aspx">Jose Barreto's Blog Complete reference of all STSADM operations (with parameters) in MOSS 2007</a><br /><br />SharePoint Administration Toolkit<br />· <a href="http://technet.microsoft.com/en-us/library/cc508851.aspx">SharePoint Administration Toolkit (Office SharePoint Server)</a><br /><br />TCP Chimney should be disabled<br /><br />· <a href="http://support.microsoft.com/kb/942861">http://support.microsoft.com/kb/942861</a><br />· <a href="http://support.microsoft.com/kb/912222/">The Microsoft Windows Server 2003 Scalable Networking Pack release</a></p>Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com0tag:blogger.com,1999:blog-583854733610692534.post-22533161719887336572009-01-29T13:43:00.000+00:002009-01-29T13:54:42.965+00:00SharePoint Accessibility ResourcesIt has been a while since I have posted anything; this is mainly because I have been extremely busy and lack of personal time...<br />I found the following resource on SharePoint Accessibility extremely useful. This is taken from <a href="http://blogs.msdn.com/sanjaynarang/default.aspx">Sanjay Narang</a>'s blog.... <br /><br />"I've been working on implementing accessibility requirements for a public facing site on MOSS. Though keywords such as "SharePoint accessibility" provide a number of results on Live Search or any other engine, I had difficult time in searching the appropriate resources. Thought it would be worthwhile sharing the resources that I found and providing a context around them. Here are these resources: <br /><br />Microsoft's Statements/Papers on SharePoint Accessibility <br />We have couple of white papers and articles on this topic, however, search engines are yet to rank them better to come towards the top. Here are these: <br /><br />Article: Accessibility features (as provided by Office Online) <br />http://office.microsoft.com/en-us/sharepointserver/CH100948721033.aspx <br /><br /> <br /><br />Blog: Improvements in accessibility – Blog entry on SharePoint Team blog by Lawrence Liu. Though it's pretty old entry (April 2006) and was written for pre RTM version, but you can find a good summary of new and improved accessibility features. Most of this holds for RTM also. The blog groups the improvement areas in categories such as Headings, Navigation, Keyboard, Graphics, High Contrast – Low Vision, HTML Controls and also relates them to specific checkpoints from WCAG 1.0 <br />http://blogs.msdn.com/sharepoint/archive/2006/04/24/improvements-in-accessibility.aspx <br /><br /> <br /><br />Whitepaper: Deliver accessible solutions by using Office SharePoint Server - This downloadable white paper provides information and guidelines about the issues that organizations face when delivering Web solutions, including those built by using Microsoft Office SharePoint Server 2007 that are accessible to people with disabilities. It's a pretty good paper to read when you are starting your journey on accessibility. It describes the available out-of-the-box (OOB) accessibility features in MOSS 2007 and also provides a very good summary on Accessibility Kit for SharePoint (AKS). If you want to know all about AKS in 4 pages, this is the article to read. However, if you are looking for best practices or implementation approaches – you need to look for a different paper. Have a look at the next one <br />http://technet.microsoft.com/en-us/library/cc668367.aspx <br /><br /> <br /><br />Whitepaper: Best practices for developing accessible Web sites - This downloadable white paper provides information about designing and developing accessible Web sites in Microsoft Office SharePoint Server 2007. If you are looking for implementation best practices that you couldn't find in the white paper listed above, this is a very useful resource. In this paper, Waldek Mastykarz, provides tips and techniques that are categorized in different areas such as General (HTML, javascript), .Net, MOSS, and IIS. You'll find tips such as appropriate MIME type, things to ensure while writing custom controls e.g. use Render method RenderControl <br />http://technet.microsoft.com/en-us/library/cc716527.aspx <br /><br />Other Resources <br />Blog: SharePoint Accessibility - Is MOSS 2007 accessible? – Provides a quick comparison of SPS 2003 and MOSS 2007 with Priority 1 requirements <br />http://www.21apps.com/sharepoint/sharepoint-accessibility-is-moss-2007-accessible/ <br /><br /> <br /><br />Article: Building ASP.NET 2.0 Web Sites Using Web Standards - Though, this article provides the best practices for ASP.net in general, it is very useful from SharePoint perspective for developing custom web parts, field controls, web controls and user controls. The article provides the basic knowledge of mechanisms available within the ASP.NET 2.0 platform which support developing accessible web sites. This contains a lot of examples that would be useful for people who are new to accessibility. The techniques provided here would be mostly used while writing the "Render" or "CreateChildControls" methods. For example, you'll find this tip from this paper: "Provide an AssociatedControlId property when declaring an ASP.NET Label controls, so that the control renders a <label> tag." <br />http://msdn2.microsoft.com/en-us/library/aa479043.aspx <br /><br /> <br /><br />Blog: CSS Friendly Control Adapters in SharePoint 2007 (A Walk-Through) – Provides step-by-step walkthrough of how to use CSS Friendly Adapters, which are very helpful in creating CSS only, standards compliant controls (like the menu and treeView) for easy styling. These would be useful in areas where you'd like to use OOB navigation control in a publishing site. <br />http://www.sharepointblogs.com/mossman/archive/2007/03/08/css-friendly-control-adapters-in-sharepoint-2007-a-walk-through.aspx <br /><br /> <br /><br />Blog: Web part zone adapter – if you are using web part zone, it is difficult to be compliant as web part zones use HTML tables for layout purposes. This adapter does a nice job on converting those table tags to div tags. <br />http://blogs.msdn.com/eigilm/archive/2008/10/07/web-part-zone-adapter.aspx <br /><br /> <br /><br />Blog: Another day, another accessible MOSS website - Provides a step-by-step walkthrough on how to go about developing an accessible site <br />http://blog.thekid.me.uk/archive/2007/05/01/another-day-another-accessible-moss-website.aspx <br /><br /> <br /><br />Toolkits <br />Accessibility Kit for SharePoint (AKS) – this kit is used by HiSoftware in collaboration with Microsoft and free for use. One thing you'd like to know that, the kit provides maximum use when you use SharePoint OOB UI and controls. If you are building a publishing site, where most of the controls and UI are custom developed, AKS can be used for references purpose mostly. <br />http://aks.hisoftware.com <br /><br />Presentation: Accessibility Kit for SharePoint - Building Accessible Websites on MOSS 2007 – slide deck from session at SPC2008; provides some screenshots on how AKS kit works, which is sometimes difficult to understand through the documentation that comes with the installer <br />http://blogs.msdn.com/sharepoint/archive/2008/03/19/slidedeck-for-accessibility-kit-for-sharepoint-building-accessible-websites-on-moss-2007-session-at-spc2008-now-available.aspx <br /><br /> <br /><br />ARF – Definition as provided at its web site - ARF is a FREE (open source) development framework for SharePoint, both MOSS and WSS. It provides a consistent solution to common problems found in SharePoint publishing development. <br />http://www.spworks.co.uk/arf/what.aspx <br /><br /> <br /><br />SharePoint Compliancy Toolkit - has been designed to help you achieve the accessibility level as described in Webrichtlijnen (Dutch government accessibility guidelines comparable to WCAG 1.0 Priority 2+) <br />http://www.sharepointblogs.com/tmt/archive/2007/10/20/Accessible-Web-Content-Management-Solutions-based-on-Microsoft-Office-SharePoint-Server-2007.aspx <br /><br /> <br /><br />Accessibility in General <br />E-Book: Understanding Accessibility - A Guide to Achieving Compliance on Web Sites and Intranets will assist you in achieving compliance with U.S. federal standards and W3C Guidelines for Web content. From the book home page – "This book is for Web Authors, Project Managers and basically any individual or team that is faced with the challenge of creating an accessible Web site or retrofitting a Web site to make it accessible. If you are new to accessibility we suggest you start at the beginning and read the entire book. If you are tasked with repairing sites that are not accessible, this book will serve as a reference and guide. If you review sites for accessibility this book will help you to select tools and understand accessibility requirements." <br />http://www.hisoftware.com/uaccess/Index.html <br /><br />W3C Resources: <br />Official W3C Recommendation for Web Content Accessibility Guidelines 1.0 - http://www.w3.org/TR/WCAG10/ <br />Web Accessibility Initiative (WAI) – Provides all resources from W3C such as Introductions, Techniques and Guidelines on Managing and Evaluating Accessibility <br />http://www.w3.org/WAI/ <br /><br /> <br /><br />Filed under: SharePoint, Accessibility, Resources, MOSS, WSS<br />Comments<br /># infoblog » SharePoint Accessibility Resources said on December 1, 2008 4:00 AM: <br />PingBack from http://blog.a-foton.ru/index.php/2008/12/01/sharepoint-accessibility-resources/"Anonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com1tag:blogger.com,1999:blog-583854733610692534.post-45958949267175607272007-06-26T11:26:00.000+01:002007-06-26T15:08:42.085+01:00Downgrading from MOSS Enterprise to Standard<span style="font-size:130%;color:#009900;"><em>Prepare and Backup</em></span><br /><br />1. Backup all SQL databases<br /><br />2. Make a List of Web applications and related IIS site, Application Pool and Content Database.<br /><br />3. Disable enterprise feature at Farm Level, for each web application and for all sites<br /><br />4. Note which server is hosting SharePoint Central Administration and confirm that there are no pending or failed backup/restore or upgrade timer jobs.<br /><br />5. Make a list of every server that host SharePoint Central Administration.Navigate to <strong>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole</strong> and record the value. Repeat these steps for each server with MOSS installed<br /><br />6. Backup the 12.0 hive from the registry (Navigate to <strong>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0</strong> Right Click on 12.0 and click Export)<br /><br />7. Now edit the registry key by renaming the dsn key. Navigate to [<strong>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB\dsn</strong>] Right click on dsn and click rename<br /><br />8. Purge the old configuration wizard logs. From command prompt type "<strong>cd "%programfiles%\common files\microsoft shared\web server extensions\12\logs</strong>" Then type <strong>del psc*.log </strong><br /><strong><br /></strong>9. Check to see if you have installed any language packs and uninstall them.<br /><br /><span style="font-size:130%;color:#009900;"><em>Uninstall Enterprise Edition</em></span><br /><br />10. Now uninstall MOSS Enterprise from Add/Remove Programs. This will uninstall MOSS completely from your machine but will not delete any of your data.<br /><br />11. Reboot your server<br /><br /><em><span style="font-size:130%;color:#009900;">Install Standard Edition</span></em><br /><br />If you have more than one MOSS server repeat these steps for all servers in the farm.<br />Now that all servers have had MOSS uninstalled from them and have been rebooted you need to install MOSS 2007 Std. You will perform the following steps on one server at a time. Start with the web front end server that previously hosted Central Admin and then you may do all additional servers in any order. Perform only on one server at a time. If any server fails resolve the issue before continuing to the next server.<br /><br />1. De-Select the box for running the Configuration Wizard and click Close.<br /><br />2. Now install any necessary language packs on the server. Instructions found <a href="http://technet2.microsoft.com/Office/f/?en-us/library/5a2be738-df29-43cd-b361-84b7822164e31033.mspx">here</a>.<br /><br />3. Once all servers have been installed return to your original web front end server which will host SharePoint Central Administration.<br /><br />4. Click Start > All Programs > Microsoft Office Server > SharePoint Configuration and Technologies Configuration Wizard.<br /><br />5. Click Next at the Welcome screen.<br /><br />6. At the warning message click Yes.<br /><br />7. At the Completing SharePoint screen you should see your database and database server listed. Click Next.<br /><br />8. You will see a warning message reminding you to install MOSS on all servers in your farm before proceeding. Ignore this warning message and click Ok<br /><br /><span style="font-size:130%;color:#009900;"><em>Post Configuration</em></span><br /><br />Now find out what your servers search topology is.<br /><br />1. Go to SharePoint Central Administration and click the Operations tab<br /><br />2. From Topologies and Services click Services on Server<br /><br />3. If the Office SharePoint Server Search is started from the command line on this server you need to run the command <strong>stsadm -o osearch -action start</strong><br /><br />4. Recreate Web application Using the Existing IIS site and Application Pool and attach the content databases to themAnonymoushttp://www.blogger.com/profile/12209114618050672004noreply@blogger.com2