| Author |
Software Deployment.
|
|
| Fugaz13 2003-08-25, 7:20 pm |
| Any help would be appreciated.
Here is the issue.
I have a test-us.com domain. I've created a OU named Software. I created a network share named Software, with subdir named Admin Tools and Office 2000, and copied the necessary files to each folder for software deployment.
On Software OU I created a GPO named Software Deployment and then edited the settings. First was computer config/software settings/ created a software package Assigned.(office 2000) Also, under user config/software settings/ created a software packaged published. (adminpack.msi)
I also created a new user and added it to this OU, and moved an existing win2k Pro machine to this OU.
After reboot it does through the motions of applying policies etc. Then it brings up Installing Microsoft Office 2000 SR-1...
After logging in I checked the start/programs/ but no office.
In add/remove programs I see the adminpack listed there.
It seems that the published item is showing up but not the assigned.
Any ideas on what I've missed.??
tHanks | |
| Fugaz13 2003-08-25, 7:31 pm |
| Ok.. if you have suggestions feel free.
dummy me didn't check event viewer and guess what errors all over.. I'm checking them out now.. I'll post what I find. | |
| jeff_j_black 2003-08-25, 8:26 pm |
| Sounds like you'll get it worked out. Please post what you find or if you need more help.
Always good to go to the Event Viewer first sign of trouble. Also make sure that all your share and NTFS permissions are in order on your software share. Often times the most bewildering issues arise from permissions configurations. | |
| Fugaz13 2003-08-26, 5:37 pm |
| Well I finally was able to get it to work. WOOT!! Not sure the fix was easy way out or only way out.
Here is a few of the errors in event viewer.
Event ID 102, 1000, 103(?) checked them at eventid.net
There were so many that I forget..
Anyways after researching the various application errors in the event viewer on the client machine it seemed that it was permissions, missing file in the \\(software share), bad system file.
Well I checked and double checked everything and nothing worked. So I reinstalled client OS (win2k). Booted up and logged in as a user in the Software OU, nothing didn't work. Next in AD user/computers I added the computer itself to the OU, rebooted and BLAM!!! there are the office products listed under programs.
Thing is I'm curious is how come when logging in as the user first it didn't work?? Is that because I Assigned the package under computer config\software settings and not Assign it under User config\software settings??
I think this fix, of reinstalling OS, was actually the best because it would been less time involved from the get go. Only thing I'm concerned about is if there was something I missed. I really would like to know, because I don't ghosting/reinstall to be a cruch..
also anyone have info on how to get ProductKeys/Key codes into the software installation?? So no user prompts??? | |
| Fugaz13 2003-08-27, 9:32 am |
| Ran a network install to the network share point. setup.exe /a
That and then used the CIW to create a .mst file for adjust any customer options.
Worked like a champ on client machine.
Installed and no user input required.. | |
| jeff_j_black 2003-08-27, 9:52 am |
| Great job! Always good to get the sense of accomplishment. |
|
|
|