Re: Tip to improve network ready time
From: KM (konstmor_at_nospam_yahoo.com)
Date: 02/18/05
- Next message: KM: "Re: Cannot connect to xpe device"
- Previous message: Doug Hoeffel: "Re: NFTS problems in XPe (What are reserved clusters?)"
- In reply to: Roger Levy: "Re: Tip to improve network ready time"
- Next in thread: Roger Levy: "Re: Tip to improve network ready time"
- Reply: Roger Levy: "Re: Tip to improve network ready time"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Feb 2005 12:05:33 -0800
Roger,
I am not sure why we are having this discussion. You are the one who created the image and you certainly know more about what's
included there than I do. You also have the control over what is launched (FBA phases, Reseal, Shell app, manual launch).
Forget about Start button. Can you launch CMD just before the reseal through FBA Generic Command (at a phase between 8500 and 12000)
?
--
Regards,
KM, BSquare Corp.
> KM,
> I don't see what you apparently see. I am looking at a screen right now on
> a target device that has just completed FBA. The screen is light blue and
> there is some branding and version text at the lower right. There are two
> popup windows. One is titled "First Boot Agent" and it has an empty
> progress bar labeled "Installing Components..." The other is titled
> "FBReseal" and it includes the message "Machine Resealed! Click OK to
> reboot" and there is an OK button. There is absolutely nothing else -- no
> Start button or CMD window to switch to. So I don't know how I could
> execute an "ipconfig /release" from this screen. Note that I do have CMD
> and ipconfig in my configuration.
>
> Roger
>
> "KM" <konstmor@nospam_yahoo.com> wrote in message
> news:%23qkbaPVFFHA.2564@tk2msftngp13.phx.gbl...
> > Roger,
> >
> > If you got CMD in your image, and it sounded you did, you won't have
> > problems running ipconfig /release from there. You will just
> > need to switch to the CMD window when you see the mentioned message box.
> > When you are done with CMD and ipconfig, switch back to the
> > message box and press OK button there.
> >
> > If you don't have ipconfig in your image, just copy it over to the image
> > from XPe repository or add appropriate component. Likely
> > you have already got all the component's required dependencies in your
> > image.
> >
> > --
> > Regards,
> > KM
> >
> >> Hmmm ... I don't remember that I have a Start button or any other way to
> >> launch
> >> a command window but I'll have to check tomorrow -- it's getting late
> >> now.
> >> Maybe I don't have those elements because I build a relatively light
> >> weight
> >> system (by Microsoft standards, not MY embedded system standards) based
> >> on
> >> minlogon and command shell with no explorer, etc.
> >>
> >> Roger
> >>
> >> KM wrote:
> >> >
> >> > Roger,
> >> >
> >> > No, I was not referring to anything very custom but rather just a
> >> > little hack during the procedure. See below..
> >> >
> >> > > Please describe to me exactly how I would issue the "ipconfig
> >> > > /release" because
> >> > > perhaps due to my relative inexperience I don't see an opportunity to
> >> > > do so.
> >> > > When I execute FBA, my target goes through several steps such as
> >> > > installing
> >> > > network components, installing PnP devices, registering components,
> >> > > etc. then it
> >> > > automatically reboots. The next phase is shorter and it ends with a
> >> > > message box
> >> > > for me to click in order to reboot and
> >> >
> >> > Before you click on in that box, can you launch CMD in parallel and
> >> > type "ipconfig /release" there? (or use Start-->Run if it is
> >> > there)
> >> > Then, when the ipconfig and done, click OK in that message box
> >> > immidiately.
> >> > I suppose the XP Network Media Sense mode is on (by default) on your
> >> > image and if you give it too much time, DHCP client service
> >> > will grab new IP after 5 minutes.
> >> >
> >> > --
> >> > Regards,
> >> > KM
> >> >
> >> > > that's when I return to the development
> >> > > environment to create my .sdi, etc. There is no phase of this
> >> > > process that
> >> > > allows me to enter a command so I imagine you are referring to some
> >> > > optional
> >> > > procedure with which I am not familiar. Maybe you are talking about
> >> > > allowing
> >> > > the target to boot a 3rd time, executing the command, and then doing
> >> > > fbresal?
> >> > >
> >> > > Roger
> >> > >
> >> > > KM wrote:
> >> > > >
> >> > > > Roger,
> >> > > >
> >> > > > Just for my knowledge... With APIPA and DHCP enabled, does the
> >> > > > delay on the "first ater cloning" boot occur if you do
> > "ipconfig
> >> > > > /release" just before the cloning (before shutting down the machine
> >> > > > to capture the golden image)?
> >> > > >
> >> > > > --
> >> > > > Regards,
> >> > > > KM
> >> > > >
> >> > > > > I've been sniffing DHCP messages and I have a tip that I haven't
> >> > > > > seen before.
> >> > > > > I'd appreciate if some real experts can comment on my
> >> > > > > observations.
> >> > > > >
> >> > > > > For a networked device that you will clone you should:
> >> > > > > 1. Disable APIPA for the entire computer as described in KB244268
> >> > > > > by adding
> >> > > > > Extra Registry Data to your configuration.
> >> > > > > 2. Execute FBA with all ethernet cables disconnected, or more
> >> > > > > prescisely with no
> >> > > > > DHCP server available.
> >> > > > >
> >> > > > > If you have DHCP available during FBA your target will get a
> >> > > > > valid DHCP address
> >> > > > > and it will "remember" this address such that after deployment
> >> > > > > every machine
> >> > > > > will ask for this address in its initial DHCP Discover message.
> >> > > > > At best only
> >> > > > > one machine can get the address and if the development network is
> >> > > > > different than
> >> > > > > the deployed network, no machines are likely to be able to get
> >> > > > > that address.
> >> > > > > See below for a comparable description of what happens in this
> >> > > > > case.
> >> > > > >
> >> > > > > If you do not have DHCP available during deployment but you do
> >> > > > > not disable APIPA
> >> > > > > then your target will ask for a 169.254.x.y address in its
> >> > > > > initial DHCP Discover
> >> > > > > message. I observed the following DHCP message scenario in this
> >> > > > > case (SP2):
> >> > > > > Client Discover with 169.254.x.y requested
> >> > > > > Server Offer with different address
> >> > > > > Client waits 15 seconds
> >> > > > > Client Discover with 169.254.x.y requested
> >> > > > > Server Offer with different address
> >> > > > > Client waits 35 seconds
> >> > > > > Client Discover with no specific address requested
> >> > > > > Server Offer with an address
> >> > > > > Client accepts address, protocol completes
> >> > > > >
> >> > > > > This protocol sequence wastes 50 seconds before the network is
> >> > > > > ready that are
> >> > > > > not wasted if you follow the 2 steps I recommended.
> >> > > > >
> >> > > > > Roger
> >> > > > > --
> >> > > > > Change "3e" in my address to "eee"
> >
> >
>
>
- Next message: KM: "Re: Cannot connect to xpe device"
- Previous message: Doug Hoeffel: "Re: NFTS problems in XPe (What are reserved clusters?)"
- In reply to: Roger Levy: "Re: Tip to improve network ready time"
- Next in thread: Roger Levy: "Re: Tip to improve network ready time"
- Reply: Roger Levy: "Re: Tip to improve network ready time"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|