1. Vast Names - https://www.vastnames.com - advanced functionality including name generation, thesaurus, sessions, favourites and instant search.  Designed for Web Designers and Business Consultants to help their clients find domain names
2. Bust A Name - https://www.bustaname.com - generates new names
3. Dot O Mator - https://www.dotomator.com/ - generates new names
4. Wordoid - https://wordoid.com/
5. Domain typer - instant search - https://domaintyper.com/

Digital Marketing Personalisation

There are three primary types of personalisation used across Digital Marketing today - these are:

• Declared Personalisation - the user "ticks boxes" or includes words such as "[X]  Camera Enthusiast", "I like: Cameras, Walking".  The SharePoint 2010 Audience Targeting feature is a "declared" approach to personalisation
• Learnt Personalisation - An approach whereby the user's interests are learnt from their behaviour - for example if a user "mostly" clicks on high-end "enthusiast" cameras, then the system will automatically 'learn' that preference and provide products that are relevant to the 'enthusiast'. 
• Anonymous Personalisation -  Personalisation in which the interests of the user are 'learnt' in one location, but then applied as the user arrives at the SharePoint 2010 website.  A solution in this space is AdRock - a Microsoft solution that is able to learn personalisation from a user's behaviour on a site such as NineMSN, but then be able to use this behaviour on other sites such as Contoso.com.   This is termed 'anonymous' personalisation as the Contoso website has does not have any declared interests from the user, and neither does it have "learnt" personalisation from previous behaviour on the Contoso website.  Instead - behaviour from the Atlas advertising network is passed to the Contoso website (with the user's permission) to allow the Contoso website to provide a more personalised experience the moment that the user's Live ID is activated.

Audience Targeting - Declared Personalisation

Audiences are part of a User Profile service application that enables organizations to target content to users based on a flexible set of rules. Audiences can be defined by one or a combination of the following items:

• By public properties in user profiles
• Active Directory
• Membership in a distribution list
• Membership in a Windows security group
• Location in organizational reporting structure

An audience is defined by a collection of one or more audience rules and by whether all or only one of the audience rules must be met when evaluating membership. An audience rule can be based on membership in a user profile
property (and other active directory related roles/groups). In a Digital Marketing scenario it is common for user's to nominate specific interests - and to store these in the user profile.  To define each audience rule, you must
select an operand, operator, and value.

Once an audience has been defined, it must be compiled on a regular basis because the underlying user profile properties and membership in directory services and groups can frequently change. An administrator schedules the timer job that controls when audiences are compiled.

See also: https://technet.microsoft.com/en-us/library/cc261958.aspx

MagiClick BehaviourPad- Learnt personalisation

https://www.magiclick.com/BehaviorPad/

BehaviorPad helps maximize conversions & revenues by enabling the
administrator to dynamically change the website's content based on visitors'
data and their tracked actions.    BehaviorPad provides a simple way to
implement behavioral targeting logic on your website with minimal or no input
from your IT department or development agency.

The process is as
follows:

• Select the page on your website, on which you want to implement behavioral
  targeting logic
• Select your targeting criteria
• Select the action you want your website to take when the criteria are
  met

Available rules include:

• Referrer - Which website did the visitor come from?
• Search Keywords - If the visit has originated from a search engine, which
  keywords has the visitor been looking for?
• User Agent - Which browser, operating system, platform etc. is the visitor
  using?
• Geolocation - Which country or city is the visit originating from?
• Visit Count - New or returning visitor? If returning, how many times did he
  or she previously visit our site?
• Page/Directory Visits - Which pages or directories has the person previously
  visited on our website, and how many times?
• Cookie Check - Does the visitor have a cookie we have placed previously by
  our site?

The solution also includes concepts such as "if the user visits type of page
X twice"

Please note that other solutions that cover not just personalisation are available - for example the IntLock SharePoint marketing Suite

* https://www.intlock.com/

https://windows.microsoft.com/en-US/windows-8/iso  (ISO images)

Enjoy!

From the site: "The Windows 8 Consumer Preview ISO files (.iso) are provided as an alternative to using Windows 8 Consumer Preview Setup. If you are on a PC running Windows and want to install the consumer preview on another partition, another PC, or a virtual machine, we recommend youdownload Windows 8 Consumer Preview Setup and use the built-in tools for converting an ISO image into installation media, such as a DVD or USB bootable flash drive. You can find additional information, including a list of supported upgrades, in the FAQ."

Important note:

Note before you download: Windows 8 Consumer Preview is prerelease software that may be substantially modified before it’s commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here. Some product features and functionality may require additional hardware or software. If you decide to go back to your previous operating system, you'll need to reinstall it from the recovery or installation media that came with your PC.

The Alternate Access Mappings (AAM) of SharePoint allows a website to function correctly under different "inbound" domain names.  This feature can also include reverse proxies and load balancing scenarios. 

Assuming that you have two domain names: "fourthcoffee.com" and "contoso.com" - how can you arrange for SharePoint to not just accept and respond to both domain names - but change any (incorrectly) specified domain names that people have accidentally used internally?

An example would be the following:

<a href="https://www.fourthcoffee.com/landingpage.aspx>link to the landing page</a>

while this link works well on the fourthcoffee.com website - the same link will fail if the page is used on Contoso.com.  In general this problem doesn't arise, as virtually all links to content within SharePoint should be "relative links" that don't include a domain name.  An example is:

Relative link:

<a href="https://blogs.technet.com/landingpage.aspx>link to the landing page</a>

How can this problem be solved? As the link is within the HTML itself - then the HTML must be adjusted to translate https://www.fourthcoffee.com into https://www.contoso.com .  This is where ourbound "rewriting" of the web page is useful, and it is often used in conjunction with AAR.

For details on AAR - please see  https://technet.microsoft.com/en-us/sharepoint/Video/ff679917, however I'll include a brief undown on the overall process here:

Assuming that your external domain name is www.sharepointinternet.com :

Create a binding for the Site in IIS to www.sharepointinternet.com

Edit the site bindings Start IIS manager Right-click the site and "edit bindings"
Add a new site binding for "sharepointinternet.com"

Create the alternate access mapping in SharePoint 2010

Simply creating the binding in IIS Manager doesn't create the proper binding to Sharepoint - in addition you also need to create the Alternate Access Mapping for the binding itself.

From Central Admin: Choose "application management" Choose "Configurate alternate access mappings"
Edit the alternate access mapping Choose the correct "alternate access mapping collection" at the top right Choose "Edit Public URLs" Add the new URL for the correct zone (eg Internet)

Add the reverse rewriting rules (in the HTML)

If the URLs within the HTML refer to the incorrect domain name - these will need to be re-written using the IIS URL Rewriting Module 2.0.  In order to rewrite the HTML returned from IIS - configure the rewrite rule as follows:

Note that you may need to download and install the following:

• The URL Rewrite module - https://www.iis.net/download/URLRewrite
• The Application Request Routing module - https://www.iis.net/download/ApplicationRequestRouting

Additional details on the framework (and ASP.NET routing) are here:

• https://learn.iis.net/page.aspx/496/iis-url-rewriting-and-aspnet-routing/ 

For the site Click on URL Rewrite
Add a blank rule
Add a 'precondition' to only process HTML.  A side effect if this is not done is that the URL Rewriter module will error - and send back "500 Server error" messages for non-HTML items such as Javascript.  Sharepoint editing and menus will not work.   From "Precondition" - choose "ResponseIsHtml1" - or create a new rule where the Content-type is "text/html".    The rule becomes: {RESPONSE_CONTENT_TYPE}   <-- Condition input matches ^text/html
The values should be similar to the following: Pattern (using Regular Expressions - https://www.regular-expressions.info/) Note - this uses a pattern capture with brackets.  Use the "test pattern" button to examine the pattern. Details on the test pattern and captures are available here: https://learn.iis.net/page.aspx/460/using-the-url-rewrite-module/   Actions The action should be "rewrite" The rewrite value (the new URL) should include a replacement pattern - the "R:1" sections.  These R:(number) sections can be found using the "test pattern" button.    Note well - This rewrites the URLs within outbound HTML only.  The inbound URLs (domain names and URLs hitting the SharePoint server aren't affected - these should be catered for using hthe the bindings and alternate access mappings above).
Choose where URLs and domain names should be matched (generally within A and IMG tags at least)

The statement from Ascentium is as follows:

"Ascentium, a technology-enabled digital marketing agency is assuming all future product development, marketing, and support of Commerce Server, subsequent to the recently released Microsoft Commerce Server 2009 R2 from Microsoft. In September, Ascentium acquired Cactus Commerce – Microsoft’s Commerce Server development partner for the last 4 years. Under that partnership, Microsoft released Microsoft Commerce Server 2009, Commerce Server 2009 R2 along with several service packs.

Ascentium is well poised to continue Commerce Server development efforts with a commitment to ongoing product investment and a customer-driven roadmap.  "

This means that Commerce Server will continue to be available to customers as part of the overall SharePoint direct technology and partner technology stack, and that Commerce solutions can be implemented on Sharepoint with Commerce Server 2009 now - with future product releases and additional features being created in future.

Are there other options for Commerce and SharePoint 2010? - yes, in theory SharePoint will cooperate with any virtually any other commerce server solution.  SharePoint would contain the detailed content, while the commerce component will handle payment and fulfilment.

Examples of other commerce solutions that will interoperate with SharePoint 2010 include:

• Commerce Server 2009 R2 - https://www.microsoft.com/commerceserver/
• Optimus BT - https://www.optimusbt.com/
• Aivea - https://www.aivea.com/aivea-commerce-server.htm
• CommercePoint - https://www.sharepointinnovations.com/sharepoint-ecommerce/default.aspx
• Itequia - https://oriolquinquilla.tech.officelive.com/solutions_Itequia_eCommerce_for_sharepoint_en.aspx  

As always - comments are welcomed, as are other links to other solutions not mentioned here.

Once a customer has logged into an SharePoint 2010 portal it is far easier to create more engaging experiences for them by providing account details, graphs, charts and analytics – as well as enabling the customer to use forms based functionality to interact with the business in a transactional sense.

• Customer and partner portals are viewed as a key enabling mechanism to permit businesses with an ability to create deep customer loyalty and facilitate advanced solutions such as:
• Customer self-service portals (for example service portals, wiki's and Microblogs)
• Advanced customer workflow
  Maps
• Search driven websites where information is rapidly surfaced in response to user queries
• Personalized websites that remember the interests products and services that customer uses or owns and modifies the site presentation accordingly to make these easier to find or promote related products

• Examples and introductory videos:
  https://social.technet.microsoft.com/wiki/contents/articles/1546.aspx?wa=wsignin1.0
  
• ADFS 2.0 - https://technet.microsoft.com/en-us/library/adfs2(WS.10).aspx
• Azure ACS
  https://www.microsoft.com/windowsazure/features/accesscontrol/
• Implementation blog:
  https://blogs.pointbridge.com/Blogs/nielsen_travis/Pages/Post.aspx?_ID=38
• https://channel9.msdn.com/Events/BUILD/BUILD2011/SAC-858T 

• https://lovecleanlondon.org/account/logon
• https://www.dubaibank.ae/  - case
  study: https://www.microsoft.com/casestudies/Case_Study_Detail.aspx?casestudyid=4000002490

The licence is at the bottom of this page, and all aspects of the licence must be complied with in order to use the code.

​Digital Marketing Office Materials Generator

OMG includes a "language" within Word 2010 that can be used to update template-style documents with information from Excel models.  OMG models all complexity and mathematics in Excel (where it is easily managed), whilst document templates are created within Word 2010.  A generation cycle blends the Excel model information with the Word template and creates a set of output documents.

Multiple documents can be created during a single generation run - allowing a single Excel model to be the reference information for documents that may be overviews, in-depth technical architectures, or pricing..

OMG is used to output Word documents such as:

• Architecture and pricing documents
• Solution benefits overview
• Architecture documents
• Pricing documents
• Templated "forms" from Excel or databases (requires custom code for databases)

 

OMG uses a simple templating language system within Word to output the generated documents. It is designed with extensiblity in mind and permits the easy definition of new template functions to be added to the processing cycle. 

 

 

Template commands within Word supports standard programming features such as:

• Excel Model references - Easy references to Excel model information  (simply include cell names in curly braces - eg {customer} )
• IF statements  (if Excel value THEN include Word text )
• FOREACH statements (foreach cell in a group of cells from Excel)
• INCLUDE files  (include a file, including the ability to conditionally include a file)

 

The Hello World template

Creating templates are easy - take any existing Word 2010 document and externalise template in it to Excel, then include references in your template to the Excel document.

 

1. Create a template

 

A simple example document could be: "Hello World, this is your lucky day - you have been templated!"

 

2. Externalise content to Excel 2010

 

Change the above Word document to:

 

"Hello {noun}, this is your lucky day - you have been {verb}-ed!"

 

The Word document should have a name that ends in ".template".   Note also the use of curly braces around 'variables' - See the following for information on variables - https://en.wikipedia.org/wiki/Variable_(programming)

 

Create an Excel file - a common name for the Excel file is "model.xlsx" or similar.  This file will typically contain the information used by all templates within the generation, although each document could use different Excel files.  Management of information - including validation - is made easier by centralising all the mathematics, modelling and information into a single file however.  The reference in the Open Excel call (below) must always be 'model'.

 

Create named cells in the Excel file (see below) - for "Noun" and "Verb"

 

Eg

 

Cell A1 - Value "World", name "Noun"

Cell A2 - Value "Template", name "Verb"

 

3. Include a command to open the Excel file in your template

 

The full template text (Hello world.template.docx) becomes:

{Excel.Open("model", "Test.xlsx")}

"Hello {noun}, this is your lucky day - you have been {verb}-ed!"

 

4. Run OMG -  from the attached distribution use the "OMG_Program_beta_2_2011_12_13a" ZIP file and look in the Debug directory

 

Run "OfficeTemplateEngine.exe" or "__start_TemplateEngine.cmd"

 

For the "Choose a directory..." - use the directory that contains your Word file ending in ".template.docx" - for example if your directory is as follows:

 

c:\users\David\Documents\OMG_Example

c:\users\David\Documents\OMG_Example\Hello world.template.docx

 

containing a file "Hello world.template.docx" - then use the directory "c:\users\David\Documents\OMG_Example".

 

Loading this directory will indicate that "Hello world.template.docx" is ready to generate.

 

Click the "generate" button

 

5. New files generated

A new file - "Hello world.docx" is created.  The '.template' is removed from the filename - this becomes the name of the new output file.

 

The output in the file will be:

"Hello World, this is your lucky day - you have been Template-ed!"

Note that multiple files can be generated in a single run.

 

Overview

Templates are enclosed in curly braces and either refer to an Excel model or execute commands such as opening the model. For example this next line is blank in the output document, but it opens the named Excel document. It creates an internal variable "model" that's referred to later in the document. The italics are ignored for the purposes of executing the template, although the output is styled identically.

The default name that’s used for shorthand references to Excel named cells is “model”, so this is the variable name to generally use when opening an Excel document.

• {Excel.Open("model", "Test.xlsx")}

Referring to Excel cells:

Referring to Excel cells is via references enclosed in curly braces. These references optionally include an output style (format) after the reference. Creating these names within Excel is covered later in this document.

• Customer: {customer}
• Donation amount: {Donation_amount dollar}
• Date of donation: {Date_of_donation date}
• Quantity: {Quantity}
• Percent: {Percent_value percent}
• Will you donate? {Definitely_donate yesno}

There are three types of template commands above:

• Open the Excel model
• A simple reference to a named cell – e.g. “customer”
• A reference to a named cell with an output format – e.g. “Date_of_donation date”
• This is the same as a simple reference but with the type after the reference
• Valid formats are date, percent, dollar, yesno or truefalse

Creating named cells in Excel

In order to create named cells within Excel use the technique “Name a cell or a range of cells” in the following document: https://office.microsoft.com/en-us/excel-help/define-and-use-names-in-formulas-HA010342417.aspx#BMcreate_a_name_by_using_a_selection_of

The simplest technique to create a name is as follows (Office 2010):

• Select a cell
• Click in the box shown below and type the name – eg “Customer” into the box in the top left underneath the ribbon (highlighted below)

Including other documents

Include a file:

• {Word.Include(“IncludedFile.docx”)}

Conditionally include a file:

{include if ($model.GetNamedCell(”Definitely_donate”)) “IncludeIfTrue.docx”}

IF statements

To have a section of the document included or not depending on a variable use the following template text:

{if ($model.GetNamedCell(”Definitely_donate”))}

     This section of text will only be included if the named cell is true

{end}

FOREACH statements

A typical requirement is to produce copies of a document for a number of similarly named variables in the Excel document as follows. In the Excel document there are four named cells: Name1, Name2, Name3 and Name4. Note that because Name4 doesn’t contain anything it is not included in the foreach results.

{ foreach ($nameSuffix in $model.GetAllCellsLike(“Name”))}

• Name : {Name$nameSuffix}

{end}

Installation and 'hello world' Guide

• Download test
• Unpack the download
• Start __start_TemplateEngine
• Click "..."
• Choose the configuration file "OMG_Configuration.xml" in the TestDocs
  directory
• Click "generate"
• Examine the generated TestDocs\Test.docx file (delete and regenerate if
  required)
• Note well: While the template file can be open in Word during generation -
  the Excel model can't be open

Comments, suggestions or improvements are always welcomed!

 

Screen snapshot below:

LICENCE

This license governs use of the accompanying software. If you use the software, you accept this license. If you do not accept the license, do not use the software.

Copyright Microsoft Corporation

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0

THIS CODE IS PROVIDED *AS IS* BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OR CONDITIONS OF TITLE,
FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABLITY OR NON-INFRINGEMENT.

See the Apache 2 License for the specific language governing permissions and limitations under the License.

distribution_OMG_Beta_2_2011_12_13a.zip

​Digital Marketing Office Materials Generator

OMG is designed to streamline the ability for partners (and customers at a later date) to easily architect Microsoft solutions. It helps to solve a common problem in which different sections of a document (or set of documents) are inconsistent due to the difficulty of ensuring that (for example) the bill of materials matches the architecture diagram.  OMG is designed to model all complexity and mathematics in Excel (where it is easily managed), whilst document templates are created within Word.  A generation cycle blends the Excel model information with the Word template and generates a set of output documents.

OMG is used to output Word documents for architectural and pricing artifacts such as:

• Solution benefits overview
• Architecture documents
• Pricing documents

OMG uses a simple templating system within Word to output the generated documents. It is designed with extensiblity in mind and permits the easy definition of new template functions to be added to the processing cycle.  

 

Template commands in Word supports useful functions such as:

• If statements  (if Excel value THEN include Word text )
• Foreach statements (foreach cell in a group of cells from Excel)
• Include files  (include a file, including the ability to conditionally include a file)
• Easy references to Excel model information  (simply include cell names in curly braces - eg {customer} )

 

 

 

Overview

Templates are enclosed in curly braces and either refer to an Excel model or execute commands such as opening the model. For example this next line is blank in the output document, but it opens the named Excel document. It creates an internal variable "model" that's referred to later in the document. The italics are ignored for the purposes of executing the template, although the output is styled identically.

The default name that’s used for shorthand references to Excel named cells is “model”, so this is the variable name to generally use when opening an Excel document.

• {Excel.Open("model", "Test.xlsx")}

 

Referring to Excel cells:

Referring to Excel cells is via references enclosed in curly braces. These references optionally include an output style (format) after the reference. Creating these names within Excel is covered later in this document.

• Customer: {customer}
• Donation amount: {Donation_amount dollar}
• Date of donation: {Date_of_donation date}
• Quantity: {Quantity}
• Percent: {Percent_value percent}
• Will you donate? {Definitely_donate yesno}

There are three types of template commands above:

• Open the Excel model
• A simple reference to a named cell – e.g. “customer”
• A reference to a named cell with an output format – e.g. “Date_of_donation date”
• This is the same as a simple reference but with the type after the reference
• Valid formats are date, percent, dollar, yesno or truefalse

Creating named cells in Excel

In order to create named cells within Excel use the technique “Name a cell or a range of cells” in the following document: https://office.microsoft.com/en-us/excel-help/define-and-use-names-in-formulas-HA010342417.aspx#BMcreate_a_name_by_using_a_selection_of

 

The simplest technique to create a name is as follows (Office 2010):

• Select a cell
• Click in the box shown below and type the name – eg “Customer” into the box in the top left underneath the ribbon (highlighted below)

 

Including other documents

Include a file:

• {Word.Include(“IncludedFile.docx”)}

 

 

Conditionally include a file:

{include if ($model.GetNamedCell(”Definitely_donate”)) “IncludeIfTrue.docx”}

 

 

 

IF statements

To have a section of the document included or not depending on a variable use the following template text:

 

{if ($model.GetNamedCell(”Definitely_donate”))}

     This section of text will only be included if the named cell is true

{end}

 

 

FOREACH statements

A typical requirement is to produce copies of a document for a number of similarly named variables in the Excel document as follows. In the Excel document there are four named cells: Name1, Name2, Name3 and Name4. Note that because Name4 doesn’t contain anything it is not included in the foreach results.

{ foreach ($nameSuffix in $model.GetAllCellsLike(“Name”))}

• Name : {Name$nameSuffix}

{end}

Installation and 'hello world' Guide

• Download test
• Unpack the download
• Start __start_TemplateEngine
• Click "..."
• Choose the configuration file "OMG_Configuration.xml" in the TestDocs
  directory
• Click "generate"
• Examine the generated TestDocs\Test.docx file (delete and regenerate if
  required)
• Note well: While the template file can be open in Word during generation -
  the Excel model can't be open

Comments, suggestions or improvements are always welcomed!

 

Screen snapshot below:

 

LICENCE

This license governs use of the accompanying software. If you use the software, you accept this license. If
you do not accept the license, do not use the software.

1. Definitions
The terms "reproduce," "reproduction," and "distribution" have the same meaning here as under U.S.
copyright law.
"You" means the licensee of the software.
"Your company" means the company you worked for when you downloaded the software.
"Reference use" means use of the software within your company as a reference, in read only form, for the
sole purposes of debugging your products, maintaining your products, or enhancing the interoperability of
your products with the software, and specifically excludes the right to distribute the software outside of
your company.
"Licensed patents" means any Licensor patent claims which read directly on the software as distributed by
the Licensor under this license.

2. Grant of Rights
(A) Copyright Grant- Subject to the terms of this license, the Licensor grants you a non-transferable,
non-exclusive, worldwide, royalty-free copyright license to reproduce the software for reference use.
(B) Patent Grant- Subject to the terms of this license, the Licensor grants you a non-transferable,
non-exclusive, worldwide, royalty-free patent license under licensed patents for reference use.

3. Limitations
(A) No Trademark License- This license does not grant you any rights to use the Licensor’s name, logo, or
trademarks.
(B) If you begin patent litigation against the Licensor over patents that you think may apply to the
software (including a cross-claim or counterclaim in a lawsuit), your license to the software ends
automatically.
(C) The software is licensed "as-is." You bear the risk of using it. The Licensor gives no express
warranties, guarantees or conditions. You may have additional consumer rights under your local laws which
this license cannot change. To the extent permitted under your local laws, the Licensor excludes the
implied warranties of merchantability, fitness for a particular purpose and non-infringement.

Copyright 2011 Microsoft Australia Pty Ltd All rights reserved

OMG_2011_10_18_beta.zip

The framework provides for:

• Configuring and creating the Active Directory (AD) server
• Setting fixed IP
• Installing PowerShell ISE
• Converting (via dcpromo) a standard Server 2008 machine to be a domain controller
• Modifying UAC settings
• Registering licence keys for Windows Server 2008
• Installing and configuring SQL Server 2008 R2
• Setting UAC off
• Installing PowerShell ISE
• Registering licence keys
• Joining to the domain controller
• Creating appropriate local and domain users for managing SQL Server
• Assigning rights (such as "logon as a service") via ntrights.exe
• Updating the default SQL Server configuration to enable TCP on network interface
• Installing and configuring SharePoint 2010
• Creation of domain users for SharePoint
• Updating sections of the autospinstaller configuration file from the local SPinaBox configuration file

The framework requires a minimal number of configuration changes as follows in order to complete an installation of SharePoint, SQL Server and Active Directory

Please feel free to try out SPinaBox today - we're keen for comments and / or bugs!

• Status: With the out of the box settings and two blank VMs - it installs SharePoint 2010 in under an hour and a half, and with about 10 minutes of "enter" keypressing from the user. 
• It comes with a 33 page detailed installation manual (largely screenshots).  The user has to type about 10 short commands to fully install SharePoint 2010.
• Prerequisites: Access to MSDN or SharePoint / SQL Server / Server 2008 installation media.

Naturally - PowerShell to the rescue!

To view the basic post-install state, open up the SQL Server Configuration Manager (below)

Double-click TCP/IP and switch to the "IP Addresses" tab.  Ah ha!  The culprit - "enabled" is set to "No" on each interface (IP1, IP2, etc)

After some basic searching I found the following Technet article - however it enables TCP "in general", but not specifically for each interface.  After further searching - I didn't find a suitable script to fix the problem, so I was forced to research and build one (see below).

The following script sets "Enabled" and the "Port" for each IP address.  Note the odd structure of ipaddressproperties field underneath a given ipaddress.

Enjoy!

As always - comments / fixes are welcomed!

$smo = 'Microsoft.SqlServer.Management.Smo.'
$wmi = new-object ($smo + 'Wmi.ManagedComputer')

# From: https://technet.microsoft.com/en-us/library/dd206997.aspx

# List the object properties, including the instance names.
# $Wmi # Uncomment to view

# Enable the TCP protocol on the default instance.

# SQL Server name should be simple - eg "SP2010".  Instance name by default is SQLSERVER. 
$uri = "ManagedComputer[@Name='YOUR SQL SERVER NAME']/ServerInstance[@Name='INSTANCE NAME']/ServerProtocol[@Name='Tcp']"
$Tcp = $wmi.GetSmoObject($uri)
$Tcp.IsEnabled = $true
$TCP.alter()
#
# To view properties, use - $tcp.ipaddresses[1].ipaddressproperties or
#                           $tcp.ipaddresses[1].ipaddressproperties[0]
#
foreach ($tcpAddress in $Tcp.ipaddresses) {
 foreach ($property in $tcpAddress.ipaddressproperties) {
  if ($property.Name -eq "Enabled") {
   $property.Value=[bool]1
   $Tcp.Alter
  }
  if ($property.Name -eq "Port") {
   $property.Value=1433
   $Tcp.Alter
  }
 }
}
$Tcp

# Enable the named pipes protocol for the default instance.
$uri = "ManagedComputer[@Name='$sp2010_server_name']/ ServerInstance[@Name='$sql_instanceName']/ServerProtocol[@Name='Np']"
$Np = $wmi.GetSmoObject($uri)
$Np.IsEnabled = $true
$Np.Alter()
$Np

Restart-Service 'MSSQL$SQLSERVER' -Force