Last week, when we posted the
first Lync Server PowerShell One of These Things is Not Like the Other Challenge
, we were afraid that the question we came up with was too hard, and that no one who entered would be able to come up with a correct answer. As it turned out, though, pretty much everyone who submitted an entry not only got it right, but also had a better explanation for why their answer was right than we had for why
answer was right. That can only mean one thing: you guys are way smarter and know way more about Lync Server PowerShell than we gave you credit for.
. What's that? Couldn't it also mean that we aren't anywhere near as smart and knowledgeable as we thought
were? Uh, no, of course not ….
Either way, we knew that, for this second challenge, we'd have to come up with something a little more challenging. With that in mind, we decided to shift gears a little and, instead of showing your four cmdlets and asking you to pick which cmdlet was not like the others, we're going to show you four parameters from the Set-CsConferencingPolicy cmdlet and ask you which
is not like the others. That's right: which parameter is not like the other parameters.
you this week's challenge was going to be more challenging.
. Isn't it terribly unfair to post such a difficult challenge? You bet it is. Now, it
be fair if there was some
somewhere that you could use to assist you in solving the challenge. But seeing as how there isn't any
like that, well, that
make this terribly unfair, doesn't it? The again, whoever said life is fair, right? Besides, maybe someday someone will write
that could assist you in tackling a challenge like this. Until then, that is, until the day some
exists, well, looks like you're on your own.
At any rate, here's Challenge No. 2: Which of these Lync Server Set-CsConferencingPolicy parameters is not like the others?
If you think you know the answer, send that answer, along with your name or alias, to
. Correct entries received before 9:00 AM Pacific Standard Time on Thursday, January 27, 2011 will be awarded 3 challenge points. (Note that you can send in multiple entries. But you can only get a maximum of 3 points per challenge.) On Thursday, January 27th
we'll post a
to this challenge. After the hint has been posted, correct entries received before 9:00 AM Pacific Standard Time on Monday, January 31, 2011 will be awarded 1 challenge point.
Sounds like a heck of a deal, doesn't it?
And remember, we don't believe that the answer we came up with is necessarily
answer to the challenge: there might very well be several different ways to solve this challenge. With that in mind, and to increase your chances of getting credit for your submission, it's a good idea to include a brief explanation as to why you think that your answer
the correct answer. For example, maybe you think that the answer to this week's challenge is "Red." Admittedly, that doesn't
right, at least not to us. But if you can make a convincing enough case for it, well ….
. OK, having said that we should also mention that there should be a Lync Server
reason for your answer. For example, it's true that, in this week's challenge, all the parameter names, except for AllowPolls, contain more than 10 characters. That's true, just like AllExternalUsersToRecordMeetings is the only parameter that has the letter
in its name. But that's not really what we're looking for.