Installation too slow

While not perhaps a flame it IS waste of time that has been posted to far
too many different newsgroups.

By and large Microsoft do not monitor public newsgroups so if you were
trying to get their attention you were doing this in vain.

As for the people who have read this post because they expected from the
Subject that it was a request for information on how to speed up an
installation (in my case a SharePoint installation because of the newsgroup
I read it in), well we've wasted our time too.

Engelbert

"Axel Dahmen" <> wrote in message
news:...
Hi,

my post may probably may interpreted as kind of a flame, which it is not
intended to be...

I notice a trend heading the wrong way and I see an urge to discuss this
with MS people: Installing/uninstalling MS software takes far too long.

As a developer I often need to install/uninstall operating systems and
Windows components. If it takes considerably more than an hour on a common
new machine to install Windows (2kS, 2k3S, Vista) then something's wrong.

Yesterday (night) it took almost an hour for me to install SPS, uninstall it
again and reinstalling using a different option (which I did by intention to
see the effect). Imagine: 60 Minutes for
installing/uninstalling/re-installing a single service component!

Most of the time a user can't even tell when the process is going to be
over. Many progress bars just "hang" at some stage for quite a while
(usually at 99%). The SPS component installation surprises with countless
progress dialogs, keeping the user utterly uninformed of the installation
progress.

MS, please consider a new approach to software deployment and installation
processes. Consider cutting down installation time by 75%. Installation of a
Windows OS should not take longer than 20 mins., a Windows component should
be ready to use within significantly less a minute.

TIA,
www.dashop.de
Axel Dahmen

Hi,
I honestly can't explain why but on two different computers and installing
Beta 2, RC1 , build 5728 and finally RC2, (all clean installs) the average
install time was less than 30 minutes.
--
Paul


"Engelbert" wrote:

> While not perhaps a flame it IS waste of time that has been posted to far
> too many different newsgroups.
>
> By and large Microsoft do not monitor public newsgroups so if you were
> trying to get their attention you were doing this in vain.
>
> As for the people who have read this post because they expected from the
> Subject that it was a request for information on how to speed up an
> installation (in my case a SharePoint installation because of the newsgroup
> I read it in), well we've wasted our time too.
>
> Engelbert
>
> "Axel Dahmen" <> wrote in message
> news:...
> Hi,
>
> my post may probably may interpreted as kind of a flame, which it is not
> intended to be...
>
> I notice a trend heading the wrong way and I see an urge to discuss this
> with MS people: Installing/uninstalling MS software takes far too long.
>
> As a developer I often need to install/uninstall operating systems and
> Windows components. If it takes considerably more than an hour on a common
> new machine to install Windows (2kS, 2k3S, Vista) then something's wrong.
>
> Yesterday (night) it took almost an hour for me to install SPS, uninstall it
> again and reinstalling using a different option (which I did by intention to
> see the effect). Imagine: 60 Minutes for
> installing/uninstalling/re-installing a single service component!
>
> Most of the time a user can't even tell when the process is going to be
> over. Many progress bars just "hang" at some stage for quite a while
> (usually at 99%). The SPS component installation surprises with countless
> progress dialogs, keeping the user utterly uninformed of the installation
> progress.
>
> MS, please consider a new approach to software deployment and installation
> processes. Consider cutting down installation time by 75%. Installation of a
> Windows OS should not take longer than 20 mins., a Windows component should
> be ready to use within significantly less a minute.
>
> TIA,
> www.dashop.de
> Axel Dahmen
>
>
>

That is so. I consistently get 27-28 minute install times for a clean
install. And I have a top of the line system - as per three year old specs.
It is lower middle road by current specs.

--

Regards,

Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

"PaulB" <> wrote in message
news:41D84CBB-89EF-43F0-B333-...
> Hi,
> I honestly can't explain why but on two different computers and installing
> Beta 2, RC1 , build 5728 and finally RC2, (all clean installs) the average
> install time was less than 30 minutes.
> --
> Paul
>
>
> "Engelbert" wrote:
>
>> While not perhaps a flame it IS waste of time that has been posted to
>> far
>> too many different newsgroups.
>>
>> By and large Microsoft do not monitor public newsgroups so if you were
>> trying to get their attention you were doing this in vain.
>>
>> As for the people who have read this post because they expected from the
>> Subject that it was a request for information on how to speed up an
>> installation (in my case a SharePoint installation because of the
>> newsgroup
>> I read it in), well we've wasted our time too.
>>
>> Engelbert
>>
>> "Axel Dahmen" <> wrote in message
>> news:...
>> Hi,
>>
>> my post may probably may interpreted as kind of a flame, which it is not
>> intended to be...
>>
>> I notice a trend heading the wrong way and I see an urge to discuss this
>> with MS people: Installing/uninstalling MS software takes far too long.
>>
>> As a developer I often need to install/uninstall operating systems and
>> Windows components. If it takes considerably more than an hour on a
>> common
>> new machine to install Windows (2kS, 2k3S, Vista) then something's wrong.
>>
>> Yesterday (night) it took almost an hour for me to install SPS, uninstall
>> it
>> again and reinstalling using a different option (which I did by intention
>> to
>> see the effect). Imagine: 60 Minutes for
>> installing/uninstalling/re-installing a single service component!
>>
>> Most of the time a user can't even tell when the process is going to be
>> over. Many progress bars just "hang" at some stage for quite a while
>> (usually at 99%). The SPS component installation surprises with countless
>> progress dialogs, keeping the user utterly uninformed of the installation
>> progress.
>>
>> MS, please consider a new approach to software deployment and
>> installation
>> processes. Consider cutting down installation time by 75%. Installation
>> of a
>> Windows OS should not take longer than 20 mins., a Windows component
>> should
>> be ready to use within significantly less a minute.
>>
>> TIA,
>> www.dashop.de
>> Axel Dahmen
>>
>>
>>

The .portalserver.development newsgroup for instance is for Programming
questions. Is this a programming question ? No, it's not.So the relevant SPS
newsgroup is the main .portalserver newsgroup.

As for posting to server.setup *and* a Vista newsgroup, isn't there a Vista
setup/install newsgroup? If there is then posting to the server.setup
newsgroup for a Vista issues is wrong too.

Stick to one newsgroup and you might possibly post to a relevant one - or is
your method to post to many newsgroups in the hope that one of those many
newsgroups is relevant

Engelbert

"Axel Dahmen" <> wrote in message
news:%...
I disagree.


> While not perhaps a flame it IS waste of time that has been posted to far
> too many different newsgroups.
> By and large Microsoft do not monitor public newsgroups so if you were
> trying to get their attention you were doing this in vain.

Microsoft people are in fact following the newsgroups. Perhaps not
officially. But give me one reason why they shouldn't on a casual basis and
I'll back-off.


> As for the people who have read this post because they expected from the
> Subject that it was a request for information on how to speed up an
> installation (in my case a SharePoint installation because of the
> newsgroup
> I read it in), well we've wasted our time too.

Please don't get out of focus that newsgroups are in fact a DISCUSSION
platform, not just a helpdesk. You may have wasted your time, why wasting it
replying? There might be others perceiving the same problem I have. And if
this is the case it should be considered important.

The reason for the newsgroups I've chosen is that there might be users
facing the same problems. There might even be Microsoft employees following
the threads. And it's definitively NOT been too many newsgroups, if such a
measurement even exists.

Regards,
Axel Dahmen

Hi,

my post may probably may interpreted as kind of a flame, which it is not intended to be...

I notice a trend heading the wrong way and I see an urge to discuss this with MS people: Installing/uninstalling MS software takes far too long.

As a developer I often need to install/uninstall operating systems and Windows components. If it takes considerably more than an hour on a common new machine to install Windows (2kS, 2k3S, Vista) then something's wrong.

Yesterday (night) it took almost an hour for me to install SPS, uninstall it again and reinstalling using a different option (which I did by intention to see the effect). Imagine: 60 Minutes for installing/uninstalling/re-installing a single service component!

Most of the time a user can't even tell when the process is going to be over. Many progress bars just "hang" at some stage for quite a while (usually at 99%). The SPS component installation surprises with countless progress dialogs, keeping the user utterly uninformed of the installation progress.

MS, please consider a new approach to software deployment and installation processes. Consider cutting down installation time by 75%. Installation of a Windows OS should not take longer than 20 mins., a Windows component should be ready to use within significantly less a minute.

TIA,
www.dashop.de
Axel Dahmen

I disagree.


> While not perhaps a flame it IS waste of time that has been posted to far
> too many different newsgroups.
> By and large Microsoft do not monitor public newsgroups so if you were
> trying to get their attention you were doing this in vain.

Microsoft people are in fact following the newsgroups. Perhaps not officially. But give me one reason why they shouldn't on a casual basis and I'll back-off.


> As for the people who have read this post because they expected from the
> Subject that it was a request for information on how to speed up an
> installation (in my case a SharePoint installation because of the newsgroup
> I read it in), well we've wasted our time too.

Please don't get out of focus that newsgroups are in fact a DISCUSSION platform, not just a helpdesk. You may have wasted your time, why wasting it replying? There might be others perceiving the same problem I have. And if this is the case it should be considered important.

The reason for the newsgroups I've chosen is that there might be users facing the same problems. There might even be Microsoft employees following the threads. And it's definitively NOT been too many newsgroups, if such a measurement even exists.

Regards,
Axel Dahmen

Hi, Paul,

I don't know. I'm running a 2,6THz machine with 512MB. Should be sufficient.

How about installing Windows components, like SPS service?

Regards,
Axel Dahmen


----------------------
"PaulB" <> schrieb im Newsbeitrag news:41D84CBB-89EF-43F0-B333-...
> Hi,
> I honestly can't explain why but on two different computers and installing
> Beta 2, RC1 , build 5728 and finally RC2, (all clean installs) the average
> install time was less than 30 minutes.
> --
> Paul

Oops, wrong keys... I guess I meant 2.6GHz...

Well, you might be right on the portalserver development group, Engelbert. It must have slipped my mind like the msnews newsgroup (hell, I don't know how this came in. Guess it'd been a long day)...

The audience I wanted to catch were/are:

microsoft.public.sharepoint.portalserver.developme nt
» Administrators installing SPS services on W2k3
(see case study in original post)

microsoft.public.windows.server.setup
» People having ever installed any windows server

microsoft.public.windows.vista.installation_setup
» Testers installing Windows Vista (not a server version yet)

These are all distinct target groups, wasting their time waiting for installers to accomplish their tasks, facing another day waiting for installations to finish. The question is: Is this my perspective only?

Regards,
Axel Dahmen

------------------

"Engelbert" <> schrieb im Newsbeitrag news:...
> The .portalserver.development newsgroup for instance is for Programming
> questions. Is this a programming question ? No, it's not.So the relevant SPS
> newsgroup is the main .portalserver newsgroup.
>
> As for posting to server.setup *and* a Vista newsgroup, isn't there a Vista
> setup/install newsgroup? If there is then posting to the server.setup
> newsgroup for a Vista issues is wrong too.
>
> Stick to one newsgroup and you might possibly post to a relevant one - or is
> your method to post to many newsgroups in the hope that one of those many
> newsgroups is relevant
>
> Engelbert
>
> "Axel Dahmen" <> wrote in message
> news:%...
> I disagree.
>
>
> > While not perhaps a flame it IS waste of time that has been posted to far
> > too many different newsgroups.
> > By and large Microsoft do not monitor public newsgroups so if you were
> > trying to get their attention you were doing this in vain.
>
> Microsoft people are in fact following the newsgroups. Perhaps not
> officially. But give me one reason why they shouldn't on a casual basis and
> I'll back-off.
>
>
> > As for the people who have read this post because they expected from the
> > Subject that it was a request for information on how to speed up an
> > installation (in my case a SharePoint installation because of the
> > newsgroup
> > I read it in), well we've wasted our time too.
>
> Please don't get out of focus that newsgroups are in fact a DISCUSSION
> platform, not just a helpdesk. You may have wasted your time, why wasting it
> replying? There might be others perceiving the same problem I have. And if
> this is the case it should be considered important.
>
> The reason for the newsgroups I've chosen is that there might be users
> facing the same problems. There might even be Microsoft employees following
> the threads. And it's definitively NOT been too many newsgroups, if such a
> measurement even exists.
>
> Regards,
> Axel Dahmen
>
>