How to setup Openwindows Calendar Manager in a distributed environment?
Sun’s original assumption that each user has a permanent machine allocated to them is not applicable in most environments. Just as users send mail to ‘user’ rather than ‘user@machine’, users want to browse others user’s calendars and do not care or want to know where the calendar is actually stored. Here is procedure to accomplish our goal. All calendars will be stored on a central server. The initial setup must be done on the server. A) Have the user login to the calendar host(calhost) machine. B) Change everyone’s .cm.rc file so that Calendar.DefaultCal points to user@calhost calhost can be an hostname alias or an actual hostname. You may want to use the alias just in case you change the “calhost” later. C) Change their Access List and Permissions (under Edit/Properties) to show user@client with BID (browse, insert, delete) permissions for any client machine the user wanted to access their calendar from. Notes: If you use the scheme you should not NFS mount /var/spool/calendar on the
Related Questions
- How do I configure Setup Manager to build configuration sets that use a user name and password that is different from the user name and password that I used when I first installed the OPK?
- How do I setup ModMaster to run in a Citrix or Terminal Server environment?
- How to setup Openwindows Calendar Manager in a distributed environment?
