TXTechie

Thank you, seadoggie01. I think I understand. Thank you for responding to my question!

Never mind. I've got it working, basically just using the following lines of code before displaying the GUI: Local $idDummy = GUICtrlCreateDummy() Local $aAccelKeys[7][2] = [["{TAB}", $idDummy], ["{ENTER}", $idDummy], ["{SPACE}", $idDummy], ["{LEFT}", $idDummy], _ ["{RIGHT}", $idDummy], ["{UP}", $idDummy], ["{DOWN}", $idDummy]] GUISetAccelerators($aAccelKeys, $hGUI) This is AWESOME, pixelsearch! Thank you so VERY MUCH!!!

This looks is working EXACTLY how I want it to, pixelsearch! Thank you for this! However, I'm using OnEventMode [Opt("GUIOnEventMode", 1)], how would I code this for OnEventMode?

Thank you, seadoggie01. It looks like I could use _IsPressed as a workaround, but how would I cancel the event after capturing it via _IsPressed? I am also concerned about the performance of my GUI, if I used _IsPressed (even if I use the recommendation of opening the 'user32.dll', as stated in the Help). Is there not a "better" more of a "best practice" way within AutoIt to do what I want to do?

I've developed a simple GUI form with a background image and just two buttons. I don't want either of the two buttons to accept any keyboard input so that the user doesn't inadvertently or accidentally press the Tab and/or Enter keys while typing when my GUI is launched via SCCM deployment. I've set both buttons to have the $GUI_SHOW+$GUI_ENABLE+$GUI_NOFOCUS states, but both of them are in the tab order (I cannot find a way to remove them both from the tab order so that pressing the Tab key will NOT cycle between them) and one of them still has the default focus so that when a user presses the Enter key one of the buttons gets chosen (whether or not that was the intention of the user). Is there any way that I can basically disable keyboard input (at least for the Tab and Enter keys) to my GUI and/or the two buttons on the GUI form so that only mouse actions will select (or otherwise interact with) the appropriate button? Or, is there some other way to accomplish this as a workaround? Regards, TX Techie

That's a great script, @VIP! My current GUI script uses OnEvent mode, do I need to modify your script any in order to use it in OnEvent mode?

Well, so much for my forum searching skills. Thank you, @faustf. I'll take a look at those message threads that you shared with me. I really appreciate your help!

Hello Everyone, I've developed my own GUI using AutoIt and I'm allowing users to minimize the GUI, but I also want to include some kind of timer so that it will automatically restore the GUI after something like 30 minutes or an hour. However, I also want them to be able to manually restore the GUI by clicking the application's icon in the taskbar. I've searched through the forums, but I'm not sure how to get started. Any ideas or functions to research are appreciated! Regards, TX Techie

Hi @Subz, Thank you for your response. One of the most important pre-checks I'm performing in the AutoIt script is to check to see if the Win10 Feature Update (install.wim) has first completely copied to the local PC before the user sees anything. Once my AutoIt pre-check determines that the Feature Update had completed copying, then (and only then) will my GUI be displayed in order to prompt the user to start the Win10 upgrade. So, I need to execute the AutoIt executable daily in order to perform this and other pre-checks outside of the Task Sequence.

Hello Everyone, I'm hoping someone as tried this before or can otherwise assist me with this task. I've got an AutoIt script that I've developed to perform some pre-launch tasks and also provides a GUI for prompting the user (when appropriate for our needs). The final task that I need this AutoIt script to do is to start/lauch/kickoff an OSD Task Sequence that is advertised to the user via SCCM's Software Center. Does anyone know how or have any ideas how I could go about doing this? All assistance is appreciated! Regards, TX Techie

Wow! This is crazy! I must have something weird going on with my primary (and AutoIt developer) PC! I compiled one of my scripts that use _IEAttach and copied it to my 2 test PCs (1 = Win10 and 1 = Win7) and it worked fine on both! Sounds like it's time to "refresh" my primary PC. What a pain! 😥 @FrancescoDiMuro & @Nine - I want to thank you both, very much, for your assistance (and patience)!

I'm using the latest release version of AutoIt (3.3.14.5) and I can successfully get a Window handle for my open IE window using WinList: #include <IE.au3> Const $navOpenInNewWindow = 1 Const $navOpenInNewTab = 2048 Const $navOpenInBackgroundTab = 4096 Const $navOpenNewForegroundTab = 65536 Const $sPrimaryServer = "server" ; Retrieve a list of window handles. Local $aList = WinList() ; Loop through the array displaying only visable windows with a title. For $i = 1 To $aList[0][0] If $aList[$i][0] <> "" And BitAND(WinGetState($aList[$i][1]), 2) Then If StringInStr($aList[$i][0], "Internet Explorer") > 0 Then ConsoleWrite("Title: " & $aList[$i][0] & @CRLF & "Handle: " & $aList[$i][1] & @CRLF) Local $oIE = _IEAttach($aList[$i][1], "hwnd") $oIE.Navigate2("https://" & $sPrimaryServer & ":8444/", $navOpenInNewTab) EndIf EndIf Next But, when I pass the handle from WinList into _IEAttach, I get the same "--> IE.au3 T3.0-2 Warning from function _IEAttach, $_IESTATUS_NoMatch" error!:

In fact, NONE of the _IEAttach examples from the AutoIt Help file work on my PC - they all throw the same "--> IE.au3 T3.0-2 Warning from function _IEAttach, $_IESTATUS_NoMatch" error! I'm running a fully patched Windows 10, 64-bit (release 1809) PC. What's going on?

@FrancescoDiMuro Thank you for your assistance. I guess I should have stated that I haven't had any luck with _IEAttach either. Here's my code: #include <IE.au3> Const $navOpenInNewWindow = 1 Const $navOpenInNewTab = 2048 Const $navOpenInBackgroundTab = 4096 Const $navOpenNewForegroundTab = 65536 Const $sPrimaryServer = "server" Local $oIE = _IEAttach("", "instance") $oIE.Navigate("https://" & $sPrimaryServer & "/", $navOpenInNewTab) And I receive the following error: What am I doing wrong?

Hello Everyone, I'm looking for a way to use an already open Internet Explorer (IE) window (if one is up and running) and then navigate to a new URL in a new IE tab. I thought that _IECreate would easily meet my needs. However, when I use the following script: #include <IE.au3> Local $oIE = _IECreate("https://" & $Server & ":8444/", 1, 1, 0, 1) ...with one or more open IE windows, it still opens yet a new IE window. Are there any other ideas for how to reliably use an already open IE windows and then how to open a new tab in IE to navigate to a new URL? Regards, TX Techie

@FrancescoDiMuro, thank you. However, I'm looking for a quick check that I can do without launching a browser and looking around, something like the _INetGetSource function. Would this be considered a good or best practice kind of check?: #include <Inet.au3> ; Check to see if the primary web server is up and running. _INetGetSource('<primary server URL>') If @error = 0 Then ; Launch the primary server's URL. ShellExecute('<primary server URL>') Else ; Launch the secondary server's URL. ShellExecute('<secondary server URL>') EndIf

Hello Everyone, We have a primary and secondary Cisco Unified Intelligence Center (CUIC) reporting server that our Customer Service Agents will be using soon. Rather than confuse them with two separate shortcuts to to the primary and backup, I was going to create a single shortcut that points to an AutoIt executable that will first check to see if the primary web server/site is up and running and if so - launch the URL to it and - if not - launch the URL to the secondary server. I've got code working already just pinging the server using the AutoIt Ping command, but I want to also handle when the server can be pinged successfully but the web page is not working for whatever reason. So, what is the best way - what AutoIt command can I use - to verify just that the web page is running properly on the web server for me to perform my check against? Regards, TX Techie

Thank you for your response, SadBunny. It caused me to dig deeper into my scripts and it's unrelated to AutoIt. Please disregard this post/message thread. TXTechie

I normally launch things silently, but now I want to launch a batch (.cmd) file and have it run as normal displaying it's standard output to the user. Whether I use ShellExecuteWait or RunWait, the command prompt window is displayed, but the output is blank (although I know that the batch file is processing normally because it also produces a log file). If this is because AutoIt is re-directing the standard I/O of the batch file/console window, is there a way I can bypass the I/O redirection? Thanks, TXTechie

Hello Everyone, I was just made aware of the free PowerShell App Deployment Toolkit and wanted to share it here. One could fairly easily customize this toolkit by adding the AutoItX DLL/COM control to it thereby utilizing the AutoIt PowerShell CmdLets making it a complete solution for all types of deployments! Regards, TXTechie

You might also just do the work of finding the Product Keys from within AutoIt itself - see this forum thread:

I have found the following registry keys reliable: HKLMSOFTWAREMicrosoftWindows NTCurrentVersionProductName HKLMSOFTWAREMicrosoftWindows NTCurrentVersionCurrentVersion TX Techie

Hi BrewManNH, Given what you just stated about your company and work environment, I thought you might be interested in this: 95% of bank ATMs face end of security support (March 4, 2014) [CNN Money] Regards, TX Techie

The company I work for is fairly frugal and our IT organization is also frugal (maybe even more so). I was told that Imprivata was chosen during the previous evaluation of potential SSO solutions because it was less expensive. The imprivata solution has been a waste of time, money and effort - all across the board. My coworkers, who manage it and were trained on it by Imprivata - were not at all impressed with the training they received (they were also NOT impressed at all with the complexity and the lack of capabilities of the Imprivata solution). This time around, our Director - who is very frugal (doesn't pay for a texting plan on his own cell phone) chose to go with Okta. My director is also a very good negotiator and has gotten us some very good deals from many IT-related suppliers. Since he told me that he couldn't tell me about our pricing because it is a negotiated rate, this tells me that he probably got us a pretty good rate compared to MSRP. Please remove Imprivata from your list of options! I don't know enough about the other two solutions to be of any value to you. I can ask if either were part of our research or evaluation and why we chose not to go with them, if you desire.

Hi JLogan3o13, We have been using Imprivata (which required deploying the Imprivata OneSign Agent to all of our PCs) for about a year or so. It's actually considered a pseudo-single sign-on solution. It is a pain and the wrong way to go about it, in our opinion (being heavily reliant on a client-side component, very hard to manage and use). We have decided to replace Imprivata with Okta, which is supposed to be a true, full single sing-on solution (web-based, etc.). We will be implementing it this year.