Office 2003 Basic won't publish via group policy

[MCSE]

I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com

 

[Bob Buckland ?:-\)]

MS Office 2003 Basic edition is an OEM only (to be
preinstalled with new PCs) edition and usually
doesn't work from an Office Admin Point that would
have an Enterprise/Volume license key installation.
http://office.microsoft.com/en-us/assistance/HA011402011033.aspx

You may want to check with the OEM system builder folks who
have separate tools than those used for a corporate deployment
of Office
http://microsoft.com/oem

You may also want to check with the folks in the Desktop Deployment
newsgroup (link below).

========
I am trying to publishing Office 2003 Basic with a Windows 2000 Server Group
Policy object but it is not working. I assigned the object to the domain,
verified that the UNC to the MSI file is correct (it runs when you type it
into start-run), and also made sure that no override was set and that it was
not disabled. I also tried placing the computers in a separate OU in the
same manner with a link to the same GPO. The XP Pro clients show no
indication of Office 2003 Basic in All Programs nor on the desktop nor in
Add/Remove Programs. I refreshed group policy, waited 15 minutes, cut and
pasted the working UNC directly from the Start-Run box into the group policy
path, all to no avail. Is this supported and/or what could I be doing wrong?
Thank you!>>
--
LLet us know if this has helped you,

Bob Buckland ?
MS Office System Products MVP
*courtesy is not expensive and can pay big dividends8

A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.deployment.desktop
or via browser:
http://microsoft.com/communities/newsgroups/en-us/?dg=microsoft.public.deployment.desktop

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/community/en-us/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com