Admin Installs - Office 2003 Pro - Microsoft Update

We're in the process of upgrading our users to Office 2003 Pro from
administrative installs of Office 2003 Pro SP1. I've noticed lately that a
few machines that have been upgraded, have been able to get Office updates at
the new Microsoft Update site. We're used to seeing a note that because we've
got an administrative install of Office, we would need to update our clients
that way. Have the rules changed with Microsoft Update now?
--
Sandy Wood
Orange County District Attorney

Hi Sandy,

We're in the process of upgrading our users to Office 2003 Pro from
administrative installs of Office 2003 Pro SP1. I've noticed lately that a
few machines that have been upgraded, have been able to get Office updates at
the new Microsoft Update site. We're used to seeing a note that because we've
got an administrative install of Office, we would need to update our clients
that way. Have the rules changed with Microsoft Update now?

I've always run it the same since Office 2000.

1. Create fully packed and patched AIP
2. Deploy to clients
3. Disable Office update on all clients

If a patch is released, MSP the AIP, then do recache and reinstall of
FEATURELIST.

There's a new barmy idea in Office 2003 called "Local Installation
Source", but I'm not sure who is falling for it. The deployment guide
seems somewhat confused in this area.

--
Gerry Hickman (London UK)

I've been doing the same since Office XP and all along if a user went to
OfficeUpdate they'd get a notice that they could not update their
installation. Now it's all open it seems.........
--
Sandy Wood
Orange County District Attorney


"Gerry Hickman" wrote:

Hi Sandy,

We're in the process of upgrading our users to Office 2003 Pro from
administrative installs of Office 2003 Pro SP1. I've noticed lately that a
few machines that have been upgraded, have been able to get Office updates at
the new Microsoft Update site. We're used to seeing a note that because we've
got an administrative install of Office, we would need to update our clients
that way. Have the rules changed with Microsoft Update now?

I've always run it the same since Office 2000.

1. Create fully packed and patched AIP
2. Deploy to clients
3. Disable Office update on all clients

If a patch is released, MSP the AIP, then do recache and reinstall of
FEATURELIST.

There's a new barmy idea in Office 2003 called "Local Installation
Source", but I'm not sure who is falling for it. The deployment guide
seems somewhat confused in this area.

--
Gerry Hickman (London UK)

NON Administrative installs normally can access the download\update =
sites.

--=20
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Sandy Wood" wrote in message =
...
I've been doing the same since Office XP and all along if a user went =
to=20
OfficeUpdate they'd get a notice that they could not update their=20
installation. Now it's all open it seems.........
--=20
Sandy Wood
Orange County District Attorney
=20
=20
"Gerry Hickman" wrote:
=20
Hi Sandy,
=20
We're in the process of upgrading our users to Office 2003 Pro from =

administrative installs of Office 2003 Pro SP1. I've noticed lately =
that a=20
few machines that have been upgraded, have been able to get Office =
updates at=20
the new Microsoft Update site. We're used to seeing a note that =
because we've=20
got an administrative install of Office, we would need to update =
our clients=20
that way. Have the rules changed with Microsoft Update now?
=20
I've always run it the same since Office 2000.
=20
1. Create fully packed and patched AIP
2. Deploy to clients
3. Disable Office update on all clients
=20
If a patch is released, MSP the AIP, then do recache and reinstall of =

FEATURELIST.
=20
There's a new barmy idea in Office 2003 called "Local Installation=20
Source", but I'm not sure who is falling for it. The deployment guide =

seems somewhat confused in this area.
=20
--=20
Gerry Hickman (London UK)

But what about Administrative Installs and Microsoft Update? Has something
changed here? Perhaps in Windows Installer 3.1?
--
Sandy Wood
Orange County District Attorney


"Peter Foldes" wrote:

NON Administrative installs normally can access the download\update sites.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Sandy Wood" wrote in message ...
I've been doing the same since Office XP and all along if a user went to
OfficeUpdate they'd get a notice that they could not update their
installation. Now it's all open it seems.........
--
Sandy Wood
Orange County District Attorney


"Gerry Hickman" wrote:

Hi Sandy,

We're in the process of upgrading our users to Office 2003 Pro from
administrative installs of Office 2003 Pro SP1. I've noticed lately that a
few machines that have been upgraded, have been able to get Office updates at
the new Microsoft Update site. We're used to seeing a note that because we've
got an administrative install of Office, we would need to update our clients
that way. Have the rules changed with Microsoft Update now?

I've always run it the same since Office 2000.

1. Create fully packed and patched AIP
2. Deploy to clients
3. Disable Office update on all clients

If a patch is released, MSP the AIP, then do recache and reinstall of
FEATURELIST.

There's a new barmy idea in Office 2003 called "Local Installation
Source", but I'm not sure who is falling for it. The deployment guide
seems somewhat confused in this area.

--
Gerry Hickman (London UK)

Sandy

Where are you trying to Update from. WU (Windows Update) MU (Microsoft =
Updates) Office Update Site,SUS,WSUS? What happens when you scan for =
Updates at Office Updates.
--=20
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Sandy Wood" wrote in message =
...
But what about Administrative Installs and Microsoft Update? Has =
something=20
changed here? Perhaps in Windows Installer 3.1?
--=20
Sandy Wood
Orange County District Attorney
=20
=20
"Peter Foldes" wrote:
=20
NON Administrative installs normally can access the download\update =
sites.
=20
--=20
Peter
=20
Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be =
acknowledged.
=20
"Sandy Wood" wrote in message =
...
I've been doing the same since Office XP and all along if a user =
went to=20
OfficeUpdate they'd get a notice that they could not update their=20
installation. Now it's all open it seems.........
--=20
Sandy Wood
Orange County District Attorney
=20
=20
"Gerry Hickman" wrote:
=20
Hi Sandy,
=20
We're in the process of upgrading our users to Office 2003 Pro =
from=20
administrative installs of Office 2003 Pro SP1. I've noticed =
lately that a=20
few machines that have been upgraded, have been able to get =
Office updates at=20
the new Microsoft Update site. We're used to seeing a note that =
because we've=20
got an administrative install of Office, we would need to update =
our clients=20
that way. Have the rules changed with Microsoft Update now?
=20
I've always run it the same since Office 2000.
=20
1. Create fully packed and patched AIP
2. Deploy to clients
3. Disable Office update on all clients
=20
If a patch is released, MSP the AIP, then do recache and reinstall =
of=20
FEATURELIST.
=20
There's a new barmy idea in Office 2003 called "Local Installation =

Source", but I'm not sure who is falling for it. The deployment =
guide=20
seems somewhat confused in this area.
=20
--=20
Gerry Hickman (London UK)

I've found this behavior updating from Microsoft Updates. In the past, Office
Updates did not act this way. Now, if I point a computer at Microsoft
Updates, it finds any Windows and / or Office updates. It will allow me to
install them, whereas in the past it gave a warning that I was trying to
update an admin install.

We're getting ready to update our SMS 2003 Scan Tools to the latest
Microsoft Updates Feature set. This appears to behave the same way as a visit
to the Microsoft Updates site. I would love to see this behavior as I could
allow my SMS infrastructure to push down the binaries instead of an admin
install refresh.
--
Sandy Wood
Orange County District Attorney


"Peter Foldes" wrote:

Sandy

Where are you trying to Update from. WU (Windows Update) MU (Microsoft Updates) Office Update Site,SUS,WSUS? What happens when you scan for Updates at Office Updates.
--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Sandy Wood" wrote in message ...
But what about Administrative Installs and Microsoft Update? Has something
changed here? Perhaps in Windows Installer 3.1?
--
Sandy Wood
Orange County District Attorney


"Peter Foldes" wrote:

NON Administrative installs normally can access the download\update sites.

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"Sandy Wood" wrote in message ...
I've been doing the same since Office XP and all along if a user went to
OfficeUpdate they'd get a notice that they could not update their
installation. Now it's all open it seems.........
--
Sandy Wood
Orange County District Attorney


"Gerry Hickman" wrote:

Hi Sandy,

We're in the process of upgrading our users to Office 2003 Pro from
administrative installs of Office 2003 Pro SP1. I've noticed lately that a
few machines that have been upgraded, have been able to get Office updates at
the new Microsoft Update site. We're used to seeing a note that because we've
got an administrative install of Office, we would need to update our clients
that way. Have the rules changed with Microsoft Update now?

I've always run it the same since Office 2000.

1. Create fully packed and patched AIP
2. Deploy to clients
3. Disable Office update on all clients

If a patch is released, MSP the AIP, then do recache and reinstall of
FEATURELIST.

There's a new barmy idea in Office 2003 called "Local Installation
Source", but I'm not sure who is falling for it. The deployment guide
seems somewhat confused in this area.

--
Gerry Hickman (London UK)

Hi Sandy,

I've found this behavior updating from Microsoft Updates. In the past, Office
Updates did not act this way. Now, if I point a computer at Microsoft
Updates, it finds any Windows and / or Office updates. It will allow me to
install them, whereas in the past it gave a warning that I was trying to
update an admin install.

OK, I understnad the problem now. I think something did change with
2003, probably with the concept of LIS coming into view, but I have it
locked with group policy anyway.

We're getting ready to update our SMS 2003 Scan Tools to the latest
Microsoft Updates Feature set. This appears to behave the same way as a visit
to the Microsoft Updates site. I would love to see this behavior as I could
allow my SMS infrastructure to push down the binaries instead of an admin
install refresh.

And then your AIP is out of date. If you don't like AIP, you can use
LIS, but personally I would not do it this way.

--
Gerry Hickman (London UK)

I'm going to keep 'updating' my AIP as I would think there would be problems
with any user's Detect and Repair to an AIP that was not as current as the
client. However I did read somewhere that you could install clients from an
AIP and then as long as you did not 'update' the AIP, you could apply binary
upates to the clients. I've updated my AIP to SP1 so this may not work.

Then again, Office 2003 is supposed to support Full-File client updates,
without having the install source files available so I'm more confused now.
I'll keep on updating my AIP until I can get a better feel for what's really
the deal.
--
Sandy Wood
Orange County District Attorney


"Gerry Hickman" wrote:

Hi Sandy,

I've found this behavior updating from Microsoft Updates. In the past, Office
Updates did not act this way. Now, if I point a computer at Microsoft
Updates, it finds any Windows and / or Office updates. It will allow me to
install them, whereas in the past it gave a warning that I was trying to
update an admin install.

OK, I understnad the problem now. I think something did change with
2003, probably with the concept of LIS coming into view, but I have it
locked with group policy anyway.

We're getting ready to update our SMS 2003 Scan Tools to the latest
Microsoft Updates Feature set. This appears to behave the same way as a visit
to the Microsoft Updates site. I would love to see this behavior as I could
allow my SMS infrastructure to push down the binaries instead of an admin
install refresh.

And then your AIP is out of date. If you don't like AIP, you can use
LIS, but personally I would not do it this way.

--
Gerry Hickman (London UK)

Hi Sandy,

Then again, Office 2003 is supposed to support Full-File client updates,
without having the install source files available so I'm more confused now.
I'll keep on updating my AIP until I can get a better feel for what's really
the deal.

I read all the docs in some detail, and the stuff in the deployment
guide about LIS comes across as propaganda to me. As I see it, the AIP
is the professional route, and recache and reinstall is very quick and
easy - I have no interest in having hundreds of unpatched LIS files and
applying full file client updates - life if too short!

The whole Windows Update, Microsoft Update, WU, WGA, AU, WSUS, SUS, MBSA
1.1, MBSA 2.0, SMS, Enterprise Scanning Tool, saga is a complete mess
anyway, and what happened to the trumpet blowing rhetoric about
"unification", LOL).

--
Gerry Hickman (London UK)