In trying to stop a MSI created by IA being installed on the Win2003 server (http://forums.installaware.com/viewtopic.php?t=1092&highlight=) I thought I would use Get Exact OS Level to ensure that will only be installed onto the XP clients.
However nothing seemed to happen so I then used /l= to create a log. But all that did was write a series of opening/closing tags and no variables. Then I wrote each step to a custom log file.
I found the OS level being reported, when the XP client booted and the software was being deployed by GPO, still as 2003 instead of XP.
I suspect this is because the server is pushing the software out (and thereby running the MSI itself) instead of the client running the MSI. Is there anyway around this as sort of defeats the whole object of being able to run from a GPO object?
Thanks - John
GET OS LEVEL and GPO
Related to the original message:
Is there any reason why a MSI script could not be as short as the following?
I have added to the GPO Software Installation OK. The server still runs it correctly (due to the reported bug which IA do not seem to be doing anything about) but not when ASSIGNED to the client by the server at computer level. I can see the client saying it is installing when applying computer policy at boot up time and the event log on the client says it was successful but the OCX is not registered.
Everything I do seems to make the MSI relate to the server itself and not the client to which it is deploying. I have even added log statements and it only reflects what has been done on the server; not the client. In fact the client does not even create the log file (which is set by UNC).
I made sure everything is OK in the MSI databases on both server & client using MSFT's Windows Installer Cleanup Wizard. Other MSI's built using IA install/uninstall fine - the only difference is that they were all imported from a PackageAware result set.
Desperate for ideas?
Thanks - John
Is there any reason why a MSI script could not be as short as the following?
Code: Select all
Set Variable REFMANDIR to \\\\SHIPSERVER\\APPS\\MSL
Register Library $REFMANDIR$\\RFW32\\AWKONE.OCX
Apply Install (get result into variable SUCCESS)
I have added to the GPO Software Installation OK. The server still runs it correctly (due to the reported bug which IA do not seem to be doing anything about) but not when ASSIGNED to the client by the server at computer level. I can see the client saying it is installing when applying computer policy at boot up time and the event log on the client says it was successful but the OCX is not registered.
Everything I do seems to make the MSI relate to the server itself and not the client to which it is deploying. I have even added log statements and it only reflects what has been done on the server; not the client. In fact the client does not even create the log file (which is set by UNC).
I made sure everything is OK in the MSI databases on both server & client using MSFT's Windows Installer Cleanup Wizard. Other MSI's built using IA install/uninstall fine - the only difference is that they were all imported from a PackageAware result set.
Desperate for ideas?
Thanks - John
Who is online
Users browsing this forum: No registered users and 92 guests