I was curious if anyone has experience with the configuration manager for the mac. I reviewed the SCCM video on this site but it didn't really go over the apple enrollment. My question is this. Do you know how the "Client policy refresh interval" is calculated or brought in? Right now its listed as 86400 min? and I have no clue how it's getting this number. Any help would be appreciated.
Solved SCCM - Configuration Manager on MacOS
Please verify that this number is not reporting
MINUTES. I would think this would make more sense because of the following math = 86,400 seconds = 1440 minutes = 24 hrs. If it's minutes, then I'm not sure what randomness is being used here.
Microsoft has the following link here. This should help you to get started with the apple enrollment.
Hi Ronnie. Thanks for the link. I took a look and I am using the "Default Client Settings." Based on the article, this is the excerpt:
Client policy polling interval (minutes)
Specify how frequently the following Configuration Manager clients download client policy:
Windows computers (for example, desktops, servers, laptops)
Mobile devices that Configuration Manager enrolls
Computers that run Linux or UNIX
I currently have the "Client Policy Polling Interval (minutes)" set to 30 min. This still does not explain why the mac clients pull in the 86400. Any other thoughts?
I just heard from Adam Gordon about this. Here is his reply:
"The short answer in terms of changing the policy polling interval is below:
If you want to change the client policy polling interval, use the Client Policy Polling Interval setting in the Client Policy client setting group.
In terms of why it is set to 86400 minutes, I am not sure, there are several possibilities.
A few are listed here:
A custom client policy has been configured and applied at the collection level
The client installation was not done correctly, or is corrupt for some reason
All of the required / necessary scam client updates may not have been installed after the initial client install. As a result, the client may not be up to date, and it's configuration may not be set correctly as a result.
While I have no way of knowing which one of the reasons called out above are the cause, I would suggest that a quick check can easily eliminate number 1 as the cause ( and fix it if it is indeed the cause).
Number 2 can be fixed by removing the client and reinstalling and Configuring correctly ( this is an involved process, as it requires a series of connected steps to get right ). A good guide can be found here:
Number 3 involves checking the Microsoft site to ensure that all updates have been applied, and that the most recent version of the client has been installed.
Hope that helps..."
It was advised to not use a custom policy if you are deploying the agent to macs, so it is using the default client policy.
I tested another mac client by installing the agent and checking the results. It does register successfully and it is listed in the sccm console. It does list a client policy polling interval of 3600 min. A day passes and the polling interval changes to 86400 min.
I am using configuration manager 1702 which is the latest as of this writing and the windows client policies are working correctly. This just seems isolated to macs, which is a concern if I am trying to push out scripts.
Any other thoughts?
Not to be a pest, but just want to follow up so this doesn't fall into the etherwebs.
This post is deleted!
Here's his reply:
As we discussed yesterday, see additional information and suggestions below:
Current build version is SCCM 1706. I have looked over the feature updates in the build, and there does not appear to be any items that would explain the behavior discussed, but just a reference point, the following site will provide links to all of the builds and documentation for them: https://buildnumbers.wordpress.com/sccm/
SCCM build numbers
↓SCCM Current Branch build numbers ↓SCCM Technical Preview build numbers ↓SCCM 2012 R2 build numbers ↓SCCM 2012 SP1 & SP2 build numbers ↓SCCM 2012 build numbers ↓SCCM 2007 build numbers ↓SMS 20…
I would suggest that taking a look at the logs associated with client configuration and the server logs associated with client management might help to shed some light on what is happening as the client is initially configured, and then through the first 24 - 36 hours of life, is changing from 3600 minutes to 86400 minutes. There has to be one or more events being recorded that are indicating what is happening, and what is making the change, and this would be the place to start working backwards from. I would suggest that the following site will provide a good overview of the logs available: https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files
Log files for Configuration Manager | Microsoft Docs
Use log files to troubleshoot issues in a System Center Configuration Manager hierarchy.
There is a set of tools in the SCCM toolkit that may be valuable to use here as well. Specifically, the policy spy tool. The link for it is here: https://www.microsoft.com/en-us/download/details.aspx?id=50012
System Center 2012 R2 Configuration Manager Toolkit
This toolkit contains fifteen downloadable tools to help you manage and troubleshoot Microsoft System Center 2012 R2 Configuration Manager.
The other thing, even though the initial answer to my first comment about this was that there is nothing that is being used to configure the client as an additional policy, or "external" factor, I would also throw out the possibility of a Primary / Secondary site hierarchy. If the architecture here is not flat, as in a single primary site being used to manage the client in question, but rather there is a Primary / Secondary relationship in force, and the client is getting the settings from the Primary site, then the change may be attributable to the policy settings from the Primary site. I would not expect that this is the case, given the behavior and the explanations of observed settings, etc... up to now in the conversation, but I am just throwing it out there as a possibility as well.
If none of the other items above, (relay item #2) yield any further information or insights, then I would suggest that it may be time to go direct to the source and open a support ticket with Microsoft, as they will have access to tools and information for troubleshooting that will most likely provide the answer."
Since Adam joined the ITPRO.TV family maybe he can answer this question. I enrolled about 2 mac computers just to test. I found all the log files on the mac but on the SCCM server, I cannot find the SMS_DM.log (the log file that records communication between mobile devices, Mac computers, and the management point that is enabled for mobile devices and Mac computers).
How can I enable this log file or has the service been corrupted?
I hope all is well. My apologies for being delayed in responding to your question. We have had some weather events in Southern Florida over the last few weeks that have disrupted a lot of things, and catching up has taken a little longer than expected.
If you are not seeing the SMS_DM.log file there are a few possibilities as noted below:
You may have more than one Site Server in your architecture, and one of the other servers may have this role assigned to it instead of the one that you are looking for the log file on.
You may not have assigned the Management Point role correctly to the server, and as a result, it may not be functional, so no logs are being generated.
Check and make sure that the server in question is actually the Site Server that has the MP role assigned for mobile devices and Mac computers.
With no further activity on this post, I've marked this as solved.