'Sign in to download from the App Store' dialog box

Is there any iLife or iWork apps installed?

Is iBooks installed? (& outdated).

Are you behind a proxy that requires authentication?

No iLife/Work. iBooks yes- as it ships in the retail distribution v1.0.1. And yes, we are behind authenticated proxy- which I can clear ok.

I know v8.73 provided official support for 10.9, I'm running 8.71...

Could that have anything to do with this? I don't see how it could, but I'm grasping now...

I am having the same problem. I am behind a proxy and firewall as well. My guess is that it is store_helper and storeagent getting triggered by the OS trying to look for updates. I am going to try moving the files out of the /System/Library/LaunchAgents folder and see what happens.

@jconte][/url , I came to the same conclusion when building our image and renamed store_helper
in /System/Library/PrivateFrameworks/CommerceKit.framework/Resources/store_helper.app/Contents/MacOS to store_helper.bak. This seemed to do the trick, but my machine just installed Apple Software Updates during a logout policy and it appears to have recreated store_helper. I'm thinking of making a logon script to check for this file and delete it if found, but let me know if anyone else comes up with another solution.

Well it does seem that this dialog box stops appearing once I authenticate to the proxy.

And removing store_helper prevents this from appearing again if I have not authenticated to the proxy. I then applied a Thunderbolt Firmware Update via Software Update and that helper did not return.

So for those of us behind a proxy, that don't want this annoyance popping up, I'm wondering what might the ramifications of removing store_helper during imaging?

-dpertschi
Did you have any luck or even try removing store_helper during imaging? I am in the proxy boat and would the end user not to see this as they will trigger a HD call.

Thanks.

unfortunately, we didn't go that route. We opened up the ports and allow unauthenticated access out to the specific locations, but to reduce the risk we have made the MAS restricted software and users need an approved security exception to unrestricted it.

@jrserapio no luck removing the store_helper. I tried once on a test machine and it seemed to work, but was not repeatable.

This must have annoyed me more than the users because I'm not getting negative feedback about it. I told our level 2 desktop folks to simply advise logging into the proxy to made it go away.

@jrserapio

I was able to successfully remove store_helper during imaging and obtain the desired results. I have an ongoing logout script that runs on all of our machines which includes the following code

#!/bin/sh

# Set path to store_helper file
storehelper="/System/Library/PrivateFrameworks/CommerceKit.framework/Resources/store_helper.app/Contents/MacOS/store_helper"

# If the store_helper file exists
if [ -e "$storehelper" ]; then
    # Output info to log
    echo "Deleting the store_helper file..."
    # Delete the store_helper file
    rm "$storehelper"
fi

I removed the store_helper file from our base image before creating the DMG, then added the logout script to the imaging configuration. So far this doesn't seem to have caused any problems for us.

I hope this helps!

Thanks for the responses guys.

@dpertschi - This is actually annoying my Imaging guys more than the end users. Some of the end users are still new to Macs, so they may think that just the way its supposed to behave :)

@dwandro92 - Thank for this. I will test this out.

Thanks... works a treat :D