Jump to content

Recommended Posts

Posted

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.Local\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?

 

T.I.A.

Posted
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!
Posted
I tried deploying it through GP and that did not work either. :(

 

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!

Posted
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.
Posted (edited)
You need to make sure 'domain computers' have permission to run the GPO and also to the share where it is located...

 

Thanks. That looks like it has cracked it!

 

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:

 

  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]
  3. AD customisations which might be required by this type of install to make the software work
  4. Other stuff I haven't thought of yet

 

What do others do with regard to this?

Edited by 6Foot2
Modify post: Add to listed items.
Posted
Thanks. That looks like it has cracked it!

 

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:

 

  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]
  3. AD customisations which might be required by this type of install to make the software work
  4. Other stuff I haven't thought of yet

 

What do others do with regard to this?

AppDeploy.com - The Application Deployment Information Center might have what your looking for

Posted (edited)
1. Where to download MSTs to customise installs using MSIs

 

You can use Orca, WininstallLE, MAKEMSI and quite a few other free utils to modify msi files and generate mst file.

 

 

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.

 

http://www.windowsnetworking.com/articles_tutorials/Group-Policy-Deploy-Applications.html

Edited by cookie_monster
Posted

They are deployed in the order they are added to the GPO, NOT the order they appear in the list which is alphabetical.

 

i thought they were added in guid order?

 

orca is ok for quick and simple stuff but thats it imo

Posted (edited)
i thought they were added in guid order?

 

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.

 

 

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.

 

http://diaryproducts.net/about/operating_systems/windows/move_software_package_to_another_gpo

Edited by cookie_monster
Posted
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.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...