Yep. I ran into that. Albeit on a Windows Server. I checked the config
file to make sure the correct information was getting saved. It was. So
I restarted the server and everything started up normally and I was able
to create an account, log in, etc.
Ok. I figured this out if you're interested. At least it works in my
environment. I created a script in the JSS, then added a script payload
to the policy that installs Jabber. Parameter 4 is set to the
provisioning URL. Here's the script: The_URL="$...