hello
When I install my app in active directory, the app gets installed on the server. This should not happen
this is described in:
http://forums.installaware.com/viewtopi ... ight=group
this does not happen with Wise install
When is it going to be fixed?
regards
ross
group policy bug
Hi Ross,
This is a confirmed logic bug for InstallAware and GPO deployment, however, if you have a look through the thread, Michael does actually indicate a valid work around by specifying a "magic" variable that you can pass to your installer in order for it to activate.
I should note that in the thread the other user is setting the Miniumum requirement to XP and not expecting it to install on Win2003 or Vista, however, this is flawed; XP version is *lower* than Win2003 or Vista, and setting the *minimum* version to XP will allow the installer to activate on XP or HIGHER - so XP, Win2003, Vista and Longhorn.
Hope this helps.
This is a confirmed logic bug for InstallAware and GPO deployment, however, if you have a look through the thread, Michael does actually indicate a valid work around by specifying a "magic" variable that you can pass to your installer in order for it to activate.
I should note that in the thread the other user is setting the Miniumum requirement to XP and not expecting it to install on Win2003 or Vista, however, this is flawed; XP version is *lower* than Win2003 or Vista, and setting the *minimum* version to XP will allow the installer to activate on XP or HIGHER - so XP, Win2003, Vista and Longhorn.
Hope this helps.
Andy Neillans
Andy,
As the original reporter of the problem, the suggestion made by Michael did not work because we are installing the software via GPO on the server, not running manually on the client. Adding a command line option is a non-starter as there is only one entry in the GPO to apply to everything.
Nor did trying to use the minimum operating system variable. If you read my thread, I suggested making the variable specific i.e. ONLY IF the OS = xx then install on xx not if the OS >= xx then install it.
I think you also need to read the related topic http://forums.installaware.com/viewtopic.php?t=2052&highlight= which nobody from IA has responded to.
I re-emphasise that all other non-IA MSI's I have tested work 100%. For time being, due to lack of action/response, I have had to stop using IA as it is corrupting files on the server due to this behaviour & and cannot be relied upon to be used in a GPO environment.
John
As the original reporter of the problem, the suggestion made by Michael did not work because we are installing the software via GPO on the server, not running manually on the client. Adding a command line option is a non-starter as there is only one entry in the GPO to apply to everything.
Nor did trying to use the minimum operating system variable. If you read my thread, I suggested making the variable specific i.e. ONLY IF the OS = xx then install on xx not if the OS >= xx then install it.
I think you also need to read the related topic http://forums.installaware.com/viewtopic.php?t=2052&highlight= which nobody from IA has responded to.
I re-emphasise that all other non-IA MSI's I have tested work 100%. For time being, due to lack of action/response, I have had to stop using IA as it is corrupting files on the server due to this behaviour & and cannot be relied upon to be used in a GPO environment.
John
Most GPO install systems that I've used allow you to specify additional command line parameters for the client side installs.
What system are you using?
As for an Exact OS identification, you can actually add this as an IF block - just check for an upper and lower limit.
The problem with this bug is we have not had many "official" reports of it - detailed information logged to us via the forum or by sending information to support at installaware dot com. If more people were to report this bug, and provide enough information for debugging, we would gladly investigate. I'm sure that you too are aware that not much can be done without sufficient reports and information. Looking through our support database, it appears we have had less than a six reports, and only three with decent information.
What system are you using?
As for an Exact OS identification, you can actually add this as an IF block - just check for an upper and lower limit.
The problem with this bug is we have not had many "official" reports of it - detailed information logged to us via the forum or by sending information to support at installaware dot com. If more people were to report this bug, and provide enough information for debugging, we would gladly investigate. I'm sure that you too are aware that not much can be done without sufficient reports and information. Looking through our support database, it appears we have had less than a six reports, and only three with decent information.
Andy Neillans
I am using Win2003 Small Business Server R2 and XP clients.
There is no way to add a command line action to the GPO Software Installation without creating MST transform files which I have never had to do when just installing something to all the clients. Even using something like MSIEXEC would not help that I can see.
I think if this http://forums.installaware.com/viewtopic.php?t=1578&highlight=cmdline thread had gone to conclusion then it would have been seen what options are available. The original poster was correct in stating that Michael may have been confused with SMS.
Rgds John
There is no way to add a command line action to the GPO Software Installation without creating MST transform files which I have never had to do when just installing something to all the clients. Even using something like MSIEXEC would not help that I can see.
I think if this http://forums.installaware.com/viewtopic.php?t=1578&highlight=cmdline thread had gone to conclusion then it would have been seen what options are available. The original poster was correct in stating that Michael may have been confused with SMS.
Rgds John
Ahh.
I'm afraid that we have not tested with SBS GPO system, and only test with the "full" implementations.
However, initial testing (I have an SBS server here) indicates that we are going to have difficulty identifying that we are in GPO mode and prevent the installation - tracking the installation calls, the GPO system is actually running the MSI when it is added (which is strange)...
We will investigate, but as I say, we cannot guarantee an instant fix as it will have to be prioritised with everything else I'm afraid.
I'm afraid that we have not tested with SBS GPO system, and only test with the "full" implementations.
However, initial testing (I have an SBS server here) indicates that we are going to have difficulty identifying that we are in GPO mode and prevent the installation - tracking the installation calls, the GPO system is actually running the MSI when it is added (which is strange)...
We will investigate, but as I say, we cannot guarantee an instant fix as it will have to be prioritised with everything else I'm afraid.
Andy Neillans
Who is online
Users browsing this forum: Google [Bot] and 106 guests
