SCCM identificates the wrong architecture

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

SCCM identificates the wrong architecture

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> SCCM identificates the wrong architecture

Page: [1]

Message

<< Older Topic Newer Topic >>

SCCM identificates the wrong architecture - 1/31/2008 6:16:00 AM

Kilimanscharo

Posts: 5
Score: 0
Joined: 1/4/2008
Status: offline

Hello,

I want to deploy Windows XP Prof over my SCCM.

I made a DHCP- Reservation for the Client, which contains the following values:

66 - DNS Name of the Server
67 - The path to the file \SMSBoot\x86\wdsnbp.com

The Server is configured correctly, I think.

I want to deploy the operating system about the PXE Boot, but I´ve got the problem, that the SCCM identificates the client- system as an x64- Architecture, but that´s wrong, It´s an x86 Architecture.

The following Messages are comming on the screen of the Client:

Downloaded WDSNBP...
WDSNBP started using DCHP Referral

Contacting Server (xxx.xxx.xxx.xxx)
Architecture: x64

TFTP download SMSBoot\x64\pxeboot.com
.
TFTP download SMSBoot\x64\pxeboot.com
.
TFTP download SMSBoot\x64\pxeboot.com
.

an so on.

Can anybody help me, to resolve the problem?

Thanks.

Best gegards

Kilimanscharo

< Message edited by Kilimanscharo -- 1/31/2008 6:18:03 AM >

_____________________________

My english is not the best, but I hope, that everybody understand me.

Post #: 1

RE: SCCM identifies the wrong architecture - 1/31/2008 12:50:02 PM

rtruss

Posts: 241
Score: 11
Joined: 11/4/2004
Status: offline

I will bet you the system is x64. I have played with Windows Deployment Services after upgrading my RIS server and noticed it was smart enough to know what architecture the system is. the following is simply the way PXE boots the system:
Contacting Server (xxx.xxx.xxx.xxx)
Architecture: x64

TFTP download SMSBoot\x64\pxeboot.com

The deployment of the OS is or should be configurable by you but the way the systems PXE boots is not.

My system also PXE boots like this:
Contacting Server (xxx.xxx.xxx.xxx)
Architecture: x64

TFTP download SMSBoot\x64\pxeboot.com

Then the WDS server gives me 5 options when I boot an x64 system (The first 4 I created using the WDS console):
Image Deploy (x86)
Image Capture (x86)
Image Deploy (x64)
Image Capture (x64)
Remote Installation Services

Sorry I cannot help you out any more than that as we do not have SCCM yet.

_____________________________

Roger Truss
Assistant Windows Administrator
SMS Admin
Trend Micro Admin
ImageUltra Admin

Please rate my post ;)

(in reply to Kilimanscharo)

Post #: 2

RE: SCCM identifies the wrong architecture - 1/31/2008 3:27:06 PM

wbracken

Posts: 1006
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline

If your runing this on a Core2Duo it will get detected as x64 due to the 64bit extensions in the proc. This is normal and like stated above has no bearing on why type of image you bring down to the machine...

_____________________________

William Bracken

http://www.clientarchitect.com

(in reply to rtruss)

Post #: 3

RE: SCCM identifies the wrong architecture - 2/1/2008 7:24:34 AM

Kilimanscharo

Posts: 5
Score: 0
Joined: 1/4/2008
Status: offline

Hello,
Thanks for the replies.
The SCCM starts Now the Windows PE but I get an error while the execution of the Task seqence.

I get the following error:

Task Sequence: Task Sequence 3 has failed with the error code(0x8004005). For more information, please contact your system administrator.

Does anybody know this issue?

_____________________________

My english is not the best, but I hope, that everybody understand me.

(in reply to wbracken)

Post #: 4

RE: SCCM identifies the wrong architecture - 2/1/2008 9:17:33 AM

rtruss

Posts: 241
Score: 11
Joined: 11/4/2004
Status: offline

My guess is you are getting the error while trying to install XP. Is this an upgrade or are you wiping the hard drive first?

You can try this out. http://support.microsoft.com/default.aspx?scid=kb;en-us;306081. I could not find much on this error. Have you verified your CD key? I am not too familiar with SCCM and the way it sequences a build but but hope this helps. The only other item I found was in German so I could not read it. Not sure if you can but here it is anyway..

http://www.mcseboard.de/windows-forum-ms-backoffice-31/task-sequence-error-0x8004005-128884.html

_____________________________

Roger Truss
Assistant Windows Administrator
SMS Admin
Trend Micro Admin
ImageUltra Admin

Please rate my post ;)

(in reply to Kilimanscharo)

Post #: 5

WDS Boot Menu - 3/12/2008 10:55:50 AM

rjarrett

Posts: 589
Score: 17
Joined: 5/26/2004
Status: offline

Roger,

I notice that your "boot menu" options include capture and deploy images. Can you elaborate?

As a test, I configured WDS without the PXE role being assigned to any site server. I want to get ANY PXE boot deployment to work first. From there I will work toward SCCM\PXE\WDS deployment.

I then imported two distinct boot and one O/S image files. In pure WDS mode, the client will PXE boot and prompt for F12 to do a network boot. The boot menu then appears, but it only has the two boot images. The O/S deployment image is not among the options.

Your menu appears to show multiple images, of different types.

Thanks.

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to rtruss)

Post #: 6

RE: WDS Boot Menu - 3/12/2008 4:11:50 PM

rtruss

Posts: 241
Score: 11
Joined: 11/4/2004
Status: offline

how did you import the O/S Image? What architecture base is the image on x86 or x64. The WDS system reads the computers hardware and only displays images that match the "hal" of the system. My capture image is used to image a syspreped system up to the server and the deploy image is used to deploy images to the computer.

(in reply to rjarrett)

Post #: 7

RE: WDS Boot Menu - 3/13/2008 8:58:07 AM

rjarrett

Posts: 589
Score: 17
Joined: 5/26/2004
Status: offline

I built a baseline WXP SP2 machine on older Pentium (x86) hardware. No possibility of the newer architecture being detected. When I imported two x86 boot images and one WXP SP2 reference image into WDS, the PXE client sees both boot images. There is no option to choose the reference image during the PXE F12 boot and the WinPE never launches the reference image. So, using WDS only:

Q1. How do you select/inititate the installation of the "reference" image by the x86 boot WinPE?

Q2. Can/should you build a "bootable" reference image to self install itself and then add it to the WDS boot images?

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to rtruss)

Post #: 8

RE: WDS Boot Menu - 3/13/2008 9:17:03 AM

rtruss

Posts: 241
Score: 11
Joined: 11/4/2004
Status: offline

Bear with me I have not played with WDS in a while, we use LENOVOs ImageUltra builder to deploy.

What happens is after your f12 boot you are presented with some options, one being Remote Installation Services if you have it enabled that way. The other option(s) would be your boot images and or capture images. I am guessing you have a boot image for x86 and one for x64. Depending on the architecture you will see either the x86 or both. Select one. The system will then boot in to the new PE environment and will need you to need to authenticate to your network/image server. Once there you should see all available images. You will NOT see them in the initial menu after you PXE boot you should only see your boot/capture and/or a RIS option after you press F12.

< Message edited by rtruss -- 3/13/2008 9:18:28 AM >

(in reply to rjarrett)

Post #: 9

RE: WDS Boot Menu - 3/13/2008 2:56:38 PM

rjarrett

Posts: 589
Score: 17
Joined: 5/26/2004
Status: offline

Alright. That sounds correct. When I am doing a WDS-only deployment (i.e. no SCCM involved) I can get it to come up and prompt for an F12 to continue. I do get a boot option menu, so long as I have more than one boot image loaded into WDS. That makes sense, if there is only one image, it will launch. The client then boots with the selected WinPE boot image.

This is where I get lost. The client boots and it automatically opens the command prompt. I can use that command prompt to verfiy IPCONFIG, map to network drives, etc. Where do I go from here? How do I launch the imaging process with my reference WIM file in WDS?

_____________________________

Let me know if this helped...

Rob Jarrett
SMS\VB Development

(in reply to rtruss)

Post #: 10

RE: WDS Boot Menu - 3/13/2008 6:22:14 PM

rtruss

Posts: 241
Score: 11
Joined: 11/4/2004
Status: offline

Try this. http://technet2.microsoft.com/WindowsVista/en/library/9e197135-6711-4c20-bfad-fc80fc2151301033.mspx?mfr=true It is what I used to create my boot and capture images. I think the capture part may be what you need. All the images I have on my server were uploaded using the capture image piece. Syspreped the box then PXE boot select capture followed the prompts and viola. We do not have SCCM either. I have not used the image import feature.

(in reply to rjarrett)

Post #: 11