Set advanced IMAP settings with profile manager?

I've finally gotten profile manager working successfully so that my employees can enroll their iOS devices and laptops for easy setup of our company services. However, there are two advanced IMAP settings we need to manage that are not available in the Profile Manager controls.
Is there a way to crack open a profile source and add in the keys for advanced IMAP settings? Specifically, i need to set "Remove Deleted Messages" to "Never" and assign an alternate mailbox for "Deleted Mailbox" under "Mailbox Behaviors"
Thanks for any help or advice!

While I was not at the time trying to do it via Profile Manager I did previously look at trying to enable Location Services via a script. Unfortunately I found it too hard or more accurately I failed to do this. I ended up 'cheating' by logging in on a test Mac, manually setting up Locations Services the way I wanted including most importantly setting the Security & Privacy settings to allow a specific application to use Location Services. I then saved a copy of the relevant configuration file which is -
/private/var/db/locationd/clients.plist
I then as part of my DeployStudio workflow to image fresh computers included a step to copy this to the correct location on the fresh computer, thereby 'restoring' the settings.
So the short answer is that /private/var/db/locationd/clients.plist is the file but the structure is such that a simple defaults write is not possible.
Let me know if you get anywhere with this.

Similar Messages

Setting apn with Profile Manager

apn profiles in Profile Manager seemes malformed.
This is a snippet of how it looks when downloaded from Profile Manager:
<dict>
          <key>DefaultsData</key>
          <dict>
                    <key>apns</key>
                    <array>
                              <dict>
                                        <key>apn</key>
                                        <string>mytestapn</string>
                                        <key>proxy</key>
                                        <string></string>
                                        <key>proxyPort</key>
                                        <string></string>
                              </dict>
                    </array>
          </dict>
</dict>
<dict>
          <key>DefaultsDomainName</key>
          <string>com.apple.managedCarrier</string>
</dict>
when I create a .mobileconfig file with IPCU, the xml looks like this:
<dict>
          <key>DefaultsData</key>
          <dict>
                    <key>apns</key>
                    <array>
                              <dict>
                                        <key>apn</key>
                                        <string>mytestapn</string>
                                        <key>proxy</key>
                                        <string></string>
                                        <key>proxyPort</key>
                                        <integer></integer>
                              </dict>
                    </array>
          </dict>
          <key>DefaultsDomainName</key>
          <string>com.apple.managedCarrier</string>
</dict>
that is, in profile Manager, DefaultsDomainName key is contained within its own dict tag, and in IPCU it is located together with the DefaultsData key.
when I try to deploy the profile to a device using profile manager, the job failed with MCPayloadErrorDomain
Has anyone had any luck on setting apn settings with Profile Manager?

Just updated OSX - problem solved

Configuration Profile Custom Settings in Profile Manager

Hi All,
I'm a newbie when it comes to OS X configuration profiles. Does anyone have any resources on customizing or editing configuration profiles?
I've been playing around with Profile Manager for a few days and see the "Custom Settings" tab. I'm curious what kind of things I can customize here. Being a newbie I don't know where to start.... If anyone has any documentation or link to online resource or book recommendation on editing mobileconfig files or creating custom settings with payloads in Profile Manager I'd really appreciate it!! There are a lot of tweeks that I'd like to set on our computers and I'd like to see if I can do these tweeks with configuration profiles.
Thanks in advance for your help!
~Joe

Thanks for posting Brian You're 100% right. It's been noted and the revised article should be published shortly.

Messages Settings in Profile Manager 2.1 Mountain Lion

Just want to let anyone and everyone know about something that I've found in Profile Manager.
I have been messing about with Messages, trying to get it set up without any success but I have found something that could be useful to anyone else in the same situation.
When applying messages settings to a Profile it seems to spoil all other settings, or at least Dock settings.
I set up my Dock and other settings for a group and all was fine. I then added the messages settings to the group and all of the Dock settings were removed leaving just Finder and the Trash Can in the dock.
Removing the Messages setting restored the previous Dock settings and everything is back to normal. Perhaps I am doing something wrong but this seems to be a bit of a bug with Profile Manager.
On a side note, I'd really appreciate some help with setting Messages up. I work in a school where it would be great if the teachers could use Messages as instant messaging between classrooms.

Did you ever get this resolved? This error is usually related to DNS, hostname, or Open Directory configuration. Let me know if you still need help.

Push profile with profile manager to two users on one mac

I have been testing profile manager today. Very interesting setup.
Unfortunately I ran into one problem:
I have a profile for a group setup as a push profile.
Two users of the group use the same mac.
So I logged in as the first user, browsed to .../mydevices and installed the trust profile. Then I clicked enroll to enroll the Mac.
Then I did the same with the second user on the same Mac.
So far so good.
When I log in again as the first user, the Mac isn't enrolled anymore. Strange but I went on.
I made a change to the profile with Profile Manager on the server. I saved the settings and checked Active Tasks to see wether it pushed the settings.
Displayed: Push Settings 1 of 2 in progress; 1 succeeded. first user sending, second user succeeded.
Then I enrolled the mac with the first user again. Then the task completes completely. But when I make a change to the profile again and push the new profile, the same problem occurs: the user last enrolled the mac gets the updated profile. The other user will not get the update.
Hopefully this wil be fixed in a next update.
Anyone got this working the right way / workaround?

Do not use a network or local user to "enroll" a device. Create a Enrolment profile in profile manager I have found that the way you are doing this will work fine. However I am having the problem that now that I have a OD with 350+ users with 100+ devices profile manager cannot keep up and cannot push the settings fast enough or just hangs on user profiles but not device profiles......

Push config files made in Server app with Profile manager

As I understand the manual you can distribuate configuration files with Profile manager.
A bit confused now when I want to use Profile manager to distribuate a configuration file I´ve made in Server app.
I saved a VPN configuration file and want to distribuate it with Profile manager but how do I import or add that file into the settings pane for my devices in profile manager?

Hi,
I have the same issue, very frustrating. Using a Win 2003 AD and 10.8.2 server and clients. If i use WGM I can see all users and groups correctly, but Server.app and Profile Manager does not show them correct.
Strange that we see issues like this since Profile Manager has been around for a while, really interested to hear other peoples experiences.
PS I see a similar thing here: https://discussions.apple.com/thread/4417085?start=0&tstart=0

Having issues with profile manager on 10.9 loosing users/device assignments.

I'm having issues with profile manager on 10.9 loosing users/device assignments. Luckly I only have arround 70 devices added so far. The first time it happened I thought it was just a freak thing, but it has just happened again. What I find weird is nothing on the server was changed, no devices added. So when this happens my users phones lose access to email, because I'm using variables, which rely on the user being assigned to the device. Anyone know how to fix this, and if not. Does anyone know how to backup and restore just profile manager in 10.9. Thanks.

I enabled all users in my AD "Domain Users" group access to "Profile Manager". I had also initially enabled "Profile Manager" access for a few individual users. Those users did not loss the device assignments. I'm not absolutely sure why/if allowing access for a group is causing this issue. Enabling access for each person would be very time consuming.... Maybe adding access to the individual users is importing that user into OD?

Blocking Applications with Profile Manager

At my workplace we recently upgraded to mountain lion and are attepting to use profile manager. After configuring a simple profile and pushing to a test device running 10.7 i decided to further test, i attepted blocking application with parental controls with profile manager through a device group, after pushing the profile and resarting (I know this isn't necessary) the computer the Administrator account is blocked from using every single application, how can i fix this? I even tried just allowing Safari butit still won't work, what should i do?

Just updated OSX - problem solved

How can I disable backup for managed app with profile manager?

I use Server App 3.1.2 to manage iOS devices with profile manager.
Is it possible to exclude managed app's backup from users iCloud or iTunes backup?
thanks
Paolo

Hi,
Please use the following link (under "Manage Print Apps" to cancel/remove it:
http://h10025.www1.hp.com/ewfrf/wc/document?docname=c02940901&cc=us&dlc=en&lc=en&product=5058336&tmp...
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

How To Install A (Almost) Working Lion Server With Profile Management/SSL/OD/Mail/iCal/Address Book/VNC/Web/etc.

I recently installed a fresh version of Lion Server after attempting to fix a broken upgrade. With some help from others, I've managed to get all the new features working and have kept notes, having found that many or most of the necessary installation steps for both the OS and its services are almost entirely undocumented. When you get them working, they work great, but the entire process is very fragile, with simple setup steps causing breaks or even malicious behaviors. In case this is useful to others, here are my notes.
Start with an erased, virgin, single guid partitioned drive. Not an upgrade. Not simply a repartitioned drive. Erased. Clean. Anything else can and probably will break the Lion Server install, as I discovered myself more than once. Before erasing my drive, I already had Lion and made a Lion install DVD from instructions widely available on the web. I suppose you could also boot into the Lion recovery partition and use disk utility to erase the OS X partition then install a new partition, but I cut a DVD. The bottom line is to erase any old OS partitions. And of course to have multiple, independent backups: I use both Time Machine with a modified StdExclusions.plist and Carbon Copy Cloner.
Also, if you will be running your own personal cloud, you will want to know your domain name ahead of time, as this will be propagated everywhere throughout server, and changing anything related to SSL on Lion Server is a nightmare that I haven't figured out. If you don't yet have a domain name, go drop ten dollars at namecheap.com or wherever and reserve one before you start. Soemday someone will document how to change this stuff without breaking Lion Server, but we're not there yet. I'll assume the top-level domain name "domain.com" here.
Given good backups, a Lion Install DVD (or Recovery Partition), and a domain name, here are the steps, apparently all of which must be more-or-less strictly followed in this order.
DVD>Disk Utility>Erase Disk [or Recovery Partition>Disk Utility>Erase Partition]
DVD>Install Lion
Reboot, hopefully Lion install kicks in
Update, update, update Lion (NOT Lion Server yet) until no more updates
System Preferences>Network>Static IP on the LAN (say 10.0.1.2) and Computer name ("server" is a good standbye)
Terminal>$ sudo scutil --set HostName server.domain.com
App Store>Install Lion Server and run through the Setup
Download install Server Admin Tools, then update, update, update until no more updates
Server Admin>DNS>Zones [IF THIS WASN'T AUTOMAGICALLY CREATED (mine wasn't): Add zone domain.com with Nameserver "server.domain.com." (that's a FQDN terminated with a period) and a Mail Exchanger (MX record) "server.domain.com." with priority 10. Add Record>Add Machine (A record) server.domain.com pointing to the server's static IP. You can add fancier DNS aliases and a simpler MX record below after you get through the crucial steps.]
System Prefs>Network>Advanced>Set your DNS server to 127.0.0.1
A few DNS set-up steps and these most important steps:
A. Check that the Unix command "hostname" returns the correct hostname and you can see this hostname in Server.app>Hardware>Network
B. Check that DNS works: the unix commands "host server.domain.com" and "host 10.0.1.2" (assuming that that's your static IP) should point to each other. Do not proceed until DNS works.
C. Get Apple Push Notification Services CA via Server.app>Hardware>Settings><Click toggle, Edit... get a new cert ...>
D. Server.app>Profile Manager>Configure... [Magic script should create OD Master, signed SSL cert]
E. Server.app>Hardware>Settings>SSL Certificate> [Check to make sure it's set to the one just created]
F. Using Server.app, turn on the web, then Server.app>Profile Manager> [Click on hyperlink to get to web page, e.g. server.domain.com/profilemanager] Upper RHS pull-down, install Trust Profile
G. Keychain Access>System>Certificates [Find the automatically generated cert "Domain", the one that is a "Root certificate authority", Highlight and Export as .cer, email to all iOS devices, and click on the authority on the device. It should be entered as a trusted CA on all iOS devices. While you're at it, highlight and Export... as a .cer the certificate "IntermediateCA_SERVER.DOMAIN.COM_1", which is listed an an "Intermediate CA" -- you will use this to establish secure SSL connections with remote browsers hitting your server.]
H. iOS on LAN: browse to server.domain.com/mydevices> [click on LHS Install trust cert, then RHS Enroll device.
I. Test from web browser server.domain.com/mydevices: Lock Device to test
J. ??? Profit
12. Server Admin>DNS>Zones> Add convenient DNS alias records if necessary, e.g., mail.domain.com, smtp.domain.com, www.domain.com. If you want to refer to your box using the convenient shorthand "domain.com", you must enter the A record (NOT alias) "domain.com." FQDN pointing to the server's fixed IP. You can also enter the convenient short MX record "domain.com." with priority 11. This will all work on the LAN -- all these settings must be mirrored on the outside internet using the service from which you registered domain.com.
You are now ready to begin turning on your services. Here are a few important details and gotchas setting up cloud services.
Firewall
Server Admin>Firewall>Services> Open up all ports needed by whichever services you want to run and set up your router (assuming that your server sits behind a router) to port forward these ports to your router's LAN IP. This is most a straightforward exercise in grepping for the correct ports on this page, but there are several jaw-droppingly undocumented omissions of crucial ports for Push Services and Device Enrollment. If you want to enroll your iOS devices, make sure port 1640 is open. If you want Push Notifications to work (you do), then ports 2195, 2196, 5218, and 5223 must be open. The Unix commands "lsof -i :5218" and "nmap -p 5218 server.domain.com" (nmap available from Macports after installing Xcode from the App Store) help show which ports are open.
SSH
Do this with strong security. Server.app to turn on remote logins (open port 22), but edit /etc/sshd_config to turn off root and password logins.
PermitRootLogin no
PasswordAuthentication no
ChallengeResponseAuthentication no
I'm note sure if toggling the Allow remote logins will load this config file or, run "sudo launchctl unload -w /System/Library/LaunchAgents/org.openbsd.ssh-agent.plist ; sudo launchctl load -w /System/Library/LaunchAgents/org.openbsd.ssh-agent.plist" to restart the server's ssh daemon.
Then use ssh-keygen on remote client to generate public/private keys that can be used to remotely login to the server.
client$ ssh-keygen -t rsa -b 2048 -C client_name
[Securely copy ~/.ssh/id_rsa.pub from client to server.]
server$ cat id_rsa.pub > ~/.ssh/known_hosts
I also like DenyHosts, which emails detected ssh attacks to [email protected]. It's amazing how many ssh attacks there are on any open port 22. Not really an added security feature if you've turned off password logins, but good to monitor. Here's a Lion Server diff for the config file /usr/share/denyhosts:
$ diff denyhosts.cfg-dist denyhosts.cfg
12c12
< SECURE_LOG = /var/log/secure
> #SECURE_LOG = /var/log/secure
22a23
> SECURE_LOG = /var/log/secure.log
34c35
< HOSTS_DENY = /etc/hosts.deny
> #HOSTS_DENY = /etc/hosts.deny
40a42,44
> #
> # Mac OS X Lion Server
> HOSTS_DENY = /private/etc/hosts.deny
195c199
< LOCK_FILE = /var/lock/subsys/denyhosts
> #LOCK_FILE = /var/lock/subsys/denyhosts
202a207,208
> LOCK_FILE = /var/denyhosts/denyhosts.pid
> #
219c225
< ADMIN_EMAIL =
> ADMIN_EMAIL = [email protected]
286c292
< #SYSLOG_REPORT=YES
> SYSLOG_REPORT=YES
Network Accounts
User Server.app to create your network accounts; do not use Workgroup Manager. If you use Workgroup Manager, as I did, then your accounts will not have email addresses specified and iCal Server WILL NOT COMPLETELY WORK. Well, at least collaboration through network accounts will be handled clunkily through email, not automatically as they should. If you create a network account using Workgroup Manager, then edit that account using Server.app to specify the email to which iCal invitations may be sent. Server.app doesn't say anything about this, but that's one thing that email address entry is used for. This still isn't quite solid on Lion Server, as my Open Directory logs on a freshly installed Lion Server are filled with errors that read:
2011-12-12 15:05:52.425 EST - Module: SystemCache - Misconfiguration detected in hash 'Kerberos':
     User 'uname' (/LDAPv3/127.0.0.1) - ID 1031 - UUID 98B4DF30-09CF-42F1-6C31-9D55FE4A0812 - SID S-0-8-83-8930552043-0845248631-7065481045-9092
Oh well.
Email
Email aliases are handled with the file /private/etc/postfix/aliases. Do something like this
root:           myname
admin:          myname
sysadmin:       myname
certadmin:      myname
webmaster:      myname
my_alternate:   myname
Then run "sudo newaliases". If your ISP is Comcast or some other large provider, you probably must proxy your outgoing mail through their SMTP servers to avoid being blocked as a spammer (a lot of SMTP servers will block email from Comcast/whatever IP addresses that isn't sent by Comcast). Use Server.app>Mail to enter your account information. Even then, the Lion Server default setup may fail using this proxy. I had to do this with the file /private/etc/postfix/main.cf:
cd /etc/postfix
sudo cp ./main.cf ./main.cf.no_smtp_sasl_security_options
sudo echo 'smtp_sasl_security_options = noanonymous' >> ./main.cf
sudo serveradmin stop mail
sudo serveradmin start mail
Finally, make sure that you're running a blacklisting srevice yourself! Server Admin>Mail>Filter> Use spamhaus.org as a blacklister. Finally, set up mail to use strong Kerberos/MD5 settings under on Server Admin>Mail>Advanced. Turn off password and clear logins. The settings should be set to "Use" your SSL cert, NOT "Require". "Require" consistently breaks things for me.
If you already installed the server's Trust Certificate as described above (and opened up the correct ports), email to your account should be pushed out to all clients.
iCal Server
Server.app>Calendar>Turn ON and Allow Email Invitations, Edit... . Whatever you do, do NOT enter your own email account information in this GUI. You must enter the account information for local user com.apple.calendarserver, and the password for this account, which is stored in the System keychain: Keychain Access>System> Item com.apple.servermgr_calendar. Double-click and Show Password, copy and paste into Server.app dialog. This is all described in depth here. If you enter your own account information here (DO NOT!), the iCal Server will delete all Emails in your Inbox just as soon as it reads them, exactly like it works for user com.apple.calendarserver. Believe me, you don't want to discover this "feature", which I expect will be more tightly controlled in some future update.
Web
The functionality of Server.app's Web management is pretty limited and awful, but a few changes to the file /etc/apache2/httpd.conf will give you a pretty capable and flexible web server, just one that you must manage by hand. Here's a diff for httpd.conf:
$ diff httpd.conf.default httpd.conf
95c95
< #LoadModule ssl_module libexec/apache2/mod_ssl.so
> LoadModule ssl_module libexec/apache2/mod_ssl.so
111c111
< #LoadModule php5_module libexec/apache2/libphp5.so
> LoadModule php5_module libexec/apache2/libphp5.so
139,140c139,140
< #LoadModule auth_digest_apple_module libexec/apache2/mod_auth_digest_apple.so
< #LoadModule encoding_module libexec/apache2/mod_encoding.so
> LoadModule auth_digest_apple_module libexec/apache2/mod_auth_digest_apple.so
> LoadModule encoding_module libexec/apache2/mod_encoding.so
146c146
< #LoadModule xsendfile_module libexec/apache2/mod_xsendfile.so
> LoadModule xsendfile_module libexec/apache2/mod_xsendfile.so
177c177
< ServerAdmin [email protected]
> ServerAdmin [email protected]
186c186
< #ServerName www.example.com:80
> ServerName domain.com:443
677a678,680
> # Server-specific configuration
> # sudo apachectl -D WEBSERVICE_ON -D MACOSXSERVER -k restart
> Include /etc/apache2/mydomain/*.conf
I did "sudo mkdir /etc/apache2/mydomain" and add specific config files for various web pages to host. For example, here's a config file that will host the entire contents of an EyeTV DVR, all password controlled with htdigest ("htdigest ~uname/.htdigest EyeTV uname"). Browsing to https://server.domain.com/eyetv points to /Users/uname/Sites/EyeTV, in which there's an index.php script that can read and display the EyeTV archive at https://server.domain.com/eyetv_archive. If you want Apache username accounts with twiddles as in https://server.domain.com/~uname, specify "UserDir Sites" in the configuration file.
Alias /eyetv /Users/uname/Sites/EyeTV
<Directory "/Users/uname/Sites/EyeTV">
    AuthType Digest
    AuthName "EyeTV"
    AuthUserFile /Users/uname/.htdigest
    AuthGroupFile /dev/null
    Require user uname
    Options Indexes MultiViews
    AllowOverride All
    Order allow,deny
    Allow from all
</Directory>
Alias /eyetv_archive "/Volumes/Macintosh HD2/Documents/EyeTV Archive"
<Directory "/Volumes/Macintosh HD2/Documents/EyeTV Archive">
    AuthType Digest
    AuthName "EyeTV"
    AuthUserFile /Users/uname/.htdigest
    AuthGroupFile /dev/null
    Require user uname
    Options Indexes MultiViews
    AllowOverride All
    Order allow,deny
    Allow from all
</Directory>
I think you can turn Web off/on in Server.app to relaunch apached, or simply "sudo apachectl -D WEBSERVICE_ON -D MACOSXSERVER -k restart".
Securely copy to all desired remote clients the file IntermediateCA_SERVER.DOMAIN.COM_1.cer, which you exported from System Keychain above. Add this certificate to your remote keychain and trust it, allowing secure connections between remote clients and your server. Also on remote clients: Firefox>Advanced>Encryption>View Certificates>Authorities>Import...> Import this certificate into your browser. Now there should be a secure connection to https://server.domain.com without any SSL warnings.
One caveat is that there should be a nice way to establish secure SSL to https://domain.com and https://www.domain.com, but the automagically created SSL certificate only knows about server.domain.com. I attempted to follow this advice when I originally created the cert and add these additional domains (under "Subject Alternate Name Extension"), but the cert creation UI failed when I did this, so I just gave up. I hope that by the time these certs expire, someone posts some documentation on how to manage and change Lion Server SSL scripts AFTER the server has been promoted to an Open Directory Master. In the meantime, it would be much appreciated if anyone can post either how to add these additional domain names to the existing cert, or generate and/or sign a cert with a self-created Keychain Access root certificate authority. In my experience, any attempt to mess with the SSL certs automatically generated just breaks Lion Server.
Finally, if you don't want a little Apple logo as your web page icon, create your own 16×16 PNG and copy it to the file /Library/Server/Web/Data/Sites/Default/favicon.ico. And request that all web-crawling robots go away with the file /Library/Server/Web/Data/Sites/Default/robots.txt:
User-agent: *
Disallow: /
Misc
VNC easily works with iOS devices -- use a good passphrase. Edit /System/Library/LaunchDaemons/org.postgresql.postgres.plist and set "listen_addresses=127.0.0.1" to allow PostgreSQL connections over localhost. I've also downloaded snort/base/swatch to build an intrusion detection system, and used Macports's squid+privoxy to build a privacy-enhanced ad-blocking proxy server.

Privacy Enhancing Filtering Proxy and SSH Tunnel
Lion Server comes with its own web proxy, but chaining Squid and Privoxy together provides a capable and effective web proxy that can block ads and malicious scripts, and conceal information used to track you around the web. I've posted a simple way to build and use a privacy enhancing web proxy here. While you're at it, configure your OS and browsers to block Adobe Flash cookies and block Flash access to your camera, microphone, and peer networks. Read this WSJ article series to understand how this impacts your privacy. If you configure it to allow use for anyone on your LAN, be sure to open up ports 3128, 8118, and 8123 on your firewall.
If you've set up ssh and/or VPN as above, you can securely tunnel in to your proxy from anywhere. The syntax for ssh tunnels is a little obscure, so I wrote a little ssh tunnel script with a simpler flexible syntax. This script also allows secure tunnels to other services like VNC (port 5900). If you save this to a file ./ssht (and chmod a+x ./ssht), example syntax to establish an ssh tunnel through localhost:8080 (or, e.g., localhost:5901 for secure VNC Screen Sharing connects) looks like:
$ ./ssht 8080:[email protected]:3128
$ ./ssht 8080:alice@:
$ ./ssht 8080:
$ ./ssht 8018::8123
$ ./ssht 5901::5900 [Use the address localhost:5901 for secure VNC connects using OS X's Screen Sharing or Chicken of the VNC (sudo port install cotvnc)]
$ vi ./ssht
#!/bin/sh
# SSH tunnel to squid/whatever proxy: ssht [-p ssh_port] [localhost_port:][user_name@][ip_address][:remotehost][:remote_port]
USERNAME_DEFAULT=username
HOSTNAME_DEFAULT=domain.com
SSHPORT_DEFAULT=22
# SSH port forwarding specs, e.g. 8080:localhost:3128
LOCALHOSTPORT_DEFAULT=8080      # Default is http proxy 8080
REMOTEHOST_DEFAULT=localhost    # Default is localhost
REMOTEPORT_DEFAULT=3128         # Default is Squid port
# Parse ssh port and tunnel details if specified
SSHPORT=$SSHPORT_DEFAULT
TUNNEL_DETAILS=$LOCALHOSTPORT_DEFAULT:$USERNAME_DEFAULT@$HOSTNAME_DEFAULT:$REMOT EHOST_DEFAULT:$REMOTEPORT_DEFAULT
while [ "$1" != "" ]
do
case $1
in
    -p) shift;                  # -p option
        SSHPORT=$1;
        shift;;
     *) TUNNEL_DETAILS=$1;      # 1st argument option
        shift;;
esac
done
# Get local and remote ports, username, and hostname from the command line argument: localhost_port:user_name@ip_address:remote_host:remote_port
shopt -s extglob                        # needed for +(pattern) syntax; man sh
LOCALHOSTPORT=$LOCALHOSTPORT_DEFAULT
USERNAME=$USERNAME_DEFAULT
HOSTNAME=$HOSTNAME_DEFAULT
REMOTEHOST=$REMOTEHOST_DEFAULT
REMOTEPORT=$REMOTEPORT_DEFAULT
# LOCALHOSTPORT
CDR=${TUNNEL_DETAILS#+([0-9]):}         # delete shortest leading +([0-9]):
CAR=${TUNNEL_DETAILS%%$CDR}             # cut this string from TUNNEL_DETAILS
CAR=${CAR%:}                            # delete :
if [ "$CAR" != "" ]                     # leading or trailing port specified
then
    LOCALHOSTPORT=$CAR
fi
TUNNEL_DETAILS=$CDR
# REMOTEPORT
CDR=${TUNNEL_DETAILS%:+([0-9])}         # delete shortest trailing :+([0-9])
CAR=${TUNNEL_DETAILS##$CDR}             # cut this string from TUNNEL_DETAILS
CAR=${CAR#:}                            # delete :
if [ "$CAR" != "" ]                     # leading or trailing port specified
then
    REMOTEPORT=$CAR
fi
TUNNEL_DETAILS=$CDR
# REMOTEHOST
CDR=${TUNNEL_DETAILS%:*}                # delete shortest trailing :*
CAR=${TUNNEL_DETAILS##$CDR}             # cut this string from TUNNEL_DETAILS
CAR=${CAR#:}                            # delete :
if [ "$CAR" != "" ]                     # leading or trailing port specified
then
    REMOTEHOST=$CAR
fi
TUNNEL_DETAILS=$CDR
# USERNAME
CDR=${TUNNEL_DETAILS#*@}                # delete shortest leading +([0-9]):
CAR=${TUNNEL_DETAILS%%$CDR}             # cut this string from TUNNEL_DETAILS
CAR=${CAR%@}                            # delete @
if [ "$CAR" != "" ]                     # leading or trailing port specified
then
    USERNAME=$CAR
fi
TUNNEL_DETAILS=$CDR
# HOSTNAME
HOSTNAME=$TUNNEL_DETAILS
if [ "$HOSTNAME" == "" ]                # no hostname given
then
    HOSTNAME=$HOSTNAME_DEFAULT
fi
ssh -p $SSHPORT -L $LOCALHOSTPORT:$REMOTEHOST:$REMOTEPORT -l $USERNAME $HOSTNAME -f -C -q -N \
    && echo "SSH tunnel established via $LOCALHOSTPORT:$REMOTEHOST:$REMOTEPORT\n\tto $USERNAME@$HOSTNAME:$SSHPORT." \
    || echo "SSH tunnel FAIL."

Cant add Apps to login items with profile manager

I can set up profile manager successfully, and set certain settings like the Dock, the login window, etc. But when I click on Login Items, and try to add an Application, the list of applications is blank. Tried it from my server, tried it logged in remotely, tried rebooting, tried it on several accounts and several groups, and its always empty.

found it:
/usr/bin/osascript -e 'tell application "System Events" to make new login item with properties { path: "/Applications/iChat.app", hidden:false } at end'

Is it possible Messages Settings break Profile Manager?

I've recently been playing about with the Messages app in ML and ML server.
I've got everything working manually, as in going to each machine, logging in as the user and adding their credentials to the Messages app.
I'm trying to automate this using profile manager, I've done simialr for Mail settings but the profile never succeeds. Always fails.
Removing the Messages component from the Profile makes everything work again.
Is this possible? I don't see how it could be any of the information that I am typing in the boxes that breaks it, I've been using %short_name% for the use names, this works for the Mail settings, could this be breaking it?

Hi,
Partner profile setting are actually soft configuration and you cannot transport them.
You have to set partner profile in all stages.
Nilesh

Early on while configuring the Device Management settings in Profile Manager (Mavericks server) I received an error code -1

When I started up the Server application, Profile Manager was not selected as expected. I selected it and started the first step of configuring Device Management in the Settings section. I entered the organization information and went on to the next step which was to Configure an SSL Certificate
I selected a "Self Signed" Cert. Which was the only one of the two choices that made sense. The other being the, com.deploystudio.server - Self signed
Hit next and it processed the info and went to "Finish" I click "Finish" and this is what I get when the setting are confirmed.
I stopped there since I suspect this error will probably come back to haunt me further down the line as if you recall we could not get the Profile to install due to the invalid cert which I suspect has something to do with this code -1 error at the get go. I ran the one command line instruction twice to verify this was not a quirk and the same occurred.
sudo /Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeDB.sh

Did you ever get this resolved? This error is usually related to DNS, hostname, or Open Directory configuration. Let me know if you still need help.

How to deploy settings in Profile Manager through Device Groups

When I go to the Profile Manager web page and create a device group and configure the payload settings it doesn't seem to send the profile settings to the Mac devices that are in the group. How do I go about getting this to work so when I get a new device that is enrolled all I have to do is throw it in the group so it will automatically push out the correct payload settings that I configured?

What you're asking should work. You should be able to create a Device Group and adjust the setting for that group. Then when you add a device to that group, the settings will be pushed to the device automatically. So, it leaves me with a few questions for you:
Why don't you think it sends the payload? When you look under "Activity" do you see tasks in the "Active" area or in the "Completed" area... or something else?
What are you trying to change? Setting up email accounts on iPhones will appear right away, but there are other changes (especially on computers) that don't take affect until it restarts (or the user at least logs out and back in).
Are you sure you have devices in your device group? Sorry, probably a really silly question, but under your device group, do you see the devices under the "Members" section?
Are your devices "trusting" your server? Did you add the trust profile to the device when you enrolled it?
Sorry I can't be more help... but I can tell you that you can do what you are asking. We have it set up in our office, and it works really well. We just add the new device to the device group and it does the rest.

Manage ARD with Profile Manager

We have a lot of "out of the box" macs in our environment we want to tame so are setting up OD and Profile Manager. Since they are out of the box, SSH and ARD are all disabled. After we get the Macs connected to OD, can we use Profile Manager to enable ARD on the clients allowing our local admin account only to access them with all the check boxes checked? Is it that granular?

That is a good question and as far as I know, the overt answer is no. While Apple has a custom setting option in Profile Manager for OS X (http://help.apple.com/profilemanager/mac/10.7/#apd9ABBDBE7-E899-4EF8-A087-CC771A E6729A), this setting is controlled by the defaults command and anything you can control with it. The issue with ARD is that it is still controlled by the archaic kickstart command. And this does not lend itself the the limited structure of profile manager.
Now, one possible way to achieve this without something like JAMF is to create a payload-less installer that contains just a post install script. The script would contain the kickstart command with all your required settings. This would allow you to enable ARD after the fact.
Now, if you are binding the machines to OD, perhaps you combine the binding script with the enable ARD kickstart command. Afterall, the assumption is that you are touching these devices at some point.
I have not tried this and perhaps others in the community can provide additional insight.

Set advanced IMAP settings with profile manager?

Similar Messages

Maybe you are looking for