Push Outlook 2003 via Active Directory to Multiple Versions of Office - HELP!!!

  • Thread starter Thread starter Brian
  • Start date Start date
B

Brian

The company I work for has multiple versions of Office (2000, XP, 2003). We
would like to push Outlook 2003 out to all workstations via a Group Policy
and Active Directory. I have a test machine set up, and everything works
great - if there isn't a version of Office on the machine. If Office
resides on the machine, I am getting an error in the Event Viewer (Event ID
102):

"The installation source for this product is not available. Verify that the
source exists and that you can access it. "

I can't seem to figure out why this is happening. Do I have to uninstall
the previous version of Outlook before I install the new one?? The versions
of Office that are on the machines were not installed via Group Policy.
They were Ghosted or installed manually.
 
I'm about to do the same - I've created my MST file, but need to figur
out how to gracefully push it to selected PC's on the network runnin
Outlook 2k or XP. Any info/instructions would be greatly appreciate
(I'm running Enterprise Server 2003/Exchange 2003 and all my PCs are X
(some with SP2)). Gracias.
*The company I work for has multiple versions of Office (2000, XP
2003). We
would like to push Outlook 2003 out to all workstations via a Grou
Policy
and Active Directory. I have a test machine set up, and everythin
works
great - if there isn't a version of Office on the machine. I
Office
resides on the machine, I am getting an error in the Event Viewer
(Event ID
102):

"The installation source for this product is not available. Verif
that the
source exists and that you can access it. "

I can't seem to figure out why this is happening. Do I have t
uninstall
the previous version of Outlook before I install the new one?? Th
versions
of Office that are on the machines were not installed via Grou
Policy.
They were Ghosted or installed manually.


-
shel
 
I'm currently working on a similar project where I'm pushing out remotly
installed applications. I would try creating an MSI fine from a clean
install, then pushing that msi file out using Runas, and the msiexec commands
in 2 seperate batch files.

Rob. R.
 
Back
Top