| Author |
Software deployment via GPO
|
|
| CyberDude 2002-05-22, 9:01 am |
| Ok, what exactly is the difference between a network share and a normal share?
I have followed my New Riders book to the letter to deploy a software package. I have created a hidden share to hold the packages.
I have use the Veritas program to create a msi file for my program and it has stored all relevant data to this share. When it came to the part of specify a path, I choose the hidden share (which gave me a message saying that it was not a network share, and if I wanted to proceed or not). I said yes.
I have created a GPO for this package and have set it to publish, and it is configured for only one user.
I logon as this user, but there is no program in the add/remove program utility. I have not checked the box for don't display this program in add/remove programs, which to me means that it should be there.
Any insight?  | |
|
|
| CyberDude 2002-05-22, 2:35 pm |
| Cheers for the help mate, but I have setup and configured RIS already (just waiting until I have emptied out a partition to test it). This is to do with software deployment using zap or msi files. | |
|
|
| CyberDude 2002-05-23, 2:46 am |
| Thanks again for the link. New Riders say to make the share hidden due to the fact that anyone can intiate an msi file. MS doe not mention this.
Is there a main site where I can find all the how to's on one page, or are they scattered around all the various subsections of the OSes?
| |
| Sexy Lexy 2002-05-23, 12:05 pm |
| Tried this myself over the last few days and hidden shares have caused me a problem.
The Microsoft (c) (r) solution is to give authenticated uses read only access and admins full access to the share. If you have published the package, ensure that you haven't selected the check box that stops the package appearing in the add remove programs section.
My question, no to steal your thunder is how do you set up a MSP (Patch file) as a published application as the software install only caters fro MSI and MST extensions?
 | |
| CyberDude 2002-05-23, 3:04 pm |
| The GPO works but for some reason it does not show in add/remove programs, and no I have not checked that box. I say it works because when I look in event viewer there is a record stating that windows installer was correctly applied to that user.
I believe that msp, mst are implemented the same way. You initialy create your msi file and deploy it. When you have created an update or new config you create an mst file and attach it to the original msi file on the network share. This process is the same for msp files. Once the mst/msp file is attached to the network share msi file, you simply redeploy the msi. | |
| Zaraspook 2002-05-23, 8:23 pm |
| Sounds to me like there's a problem with the package you created! If nothing is appearing in ADD/Remove Programs, then something is difinetly wrong with either your GPO or your package. Re-check your GPO settings one more time, making sure you don't have any conflicts. If your settings check out, then it's got to be a problem with the package.
One thing you might try is publishing a MSI from one of the Office 2000 suite or other that comes with MSIs as part of the installation package. If it shows up in ADD/Remove Programs, then it will confirm a problem with the package. Good luck!  | |
| KScheler 2002-05-23, 10:30 pm |
| CyberDude:
Seems like MS has lots of things scattered. Sometimes I go to Technet and do a search for "how to" or "step by step". It's amazing what they do have out there. Sometimes it just takes some digging. | |
| CyberDude 2002-05-27, 5:16 am |
| Zaraspook was right. I published the support tools in the same GPO with the same settings as the package, and it showed up in add/remove programs. This means that the package is at fault, which is rather unfortunate considering I do not have a clean system anymore with which to create a new one. At least I know that the process was correct. Is there another way where I can fix the package, without needing a clean install system? Thanks guys. | |
|
|
| CyberDude 2002-05-28, 2:05 am |
| Cheers Zaraspook, I will try it now. | |
| CyberDude 2002-05-28, 2:29 am |
| And the jury says, uhah!! Sorry mate, but it still does not appear in add/remove programs. What I think I will do is delete the package from the share, and recreate it via the Veritas program again. I know that I do not have a clean machine this time, but as the machine will be the one that will have installed on anyway, hopefully it won't matter. The settings work, as the support tools showed up, which must only mean that the Veritas program failed somewhere. Will post back. | |
| CyberDude 2002-05-28, 3:59 am |
| That did not work either. Could this be that as it is a legacy program (requiring admin privs to install), that it will still fail to install by a normal user, or is this why msi files are good because the DO allow legacy programs to be installed by normal user? I have tried to install the msi direct from its share, but fails to complete due to the user not having admin privs.
I have repackaged it and it still does not appear in add/remove programs (if you install it direct from cd it is not shown in add/remove programs either).
Any ideas? I know that the process works so this part of my studies are over. I would have liked this program to have worked as well, as I don't want to have to keep starting the program via the admin password before my boys can play it, and I do not wish them to become power users either. |
|
|
|