Hey guys
I've just had something weird happen on our system. I have a new policy
that installs a package at startup (we have a few of these) and I've set it
to install on our test group (1 machine). The machine starts but the policy
log says that the machine still hasn't run the policy. I checked the client
logs and it says the policy has run and even has the submission of the log
(no errors in the log):
Jul 28 10:31:29 csdd043115 com.jamfsoftware.startupItem53]: Executing
Policy Microsoft Silverlight (Intel Only)...
Jul 28 10:31:29 csdd043115 com.jamfsoftwar...
Jul 28 10:31:31 csdd043115 com.jamfsoftware.startupItem[53]: Installing
Silverlight.pkg...
Jul 28 10:31:36 csdd043115 com.apple.DirectoryServices[11]: Enter machine
password:
Jul 28 10:31:47: --- last message repeated 1 time ---
*Jul 28 10:31:47 csdd043115 com.jamfsoftware.startupItem[53]: Successfully
installed Silverlight.pkg.*
*Jul 28 10:31:47 csdd043115 com.jamfsoftware.startupItem[53]: Submitting log
to https://xxxx:8443//...*
The policy before it also runs successfully but it shows fine in the server
logs. I thought it was an error with the package but the package did
install and is working fine. I thought it might be a problem with the jamf
binary screwing up so I ran it manually (jamf policy -trigger startup) and
that worked fine (successful install and log entry on the server).
I re-created the policy and restarted the machine. That works; package
installs and entry in the log. I flush the policy and restart the machine.
Back to square one. Package installs but the server thinks it hasn't. So
only when I flush the policy does it seem to go into this state. I wouldn't
have noticed except that I made a change to the package and just flushed the
policy to test again.
Anyone seen this (or something like it) before?
I'm running Casper 8.1 on a 10.6.3 server. The client is 10.6.6 (iMac). The
policy is set to trigger at startup once per computer. The package is
nothing special; flat pack of the Silverlight package.
Regards
Sven Schott
