durge
asked on
PXE Netboot Windows 2003 Server x64 via Tftpd32
I've got an Asus AP1600r server (manual: http://dlsvr02.asus.com/pub/ASUS/server/AP1600R(PR-DLSR)/Manual/e1107_ap1600r.pdf )
I've currently got 2 workstations, both running Windows XP x64, I'd like to be able to PXE netboot the Asus server to install Windows 2003 Server Standard x64, Some nice step-by-step instructions would be nice, with URL's :)
- I don't have another 2003 server here, so RIS isn't the answer.
- I have a switch, on an internal network with no DHCP.
- I have untouched MSDN ISO's for the server OS.
I've assigned 500 Points for this one, so get thinking. :)
Many thanks.
I've currently got 2 workstations, both running Windows XP x64, I'd like to be able to PXE netboot the Asus server to install Windows 2003 Server Standard x64, Some nice step-by-step instructions would be nice, with URL's :)
- I don't have another 2003 server here, so RIS isn't the answer.
- I have a switch, on an internal network with no DHCP.
- I have untouched MSDN ISO's for the server OS.
I've assigned 500 Points for this one, so get thinking. :)
Many thanks.
Just realized the x64, sorry. I don't know of a method at this point.
ASKER
Well, does anyone know if the installer for x64 will run under 16-bit? I know it does with the 32-bit OS'es, and I'm thinking it might be something the same... But I'm not entirely sure.
I'll get the PXE environment up and running tomorrow with the DOS/*nix method suggested.
I'll get the PXE environment up and running tomorrow with the DOS/*nix method suggested.
No it will not, nor will it under 32 bit.
The following list describes the key changes between the Windows x64 Edition installation process and the Windows x86 installation process:
* Windows Startup floppy disks cannot be used to install x64 Edition-based version of Windows Server 2003 and Windows XP Professional. This is because the kernel that is supplied with x64 Edition-based operating systems is now over 2 MB and does not fit on a standard floppy disk.
* You cannot use Winnt.exe to install Windows x64 Edition. Winnt.exe is not included on the Windows x64 Edition installation CD-ROM.
* The installation process for x86 32-bit operating systems cannot be started from within the x64 operating system environment. For example, you cannot install Windows XP Professional x64 Edition from within the 32-bit version of Windows XP Professional.
* The x86 versions of the Windows operating system cannot be upgraded to the x64 Edition version of the Windows operating system. However, Windows Server 2003 x64 Standard Edition can be upgraded to Windows Server 2003 x64 Enterprise Edition.
* The installation process for x64 Edition operating systems does not support MS-DOS based mechanisms. For example, you cannot install Windows XP Professional x64 Edition from a command prompt.
* The layout of the x64 Edition-based version of Windows Server 2003 and Windows XP installation CD-ROM has changed. The primary installation folder for Windows x64 Editions is the AMD64 folder. However, the i386 folder still exists and contains files that are required to install the Windows x64 Edition-based operating system. Therefore, before you can successfully start the installation of the Windows x64 Edition operating system either locally or from a network share, you must make sure that the AMD64 folder and the other folders that are contained on the Windows x64 Edition installation CD-ROM are either copied locally or copied to the network share.
* The installation of the Windows x64 Edition-based operating system must be performed by starting the computer by using the Windows x64 Edition installation CD-ROM or by starting the installation from within another Windows 64-bit operating system.
* The Windows x64 Edition operating system is not currently available as a retail product. At release the Windows x64 Edition operating system will only be distributed for evaluation or through MSDN, Software Assurance, volume channels and OEM channels.
* The Windows x64 Edition operating system supports "sticky" hotfixes. "Sticky" hotfixes are not overwritten or uninstalled when other updates are applied unless those updates are a more current version than the file that is currently installed on the computer.
Because of these changes, we recommend that you perform a clean installation of the Windows x64 Editions operating systems from the CD-ROM.
The Windows x64 Editions operating systems may also be deployed by using an unattended installation, System Preparation Tool (Sysprep), and Remote Installation Services (RIS) methods. For more information about how to use these tools, visit the following Microsoft Web site:
The following list describes the key changes between the Windows x64 Edition installation process and the Windows x86 installation process:
* Windows Startup floppy disks cannot be used to install x64 Edition-based version of Windows Server 2003 and Windows XP Professional. This is because the kernel that is supplied with x64 Edition-based operating systems is now over 2 MB and does not fit on a standard floppy disk.
* You cannot use Winnt.exe to install Windows x64 Edition. Winnt.exe is not included on the Windows x64 Edition installation CD-ROM.
* The installation process for x86 32-bit operating systems cannot be started from within the x64 operating system environment. For example, you cannot install Windows XP Professional x64 Edition from within the 32-bit version of Windows XP Professional.
* The x86 versions of the Windows operating system cannot be upgraded to the x64 Edition version of the Windows operating system. However, Windows Server 2003 x64 Standard Edition can be upgraded to Windows Server 2003 x64 Enterprise Edition.
* The installation process for x64 Edition operating systems does not support MS-DOS based mechanisms. For example, you cannot install Windows XP Professional x64 Edition from a command prompt.
* The layout of the x64 Edition-based version of Windows Server 2003 and Windows XP installation CD-ROM has changed. The primary installation folder for Windows x64 Editions is the AMD64 folder. However, the i386 folder still exists and contains files that are required to install the Windows x64 Edition-based operating system. Therefore, before you can successfully start the installation of the Windows x64 Edition operating system either locally or from a network share, you must make sure that the AMD64 folder and the other folders that are contained on the Windows x64 Edition installation CD-ROM are either copied locally or copied to the network share.
* The installation of the Windows x64 Edition-based operating system must be performed by starting the computer by using the Windows x64 Edition installation CD-ROM or by starting the installation from within another Windows 64-bit operating system.
* The Windows x64 Edition operating system is not currently available as a retail product. At release the Windows x64 Edition operating system will only be distributed for evaluation or through MSDN, Software Assurance, volume channels and OEM channels.
* The Windows x64 Edition operating system supports "sticky" hotfixes. "Sticky" hotfixes are not overwritten or uninstalled when other updates are applied unless those updates are a more current version than the file that is currently installed on the computer.
Because of these changes, we recommend that you perform a clean installation of the Windows x64 Editions operating systems from the CD-ROM.
The Windows x64 Editions operating systems may also be deployed by using an unattended installation, System Preparation Tool (Sysprep), and Remote Installation Services (RIS) methods. For more information about how to use these tools, visit the following Microsoft Web site:
ASKER
The AP1600R has some weird CDrom that clips on (I don't have it), It has no IDE controllers on the motherboard, it has 1 scsi connector on the board at the back of the case, but I have no CDrom to connect to this.
The BIOS doesn't support booting USB devices, and I've already tried, so am I gonna be stuck with a 32-bit OS?
Or am I gonna have to install say Ubuntu server 64-bit, and then install Server 2003 x64 inside of this?
The BIOS doesn't support booting USB devices, and I've already tried, so am I gonna be stuck with a 32-bit OS?
Or am I gonna have to install say Ubuntu server 64-bit, and then install Server 2003 x64 inside of this?
If the system will support PXE boot and you have some time, you could download virtual PC and load XP32 in a VM and load TFTPD32 on top of that which will do DHCP and PXE. Then all you would need is the install / config.
The VM would be on either PC and virtual PC is free from Microsoft.
ASKER
Why would I need a VM?
XP x64 with Tftpd32 works fine from what I'm reading, It's merely the process of netbooting x64 Server 2003 eludes me.
The server does support PXE, Intel Pro 1000 onboard (that's why I attached the specs in my first post).
WinPE x64?
XP x64 with Tftpd32 works fine from what I'm reading, It's merely the process of netbooting x64 Server 2003 eludes me.
The server does support PXE, Intel Pro 1000 onboard (that's why I attached the specs in my first post).
WinPE x64?
You wouldn't need a VM if TFTPd32 works on x64 I just noticed posts of issues with it. Looks like winPE 2.1 would work and below is instructions on setting up the pxe image of PE.
http://www.windowsdevcenter.com/pub/a/windows/2007/03/20/pc-deployment-with-winpe.html
http://www.windowsdevcenter.com/pub/a/windows/2007/03/20/pc-deployment-with-winpe.html
ASKER
Thanks, I'll have a play. Though, this deployment uses RIS though right?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok... so here's what I've done...
Sun xVM Virtualbox...
Built a Windows Server 2003 x64.
Installed DHCP/DNS/RIS.
Added Windows 2003 Server x64 to RIS.
--
It wouldn't work, PXE boot wasn't picking up there being a PXE server.
--
Downloaded latest WAIK (vista PE).
Installed Windows Remote Deployment/WAIK.
The ASUS server finally detected that there was a PXE server present, I pressed F12 and got the the menu up asking me whether to boot to Vista PE or my 2003 Server RIS environment.
--
Server 2003 RIS wouldn't work, it just errored saying it wouldn't work (can't remember the exact error).
--
Booted to Vista PE, Mounted a network drive via NET USE pointing at a Windows Server 2003 Web Edition disk (I had a feeling x64 would be pedantic).
CD'ed into the i386 dir.
Ran winnt32, hard disk couldn't be found.
So this is where i'm currently up to, I've got the DISKPART utility formatting the disk at the moment, so hopefully when this is done i'll be able to install this bloody server finally.
Sun xVM Virtualbox...
Built a Windows Server 2003 x64.
Installed DHCP/DNS/RIS.
Added Windows 2003 Server x64 to RIS.
--
It wouldn't work, PXE boot wasn't picking up there being a PXE server.
--
Downloaded latest WAIK (vista PE).
Installed Windows Remote Deployment/WAIK.
The ASUS server finally detected that there was a PXE server present, I pressed F12 and got the the menu up asking me whether to boot to Vista PE or my 2003 Server RIS environment.
--
Server 2003 RIS wouldn't work, it just errored saying it wouldn't work (can't remember the exact error).
--
Booted to Vista PE, Mounted a network drive via NET USE pointing at a Windows Server 2003 Web Edition disk (I had a feeling x64 would be pedantic).
CD'ed into the i386 dir.
Ran winnt32, hard disk couldn't be found.
So this is where i'm currently up to, I've got the DISKPART utility formatting the disk at the moment, so hopefully when this is done i'll be able to install this bloody server finally.
ASKER
Just a follow up, after I finished the format, I set the disk to ACTIVE and ONLINE.
Ran winnt32 again, it copied all the files, took the CD key etc.
But the installer after it got to the end of stage 1 just exited, I rebooted and Windows still doesn't boot.
This is really becoming such a mission, I've been netbooting Cobalt RaQ's for many years but this is seriously over complicated, if I can't get this working I think I'm gonna move onto an Open Source solution.
Ran winnt32 again, it copied all the files, took the CD key etc.
But the installer after it got to the end of stage 1 just exited, I rebooted and Windows still doesn't boot.
This is really becoming such a mission, I've been netbooting Cobalt RaQ's for many years but this is seriously over complicated, if I can't get this working I think I'm gonna move onto an Open Source solution.
ASKER
/working, server 2008 web edition from Vista PE environment.
http://thesystemadministrator.com/The_System_Administrator/Tips_&_Tricks/PXE,_aka_Pre-Execution_Environment_-_Part_1/