I have been searching the web and InstallShield help to find a resource that explains the MSI design requirements to be able to deply an MSI in the various Active Directory(AD)/Group Policy (GPO) deplyment methods, but have come up empty so far. Does anyone know of any such thing?
For example, one of our MSI installations does not work when it is Published to a user with Active Directory. Is there any documentation that explains the MSI elements that must be present in order for this scenario to work?
Any help is appreciated!
Thanks,
Shane
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
MSI Requirementes for Active Directory Deployment
Started by
sjimmerson
, Aug 18 2005 23:27
1 reply to this topic
Zweitze
-
- Full Members
- 522 posts
Posted 19 August 2005 - 22:53
Ensure that the following works:
1) Per-user installation. Your setup must respect the [ALLUSERS] property, and it should never modify its value. You can set a default in the property table, but that's all.
2) (Assinging only) Advertizing. To emulate the most important part, try running setup with the following command:
Msiexec /ju Yourapp.msi
Note this does not apply to publishing.
You do realize, that with publishing, the app gets listed in Add/Remove programs? You will should the app in "Programs on the network" (or something like that), and install it. If it's not there, your network is probably not configured OK, usually DNS-related. Check the EventLog of the client system.
1) Per-user installation. Your setup must respect the [ALLUSERS] property, and it should never modify its value. You can set a default in the property table, but that's all.
2) (Assinging only) Advertizing. To emulate the most important part, try running setup with the following command:
Msiexec /ju Yourapp.msi
Note this does not apply to publishing.
You do realize, that with publishing, the app gets listed in Add/Remove programs? You will should the app in "Programs on the network" (or something like that), and install it. If it's not there, your network is probably not configured OK, usually DNS-related. Check the EventLog of the client system.