SCCM Console Right click Multiple computers to open Client Center for SCCM errors out

[kintaroju]

Hi @rzander ,

One issue I discovered is when you right click on more than 1 computer to open Client Center from the SCCM console, the below error occurs.

If you need any help testing anything let me know

Cheers!

[SCCMAdmin]

Hi @kintaroju ...honestly I've never even used this not even for one PC let alone multiple. When you try multiple, how many copmuters are you talking about? What scenario makes you want to do this? Curious to understand. Cheers. :-)

[kintaroju]

hi @SCCMAdmin ,

Depends on the situation, like an example is when we needed to check what the status of multi systems for patching, especially like during the wannacry situation, we have to sift through reports and then figure out why the system isn't at a particular patch level, which would involve connecting to multiple machines to find a common theme.

Another situation would be like you needed to do a quick a dirty remote uninstall of an application to like 5 machines, but don't want to create a deployment just to remove the application.

Another example would be you try to multi task tickets and have to remote to two machines.

It's those little things that help :D.

Cheers!

[rzander]

To trigger any activity on multiple Clients just use : https://cmcollctr.codeplex.com/ or wait until the "Script function" from the current TechnicalPreview will be released...

[kintaroju]

Hi @rzander ,

another awesome hidden tool you have, i'll my colleagues know about it :D.

BTW the only two questions i have, after reading the document:

For the client center it being grayed out I read the docs on codeplex and updated CMCollCtr.exe.config, and added the exe path for it into there, except it still doesn't work, is there something I am missing?

Also for the PSremoting option being grayed out how do I fix that? Also if i fix it, will it give me a interactive PS session like in client center for SCCM?

Also when you plan to port that awesome tool into github?

Cheers!

Side note: I've tried using both version, the stable and new beta both didn't help my cause.

[rzander]

Try this one, there is a bug in the published Version: plugin.collctr.sccmclictr.zip

[kintaroju]

Hi Roger,

That fixed the issue for it being grayed out, but when i select two or more machines it only opens client center for the last highlighted machine, any thoughts?

Also the powershell remoting still is grayed out, anything I can do to fix that?

Cheers!

[rzander]

You should not open Client Center for every machine in the list... just run it once and copy the powershell Code... validate and paste the Powershell in CollectionCommander... or just place PowerShell-Files in the Folder PSScripts (same Path as the .exe), so you can pick the File for the next time...

[SCCMAdmin]

Thanks @kintaroju for explanation above. We obviously work differently.

On this point, we only troubleshoot and manage workstations with sccmclictr. Haven't configured servers to accept these connections (still can use old 2007 related sccmclictr when desperate for some things). Do you troubleshoot workstations only or workstations and servers?

Interesting discussion above. I didn't know of collection commander and will check it out at some point. Have lived without it fine so far. :-)

[rzander]

I use ClientCenter and CollectionCommander for Servers and Workstations... Servers normaly do have the WinRM enabled by Default...

[kintaroju]

Hi @rzander ,

For collectioncommander, do you plan to bring it to github, as i can start to slowly seem the awesome potential.

As for collectioncommander, can you use it from a command line perspective, instead of gui? So eg, I want to trigger a client install with collection commander based on collection ID.

Cheers!

[rzander]

Collection commander will die with codeplex ;-)... with ConfigMgr 1706 there is an option to store and run PowerShell scripts against collections... so I don't think I will invest some time in CollectCommander.

there is no need for a command line option as you have PowerShell... Invoke-Command -ComputerName Server01, Server02 -FilePath c:\Scripts\DiskCollect.ps1

[kintaroju]

yea that part is the easy part to invoke the command, but to automate it with 2012 r2 is another story :(. that is why i was hoping there would be a "collectioncommand -collectionid -invokeps-script", then viola, but clearly that burst my bubble lol

[SCCMAdmin]

FYI @kintaroju I can confirm I have the same error you posted at the start of this issue. I successfully connected to one client (it was very fast I was a little surprised), but when I highlight two I got the same error. Sharing only. I don't think I will use this, but following along for keeping up with what the community is up to. ;-]