Hey Everyone,

I have an interesting scenario, which I hope you can help me with.

I have a mailbox with over 6K worth of mail. I would like to export it into a multiple .PST files, each containing only a 1000 emails. So, basically script would run and once it reaches 1000 emails, it would create a new .PST, until the export criteria is reached.  

I looked around but was not able to get a definitive answer; could be because of my search conditions.

Please let me know if something like this is possible and how would I alter this script: 

New-MailboxExportRequest -Mailbox Journal-2011 -FilePath \\vm-exg-01\d\PST\old_Journal_2011.pst (for example)

Thanks in advance for everyone's respond.

• Moved by Jason Johnston [MSFT]Microsoft employee 17 hours 7 minutes ago Not a development question.

You can probably do this via EWS https://msdn.microsoft.com/en-us/library/office/dd877012%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396

Thanks for a quick respond; I would not utilize these tools in any other way though, so I would have to look for alternative means.

Thank.

So we make a tool that can slice and dice the data in many ways, alas we have not added to option to export via item count.   That said perhaps this would be a good future feature, however what is the reason you want to limit the PST by item count?

We have a mailbox that archives to the MXLogic once it reaches 1000 mark. That being said, we have a large .pst file with over 16K items. MX Logic will not accept anything over 1000 so I wanted to break it down and do an import gradually. 

Thanks for the explanation, I will ask my team about this to see how hard it would be to accomplish

Thanks a lot Troy; I appreciate your help. 

My pleasure and will let you know when I hear back from them.

I spoke with my team and we have added this to be implemented within a future build this year. 

It doesn't look like a hard feature to implement, however its estimated that it would take 3-4 days to implement into the product. 

Since this is the only request we've had for the functionality it would be low priority.  Only way to get it done faster would be to sponsor the feature aka pay $$ for the implementation.   What I would suggest is to register on our website so that when the feature comes out you will be notified. 

Thanks Troy; this is not a rush, by any means. I do once again thank you for your research. Please let me know where I can register for this roll-out notification. 

• Marked as answer by viruss Impaler 12 hours 32 minutes ago
• Unmarked as answer by viruss Impaler 12 hours 32 minutes ago

ok great so just register here http://www.lucid8.com/download/CreateAccount.aspx?ref=support and select that you are interested in DigiScope.  After you submit you will be taken to a page that will allow you to enter comments/questions so enter in a statement about this feature and that you were talking to me about it.

Upon completion your be in our system to get notified of all new releases. 

• Version 6.0 is the current release in QA and we expect it to be out in the next few weeks. 
• I will try to see if the team can then get this into version 6.1

Hey a couple more questions;

1. Is this an ongoing need or a short term, one time event you need to accomplish?

2. How many databases are involved?

The reason I ask is that I might be able to squeeze this into 6.0 before it ships.  No promises but if dev finishes the last of the 6.0 items and we have time it might be doable, however it would help to know the possible revenue opportunity as well so we could determine how much of the development it would offset.

Thanks

1. This is a short term thing. Probably will only use once or twice, during the initial migration. But will probably use for other MX Logic migrations.

2. a single Database, at this client. 

Thanks. 

Thanks that helps and over what contiguous time frame do you think you would use the functionality at this particular clients, i.e.  couple days, weeks, 3, 6, 9 months etc?

This client probably a week or two, just to make sure all works well. 
Other clients, depends on the database size and users.