First published on TECHNET on Apr 11, 2011
Welcome back to the weekly Lync Server PowerShell
One of These Things is Not Like the Others
challenge. We should probably point out to everyone that this is the 13
th
Challenge in the series. If this challenge proves to be unlucky, well, don't say we didn't warn you.
Note
. Just in case you're wondering what the heck we're talking about (you'd be surprised how often that happens), in many western cultures 13 is considered an unlucky number. For example, tall buildings often omit the 13
th
floor. (That doesn't mean there's a big empty space in the middle of the building, just that you have a 12
th
floor and a 14
th
floor, but no 13
th
floor.) Many airplanes do not have a 13
th
row, and in a number of European cities you'll have a house with an address like 12 Cucina Avenue and another with an address like 14 Cucina Avenue. The house in the middle? 12 ½ Cucina Avenue.
Like we said, this is a western world superstition; we've heard that in many parts of the eastern world,
4
is considered an unlucky number. Although, if you add the digits in 13 (1 + 3) you get – hmmm, interesting ….
At any rate, for those of you with a crazy, reckless, devil-may-care attitude, here's this week's challenge. Which of the following Lync Server PowerShell cmdlets is not like the others (and yes, this
is
a tricky one, at least in our opinion):
Stop-CsWindowsService
|
Get-CsAdUser
|
Set-CsUserAcp
|
New-CsServerApplication
|
Note
. So why
is
13 considered an unlucky number? There's definitely disagreement on that. Some people think it has to do with there being 13 people in attendance at the
Last Supper
; others suggest it has to do with the Norse god Loki crashing a party as the 13
th
guest. (And then, if that wasn't bad enough, killing the Norse god Baldr while at that same party.) Regardless, the authors of the Lync Server PowerShell blog don't believe that the number 13 is unlucky. After all, throughout his athletic career one of the authors always wore number 13, and look at how well
he
turned out.
You know, on second thought ….
Challenge 13 Hint
Challenge 13 Answer
Challenge Home
