It’s the moment we’ve all been waiting for!
In response to this little feedback feature from one Steven Owen – now an employee at Microsoft:
Microsoft has added the long awaited community hub and now it’s more than just the documentation! In fact you’ll soon be able to submit your own features to it!
There are some requirements that need to be met before the Community Hub component can be leveraged. Some of them are kinda weird so bear with me:
- You MUST connect from a WINDOWS 10 Machine – I know Server 2016/19 is kind of like windows 10 but in this case it’s NOT the same. If you you try to use the Primary Site Server you WILL receive an error.
- You MUST have .NET 4.6 OR Higher installed.
NOTE: After this blog was posted Mark Silvey Replied and explained WHY these requirements currently exist:
If you don’t meet the above requirements you will get the following error
- The logged in users CANNOT be the built-in administrator account – I feel there is a story behind this one.
I didn’t’ test this one so I can’t show you what the behavior on it is short of it might crash. I’m honestly unsure.
- Unable to access Community hub node when running console as a different user – If you’re signed in as a user with lower rights and choose Run as a different user to open the Configuration Manager console, you may not be able to access the Community hub node.
This one I can show you the behavior for because I don’t typically log into my machine as my ConfigMgr admin account. This is a common result if you use the “run as” command.
Having seen something similar to this before with trying to use configuration manager from a non-domain joined machine. So I tried this and it seemed to work but as far as I know it’s not supported.
PS C:\Users\jbenz001> runas /netonly /user:DOMAIN\USERNAME "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\Microsoft.ConfigurationManagement.exe"
- The administration service in Configuration Manager needs to be set up and functional.
The last one is the big one. You need to make sure you have the Administration Service enabled. This includes ensuring the checkbox for the hierarchy is checked see the below image.
If you have an environment that does NOT have a PKI infrastructure. You may face some additional challenges. The below message is one example.
If you experience this and are you using EHTTPS, you need to import the SMS Issuing certificate into your Trusted Root store. You can do this by opening the configuration manager console, navigating to: Administration -> Security -> Certificates. Select the currently ACTIVE certificate for SMS Issuing, right click and view its properties. Then select to install the certificate in the trusted root store for the computer.
Enough Requirements Show Me the goods!
So once you’ve finally got all your requirements done. Here’s what it looks like!
You’ll want to get logged into GitHub by clicking the login item in the top panel. When you do this you WILL be prompted for MFA if you have it configured – I hope you do…and for permission to generate an OAUTH token.
The current Icons are a little confusing as to what is what so here’s a quick clarifying screenshot.
Remember if you pull in a script, you will still need to APPROVE it before it can be used in your environment. For example lets say we wanted the Query Windows Power Plan Per Device script. Click the item which will then provide you with the “Download” option.
Make sure you have the appropriate permissions to create a script in the environment otherwise you’ll get yelled at.
This will then generate the script in your console.
Finally if you ever try to download an item and it can’t create the object you can always click “View Source” and it will take you to the GitHub page and you can see source contents to copy for yourself!
Hopefully this helps you out with getting started!