SBS 2003 and beyond » Exchange 2007

Exchange 2007 to Exchange 2010 user move errors Part 2

Roger Crawford — Tue, 23 Aug 2011 16:32:11 +0000

Ok was doing the Exchange 2007 to Exchange 2010 migration/transition whatever you want to call it and we got an error when trying to move a user and it had to do with corrupted items in the users mailbox. Which could be a piece of junk mail or who knows but it did not like it. So I increased the amount to 50 and it still failed and if you look at the details on the user move it will show how many items it stopped at unless it is over 50 which is the limit that is in the Mail Move for corrupted items unless you add the switch below and run this from the PS. So I ran the command below from Power Shell and finally got the email moved but the user had 74 items in their mailbox which was corrupted. I think the next limit is 100 with the switch below and then the fix would have been to export the email to pst and then fixed the pst if possible and import into Outlook for that user if possible.

Till later just Roger

Failed

Error:

Large BadItemLimit (50) is specified. Please confirm your intention to accept a large amount of data loss by specifying AcceptLargeDataLoss. This information will be kept in the logs with ‘d065654.local/Users/Administrator’ as the identity of the requestor.

Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.285.0&t=exchgf1&e=ms.exch.err.ExD15B33

Command to run

New-MoveRequest –identity UserName –TargetDatabase “Mailbox Database Name” -MRSServer NewExchServerName -BadItemLimit 60 -AcceptLargeDataLoss

Exchange 2007 to Exchange 2010 User move Error

Roger Crawford — Tue, 23 Aug 2011 15:48:41 +0000

I was doing an Exchange 2007 to Exchange 2010 migration and when I went to move the users I got this error below. The fix for this was Open Active Directory Users and Computers click on the view Tab and select Advanced and then find the user you are having problems with and right click on the user go to Properties and then Secuirty and then Advanced and check the box that Says “Include Inheritable Permissions from objects parent” hit apply and then ok your way out of this and then go back and move that user and away you go.

Till later just Roger

Username
Failed

Error:
Active Directory operation failed on server.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

The user has insufficient access rights.
Click here for help… http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.285.0&t=exchgf1&e=ms.exch.err.Ex6AE46B

Exchange Management Shell command attempted:
‘domain.local/Location User Groups/Location Users/username | New-MoveRequest -TargetDatabase ‘Mailbox Database name’

Elapsed Time: 00:00:04

Shadow Protect Server 4.0 and restoring Exchange mailbox Part 3

Roger Crawford — Mon, 08 Aug 2011 20:15:40 +0000

So what I did was to do the restore of the DC using the HIR option as it was a physical server and then loading the integrated components from within HyperV and on the Exchange server which was a Virtual running in HyperV already not to do the HIR and then when everything came up they all was talking and doing what they should have been in the first place. Moral of the story for this piece was if it is Physical do the HIR when restoring into a Virtual area and if it was already a Virtual not too.

Now that I had that all running I just created myself a Windows 7 machine and loaded Office on it and then connected Outlook as that user and exported out what I needed. Life was good and I know it seems like a lot of work but it wasn’t that bad and in the end everyone was happy and I now had my way of doing this down.

Til later just Roger

Shadow Protect Server 4.0 and restoring Exchange mailbox Part 2

Roger Crawford — Mon, 08 Aug 2011 19:59:18 +0000

I booted to my Windows 2008 R2 server on my laptop and then I created a couple of Guest machines within HyperV one for the main DC and one for the Exchange 2007 Server. I started the restore of the Shadow Protect backup on HyperV Server into the Virtual DC and this went well until the point of the HIR restore which if you are familiar with Shadow Protect it will load a generic driver set and 99% of the time work. I selected to do this and when the restore was complete I also fixed the MBR with the Shadow Protect tool and the server seemed to boot ok and to be opertional. Cool thought I was moving forward so I cleaned up AD and DNS and the sites or all the DCs and sites that was not there. I felt pretty good so I did my exchange server restore and when I brought up exchange there was some services hanging and exchange was not talk to the Domain Controller. Checked my networking on the Virtual Exchange server and that was good and then checked the Domain Controller out and I had multiple NICs and they would not remove when I tried to uninstall them. Looked to be the networking on the DC or Exchange was not working properly. So what to do what to do.

Till later just Roger

SBS 2003 to Exchange 2007 migration Part 5

Roger Crawford — Sat, 17 Jan 2009 06:50:41 +0000

Well the server from hell started to blue screen this week. It was a SBS 2003 server that someone had decided to treat the server as one would for a Enterprise Server and had it all messed up. This server had many issues and that was one of the reasons that this customer decided to spilt off the parts onto Full Server Servers. Last week when I had been onsite I had done a Sharepoint backup and what I could so we could remove the Exchange 2003 Server and demote this server down. Well that was not the case as the server started to Blue Screen come Monday so the onsite IT guy said no more and shut it down.

I got onsite yesterday and made sure that was what we was going to do for sure and I then went through the process of cleaning AD up from the failed DC and seized the roles over to the Main 2008 DC and cleaned AD and DNS and all those fun parts that are still there. I have the matter of cleaning the orphaned Exchaneg server out of AD so the Exchange 2007 server don’t think it is there anymore. Ya know there is really no good articles on this process and I am still trying to find that article that will help clean up the Exchange 2007 Server from the reminants of the Exchange 2003. When I get that tracked down I will let you know but for the most part looking back on this whole deal it was really simple to do other than all the problems had with the SBS 2003 Server. I did get the Sharepoint restored onto a 2003 Server running in HyperV and that went over real good as the customer had figured it was gone. Now it is getting the new ISA 2006 server in place and publishing either 2008 TS Gateway or a Terminal Server they was still kicking that one around will see where that goes for sure. Well it is off to a weekend of fun at the Great Wolf Lodge in Kansas City with all my children except for my oldest he and his son. They will be missed but the rest of us sure will be thinking of them as we will be playing in the 84 degree warm swimming area.

Til later just Roger