DWeuve Absent Member.
Absent Member.
1445 views

Getting prompted for server IP when I shouldn't be.....

Hello everyone,

I'm got ZCM 11.2 installed on a Windows 2003 Standard server.

I used the CD media creator utility to modify the settings.txt file and
added it to the bootcd.iso file and created a bootable CD. I looked at the
settings.txt and bootcd.iso every step along the way and everything seems to
be exactly the way I would expect it, until I boot up a computer off that
CD.

Then I get prompted for my imaging server.

That is what the PROXYADDR is for, right?

Any ideas??

Delon


________________________________________

Delon E. Weuve
Senior Network Engineer
Office of Auditor of State
State of Iowa
United States of America

Labels (2)
0 Likes
13 Replies
nop19832 Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Delon E. Weuve wrote:

> Hello everyone,
>
> I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
>
> I used the CD media creator utility to modify the settings.txt file
> and added it to the bootcd.iso file and created a bootable CD. I
> looked at the settings.txt and bootcd.iso every step along the way
> and everything seems to be exactly the way I would expect it, until I
> boot up a computer off that CD.
>
> Then I get prompted for my imaging server.
>
> That is what the PROXYADDR is for, right?
>
> Any ideas??
>
> Delon


After you burn the cd, does the setting.txt look alright?

Yes, it should look like this:
#PROXYADDR is the IP address or DNS name of the ZENworks Imaging Server.
PROXYADDR=1.1.1.1

If you write the IP (when prompted) of the PXE server the imaging
works, right?

--

--
Niels Poulsen

Novell Knowledge Partner

-------------------------------
A TRUE RED DEVIL

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
DWeuve Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Niels,

Yes, when I enter the exact same IP address as what's in the PROXYADDR, it
works.

Delon


________________________________________

Delon E. Weuve
Senior Network Engineer
Office of Auditor of State
State of Iowa
United States of America


>>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>

Delon E. Weuve wrote:

> Hello everyone,
>
> I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
>
> I used the CD media creator utility to modify the settings.txt file
> and added it to the bootcd.iso file and created a bootable CD. I
> looked at the settings.txt and bootcd.iso every step along the way
> and everything seems to be exactly the way I would expect it, until I
> boot up a computer off that CD.
>
> Then I get prompted for my imaging server.
>
> That is what the PROXYADDR is for, right?
>
> Any ideas??
>
> Delon


After you burn the cd, does the setting.txt look alright?

Yes, it should look like this:
#PROXYADDR is the IP address or DNS name of the ZENworks Imaging Server.
PROXYADDR=1.1.1.1

If you write the IP (when prompted) of the PXE server the imaging
works, right?

‑‑

‑‑
Niels Poulsen

Novell Knowledge Partner

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑
A TRUE RED DEVIL


0 Likes
nop19832 Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Delon E. Weuve wrote:

> Niels,
>
> Yes, when I enter the exact same IP address as what's in the
> PROXYADDR, it works.
>
> Delon
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>

> Delon E. Weuve wrote:
>
> > Hello everyone,
> >
> > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> >
> > I used the CD media creator utility to modify the settings.txt file
> > and added it to the bootcd.iso file and created a bootable CD. I
> > looked at the settings.txt and bootcd.iso every step along the way
> > and everything seems to be exactly the way I would expect it, until
> > I boot up a computer off that CD.
> >
> > Then I get prompted for my imaging server.
> >
> > That is what the PROXYADDR is for, right?
> >
> > Any ideas??
> >
> > Delon

>
> After you burn the cd, does the setting.txt look alright?
>
> Yes, it should look like this:
> #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> Server. PROXYADDR=1.1.1.1
>
> If you write the IP (when prompted) of the PXE server the imaging
> works, right?
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑�
> ��‑� ��‑‑‑‑‑
> A TRUE RED DEVIL


And the settings.txt file on your cd looks right?

--

--
Niels Poulsen

Novell Knowledge Partner

-------------------------------
A TRUE RED DEVIL

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
DWeuve Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Niels,

There are only three non-commented lines in the settings.txt file:

PARTITIONSIZE=150

netsetup="dhcp,now,all"

PROXYADDR=<My imaging server IP>

The first two are defaults. The last one is correct as far as I know...

Delon


________________________________________

Delon E. Weuve
Senior Network Engineer
Office of Auditor of State
State of Iowa
United States of America


>>> Niels Poulsen<nop@viborg.dk> 4/23/2012 1:02 PM >>>

Delon E. Weuve wrote:

> Niels,
>
> Yes, when I enter the exact same IP address as what's in the
> PROXYADDR, it works.
>
> Delon
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>

> Delon E. Weuve wrote:
>
> > Hello everyone,
> >
> > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> >
> > I used the CD media creator utility to modify the settings.txt file
> > and added it to the bootcd.iso file and created a bootable CD. I
> > looked at the settings.txt and bootcd.iso every step along the way
> > and everything seems to be exactly the way I would expect it, until
> > I boot up a computer off that CD.
> >
> > Then I get prompted for my imaging server.
> >
> > That is what the PROXYADDR is for, right?
> >
> > Any ideas??
> >
> > Delon

>
> After you burn the cd, does the setting.txt look alright?
>
> Yes, it should look like this:
> #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> Server. PROXYADDR=1.1.1.1
>
> If you write the IP (when prompted) of the PXE server the imaging
> works, right?
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> ‑ ‑‑‑‑‑
> A TRUE RED DEVIL


And the settings.txt file on your cd looks right?

‑‑

‑‑
Niels Poulsen

Novell Knowledge Partner

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑
A TRUE RED DEVIL


0 Likes
nop19832 Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Delon E. Weuve wrote:

> Niels,
>
> There are only three non-commented lines in the settings.txt file:
>
> PARTITIONSIZE=150
>
> netsetup="dhcp,now,all"
>
> PROXYADDR=<My imaging server IP>
>
> The first two are defaults. The last one is correct as far as I
> know...
>
> Delon
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 1:02 PM >>>

> Delon E. Weuve wrote:
>
> > Niels,
> >
> > Yes, when I enter the exact same IP address as what's in the
> > PROXYADDR, it works.
> >
> > Delon
> >
> >
> > ________________________________________
> >
> > Delon E. Weuve
> > Senior Network Engineer
> > Office of Auditor of State
> > State of Iowa
> > United States of America
> >
> >
> > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>

> > Delon E. Weuve wrote:
> >
> > > Hello everyone,
> > >
> > > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> > >
> > > I used the CD media creator utility to modify the settings.txt
> > > file and added it to the bootcd.iso file and created a bootable
> > > CD. I looked at the settings.txt and bootcd.iso every step along
> > > the way and everything seems to be exactly the way I would expect
> > > it, until I boot up a computer off that CD.
> > >
> > > Then I get prompted for my imaging server.
> > >
> > > That is what the PROXYADDR is for, right?
> > >
> > > Any ideas??
> > >
> > > Delon

> >
> > After you burn the cd, does the setting.txt look alright?
> >
> > Yes, it should look like this:
> > #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> > Server. PROXYADDR=1.1.1.1
> >
> > If you write the IP (when prompted) of the PXE server the imaging
> > works, right?
> >
> > ‑‑
> >
> > ‑‑
> > Niels Poulsen
> >
> > Novell Knowledge Partner
> >
> >

> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> > ‑ ‑‑‑‑‑
> > A TRUE RED DEVIL

>
> And the settings.txt file on your cd looks right?
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑�
> ��‑� ��‑‑‑‑‑
> A TRUE RED DEVIL


Okay, yes it looks okay.
During the imaging boot, try to hit ctrl-alt-F4 or ctrl-alt-F3 (not
sure which of them). This wil send you to the terminals where you can
see what it's doing in the process. Check to see if you can find the
part where it reads from the setting.txt file. Maby it comes with an
error doing so.
Let me know if you can't find it, then I'll try to explain better 🙂

--

--
Niels Poulsen

Novell Knowledge Partner

-------------------------------
A TRUE RED DEVIL

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
DWeuve Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

I found a reference to settings.txt in the boot sequence.

The only two errors I found were Unknown error 132 right after the reference
to settings.txt and an error that when DHCP was going where the DNS entry
could not be found. Since I am using the IP address, I'm not surprised about
the second error.

Any idea what Unknown error 132 is??



________________________________________

Delon E. Weuve
Senior Network Engineer
Office of Auditor of State
State of Iowa
United States of America


>>> Niels Poulsen<nop@viborg.dk> 4/23/2012 2:12 PM >>>

Delon E. Weuve wrote:

> Niels,
>
> There are only three non‑commented lines in the settings.txt file:
>
> PARTITIONSIZE=150
>
> netsetup="dhcp,now,all"
>
> PROXYADDR=<My imaging server IP>
>
> The first two are defaults. The last one is correct as far as I
> know...
>
> Delon
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 1:02 PM >>>

> Delon E. Weuve wrote:
>
> > Niels,
> >
> > Yes, when I enter the exact same IP address as what's in the
> > PROXYADDR, it works.
> >
> > Delon
> >
> >
> > ________________________________________
> >
> > Delon E. Weuve
> > Senior Network Engineer
> > Office of Auditor of State
> > State of Iowa
> > United States of America
> >
> >
> > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>

> > Delon E. Weuve wrote:
> >
> > > Hello everyone,
> > >
> > > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> > >
> > > I used the CD media creator utility to modify the settings.txt
> > > file and added it to the bootcd.iso file and created a bootable
> > > CD. I looked at the settings.txt and bootcd.iso every step along
> > > the way and everything seems to be exactly the way I would expect
> > > it, until I boot up a computer off that CD.
> > >
> > > Then I get prompted for my imaging server.
> > >
> > > That is what the PROXYADDR is for, right?
> > >
> > > Any ideas??
> > >
> > > Delon

> >
> > After you burn the cd, does the setting.txt look alright?
> >
> > Yes, it should look like this:
> > #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> > Server. PROXYADDR=1.1.1.1
> >
> > If you write the IP (when prompted) of the PXE server the imaging
> > works, right?
> >
> > ‑‑
> >
> > ‑‑
> > Niels Poulsen
> >
> > Novell Knowledge Partner
> >
> >

> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> > ‑ ‑‑‑‑‑
> > A TRUE RED DEVIL

>
> And the settings.txt file on your cd looks right?
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> ‑ ‑‑‑‑‑
> A TRUE RED DEVIL


Okay, yes it looks okay.
During the imaging boot, try to hit ctrl‑alt‑F4 or ctrl‑alt‑F3 (not
sure which of them). This wil send you to the terminals where you can
see what it's doing in the process. Check to see if you can find the
part where it reads from the setting.txt file. Maby it comes with an
error doing so.
Let me know if you can't find it, then I'll try to explain better 🙂

‑‑

‑‑
Niels Poulsen

Novell Knowledge Partner

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑
A TRUE RED DEVIL


0 Likes
nop19832 Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Delon E. Weuve wrote:

> I found a reference to settings.txt in the boot sequence.
>
> The only two errors I found were Unknown error 132 right after the
> reference to settings.txt and an error that when DHCP was going where
> the DNS entry could not be found. Since I am using the IP address,
> I'm not surprised about the second error.
>
> Any idea what Unknown error 132 is??
>
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 2:12 PM >>>

> Delon E. Weuve wrote:
>
> > Niels,
> >
> > There are only three non‑commented lines in the settings.txt file:
> >
> > PARTITIONSIZE=150
> >
> > netsetup="dhcp,now,all"
> >
> > PROXYADDR=<My imaging server IP>
> >
> > The first two are defaults. The last one is correct as far as I
> > know...
> >
> > Delon
> >
> >
> > ________________________________________
> >
> > Delon E. Weuve
> > Senior Network Engineer
> > Office of Auditor of State
> > State of Iowa
> > United States of America
> >
> >
> > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 1:02 PM >>>

> > Delon E. Weuve wrote:
> >
> > > Niels,
> > >
> > > Yes, when I enter the exact same IP address as what's in the
> > > PROXYADDR, it works.
> > >
> > > Delon
> > >
> > >
> > > ________________________________________
> > >
> > > Delon E. Weuve
> > > Senior Network Engineer
> > > Office of Auditor of State
> > > State of Iowa
> > > United States of America
> > >
> > >
> > > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>
> > > Delon E. Weuve wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> > > >
> > > > I used the CD media creator utility to modify the settings.txt
> > > > file and added it to the bootcd.iso file and created a bootable
> > > > CD. I looked at the settings.txt and bootcd.iso every step along
> > > > the way and everything seems to be exactly the way I would
> > > > expect it, until I boot up a computer off that CD.
> > > >
> > > > Then I get prompted for my imaging server.
> > > >
> > > > That is what the PROXYADDR is for, right?
> > > >
> > > > Any ideas??
> > > >
> > > > Delon
> > >
> > > After you burn the cd, does the setting.txt look alright?
> > >
> > > Yes, it should look like this:
> > > #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> > > Server. PROXYADDR=1.1.1.1
> > >
> > > If you write the IP (when prompted) of the PXE server the imaging
> > > works, right?
> > >
> > > ‑‑
> > >
> > > ‑‑
> > > Niels Poulsen
> > >
> > > Novell Knowledge Partner
> > >
> > >

> >

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑�
> > �
> > > ‑ ‑‑‑‑‑
> > > A TRUE RED DEVIL

> >
> > And the settings.txt file on your cd looks right?
> >
> > ‑‑
> >
> > ‑‑
> > Niels Poulsen
> >
> > Novell Knowledge Partner
> >
> >

> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> > ‑ ‑‑‑‑‑
> > A TRUE RED DEVIL

>
> Okay, yes it looks okay.
> During the imaging boot, try to hit ctrl‑alt‑F4 or
> ctrl‑alt‑F3 (not sure which of them). This wil send you to the
> terminals where you can see what it's doing in the process. Check to
> see if you can find the part where it reads from the setting.txt
> file. Maby it comes with an error doing so.
> Let me know if you can't find it, then I'll try to explain better 🙂
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑�
> ��‑� ��‑‑‑‑‑
> A TRUE RED DEVIL


Is the WIFI adapter enabled? (Unknown error 132)
Perhaps there's a conflict... Do you have the problem on different
devices, hardware types?

If not, could you send me your bootcd.iso file?


--

--
Niels Poulsen

Novell Knowledge Partner

-------------------------------
A TRUE RED DEVIL

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
DWeuve Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

I have only tried this on one laptop, A Lenovo T500. Which is the same model
that I created the image I'm using from.

Both came up with the question.

I know the WiFi wasn't on when the image was created. Not so sure on the
destination laptop.


________________________________________

Delon E. Weuve
Senior Network Engineer
Office of Auditor of State
State of Iowa
United States of America


>>> Niels Poulsen<nop@viborg.dk> 4/24/2012 5:04 PM >>>

Delon E. Weuve wrote:

> I found a reference to settings.txt in the boot sequence.
>
> The only two errors I found were Unknown error 132 right after the
> reference to settings.txt and an error that when DHCP was going where
> the DNS entry could not be found. Since I am using the IP address,
> I'm not surprised about the second error.
>
> Any idea what Unknown error 132 is??
>
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 2:12 PM >>>

> Delon E. Weuve wrote:
>
> > Niels,
> >
> > There are only three non‑commented lines in the settings.txt file:
> >
> > PARTITIONSIZE=150
> >
> > netsetup="dhcp,now,all"
> >
> > PROXYADDR=<My imaging server IP>
> >
> > The first two are defaults. The last one is correct as far as I
> > know...
> >
> > Delon
> >
> >
> > ________________________________________
> >
> > Delon E. Weuve
> > Senior Network Engineer
> > Office of Auditor of State
> > State of Iowa
> > United States of America
> >
> >
> > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 1:02 PM >>>

> > Delon E. Weuve wrote:
> >
> > > Niels,
> > >
> > > Yes, when I enter the exact same IP address as what's in the
> > > PROXYADDR, it works.
> > >
> > > Delon
> > >
> > >
> > > ________________________________________
> > >
> > > Delon E. Weuve
> > > Senior Network Engineer
> > > Office of Auditor of State
> > > State of Iowa
> > > United States of America
> > >
> > >
> > > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>
> > > Delon E. Weuve wrote:
> > >
> > > > Hello everyone,
> > > >
> > > > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> > > >
> > > > I used the CD media creator utility to modify the settings.txt
> > > > file and added it to the bootcd.iso file and created a bootable
> > > > CD. I looked at the settings.txt and bootcd.iso every step along
> > > > the way and everything seems to be exactly the way I would
> > > > expect it, until I boot up a computer off that CD.
> > > >
> > > > Then I get prompted for my imaging server.
> > > >
> > > > That is what the PROXYADDR is for, right?
> > > >
> > > > Any ideas??
> > > >
> > > > Delon
> > >
> > > After you burn the cd, does the setting.txt look alright?
> > >
> > > Yes, it should look like this:
> > > #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> > > Server. PROXYADDR=1.1.1.1
> > >
> > > If you write the IP (when prompted) of the PXE server the imaging
> > > works, right?
> > >
> > > ‑‑
> > >
> > > ‑‑
> > > Niels Poulsen
> > >
> > > Novell Knowledge Partner
> > >
> > >

> >

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> >
> > > ‑ ‑‑‑‑‑
> > > A TRUE RED DEVIL

> >
> > And the settings.txt file on your cd looks right?
> >
> > ‑‑
> >
> > ‑‑
> > Niels Poulsen
> >
> > Novell Knowledge Partner
> >
> >

> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> > ‑ ‑‑‑‑‑
> > A TRUE RED DEVIL

>
> Okay, yes it looks okay.
> During the imaging boot, try to hit ctrl‑alt‑F4 or
> ctrl‑alt‑F3 (not sure which of them). This wil send you to the
> terminals where you can see what it's doing in the process. Check to
> see if you can find the part where it reads from the setting.txt
> file. Maby it comes with an error doing so.
> Let me know if you can't find it, then I'll try to explain better 🙂
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> ‑ ‑‑‑‑‑
> A TRUE RED DEVIL


Is the WIFI adapter enabled? (Unknown error 132)
Perhaps there's a conflict... Do you have the problem on different
devices, hardware types?

If not, could you send me your bootcd.iso file?


‑‑

‑‑
Niels Poulsen

Novell Knowledge Partner

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑
A TRUE RED DEVIL


0 Likes
nop19832 Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Delon E. Weuve wrote:

> I have only tried this on one laptop, A Lenovo T500. Which is the
> same model that I created the image I'm using from.
>
> Both came up with the question.
>
> I know the WiFi wasn't on when the image was created. Not so sure on
> the destination laptop.
>
>
> ________________________________________
>
> Delon E. Weuve
> Senior Network Engineer
> Office of Auditor of State
> State of Iowa
> United States of America
>
>
> >>> Niels Poulsen<nop@viborg.dk> 4/24/2012 5:04 PM >>>

> Delon E. Weuve wrote:
>
> > I found a reference to settings.txt in the boot sequence.
> >
> > The only two errors I found were Unknown error 132 right after the
> > reference to settings.txt and an error that when DHCP was going
> > where the DNS entry could not be found. Since I am using the IP
> > address, I'm not surprised about the second error.
> >
> > Any idea what Unknown error 132 is??
> >
> >
> >
> > ________________________________________
> >
> > Delon E. Weuve
> > Senior Network Engineer
> > Office of Auditor of State
> > State of Iowa
> > United States of America
> >
> >
> > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 2:12 PM >>>

> > Delon E. Weuve wrote:
> >
> > > Niels,
> > >
> > > There are only three non‑commented lines in the settings.txt
> > > file:
> > >
> > > PARTITIONSIZE=150
> > >
> > > netsetup="dhcp,now,all"
> > >
> > > PROXYADDR=<My imaging server IP>
> > >
> > > The first two are defaults. The last one is correct as far as I
> > > know...
> > >
> > > Delon
> > >
> > >
> > > ________________________________________
> > >
> > > Delon E. Weuve
> > > Senior Network Engineer
> > > Office of Auditor of State
> > > State of Iowa
> > > United States of America
> > >
> > >
> > > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 1:02 PM >>>
> > > Delon E. Weuve wrote:
> > >
> > > > Niels,
> > > >
> > > > Yes, when I enter the exact same IP address as what's in the
> > > > PROXYADDR, it works.
> > > >
> > > > Delon
> > > >
> > > >
> > > > ________________________________________
> > > >
> > > > Delon E. Weuve
> > > > Senior Network Engineer
> > > > Office of Auditor of State
> > > > State of Iowa
> > > > United States of America
> > > >
> > > >
> > > > >>> Niels Poulsen<nop@viborg.dk> 4/23/2012 12:34 PM >>>
> > > > Delon E. Weuve wrote:
> > > >
> > > > > Hello everyone,
> > > > >
> > > > > I'm got ZCM 11.2 installed on a Windows 2003 Standard server.
> > > > >
> > > > > I used the CD media creator utility to modify the settings.txt
> > > > > file and added it to the bootcd.iso file and created a
> > > > > bootable CD. I looked at the settings.txt and bootcd.iso
> > > > > every step along the way and everything seems to be exactly
> > > > > the way I would expect it, until I boot up a computer off
> > > > > that CD.
> > > > >
> > > > > Then I get prompted for my imaging server.
> > > > >
> > > > > That is what the PROXYADDR is for, right?
> > > > >
> > > > > Any ideas??
> > > > >
> > > > > Delon
> > > >
> > > > After you burn the cd, does the setting.txt look alright?
> > > >
> > > > Yes, it should look like this:
> > > > #PROXYADDR is the IP address or DNS name of the ZENworks Imaging
> > > > Server. PROXYADDR=1.1.1.1
> > > >
> > > > If you write the IP (when prompted) of the PXE server the
> > > > imaging works, right?
> > > >
> > > > ‑‑
> > > >
> > > > ‑‑
> > > > Niels Poulsen
> > > >
> > > > Novell Knowledge Partner
> > > >
> > > >
> > >

> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> > >
> > > > ‑ ‑‑‑‑‑
> > > > A TRUE RED DEVIL
> > >
> > > And the settings.txt file on your cd looks right?
> > >
> > > ‑‑
> > >
> > > ‑‑
> > > Niels Poulsen
> > >
> > > Novell Knowledge Partner
> > >
> > >

> >

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑�
> > �
> > > ‑ ‑‑‑‑‑
> > > A TRUE RED DEVIL

> >
> > Okay, yes it looks okay.
> > During the imaging boot, try to hit ctrl‑alt‑F4 or
> > ctrl‑alt‑F3 (not sure which of them). This wil send you to the
> > terminals where you can see what it's doing in the process. Check to
> > see if you can find the part where it reads from the setting.txt
> > file. Maby it comes with an error doing so.
> > Let me know if you can't find it, then I'll try to explain better 🙂
> >
> > ‑‑
> >
> > ‑‑
> > Niels Poulsen
> >
> > Novell Knowledge Partner
> >
> >

> ‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑
> > ‑ ‑‑‑‑‑
> > A TRUE RED DEVIL

>
> Is the WIFI adapter enabled? (Unknown error 132)
> Perhaps there's a conflict... Do you have the problem on different
> devices, hardware types?
>
> If not, could you send me your bootcd.iso file?
>
>
> ‑‑
>
> ‑‑
> Niels Poulsen
>
> Novell Knowledge Partner
>
>

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑�
> ��‑� ��‑‑‑‑‑
> A TRUE RED DEVIL


Could you try to boot on another type? Just to check if it's tha same
issue on all?

--

--
Niels Poulsen

Novell Knowledge Partner

-------------------------------
A TRUE RED DEVIL

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
nop19832 Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Delon E. Weuve,

You don't use the tuxera driver (tntfs)?
The boot file you sent me was not good, still on version 11.1 (sept.).
So before I test some more I just need to know if you have uploaded the
tuxera driver in zcc?

--

Niels Poulsen

Novell Knowledge Partner

-------------------------------
A TRUE RED DEVIL

-- Niels I have always liked... Cowabunga! If you find this post helpful, please show your appreciation by clicking on the star below. A member must be logged in before s/he can assign reputation points.
0 Likes
DWeuve Absent Member.
Absent Member.

Re: Getting prompted for server IP when I shouldn't be.....

Niels,

No, I have not.

And I don't know how to do that and what it does when we do...

Help me out here...?

Delon


________________________________________

Delon E. Weuve
Senior Network Engineer
Office of Auditor of State
State of Iowa
United States of America


>>> Niels Poulsen<nop@viborg.dk> 4/26/2012 4:50 AM >>>

Delon E. Weuve,

You don't use the tuxera driver (tntfs)?
The boot file you sent me was not good, still on version 11.1 (sept.).
So before I test some more I just need to know if you have uploaded the
tuxera driver in zcc?

‑‑

Niels Poulsen

Novell Knowledge Partner

‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑‑â
€‘‑‑‑‑‑
A TRUE RED DEVIL


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.