Installing Windows for Clients

Friction

New Member
Reaction score
0
I have installed numerous copies of most of the different versions of Windows as either an Upgrade or a Clean Install which I have no problem doing. But I would like to know what you guys do for your clients when installing it. Do you install Windows fully or do you install it like when you purchase a New PC from a retail store where you have to enter the PC Name, etc when you turn it on for the first time? If the latter, how do you go about doing so?
 
Hi there.

There is a huge number of threads on this subject on the forum, discussing the multiple ways of which windows is installed/reinstalled.

Can I firstly suggest that you use the search feature, and have a trawl through the forum first. Then read everything, and finally if you still have questions, don't hesitate to ask, and we will do our best to answer them fully for you.
 
I already did a search and couldn't find anything.

Perhaps you could link me to where I may find some of them?
 
It might have something to do with how old the copy of VBulletin is on this site. Perhaps an update is in order. This would certainly help with the search function as well as fix any unwanted security flaws.

Thanks for the link.
 
The quick answer is to use the manufacturers recovery partition where ever possible.
Then to remove all the associated software which comes bundled with it.

If you want to do it, where the client has to enter their name, and accept the eula, then look into oobe.
 
I'm talking about when we as system builders build a new system and the user is presented with the UELA when they switch on their PC for the first time.
Isn't OOBE part of the OEM OS installation?
 
I install fully/activate/all updates, etc. I will ask the client beforehand what name/password they want to use for the computer.
 
If you want the client to accept the EULA themselves when first turned on, then no. The OEM install will not do it.

OOBE is the only way of doing this.

Using the manu recovery partition / media, it will leave the machine at factory settings, ie all their assorted bumph, which we usually remove in any case - together with the usual trial versions of office, norton etc. Drivers could be outdated, windows updates will certainly be.

Dependant on how old said machine is, and the OS involved, there may well be 1-2 service packs to be installed.

I suppose it is possible, you could do all the work required, and then OOBE the machine again, if your so inclined.

You could also try slipstreaming any software into your installation media.
 
I install fully/activate/all updates, etc. I will ask the client beforehand what name/password they want to use for the computer.

But according to the System Builder license, don't you have to have the UELA screen appear on the screen for the client so they can choose to Agree/Disagree to it? Otherwise you have broken the license agreement?
 
But according to the System Builder license, don't you have to have the UELA screen appear on the screen for the client so they can choose to Agree/Disagree to it? Otherwise you have broken the license agreement?

This is true, you do need this. But you could always be acting on the clients behalf, and accepting it as such.
 
This is true, you do need this. But you could always be acting on the clients behalf, and accepting it as such.

Exactly. I don't get too caught up in all the legal mumbo jumbo...I mean, the client isn't going to read it anyway, and it must be accepted to use the computer. It's a legal catch 22 that MSoft lawyers have written into it to CYA...not COA. :rolleyes:
 
This is true, you do need this. But you could always be acting on the clients behalf, and accepting it as such.

Wouldn't that mean reading them the UELA over the phone to see if they agree/disagree? Surely you don't just ask them if they accept the UELA without reading it to them?
 
Exactly. I don't get too caught up in all the legal mumbo jumbo...I mean, the client isn't going to read it anyway, and it must be accepted to use the computer. It's a legal catch 22 that MSoft lawyers have written into it to CYA...not COA. :rolleyes:

Client's don't tend to read the EULA's, when they are installing ANY software. I mean look at all the malware out in the wild at the moment, because the client is simply going next, next, next. Not reading what they are actually installing.

So if they won't read what they are installing, then chances of them reading the EULA, is zip.
 
Exactly. I don't get too caught up in all the legal mumbo jumbo...I mean, the client isn't going to read it anyway, and it must be accepted to use the computer. It's a legal catch 22 that MSoft lawyers have written into it to CYA...not COA. :rolleyes:

I wouldn't want to do anything to jeapordize my business by not following the license correctly. A huge corporation like that would burn the little guys like us by not doing things by the book.
 
Wouldn't that mean reading them the UELA over the phone to see if they agree/disagree? Surely you don't just ask them if they accept the UELA without reading it to them?

You are acting as the clients agent in cases such as this.

Ergo, acting on their behalf, and in their best interests. Clients are paying us to get the job done as quickly and efficiently as possible.

As mentioned above, they don't read what they are installing, when it comes to free software. Yet alone the MS EULA. Which you need a honours degree in law to actually understand. Either that or take the EULA to a lawyer, and get them to go over it, and see if it's something they should agree to.

Putting it another way, if they don't agree to it, then they can't use their computer can they?
 
Client's don't tend to read the EULA's, when they are installing ANY software. I mean look at all the malware out in the wild at the moment, because the client is simply going next, next, next. Not reading what they are actually installing.

So if they won't read what they are installing, then chances of them reading the EULA, is zip.

You can't presume what a customer will do with the UELA! You have to according to the license present them with it.

So after linking me to that "Questions and Answers relating to Microsoft Licencing Guidelines" thread that you actually wrote, are you saying you don't follow the guidelines according to the license?
 
I'm not getting into any arguments here.

What I'm saying is what I myself do, on behalf of MY clients. What you do with yours, is entirely your business.

I know that the vast majority of clients DO NOT look at what they are installing when it comes to software. As mentioned, else why is, Conduit, Babylon, Search Protect, Delta etc so prevalent.

If they actually READ what they were agreeing to, malware jobs would be minimal.

Re the sticky I wrote. What I have wrote there is what is on the MS site verbatim. I'm certainly not saying that I don't follow the guidelines. I'm saying I do what is best for my clients.

It's not that I do a great amount of fresh installations, I try leaving that to the last resort. There are other ways of getting the machine back to better than factory settings, without resorting to a reinstall with each job.

On new machines I sell, I install windows, activate it, do ALL windows updates, install the software clients need, rather than the rubbish they don't, and then set up the OOBE for them.

They accept it, when they check the machine out, before it's boxed up for them, when they take it out of the workshop. As far as I'm concerned, I am covered.
 
Back
Top