|
|
|||||||
Many companys use KIX scripting to update there workstations with hotfixes and service packs. To update workstations with different versions of IE you must type a lot. Maybe you can make an macro fot this. Kinds regards, Onno van den Berg |
||||||||
|
|
|||||||
macro? macro which updates IE? could you clarify your request a little? |
||||||||
|
|
|||||||
@UPDATEIE If that would be possible then... @UPDATEWINDOWSWITHSPx @UPDATEEVERYTINGWITHHOTFIXx @UPDATESYTEMROMWITHNEWREVISSION and some more ...would also be nice. Just typing @UPDATEIE and Kix would do the rest. Maybe he means something like a macro used in word or excel but that would also scripting though. |
||||||||
|
|
|||||||
What? Can't type in HFNETCHK? |
||||||||
|
|
|||||||
quote:That's what I mean. Maybe use MBSA? Uses HFNETCHK technology. Get MBSA here: download MBSA or read about HFNETCHK here: HFNETCHK [ 26. August 2003, 00:05: Message edited by: R2D2 ] |
||||||||
|
|
|||||||
With the tools out there - Altiris Mobile Automation KiXSMS SUS HFNETCHK MSBSA Do we need to add bloat to the KiXtart code? For example, running @UPDATEWINDOWSWITHSPx would have to query what is installed on the system, go to a website (or local repository), pull down the code, and install it. What about locked down users? Kent |
||||||||
|
|
|||||||
I couldn't agree with you more, Kent. Just checking the product version, CSD, hot fix level or something with some code and installing a patch or hot fix with the Task scheduler UDF , SU, SMS or whatever would be the way to go. |
||||||||
|
|
|||||||
he is probably just referring to a macro that enums: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components looking for IE hotfixes typically Qxxxxxx hopefully MS will eventually start making the IE patches go in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates like the other updates... |
||||||||
|
|
|||||||
Hello everyone, I shall try to specify my request for an macro to identify the installed version of Internet Explorer. What I meant is the following: For the installed operating system you have the macro @ProductType. So maybe it is possible to make an macro wich identifies the installed Internet Explorer browser. For example @IE = "Internet Explorer 5.5". I hope my request is more clearly right know. Kinds regards, Onno van den Berg |
||||||||
|
|
|||||||
you mean a macro that replaces: code:or?$IEver=readvalue("HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer","version") |
||||||||
|
|
|||||||
I vote against this suggestion. Why bloat KiX when a simple reg read can get it? |
||||||||
|
|
|||||||
if this is his suggestion, I'm against it too. |
||||||||
|
|
|||||||
What i meam is that you have different type of Internet Explorer browser version. For example: Internet Explorer 6 for Windows XP Internet Explorer 6 SP-1 Internet Explorer 5.5 with SP-2 Internet Explorer 5.5 Internet Explorer 5.01 Microsoft released different updates/hotfixes for the blaster worm. If you would like to install these patches with a KIX logon script it's a problem. You cannot find the right information with one READVALUE. Kind regard, Onno van den Berg |
||||||||
|
|
|||||||
why not? IE major version seems the only thing you need to read. 5.5 is trickier. for proper resolving, you might want to use: http://www.kixtart.org/board/ultimatebb.php?ubb=get_topic;f=12;t=000229 |
||||||||
|
|
|||||||
There is also this one http://kixtart.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=1&t=003748 |
||||||||
|
|
|||||||
doc, I quess that the UDF is kinda copy of that topic or the other way around so, did the chicken come before the eggs? |