Comment 1 for bug 800760

So looking at the current sources those are some notes

* bin/ubiquity-dm

you should lock down gsettings keys as well there

* d-i/source/migration-assistant/evolution-import.c doesn't need migrating, evolution 3.0 still use gconf, the gsettings migration might happen for 3.2 but it's not sure, I will update the bug if it becomes likely

* d-i/source/migration-assistant/windows-import.c

the current oneiric version is using gconf but git is using gsettings so that will likely need work before oneiric

* d-i/source/user-setup/user-setup-apply

libgksu is still using gconf by that might change before oneiric

* scripts/plugininstall.py:

not sure what the key used there do but you should check if there is an equivalent still

* ubiquity/components/apt_setup.py

the proxy values are in gsettings, org.gnome.system.proxy.http nowadays

* ubiquity/frontend/gtk_ui.py

the indicator-session keys will migrate to gsettings in oneiric

nautilus migrated to gsettings and the automount feature move to gnome-settings-daemon, you want to tweak the gsettings in
org.gnome.nautilus.desktop and org.gnome.settings-daemon.plugins.automount

you should lock down gsettings keys as well there

* ubiquity/misc.py
the keyboard layouts are in desktop.gnome.periphericals.keyboard.kbd layouts