How to Convert Physical Computers to Virtual Machines (Microsoft Hyper-V)

It's Time to learn Virtualization World of IT. There are several ways to do, but the recommended option as inform bellow. Why I'm explaining now is because never to late to learn even though there are many ways to do it in the Internet now when you search, I'm just explaining from my perspective. Hope Clears you out. Cheers.

1. Physical conversion to Virtualization using using the Microsoft ways.
   
   Before we begin, there are different ways converting physical to virtual, one most suitable option to do this is called Disk2VHD and yes is free from Microsoft. You can download from here and doesn't require installation meaning is portable version.
2. After download completed, Run Disk2VHD from the physical server you are converting.
   
   Note : If your are planning to run Hyper-V on Windows 2008 R2 based, remove "Use Vhdx" check option, otherwise it will not work. The use of vhdx option can only be used above Windows 2012 or Windows 8. It means that Hyper-V Windows 2008 cannot recognize converted virtual Hard drive with extension *.vhdx
   
   
   
3. When Finish converting the process. you will get a file name with extension *.vhd or *.vhdx (again please note above) where you save the file.
4. Create a new VM on a Hyper-V host, the whole process just followed default option.
   
   
   
   
   NOTE: Choose your VM generation carefully. Starting with Windows 2012 R2, Hyper-V has a new option: Generation 2 virtual machine. This is a second generation firmware for VMs with a revised set of virtual hardware and new opportunities for users, such as a boot from an SCSI device. There will be more to come on this topic in future releases. Among noticeable limitations of Generation 2 VMs, is that there is no support for a guest OS older than Windows 8, not to mention Unix-like. Practically speaking, choose this only for Windows 8/8.1 or Windows Server 2012/2012 R2 and only for 64-bit builds.
5. When you finish,Right-Click on a VM, Select RUN, then Right-Click again, Select CONNECT.
   
   
   
   
6. It will take some time for the VM to boot up since the hardware configuration will be different. However, in a few minutes you’ll see the welcome screen and be ready to log in to the system. Congratulations!

421 4.4.2 Connection dropped due to SocketError in Exchange 2010 mail queue

In the Following weeks, I've been troubleshooting issue with Email queue with information shown bellow

"When send some emails to specific domain email address, emails we're stucked in mail queue with error 421 4.4.2 Connection dropped due to SocketError"

There are several issue and method to resolve but one particularly notice me that there are same procedure to process. This is because the receiving server has requested TLS so your exchange tries to start TLS but somehow has fails and the message is sent without TLS with the normal procedure even though you have disabled TLS this does not stop the receiving server from requesting TLS

You can correct these setting by following procedure bellow:

• Open Exchange Management Shell and type
  
  "Get-SendConnector | FL"
  
  
• Type command
  
  "Set-SendConnector -Identity “Name of Send Connector” -IgnoreStartTLS: $TRUE"
  
  
• After issuing this command, restart the MS Exchange Transport Service

That's it, check your email for any queue left with error specific

PS: If you want to enable TLS just set the IgnoreSTARTTLS parameter to False again.

Exchange ActiveSync Returned an HTTP 500 Error

Today, I Experienced problem with one mobile user connected to Exchange 2010 using Android device or Any mobile device cannot automatically sync inbox but can send email. Using alternative method (Exchange, IMAP & POP) of sync email as well as install Android 3rd party application synchronize inbox email with no luck. After searching the whole information on the internet found the issue when test connection using Microsoft tools ( Microsoft Remote Connectivity Analyzer ) and reported error "Exchange Active Sync returned an HTTP 500 Error" especially when "Testing of the GetEstimate command failed" in the test step information.

When I checked logs in the server email and found:

Event ID : 1008

"An exception occurred and was handled by Exchange ActiveSync. This may have been caused by an outdated or corrupted Exchange ActiveSync device partnership. This can occur if a user tries to modify the same item from multiple computers. If this is the case, Exchange ActiveSync will re-create the partnership with the device. Items will be updated at the next synchronization."

Active Sync Exception 
"--- Exception start ---
Exception type: Microsoft.Exchange.Data.Storage.ObjectNotFoundException
Exception message: ICS synchronization failed.
Exception level: 0
Exception stack trace:    at Microsoft.Exchange.Data.Storage.MailboxSyncProvider.CatchUpIcsState(MailboxSyncWatermark currentWatermark)
   at Microsoft.Exchange.Data.Storage.MailboxSyncProvider.GetMaxItemWatermark(ISyncWatermark currentWatermark)
   at Microsoft.Exchange.Data.Storage.FolderSync.EnumerateServerOperations(Int32 windowSize)
   at Microsoft.Exchange.AirSync.SyncCollection.GetServerChanges(UInt32 maxWindowSize, Boolean enumerateAllOperations)
   at Microsoft.Exchange.AirSync.SyncCommand.SyncTheCollection(SyncCollection collection, Boolean createSubscription, Boolean tryNullSync)
   at Microsoft.Exchange.AirSync.SyncCommand.OnExecute()
   at Microsoft.Exchange.AirSync.SyncCommand.ExecuteCommand()
   at Microsoft.Exchange.AirSync.Command.WorkerThread()
Inner exception follows below:
Exception type: Microsoft.Mapi.MapiExceptionNotFound
Exception message: MapiExceptionNotFound: Unable to synchronize manifest. (hr=0x8004010f, ec=-2147221233)"



There are found links & several information related to that issue, you can find easy information to read but the problem still exist.
Exchange ActiveSync Returned an HTTP 500 Error
How to troubleshoot server ActiveSync HTTP error codes

After weeks of searching and finding, finally the problem has been resolved. Found out that the problem is with the mailbox  corrupt related to Exchange Active Sync connection. Next step is to process the repair in the Exchange PowerShell server email by typing command bellow:

"New-MailboxRepairRequest -Mailbox user@domain.com -CorruptionType SearchFolder, AggregateCounts, ProvisionedFolder, FolderView"

Mailbox Repair in Exchange 2010/2013

When you finished process repair, apply to reconnecting the active sync using mobile devices again, and testing Tools ( Microsoft Remote Connectivity Analyzer ) and now user was able to synchronizing email Inbox and errors disappeared.

Conclusion:

One can easily fix the Exchange Active Sync HTTP 500 Error once the root cause is estimated. The above mentioned section elaborates different probable causes of the sync issues and also explains about different methods to troubleshoot it. But it is highly recommended to perform these work-around methods carefully as any blunder in settings can cause more frantic situations.