I plugged the two units in to the power points, they immediately connected to provide me with the ethernet link I needed to connect the ADSL modem to a better positioned Access Point. I plugged the AP I had in to one of the ethernet ports (there are two) and it all worked perfectly.

The I tried to connect to the built in AP. I could see the SSID, just as the manual described. The problem was that when I tried to connect to it it would not accept the password as described in the manual. On one of the devices that I have I received an invalid password message.

The solution – I downloaded the configuration utility, you can find it here:

http://www.netcomm.com.au/sm/drivers/np206

When I ran this, the password displayed for the AP was nothing like that described in the manual.

I reset the password (And the SSID while I was at it) and now have all my WiFi devices connecting to it.

The units seem to be working very well, and, with the exception (and quite a big one at that!) of the wrong password being described in the manual, it worked very easily.

function Get-CommandByParameter ([string]$Parameter)
{
    Get-Command | Where-Object {try {$_.Parameters.Keys -contains $Parameter} catch {}}
}

I found this useful reference:

http://blog.falchionconsulting.com/index.php/2007/11/delete-list-forget-about-forcedeletelist/

Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008

http://msdn.microsoft.com/en-us/library/ee554869.aspx

Site Templates and their IDs

With the SharePoint PowerShell management console (all one one line):

Get-SPWebTemplate |
select Title,Name,Description | ConvertTo-HTML | Out-File
c:\data\SPTemplates.html

http://technet.microsoft.com/en-us/library/ff607979.aspx

http://www.toddbaginski.com/blog/archive/2009/11/20/which-sharepoint-2010-site-template-is-right-for-me.aspx

List reference IDs

http://techtrainingnotes.blogspot.com/2008/01/sharepoint-registrationid-list-template.html

MSDN References

Schema description

http://msdn.microsoft.com/en-us/library/ms462947.aspx

SPListTemplateType Enumeration

http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.splisttemplatetype.aspx

SPMetal

http://msdn.microsoft.com/en-us/library/ee538255(office.14).aspx

http://fabiangwilliams.wordpress.com/2010/01/03/how-to-using-spmetal-utility-in-sharepoint-2010-to-presumably-manipulate-data-on-a-bcs-external-list/

Sandbox Solutions

Namespaces and Types in Sandboxed Solutions

http://msdn.microsoft.com/en-us/library/ee537860(office.14).aspx

Client Side Object Model

http://msdn.microsoft.com/en-us/library/ee857094(office.14).aspx

http://channel9.msdn.com/Learn/Courses/SharePoint2010Developer/ClientObjectModel

Workflow with Visio 2010

http://office.microsoft.com/en-us/visio-help/create-import-and-export-sharepoint-workflows-in-visio-HA101888007.aspx

http://blogs.msdn.com/b/visio/archive/2010/01/19/sharepoint-workflow-authoring-in-visio-premium-2010-part-2.aspx

function Test-CommonParameterVariables
{
[CmdletBinding()]
Param
(
[string]$switches
)
“Commandline switches: $switches`n”
“Preference Variables:”
“———————”
dir variable:\*Preference | Sort-Object -Property Name
if ($VerbosePreference -ne ‘SilentlyContinue’)
{
Write-Warning “In the VerbosePreference block”
}
if ($DebugPreference -ne ‘SilentlyContinue’)
{
Write-Warning “In the DebugPreference block”
}
}

Clear-Host
Test-CommonParameterVariables ‘No switches’
Write-Host “—————————————-”
Test-CommonParameterVariables ‘-Verbose’ -Verbose

Write-Host “—————————————-”
Test-CommonParameterVariables ‘-Debug’ -Debug

Write-Host “—————————————-”
Test-CommonParameterVariables ‘-Verbose -Debug’ -Verbose -Debug

Write-Host “—————————————-”
Test-CommonParameterVariables ‘-ErrorAction Continue’ -ErrorAction Continue

Write-Host “—————————————-”
Test-CommonParameterVariables ‘-ErrorAction Inquire’ -ErrorAction Inquire
Write-Host “—————————————-”
Test-CommonParameterVariables ‘-ErrorAction Stop’ -ErrorAction Stop
Write-Host “—————————————-”

The following code is what I have been using to check the functionality:

###############################################
# Script to explore common parameters
# Brent Challis
# Dimension Data Learning Solutions
# Melbourne, Victoria, Australia
###############################################
function Test-CommonParametersWithCmdletBinding
{
[CmdletBinding()]
Param
(
[string]$FunctionMessage = “Initial Value”
)
Write-Output “Starting Function with CmdletBinding.”
Write-Host “Writing to the host.”
Write-Output $FunctionMessage
Write-Verbose “Verbose message.”
Write-Debug “Debug message.”
Write-Warning “Warning message.”
Write-Output “Function Complete.”
}

function Test-CommonParametersWithoutCmdletBinding
{
Param
(
[string]$FunctionMessage = “Initial Value”
)
Write-Output “Starting Function without CmdletBinding.”
Write-Host “Writing to the host.”
Write-Output $FunctionMessage
Write-Verbose “Verbose message.”
Write-Debug “Debug message.”
Write-Warning “Warning message.”
Write-Output “Function Complete.”
}

Clear-Host
Write-Host “Starting.”
Write-Host “==========================================================”
Write-Host “Getting help info”
Get-Help Test-CommonParametersWithCmdletBinding
Write-Host “———————————————————-”
Get-Help Test-CommonParametersWithoutCmdletBinding
Write-Host “==========================================================”
Write-Host “Run with CmdletBinding.”
Test-CommonParametersWithCmdletBinding “Test Message” -Verbose -Debug
Write-Host “==========================================================”
Write-Host “Run without CmdletBinding.”
Test-CommonParametersWithoutCmdletBinding “Test Message” -Verbose -Debug
Write-Host “==========================================================”
Write-Output “Test complete.”

http://nearbaseline.com.au/blog/2010/02/powershell-warmup-script-2/

############################################################################
#WarmUp2.ps1 – Enumerates all web sites in web applications in a 2010
# SharePoint farm and opens each in a browser.
#Notes:
#-”get-webpage” function borrowed from:
# http://kirkhofer.wordpress.com/2008/10/18/sharepoint-warm-up-script/
#
#Assumptions:
#-Running on machine with WSS/MOSS 2010 installed
############################################################################

Add-PsSnapin Microsoft.SharePoint.PowerShell
$extrasitelistfile = ‘c:\Tools\Warmup\warmup-extrasites.txt’

function get-webpage([string]$url,[System.Net.NetworkCredential]$cred=$null)
{
$wc = new-object net.webclient
if($cred -eq $null)
{
$cred = [System.Net.CredentialCache]::DefaultCredentials;
}
$wc.credentials = $cred;
return $wc.DownloadString($url);
}

#This passes in the default credentials needed. If you need specific
#stuff you can use something else to elevate basically the permissions.
#Or run this task as a user that has a Policy above all the Web
#Applications with the correct permissions

$cred = [System.Net.CredentialCache]::DefaultCredentials;
#$cred = new-object System.Net.NetworkCredential(“username”,”password”,”machinename”)

$apps = get-spwebapplication -includecentraladministration
foreach ($app in $apps) {
$sites = get-spsite -webapplication $app.url
foreach ($site in $sites) {
write-host $site.Url;
$html=get-webpage -url $site.Url -cred $cred;
}
}
# Warm up other sites specified in warmup-extrasites.txt file (such as SSRS)

if (test-path $extrasitelistfile) {
$extrasites = get-content $extrasitelistfile
foreach ($site in $extrasites) {
write-host $site;
$html=get-webpage -url $site -cred $cred;
}
}

I did this by adding a reference to the IWshRuntimeLibrary by selecting Add reference and from the COM tab, selecting the Windows Script Host Object Model.

Then in my code simply put:

IWshRuntimeLibrary.WshShellClass wshShell = new IWshRuntimeLibrary.WshShellClass();

wshShell.Popup(“The Master version has shut down, so this instance needs to close as well.”, 10, “Master Instance of GhostCaster has closed”);

<#
.SYNOPSIS
  Inset tags to support the Get-Help Cmdlet
.DESCRIPTION
  Insert-FunctionHelpText inserts text at the current cursor position to provide
  a skeleton of tags which can then be edited to provide support for the function
  and the Get-Help Cmdlet.
.NOTES
  This is a useful function to be called from a menu added to the PowerShell-ISE
  Add-ons menu structure. 
.EXAMPLE
  Insert-FunctionHelpText
#>
function Insert-FunctionHelpText()
{
$psISE.CurrentFile.Editor.InsertText("<#
.SYNOPSIS
  Brief description of function.  Start with a verb.
.DESCRIPTION
  Full description of the function.  Start with <function name>
.PARAMETER parameterName
  Description of parameter
.INPUTS
  List .NET classes the function will accept as input.
.OUTPUTS
  List .NET classes the function will output.
.NOTES
  List information that does not easily fit into other parts of the structure.
.LINK
  about_function
.EXAMPLE
  function-name -parameter
#>
")
}

Set-StrictMode -Version "2.0"
<#
.SYNOPSIS
    This filter reads objects from the pipeline and only passes those obects which include the aclName
    on the ACL.
.DESCRIPTION
    The filter processes the objects passed through the pipeline and examines the ACL to see if the
    name passed in as the aclName is either the owner of the object, or is listed as one of the
    IdentityReferences in the ACL Entries.  The comparison for the name is performed using the
    -like operator which allows for widcard inclusion. 
.PARAMETER aclName
    The value passed in this parameter is compared to the name of the owner in the ACL and the
    IdentityReference values of the ACL entries
.EXAMPLE
    dir c:\webdem | Select-ItemsByAclEntry -aclName "*guest*"
.EXAMPLE
    dir HKCU:\Software\Microsoft\VisualStudio -recurse | Select-ItemsByAclEntry -aclName *guest
    The dir part of this statement, in particular, needs to be executed with credentials that
    have sufficent access to the Registry Keys.
#>
filter Select-ItemByAclEntry ([string]$aclName)
{
    try
    {
        $acl = $_.GetAccessControl()
        $foundUser = ($acl.Owner -like $aclName)
        if (-not $foundUser)
        {
            if ( $acl.Access.Count -gt 0)
            {
                foreach ($a in $acl.Access)
                {
                    if ($a.IdentityReference -like $aclName)
                    {
                        $foundUser = $true
                    }
                }
            }
        }
    }catch
    {
        Write-Host "There was an exception: $_"
    }
    if ($foundUser)
    {
        Write-Output($_)
    }
}