Jump to content

Matthew VanDerlofske

Members
  • Posts

    18
  • Joined

  • Last visited

Matthew VanDerlofske's Achievements

Seeker

Seeker (1/7)

0

Reputation

  1. Thanks for the help, you get so used to using one product for all your automation tasks and you forget to see if it is already part of the OS.
  2. I have about 80 servers that I reboot each week, they are our backup servers so I also have an unlock script that runs on startup. I would like to automate the login of each of these servers as well. They are all always logged in so any members of the helpdesk can check on a backup or look at the history. I have tryed to get this to work but have not been able to so far. Any ideas?
  3. Yeah, and I can setup windows backup to backup the system state on reboot, however I cannot find a way to do a mass roll out that way. If I could create a exe that would initiate the backup on reboot I could roll that out easily.
  4. I have been looking into different ways to do this. I would like to prove autoit's worth to my coworkers, can autoit initiate a system state backup? I have not seen a way to do this through autoit.
  5. A non admin user can read the file. Like I said the autoit executable works fine when it is not called by a login script. Here is what the autoit window info tool reported: Press CTRL-ALT-F to pause the display. >>>>>>>>>>>> Window Details <<<<<<<<<<<<< Title: AutoIt Error Class: #32770 Size: X: 363 Y: 306 W: 303 H: 185 >>>>>>>>>>> Mouse Details <<<<<<<<<<< Screen: X: 39 Y: 6 Cursor ID: 2 >>>>>>>>>>> Pixel Color Under Mouse <<<<<<<<<<< RGB: Hex: 0x9EE8FF Dec: 10414335 >>>>>>>>>>> Control Under Mouse <<<<<<<<<<< Size: Control ID: ClassNameNN: Text: >>>>>>>>>>> Status Bar Text <<<<<<<<<<< >>>>>>>>>>> Visible Window Text <<<<<<<<<<< OK Line 0 (File "\\docstar\setup\Test1.exe"): Run("\\docstar\SETUP\SETUP.exe /s") Error: Unable to execute the external program. The directory name is invalid. >>>>>>>>>>> Hidden Window Text <<<<<<<<<<<
  6. I have tryed using group policy to call the autoit executable as well that had the same result. I then tryed to disable all local group policies, that had the same results as well. I am sure that the problem is envirenmental becuase it works fine in my test envirenment, but I am not sure what is causing the issue. Can it be that what ever is calling the autoit file does not have permissions to access the setup.exe?
  7. I have a login script that calls an autoit executable, the auto it run an installation as the administrator. When I run the Batch file while logged it the process completes successfully. WHen I run it while logging in I recieve the following error: Autoit Error: Line 0 (File "\\docstar\setup\test1.exe") Run ("\\DOCSTAR\SETUP/setup.exe /s") Error: Unable to execute the external program. The directory name is invalid. I have tryed running this with a mapped drive as well that did not work. I also disabled the group policy that forces a login script to complete prior loading the desktop. Any Ideas? ; <AUT2EXE VERSION: 3.1.1.0> ; ---------------------------------------------------------------------------- ; <AUT2EXE INCLUDE-START: C:\Program Files\AutoIt3\Examples\Docstarinstall.au3> ; ---------------------------------------------------------------------------- ;Credentials $USERNAME = "admin user" $Password = "password" $Domain = "domain" ;Check the version $ver = FileGetVersion("C:\Docstar\dsclient.exe") IF $ver <> "3.4.0.9" Then ; Note the versions listed have an extra 0 in them so for 3.5.4 it will be 3.5.0.4 ;Message to users. Can be commented out if not needed, Installation will not start until OK is pressed. MsgBox(0, "Important DocSTAR Update", "A Docstar Update is currently being applied, please" & @CRLF & "do not launch DocSTAR until the update has completed" & @CRLF & "and you have rebooted your computer (You will recieve" & @CRLF & "a prompt to reboot when the update has completed). You" & @CRLF & "can use your computer while the update is being preformed." & @CRLF & "If DocSTAR starts automatically you will need to close it" & @CRLF & "before the install will start") ;Wait 2 minutes before starting the installation ;Sleep(1200000) ;Check to make sure Docstar is not running WinWaitClose("DocSTAR") ;Login as the user specified above Runasset ($username, $Domain, $password) ;Run the installation. Note: Do not change the orientation of the slashes. Run("\\docstar\setup\Setup.exe /s") Endif ; ---------------------------------------------------------------------------- ; <AUT2EXE INCLUDE-END: C:\Program Files\AutoIt3\Examples\Docstarinstall.au3> ; ----------------------------------------------------------------------------
  8. Having an issue with spaces when calling a program. to resolve I need to put quotes around a string. How do I do that. Here is my code: #include <GUIConstants.au3> GUICreate(" My GUI input acceptfile", 320,120, @DesktopWidth/2-160, @DesktopHeight/2-45, -1, 0x00000018); WS_EX_ACCEPTFILES $file = GUICtrlCreateInput ( "", 10, 5, 300, 20) GUICtrlSetState(-1,$GUI_DROPACCEPTED) GUICtrlCreateInput ("", 10, 35, 300, 20) ; will not accept drag&drop files $btn = GUICtrlCreateButton ("Ok", 40, 75, 60, 20) GUISetState () $msg = 0 While $msg <> $GUI_EVENT_CLOSE $msg = GUIGetMsg() Select Case $msg = $btn exitloop EndSelect Wend Run("C:\DOCSTAR\DSCLIENT.EXE " & GUICtrlRead($file)) The issue is that if a files location has spaces it will not work. I need to put quotes around the file path.
  9. I know that this is a vary easy question for someone to answer. How do I check what button was pressed when your using a msgbox
  10. So simple no wonder I was missing it. Thank you
  11. So this script runs great when using the run script option, but when I compile it to a EXE it just keeps running and never exits. Here is the code: $Printer = "LDLAPChecks" $Server = "PlanetPress" $answer = InputBox("LDL Ap Checks", "How meny checks do you want to print?") $answer1 = $answer FileDelete("C:\APChecks.txt") $file = FileOpen("c:\APChecks.txt", 1) While $answer1 > 0 FileWrite($file, "." & @CRLF) $answer1 = $answer1 - 1 WEnd FileClose($file) $LprCmd = "lpr -S " & $Server & " -P " & $Printer & " C:\APChecks.txt" Run($LprCmd, @TempDir, @SW_HIDE) MsgBox(4096, "AP Checks Printed", $answer & " Print Job(S) Sent Successfully") FileDelete("C:\APChecks.txt") Exit
  12. No Not really, I want to log the memory usage of a process every few minutes.
×
×
  • Create New...