KACE Product Support Question

K1000 will not allow upload of mobileconfig

08/24/2016 1228 views
Hello All

I'm at a complete halt right now...

I have created mobileconfig files which contain numerous payloads.

First one created was from OSX Server.
The second one created was from Apple Configurator on a macbook.

Both files I am trying to upload (either or, they both have the same settings), KACE always comes up with the error:

This does not appear to be a valid mobileconfig file. Check that the file format is correct and that the filename ends in .mobileconfig.

I've been trying to research to find out if KACE has any restrictions with these mobileconfig files, but nothing is shown.

Are there any settings that I can't place in these files? Or is there another way to create a compatible mobileconfig file for KACE to distribute?

I'm at a complete loss here... I did everything that was said on the K1000 articles.
2 Comments   [ + ] Show comments


  • Hi,

    What is the exact file name being used? does it end in .mobileconfig? What exact version of the K1? Is your K1 using a proxy server in the K1000 network settings? Do you have a support ticket open? if so can you provide me with the number.
  • The name is Profile1.mobileconfig - yes it ends in mobileconfig.
    K1000 is the latest version - 6.4.120822

    It's not using a proxy server in the network settings.

    I tried calling KACE support, but as usual, I am on hold for over an hour before I give up, which is why I came to here for some help.

    I have since found a workaround though.

    Instead of using the 'Mac Profiles' function in K1000, I have created a manual script, in which the dependency is the mobileconfig file, and a shell script to install it. This seems to work for now.

    Though I would like to know why the mobileconfig file that I have generated does not get accepted by the server as a mobileconfig file.

All Answers

Check to see if you are signing the configuration profiles in Profile Manager or Apple Configurator. This definitely causes the same error you're seeing and keeps a profile from working with KACE. After turning this off in our environment, I could upload profiles without error.
Answered 09/28/2016 by: bknorr
Purple Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ