Throw a NodeFone SIP phone call onto the mix and with perfect voice quality I can see the following utilisation graph on the FritxBox:

You can see the downloads peaked with 800Kb/s of file downloads, an unknown quantity for voice traffic and the remainder for streaming content. Upload is more obvious with Real-time (voice), Prioritized (Video) & Normal (Downloads).

Given I can only prioritise outbound traffic, it just goes to further demonstrate InterNode’s awesomeness for prioritising inbound content. InterNode + FritzBox FTW!

While at the event I had the opportunity to grill engage with many different departments; techs were available from research, design, implementation, testing and maintenance. All within line-of-site and all happy to discuss the technology to great detail. It is difficult to find technical information published on the Telstra Velocity/ NBN network equipment being deployed around Australia. We know that it uses fibre to provide up to 100Mbit/s internet, phone and cable TV but what you don’t know is the HOW.

From my discussions I learned that the fibre based Ethernet+ PSTN+ Cable services being deployed utilise a type passive hub or one-to-many fibre splice connecting a single service from the Exchange to 24 nodes. All 24 end nodes will receive the same light transmissions from the exchange relying on the end hardware to select traffic destined for the appropriate serial number to process. At present a standard light wavelength will be used for each of the Ethernet/ PSTN & Cable service; each signal from the fibre using encoding unique to the appropriate port signal. Every premise will send & receive on the SAME light wavelength meaning that there must be some time-splicing or multiplexing built into signal transmission.

To my fortune, a Telstra Account Executive had invited me along to the day and was able to arrange for a personal tour of the live Exchange. Seeing the technology advance from a wall off rotating counter wheels soldered directly to telephone wires using string for cable management; to the racks of POTS switching equipment right through to the “new” ADSL DSLAM units connected by only a few strands of fibre was simply amazing. So much of the exchange is now empty where Moore’s law has reduce the space used by active equipment by 1/5 while still servicing the heavily populated inner-city suburbs.

There isn’t time to cover the relics and equipment in the Museum side of the Exchange, the only word that can sum up all the experiences from the day. #BestOpenDayEver

The official download page from Microsoft is located here with documentation on the service here.

Thanks Geoff, even if the adds are a little obtrusive.

PowerShell (From server with Exchange Extensions):

$LiveCred = Get-Credential

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic -AllowRedirection

Import-PSSession $Session

Send-As mailbox access:

Add-RecipientPermission -Identity <sharedEmail> -Trustee <userEmail> -AccessRights SendAs

Y

 Add Full Mailbox Access:

Add-MailboxPermission <sharedEmail> -User <userEmail> -AccessRights FullAccess

Remove Mailbox Access

Remove-MailboxPermission -Identity <SharedMailbox>  -AccessRights <MailboxRights>  -User <UserEmail>

Removing Distribution Groups

Use the Remove-DistributionGroup cmdlet together with the BypassSecurityGroupManagerCheck parameter to remove the distribution group as follows:

Remove-DistributionGroup <name of the group> -BypassSecurityGroupManagerCheck

Forwarding Email With Copy

Set-Mailbox user -DeliverToMailboxAndForward:$True -ForwardingAddress $forward       (NOTE must be user within Exchange Org, otherwise use ForwardingSMTPAddress)

Removing Forward

Set-Mailbox $user -DeliverToMailboxAndForward:$False -ForwardingAddress $null

Create a Shared Mailbox (http://technet.microsoft.com/en-us/exchangelabshelp/ee441202)

set-mailbox <shared> -type shared

New-Mailbox -Name “<Shared>” -Alias <Shared> -Shared

Set-Mailbox <Shared> -ProhibitSendReceiveQuota 5GB -ProhibitSendQuota 4.75GB -IssueWarningQuota 4.5GB

Moral of the story: Notify users, Confirm ‘Default Policy’ settings, Then tick the box.

A built in tool ‘sc’ is now the command to use for all your services related configurations.

SRVANY.exe can still be used to run applications, simply specify:

sc create MRTG binPath= C:\Windows\System32\srvany.exe DisplayName= "MRTG"

Add the appropriate information into HKLM\SYSTEM\CCS\Services\MRTG\Parameters\ and your favourite multi-router traffic grapher will start with windows. =)

Thanks to several posts on the SBS Diva Blog I was able to identify the issue and fix it in a slightly different way.

All web sites hosted (http://server/Remote, /Connect, etc.) were reporting the following HTTP 500.0 server error -
“Calling LoadLibraryEx on ISAPI filter “C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll”

Is obviously caused by x64 code being executed by x32 .NET – Enabling x32 compatibility in the Application Pool did not help. To resolve:

Under the <Server> Home – ISAPI Filters, ASP.NET_4.0.30319.0 was set to use x32 Framework. Updated the filter DLL path to Framework64 and all applications are working normally.

I Found a really usefull post which shows how to fix Just this issue!

Option #1:Repair Damaged Certificate (Windows Server 2003/2008)

1. Open MMC and add the Certificate Snap-In for the Local Computer account.
2. Double-Click on the recently imported certificate
3. Select the Details tab.
4. Click on the Serial Number field and copy that string
5. Open up a command prompt session. (cmd.exe aka DOS Prompt)
6. Type: certutil -repairstore my “SerialNumber” (SerialNumber is that which was copied down in step 4.)
7. After running the above command, go back to the MMC and Right-Click Certificates and select Refresh (or hit F5 in the MMC)
8. Double-Click on the problem certificate. At the bottom of this window (General tab) it should state: “You have a private key that corresponds to this certificate.“

30 seconds later – Legend!

Just keep in mind, SBS likes to have any certificates with a subordinate authority also have their certificates listed in the MMC -> Certificates -> Server -> Trusted Subordinate Authorities.