Keychain doesn't exist until second login (AD accounts).

[Aziz]

This is happening randomly with no pattern on our AD accounts after imaging.

Issues:

1. Keychain access shows that the login keychain isn't created for anyone until the second login.
2. The tech has to log in twice for everyone to receive a login keychain afterwards.

Basically, I log in the first time and have no login keychain. I log in a second time and then everything is fine.

Base image has no issues whatsoever. It's when I start installing Adobe CC 2014/2015 (no FEU/FUT) during imaging via a policy that this issues arises.

I've tested ten machines and four of them did not have a login keychain. I even created a Keychains folder in the user template using Composer and that didn't work.

What would be causing this issue?

Only our base image has FEU/FUT, the additional packages do not.

Other people having the same issue:

https://jamfnation.jamfsoftware.com/discussion.html?id=7662

https://jamfnation.jamfsoftware.com/discussion.html?id=7462

[davidacland]

If you disable FUT/FEU on the Adobe package does the symptom go away?

On our deployments of Adobe CC we use the Adobe CC Packaging tool and use pkgs so my guess would be the package you have is breaking something in the user template.

Last random thought, there used to be an MCX setting (I think related to mobility settings) that let you specify what template to use for new home folders. Just thought I'd mention it in case!

[Aziz]

Thanks for responding @davidacland

I currently do not use FET/FEU on any Adobe package, just our base image. I use the Adobe CCP tool to create the packages. I've tried installing the .pkg with a policy during imaging and I've also tried the installPKGfromDMG during image, both with no success.

As for MCX, we currently do not use MCX.

[davidacland]

Ah ok, sorry I misread.

So our usual setup is a base image from AutoDMG, a first boot script (to set time servers etc), a few config profiles and the apps (including Adobe CC). In that setup we don't get the issue.

The main difference you mention is the FUT & FEU on the base image. In the first instance I would try unchecking those options. Whats in your base image that needs FUT & FEU?

[mpermann]

@Abdiaziz is your base image just an OS or does it include other stuff? What I consider my base image is just an OS that was created by AutoDMG. There is nothing else in my base image other than than the OS so there is no need for me to use FET/FEU on that .dmg. I have lots of other .pkgs and .dmgs that get installed during the first run boot process.

[Aziz]

@davidacland @mpermann

Our usual setup is a base image using AutoDMG, applications that have to be on every machine, a first boot script and some config profiles.

Our base image is the OS and a few applications. Five of which have FUT enabled. Those five packages have never caused an issue before. We're started getting these issues when we started using Adobe CC.

We can image a machine with our base image and everything runs smooth, and it has a keychain.

I'm currently imaging two machine with no packages that require FEU or FUT and a policy to install Adobe 2015 afterwards.

[mpermann]

@Abdiaziz does the keychain issue happen when you simply put down the OS and just the Adobe CC 2015 with nothing else added?

[Aziz]

@mpermann @davidacland

I imaged two machines with FUT/FEU removed, the first machine had a keychain the second did not. I've narrowed down the issue to one of these three packages.

AdobeDreamweaver2015

AdobeFireworksCS6

AdobeFlashPro2015.

Now to test each one.

[Aziz · Accepted solution]

The issue magically disappeared.

[CSHGreenwich]

I am getting this on both imaged and non imaged machines. I thought it was Google chrome so I just did a drag and drop.. I tested with local users on an imaged machine and it was fine . But now with a fresh OS X band new machine, I am getting the error.. Staring from scratch again with fresh installs without Casper Packaging first.

[Aziz]

@CSHGreenwich

I spent many frustrating hours trying to find the cause of this issue with three test machines with no luck. It just disappeared a couple of days later.

[dferrara]

@Abdiaziz I've got the exact issue you're describing, and I can't figure it out. I was so excited to see a solution until you said it disappeared magically, ha. What JSS are you running?

[Aziz]

@dferrara

Issue started happening on 9.72, fixed on 9.72. Currently on 9.73

I actually found the main cause after marking this as solved, it was a .dmg that had "FEU" ticked, but not "FUT".

I spent time going through all the .dmgs to find that it was just a checkbox waiting to be selected....

[dferrara]

@Abdiaziz I think you just saved me a lot of time. Many thanks!