self service blank screen redux

Now yet another weird oddity. Apparently editing a setting in the /etc/jamf.conf file makes it connect more frequently. However, when I try to run the policy in question it runs instantly runs and there are zero logs in the JSS that the policy actually ran...

This is just getting more and more weird. To add to this, some clients work just fine with zero issues. I think I may roll out a Casper upgrade soon.

OK, this is what I did to get it working on 1 client that had the blank screen. After each command I tried to refresh the Self Service screen by quitting and relaunching self service.

admins-imac:~ tlarkin$ ssh cadmin at 10.160.75.128 Password: WYA_KCK03364:~ cadmin$ sudo -s Password: bash-3.2# jamf recon Retrieving Inventory Preferences from https://xs001-casper.kckps.org:8443/... Locating Hard Drive Information... Locating Hardware Information (Mac OS X 10.5.8)... Locating Applications... Locating Receipts... Gathering Application Usage Information... Finding Extension Attributes... Submitting data to https://xs001-casper.kckps.org:8443/... <computer_id>3515</computer_id> bash-3.2# jamf manage The Management Framework will be enforced as soon as all Policies are done executing. bash-3.2# killall jamf bash-3.2# jamf manage Getting Management Framework from JSS... Enforcing Management Framework... Enforcing Login/Logout Hooks... Creating Startup Script... Enforcing Scheduled Tasks... Creating Usage Monitoring Task... Creating Restricted Software Task... bash-3.2# jamf recon Retrieving Inventory Preferences from https://xs001-casper.kckps.org:8443/... Locating Hard Drive Information... Locating Hardware Information (Mac OS X 10.5.8)... Locating Applications... Executing Unix Applications... Locating Receipts... Proxy Server Detected. Killing Software Update. Gathering Application Usage Information... Finding Extension Attributes... Submitting data to https://xs001-casper.kckps.org:8443/... <computer_id>3515</computer_id> bash-3.2# jamf manage Getting Management Framework from JSS... Enforcing Management Framework... Enforcing Login/Logout Hooks... Creating Startup Script... Enforcing Scheduled Tasks... Creating Usage Monitoring Task... Creating Restricted Software Task... bash-3.2# jamf checkJSSConnection Checking availability of https://xs001-casper.kckps.org:8443/... The JSS is available. bash-3.2#

Now after that last command it connected and it was no longer blank, however when I execute certain policies they do not actually install. Like I said, it is completely random. Sometimes a single recon will fix it. Sometimes rebooting the client, or logging in as a different user will fix it. Sometimes it takes 15 recons to fix it.

Any insight?

Thanks,

Tom