Troubleshooting Issue: Can’t manage Skype Response Groups from CSCP GUI


, ,


The Response Groups tab does not show any configured Workflows, Queues or Groups. Also I am unable to configure any Response Groups.

Manage Response Groups

Response Group Workflow Page Blank


The Workflows do exist as my first check was to make sure they are visible and I can manage them from PowerShell. So permissions don’t appear to be an issue.

Attempting to add a group via the Control Panel I get the message “No workflows are assigned to current manager”.

Skype Response Groups No Workflows are assigned to current manager

Now that’s cryptic, why does the Control Panel think I am a Response Group Manager?

A quick check in Active Directory Group Membership for my account shows that I am a member of CSAdministrator BUT am also a member of CSResponseGroupManager.


Response Group Manager

I am certainly not supposed to be an RGS Manager.


 The CSResponseGroupManager group only allows access to manage groups that a user has been specifically assigned too. Removing my account from this group corrected the situation and I was able to manage all RGS as expected.
If a user was assigned as the group manager, then ONLY that particular group would be visible in the Control Panel.

Why you should be piloting MS Teams – Today!


Microsoft Teams

Microsoft Teams promises to be a big deal. Of course not everyone is keen to jump on every solution, application and idea thats come out of the Microsoft factory. To be honest, in this day and age most have a hard enough time keeping up, no time to waste playing with technology that may not be hugely successful in the near future, or where little benefit is percieved.

Thats said, I’d like to point out why you should be piloting teams today.

On the surface, Teams appears to be a feature rich replacement for Persistent Chat (I was never a fan of PC, too many limitations). With integration to Exchange Online, Sharepoint Online  and OneDrive for Business users can work within a single pain. Add to that audio and video conferencing and you have a powerhouse application, or a “hub for teamwork”.

I need to point out though, at the time of writing this post, Teams is not geared at the Enterprise Voice Space. Microsoft have however indicated that ultimately it will evolve to include the Skype for Business feature sets as well.

So what..another Persistent Chat app. to distract people from getting on with the job, you say. I am as sceptical as they come and initially resisted a bit too.

I certainly dont have alot of spare time to waste, what I need is an app that will save me time, not consume my time. Spending much of my time looking for documentation, chasing folks for progress updates, finding out who is doing what and the like.

This is WHY I believe Teams will be the next BIG thing.

From my perspective, the most exciting part of Teams is how it keeps all of my content and collaboration in one place. Tracking progress on a project within a channel made easy. Been away for a few days, no problem, all the happening are recorded within your Team discussion. Keep everyone in the loop – All the Time!

Turn your frequesntly used apps and files into tabs at the top of any channel and Boom! All your content relative to the channel at your fingertips.

More about Teams comming soon, but for now, come on – you know you hate wasting time, take the lead. Happy piloting.

Should you halt your Skype for Business deployment and wait for Teams?

Skype vs Teams

I know that the announcement at Ignite 2017 around the future of Skype for Business and Teams has the world on fire. I am also very aware that this subject has been well covered as far as the future state, even though we still await a official roadmap from Microsoft.

The perspective I’d like to focus on is all those organisations who are currently in one of the following situations:-

  • Skype for Business is on the roadmap in the next 12 months
  • About to embark on a Skye for Business deployment
  • Have a Pilot going and looking to do a full rollout
  • Deployment has already started but not completed just yet

So the answer to the question, “Should you hold off your Skype for Business deployment and wait for Teams?” is actually fairly straight forward. The answer can be achieved by asking a few simple questions. By no means is this a comprehensive list, simply a good starting point.

These questions are:-

  1. Do you need basic PBX features and calling (i.e. Enterprise Voice)?
  2. Will you need complex functionality such as Contact Center, CRM integration etc.?
  3. Is federation with other organisations (including Skype Consumer) requirement?

If you have answered YES to ANY of those 3 questions then Skype for Business (Online or On-premises) is the way to go.

The reality is that Teams is a great way for people to collaborate and keep on top of shared workloads, projects and the like. But when it comes to replacing your PSTN Voice, Teams is in its very early infancy.

When Teams has matured to a point where your PSTN workloads can be addressed in line with your business requirements, Microsoft has assured us that there will be a simple switch over (for Online users). Not much has been said about On-premises and switching to Teams at this time.

Ultimately, Teams is not ready to take over from Skype for Business. It does a very good job in the persistent chat space and also gives slack a run for their money. Beyond using Teams for those cases, Skype for Business is still king!

Microsoft has a proven track record of fast tracking these things, however, keep in mind that Skype for Business Online was supposed to have feature parity with On-premises by now. Before this milestone has been reached, the game plan has changed. Its a massive undertaking and will take time get right.

Take Teams for a spin, it will grow on you. But don’t dismiss Skype for Business just yet, especially if Skype for Business Online can’t deliver the functionality you need and you have gone down the On-premises track.

Other Great Microsoft Teams reads..

Feature Comparison – by LucaVitali

An honest opinion on Technical readiness – by Andrew Morpeth

The challenges Microsoft face – by Mark Vale