I have a scenario where I need some help... Customer is onboarding endnuser 100/200 a month and have a system for doing this. Problem is when users return/same user is rehired. This happens a lot - the system they have in place have procedure deleting the user and the recreates the same user with same id to ensure everything is deleted. This is due to security and making the mailboxes disconnected on 2007 I need a solution to address this.. I found a manual workaround I need to automate - problem is they need to be on 2010 to make it work - and migrate all terminated mailboxes (they keep them for 2 years) to 2010 if the scenario a user returns an demands the old mailbox to be available... The problem is the customer does not want everything to be deleted - they want the user to get the same mail data (and home drive and profile) if they are rehired within 2 years. They have always done this manually, but is has not been implemented by the system. So the problem is when creating a new user system delete old use and recreates a new user to remove all security. Hence the connection to Exchange is dropped and we have a disconnected mailbox My idea is to search for old mailbox for the same user and import old mail data to the new mailbox (maybe delete old mailbox)?? This run once a day. According to them they have a lot of these so manually doing this is not an option I found a solutions doing it Get-MailboxDatabase | Clean-MailboxDatabase Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} | ft displayname,database,disconnectreason -auto New-MailboxRestoreRequest -SourceDatabase "mbxdb01 (EXCHMBX50)" -SourceStoreMailbox "10e69160-827-4c3d-921b-992juy854b59" -TargetMailbox "kiada" -AllowLegacyDNMismatch Get-MailboxRestoreRequest mbxdb01 (EXCHMBX50) location 10e69160-827-4c3d-921b-992juy854b59 is old account (disconnected) kiada new mailbox Any others idears

Hi Christian, For questions on scripts, it is reconmended to post in Exchange Development forum. Your understanding would be appreciated. Fiona Liao TechNet Community Support

Hi Christian, For questions on scripts, it is reconmended to post in Exchange Development forum. Your understanding would be appreciated. Fiona Liao TechNet Community Support

Tried... Can you move? This is 2nd time :(

On Tue, 29 Jan 2013 12:58:24 +0000, Christian Dinesen wrote: > > >I have a scenario where I need some help... > >Customer is onboarding endnuser 100/200 a month and have a system for doing this. > >Problem is when users return/same user is rehired. This happens a lot - the system they have in place have procedure deleting the user and the recreates the same user with same id to ensure everything is deleted. This is due to security and making the mailboxes disconnected on 2007 > >I need a solution to address this.. > >I found a manual workaround I need to automate - problem is they need to be on 2010 to make it work - and migrate all terminated mailboxes (they keep them for 2 years) to 2010 if the scenario a user returns an demands the old mailbox to be available... > >The problem is the customer does not want everything to be deleted - they want the user to get the same mail data (and home drive and profile) if they are rehired within 2 years. They have always done this manually, but is has not been implemented by the system. > >So the problem is when creating a new user system delete old use and recreates a new user to remove all security. Hence the connection to Exchange is dropped and we have a disconnected mailbox > >My idea is to search for old mailbox for the same user and import old mail data to the new mailbox (maybe delete old mailbox)?? > >This run once a day. > >According to them they have a lot of these so manually doing this is not an option I found a solutions doing it > >Get-MailboxDatabase | Clean-MailboxDatabase Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} | ft displayname,database,disconnectreason -auto New-MailboxRestoreRequest -SourceDatabase "mbxdb01 (EXCHMBX50)" -SourceStoreMailbox "10e69160-827-4c3d-921b-992juy854b59" -TargetMailbox "kiada" -AllowLegacyDNMismatch Get-MailboxRestoreRequest > >mbxdb01 (EXCHMBX50) location 10e69160-827-4c3d-921b-992juy854b59 is old account (disconnected) kiada new mailbox > > > >Any others idears Why not just use the connect-mailbox cmdlet to attach the disconnected mailbox to the new AD User account? There's no need for Exchange 2010 to do that. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Because this hapsens many times and its a manuel task - I wanted to automate

But why not simply connect the disconnected mailbox to the "new" users Active Directory user account? Why create a brand new (empty) mailbox when the objective is to move all the old mail over (if needed)? Even then, you have to write a complex script. * It seems like you'd have to... hmmmm - Search the Active Directory database for users (new users) that do not have a mailbox. ---> Challenge here is that all new users are not necessarily former employees with an old mailbox. - Search disconnected mailboxes for a name (?) matching that of the new user. You'd have to find something that allows the two to be linked. - Connect the disconnected mailbox with same name to that "new" user.Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Problem is the solutions managing users is doing it..

On Tue, 26 Feb 2013 13:18:31 +0000, Christian Dinesen wrote: >Because this hapsens many times and its a manuel task - I wanted to automate If you already have the disconnected mailbox's GUID and you know the AD user to which the mailbox should be connected then the script should be pretty easy to create. Just prepare a small CSV file with a column for the user,one for the mailbox database, and another for the mailbox GUID. Import the CSV file and parameterize the connect-mailbox within a foreach loop. Something like this: import-csv |foreach{connect-mailbox -identity <GUID> -Database <DATABASE> -User <USER>} There's no need to use Exchange 2010, and there's no reason to create an additional mailbox only to move the contents into it from a disconnected mailbox. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Mon, 4 Mar 2013 09:49:45 +0000, Christian Dinesen wrote: >We don't know the GUID, but can find it :) problem is this happing without the Exchange team is notified. > >Senario > >User get hired Jan 15. 2010 - Has mail and is a happy camper > >Users gets termnated April 1. 2012 - Mail and users stays untouch So the mailbox was never disabled? >Users gets "re-hired" Jan 1. 2013 - a new users and new mailbox is created - users is unhappy - no of the old mail is present The first thing that comes to mind is that your "on-boarding" process is in need of attention. How does anyone know that the user is a "re-hire" to begin with? And, if they do know, why are they creating a new user? --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

We don't know the GUID, but can find it :) problem is this happing without the Exchange team is notified. Senario User get hired Jan 15. 2010 - Has mail and is a happy camper Users gets termnated April 1. 2012 - Mail and users stays untouch Users gets "re-hired" Jan 1. 2013 - a new users and new mailbox is created - users is unhappy - no of the old mail is present