10.7 Configuration Profiles Not being applied

SIXfoot5ins
New Contributor II

Hi guys,
I'm having problems apply Configuration Profiles to our 10.7.2 clients, they just wont apply.
I've met the requirements from the Admin guide but I'm confused why none of the preferences are seen, what is really interesting is when I select a scope and try to add a Individual Computer nothing is listed even though I have 10.7.2 client recorded in the JSS.

I've created a group and added a test 10.7.2 client to it to scope the Configuration to it with no joy!

Running JSS 8.43

Any help would be great
Thanks!

1 ACCEPTED SOLUTION

SIXfoot5ins
New Contributor II

Just in case this will help someone else....
After getting some help from JAMF Support we found out that we had to replace the Web Certificate

  1. Navigate to Settings > General Settings > Server Configuration
  2. Click on the link for "Replace with certificate from the JSS's built-in CA"
  3. Restart Tomcat with the steps on the following page:

https://jamfnation.jamfsoftware.com/article.html?id=117

...then test that we're able to communicate with Apples Push Notification system by using the command...

telnet gateway.push.apple.com 2195

...from the server running the JSS

We had to open the port on the Firewall

View solution in original post

8 REPLIES 8

clay7331
New Contributor

Good morning: I had the same issue as you on Friday. This article, https://jamfnation.jamfsoftware.com/discussion.html?id=59. helped tremendously. Specifically, the first paragraph of the response by jason.vanzanten. Talks about enabling certificates in your JSS.

I am having issues with the new verb added. I can't seem to get it to work. I'm pretty much relegated to a recon to push the profiles onto the client. Still hashing through though.

Hope this helps.
Clay

clay7331
New Contributor

Good morning: I had the same issue as you on Friday. This article, https://jamfnation.jamfsoftware.com/discussion.html?id=59. helped tremendously. Specifically, the first paragraph of the response by jason.vanzanten. Talks about enabling certificates in your JSS.

I am having issues with the new verb added. I can't seem to get it to work. I'm pretty much relegated to a recon to push the profiles onto the client. Still hashing through though.

Hope this helps.
Clay

clay7331
New Contributor

Good morning: I had the same issue as you on Friday. This article, https://jamfnation.jamfsoftware.com/discussion.html?id=59. helped tremendously. Specifically, the first paragraph of the response by jason.vanzanten. Talks about enabling certificates in your JSS.

I am having issues with the new verb added. I can't seem to get it to work. I'm pretty much relegated to a recon to push the profiles onto the client. Still hashing through though.

Hope this helps.
Clay

clay7331
New Contributor

Oops sorry for the double post guys.

rob_potvin
Contributor III
Contributor III

Maybe head to a 10.7.2 machine, open up terminal and run

sudo jamf manage -verbose

I had an issue with the certificate on a few, this proved it that there was a problem, then remove JAMF and reinstall with a new quickadd package.

SIXfoot5ins
New Contributor II

Thanks for your help @clay7331 @rpotvin.

I get an internal error when the profile installs so I've bounced it onto JAMF Support hopefully we can work together to resolve it

S.

SIXfoot5ins
New Contributor II

Just in case this will help someone else....
After getting some help from JAMF Support we found out that we had to replace the Web Certificate

  1. Navigate to Settings > General Settings > Server Configuration
  2. Click on the link for "Replace with certificate from the JSS's built-in CA"
  3. Restart Tomcat with the steps on the following page:

https://jamfnation.jamfsoftware.com/article.html?id=117

...then test that we're able to communicate with Apples Push Notification system by using the command...

telnet gateway.push.apple.com 2195

...from the server running the JSS

We had to open the port on the Firewall

kirk_magill
New Contributor

SIXFoot5ins - This solution you posted worked for me - the trick I think I forgot was to restart Tomcat. Thanks!