Below are answers to some common questions about the technical deployment of Google Apps
We've seen schools carefully evaluate whether or not they'll be migrating user data to Google Apps. In many instances, we've seen schools that have opted to migrate data for faculty and staff but have decided to let students decide whether they'd like their data migrated. Another option is to send out a survey to your students, faculty, and staff and ask whether or not they'd like their data migrated. Some people will probably decide that they'd like to start with a clean slate and not migrating data can help to reduce the deployment time!
Do you have contacts that you'd like to share with your users, but the contacts are for users that are outside of your domain? If so, you can look into using Google Apps Directory Sync or the Shared Contacts API in order to add these contacts to your Google Apps account.
Single sign-on (SSO) allows users to authenticate to Google and other services that you may have (such as a portal or learning management system) with one login. With SSO passwords are kept in sync and only one login is required. Single sign-on also allows for far greater customization of the login page. It is, however, one of the more technically complex pieces of a Google Apps deployment. If you decide to implement single sign-on, you should make sure that you have a person (or more) on your project team that will be working on this part of the project. If you don't have the resources internally, we recommend contacting a Google Apps partner.
If you're receiving a message stating that your domain is already registered, it's likely that some users on your domain may have Team Edition Google Apps accounts.
Users that have existing Gmail accounts may be interested in integrating some of this data to their new Google Apps account. If this is the case, please have users reference http://www.google.com/support/a/bin/answer.py?hl=en&answer=1041297. The link contains instructions for migrating data between Google accounts.Certain Google properties, such as Google Sites, allow users to access community-created Gadgets. Some schools The Feed Server Client Tool (FSCT) allows administrators to set which gadgets may be accessed within their domain. You can read more about this at http://edutraining.googleapps.com/Training-Home/module-5-sites/chapter-3/8-4.
Some schools want to block users from changing their Google Apps passwords but aren't sure how to do it if they're not using single sign-on. To achieve this, specify a ‘Change Password URL’ in the single sign-on settings page; when users attempt to change their password, this will redirect them to the supplied URL. Make sure that you're leaving the 'Enable Single Sign-on' box at the top of the screen unchecked.