Nothing too special about this post, just a query statement. Use this query in an SCCM collection and it will give you all WORKGROUP machines.
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.ResourceDomainORWorkgroup = “WORKGROUP”
There ya go! Hope I’ve made your day, at least a little bit easier.
We all know SCCM can be your best friend, and your worst nightmare. Today I had to compile a list of client logs to check for a friend of mine, and thought I’d share. These should get you 95% of the way on your troubleshooting (from the client side anyways). Remember to always use CMTrace as your SCCM log viewer, it just makes your life easier.
All of these listed directly below, should be located in C:\Windows\CCM\logs on your client.
- Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
- Provides information about software update compliance scanning and about the download and installation of software updates on the client.
- Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
- Provides information about when the Windows Update Agent on the client searches for software updates.
- Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
You can also reference C:\Windows\WindowsUpdate.log which is a windows native log and not to SCCM, but is updated with actions taken by SCCM in regards to updates.
I hope this has made your day, at least a little bit easier!
So this is the issue — you’re going to subscribe to a report in SCOM and the only options are “Windows File Share” and “Null Delivery Provider”.
Well that’s a problem…we want these reports emailed. This error typically occurs when a SQL Migration is done, the reporting role is migrated, or on new installs. So go open up SQL Server Reporting Services Configuration Manager, and go to the “email settings” tab on the side. Notice there’s no data in there.
Configure this to include whatever you want your sender address to be, and your SMTP server, then click apply and you should get this.
Now, let go back and open up the SCOM Report Subscription again, and there we go!
I hope I’ve made your day, at least a little bit easier.
As I went to upgrade an evaluation version of System Center Configuration Manager 2012 to a full version, I noticed unlike Operations Manager — you have to do this through the setup/install interface. Upon first search people were saying just run the setup again and choose “Perform site maintenance or reset the site”, though it was greyed out. Here’s the quick tip to remedy that.
Here, I’m just running the setup again and choosing Install, and the option is greyed out to perform site maintenance.
So here’s what you do instead. Close the setup window, and go open Programs and Features in your Control Panel. Find “Microsoft System Center 2012 Configuration Manager Primary Site Setup” (this may be different if the top of your hierarchy is a CAS), and click “Uninstall/Change”.
Then, there it is — not greyed out!
Click next and you’re able to do what you need to do.
At this point you can do a few things.
- Reset your site with no configuration changes
- Modify SQL Server Configuration
- Modify SMS Provider Configuration
- Modify Language Configuration
- Upgrade Evaluation Edition to a Licensed Edition
I just needed to upgrade my site to a licensed edition, and this worked like a charm.
I hope I’ve made your day at least a little easier!
I did a few new SCOM 2012 installs recently and noticed that after pushing the agent to the DCs, they showed up grayed out in Ops Manager. Here’s a quick tip on how to fix that.
Logon to the DC(s), and with an administrative comand prompt run the HSLockdown tool, and add the local system account to the allowed group.
C:\Program Files\System Center Operations Manager\Agent:
*NOTE* In newer version, this is now stored in “C:\Program Files\Microsoft Monitoring Agent\Agent”
Run the command “HSLockdown /L” to show what accounts are being allowed or denied. In this case, my local system isn’t even populated.
Now run the HSLockdown tool again with the add switch to allow local system.
“HSLockdown /A “NT AUTHORITY\SYSTEM”
Restart the agent with “net stop heathservice && net start healthservice” and give it 5 minutes or so then it should be all green in your dashboard.
Hope this made your day at least a little easier!