Office 2007 beta uninstall

R

Ray Kilham

Help!!!!!!!

I have uninstalled the above as per Microsfts details, but when I go to
install a full copy of Office 2007 the system will not let me as its says the
betra version is not removed.

I have also removed the "office12" folders for the shared files and all
references as far as I could if to "Office12" in the registry, can any one
help please.

Ray
 
M

Milly Staples [MVP - Outlook]

Do not multi-post. See your answer in microsoft.public.office.misc

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Ray Kilham asked:

| Help!!!!!!!
|
| I have uninstalled the above as per Microsfts details, but when I go
| to install a full copy of Office 2007 the system will not let me as
| its says the betra version is not removed.
|
| I have also removed the "office12" folders for the shared files and
| all references as far as I could if to "Office12" in the registry,
| can any one help please.
|
| Ray
 
M

Milly Staples [MVP - Outlook]

Do not multi-post. See your answer in microsoft.public.office.misc

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, Ray Kilham asked:

| Help!!!!!!!
|
| I have uninstalled the above as per Microsfts details, but when I go
| to install a full copy of Office 2007 the system will not let me as
| its says the betra version is not removed.
|
| I have also removed the "office12" folders for the shared files and
| all references as far as I could if to "Office12" in the registry,
| can any one help please.
|
| Ray
 
I

ilv-m

Since this is the Office installation topic, would you kindly post the answer
here? This is not a 'misc' type of issue, but a show-stopper for us too.
We're glad to see that so many others want this Office 2007 installer defect
fixed so that hopefully Microsoft will either do that, or provide an
automated clean-up tool to deal with the problem.

The extremely time-consuming manual steps described in the KB's about this
problem are ridiculous. The people with the info to write the steps into a KB
should have incorporated the clean-up in the Office 2007 RTM installer, or
provided an Office 2007 beta wipe-down tool to make sure that Microsoft's
best and brightest customers are not angered by this kind of sloppiness.
Business is being lost as we and our customers wait for a reasonable
solution. The competition for a botched Office 2007 release is to do nothing
but stand on Office 2003.

If we were flying in Microsoft-designed aircraft, with such poor quality
control, we would probably all be dead.
 
I

ilv-m

Since this is the Office installation topic, would you kindly post the answer
here? This is not a 'misc' type of issue, but a show-stopper for us too.
We're glad to see that so many others want this Office 2007 installer defect
fixed so that hopefully Microsoft will either do that, or provide an
automated clean-up tool to deal with the problem.

The extremely time-consuming manual steps described in the KB's about this
problem are ridiculous. The people with the info to write the steps into a KB
should have incorporated the clean-up in the Office 2007 RTM installer, or
provided an Office 2007 beta wipe-down tool to make sure that Microsoft's
best and brightest customers are not angered by this kind of sloppiness.
Business is being lost as we and our customers wait for a reasonable
solution. The competition for a botched Office 2007 release is to do nothing
but stand on Office 2003.

If we were flying in Microsoft-designed aircraft, with such poor quality
control, we would probably all be dead.
 
B

Bob Buckland ?:-\)

There isn't a tool for uninstalling the Office 2007 betas as there were a number of them going on (including the sister product, MS
Expression web) at the same time and there is a large number of possible combinations that could be in play.

When the beta isn't removed through normal procedures, add-remove programs, it's often because the installation was already broken.
If you review the Knowledge Base articles for steps to remove a broken 'regular' Office installation manually they're not far
different. Broken installations come from adding other software or add-ins over time or using utilities such as computer 'speedup'
or 'registry cleaner' ones that are 'helping'.

There is a risk to relying on time limited beta software, although it is easy to get used to using it and forgetting it's 'test
software'.

For many people the basic steps in the MSKB article, removing all prior betas and related add-ins, from Add/Remove Programs in the
Windows control panel, do work to have a clean environment to install the release version of MS Office 2007. It is the quality of
operation that is one of the prime reasons for starting clean with release software rather than focusing on 'upgrading' a beta/test
software.

=================
Since this is the Office installation topic, would you kindly post the answer
here? This is not a 'misc' type of issue, but a show-stopper for us too.
We're glad to see that so many others want this Office 2007 installer defect
fixed so that hopefully Microsoft will either do that, or provide an
automated clean-up tool to deal with the problem.

The extremely time-consuming manual steps described in the KB's about this
problem are ridiculous. The people with the info to write the steps into a KB
should have incorporated the clean-up in the Office 2007 RTM installer, or
provided an Office 2007 beta wipe-down tool to make sure that Microsoft's
best and brightest customers are not angered by this kind of sloppiness.
Business is being lost as we and our customers wait for a reasonable
solution. The competition for a botched Office 2007 release is to do nothing
but stand on Office 2003.

If we were flying in Microsoft-designed aircraft, with such poor quality control, we would probably all be dead. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*
 
B

Bob Buckland ?:-\)

There isn't a tool for uninstalling the Office 2007 betas as there were a number of them going on (including the sister product, MS
Expression web) at the same time and there is a large number of possible combinations that could be in play.

When the beta isn't removed through normal procedures, add-remove programs, it's often because the installation was already broken.
If you review the Knowledge Base articles for steps to remove a broken 'regular' Office installation manually they're not far
different. Broken installations come from adding other software or add-ins over time or using utilities such as computer 'speedup'
or 'registry cleaner' ones that are 'helping'.

There is a risk to relying on time limited beta software, although it is easy to get used to using it and forgetting it's 'test
software'.

For many people the basic steps in the MSKB article, removing all prior betas and related add-ins, from Add/Remove Programs in the
Windows control panel, do work to have a clean environment to install the release version of MS Office 2007. It is the quality of
operation that is one of the prime reasons for starting clean with release software rather than focusing on 'upgrading' a beta/test
software.

=================
Since this is the Office installation topic, would you kindly post the answer
here? This is not a 'misc' type of issue, but a show-stopper for us too.
We're glad to see that so many others want this Office 2007 installer defect
fixed so that hopefully Microsoft will either do that, or provide an
automated clean-up tool to deal with the problem.

The extremely time-consuming manual steps described in the KB's about this
problem are ridiculous. The people with the info to write the steps into a KB
should have incorporated the clean-up in the Office 2007 RTM installer, or
provided an Office 2007 beta wipe-down tool to make sure that Microsoft's
best and brightest customers are not angered by this kind of sloppiness.
Business is being lost as we and our customers wait for a reasonable
solution. The competition for a botched Office 2007 release is to do nothing
but stand on Office 2003.

If we were flying in Microsoft-designed aircraft, with such poor quality control, we would probably all be dead. >>
--

Bob Buckland ?:)
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*
 
I

ilv-m

If this is the best that Microsoft can offer, we won't risk the liability of
any Office 2007 upgrade recommendations to anyone. We will depend on
customers to insist on taking the risk on a time & materials basis.

Wiping all systems down and starting over from scratch with new OS
installations and all application software is financially acceptable to very
few.

Why is Windows sooooo very poorly designed that software upgrades are not as
clean as they once were before the abomination of the registry was
introduced? Why does Microsoft still use hierarchical database technology
that virtually everyone else threw out in the 1960's because it was known by
then how completely out of control such databases can get.

It's no wonder that Windows is a heaving, hulking, unreliable pile of
garbage since it depends so desperately on an absolute disaster of a
hierarchical database in the form of the registry hives.

Would someone at Microsoft please justify why their product line is such a
tangled mess that new system software images being built up from scratch with
many applications may take DAYS to assemble--and after they are built are so
unbelievably fragile? How can this be the best that the software world has
to offer when we all should know very well how far short of best-practices
the whole Microsoft approach has become?

Microsoft in this area seems to have become far worse than IBM ever was at
its most arrogant market-dominating point.
 
I

ilv-m

If this is the best that Microsoft can offer, we won't risk the liability of
any Office 2007 upgrade recommendations to anyone. We will depend on
customers to insist on taking the risk on a time & materials basis.

Wiping all systems down and starting over from scratch with new OS
installations and all application software is financially acceptable to very
few.

Why is Windows sooooo very poorly designed that software upgrades are not as
clean as they once were before the abomination of the registry was
introduced? Why does Microsoft still use hierarchical database technology
that virtually everyone else threw out in the 1960's because it was known by
then how completely out of control such databases can get.

It's no wonder that Windows is a heaving, hulking, unreliable pile of
garbage since it depends so desperately on an absolute disaster of a
hierarchical database in the form of the registry hives.

Would someone at Microsoft please justify why their product line is such a
tangled mess that new system software images being built up from scratch with
many applications may take DAYS to assemble--and after they are built are so
unbelievably fragile? How can this be the best that the software world has
to offer when we all should know very well how far short of best-practices
the whole Microsoft approach has become?

Microsoft in this area seems to have become far worse than IBM ever was at
its most arrogant market-dominating point.
 
M

Milly Staples [MVP - Outlook]

First question for you is why you ignored all the warnings and ran beta software on a production machine in direct violation of the Licensing agreement that accompanied the beta?

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, ilv-m asked:

| If this is the best that Microsoft can offer, we won't risk the
| liability of any Office 2007 upgrade recommendations to anyone. We
| will depend on customers to insist on taking the risk on a time &
| materials basis.
|
| Wiping all systems down and starting over from scratch with new OS
| installations and all application software is financially acceptable
| to very few.
|
| Why is Windows sooooo very poorly designed that software upgrades are
| not as clean as they once were before the abomination of the registry
| was introduced? Why does Microsoft still use hierarchical database
| technology that virtually everyone else threw out in the 1960's
| because it was known by then how completely out of control such
| databases can get.
|
| It's no wonder that Windows is a heaving, hulking, unreliable pile of
| garbage since it depends so desperately on an absolute disaster of a
| hierarchical database in the form of the registry hives.
|
| Would someone at Microsoft please justify why their product line is
| such a tangled mess that new system software images being built up
| from scratch with many applications may take DAYS to assemble--and
| after they are built are so unbelievably fragile? How can this be
| the best that the software world has to offer when we all should know
| very well how far short of best-practices the whole Microsoft
| approach has become?
|
| Microsoft in this area seems to have become far worse than IBM ever
| was at its most arrogant market-dominating point.
|
|
| "Bob Buckland ?:)" wrote:
|
|| There isn't a tool for uninstalling the Office 2007 betas as there
|| were a number of them going on (including the sister product, MS
|| Expression web) at the same time and there is a large number of
|| possible combinations that could be in play.
||
|| When the beta isn't removed through normal procedures, add-remove
|| programs, it's often because the installation was already broken. If
|| you review the Knowledge Base articles for steps to remove a broken
|| 'regular' Office installation manually they're not far different.
|| Broken installations come from adding other software or add-ins over
|| time or using utilities such as computer 'speedup' or 'registry
|| cleaner' ones that are 'helping'.
||
|| There is a risk to relying on time limited beta software, although
|| it is easy to get used to using it and forgetting it's 'test
|| software'.
||
|| For many people the basic steps in the MSKB article, removing all
|| prior betas and related add-ins, from Add/Remove Programs in the
|| Windows control panel, do work to have a clean environment to
|| install the release version of MS Office 2007. It is the quality of
|| operation that is one of the prime reasons for starting clean with
|| release software rather than focusing on 'upgrading' a beta/test
|| software.
||
|| =================
||
|| Since this is the Office installation topic, would you kindly post
|| the answer
|| here? This is not a 'misc' type of issue, but a show-stopper for us
|| too.
|| We're glad to see that so many others want this Office 2007
|| installer defect
|| fixed so that hopefully Microsoft will either do that, or provide an
|| automated clean-up tool to deal with the problem.
||
|| The extremely time-consuming manual steps described in the KB's
|| about this
|| problem are ridiculous. The people with the info to write the steps
|| into a KB
|| should have incorporated the clean-up in the Office 2007 RTM
|| installer, or
|| provided an Office 2007 beta wipe-down tool to make sure that
|| Microsoft's
|| best and brightest customers are not angered by this kind of
|| sloppiness.
|| Business is being lost as we and our customers wait for a reasonable
|| solution. The competition for a botched Office 2007 release is to do
|| nothing
|| but stand on Office 2003.
||
|| If we were flying in Microsoft-designed aircraft, with such poor
|| quality control, we would probably all be dead. >> --
||
|| Bob Buckland ?:)
|| MS Office System Products MVP
||
|| *Courtesy is not expensive and can pay big dividends*
 
M

Milly Staples [MVP - Outlook]

First question for you is why you ignored all the warnings and ran beta software on a production machine in direct violation of the Licensing agreement that accompanied the beta?

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, ilv-m asked:

| If this is the best that Microsoft can offer, we won't risk the
| liability of any Office 2007 upgrade recommendations to anyone. We
| will depend on customers to insist on taking the risk on a time &
| materials basis.
|
| Wiping all systems down and starting over from scratch with new OS
| installations and all application software is financially acceptable
| to very few.
|
| Why is Windows sooooo very poorly designed that software upgrades are
| not as clean as they once were before the abomination of the registry
| was introduced? Why does Microsoft still use hierarchical database
| technology that virtually everyone else threw out in the 1960's
| because it was known by then how completely out of control such
| databases can get.
|
| It's no wonder that Windows is a heaving, hulking, unreliable pile of
| garbage since it depends so desperately on an absolute disaster of a
| hierarchical database in the form of the registry hives.
|
| Would someone at Microsoft please justify why their product line is
| such a tangled mess that new system software images being built up
| from scratch with many applications may take DAYS to assemble--and
| after they are built are so unbelievably fragile? How can this be
| the best that the software world has to offer when we all should know
| very well how far short of best-practices the whole Microsoft
| approach has become?
|
| Microsoft in this area seems to have become far worse than IBM ever
| was at its most arrogant market-dominating point.
|
|
| "Bob Buckland ?:)" wrote:
|
|| There isn't a tool for uninstalling the Office 2007 betas as there
|| were a number of them going on (including the sister product, MS
|| Expression web) at the same time and there is a large number of
|| possible combinations that could be in play.
||
|| When the beta isn't removed through normal procedures, add-remove
|| programs, it's often because the installation was already broken. If
|| you review the Knowledge Base articles for steps to remove a broken
|| 'regular' Office installation manually they're not far different.
|| Broken installations come from adding other software or add-ins over
|| time or using utilities such as computer 'speedup' or 'registry
|| cleaner' ones that are 'helping'.
||
|| There is a risk to relying on time limited beta software, although
|| it is easy to get used to using it and forgetting it's 'test
|| software'.
||
|| For many people the basic steps in the MSKB article, removing all
|| prior betas and related add-ins, from Add/Remove Programs in the
|| Windows control panel, do work to have a clean environment to
|| install the release version of MS Office 2007. It is the quality of
|| operation that is one of the prime reasons for starting clean with
|| release software rather than focusing on 'upgrading' a beta/test
|| software.
||
|| =================
||
|| Since this is the Office installation topic, would you kindly post
|| the answer
|| here? This is not a 'misc' type of issue, but a show-stopper for us
|| too.
|| We're glad to see that so many others want this Office 2007
|| installer defect
|| fixed so that hopefully Microsoft will either do that, or provide an
|| automated clean-up tool to deal with the problem.
||
|| The extremely time-consuming manual steps described in the KB's
|| about this
|| problem are ridiculous. The people with the info to write the steps
|| into a KB
|| should have incorporated the clean-up in the Office 2007 RTM
|| installer, or
|| provided an Office 2007 beta wipe-down tool to make sure that
|| Microsoft's
|| best and brightest customers are not angered by this kind of
|| sloppiness.
|| Business is being lost as we and our customers wait for a reasonable
|| solution. The competition for a botched Office 2007 release is to do
|| nothing
|| but stand on Office 2003.
||
|| If we were flying in Microsoft-designed aircraft, with such poor
|| quality control, we would probably all be dead. >> --
||
|| Bob Buckland ?:)
|| MS Office System Products MVP
||
|| *Courtesy is not expensive and can pay big dividends*
 
I

ilv-m

Just why the condescending arrogance? So often the only reason to bother with
these 'support' forums is to prove to customers just how awful the attitudes
are inside Microsoft and their close circle of sycophants.

How many times do we have to drive this point home---they are test machines
for both us and the customers. Yes they can be wiped down and/or rolled back
to get rid of every trace of Office 2007 beta, but that wastes a great deal
of time and money due to other software that we are also testing internally
and at customer sites on those systems. Roll-backs would be just as
destructive to testing under way as full system restores.

We really have to wonder if any of those representing the Microsoft line on
these forums has any commercial IT operations experience whatsoever!

Why is it so hard to understand that we expect the Microsoft installation
code to hold its own and not trip over tiny cracks in the pavement. Why
should we trust a product line when the installer component is such a piece
of junk?

I can state for the record that with the Exchange 2000 release and the way
that it could utterly destroy Windows domains due to numerous installer code
bugs, we finally gave up on that product line and migraded ourselves and all
further email systems installations over to standards-based IMAP-based
products. They are far more scalable and far more stable. Now we are thankful
in a way that Microsoft bombed that release so badly that we are running on
email server software that is so operationally superior.

If we had something to recommend besides Office 2007, we would be doing that
now as well. So since this kind of derrogatory dismissive 'support' from its
MVPs is all that Microsoft has to offer in public, rather than fix their
design mistake, it's just easier to reject the upgrade for now and keep
customers at Office 2003 plus more third-party software.



Milly Staples said:
First question for you is why you ignored all the warnings and ran beta software on a production machine in direct violation of the Licensing agreement that accompanied the beta?

--Â
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, ilv-m asked:

| If this is the best that Microsoft can offer, we won't risk the
| liability of any Office 2007 upgrade recommendations to anyone. We
| will depend on customers to insist on taking the risk on a time &
| materials basis.
|
| Wiping all systems down and starting over from scratch with new OS
| installations and all application software is financially acceptable
| to very few.
|
| Why is Windows sooooo very poorly designed that software upgrades are
| not as clean as they once were before the abomination of the registry
| was introduced? Why does Microsoft still use hierarchical database
| technology that virtually everyone else threw out in the 1960's
| because it was known by then how completely out of control such
| databases can get.
|
| It's no wonder that Windows is a heaving, hulking, unreliable pile of
| garbage since it depends so desperately on an absolute disaster of a
| hierarchical database in the form of the registry hives.
|
| Would someone at Microsoft please justify why their product line is
| such a tangled mess that new system software images being built up
| from scratch with many applications may take DAYS to assemble--and
| after they are built are so unbelievably fragile? How can this be
| the best that the software world has to offer when we all should know
| very well how far short of best-practices the whole Microsoft
| approach has become?
|
| Microsoft in this area seems to have become far worse than IBM ever
| was at its most arrogant market-dominating point.
|
|
| "Bob Buckland ?:)" wrote:
|
|| There isn't a tool for uninstalling the Office 2007 betas as there
|| were a number of them going on (including the sister product, MS
|| Expression web) at the same time and there is a large number of
|| possible combinations that could be in play.
||
|| When the beta isn't removed through normal procedures, add-remove
|| programs, it's often because the installation was already broken. If
|| you review the Knowledge Base articles for steps to remove a broken
|| 'regular' Office installation manually they're not far different.
|| Broken installations come from adding other software or add-ins over
|| time or using utilities such as computer 'speedup' or 'registry
|| cleaner' ones that are 'helping'.
||
|| There is a risk to relying on time limited beta software, although
|| it is easy to get used to using it and forgetting it's 'test
|| software'.
||
|| For many people the basic steps in the MSKB article, removing all
|| prior betas and related add-ins, from Add/Remove Programs in the
|| Windows control panel, do work to have a clean environment to
|| install the release version of MS Office 2007. It is the quality of
|| operation that is one of the prime reasons for starting clean with
|| release software rather than focusing on 'upgrading' a beta/test
|| software.
||
|| =================
|| || Since this is the Office installation topic, would you kindly post
|| the answer
|| here? This is not a 'misc' type of issue, but a show-stopper for us
|| too.
|| We're glad to see that so many others want this Office 2007
|| installer defect
|| fixed so that hopefully Microsoft will either do that, or provide an
|| automated clean-up tool to deal with the problem.
||
|| The extremely time-consuming manual steps described in the KB's
|| about this
|| problem are ridiculous. The people with the info to write the steps
|| into a KB
|| should have incorporated the clean-up in the Office 2007 RTM
|| installer, or
|| provided an Office 2007 beta wipe-down tool to make sure that
|| Microsoft's
|| best and brightest customers are not angered by this kind of
|| sloppiness.
|| Business is being lost as we and our customers wait for a reasonable
|| solution. The competition for a botched Office 2007 release is to do
|| nothing
|| but stand on Office 2003.
||
|| If we were flying in Microsoft-designed aircraft, with such poor
|| quality control, we would probably all be dead. >> --
||
|| Bob Buckland ?:)
|| MS Office System Products MVP
||
|| *Courtesy is not expensive and can pay big dividends*
 
I

ilv-m

Just why the condescending arrogance? So often the only reason to bother with
these 'support' forums is to prove to customers just how awful the attitudes
are inside Microsoft and their close circle of sycophants.

How many times do we have to drive this point home---they are test machines
for both us and the customers. Yes they can be wiped down and/or rolled back
to get rid of every trace of Office 2007 beta, but that wastes a great deal
of time and money due to other software that we are also testing internally
and at customer sites on those systems. Roll-backs would be just as
destructive to testing under way as full system restores.

We really have to wonder if any of those representing the Microsoft line on
these forums has any commercial IT operations experience whatsoever!

Why is it so hard to understand that we expect the Microsoft installation
code to hold its own and not trip over tiny cracks in the pavement. Why
should we trust a product line when the installer component is such a piece
of junk?

I can state for the record that with the Exchange 2000 release and the way
that it could utterly destroy Windows domains due to numerous installer code
bugs, we finally gave up on that product line and migraded ourselves and all
further email systems installations over to standards-based IMAP-based
products. They are far more scalable and far more stable. Now we are thankful
in a way that Microsoft bombed that release so badly that we are running on
email server software that is so operationally superior.

If we had something to recommend besides Office 2007, we would be doing that
now as well. So since this kind of derrogatory dismissive 'support' from its
MVPs is all that Microsoft has to offer in public, rather than fix their
design mistake, it's just easier to reject the upgrade for now and keep
customers at Office 2003 plus more third-party software.



Milly Staples said:
First question for you is why you ignored all the warnings and ran beta software on a production machine in direct violation of the Licensing agreement that accompanied the beta?

--Â
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, ilv-m asked:

| If this is the best that Microsoft can offer, we won't risk the
| liability of any Office 2007 upgrade recommendations to anyone. We
| will depend on customers to insist on taking the risk on a time &
| materials basis.
|
| Wiping all systems down and starting over from scratch with new OS
| installations and all application software is financially acceptable
| to very few.
|
| Why is Windows sooooo very poorly designed that software upgrades are
| not as clean as they once were before the abomination of the registry
| was introduced? Why does Microsoft still use hierarchical database
| technology that virtually everyone else threw out in the 1960's
| because it was known by then how completely out of control such
| databases can get.
|
| It's no wonder that Windows is a heaving, hulking, unreliable pile of
| garbage since it depends so desperately on an absolute disaster of a
| hierarchical database in the form of the registry hives.
|
| Would someone at Microsoft please justify why their product line is
| such a tangled mess that new system software images being built up
| from scratch with many applications may take DAYS to assemble--and
| after they are built are so unbelievably fragile? How can this be
| the best that the software world has to offer when we all should know
| very well how far short of best-practices the whole Microsoft
| approach has become?
|
| Microsoft in this area seems to have become far worse than IBM ever
| was at its most arrogant market-dominating point.
|
|
| "Bob Buckland ?:)" wrote:
|
|| There isn't a tool for uninstalling the Office 2007 betas as there
|| were a number of them going on (including the sister product, MS
|| Expression web) at the same time and there is a large number of
|| possible combinations that could be in play.
||
|| When the beta isn't removed through normal procedures, add-remove
|| programs, it's often because the installation was already broken. If
|| you review the Knowledge Base articles for steps to remove a broken
|| 'regular' Office installation manually they're not far different.
|| Broken installations come from adding other software or add-ins over
|| time or using utilities such as computer 'speedup' or 'registry
|| cleaner' ones that are 'helping'.
||
|| There is a risk to relying on time limited beta software, although
|| it is easy to get used to using it and forgetting it's 'test
|| software'.
||
|| For many people the basic steps in the MSKB article, removing all
|| prior betas and related add-ins, from Add/Remove Programs in the
|| Windows control panel, do work to have a clean environment to
|| install the release version of MS Office 2007. It is the quality of
|| operation that is one of the prime reasons for starting clean with
|| release software rather than focusing on 'upgrading' a beta/test
|| software.
||
|| =================
|| || Since this is the Office installation topic, would you kindly post
|| the answer
|| here? This is not a 'misc' type of issue, but a show-stopper for us
|| too.
|| We're glad to see that so many others want this Office 2007
|| installer defect
|| fixed so that hopefully Microsoft will either do that, or provide an
|| automated clean-up tool to deal with the problem.
||
|| The extremely time-consuming manual steps described in the KB's
|| about this
|| problem are ridiculous. The people with the info to write the steps
|| into a KB
|| should have incorporated the clean-up in the Office 2007 RTM
|| installer, or
|| provided an Office 2007 beta wipe-down tool to make sure that
|| Microsoft's
|| best and brightest customers are not angered by this kind of
|| sloppiness.
|| Business is being lost as we and our customers wait for a reasonable
|| solution. The competition for a botched Office 2007 release is to do
|| nothing
|| but stand on Office 2003.
||
|| If we were flying in Microsoft-designed aircraft, with such poor
|| quality control, we would probably all be dead. >> --
||
|| Bob Buckland ?:)
|| MS Office System Products MVP
||
|| *Courtesy is not expensive and can pay big dividends*
 
I

ilv-m

All of the Office 2007 beta components and add-ins were removed in an orderly
manner using the normal uninstall removal steps. This is just a case where
the newer Office 2007 RTM installation code is simply too touchy, and should
have been written to TELL THE OPERATOR just what it thinks is wrong before
aborting. The fact that the installer complains and then just aborts without
providing any detail whatsoever is rediculous. Programmers of such junk would
never graduate from any of the CompSci programs what we are aware of. Most
corporations would fire IT staff that was as sloppy.
 
I

ilv-m

All of the Office 2007 beta components and add-ins were removed in an orderly
manner using the normal uninstall removal steps. This is just a case where
the newer Office 2007 RTM installation code is simply too touchy, and should
have been written to TELL THE OPERATOR just what it thinks is wrong before
aborting. The fact that the installer complains and then just aborts without
providing any detail whatsoever is rediculous. Programmers of such junk would
never graduate from any of the CompSci programs what we are aware of. Most
corporations would fire IT staff that was as sloppy.
 
P

Patrick Schmid [MVP]

Support? If you want support, call Microsoft and pay $250 an hour.
These here are peer-to-peer newsgroups where other users like you are
offering their free help. MVPs are not Microsoft employees.
We really have to wonder if any of those representing the Microsoft line on
these forums has any commercial IT operations experience whatsoever!
Yes, which is why I wouldn't be bitching about a beta product not being
removed cleanly from a test machine. In my commercial IT operations
experience, I had a set of images laying around with several different
configurations. A beta destroyed a machine? Oh well, 20 mins later I had
a clean set up on the machine again ready to go. I still have the same
kind of setup for my own virtual machines, so wiping on real test
machines is just a question of copying something over.
Why is it so hard to understand that we expect the Microsoft installation
code to hold its own and not trip over tiny cracks in the pavement. Why
should we trust a product line when the installer component is such a piece
of junk?
You tested a beta product with a beta setup program. Why should the
setup program be in any different shape than actual applications during
the beta?
If we had something to recommend besides Office 2007, we would be doing that
now as well. So since this kind of derrogatory dismissive 'support' from its
MVPs is all that Microsoft has to offer in public, rather than fix their
design mistake, it's just easier to reject the upgrade for now and keep
customers at Office 2003 plus more third-party software.
Design mistake? You clearly don't know what you are talking about.
Before you blast the Office setup program and how its RTM version should
clean up the beta, I suggest you read up on how Windows Installer works.
To answer your question about removing the beta, see
http://pschmid.net/blog/2006/11/13/80. It takes about 15 mins for
someone who knows what they are doing to remove the beta using the
manual steps from a computer. I'd say if you had just sat down and done
it instead of writing long posts here, you would be finished by now.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed
 
P

Patrick Schmid [MVP]

Support? If you want support, call Microsoft and pay $250 an hour.
These here are peer-to-peer newsgroups where other users like you are
offering their free help. MVPs are not Microsoft employees.
We really have to wonder if any of those representing the Microsoft line on
these forums has any commercial IT operations experience whatsoever!
Yes, which is why I wouldn't be bitching about a beta product not being
removed cleanly from a test machine. In my commercial IT operations
experience, I had a set of images laying around with several different
configurations. A beta destroyed a machine? Oh well, 20 mins later I had
a clean set up on the machine again ready to go. I still have the same
kind of setup for my own virtual machines, so wiping on real test
machines is just a question of copying something over.
Why is it so hard to understand that we expect the Microsoft installation
code to hold its own and not trip over tiny cracks in the pavement. Why
should we trust a product line when the installer component is such a piece
of junk?
You tested a beta product with a beta setup program. Why should the
setup program be in any different shape than actual applications during
the beta?
If we had something to recommend besides Office 2007, we would be doing that
now as well. So since this kind of derrogatory dismissive 'support' from its
MVPs is all that Microsoft has to offer in public, rather than fix their
design mistake, it's just easier to reject the upgrade for now and keep
customers at Office 2003 plus more third-party software.
Design mistake? You clearly don't know what you are talking about.
Before you blast the Office setup program and how its RTM version should
clean up the beta, I suggest you read up on how Windows Installer works.
To answer your question about removing the beta, see
http://pschmid.net/blog/2006/11/13/80. It takes about 15 mins for
someone who knows what they are doing to remove the beta using the
manual steps from a computer. I'd say if you had just sat down and done
it instead of writing long posts here, you would be finished by now.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed
 
P

Patrick Schmid [MVP]

P

Patrick Schmid [MVP]

I

ilv-m

And we applaud Microsoft for being so generous to so many people groups
around the world---but could they just get their installer to work right?

As another has stated, this is 'peer' support as we know very well, and that
MVPs are not technically Microsoft employees. However, there is a reason that
MVPs make the effort because they are compensated by Microsoft at least
through intangible benefits.

We do normally pay Microsoft to provide solutions to their mistakes, but
since Microsoft also encourages their business partners to participate in
these online communities, I thought it would be interesting to see what kind
of quality we would find, and how the MVPs would respond to criticisms of
Microsoft. For example, would they attack those posting the complaint, or
would they actually try to help with new and meaningful information.

As we expected, there are very few helpful and constructive answers being
provided in this setting. Most of the information it completely useless.
Microsoft customers are regularly insulted rather than being helped.

So the bottom line is that next time we have a face-to-face with our
Microsoft counterparts, we have all the evidence we need to tell them how
wrong it is to tell their customers and partners to waste their time trying
to get help from 'peers' when Microsoft should have been providing all of
that support in the first place.

Maybe some of you like to defend support practices of companies with profits
in the billions and incomes larger than most other corporations, but we have
a strong disregard for a customer support approach that is built on pure
greed.

That almost killed IBM. What a waste if the same mistakes damage Microsoft
the same way.

Patrick Schmid said:
Most corporations don't write software that has to work for 400+ million
people in 80 different languages.

Patrick Schmid [OneNote MVP]
--------------
http://pschmid.net
***
Office 2007 RTM Issues: http://pschmid.net/blog/2006/11/13/80
***
Customize Office 2007: http://pschmid.net/office2007/customize
RibbonCustomizer Add-In: http://pschmid.net/office2007/ribboncustomizer
OneNote 2007: http://pschmid.net/office2007/onenote
***
Subscribe to my Office 2007 blog: http://pschmid.net/blog/feed

All of the Office 2007 beta components and add-ins were removed in an orderly
manner using the normal uninstall removal steps. This is just a case where
the newer Office 2007 RTM installation code is simply too touchy, and should
have been written to TELL THE OPERATOR just what it thinks is wrong before
aborting. The fact that the installer complains and then just aborts without
providing any detail whatsoever is rediculous. Programmers of such junk would
never graduate from any of the CompSci programs what we are aware of. Most
corporations would fire IT staff that was as sloppy.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top