KB835732 scripting problem
Dear Wise Experts!!,
This is really weird I am being told to create an msi that should run on win 2k and win XP and should install the KB835732 update appropriately, that means the package should be WISE enough to detect the OS and apply the appropriate update. I need helppppppppppppppp!!!!!!!! I am gonna go crazy since I have tried all the things nothing works not even a VBScript.!!! I can attach the piece of my script or can give the package if somebody wants to go thru it.
here is the #$&#@ code
If DoUninstall then
set property UninstallPath to [WindowsFolder]$NtUnistallKb835732\spuinst.exe
If Do Install and VersionNT = 500 the
Set Property RunSetupPath to SourceDir\winxp\xpsp1hfm.exe
end
If Do Install and VersionNT=501 the
Set Property RunSetupPath to SourceDir\winxp\xpsp1hfm.exe
end
the same script is in USer Interface tab and Execute Immediate but not in execute deferred.
Now I am deploying this package using win2k server on win2k client and win xp client
but the unistall path does not comes up in the windows directory (whereas it should!!), please an urgent help would be great !!!
This is really weird I am being told to create an msi that should run on win 2k and win XP and should install the KB835732 update appropriately, that means the package should be WISE enough to detect the OS and apply the appropriate update. I need helppppppppppppppp!!!!!!!! I am gonna go crazy since I have tried all the things nothing works not even a VBScript.!!! I can attach the piece of my script or can give the package if somebody wants to go thru it.
here is the #$&#@ code
If DoUninstall then
set property UninstallPath to [WindowsFolder]$NtUnistallKb835732\spuinst.exe
If Do Install and VersionNT = 500 the
Set Property RunSetupPath to SourceDir\winxp\xpsp1hfm.exe
end
If Do Install and VersionNT=501 the
Set Property RunSetupPath to SourceDir\winxp\xpsp1hfm.exe
end
the same script is in USer Interface tab and Execute Immediate but not in execute deferred.
Now I am deploying this package using win2k server on win2k client and win xp client
but the unistall path does not comes up in the windows directory (whereas it should!!), please an urgent help would be great !!!
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
inert
19 years ago
I think you should download all of the patches for all OS's from MS.
Nest them into 1 MSI and do a customaction check for Windows Version (read it from the client registry) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion[ProductName].
So the installer knows which OS is running and so can start the correct KBpatch silent install.
With some luck you don't even need VB.
Nest them into 1 MSI and do a customaction check for Windows Version (read it from the client registry) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion[ProductName].
So the installer knows which OS is running and so can start the correct KBpatch silent install.
With some luck you don't even need VB.
Posted by:
wiseapp
19 years ago
Thanks a lot inert for your reply, sounds great relief to me, well I would try the suggestion but I would like to ask you one question the WISE API (VersionNT) that I am using to find out which OS is running on the target machine is similar to this or not!!!
Posted by:
inert
19 years ago
Yes, you should explicitely make a search for this regkeyvalue, in the Customaction sequence
it's either "Microsoft Windows XP" , "Microsoft Windows 2000" , however 2Ksvr is the same value.
But take a look in the WinInstaller SDK: "Operating System Property Values"
So you could also try the 'WindowsBuild' & 'ServicePackLevel' Properties.
it's either "Microsoft Windows XP" , "Microsoft Windows 2000" , however 2Ksvr is the same value.
But take a look in the WinInstaller SDK: "Operating System Property Values"
So you could also try the 'WindowsBuild' & 'ServicePackLevel' Properties.
Posted by:
wiseapp
19 years ago
Dear Inert,
I am really glad that you are so spontaneous regarding my problem, I would request you one more favour if you can tell me how to make a explicit search on these registry values since i dont have ne idea how to run this search. If you can provide me with the code i would be too glad. thanks for all ur help.
I am really glad that you are so spontaneous regarding my problem, I would request you one more favour if you can tell me how to make a explicit search on these registry values since i dont have ne idea how to run this search. If you can provide me with the code i would be too glad. thanks for all ur help.
Posted by:
inert
19 years ago
I'll be happy to help around here & there, but i also have a daytime....
Time is a luxury for us ICTers.
Meanwhile, try to (instead of using the VersionNT property)
-------
If WindowsBuild=2195 then
Execute Installed Program Windows2000KB835732x86ENU.EXE /silent (W2K)
End
If WindowsBuild=2600 then
Execute Installed Program WindowsXPKB835732x86ENU.EXE /silent (WXP)
End
---
Right after the InstallFinalize in Execute Immediate Sequence. The patches you can place somewhere in an Prorga~1\Patches directory or sumting.
May be smart to make an "If NOT Installed" statement though.
I didn't spend much time on it, but it seems to be working better than the VersionNT prop.
Be carefull when application-nesting though, customaction placement is critical.
I'll keep trying myself also, these sort of patches are a pain in the back, and in the future these kinds of things are bound to happen more often.
Time is a luxury for us ICTers.
Meanwhile, try to (instead of using the VersionNT property)
-------
If WindowsBuild=2195 then
Execute Installed Program Windows2000KB835732x86ENU.EXE /silent (W2K)
End
If WindowsBuild=2600 then
Execute Installed Program WindowsXPKB835732x86ENU.EXE /silent (WXP)
End
---
Right after the InstallFinalize in Execute Immediate Sequence. The patches you can place somewhere in an Prorga~1\Patches directory or sumting.
May be smart to make an "If NOT Installed" statement though.
I didn't spend much time on it, but it seems to be working better than the VersionNT prop.
Be carefull when application-nesting though, customaction placement is critical.
I'll keep trying myself also, these sort of patches are a pain in the back, and in the future these kinds of things are bound to happen more often.
Posted by:
wiseapp
19 years ago
Dear Inert:
This seems a gr8 relief to me as well but I should inform you that we can not have absolute path for the patches thats why we were using set property method(setting a custom created property value here) to deploy this patch by putting the path as \\abc\abc.exe , so is it safe to use execute program i mean will "execute program" work with relative path since i have a big doubt regarding this meanwhile i while try your code with set property. Thanks again for your time Inert , may god bless you !!!
This seems a gr8 relief to me as well but I should inform you that we can not have absolute path for the patches thats why we were using set property method(setting a custom created property value here) to deploy this patch by putting the path as \\abc\abc.exe , so is it safe to use execute program i mean will "execute program" work with relative path since i have a big doubt regarding this meanwhile i while try your code with set property. Thanks again for your time Inert , may god bless you !!!
Posted by:
inert
19 years ago
Ececute Program from Path has not ever let me down. (don't do relative path, this seems to work only with nested .MSI's)
Just make sure you know your Properties!
Success.
Just make sure you know your Properties!
Success.
Posted by:
wiseapp
19 years ago
Dear Inert:
Thanks a lot for your help but as I told you we cannot have absolute path for the installations . Any way I got the msi working by placing my script in execute deffered and setting source dir in execute immediate this seems to be working fine thru AD as well. But thanks a lot for your great help and quick responses . I have posted a new topic check out whether its of any use to you.
Thanks again and god bless you
Thanks a lot for your help but as I told you we cannot have absolute path for the installations . Any way I got the msi working by placing my script in execute deffered and setting source dir in execute immediate this seems to be working fine thru AD as well. But thanks a lot for your great help and quick responses . I have posted a new topic check out whether its of any use to you.
Thanks again and god bless you
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.