Install win xp over a network

[Bandul]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom. I must install
win xp pro on every one.
Can i do that over a network.( got switch) or someting else.
Thanks.

 

[Dion]

You can install XP over a network but you usually need 3rd party software
like ghost , altiris deployment server(think you can try this one out for
free) or a RIS server.

Dion

 

[Some Guy]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom.

No cd drive? They're what, $30 now adays?

I must install win xp pro on every one.

Too bad. XP is a piece of shit. It's an over-managed, convoluted,
bloated operating system with no real benefits over Win-2K (or even
Win-98) for the typical office. It's a security nightmare from a
network point of view (we use netbuei for inter-office file sharing -
microsoft made it practically impossible to use netbuei on XP).

If the computers are exactly the same - same amount of memory, same
CPU, same hard drive (same make and model number), same motherboard,
then you might be able to make a master drive and clone it.

Go one step further and install all the apps (office, A/V software,
utilities like winzip, multi-media, flash, quicktime, etc). Then use
ghost and duplicate the drives.

Not having an optical drive (cd/dvd) will make it a little tougher to
have the clones pass the WPA activation, but if the computers really
are identical then you should have enough "votes" to get the clones to
pass the WPA.

You'll have to put a CD drive in the master system (just to install XP
from a CD).

These will have to be desk-top computers - not laptops (unless the
hard drives are removable).

 

[Synapse Syndrome]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom. I must install
win xp pro on every one.
Can i do that over a network.( got switch) or someting else.
Thanks.

I think you'll find what you need in the Resource Kit folder on the XP CD.

ss.

 

[Synapse Syndrome]

I think you'll find what you need in the Resource Kit folder on the XP CD.

ss.

Ok. Here are a couple of tutorials.

http://www.mcmcse.com/windows_xp/guides/additionalinstall.shtml

http://www.serverwatch.com/tutorials/article.php/1466511

This may be useful too.

http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/default.mspx

ss.

 

[Uncle-Fester]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom. I must install
win xp pro on every one.
Can i do that over a network.( got switch) or someting else.
Thanks.

If all identical build and install on one then ghost across the network
will take only a few minutes to drag across..

 

[X.Ray]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom. I must install
win xp pro on every one.
Can i do that over a network.( got switch) or someting else.
Thanks.
If all identical build and install on one then ghost across the network
will take only a few minutes to drag across..

Ghost is the way to go if all computers are identical
don't ya have to make 10 floppies and make sure the network drivers is all
setup properly
or is it more easier with Ghost 9

Will XP Install from the Harddrive folder..

 

[David Maynard]

No cd drive? They're what, $30 now adays?




Too bad. XP is a piece of shit. It's an over-managed, convoluted,
bloated operating system with no real benefits over Win-2K (or even
Win-98) for the typical office. It's a security nightmare from a
network point of view (we use netbuei for inter-office file sharing -
microsoft made it practically impossible to use netbuei on XP).

You can install netbeui on XP but the real problem is in using an
antiquated protocol that MS has told you should be migrated away from since
Windows 98.

 

[Synapse Syndrome]

You can install netbeui on XP but the real problem is in using an
antiquated protocol that MS has told you should be migrated away from
since Windows 98.

Yup.

http://www.practicallynetworked.com/sharing/troubleshoot/myths.htm

ss.

 

[Last Boy Scout]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom. I must install
win xp pro on every one.
Can i do that over a network.( got switch) or someting else.
Thanks.

why dont you just buy a cheap CDROM for $20.00 and just install it normally.

 

[Some Guy]

You can install netbeui on XP but the real problem is in using an
antiquated protocol that MS has told you should be migrated away
from since Windows 98.

Netbuie is non-routable and is a more secure protocal to use on a
mixed network where any given PC needs to have TCP/IP (for general
internet access) and also needs to access internal file shares (where
netbuie can be used without fear that those same shares can be
accessed from outside the network)

I've never read anything concrete that explains just what is wrong
with netbuie - other than Microsoft wanted to base all their new shit
on TCP and to hell with Netbuie (and it's security benefits). Some
on-line writeups recommend that you use netbuie for this reason, and
they say to use Win-2k netbuie DLL files on XP systems because of
problems with XP's version of netbuie.

We've never gotten XP to work properly on our network using netbuie,
so our servers and developer systems run either NT4 or Win-2K. XP is
just too much a piece of shit (configuration wise) to be worth using.

What microsoft wants in terms of product migration is because it
serves their revenue needs, not because their old stuff isin't good
enough or magically stops working. IT droids see the words
"unsupported" and run in fear like a bunch of lemmings to XP or 2003
or what-ever. Exactly what Macro$oft wants. Then everyone runs
around putting out security fires on the new stuff until it's stable
but by then it's time to get people to move to the next OS.

 

[Conor]

I've got 10 problems.
I bought 10 computers recent. Comp dont have a cd/dvd-rom. I must install
win xp pro on every one.
Can i do that over a network.( got switch) or someting else.
Thanks.

Buy a USB CDROM drive.

 

[kony]

You can install netbeui on XP but the real problem is in using an
antiquated protocol that MS has told you should be migrated away from since
Windows 98.

No, the problem is XP's networking. If anything, antiquated
protocols have been around so long there is simply no excuse
for problems from the OS.

MS does not "tell us" what to migrate away from. When they
give me a free PC then they can dictate what it uses, not
when it's listed as a "supported" feature.

 

[Keith Willcocks]

Buy a USB CDROM drive.

Or even an ordinary internal one and fit it in each machine for the duration
of the XP installation. It is only a 5 minute job.

 

[atec]

Ghost is the way to go if all computers are identical
don't ya have to make 10 floppies and make sure the network drivers is
all setup properly
or is it more easier with Ghost 9

Will XP Install from the Harddrive folder..

boot from floppy , make commands and copy image across , reboot . if I
can do it so can you , last time we did this was over a gig network in
an Internet cafe and averaged 10 minute installs with several running at
once .
total job took about 85 minutes for 40 machines ghosted.. good luck.

 

[David Maynard]

No, the problem is XP's networking. If anything, antiquated
protocols have been around so long there is simply no excuse
for problems from the OS.

MS does not "tell us" what to migrate away from. When they
give me a free PC then they can dictate what it uses, not
when it's listed as a "supported" feature.

That sounds so terribly 'consumer noble' but the fact of the matter is
there's no good reason to support an antiquated protocol.

 

[David Maynard]

David Maynard wrote:




Netbuie is non-routable

Which is one reason why it is of limited use and not worth supporting.

and is a more secure protocal to use on a
mixed network where any given PC needs to have TCP/IP (for general
internet access) and also needs to access internal file shares (where
netbuie can be used without fear that those same shares can be
accessed from outside the network)

TCP/IP can also be used 'without fear' when set up properly.

You can also use IPX.

I've never read anything concrete that explains just what is wrong
with netbuie

You just listed one. It's non-routable.

- other than Microsoft wanted to base all their new shit
on TCP and to hell with Netbuie (and it's security benefits). Some
on-line writeups recommend that you use netbuie for this reason, and
they say to use Win-2k netbuie DLL files on XP systems because of
problems with XP's version of netbuie.

One can find all sorts of nonsense on web sites.

We've never gotten XP to work properly on our network using netbuie,
so our servers and developer systems run either NT4 or Win-2K. XP is
just too much a piece of shit (configuration wise) to be worth using.

The point was there's no valid reason to use it in the first place.

What microsoft wants in terms of product migration is because it
serves their revenue needs, not because their old stuff isin't good
enough or magically stops working. IT droids see the words
"unsupported" and run in fear like a bunch of lemmings to XP or 2003
or what-ever.

You're free to run unsupported software if you like.

Exactly what Macro$oft wants. Then everyone runs
around putting out security fires on the new stuff until it's stable
but by then it's time to get people to move to the next OS.

We shoot, man, stay with WFW 3.11. Using your logic it must be stable as
hell by now.

 

[kony]

That sounds so terribly 'consumer noble' but the fact of the matter is
there's no good reason to support an antiquated protocol.

Define support.

There is no good reason NOT to support it to the extent that
it works. There is no good reason not to support ANY
protocol, even one completely home-grown, to the extend that
it installs in same manner and is supported though whatever
features it, itself, supports in a standardized manner.

Perhaps it's only antiquated in your and MS's minds.
Certainly not so to anyone who uses it. That doesn't even
begin to mean someone else shouldn't use something that
suits their needs more than your own personal alternative
would.

The fact of the matter is that the main benefit of TCP/IP is
that it's routable.. Once you remove that need, you're left
with a slower protocol.

 

[David Maynard]

Define support.

There is no good reason NOT to support it to the extent that
it works. There is no good reason not to support ANY
protocol, even one completely home-grown, to the extend that
it installs in same manner and is supported though whatever
features it, itself, supports in a standardized manner.

That is simply silly. 'Support', of any kind, costs time and effort and
when the return doesn't justify it then one doesn't do it.

Perhaps it's only antiquated in your and MS's minds.

It's antiquated by comparing it's capabilities to the alternatives.

Certainly not so to anyone who uses it.

Neither are buggy whips, to those who 'use them'. but there's little reason
to 'support' them in "horseless carriages."

That doesn't even
begin to mean someone else shouldn't use something that
suits their needs more than your own personal alternative
would.

They're free to use it. They'll just have to provide their own 'support',
or a third party who might be interested.

The fact of the matter is that the main benefit of TCP/IP is
that it's routable..

Ain't no 'little' thing.

Not to mention it's universally supported across virtually every platform
on the planet instead of a single O.S..

Once you remove that need, you're left
with a slower protocol.

Remove it and you've got an antiquated, severely limited, protocol.

 

[Black Adder]

Mate, your a dead-set idiot if you think 98 and 2000 are better than XP.
Windows XP has got more functionallity, better communications and runs
faster than those OS's.

There are only security issues when the I.T. bloke can't secure the network
properly. Anyone today who buys a windows 98 or windows 2000 network and
uses network procedures from the mid 90's already has a security nightmare!
GO BACK TO SCHOOL!