There is a very powerful and easy to use GUI Tool out there from Cireson – a company that develops in Microsoft Service Manager and Configuration Manager in Asset and Service Management Tools. You must TRY it as SCCM Admin or even an AD Admin in any company, and I thought that I must share with all because not a lot of people know about it …….. and IT IS FREE:
“Remote Manage app” : this free tool is considered a WMI and SCCM Client tool that can give a lot of information about any PC in your SCCM Client environment and help troubleshoot any problems about it, also it can do some actions or open some admin consoles on the machine …it is very useful and I use it a lot in my work
It is working based on PowerShell CMDlets, so be sure that WinRM Service are running on machines and PowerShell Execution Policy is set to allow these CMDlets to run
How To Use: Just type the name or IP of the client and the Site Server name or IP (check below first image) and click …….CONNECT 🙂
with this tool you can:
Make a Client Actions same like you initiate the action cycles in SCCM Control Panel Icon.
review the Collections the machine is member of and add it to any other collection.
Open C$ share directly from it
Open ConfigMgr Client Logs Folder directly from it
Repair ConfigMgr Client from it
Reset the SCCM Client Machine Policy (this resets all policies on the machine not only getting a new policy from the MP)
Uninstall ConfigMgr Client
check client info like OS, IP, System Model, CPU, RAM, Top Console user, UpTime,….
See real-time Logging of the PS Commands that the tool is running against the machine to get ll these info and actions
Review the Installed Software on the Client, and you can filter the results:
See the available Software to this client in Software Center and Install or Uninstall any one:
check and deploy the available or required Windows Updates published to the client by SCCM.
Review the Installed Updates on the machine and the MISSING updates (This is very useful to compare between missing updates here and the updates configured in SCCM ADRs and to know that your rules are getting the right updates to the right machines…. and that you are going to the right party 🙂 )
Review the Running Processes in the machine and the owner and path of each one, like you do in Task Manager, and you can KILL any process from the tool:
Review the Installed Printers and also cancel print jobs or Pause the Print Queue of any Printer:
Review all System Services and Start or Stop any of them (like in Services.msc console):
The last Tab is the most useful and exited tab ……that is …OTHER Tab, in it you will find tools to do the following:
Shutdown or Reboot the machine
Open Computer Management, User Management and Event Viewer Consoles directly from the tool
Know more info about the Agent like: Last Logon User, Last Reboot, Uptime and whether there is a reboot pending or not …..GREAT Right ?
Verify or Repair or Reset WMI on the targeted machine
Run PowerShell remotely on the machine
Run Remote Desktop or Remote Control and connects directly to the machine ……also GREAT Right ?
THE GREATEST: execute and simulate a Group Policy Results directly from the tool against target machine (very useful to troubleshoot GPOs applied to any machine and the wining GPO in every Single Setting) – this is like running RSOP.msc Console (but faster)
Thanks to Cireson for such a great FREE Tool that make SCCM Client Administration easier 🙂
at last ….. you can DOWNLOAD this tool from Cireson website:
If you have Event ID: 364 in Application Event Log related to Windows Server Update Services (WSUS) can’t download some updates, like this one:
Then you are lucky by reading this article, because there is a workaround for this nightmare:
This error happens because of some proxies or routers (that maybe not in your internal environment, it might be in the ISP or any place in the way to Microsoft Update Servers) doesn’t support the ancient 10 years old HTTP 1.1 Protocol used by BITS service. The workaround is to configure BITS with a command by connecting to WSUS Database with SQLCMD.exe tool as following steps (If you have SQL 2012 installed in the WSUS Server (As the command to connect to a named pipe changed in SQL 2012) :
In a command prompt, navigate to C:\Program Files\Microsoft SQL Server\90\Tools\Binn\ and run the following command: exe -S \\.\pipe\MICROSOFT##WID\tsql\query -E -b -Q “USE SUSDB update tbConfigurationC set BitsDownloadPriorityForeground=1”
If everything works ok, you will see the following result:
Hi all, today I’ll share with you ConfigMgr 2012 behind the scene setting that may affect your whole infrastructure and productivity. It’s Remote Control settings in SCCM Client Settings:
We all know that by default, the Administrators and Remote Desktop Users groups have the right to log on remotely through Remote Desktop Protocol. (for Domain Controllers it is Administrators only) ….but Configuration Manager 2012 has another opinion when you give it the controller stick 🙂
To permit users to remotely control machines, by using Remote Desktop or Remote Control tool, we do the following steps:
From SCCM Console go to Administration Tab and click Client Settings from the left side list:
2. Open the Default Client Settings or the custom client settings (If you created one for Remote Settings) and click Remote Tools from the left side list:
3. On Permitted viewers of Remote Control and Remote Assistance click on Set Viewers … :
4. It will open a list that you can add to it Domain Users or Groups as a Permitted Viewers (Recommend to add dedicated group for Users that needs Remote Access Permissions):
NOW, What happens when you add Accounts into this list (Permitted Viewers) ?
To answer this question, let’s see what ConfigMgr is doing when you enable Remote Control on Clients:
Configuration Manager creates a group called “ConfigMgr Remote Control Users” in local groups on every Machine, and it give this group the local security policy user wright: “Allow Log on Through Remote Desktop Services“. So when you add any accounts to the Permitted Viewers List, ConfigMgr Client will add them to this group. If you want for example to give Domain Admins the permission to use Remote Control to Share Users Desktop in a shared session, put the Domain Admins group in the Permitted Viewers List. Microsoft Doesn’t recommend adding users to this group (ConfigMgr Remote Control Users) directly, instead add them to the Permitted Viewers List.