Admin Installs - Office 2003 Pro - Microsoft Update

[Gerry Hickman]

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]

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]

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]

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.

 

[Sandy Wood]

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]

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]

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]

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]

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]

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]

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]

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]

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.

 

[Gerry Hickman]

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]

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]

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]

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]

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]

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]

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).