Network booting 100 computers

Tech-Archive recommends: Speed Up your PC by fixing your registry

anonymous_at_discussions.microsoft.com
Date: 06/03/04

  • Next message: Saaby: "Re: S L O W display!"
    Date: Thu, 3 Jun 2004 13:57:48 -0700
    
    

    Have you checked out BXP:

    www.vci.com

    >-----Original Message-----
    >The idea is to have around 100 mini computers all running
    XP embedded and
    >all booting from the network. I am currently running
    experiments booting up
    >from a wired network but the idea is to go wireless.
    >
    >
    >
    >So what's the problem you may wonder? Well, it takes
    quite some time to load
    >the image from the server to just one computer and I
    think that loading the
    >image to 100 computers is going to be slow as hell,
    specially because the
    >idea is to turn off all the computers after work and
    start them up the next
    >morning every day, this will probably overload the
    network traffic slowing
    >everything to a crawl.
    >
    >
    >
    >So my question is, since the Ethernet signal is
    broadcasted to all the
    >clients weather they use the packets of information or
    not (I think). Is
    >there a way to have all computers listen to the same
    signal and all loads
    >the OS in one shot instead of each individual system
    having a private
    >session with the Remote Boot Server? In other words, just
    like a speaker
    >talking to a crowd, the speaker only speaks once and
    everyone listens
    >instead of the speaker talking and saying the same thing
    individually to all
    >the people present.
    >
    >
    >.
    >


  • Next message: Saaby: "Re: S L O W display!"

    Relevant Pages

    • Re: Networks : Workgroups and Domains. How Do I Use Them?
      ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
      (microsoft.public.windowsxp.network_web)
    • Re: The Hard Problem for Behaviorists
      ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
      (sci.cognitive)
    • Re: {workgroup}"...is not accessible" after removing NWLINK
      ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
      (microsoft.public.windowsxp.network_web)
    • Help with 070-217
      ... The network contains 25,000 computers. ... single Windows 2000 domain named research.contoso.com. ... Server computers that are configured as domain controllers. ...
      (microsoft.public.cert.exam.mcse)
    • Re: Help with 070-217
      ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
      (microsoft.public.cert.exam.mcse)