Skip to main content

I have build a NoMAD config profile and have pushed it out. When it is FIRST INSTALLED, it works beautifully. If I either Quit NoMAD (and let it relaunch according to the LaunchAgent) or restart the computer, it breaks horribly. As you can see from my raw plist below It should show extra menus but after the NoMAD app is quit and it relaunches, it loses all the customization and it even stops displaying the password expiration in the menu bar!



<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.0">

<dict>

    <key>ADDomain</key>

    <string>ourdomain</string>

    <key>GetHelpOptions</key>

    <string>https://internalsite.company.org</string>

    <key>GetHelpType</key>

    <string>URL</string>

    <key>HideExpiration</key>

    <false/>

    <key>HidePrefs</key>

    <false/>

    <key>KerberosRealm</key>

    <string>COMPANY.ORG</string>

    <key>KeychainItems</key>

    <dict>

        <key>Exchange</key>

        <string>&lt;&lt;shortname&gt;&gt;@company.org</string>

    </dict>

    <key>LocalPasswordSync</key>

    <true/>

    <key>MenuAbout</key>

    <string>About NoMAD</string>

    <key>MenuGetHelp</key>

    <string>Get Help</string>

    <key>MenuGetSoftware</key>

    <string>Self Service</string>

    <key>MenuHomeDirectory</key>

    <string>Network home folder</string>

    <key>MenuRenewTickets</key>

    <string>Renew Kerberos Tickets</string>

    <key>MessageUPCAlert</key>

    <string>Your password was changed elsewhere.</string>

    <key>PasswordExpireCustomAlertTime</key>

    <integer>0</integer>

    <key>RenewTickets</key>

    <true/>

    <key>SecondsToRenew</key>

    <string>7200</string>

    <key>ShowHome</key>

    <true/>

    <key>UPCAlert</key>

    <true/>

    <key>UseKeychain</key>

    <true/>

</dict>

</plist>


I've tried building it with ProfileCreator and I've tried building it via defaults write commands from scratch and they both have the same result when I push them out to machines. What am I missing? It's just VERY weird that it DOES work.... until NoMAD is relaunched and then I can never get it to work again.

bump. Has anyone else experienced this? Is it maybe a faulty key that doesn't work? Is it a conflict between keys?

Here's what it works like right after the Config Profile is pushed out. Wonderful

Here's what it looks like if I either choose Quit from the menu, Log the user out, or restart the computer. And there is nothing that I can do to make it work again other than remove the config profile and re-add it.

Turns out it was 



<key>ADDomain</key>

    <string>ourdomain</string>


should be 



<key>ADDomain</key>

    <string>ourdomain.org</string>


It's still very odd behavior. Problem solved.

So can you confirm something for me, if our Domain is , SD.local, it should be SD.local.org?

So can you confirm something for me, if our Domain is , SD.local, it should be SD.local.org?



I don't have a way of testing that myself. It's my understanding that most Active Directory domains will have a FQDN like ourdomain.org and also have a NETBIOS name like OURDOMAIN. In your case, I'd play around with "SD" and "SD.LOCAL" to see which it likes. "SD.local.org" would only apply if that is the FQDN your AD administrators have setup for the domain.

Terms & ConditionsCookie settings