Admin Installs - Office 2003 Pro - Microsoft Update

[Sandy Wood]

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?

 

[Gerry Hickman]

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]

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]

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]

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]

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]

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]

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]

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]

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.

 

[Sandy Wood]

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]

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]

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]

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]

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]

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]

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]

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]

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

 

[Peter Foldes]

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