CalDAV created as "manual download" by profile manager.

why CalDav account pushed by profile manager to my iDevices are created and setted as "fetch manually" and not as "push" ?
is there a way to tell profile manager to create them as "push" or at least to "fetch every X minutes" ?
if I manually create the account on my idevice it will let me set as "push".
if Profile manager create the account for me it will set it as "manual" and the "push" setting is unavailable.
i use iCal server from Lion Server (fully updated) and iOS 5.1 (fully updated)
thanks.

no one ? please help me

Similar Messages

Deploying Calendars via Profile Manager

I recently needed to start sharing calendars between staff here at school. I have successfully created and shared calendars between two test accounts, setting them up manually via the "Mail, Contacts & Calendars" section of system preferences for each user.
I then shared then opened up the calendar app and shared each test accounts calendar with each other via the right click menu>Sharing Settings.
Everything is working exactly as I want but I want to automate this setup for our staff and so I turned to profile manager thinking that we could at least skip the step that was covered through "Mail, Contacts and Calendar".
I could not.
It seems that Profile Manager settings requires a password which is terrible and that would have all staff subscribe to one calendar account rather than having their own.
Is there a way around this or am I destined to set up each user individually?

Thank you both so very much for using these forums. Today I was having the issue of the profile not pushing when there were Calendar settings in the profile. Then I ran across this discussion. I was able to confirm your findings Henry. Indeed when I set it to manual, downloaded the profile and installed, it worked like a charm. (sad this is still an issue in Yosemite) Anyway, it gave me an idea. All I did was add a description to the General section of the profile, changed it back to automatic push, no password installed and using SSL, and it worked. I have no idea, but just placing a comment in the field did the trick. Thought it should be shared. Thanks for your discussion, help, and feedback. Have a great day!

Argh! Profile Manager and Code-Signing of profiles

I am setting up Profile Manager in Mavericks with Server.app 3.0.1.
I have DNS correctly setup, I have created an OD Master for Profile Manager, Profile Manager is running and network users can login and I can setup profiles. I also have the https site working properly for clients although that needed some help.
We have a self-signed root CA and off that we have two intermediate CAs, one for signing server SSL certificates, and one for signing codesigning certificates. On my server I have installed the rootCA, and the intermediate CAs and of course the server SSL certificate itself. As mentioned initially I had a problem with the https site on the server and what was happening was that the server was not sending the intermediate certificate along with the server certificate to clients. (The clients already have our rootCA certificate installed and trusted.)
As a result the chain was incomplete and clients did not trust the http site. I tracked this down to the files in /etc/certificates it turned out that of the four files for the server certificate i.e. .key.pem, .chain.pem, .concat.pem and .cert.pem that the .chain.pem did not contain the intermediate CA. I replaced it with the intermediate CA pem file and restarted Apache and clients now get the full chain and can therefore trust the https site.
My problem now is with the codesigning certificate, this also has been selfsigned this time by the intermediate codesigningCA. It is accepted by Profile Manager and it does sign the profiles. However when I download the Trust profile and try installing it, it comes back unverified. (If it was unsigned it would say unsigned instead.) This trust profile contains a copy of the server certificate and the rootCA certificate but does not contain the intermediate codesigningCA certificate.
I tried the same trick of swapping out the codesigning .chain.pem file in /etc/certificates but this did not help. I am currently stuck, any suggestions from any one?
Thanks.

I would really appreciate being walked through these steps. I just upgraded to Yosemite and Server.app 4 and am dealing with all the brokenness.
Profile Manager does not show a code signing certificate when I ask it to sign configuration profiles.
I DO NOT have the Code Signing Certificate in my keychain created when OD was created.
I DO have the four code signing certificate files:
/etc/certificates/host.domain.tld.Code Signing Certificate.<UUID hash>.cert.pem
/etc/certificates/host.domain.tld.Code Signing Certificate.<UUID hash>.chain.pem
/etc/certificates/host.domain.tld.Code Signing Certificate.<UUID hash>.concat.pem
/etc/certificates/host.domain.tld.Code Signing Certificate.<UUID hash>.key.pem
Furthermore, when I search my System keychain passwords, for <UUID hash>, I see that have the password that decrypts these pem's, e.g. via the openssl command
openssl rsa -outform der -in 'host.domain.tld.Code Signing Certificate.<UUID hash>.key.pem' -out 'host.domain.tld.Code Signing Certificate.<UUID hash>.key'
What's the specific step-by-step to convert these four files into something that Profile Manager can use to sign configuration profiles?
I am stuck.

Mac Mini Profile Manager installing/updating ipad Apps - HELP!

Hi,
i am hoping someone might be able to help with the following.
we have a mac mini server to remote manage 25 ipads using profile manager.
this works well as we can lock, wipe and clear passcodes etc.and attach the policies without any trouble.
However we are trying to push out an app (version 1.4) to the devices and this is sort of working but not fully.
if the app is already installed with version 1.3 it doesnt update even though in profile manager, 'active tasks' it says successful.
if you go go into profile manager and select the device and select 'update info' this registers against the device but still shows as the old version.
if we delete the app from our test ipad and push it out via profile manager it goes in active tasks as successful then the ipad has a pop up message box saying the xxxxxx.ourdomain.co.uk would like to install the app, once this has been ok'd it installs on the ipad ok, but when you select the app it tries to open then goes back to the screen again and never opens the app.
if you download the app direct from itunes it opens with out any trouble.
here is the process i am using.
on the mac mini server.
download the app via itunes
then in apps i drag the app on to the desktop, this creates the .ipa file
in profile manager, select the device, edit apps and browse to the .ipa and upload
select the uploaded app and 'add'
when you save this, then go to active tasks it gets pushed out to the device and reports as successful
then the app either doesnt update if old version is installed or installs if no app is installed but doesnt open
any help welcome
regards
Gavin

Gavin,
We've run into the same issue that you mentioned. My understanding of the Push App functionality of Profile Manager is this:
Pushing apps is designed to be used to deliver In-House developed apps over the air (OTA). Meaning, if your organization develops an app for use on its own devices, you can upload the .ipa to Profile Manager and push it out while bypassing any App Store interaction. The In-House .ipa would contain its own provisioning profile that would dictate who is allowed to run it.
When you download an app from the App Store, the .ipa that you get actually contains the AppleID that was used to purchase/download the app in the .plist. If you then push that app to a device that has never been used with that AppleID, the app will fail to launch as it cannot verify that you actually own the app.
Before we go any further: what I'm about to discuss isn't officially condoned or supported by Apple, which means it is inheritly risky and could be patched over at any time.
In order to bypass the issue, what has worked for us is to sign into the App Store on each iPad with the AppleID that is used to purchase the apps on your Mac Mini. You need to download at least one app to the iPad while logged in with that AppleID in order for the iPad to retain the AppleID after the iPad users log in again with their personal AppleID. After you have done that, users may once again log in with their own AppleID.
At this point, you can push an app to any of those devices that have been paired with your Mac Mini's AppleID at least once. The apps won't (immediately) crash.
Here's the catch: I'm told that the .ipa contains an "expiration date" of sorts. Once that date has elapsed, your iPad will attempt to extend the expiration date by connecting to the App Store to verify that the same AppleID that was used to download the app in the first place is still active on the device. If it is not, the app may once again crash when you attempt to run it. Now, this expiration date or timer is not disclosed, meaning, if this is really the case, you will have no idea when the apps will stop working. It could be weeks, or months, or years. A gamble, really. So, use that at your own risk.
Currently, there is no official method for pushing App Store apps Over-the-air with Profile Manager or any other Mobile Device Management platform.
Remember!: If you are even considering pushing apps in the manner mentioned above, you will still need to account for licensing. As an organization, you must have purchased the same number of copies of an app as you intend to install on your devices. This is a non-issue with free apps, but for auditing purposes, you'd best look into VPP or steer clear of pushing apps altogether.
I hope some of that helped clear up your question.
Good luck!

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

Profile Manager Tasks Queue up without completing

I've got a fresh Lion server, fully-qualified, publicly-addressable DNS, brand-new SSL Cert installed and working, ready for Profile Manager. I can enroll the iPad just fine, and it shows up in Profile Manager as a New Device. Unfortunately, it never makes it past that point. The initial tasks that Profile Manager performs on new devices (the "Update Info: New Device" tasks) just queue up, and never complete. If I do anything else with the iPad (setting restrictions, attempting to lock it, etc), those tasks just get added to the end of the queue and don't go anywhere.
I've got all the ports open for the Lion server (in fact, at the moment, I opened the firewall completely for the server). I also opened what I believe are the relevant ports for my LAN subnets as well (though in theory, that shouldn't be necessary, since the iPads only talk to the APNS servers and shouldn't need anything special beyond that).
Am I missing something?

Hi Josh,
I don't know if this fits with what you are doing! But, instead of automatic push, try manual download of profiles. You open profile manager/my devices in safari and log in as the user on your client machine. From there you can enroll and download profiles. You will have to configure the General payload for each device/group etc., to manual though on your server.
I've found this to be the easiest option because of all the hassles with auto push etc.. This means you can reapply your firewalls and close your ports.
LS 10.7.2 doesn't improve on any of the issues either. Very buggy indeed!
I hope this helps.
Paul.

(null) users listed in Profile Manager

While configuring Lion Server, I created and reset Open Directory several times as I experimented with different configurations. As you can see from the attached image, it appears that this action has created (null) users in the profile manager user list. These users do not show up in Open Directory when viewed via Workgroup Manager. Does anyone know how to get rid of them? Thanks in advance.

Hi Mike,
And my problems have gotten worse because I ran the WipeDB tool and I have destroyed the Open Directory several times in an attempt to remove the null users, but now when I rebuild everything and start from "scratch" the Profile Manager page crashes regularly.
I even went so far as to rename the host name on the machine to see if the new Open Directory that it created would emerge in a new structure, but no luck.
The "Null" users no longer say "null null", now their entries just say "loading..." and they never load, probably because there is nothing TO load, just old dead record pointers somewhere in the Profile Manager.
I've hunted through the file system in command line trying to figure out where any of this data might be stored, but I haven't found anything I feel comfortable deleting yet. I'm facing a reformat of the disks and a re-installatoin of the OS if I can't figure out how to fix this.
How can I clean this up? Anyone have any idea?
Thanks,
Ralph

Profile Manager - Why create Enrollment Profiles?

So a similar question was asked previously:
Why use an enrollment profile?
I've read through it and I don't think the answers provided tell the whole story, so I'd like to ask again adding some of my own thought and clarifications on the previous thread. This may be considered a "primer" by some - though I am certainly not the expert on Profile Manager. I'm laying it out there to explain my understanding and off of that, ask a question. If you are an expert, and understand how all this works, please just skip to my question below!
First, my experience and understanding. (I urge others to correct/clarify where they see fit):
The previous thread attempted to make a distinction between the 3 different types of profiles: Trust, Enrollment.and Remote Management Profiles.
I believe the proper 3 distinctions should be: Trust, Remote Management/Enrollment, and Configuration Profiles.
- The Trust Profile is basically a Profile (.mobileconfig file) that contains the Server Certificate that needs to be present to validate other signed Profiles. It's a fancy way of packaging up the Root certificates.
- The Remote Management/Enrollment Profile is a Profile (.mobileconfig file) that delivers the Remote Management "connection". It registers the device with the Profile Manager server and facilitates the ability to use PM/APNS to push various Configuration Profiles as well as commands (wipe/lock/etc). It is *only* called an Enrollment Profile when you explicitly create one (more on that below). Because an Enrollment Profile does not need to exist to enroll (or rather it will use the implicit "unseen" enrollment), this is the most confusing of the 3 Profile types. It is further confusing because the term "Profile" is used almost elusively on the device and not within Profile Manager. In fact the "Enrollment Profile" is the only one explicitly called a "Profile" within the management interface!
IOW: While it is not shown anywhere in Profile Manager, I believe that "Remote Management" (called a Profile on the device) is basically the *default* Enrollment Profile that is only inferred and seen when you use the Enroll function on MyDevices. This means you don't need to create any Enrollment Profile to enroll your devices interactively via the MyDevices page.
- The Configuration Profile is a Profile (.mobileconfig file) that delivers specific settings. These Profiles are applied to either Users, Groups, Devices, or Device Groups. They can be automatically pushed to an enrolled device, or they can be manually downloaded from the MyDevices page (seems to apply to User configuration only) for devices even if they are not enrolled (this would allow the end user the 'choice' to pull down settings).
Having outlined that, the simplest steps to enrollment...:
When you setup Profile Manager, you can go right to the MyDevices page on your device, login, and choose "Enroll." (sample device is let's say an iPad)
Doing so will prompt you to install the "Remote Management" profile.
Note that when enrolling in this way it does not appear necessary to install the "Trust Profile" for your server, even when using a Self-signed Cert. It would appear that this "Remote Management" profile contains not only the SCEP Enrollment Request and the Device Management payload, but also the Certificates that would be installed with the "Trust profile"
So we have seen here that one can enroll a device without explicitly creating any "Enrollment Profile."
So why use an Enrollment Profile?
Well according to https://help.apple.com/profilemanager/mac/3.1/#apd6DD5E89E-2466-4D3C-987E-A4FF05 676EB7, the answer is pretty straightforward:
"The user does not need to authenticate or log in to Profile Manager’s user portal"
This is a great feature. For one, you can create an Enrollment Profile and send it via e-mail and the user doesn't need to visit a web page and login to enroll a device. In fact, based on my experience Enrollment Profiles can't even be accessed via the MyDevices page unless you are a Server Admin.
However, when distributing an Enrollment Profile you seemingly *must* install the Trust Profile prior to this, or you will get an error about communicating with the server. Several docs/tutorials you can google explain how to set up your deployment systems (specifically OSX machines) to deploy systems with both the Trust and Enrollment profiles to facilitate automatic enrollment when a new system is deployed so it can instantly be managed.
However, since a device that is already deployed will/may not have the Trust Profile installed, one would have to visit the MyDevices page to install that prior to being able to import a delivered Enrollment Profile. Because of that it seems that from a distribution approach (as opposed to a deployment scenario) there is not much advantage of using an explicit Enrollment Profile anyway since we already need to visit the MyDevices page to get the Trust Profile, we might as well just use the standard MyDevices implicit Enrollment.
All devices that have enrolled themselves via a defined/explicit Enrollment Profile will be listed under that Profile in Profile Manager. Devices that have enrolled via MyDevices will not be listed under any Profile, but rather just under Devices (where *all* devices will be shown regardless of how they enrolled).
So, now the questions:
So, the idea of an Enrollment Profile makes perfect sense - it is basically the only way to create an exportable profile that can be distributed and configured to automatically enroll a device without interactive enrollment via the MyDevices page.
What I don't get is WHY is there the ability to create multiple Enrollment Profiles rather than simply providing a default exportable profile?
The reason it makes no sense to me is there is absolutely no correlation (that I can deduce) between an Enrollment Profile and the devices that used it to enroll. While I can see a (non-exportable) list of each device enrolled via each Enrollment Profile, it ends there. I can't, for instance, create Configuration Settings that I link to an Enrollment Profile. Or dynamically populate a Device Group with all devices enrolled from a specific Enrollment Profile. If I could do these things, it might make sense to me and I have spent much time looking at the interface and scouring documentation to see where the connection is. I have simply determined that there isn't one.
I can go ahead and create several Enrollment Profiles such as:
iPads
Lab Systems
Main Office Systems
High Security Systems
And I can deploy these Profiles (either via mail/file or via initial deployment) to the respective devices. I can then see under each Profile which devices enrolled. But, since I can't actually do anything to correlate those systems to a configuration, why would I want to do this segregation? Sure it gives me a listing of iPads apart from OSX machines, but I can't do anything with this listing!
Now, of course, I can still pre-stage devices and add them into particular device groups so that as soon as they are enrolled (via any Enrollment Profile) they will get the Configuration Profile(s) attached to them. This makes the inclusion of multiple Enrollment Profiles even more suspect.
Am I missing something? Can someone enlighten me as to what the purpose of creating more than one Enrollment Profile would be?
We can easily say "Well it's not hurting having them there" but, in terms of complexity and confusion I believe it is. Had they simply provided a single Enrollment Profile ("Remote Management") that was downloadable/exportable it would have been sufficient.
Thoughts?

So a similar question was asked previously:
Why use an enrollment profile?
I've read through it and I don't think the answers provided tell the whole story, so I'd like to ask again adding some of my own thought and clarifications on the previous thread. This may be considered a "primer" by some - though I am certainly not the expert on Profile Manager. I'm laying it out there to explain my understanding and off of that, ask a question. If you are an expert, and understand how all this works, please just skip to my question below!
First, my experience and understanding. (I urge others to correct/clarify where they see fit):
The previous thread attempted to make a distinction between the 3 different types of profiles: Trust, Enrollment.and Remote Management Profiles.
I believe the proper 3 distinctions should be: Trust, Remote Management/Enrollment, and Configuration Profiles.
- The Trust Profile is basically a Profile (.mobileconfig file) that contains the Server Certificate that needs to be present to validate other signed Profiles. It's a fancy way of packaging up the Root certificates.
- The Remote Management/Enrollment Profile is a Profile (.mobileconfig file) that delivers the Remote Management "connection". It registers the device with the Profile Manager server and facilitates the ability to use PM/APNS to push various Configuration Profiles as well as commands (wipe/lock/etc). It is *only* called an Enrollment Profile when you explicitly create one (more on that below). Because an Enrollment Profile does not need to exist to enroll (or rather it will use the implicit "unseen" enrollment), this is the most confusing of the 3 Profile types. It is further confusing because the term "Profile" is used almost elusively on the device and not within Profile Manager. In fact the "Enrollment Profile" is the only one explicitly called a "Profile" within the management interface!
IOW: While it is not shown anywhere in Profile Manager, I believe that "Remote Management" (called a Profile on the device) is basically the *default* Enrollment Profile that is only inferred and seen when you use the Enroll function on MyDevices. This means you don't need to create any Enrollment Profile to enroll your devices interactively via the MyDevices page.
- The Configuration Profile is a Profile (.mobileconfig file) that delivers specific settings. These Profiles are applied to either Users, Groups, Devices, or Device Groups. They can be automatically pushed to an enrolled device, or they can be manually downloaded from the MyDevices page (seems to apply to User configuration only) for devices even if they are not enrolled (this would allow the end user the 'choice' to pull down settings).
Having outlined that, the simplest steps to enrollment...:
When you setup Profile Manager, you can go right to the MyDevices page on your device, login, and choose "Enroll." (sample device is let's say an iPad)
Doing so will prompt you to install the "Remote Management" profile.
Note that when enrolling in this way it does not appear necessary to install the "Trust Profile" for your server, even when using a Self-signed Cert. It would appear that this "Remote Management" profile contains not only the SCEP Enrollment Request and the Device Management payload, but also the Certificates that would be installed with the "Trust profile"
So we have seen here that one can enroll a device without explicitly creating any "Enrollment Profile."
So why use an Enrollment Profile?
Well according to https://help.apple.com/profilemanager/mac/3.1/#apd6DD5E89E-2466-4D3C-987E-A4FF05 676EB7, the answer is pretty straightforward:
"The user does not need to authenticate or log in to Profile Manager’s user portal"
This is a great feature. For one, you can create an Enrollment Profile and send it via e-mail and the user doesn't need to visit a web page and login to enroll a device. In fact, based on my experience Enrollment Profiles can't even be accessed via the MyDevices page unless you are a Server Admin.
However, when distributing an Enrollment Profile you seemingly *must* install the Trust Profile prior to this, or you will get an error about communicating with the server. Several docs/tutorials you can google explain how to set up your deployment systems (specifically OSX machines) to deploy systems with both the Trust and Enrollment profiles to facilitate automatic enrollment when a new system is deployed so it can instantly be managed.
However, since a device that is already deployed will/may not have the Trust Profile installed, one would have to visit the MyDevices page to install that prior to being able to import a delivered Enrollment Profile. Because of that it seems that from a distribution approach (as opposed to a deployment scenario) there is not much advantage of using an explicit Enrollment Profile anyway since we already need to visit the MyDevices page to get the Trust Profile, we might as well just use the standard MyDevices implicit Enrollment.
All devices that have enrolled themselves via a defined/explicit Enrollment Profile will be listed under that Profile in Profile Manager. Devices that have enrolled via MyDevices will not be listed under any Profile, but rather just under Devices (where *all* devices will be shown regardless of how they enrolled).
So, now the questions:
So, the idea of an Enrollment Profile makes perfect sense - it is basically the only way to create an exportable profile that can be distributed and configured to automatically enroll a device without interactive enrollment via the MyDevices page.
What I don't get is WHY is there the ability to create multiple Enrollment Profiles rather than simply providing a default exportable profile?
The reason it makes no sense to me is there is absolutely no correlation (that I can deduce) between an Enrollment Profile and the devices that used it to enroll. While I can see a (non-exportable) list of each device enrolled via each Enrollment Profile, it ends there. I can't, for instance, create Configuration Settings that I link to an Enrollment Profile. Or dynamically populate a Device Group with all devices enrolled from a specific Enrollment Profile. If I could do these things, it might make sense to me and I have spent much time looking at the interface and scouring documentation to see where the connection is. I have simply determined that there isn't one.
I can go ahead and create several Enrollment Profiles such as:
iPads
Lab Systems
Main Office Systems
High Security Systems
And I can deploy these Profiles (either via mail/file or via initial deployment) to the respective devices. I can then see under each Profile which devices enrolled. But, since I can't actually do anything to correlate those systems to a configuration, why would I want to do this segregation? Sure it gives me a listing of iPads apart from OSX machines, but I can't do anything with this listing!
Now, of course, I can still pre-stage devices and add them into particular device groups so that as soon as they are enrolled (via any Enrollment Profile) they will get the Configuration Profile(s) attached to them. This makes the inclusion of multiple Enrollment Profiles even more suspect.
Am I missing something? Can someone enlighten me as to what the purpose of creating more than one Enrollment Profile would be?
We can easily say "Well it's not hurting having them there" but, in terms of complexity and confusion I believe it is. Had they simply provided a single Enrollment Profile ("Remote Management") that was downloadable/exportable it would have been sufficient.
Thoughts?

How do I create an ACR custom lens profile if camera exposure can't be set to manual?

How do I create an ACR custom lens profile if camera exposure can't be set to manual?
I ask this question for the Nokia 808 PureView 41MP camera. It produces stunning image quality but exposure can only be controlled via EV +/- compensation. I need a lens profile to correct for vignetting to get even skies in panorama (which turn out stunningly otherwise). There is no profile for the Nokia 808 PureView I am aware of and I'd like to produce one.
Is the Adobe profile creator able to correct for varying exposure using EXIF or overlapping parts of the chart or background?
Or would the Adobe profile creator ignore EXIF if I use studio flash to enforce a constant lightning situation, even if shutter speed would vary (aperture is constant and ISO can be set constant, just not the shutter speed)?
Or did Adobe produce a profile internally they can share?
Thanks.

If you read the first post, this is the camera-app of a 41MP Nokia Pureview 808 camera-phone, so maybe someone could write a new camera app but the phone is Symbian OS which is dead, making that unlikely.
http://www.digitaltrends.com/mobile/the-skeptics-guide-to-nokias-808-pureview-five-reasons -41-megapixels-are-not-a-gimmick/
http://www.digitaltrends.com/mobile/the-nokia-lumia-820-and-lumia-920-too-little-too-late/
It would probably be easier for Adobe to rewrite the LPC to allow vignetting to be computed from a single shot of a blank wall without a target in the shot, than to have someone rewrite a camera app that allows manual exposure.
Another idea about how to get the phone to keep a constant exposure would be to experiment with putting darker and lighter objects in the field-of-view away from the target area to make the camera metering adjust things so it’s exposure is the same from one shot to the next. This would take some doing but should work, unless the LPC uses the part of the frame that doesn’t contain the checkboard target in its computations.
You’re basically varying the scene around the target so the camera takes the same exposure of the target each time.

Firefox doesn't open with profile even after creating a profile through Profile Manager.

I created a profile of Firefox yesterday using Profile Manager. And placed it in a virtual encrypted drive created by TrueCrypt. But Firefox didn't open with the profile. Instead it opened in default setting that Firefox usually gets when newly installed. I tried to select the profile through Profile Manager and open Firefox but to no avail. Even tried placing the profile in the Profile folder in Firefox pathway in AppData. Still same thing. At last reset Firefox and the profile was deleted. Now I'm with newly default setting. Luckily I had saved my bookmarks from Bookmark Manager.
I just wanted to save a profile so that only I can only access my profile and any other person would just had to use default setting. Also to restore my settings in case I install a fresh Firefox or reset Firefox to solve a problem.
Please help me fulfill my wants as stated above and why did it not work yesterday with the Profile Manager?

Hello ams963, i think the problem is with TrueCrypt because it is not support your win 8 yet. see: http://www.truecrypt.org/
http://www.truecrypt.org/docs/version-history
see if can find a method in the next link, not too useful i think for your win 8 : [http://kb.mozillazine.org/Protect_the_profiles_contents Protecting the contents of the profile]
thank you

Is there an easier/more-automated way to create user settings in Profile Manager?

I'm setting up a Mavericks Server and am setting up the settings for each user within the Profile Manager. I'm finding somewhat tedious to have to enter all of the server and account information per service per user. Seeing that it knows the details of the server it's running on – and the user for whom I'm setting up the profiles, is there no automatic way to produce a settings bundle for each user? At the very least, the server hostname and username should be prefilled.

What settings are you setting in the profiles? You can set a general setting that is available to all users, and also create various device configurations and add devices to them. I personally have not found much use for user specific profiles within profile management.

Firefox will not start. Open profile manager. Delete old profile. Create new profile. Click start firefox. Firefox starts. Close firefox. Click start, "Mozilla Firefox", FireFox DOES NOT start. Help!?

Firefox will not start.
Run profilemanager and delete old profile - create new profile - click run firefox from profile manager and firefox opens.
Close firefox and try to reopen. Will not open. Follow above procedure again and foerefox opens until closed them will not open.
== This happened ==
Every time Firefox opened
== Last week ==
== User Agent ==
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8

Thanks for your help. I had tried starting Firefox in safe-mode before I posted this request, but it did not work. I tried to restore the system to an earlier version, but that made everything worse. Two accounts were unusable and one sort of worked, so I reloaded the operating system and now firefox works, for how long, I don't know. But thanks again for your suggestion.

Profile manager (macOSX FF 3.6.8) won't create new profile or rename

Using terminal I used profile manager to successfully create a new profile (it called it Default User) and then I copied essential files like bookmarks into the new folder. FF works fine, but I can not longer create a new profile or rename the old one. In terminal the create new / rename dialogue appears, but when I try to type in a new name into the dialogue box the text does not appear in the dialogue box but appears in the terminal window. The profile folder only contains the one profile and it is correctly referenced in the .ini file.

I also have this problem and it just started in the last week or so. It seems to be dependent on my home network and the problem only exists with firefox. I have used chrome and IE8 with no issues. I can verify tomorrow that it only exists in my network but one thing I was able to test is that the problem exists even on my linux boot. I am totally dumbfounded with this problem and I can't find anything that will allow the gmail page to load. All other pages I have tried load fine, all be it a little slower than normal but they load. If anyone knows of a difference between firefox and all other browsers on how it goes through the router I would appreciate the info cause I don't know of any differences.

I need help in creating Firefox profiles directly from command line (script like) without having to use the profile manager step-by-step window

is there a way to provide command line arguments when invoking profile manager so that I can seamlessly create a profile from one invocation? Passing profile name and profile location. I have to bypass user interaction with profile manager window. Thanks.

http://developer.mozilla.org/en/docs/Command_Line_Options#User_Profile

CalDAV and Profile Manager question

I am attempting to set up CalDAV in Profile Manager for our mobile devices. I am applying these settings to a group. I can't complete configuring the CalDAV payload because Profile Manager tells me that a CalDAV username is required. Again, this profile is for a group, so each user should be entering his own username to connect to his personal calendar. I've included a screenshot below to illustrate what's happening.
Is there something I'm misunderstanding about how CalDAV needs to be configured, or is this a bug?

Hi Adams,
You can use variables keys in Profile Manager to push groups settings
(I don't know if this list is exhaustive or not)
User keys:
      email
      full_name
      guid
      short_name
      first_name
      last_name
      job_title
      mobile_phone
      uid
Device keys:
      udid
      device_type
      guid
      scep_uuid
      scep_challenge
      reg_cert
      reg_cert_uuid
      reg_challenge
      mdm_cert
      mdm_cert_uuid
      mdm_challenge
      user_id
      pending_user_id
      token
      unlock_token
      push_magic
      last_checkin_time
      Version
      Serial
      Product
      ProductName
      PhoneNumber
      DeviceName
      OSVersion
      BuildVersion
      ModelName
      Model
      SerialNumber
      DeviceCapacity
      AvailableDeviceCapacity
      IMEI
      MEID
      JailbreakDetected
      ModemFirmwareVersion
      Query
      ICCID
      BluetoothMAC
      WiFiMAC
      CurrentCarrierNetwork
      SIMCarrierNetwork
      CarrierSettingsVersion

CalDAV created as "manual download" by profile manager.

Similar Messages

Maybe you are looking for