Errata

(If you’re looking for the errata for Tony’s book, try this link instead.)

Like most software, technical books are complex beasts that are produced by teams of people through a multi-step process. And, like most software, sometimes errors make it into the finished product. Once I finish a chapter and it goes off for editing, the technical and copy-editing teams may modify it, and once they’re finished the desktop publishers who lay out the actual book pages may modify it further. Having said that, I’m ultimately responsible for every mistake in the book, so let me start by apologizing that this page is even necessary– a distressing number of errors in the finished book were put there by me so I can’t fob off responsibility for it.

I’m working with Microsoft Press to fix the problems that I know of so that the updated text feeds into their publishing process for future editions. (I don’t yet know whether they will be using the automatic-update feature of the Kindle and Nook to push text updates to people who buy the electronic version– if you see such an update please let me know). In the meantime, the below list contains all the problems of which I’m aware. I’ll keep updating it as I receive problem reports or find problems on my own.

Thanks for buying the book, and sorry for the mistakes.

– Paul

Chapter 1 – Client access servers

Page 26: the discussion of the unencrypted GET request made to the Autodiscover endpoint should be using an HTTP URL, not HTTPS.

Page 26, bullet 3: the initial request goes to “…autodiscover.xml”, not “autodiscover.svc”.

Chapter 2 – The Exchange transport system

Page 53: the last sentence in the second paragraph (“…or to the Mailbox Transport Submission service if the current server…”) is incorrect. If the current server has the active database copy, the message goes to the Transport service.

Chapter 3 – Client management

Nothing reported yet.

Chapter 4 – Mobile device management

The script on page 260 is truncated in the Kindle version (apparently at, or around, location 5656). here’s the correct version:

$Date = Get-Date -uformat "%Y%m%d"
$Logfile = "C:\Logs\ActiveSync-all-$date.txt"

$Lst = Get-CASMailbox -ResultSize Unlimited -Filter {HasActiveSyncDevicePartnership -eq $True} | where {$_.ExchangeVersion.ExchangeBuild.Major -ge 15}

ForEach ($CASMbx in $lst) {
       $Devices=(Get-MobileDeviceStatistics -Mailbox $CASMbx.name)
       if ($Devices) {
                foreach ($Device in $Devices) {
                        $ReturnObject=($Device | select DeviceModel,DeviceType,LastSuccessSync,DevicePhonenumber,DeviceUserAgent)
                        Add-Content -path $Logfile ((ConvertTo-CSV -NoTypeInformation -InputObject $ReturnObject) | select -skip 1)
                }
       }
}

Chapter 5 – Message hygiene and security

Nothing reported yet.

Chapter 6 – Unified messaging

Nothing reported yet.

Chapter 7 – Integrating Exchange 2013 with Lync Server

Nothing reported yet.

Chapter 8 – Office 365: a whirlwind tour

Nothing reported yet.

 

Advertisements

3 responses to “Errata

  1. Hello Paul,
    First of all, let me thank you for the great book – it’s very helpful to me!

    Would you please clarify this to me:
    (chapter 2, page 82/64)

    “New-ReceiveConnector -Name “Receive From Tailspin Toys” -Usage Custom -Bindings ‘0.0.0.0:9925’ -RemoteIPRanges ‘192.168.70.71’ -Server PAO-EX02

    After the connector has been created, you can see its properties with the Get-ReceiveConnector cmdlet:
    Get-ReceiveConnector -id “PAO-EX01\Default Frontend PAO-EX01″ | flRunspaceId : 3d9854bc-c9bc-494d-a641-39f1d5186336
    AuthMechanism : Tls, Integrated, BasicAuth,
    BasicAuthRequireTLS, ExchangeServer
    Banner :
    BinaryMimeEnabled : True
    Bindings : {[::]:25, 0.0.0.0:25}
    …”

    – doesn’t the parameter “-Bindings ‘0.0.0.0:9925′” mean the bindings must be 9925, not 25 (“Bindings : {[::]:25, 0.0.0.0:25}”)?

    Regards,
    Michael Firsov

    • robichaux

      Michael, you are absolutely right. My apologies for the error. I’ll let MS Press know so they can correct it in future releases.

  2. Hello Paul,

    One more question please:

    Page 209/229

    “Customizing Ooutlook Web App

    Themes define the color scheme and graphic elements used for Outlook Web App. Exchange 2007 introduced support for customizable Outlook Web App themes; Exchange 2013 continues this support by including a set of 22 themes that users can apply to customize their Outlook Web App session’s appearance. …

    The simplest way to do this is to copy one of the existing themes (located in \Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\Current\themes) and then edit the files you find there, being careful to preserve exact dimensions.”

    I was suprised to see there’re only three subfolders in \Program Files\Microsoft\Exchange Server\V15\ClientAccess\owa\Current\themes on my test Exchange and I asked a question regarding supporting 22 themes in Exchange 2013 on technet forum to wich they answered as follows:

    “I have verified on several labs, we have the same themes folders as yours in the snapshot.

    I did some research including in our internal database, there is no official document or our internal document states the “a set of 22 themes” in Exchange 2013. Maybe our product team has been working on this and it’s coming soon in the next version or service pack. ”

    https://social.technet.microsoft.com/Forums/office/en-US/05e68e19-74e0-45ae-a393-250db8dc923c/exchange-2013sp1-owa-themes?forum=exchangesvrgeneral

    ???

    Regards,
    Michael Firsov

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s