Posted: Tue Jul 10, 2007 5:04 pm
Hi Admin,
Sorry for the slow response. I have very busy. I have also been working on this problem. Thanks for explaining what is actually going on with this one. I do understand why you create your own profile. This list of potential problems of using the default profile is convincing.
Thanks for your suggestions on how to get around this problem. Unfortunatly this will not work for my client. I had him setup just as you suggested. I setup Outlook to archive all emails that were older than 6 months on the source machine only. I set the frequency to archive every day. I then used EZOS to sync the main PST and also the archive PST. So I had two profiles in EZOS, one for the main and one for the archive. Unfortunately this is what got me in trouble. His archive PST grew to large and blew over the 2GB limit. I should mention that Outlook gave no warning that the archive was approaching 2GB. When this happened the archive PST was corrupted and not repairable. Fortunately I sync every night so I had another copy of the archive file on his laptop which is the target machine. The targets archive was slightly under 2GB so we only lost a few messages.
That is the history and this is why i decided to split his email into 5 PST's. I have the main PST and 4 others (one for each of his email accounts). What I have noticed is that if EZOS opens the main PST first, then I can open all the other PST's without having the additional special folders created (i.e. Sent Items, Outbox). I started investigating using REGMON for Sysinternals. I found the EZOS Profile key in the registry that is created when EZOS attaches to the source and target PST's. I decided that this is the answer to my problem. If I can make sure that this registry key is present before I launch EZOS then it will not matter which PST I open becuase the special folders will not be created.
Here is my implimentation. I wrote a command script that will sync all 5 profiles. The command script will run nightly via the task scheduler. I first exported the EZOS Profile registry key into a .reg file after launching EZOS with the default Outlook profile (main PST). The command script will use regedit to load the .reg file into the registry. The script will then run a command line sync on the profile. I set this up in a loop so that for each EZOS profile that I sync, I will first load the .reg file. This works great and it keeps EZOS from creating the Sent Items and Outbox folders.
I do still have a problem with manual sync's. Since EZOS keeps track of the last EZOS profile on display, I have to make sure that I always load the default profile (main PST) before exiting EZOS. If not then the next time the program is launched, it will create the special folders for one of the other PST's.
I was wondering if perhaps you could add a switch to instruct EZOS to allways load the default profile (main PST) when running the GUI? This would solve the problem. I am certain that my client will forget to load the default EZOS profile before exiting the GUI.
I realize this reply is long and winded but I wanted to let you no what I am doing to get around this problem. Would you please give me some feedback on this stuff? The only problem that I can see is when processing the main PST from my command script. Since I am preloading the EZOS Profile registry key with the .reg file, will EZOS overwrite the keys when processing the main PST? I hope that it will in case something has changed in the main PST that will change the keys created when EZOS creates it's own profile.
Thanks for your support and I look forward to your reply...
Sorry for the slow response. I have very busy. I have also been working on this problem. Thanks for explaining what is actually going on with this one. I do understand why you create your own profile. This list of potential problems of using the default profile is convincing.
Thanks for your suggestions on how to get around this problem. Unfortunatly this will not work for my client. I had him setup just as you suggested. I setup Outlook to archive all emails that were older than 6 months on the source machine only. I set the frequency to archive every day. I then used EZOS to sync the main PST and also the archive PST. So I had two profiles in EZOS, one for the main and one for the archive. Unfortunately this is what got me in trouble. His archive PST grew to large and blew over the 2GB limit. I should mention that Outlook gave no warning that the archive was approaching 2GB. When this happened the archive PST was corrupted and not repairable. Fortunately I sync every night so I had another copy of the archive file on his laptop which is the target machine. The targets archive was slightly under 2GB so we only lost a few messages.
That is the history and this is why i decided to split his email into 5 PST's. I have the main PST and 4 others (one for each of his email accounts). What I have noticed is that if EZOS opens the main PST first, then I can open all the other PST's without having the additional special folders created (i.e. Sent Items, Outbox). I started investigating using REGMON for Sysinternals. I found the EZOS Profile key in the registry that is created when EZOS attaches to the source and target PST's. I decided that this is the answer to my problem. If I can make sure that this registry key is present before I launch EZOS then it will not matter which PST I open becuase the special folders will not be created.
Here is my implimentation. I wrote a command script that will sync all 5 profiles. The command script will run nightly via the task scheduler. I first exported the EZOS Profile registry key into a .reg file after launching EZOS with the default Outlook profile (main PST). The command script will use regedit to load the .reg file into the registry. The script will then run a command line sync on the profile. I set this up in a loop so that for each EZOS profile that I sync, I will first load the .reg file. This works great and it keeps EZOS from creating the Sent Items and Outbox folders.
I do still have a problem with manual sync's. Since EZOS keeps track of the last EZOS profile on display, I have to make sure that I always load the default profile (main PST) before exiting EZOS. If not then the next time the program is launched, it will create the special folders for one of the other PST's.
I was wondering if perhaps you could add a switch to instruct EZOS to allways load the default profile (main PST) when running the GUI? This would solve the problem. I am certain that my client will forget to load the default EZOS profile before exiting the GUI.
I realize this reply is long and winded but I wanted to let you no what I am doing to get around this problem. Would you please give me some feedback on this stuff? The only problem that I can see is when processing the main PST from my command script. Since I am preloading the EZOS Profile registry key with the .reg file, will EZOS overwrite the keys when processing the main PST? I hope that it will in case something has changed in the main PST that will change the keys created when EZOS creates it's own profile.
Thanks for your support and I look forward to your reply...