Prev: Error While Installation- setup unable to read or write to drive c
Next: WDS Imaging very slow
From: Steve on 3 Oct 2007 19:44
I need to do simple imaging using WDS. All I want to be able to do right now
is take an image of a WinXP machine and then be able to image other machines
with that image. I have WDS set up on a Win2003 Server but thats about as far
as I get before I hit a brick wall. The instructions are very muddy. When I
boot an existing Xp machine with PXE it does not find the WDS server. I get
PXE errors like tftp error and no file found. Can anyone point me to a simple
step by step document on how to get this working? We have used Novell
Zenworks for imaging for years but we are trying to get away from that.
From: Ben on 4 Oct 2007 06:58
"Steve" <Steve(a)discussions.microsoft.com> wrote in message
news:481D9C7F-534A-46E4-94A7-6E4D798068E0(a)microsoft.com...
>I need to do simple imaging using WDS. All I want to be able to do right
>now
> is take an image of a WinXP machine and then be able to image other
> machines
> with that image. I have WDS set up on a Win2003 Server but thats about as
> far
> as I get before I hit a brick wall. The instructions are very muddy. When
> I
> boot an existing Xp machine with PXE it does not find the WDS server. I
> get
> PXE errors like tftp error and no file found. Can anyone point me to a
> simple
> step by step document on how to get this working? We have used Novell
> Zenworks for imaging for years but we are trying to get away from that.

Steve,

Need to know a bit more about your setup! What version of Win 2003 server
are you running - Win 2003, or Win 2003 R2? What service pack is it? Have
you authorised your WDS server in active directory? Have you configured the
other tabs under server properties? i.e. PXE Response settings, Boot, DHCP
etc?

You _may_ need to add addition DHCP Scope options, specifically option 60 -
PXEClient, 66 - Boot Server Host Name & 67 - Boot File Name. Additionally
make sure you have the boot files referenced under the Boot tab, x86 -
Boot\x86\pxeboot.com, x64 - Boot\x64\pxeboot.com etc, and check those files
exist under <drive>\<Ris install>\Boot you should have at least x64, x86,
which need to have the boot files contained with in (there should be other
folders like fonts etc as well).

HTH

Ben


From: Steve on 4 Oct 2007 08:25


"Ben" wrote:

> "Steve" <Steve(a)discussions.microsoft.com> wrote in message
> news:481D9C7F-534A-46E4-94A7-6E4D798068E0(a)microsoft.com...
> >I need to do simple imaging using WDS. All I want to be able to do right
> >now
> > is take an image of a WinXP machine and then be able to image other
> > machines
> > with that image. I have WDS set up on a Win2003 Server but thats about as
> > far
> > as I get before I hit a brick wall. The instructions are very muddy. When
> > I
> > boot an existing Xp machine with PXE it does not find the WDS server. I
> > get
> > PXE errors like tftp error and no file found. Can anyone point me to a
> > simple
> > step by step document on how to get this working? We have used Novell
> > Zenworks for imaging for years but we are trying to get away from that.
>
> Steve,
>
> Need to know a bit more about your setup! What version of Win 2003 server
> are you running - Win 2003, or Win 2003 R2? What service pack is it? Have
> you authorised your WDS server in active directory? Have you configured the
> other tabs under server properties? i.e. PXE Response settings, Boot, DHCP
> etc?
>
> You _may_ need to add addition DHCP Scope options, specifically option 60 -
> PXEClient, 66 - Boot Server Host Name & 67 - Boot File Name. Additionally
> make sure you have the boot files referenced under the Boot tab, x86 -
> Boot\x86\pxeboot.com, x64 - Boot\x64\pxeboot.com etc, and check those files
> exist under <drive>\<Ris install>\Boot you should have at least x64, x86,
> which need to have the boot files contained with in (there should be other
> folders like fonts etc as well).
>
> HTH
>
> Ben
>
>
>

Hi Ben,

Thanks for helping me. Here is what I can tell you right now. The WDS server
is running on Win 2003 SP2. The server is in Active Directory but I am not
sure what you mean by authorizing it in AD. I have configured the tabs under
server properties.

When I do a PXE boot of a machine the machice does get a DHCP address form
my Netware DHCP server. (I know..Netware.. :-) we are trying to move away
from it)

The files referenced under the boot tab x86 pxeboot.com are not in the
Remote install\Boot\x86 directory. There are some files and folders there but
the pxeboot.com file is not there. So this may be at least part of my
problem. Am I suppose to create these files manually somehow?

Sorry to seem dnese about this. We are just moving to Microsoft form Netware
so I'm trying to get up to speed.
From: Ben on 5 Oct 2007 06:40
"Steve" <Steve(a)discussions.microsoft.com> wrote in message
news:C8780A34-C4AC-4D50-85E6-FEB39418DFB3(a)microsoft.com...
>
> Hi Ben,
>
> Thanks for helping me. Here is what I can tell you right now. The WDS
> server
> is running on Win 2003 SP2. The server is in Active Directory but I am not
> sure what you mean by authorizing it in AD. I have configured the tabs
> under
> server properties.
>
> When I do a PXE boot of a machine the machice does get a DHCP address form
> my Netware DHCP server. (I know..Netware.. :-) we are trying to move away
> from it)
>
> The files referenced under the boot tab x86 pxeboot.com are not in the
> Remote install\Boot\x86 directory. There are some files and folders there
> but
> the pxeboot.com file is not there. So this may be at least part of my
> problem. Am I suppose to create these files manually somehow?
>
> Sorry to seem dnese about this. We are just moving to Microsoft form
> Netware
> so I'm trying to get up to speed.

Steve,

Went through a similar process at my last company, Netware 5 to Win2000.

When I said authorise in AD, I of course meant DHCP ;-) This is under the
Advanced tab of the WDS server - DHCP Authorisation - Yes I want to
authorise the WDS server in DHCP. However, I don't know how Netware DHCP
works with this. Microsoft DHCP is Active Directory aware, and works with
other Microsoft products. Just looking at the DHCP tab of WDS it says
"Non-Microsoft DHCP servers require manual configuration of DHCP option tag
60."

Try adding the 3 DHCP scope options:
Option 60 - Client Identifier set to "PXEClient"
Option 66 - Boot Server Host Name set to server name i.e. WDSServer
Option 67 - Boot File Name set to the boot file name, for old RIS this is
\Oschooser\i386\Startrom.com for WDS this would be Boot\x86\pxeboot.com
(some Linux servers use / rather than \ not sure about Netware)

From what I remember, the files under the Boot\x86 and boot\x64 directory
were created automatically when I installed WDS, although it was nearly a
year ago since I did that so not 100% sure, but I don't ever remember having
to create the files. Try uninstalling + re-installing!

Also, what is the path to those files, I notice you said "Remote
Install\Boot\x86" does it actually have a space in between? I don't know if
it does affect anything, but I'd get rid of the space, just in case, we use
"RIS\Boot\x86"

HTH

Ben


From: Steve on 5 Oct 2007 10:46


"Ben" wrote:

> "Steve" <Steve(a)discussions.microsoft.com> wrote in message
> news:C8780A34-C4AC-4D50-85E6-FEB39418DFB3(a)microsoft.com...
> >
> > Hi Ben,
> >
> > Thanks for helping me. Here is what I can tell you right now. The WDS
> > server
> > is running on Win 2003 SP2. The server is in Active Directory but I am not
> > sure what you mean by authorizing it in AD. I have configured the tabs
> > under
> > server properties.
> >
> > When I do a PXE boot of a machine the machice does get a DHCP address form
> > my Netware DHCP server. (I know..Netware.. :-) we are trying to move away
> > from it)
> >
> > The files referenced under the boot tab x86 pxeboot.com are not in the
> > Remote install\Boot\x86 directory. There are some files and folders there
> > but
> > the pxeboot.com file is not there. So this may be at least part of my
> > problem. Am I suppose to create these files manually somehow?
> >
> > Sorry to seem dnese about this. We are just moving to Microsoft form
> > Netware
> > so I'm trying to get up to speed.
>
> Steve,
>
> Went through a similar process at my last company, Netware 5 to Win2000.
>
> When I said authorise in AD, I of course meant DHCP ;-) This is under the
> Advanced tab of the WDS server - DHCP Authorisation - Yes I want to
> authorise the WDS server in DHCP. However, I don't know how Netware DHCP
> works with this. Microsoft DHCP is Active Directory aware, and works with
> other Microsoft products. Just looking at the DHCP tab of WDS it says
> "Non-Microsoft DHCP servers require manual configuration of DHCP option tag
> 60."
>
> Try adding the 3 DHCP scope options:
> Option 60 - Client Identifier set to "PXEClient"
> Option 66 - Boot Server Host Name set to server name i.e. WDSServer
> Option 67 - Boot File Name set to the boot file name, for old RIS this is
> \Oschooser\i386\Startrom.com for WDS this would be Boot\x86\pxeboot.com
> (some Linux servers use / rather than \ not sure about Netware)
>
> From what I remember, the files under the Boot\x86 and boot\x64 directory
> were created automatically when I installed WDS, although it was nearly a
> year ago since I did that so not 100% sure, but I don't ever remember having
> to create the files. Try uninstalling + re-installing!
>
> Also, what is the path to those files, I notice you said "Remote
> Install\Boot\x86" does it actually have a space in between? I don't know if
> it does affect anything, but I'd get rid of the space, just in case, we use
> "RIS\Boot\x86"
>
> HTH
>
> Ben
>
>
>
Hello Ben,

I reinstalled my server and brought it up as Win 2003 SP1 first. Installed
RIS. Then Updated to SP2 and configured WDS. I still do not have the
PXEBoot.com file. I was able to point the boot to
\OSChooser\i386\startrom.com and boot up with PXE and connect to the server.
But the only option I have once I connect to the server is client
installation. I need to be able to take an image of a machine I already have
configured. Then be able to use that image to image 80 other machines. So I
am still having a problem. I was able to set Option 60 on my Novell DHCP
server to PXEClient. I'm sure it is something I am doing wrong but I don't
know waht it is.
 |  Next  |  Last
Pages: 1 2 3
Prev: Error While Installation- setup unable to read or write to drive c
Next: WDS Imaging very slow