Trying FEU for the first time, not working

[tak10]

I'm trying FEU for the first time but it doesn't seem to be working.
Here is what I'm trying to accomplish. We just recently deployed network projectors throughout the building, I'm trying to send out profile with IP address/DNS names of projectors to Epson EasyMP Network Projection applications so when the user opens up the applications, the profile is already built with list of projectors in the building.

The challenging part of this is that the projector list preferences are built within the user-level preferences folder. I ran through the usually with the composer to capture the data and I have several preferences files built into the /Users/Admin/Library/Preferences/ folder. I uploaded the DMG to the Casper Admin and checked the FEU check box. Then, created a self service policy to install the projector application with FEU check box checked from the policy as well. I ran this against the test machine from my AD account. However, the preferences files are only coming to the /Users/Admin/Library/Preferences/, not to my user /Library/Preferences folder. Where should I look to troubleshoot this issue? We are running 9.72 JSS and 10.10.4 OS X.

[amfarrell]

Are your AD accounts mobile? Casper looks at the dscl records, so if the accounts aren't mobile, FEU will not work.

[davidacland · Accepted solution]

I've still been using FEU with a few versions of 10.10.x and they've worked ok. If it's deploying to /Users/AdminLibrary/Preferences/ it sounds like it's behaving like a pkg installer.

You have to tick the FEU option on the package itself and the policy (just in case it's that).

[tak10]

Thank you for the guidance, I will try repackaging it again from beginning to end and make sure they are on Mobile account.

@davidacland When you say tick the FEU option on the package itself, you are referring to the box within the CasperAdmin, correct? Because I don't see any FEU option within the Composer app.

[davidacland]

Yep, in Casper Admin.

[tak10]

I re-capture the package from an AD profile instead of the local admin account. It seems to be working now. Thank you.