firstdivision
MIS
Hello all,
I've been trying to deploy Office 2000 Premium across my Windows 2000 network using Group Policy. Everything worked fine until I tried to open Outlook on the client machine (which is XP).
I've been following Mark Minasi's steps in "Mastering Windows 2000 Server SE". Here's what I've done:
- I performed an administrative installation of Office2k and saved it to a folder on the domain controller (c:\packages\Office2KPro). I shared the packages folder.
- I created a new Group Policy Object called Office2k within the organizational unit that I want to recieve Office.
- I added the package to the GPO using the network path "\\servername\packages\Office2KPro\data1.msi", I added the package to the "user configuration\software settings\software installation" directory of the GPO.
- I chose for the package to be assigned.
- I rebooted the XP client and was notified that new software was being installed. This was expected...Yay!
- I clicked on Word in the start menu. After a brief install period it opened up. I created a new letter template to test it and my username showed up in the template. Yay!
--- up until this point, everything looked good ---
- I clicked on Outlook and recieved an error. Something to the effect of "Portions of this installation require administrative privilages. Please contact your Administrator or log on as an Administrator to complete the installation of Outlook". Doh!
The problem is that the domain user does not have administrative privilages over the computer (I guess), the software is assigned to the user, so none of the Office apps show up in the start menu if I am logged on as either a local or domain admin.
So...how do I get this installation to work? Ideally I want the user to be able to open up Outlook just like he/she can open up Word and Excel...no admin needed. Is there some special change I need to make to allow this? There is no mention of this little quirk in the book.
Thanks and Cheers,
Andrew
I've been trying to deploy Office 2000 Premium across my Windows 2000 network using Group Policy. Everything worked fine until I tried to open Outlook on the client machine (which is XP).
I've been following Mark Minasi's steps in "Mastering Windows 2000 Server SE". Here's what I've done:
- I performed an administrative installation of Office2k and saved it to a folder on the domain controller (c:\packages\Office2KPro). I shared the packages folder.
- I created a new Group Policy Object called Office2k within the organizational unit that I want to recieve Office.
- I added the package to the GPO using the network path "\\servername\packages\Office2KPro\data1.msi", I added the package to the "user configuration\software settings\software installation" directory of the GPO.
- I chose for the package to be assigned.
- I rebooted the XP client and was notified that new software was being installed. This was expected...Yay!
- I clicked on Word in the start menu. After a brief install period it opened up. I created a new letter template to test it and my username showed up in the template. Yay!
--- up until this point, everything looked good ---
- I clicked on Outlook and recieved an error. Something to the effect of "Portions of this installation require administrative privilages. Please contact your Administrator or log on as an Administrator to complete the installation of Outlook". Doh!
The problem is that the domain user does not have administrative privilages over the computer (I guess), the software is assigned to the user, so none of the Office apps show up in the start menu if I am logged on as either a local or domain admin.
So...how do I get this installation to work? Ideally I want the user to be able to open up Outlook just like he/she can open up Word and Excel...no admin needed. Is there some special change I need to make to allow this? There is no mention of this little quirk in the book.
Thanks and Cheers,
Andrew