jeetu@FVC-Jeetu /usr/local/libexec
$ ./slapd.exe
jeetu@FVC-Jeetu /usr/local/libexec
$ ldapsearch -x -b '' -s base '(objectclass=*)' namingContexts
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: namingContexts
#
#
dn:
namingContexts: dc=jeetualex,dc=info
# search result
search: 2
result: 0 Success
# numResponses: 2
# numEntries: 1
jeetu@FVC-Jeetu /usr/local/libexec
$ cat > jeetu.ldiff
jeetu@FVC-Jeetu /usr/local/libexec
$ cat > jeetu.ldif
dn: dc=jeetualex,dc=info
objectclass: dcObject
objectclass: organization
o: fvc
dc: jeetualex
dn: cn=Manager,dc=jeetualex,dc=info
objectclass: organizationalRole
cn: Manager
[1]+ Stopped cat > jeetu.ldif
jeetu@FVC-Jeetu /usr/local/libexec
$ ls -l
total 1601
-rw-r--r-- 1 jeetu Domain Users 174 Dec 27 20:27 jeetu.ldif
-rw-r--r-- 1 jeetu Domain Users 0 Dec 27 20:27 jeetu.ldiff
-rwxr-xr-x 1 jeetu Domain Users 1578510 Dec 27 18:16 slapd.exe
jeetu@FVC-Jeetu /usr/local/libexec
$ rm jeetu.ldiff
jeetu@FVC-Jeetu /usr/local/libexec
$ ls -l
total 1601
-rw-r--r-- 1 jeetu Domain Users 174 Dec 27 20:27 jeetu.ldif
-rwxr-xr-x 1 jeetu Domain Users 1578510 Dec 27 18:16 slapd.exe
jeetu@FVC-Jeetu /usr/local/libexec
$ vi jeetu.ldif
jeetu@FVC-Jeetu /usr/local/libexec
$ ldapadd -x -D "cn=Manager,dc=jeetualex,dc=info" -W -f jeetu.ldif
Enter LDAP Password:
adding new entry "dc=jeetualex,dc=info"
adding new entry "cn=Manager,dc=jeetualex,dc=info"
jeetu@FVC-Jeetu /usr/local/libexec
$ ldapsearch -x -b 'dc=example,dc=com' '(objectclass=*)'
# extended LDIF
#
# LDAPv3
# base <dc=example,dc=com> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#
# search result
search: 2
result: 32 No such object
# numResponses: 1
jeetu@FVC-Jeetu /usr/local/libexec
$ ldapsearch -x -b 'dc=jeetualex,dc=info' '(objectclass=*)'
# extended LDIF
#
# LDAPv3
# base <dc=jeetualex,dc=info> with scope subtree
# filter: (objectclass=*)
# requesting: ALL
#
# jeetualex.info
dn: dc=jeetualex,dc=info
objectClass: dcObject
objectClass: organization
o: fvc
dc: jeetualex
# Manager, jeetualex.info
dn: cn=Manager,dc=jeetualex,dc=info
objectClass: organizationalRole
cn: Manager
# search result
search: 2
result: 0 Success
# numResponses: 3
# numEntries: 2
jeetu@FVC-Jeetu /usr/local/libexec
$
Tuesday, December 27, 2011
OpenLDAP testing on Cygwin
Monday, December 26, 2011
LDAP Server sync to Google Apps
These are the requirements:
- Google Apps for Business/Education/Government
- Google Apps Admin Account login/OAuth Credentials
- Provisioning API enabled
- Server 5 GB (debug mode), 1 GB RAM for 10000 users or 2 GB for more users
- READ and EXECUTE access to the ou structure on LDAP server
- Network access to Google Apps Server via, HTTPS
- Mail server that accepts relay notifications from the tool
User provisioning in Google Apps
Create manually – 1-10 users
Bulk upload – 10 – 100 isers
LDAP Directory Sync – 100 above users also sync the contact, group and global address list, profiles
Provisioning API – 3rd party tools
Creating users in Google Apps
Check the video here.
If you have multiple domains associated with your Google Apps account, the field to the right of the @ sign is a drop-down list with the available domains. The domain you select will be the portion of the user's email address that appears after the @ sign.
Click Email instructions or Print instructions to deliver the account information to the new user.
It can take up to 24 hours for new user accounts to appear in the searchable Directory.
Methods for domain verification for Google Apps
You must verify your domain before you can use Gmail or any of your other new services.
- Create a TXT record - Up to 48 hours
- Upload an HTML file - An hour
- Add a <meta> tag to your home page - An hour
- Verify using your Google Analytics tracking code - within 24 hours
If you signed up for Google Apps, you must verify domain ownership within 14 days. For Google Apps for Business or Education, you have 21 days. If you don't verify ownership within this timeframe, we'll remove your domain and data from our system. If you want to use Google Apps in the future, just sign your domain up, again. Google Apps for Business, you can contact our Support team for help with other verification or setup tasks.
See this link for more information
Google Apps for Medium Size Business
This can be done in 4 phases in 30 days
Week 1
- Set up organization's Google Apps account
- Set up mail routing
- Determine mobile strategy
- Tell users about the transition
- Start provisioning users
Week 2
- Finish provisioning users
- Start migrating email and other data
- Plan Helpdesk operations
- Announce go-live date
Week 3
- Finalize mail routing/go live
- Configure mobile devices
- Run Helpdesk
Week 4
- Run Helpdesk
- Configure mobile devices
- Complete any remaining tasks
See this for more information
Check the change management activities and timeline template here
Check the Technical Transition Guide here
Google Apps Deployment for Small Business
- Verify your domain – use a txt record or html file upload on your DNS hosting server
- Add users – bulk upload using CSV, optionally you can use Sherpa Tools to manage your shared contacts.
- Activate email – replace the current MX records with the new Google MX records. See Figure 1.0 below.
- Set up mobile devices – Install the device policy app from market in android and give the credentials for syncing. See Figure 1.1 below. Also see this link for more details on blackberry configuration
- Migrate data - Migrate your current pst data using google tools for migration. Also see this link.
- Sync email with other clients - use google tools to sync your data with google apps. Also see the google apps sync for ms outlook and IMAP configuration
The Setup Wizard will guide you through the entire setup process. Using the wizard, most customers can set up Google Apps in under an hour.
click here for more details
Figure 1.0 – shows where you can get your mx records in the admin dashboard
Figure 1.1 – shows where you can manage your mobile devices after syncing
See this video for a better picture
Check the Transition Guide here