How do you do....it? Thread, Deploy AdminPak.MSI in Technical; I would like to deploy AdminPak.MSI to our workstations so that our Staff can manage Student passwords. I have experimented ...
5th October 2009, 12:56 PM #1
I would like to deploy AdminPak.MSI to our workstations so that our Staff can manage Student passwords. I have experimented with:
msiexec /i \\ServerName.ChildDomainName.ParentDomainName.Loca l\NetLogon\adminpak.msi ADDLOCAL=FeADTools /qb
at a station locally and this works perfectly. I would now like to incorporate this into a script so that it will work without me having to go to each station in turn.
I have added the command above [including the switches] into Group Policy for Staff but it does not deploy properly. I would like to be able to add the suggested script into Computer Configuration in AD.
Does anyone have such a script?
IDG Tech News
5th October 2009, 01:23 PM #2
Why can't you just add it as a piece of managed software in a GPO? This is what I do - remember to assign it as a computer configuration though!
5th October 2009, 01:24 PM #3
Why don't you just deploy it using the software policy of AD.
5th October 2009, 01:31 PM #4
Hi guys. Thanks for the replies.
I tried deploying it through GP and that did not work either.
5th October 2009, 01:49 PM #5
You need to make sure 'domain computers' have permission to run the GPO and also to the share where it is located...
5th October 2009, 01:50 PM #6
Well thats strange because I have deployed this in about 10 seperate organisations without a problem.
5th October 2009, 02:31 PM #7
You can use the Group Policy Management Console to troubleshoot the deployment. The relevent event logs are pulled and ofter the error descriptions are quite good and actually tell you how to fix the problem!
Originally Posted by DaveP
5th October 2009, 02:36 PM #8
Have you checked the requirements for the software on the client PCs?
5th October 2009, 06:33 PM #9
You haven't said where you're trying to deploy this. If it's as a script, it needs to be as a computer startup script (not user logon; they won't have rights to run it). If it's a GPO to do software deployment then again, it needs to be at machine level.
5th October 2009, 08:08 PM #10
Thanks. That looks like it has cracked it!
Originally Posted by Domino
Why did I not spot it before? Because I have an MSI deployed through AD in exactly the same way which does not appear to require the same settings [checking tomorrow]
Now I have an idea of how this is supposed to work I would like to slim down my Ghost images and deploy whatever software I can this way. So I will need to find out:
- Where to download MSTs to customise installs using MSIs
- What are the rules about which order software is installed [Word before SharePoint or Microsoft before Adobe etc]
- AD customisations which might be required by this type of install to make the software work
- Other stuff I haven't thought of yet
What do others do with regard to this?
Last edited by DaveP; 5th October 2009 at 08:12 PM.
Reason: Modify post: Add to listed items.
6th October 2009, 12:56 AM #11
6th October 2009, 08:30 AM #12
You can use Orca, WininstallLE, MAKEMSI and quite a few other free utils to modify msi files and generate mst file.
1. Where to download MSTs to customise installs using MSIs
2. What are the rules about which order software is installed [Word before SharePoint or Microsoft before Adobe etc]
They are deployed in the order they are added to the GPO, NOT the order they appear in the list which is alphabetical.
Take a look at this link.
Last edited by cookie_monster; 6th October 2009 at 08:35 AM.
6th October 2009, 08:33 PM #13
i thought they were added in guid order?
Originally Posted by cookie_monster
orca is ok for quick and simple stuff but thats it imo
6th October 2009, 10:26 PM #14
I thought that in the past but I've read a few times and been told that it reads the timestamp which is why manually altering the GPO can cause software to reinstall. It does seem that way when I've tested it as well.
i thought they were added in guid order?
Note, though, that even the tiniest modification to a package will cause its timestamp to be adjusted to the current date and time, pushing it to the end of the installation sequence.
Last edited by cookie_monster; 6th October 2009 at 10:29 PM.
7th October 2009, 08:50 AM #15
And also not every msi requires an MST. To my experience 90% don't need one. Normally well written software and up to date comes with a ready to use MSI. Shame MS did not do this with Office 2007 as it's sort of their technology.
By Little-Miss in forum Learning Network Manager
Last Post: 15th October 2009, 12:45 PM
By LOUD in forum Windows Server 2000/2003
Last Post: 13th August 2009, 03:56 PM
By sidewinder in forum Windows
Last Post: 5th June 2008, 12:04 PM
By tobyhughes in forum How do you do....it?
Last Post: 18th June 2006, 07:53 PM
By Norphy in forum Windows
Last Post: 30th January 2006, 04:12 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)