Now here's something you don't see every day: we made a big mistake in
last week's challenge
. (Well, OK, maybe that
something you see every day after all.) Last week we asked you which of the following four Lync Server PowerShell cmdlets was not like the others:
Everyone who submitted an answer for last week's challenge came up with the same answer: New-CsNetworkInterface. And why did they come up with that answer? That's easy: the other three cmdlets actually exist. New-CsNetworkInterface
So were we just giving you an easy one, or maybe trying to trick you by throwing in a cmdlet that doesn't actually exist? Would you believe us if we said yes, that's
what we were doing? We didn't think so.
Instead, we screwed up. We were supposed to ask you which of the following Lync Server PowerShell
was not like the others:
That would have been at least at
more challenging. In that case, the correct answer would have been CsNetworkInterface. Why? Because, even though all four cmdlets have the word
in their name, CsNetworkInterface is the only cmdlet that doesn't deal with CAC: the Call Admission Control service. Instead, that cmdlet is used simply to return information about the network interfaces used on a computer.
However, for some weird reason we stuck
in front of each noun name and instead issued a challenge that was way too easy, especially for all of you guys. Hey, you owe us one!
On the bright side, we have
one last challenge
for you this week. Did we do this week's challenge correctly? We're not going to say yes, but we're not going to say no, either. After all, stranger things have happened.
And no, we can't think of anything rarer than us actually doing something right for a change. But surely there must be
stranger than that.