The only way that I know of to do this is to use the automation functions of the Microsoft Exchange Migration Wizard. There are several files involved, a control file, a PKL file (Packing List) and a PRI (Primary) file. You do not need a SEC file (Secondary). Here is how these files look:
Control File: ---------------------- Mode,FILE File,c:\data\testing\mig\MadCap\TS01\Batch\00000000.PKL Mailbox,TRUE Public,FALSE ImportDestination,Server ExchStoreDN,CN=StoreA,CN=First Storage Group,CN=InformationStore,CN=CVGEXC001,CN=Servers,CN=CVG01,CN=Administrative Groups,CN=AFGExchange,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CCCinc,DC=com Container,CN=Users,DC=OU1,DC=CCCinc,DC=com PKL File: ------------------ !CodePage 1252 !HeaderLine Filename,Filetype 00000000.PRI,Primary PRI File ------------------- !Migration Type DIRECTORY !HeaderLine Obj-Class,Mode,Common-Name,Home-Server,Secondary-Proxy-Addresses MailBox,Create,gsurname,~SERVER,SMTP:[EMAIL PROTECTED] These files are some examples of the output of our Rocket product, which automatically generates these files and automates the entire migration process to Exchange. This is the piece that flips a Contact or Mail-enabled user to a Mailbox-enabled user. You'll have to read up on how these automation files work. Check out the help documentation for Microsoft Exchange server. But here it is in a nutshell. You feed the control file into the Exchange Migration Wizard via the command line. The ExchStoreDN field specifies the information store where you want to create the mailbox. The Container field can be any valid container. You will note that the control file references the PKL file. The PKL file does nothing other than reference the PRI file. The PRI file references the user's SMTP address that you want to convert to a mailbox. Viola! Believe it or not, it actually works really well. Exactly why Microsoft decided to make it this convoluted is anyone's guess. The real pain is in generating the control, PKL and PRI files necessary to perform the automation, which is why we created Rocket originally. We then matured Rocket into a full-blown migration suite. Let me know if you have any questions or issues. > Does anyone know if it is possible to migrate a windows 2000 > contact to a user? I have quite a few Active Directory > contacts (with smtp addresses) that eventually get > migrated to our exchange 2000 server as users with email > accounts. (The email address stays the same though). > However if I delete the contact and migrate the user to > the exchange server, multiple rejects begin occuring > because Outlook has cached the older conatct info and > doesn't look to the new user info when sending. I start > getting rejects galore whenever this occurs. If I could > successfully migrate a Contact to and actual User, it > would sure save some headaches. > > Thanks for your time, _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:leave-exchange@;ls.swynk.com Exchange List admin: [EMAIL PROTECTED]
