I took the bog standard VirtualBox package and added it to the JSS. When it deploys as part of a policy, there are no issues, but if it is included as part of a configuration it fails to install. The imaging log does not show an error; the application simply does not exist on the machine after imaging.
Has anyone seen something like this?
I don't manage VirtualBox for any users, but in general, if a package installs OK via policy but not during imaging, I try checking "This package must be installed to the boot volume at imaging time" for the package in Casper Admin. It may need a logged in user to fully install or somesuch.
I will try that and report back. Thanks a lot for the suggestion.
That worked. Thanks!
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.