JimmyJ

I tried just about everything and nothing worked for me. I realized i changed some boundaries and fixed the environment I was working on, then it dawned on me, let me reinstall the SMP role. When I did, everything starting working again.

I've been recently tasked to check the overall health of the SCCM 1606 environment and AD environment. I've found some useful scripts from TechNet and am wondering what other people have used in the past to help them assess the current setup and infrastructure? I know I can check component status and logs, but those don't always paint the complete picture, nor do they give you a pretty email or chart to show your clients where they may have issues. The two scripts I've found are these ones: https://gallery.technet.microsoft.com/ConfigMgr-Client-Health-ccd00bd7 https://gallery.technet.microsoft.com/ConfigMgr-Daily-Health-014b0d3e/view/Discussions#content Can anyone else recommend some tips for checking overall health status and doing a general audit? The other steps I've gone through are: Items 1) Get Site name and CAS name. Get access. 2) Get SQL Server name and WSUS and get access to DB and servers where hosted. 3) Discovery of all SCCM servers and roles from CAS. (script) 4) Hardware Inventory (for each server) and OS version (2 scripts) 5) Active Directory and GPO check (Manual) (Make sure SCHEMA is extended. Nothing is hardcoded and service accounts exist. Verify domain service account for SQL. Check Group Membership) 6) Verify Distribution points health (script) 7) Boundaries, Discovery Methods, DPs and DP Groups. Active Directory Forests. 😎 Client Settings 9) Software Updates/WSUS health 10)Security Posture (SSL, IBCM, PKI) 11)System Health Reports (monitoring -> system components) 12)Access Control best practices (least control principle, not complicates) 13)Remote Access (ask first option, usage, security) 14)Packages and Applications: Naming standards, versioning information 15)Software Update Center website and application availability (SCCM Client) 16)Software Updates and retention, software updates required, maintenance plans, saved searches 17)Drivers packages, boot images, task seqs and health/standards 18)Collections: Collections with 0 members. Clients with old clients. Clients that aren't reporting back. Collections that are direct and not queries. How often they are updated 19)Monitoring: Queries naming standards, alerts, system status, content status, deployments (recent), SSRS health. 20)Helper tools 21)Logs: dive deeper 22)Endpoint protection, MBAM, intune other. 23)Database server health: backups, scheduled tasks, user access 24)Event logs on all servers

I wasn't sure if there was more intelligence than that ... So what you're saying is, if a machine receives the bootfile across the WAN (via IP helpers to a DHCP server), but the image is in the LAN, it will grab the image file from inside that LAN because of the IP Helpers setup?

I know "which" image it gets (from the TS), but I am wondering from what location? Ie. Machine A, Site 1 and Site 2 (both sites are PXE capable and have the bootfile, WinPE and WIM image). Machine A Pxe boots at Site 1. What intelligence tells the machine to load the image (WIM) from Site 1, and not Site 2 (that's over the WAN, for instance).

I understand the boot process does a bunch of handshakes with the DHCP/PXE server, but after it loads into the WinPE environment, how does it know to grab the image file? Is there intelligence in the pxe boot file that tells it to grab it locally? http://blogs.technet.com/b/dominikheinz/archive/2011/03/18/sccm-pxe-network-boot-process.aspx

I'm looking to get a report/query for all machines that have a specific KB installed. I've found a few that give me reports for updates, will those cover the rollups as well? This is what I have so far - will QNumber give me a report on rollups as well? Specifically looking to report on "kb2992020" select summ.ID,summ.QNumbers as 'Q Number', COUNT(distinct ps.ResourceID) as 'Requested', COUNT(distinct case when ps.LastState=107 or ps.laststate=102 or ps.laststate=105 then ps.ResourceID else NULL End) as 'Installed', ROUND(100.0*COUNT(distinct case when ps.LastState=107 or ps.laststate=102 or ps.laststate=105 then ps.ResourceID else NULL End) /count(distinct ps.ResourceID),2) as 'Success %' from v_GS_PatchStatusEx ps join v_ApplicableUpdatesSummaryEx summ on ps.UpdateID=summ.UpdateID where (summ.QNumbers like '%2992020%') group by summ.ID,summ.QNumbers order by summ.ID

We're currently deploying WIN7 via SCCM 2007 R3 and have a program to run before the task sequence starts the state capture. The program is an "hta" that displays a countdown timer and a custom message to close outlook and get on a wired connection. After the timeout period of 5 minutes, or if a user clicks "ok", the program stops and the task continues. I'm curious if there's any way I can script and force the wireless to turn off?

Did you ever find a solution for this? I'm having the same problem.