Thursday, July 21, 2011

details you may not know - Transition from Exchange 2003 to Exchange 2010

details you may not know - Transition from Exchange 2003 to Exchange 2010

If you are an IT guy of a small company ( 5 - 50 people), and need to upgrade your Exchange 2003 to Exchange 2010, this document is a very good guide:

http://msexchangegeek.com/2010/01/30/rapid-transition-guide-from-exchange-2003-to-exchange-2010/

However, this document, also almost all of online guides, did not mention some details of transition from Exchange 2003 to Exchange 2010. Maybe for an experienced Exchange Administrator, those are just common sense, but, for small company's IT guys, those might become nightmares.


Think carefully before you install Exchange 2010.

1. Moving mailboxes spend too much time, the speed is about 3G/hour. A 20 people company with 60G data in Exchange 2003 spend almost one whole day.

2. When moving begin, incoming email will stay in queue, not deliver to mailbox, until moving mailboxes has finished.

3. McAfee might delete mailbox log files, and made mailbox database dismounted. This is my biggest nightmare before I figured it out.

4. Exchange 2010 uses about 4 times more space than Exchange 2003, and, if free space too low (< 5G), exchange will stop receiving incoming emails.



Therefore, when you plan to upgrade exchange server, be very careful. Email service is essential for businesses. Do not screw it up.

Tuesday, July 19, 2011

vmware converter: Unable to clone volume 'C:'

When I used Vmware vCenter Converter Standalone 3.0.5 to dynamically converter a physical machine (Windows 2003) to VMware virtual machine.

Get error when just finish 1%:

vmware converter: Unable to clone volume 'C:'.

for vmware converter log:

[2011-06-27 17:07:18.551 04504 info 'App'] Scheduler scheduling item 4 to run at time = 2011-06-27 17:07:18.551. -- void __thiscall Converter::Server::Scheduler::SimpleScheduler::Run(void) ("d:/build/ob/bora-292238/bora/sysimage/ufad/server/scheduler/simpleScheduler.cpp:88")

[#11] [2011-06-27 17:07:18.589 04516 info 'App'] ConverterConnection: KeepAlive timer canceled, StopKeepAlive succeeded

[#11] [2011-06-27 17:07:18.591 04516 info 'vmomi.soapStub[9]'] Resetting stub adapter for server PIPE:\\.\pipe\vmware-converter-worker-soap : Closed

[2011-06-27 17:07:19.236 04496 info 'App'] Started task "task-6" for job="job-27", item ="4" -- void __thiscall Converter::Server::Job::JobProcessorImpl::StartProcessingJobs(void) ("d:/build/ob/bora-292238/bora/sysimage/lib/converter/server/job/jobProcessorImpl.cpp:351")

[2011-06-27 17:07:19.294 11848 info 'App'] [task,332] [task-6] -- BEGIN -- Convert

[2011-06-27 17:07:19.304 11848 error 'App'] Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)

[2011-06-27 17:07:19.339 11848 info 'App'] [taskSpec,464] [task-6] [TaskMap] task-6:task-4

[2011-06-27 17:15:09.105 11848 error 'App'] [task,344] [LRO] Unexpected Exception: converter.fault.CloneFault

[2011-06-27 17:15:09.108 11848 info 'App'] [task,373] [task-6] -- ERROR -- Convert: converter.fault.CloneFault

(converter.fault.CloneFault) {

dynamicType = ,

faultCause = (vmodl.MethodFault) null,

description = "converter.fault.FileIOFault",

msg = "",

}

[2011-06-27 17:15:09.108 11848 info 'App'] [diagnosticManager,260] Retrieved taskInfo for "converter.task.Task:task-6" mapping it to "converter.task.Task:task-6".

[2011-06-27 17:15:09.108 11848 info 'App'] [diagnosticManager,300] The task with id = "task-6" was found to be a "recent" task.

[2011-06-27 17:15:09.108 11848 info 'App'] [diagnosticManager,314] No existing log bundle found for task with id = "task-6". The task is still "recent" so a log bundle will now be generated for it.

[2011-06-27 17:15:09.108 11848 info 'App'] [diagnosticManager,756] Retrieving task related diagnostics for server task with id = "task-6".



Google about “Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)”, get a useful info:

http://support.microsoft.com/kb/907574
get this error is caused by VSS, not converter, or something relate to SSL.

check source machine’s event viewer: VSS error:

Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {24602736-bed9-4619-91b0-243447c6409c}. Routine details DeleteSnapshots({b4b1c18e-b85c-43d0-b6d8-86357ff4e9b1}, 2, 1, [0],[{00000000-0000-0000-0000-000000000000}]) failed [hr = 0x80004005].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

check the GUI {24602736-bed9-4619-91b0-243447c6409c} from regedit:
got the VSS provider:

StorageCraft Volume Snapshot Software Provider


This is our backup software. Looks VMware is not compatible with StorageCraft’s backup software.

Uninstall it, conversion finished successfully.

New topic for my blogs

Recently, I worked as Network administrator, and have countered some difficult problems,and even cannot find solution from Internet directly.

Therefore, I plan to post them to my blog, and wish that it will help other IT guys.

Maybe I will not write all details, or it is not very clear to you. you could post your questions, and we could work on it together.