Thanks. Found the problem, the clients weren't getting policy because they had an improper MP certificate. The permissions on the systems management container were set improperly, so once we reset them and waited clients started getting the policies we expected. The question is how the bad MP cert got in there in the first place, but hey. Ryan
From: [email protected] [mailto:[email protected]] On Behalf Of Russ Rimmerman Sent: Wednesday, March 12, 2014 8:21 PM To: [email protected] Subject: [mssms] RE: troubleshooting an issue Try pushing another less impacting command-line to them like ipconfig.exe and watch execmgr.log to see if it executes. If not, use policyspy or other similar utility to look in one of the client's policies to see if it's receiving the policy (or any policy). From: [email protected] [mailto:[email protected]] On Behalf Of Ryan Shugart Sent: Wednesday, March 12, 2014 10:30 AM To: [email protected] Subject: [mssms] RE: troubleshooting an issue Hi Russ: No, no maintenance windows set at all on anything in the environment. Ryan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Russ Rimmerman Sent: Tuesday, March 11, 2014 8:38 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: troubleshooting an issue Any maintenance windows set on the collections? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Shugart Sent: Tuesday, March 11, 2014 10:02 AM To: [email protected]<mailto:[email protected]> Subject: [mssms] troubleshooting an issue Hi all: OK, this is my first troubleshooting issue with SCCM 2012R2, so please be gentle. I just want to make sure my ducks are in a row before I open a PSS case. The environment is SCCM 2012R2, single site, single network, about 20 clients in the environment.. I have an old style package/program that reboots the machine its advertised to, it just runs shutdown.exe /f /r. There's no source files, nothing like that. This last weekend, I sent this out to ten collections of machines to do a staggered reboot over a few hours. Two collections worked fine, the other eight did not. From what I can tell looking at logs, they didn't even try to run the package, I'm not 100% sure they even knew about it. I did try creating a new package/program, and sent that out to one of the collections and I'm not seeing it trying to run that program either. So, it almost sounds like there's some kind of communications issue between client and SCCM server, but things look fine in that regard. There's no cert infrastructure in this environment, so things should be talking over HTTP, etc. And the clients seem healthy. So, anything else I should check before calling MS? Thanks. Ryan Ryan Shugart LAN Administrator MiTek USA, MiTek Denver 314-851-7414 MiTek Holdings, Inc., 2011-2014, All Rights Reserved ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. MiTek Holdings, Inc., 2011-2014, All Rights Reserved ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it. MiTek Holdings, Inc., 2011-2014, All Rights Reserved ________________________________ This communication (including any attachments) contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying, or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it.
