One of These Things is Not Like the Others: Challenge 4
A tip of the cap this week to ewright19: we barely had time to post the challenge before she had sent in her answer. Is it legal to submit an answer to the challenge just minutes after it's been posted? You bet it is. In fact, we encourage people to send their answers in before we post the challenge. If everyone would send their answers in now, we wouldn't have to bother trying to come up with a new question this week. That would make our lives much, much easier.
Which, we assume, is something very important to all of you.
So what question was ewright19 so quick to answer? This one: which of the following Microsoft Lync Server 2010 PowerShell cmdlets is not like the others?
|
Move-CsLegacyUser
|
|
Move-CsUser
|
|
Merge-CsLegacyTopology
|
|
Move-CsRgsConfiguration
|
The answer that most people gave is the same answer we had in mind: Move-CsUser. Why? Well, in the words of Aleksandar N.:
Other three cmdlets migrate things from an earlier version of Office Communications Server to Lync Server 2010. Move-CsUser is designed to move users from one Lync Server to another Lync Server pool, or to move a user from a Lync Server pool to an Office Communications Server pool.
So is he right? Are you kidding: Aleksandar is always right! The Move-CsLegacyUser cmdlet provides a way for you to move one or more Office Communications Server (or Office Communications Server 2007 R2) user accounts to Lync Server. (It's a pretty cool cmdlet, by the way. For example, it lets you decide whether you want to just move the user account itself, or whether you'd also like to migrate things like the user's dial plan, voice policy, conferencing policy, etc.) Merge-CsLegacyTopology migrates such things as the trusted service entries and topology information for domains, user services, Registrars, Mediation Servers, and Edge Servers from Office Communications Server to Lync Server. (That's important for actually switching from Office Communications Server to Lync Server. However, it's also useful if you want to run both Office Communications Server and Lync Server, the "coexistence" scenario.) And then there's Move-CsRgsConfiguration, everyone's favorite cmdlet for migrating your Office Communications Server Response Group settings to Lync Server.
So who's the odd man out (or, more correctly, the odd cmdlet out) in this challenge? It pretty much has to be Move-CsUser. As we've seen, the other three cmdlets can be used to move people from Office Communications Server to Lync Server. By contrast, Move-CsUser provides a way for you to move a user from Lync Server back to Office Communications Server. If you're in a coexistence scenario and, somehow or another, you migrated a user account that shouldn't have been migrated yet, well, Move-CsUser provides a way for you to return that user to Office Communications Server.
And, of course, the cmdlet can also be used to move users from one Lync Server pool to another.
With one exception, everyone who submitted an answer for Challenge 4 came up with Move-CsUser. The one exception was Johann D., who pointed out that Move-CsRgsConfiguration is the only one of the four cmdlets that does not support the WhatIf and Confirm parameters. To tell you the truth, we didn't even realize that, but he's right.
And yes, it is hard to believe something could have slipped past our eagle eyes, isn't it?
That's it for Challenge 4. By the time you read this, Challenge 5 will already be up and running.
And, no doubt, ewright19 will have already submitted her answer for it.
