We have a working OSD environment with x86. So basically the Windows 7 x86 WinPE x86. We are moving to Windows x64, I imported the x64 image and created a package for Windows x64. My question is what do I do with WinPe do I need x64 WinPE. We have MDT 2010 integrated with SCCM do I need to generate new x64 WinPE, if so does anyone have any suggestion on how to do that.

Thanks

You can use a x86 boot image to deploy x64 OS

http://www.systemcentercentral.com/sccm-osd-when-to-use-an-x86-or-x64-boot-image/

as Paul explained, you are able to use a x86 boot image to deploy an x64 image, however, you cannot do a build and capture task using a OS installer.

Important
The boot image you specify must match the chip architecture installed on the target computer and the chip architecture specified in the operating system install package or the task sequence will fail.

source:

http://technet.microsoft.com/en-us/library/bb633062.aspx

Can you explain what you mean by cannot do build and capture using OS installer

Can you explain what you mean by cannot do build and capture using OS installer

I think @ismaelortiz101 is phrasing it somewhat loosely.
In CM07, there are two types of OS "package": http://technet.microsoft.com/en-us/library/bb680950.aspx

In CM12, the same things also exist, but, have slightly different names, and, are usually used differently due to the implications of Windows8 and the WADK.

The "OS installer" is typically used when dealing with legacy OS such as WinXP (which does not use WIM as part of the native setup routine).

[I note that this might not actually serve to explain things well, since it is a rather twisted concept which MS have given us to work with here.... :S]

I am not using OS installer. I do need to do build and capture will I be able to use x86 winpe to do build and capture on Win 6 x64

I am not using OS installer. I do need to do build and capture will I be able to use x86 winpe to do build and capture on Win 6 x64

For the B&C, use the matching architecture.
For the deploy, you can use either. We use x86 to deploy both architectures.

Getting the error below duruing Build and Capture x64

The task sequence execution engine failed executing the action (Setup windows and ConfigMgr) in the group (Install Operating System) with the error code 2147500037
Action output: ce\unattend.xml
Successfully initialized driver information
Command line for extension .EXE is "%1" %*
Set command line: "C:\_SMSTaskSequence\Packages\HH1002A3\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot
Executing commandline: "C:\_SMSTaskSequence\Packages\HH1002A3\SOURCES\SETUP.EXE" "/unattend:C:\_SMSTaskSequence\unattend.xml" /noreboot
Process completed with exit code 31
Windows Setup completed with exit code 31
Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\HH1002A3
reference count 1 for the source C:\_SMSTaskSequence\Packages\HH1002A3 before releasing
Delete source directory C:\_SMSTaskSequence\Packages\HH1002A3
Released the resolved source C:\_SMSTaskSequence\Packages\HH1002A3
exitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,440)
setup.run(), HRESULT=80004005 (e:\nts_sms_fre\sms\client\osdeployment\setupwindows\setupwindows.cpp,1707)
Exiting with code 0x80004005
Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error

x86 B&C works fine

Windows setup failed, code 31. The operating system reported error 2147500037: Unspecified error

x86 B&C works fine

you'll need to examine the Windows setup logfiles to work out what's happening (cause of the error 31)

http://support.microsoft.com/kb/927521/en-au