Note in 2020 and beyond: In my opinion, you should be using Edge in your enterprise environment at this point. It offers all the same benefits (and engine) as chrome, but with o365 accounts, IE mode for sites that need it (think a single browser in your environment without the need to manage shortcuts to open specific sites in this or that browser), and enhanced security.
I have posted an application called Computer Info to the site, free for use in your environments. The application displays customized branding via the system's registry and provided logo PNG file, and is an easy way to display information to your end users to help them tell your support staff things they may need to know quickly. This application will also be featured in a blog post coming soon about managing Windows 10 Feature Updates, as well as general patches in a 24/7 environment.
Enjoy!
Sean
With Oracle's move to licensed Java installations for business use, many organizations are still left wondering "we need Java, what do we do?". A viable solution for many organizations will be to move onto the open source OpenJDK as a standard, and only keep/deploy licensed Java if and when necessary. Oracle's java are built from OpenJDK in the first place, so this is a highly compatible and viable option for any organization using Java today (See reference below).
This is a common question even experienced ConfigMgr admins run into once in a while (it's not often you're troubleshooting the client on a primary site server). The location of the logs is likely:
But could also be in the normal location:
%systemdrive%\Windows\CCM\Logs
I noticed some management points filling their OS drive space with IIS logs. I created the following script which you can run on a scheduled task every day to prevent that from happening. Adjust the retention period in the script as needed.
Hope it helps someone!
Been running this quite a bit in an environment that has had a lot of invalid content out there. I happened to notice today massive disk I/O was used while this tool ran, and Resource monitor showed MsMpEng.exe was the culprit. I added a process exclusion for the exe path I have been running ContentLibraryCleanup.exe out of locally on the DPs to the Antimalware policy I have deployed to my DPs, and the tool ran very noticeably faster than prior.
For most businesses, operational hours are 8AM-5PM, making managing Windows cumulative updates and feature updates (formerly known as build updates) a non-issue. For some sectors such as healthcare, however, this task is not so easy. Releasing an update everywhere could cause disaster. If not related to a bad update itself, catastrophe could be related to the delivery of the update itself, where several departments cannot afford to have all their systems down at once for an update or upgrade to install.
Just a note for SysAdmins out there writing scripts or automating all the things: never query the Win32_Product class to find software installed on devices. There's better ways, and querying this can/will cause problems!
Working with some Windows 10 2016 LTSB PCs running Lab robots last week, I noticed they didn’t have updates showing as applicable even though they were in collections with ADR based update groups deployed. We have an LTSB 2015 test machine in our area, so I checked his, same story. I double checked, and we do have the product Windows 10 LTSB enabled, and in that ADR, we are including updates for that product.
For those who haven't heard yet (or even for those who have), Microsoft has finally updated System Center Updates Publisher (SCUP). Here are some notes from my own upgrade from the old version to the new:
1. Leaving the old version installed and configured is a good thing! In fact, if you do this, the new version will prompt you to import settings from the old version (in terms of your WSUS and ConfigMgr setup, as well as your signing cert). Super cool!