Re: Setting specific IP address?
From: andy smart (anonymus_at_discussions.microsoft.com)
Date: 05/13/05
- Next message: DD: "Re: Google Warning..."
- Previous message: Michael Pelletier: "Re: Google Warning..."
- In reply to: Moe Trin: "Re: Setting specific IP address?"
- Next in thread: Jim Watt: "Re: Setting specific IP address?"
- Reply: Moe Trin: "Re: Setting specific IP address?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 13 May 2005 09:28:52 +0100
Moe Trin wrote:
> In article <d5vig4$laa$1@newsfeed.th.ifl.net>, andy smart wrote:
>
>>Moe Trin wrote:
>
>
>>>What is the difference in the effort to set up a static IP address on
>>>the DHCP (D is for Dynamic), then to set it on the host?
>
>
>>Actually, and of course I speak for me and my experience, its a lot
>>faster to do via DHCP (with reservations if required) than to set client
>>IP.
>
>
> For us, it's the difference between filling in three entries in a text file,
> and seven - seconds. Our network masks are standardized, so one need only
> look at the paperwork that comes with the system to get hostname and IP.
> The rest of the data is 'fingers on autopilot'. For an install or re-install,
> it's not even that much, as the install program (about a 250 line shell
> script) asks for the hostname, and does a lookup and then configures based
> on that.
>
>
>>We have 200+ stations here which often need rebuilding,
>
>
> The only systems we rebuild are those going in or out of the facility,
> which is extremely few.
>
>
>>I would say that most get a total re-installation at least once if not
>>twice a year.
>
>
> When we do a re-install, it always is a 'wipe and install' operation,
> as we do them as a security measure. But this effects well under one
> percent of the system in any given week.
>
>
>>I can start it going via PXE and go off and leave it knowing that it
>>will get its OS installed, all the apps deployed via AD and an IP
>>assigned via DHCP and I need not go back to it at any stage unless
>>something goes wrong!
>
>
> Installations aren't my regular job, but we're doing something similar.
> We install a floppy drive (only a handful of systems have a removable
> media drive - NONE of the workstations), and insert a floppy with the
> installer. It comes up on the net using an installation IP, connects to
> the file server, and just pours the bits straight to disk. Part of the
> initial setup asks for hostname (which it looks up to get parameters) and
> the type of install (workstation, <mumble>server, etc) and things are then
> pretty much automatic. The paperwork takes longer than the work at the
> keyboard. On new systems, the initial stage is slightly different,
> because the install guy does an inventory (serial numbers, etc.), and
> boots the system using a burn-in program (which is a heavy-duty compiling
> program to flog the hardware to limits) which is run for a minimum of 48
> hours to weed out the preme's..
>
>
>>I used to work somewhere where we used to do fixed IP, so we had to have
>>an accurate listing of which machines got which IP, then we had to set
>>them up one at a time;
>
>
> Part of the "customer service" our install crew does in to make and
> attach an embossed tape (Dymo) label on the upper left of each computer
> and monitor giving the hostname. As for accurate lists, thats why
> we run DNS which is updated by a 'makefile' from the central database.
> The registrar makes all the data entry into that as part of the system
> registration process (which serves a multitude of processes, including
> how the individual cost centers get billed for computer services).
>
>
>>they've now gone onto DHCP (they also now re-build every one of their
>>machines at least once a month which solves most of the problems we used
>>to have in my day)
>
>
> Cue the standard joke about how to fix any problem on a windoze box
> 'reboot', 'reload' 'reformat and reload' for increasing seriousness
> of the problem. We don't use windoze, so we don't have that problem.
>
> Old guy
LOL, actually we tend to miss the 'reload' stage on ours. We're a school
where anything can happen to our PCs, and frequently does. We've tried
everything we can possibly do to prevent them accessing the C drives,
but they still find ways to do which we can't disallow without stopping
XP working for example, they just keep pushing the damn envelope. We
can't use nice Dymo lables on ours, they keep peeling them off, we have
to use magic marker!
In one of our rooms of 31 workstations I did a complete re-install on 4
last week. We often do entire rooms during the vacation just to clear
any lingering issues. In our situation, and to be honest it's mainly
only in education where this happens, regular reinstalling is the only
way to go.
I'll look into some of your ways of doing stuff though, always
interested in seeing if something works for us better.
- Next message: DD: "Re: Google Warning..."
- Previous message: Michael Pelletier: "Re: Google Warning..."
- In reply to: Moe Trin: "Re: Setting specific IP address?"
- Next in thread: Jim Watt: "Re: Setting specific IP address?"
- Reply: Moe Trin: "Re: Setting specific IP address?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
