I have used the SCCM Tools workspace in many troubleshooting scenarios. Tools workspace in a hidden workspace within the SCCM console.
In this post, you will see how to make the Tools workspace visible for SCCM admins and SCCM Console Tips.
You can try to understand the process of building SCCM Console Extensions. More details Build SCCM Console Extension Right Click Tools For SCCM.
Another useful post explains about New Method To Install SCCM Console Extensions.
SCCM Tools Hidden Workspace
Have you seen the SCCM console with TOOLS Workspace? If not, here is the chance to create tools Workspace in the SCCM Console. You can add TOOLS workspace without writing a line of code and without using any 3rd party console extension.
SCCM Hidden Workspace – \Tools\Overview\Namespaces\
I used the SCCM tools workspace for many troubleshooting scenarios and discovered the WMI classes and paths of SCCM objects from the console. Tools hidden workspace is one of the SCCM console tips.
How to Make Tools Hidden Workspace Available in SCCM Console
You can enable Tools workspace from the SCCM console shortcut file. The following steps will help make the hidden workspace SCCM Tools visible in the console.
- Start menu – Right-click on the Configuration Manager Console shortcut and select Properties
- Add “SMS: debug view” value as shown in the below picture
- Click on the continue button on Access Denied Window
- Re-launch the SCCM console
- Click on Tools Workspace from the SCCM console and start using it
- Go to Software Library – Applications
- Right-Click one application and Select Show Object Details
- The application object details will be available in Tools Hidden Workspace
How Useful is SCCM Tools Hidden Workspace?
You can get many useful troubleshooting tips after enabling Tools hidden Workplace. You can get the following details once you allow a hidden workspace called Tools in SCCM Console.
Tools hidden workspace is one of the SCCM console tips, and more to follow in the below section of this post.
- WMI NameSpace
- WMI Class
- WMI Path
- Application Scope ID/CI Unique ID
Following are some of the examples of Tools Workspace troubleshooting examples.
- Application – \Tools\Overview\Namespaces\SMS_ ApplicationLatest.ModelName=”ScopeId_77756C2C-A568-4030-B8E4-5864C7E51302/Application_06ca558a-ec56-4a7a-9907-b29a37f52d37″
- Package – \Tools\Overview\Namespaces\SMS_Package. PackageID=”PR300003″
- Boundary – \Tools\Overview\Namespaces\SMS_Boundary. BoundaryID=16777217
- Site – \Tools\Overview\Namespaces\SMS_Site.SiteCode=”PR3″
- Monitor – \Tools\Overview\Namespaces\SMS_ ComponentSummarizer.ComponentName=”CONFIGURATION_MANAGER_UPDATE”,MachineName=”SCCM_PROD.INTUNE.COM”,SiteCode=”PR3″,TallyInterval=”0001128000100008″
- Collection Device – \Tools\Overview\Namespaces\SMS_Combined DeviceResources.ResourceID=2097152009
Additional SCCM Console Tips
The following SCCM console options will help you with other SCCM console tips /options which will help your day-to-day operational task as SCCM Admin.
NOTE! – Instead the following SCCM console tips/options are useful for SCCM admin turn developers 🙂
SCCM Console Options | Description |
/sms:debugview=1 | A DebugView is included in all ResultViews that specify a view. DebugView shows raw properties (names and values). |
/sms:NamespaceView=1 | Shows namespace view in the SCCM console. |
/sms:ResetSettings | The SCCM console ignores user persisted connection and view states (SCCM Console window size is not reset). |
/sms:IgnoreExtensions | Disables any SCCM extensions. |
/sms:NoRestore | The SCCM console ignores previous persisted node navigation. |
4