Calendar Server 1.x to 3.x Migration

Question

I need to migrate my Calendar Server 1.x to Calendar Server 3.5.
How do I export my calendar user information?
<P>
Use CTDB2LDIF.This information is available in the Calendar Server
3.5 ReadMe.
<P>
SYNTAX
ctdb2ldif -n node-ID [ -host hostname ] [ -p sysOpPwd ] [ -f filter ]
[ -dnsuffix dn ]
ctdb2ldif -v
ctdb2ldif -h
DESCRIPTION
The ctdb2ldif script exports the database of a specific Calendar node
into an LDIF file which describes a series of modifications in the form
of change records. This utility can be used to add new entries or to
modify existing entries in a pre-populated directory server, or to
populate a new directory server.
The created LDIF file can be used by the ldapmodify utility to apply
the entry modification information to the directory server.
ctdb2ldif outputs two files, node.ldif and
undo.ldif.
OPTIONS
-n
node-ID
Node-ID of the node to export.
-host
hostname
Specifies the host on which the database for the specified Node-ID can
be found. The default is localhost.
-p
sysOpPwd
Specifies the password of the node's SYSOP.
-dnsuffix
Specifies a suffix string to be used when creating distinguished names
for directory entries.
-f
filter
Specifies the calendar item to export. The filter has the following
format: "key=value/.../key=value" where key is one of the key listed
below (uppercase and lowercase both accepted) and value is a string
that can contain wild cards (*).
Key
Directory Fields
S
Surname
G
Given name
I
Initials
Q
Generation qualifier
OU1
Organizational Unit 1
OU2
Organizational Unit 2
OU3
Organizational Unit 3
OU4
Organizational Unit 4
O
Organization
C
Country
A
Administration domain
P
Private Domain
EMPL-ID
Employee number
-v
Prints the current version.
-h
Prints a usage message explaining how to run ctdb2ldif.
EXAMPLES
1.The following command:
ctdb2ldif -n 10000 -dnsuffix "o=Airius.com"
exports the database of the calendar node 10000 on localhost using an alternate distinguished name suffix instead of the basedn specified in
/users/unison/misc/ctdb2ldif.ini into an LDIF file.
2.The following command:
ctdb2ldif -n 10000 -dnsuffix "o=Airius.com"
exports the database of the calendar node 10000 on localhost using an alternate distinguished name suffix instead of the base dn specified in
/users/unison/misc/ctdb2ldif.ini into an LDIF file.
FILES
/users/unison/misc/ctdb2ldif.ini
[CTDB2LDIF]
NOTE: A "#" as the first character in a line is used to indicate that this line is a comment and should be ignored when ctdb2ldif is run.
ldifdir =
Specifies the output directory for LDIF files. The default directory is /users/unison/tmp.
userfilterfmt = "(&(givenName=%gn)(surName=%sn))"
Specifies the LDAP search filter format to be used to match existing entries.
Supported format codes are :
%sn
SurName
%gn
GivenName
%in
Initials
%ge
Generation
%u1
OrgUnit1
%u2
OrgUnit2
%u3
OrgUnit3
%u4
OrgUnit4
%co
Country
%d1
AdminDomain
%d2
PrivmDomain
%ad
Address
%en
EmployeeNo
%ph
Phone
%fa
Fax
%ex
Extension
%jt
JobTitle
%re
ResourceName
%rn
ResourceNo
%ca
Capacity
%no
Node-ID
%id
ItemId
[LDAP,v2,NSCP,1]
host =
Specifies the host on which the LDAP directory server is running.
The default host is localhost.
port =
Specifies an alternate TCP/IP port on which the LDAP directory server
is listening. The default port is 389.
basedn =
Specifies the starting point for search operations on the Directory
Information Tree. The default is "o=Airius.com".
binddn =
Specifies the distinguished name used to bind to the LDAP directory
server. The default is "cn=Directory Manager".
NOTE: If this LDAP directory server is 1.03, this binddn must also
include the basedn. For example, the binddn should be changed to
something like "cn=Directory
Manager,o=Airius.com".
bindpwd =
Specifies the password used to bind to the LDAP directory server.
The default is secret99.
admin =
Used in conjunction with the basedn to specify the location of Calendar
administrators in the Directory Information Tree. The default value is
"ou=Netscape Servers".
admingroup =
Used in conjunction with the basedn to specify the location of Calendar
administrators in the Directory Information Tree. The default value
is "cn=Netscape Calendar Server Administrators,ou=Netscape Servers"
defaultpwd =
Default user Password to use for entries without a password. The
default password is "sesame".
/users/unison/log/ctdb2ldif.log
A log file of all related errors and warnings.
/users/unison/tmp/node.ldif
/users/unison/tmp/undo.ldif
LDIF files describing a series of modifications in the form of change
records.
/bin/slapd/server/ldapmodify
A shell-accessible interface to the ldap_modify(3) and ldap_add(3)
library calls.
WARNINGS
Items with an empty SurName are exported with the "CalUser:
" (eg. "CalUser 10000:00256") value as directory entries with
the inetOrgPerson object class are required to have a surname.
Only the first eight characters of the original passwords are used to
construct the encrypted value of the userPassword attribute; the rest
are ignored.
RETURN VALUES
Exit values are:
0 Success
1 Failure
2 Usage error
3 User interrupt

Answer 1

Hi,
You are very welcome.
You can always migrate from ADFS 1.x to ADFS 2.0, we cannot upgrade from ADFS 2.0 to 3.0 though.
Since we are not very familiar about ADFS, so the experts in ADFS forum as I mentioned above will provide more efficient support to you.
More information for you:
Migrating from AD FS 1.x to AD FS 2.0
http://technet.microsoft.com/en-us/library/ff678035(v=WS.10).aspx
ADFS 2.0 compatibility with ADFS 3.0
http://social.technet.microsoft.com/Forums/windowsserver/en-US/45b579ca-ba3b-49e6-8cbd-285516de6cc3/adfs-20-compatibility-with-adfs-30?forum=winserverDS
Have a nice day!              
Amy