Archive for category: Knowledge base

When trying to move a mailbox from one Exchange server 2008/2010/2013 to another or from Database to another you get the error message below.  Fixing it is easy if you have used ASDIEdit before.  Basically you are going to reset the Exchange Mailbox Move Values…

Sample Error:

Data migrated:
Migration rate:
Error: MigrationTransientException: Failed to communicate with the mailbox database. –> Failed to communicate with the mailbox database. –> MapiExceptionLogonFailed: Unable to open message store. ‎(hr=0x80040111, ec=-2147221231)‎

Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=132] Lid: 43559 EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=272][latency=0] Lid: 52176 ClientVersion: 15.0.1395.10 Lid: 50032 ServerVersion: 14.3.442.0 Lid: 23226 — ROP Parse Start — Lid: 27962 ROP: ropLogon [254] Lid: 17082 ROP Error: 0x80040111 Lid: 26937 Lid: 21921 StoreEc: 0x80040111 Lid: 27962 ROP: ropExtendedError [250] Lid: 1494 —- Remote Context Beg —- Lid: 26426 ROP: ropLogon [254] Lid: 44215 Lid: 60049 StoreEc: 0x8004010F Lid: 49469 Lid: 65341 StoreEc: 0x8004010F Lid: 56125 Lid: 47933 StoreEc: 0x8004010F Lid: 32829 Lid: 49213 StoreEc: 0x8004010F Lid: 48573 Lid: 64957 StoreEc: 0x8004010F Lid: 59409 Lid: 45073 Lid: 11173 StoreEc: 0x80040111 Lid: 22970 Lid: 8620 StoreEc: 0x80040111 Lid: 1750 —- Remote Context End —- Lid: 26849 Lid: 21817 ROP Failure: 0x80040111 Lid: 26297 Lid: 16585 StoreEc: 0x80040111 Lid: 32441 Lid: 1706 StoreEc: 0x80040111 Lid: 24761 Lid: 20665 StoreEc: 0x80040111 Lid: 25785 Lid: 29881 StoreEc: 0x80040111
Report: User@domain.com Download the report for this userLast successful sync date:

Status:Queued duration:
In-progress duration:
Synced duration:
Stalled duration:

 

Resolution:

Launch ADSI.MSC

Once launch, right click on ADSI Edit on the left pane and choose “Connect to” and when the “Connection Settings” open , CLick OK which will open the default naming context.

On the left double-click on default naming context and that should start drilling down on sub items that (otherwise would have stayed hidden).  Double click on the domain.  You should see OUs structure like AD.

Find the user.  Right click and choose Properties

Under Attribute Editor click on Filter and check off option to Show only attributes that have values (this way you filter out empty fields.)

Find all msExchangeMailboxMoveXXXXXXX values and reset them to blank.  In my case I had:

msExchangeMailboxMoveFlags
msExchangeMailboxMoveStatus
msExchangeMailboxMoveTargetMDBLink

To reset them to blank, you can’t just remove the values, you should highlight the value and click Edit and then Clear.  I would write down what those values are before clearing them (I don’t believe you need them going forward but why not recording them).

Click OK then try moving that mailbox again.

There are two traditional ways to move physical machines to Hyper-V virtual machine using Microsoft Tools.

1- Microsoft Virtual Machine Converter

When you try to convert a Windows server 2012 for example from physical to a VM, you might get the following error:

Microsoft Virtual machine Converter encountered an error while attempting to convert the virtual machine

There are blocking issues for the physical-to-virtual conversion, there is no BCD boot device found in the source machine, noticing that conversion of an EFI boot machine is currently not supported.

2- Disk2VHD

Another tool is Disk to VHD and if you try to convert the physical machine using Disk2VHD tool, then try to boot the VHD disk in Hyper-V manager you get the following error in Hyper-V Manager:

Boot Failed.  EFI SCSI Device

Boot Failed.  EFI Network

No Operating System was loaded.  Press a key to retry boot sequence

 

Solution:

Use Disk2VHD to convert the physical machine to a disk.  Before you do that map the boot partition on the source machine to a drive so when you run the Disk2VHD that partition will get captured.

To do that, go to command line and type:

mountvol V: /S

That will mount the boot partition to a drive called V: drive (you could choose any other available drive if you want).  Now run Disk2VHD.  That will convert the server’s partitions and disks including the boot to VHD.  Copy to the Hyper-V machine and boot the new VM with that disk.

 

If you are running a Windows Server 2016 standard 180 days evolution copy that you downloaded off Microsoft Website and try to activate the installation with a product key that you purchased for Microsoft Server 2016, you might get an error message saying that it can’t activate, or that you entered a product key that can’t be used to activate Windows with error 0xc004f050, here how you can activate it.

Go to Command Line and type:

Dism /online /Set-Edition:ServerStandard /AcceptEula /ProductKey:xxxxx-xxxxx-xxxxx-xxxx-xxxxx

Where xxxxx-xxxxx-xxxxx-xxxx-xxxxx is the product key you purchased

Press Enter.

Process might get stuck at 10% for a little while, give it time. After it is done, you will be asked to reboot. Windows will be all good and permanently activated after it comes back up.

Can’t remote desktop into a Windows 7 – RDP

Run registry editor, regedit, and make sure PortNumber under

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-TCP

is 3389 in Decimal