wesb

Smartee...way to think outside the box!! All I had to do was use script B to call script A with a RunWait then continue to run script B and get the info posted to the ini...Thanks a bunch...way to end the work week!!

I am guessing Outlook is not configured for that user (Administrator)...this morning, I tried shelling it out using both the Administrative command prompt and the user command prompt...it worked fine with user command prompt and failed on the Administrative command prompt... I have tried to call a started script from the primary to then launch a third script but it seems the same issue continues. If outlook is closed...the email will be created and then sent once outlook is opened...only i cant force outlook to close just to send my response and too many of my users never shut the machines down...only put it to sleep.

Thanks Jayson...i have tried calling another script that calls another script that calls the mail script and still get the same error. Once i remove the #requireAdmin from the first script...all works fine except that my application doesnt have the rights needed to perform all the necessary functions of remediation....grrrrrr

I have been looking all through the forum and I havent been able to find anything on how to elevate a portion of a script or just a function with admin rights to work around the UAC and then get back to running the script as or with user rights. is there a switch to turn on #requireadmin and then turn it back off midway through a script? I thought about using RunAs but that wont work without passwords...i find that if I use RequireAdmin in script 1 and then call script 2 from script 1, 2 launches automatically as Admin and instead I need it to run as end user. thanks,

Okay Water...thanks...before you go on a mission, the problem is in calling the script after using the #RequireAdmin in my parent scripts. I have to find a way to run this piece as the logged in user. You see I have a health check application that requires read and write access to the registry, WMI etc and based on what it finds, it will then perform remediation steps and these steps require the elevated access. When it finds things it cant fix, I am trying to get it to email the issue to us so we can open a ticket and notify the end user. Calling the email piece from the check script calls it as Administrator and so that account has no access to the outlook application. Thanks for all the work you and everyone else does.

Hello...I have a question. I do not seem to be able to get the send mail to work even at the easiest level. i dont get an error, i get nothing...for example i have this test bit of code... ------------------------------------------------------------------ #RequireAdmin #include <OutlookEx.au3> $oOL = _OL_Open() _OL_Wrapper_SendMail($oOL, "me@mycompany.com", "", "", "Testmail", "<b>Test</b>", "", $olFormatHTML, $olImportanceHigh) --------------------------------------------------------------------------------------------------- I have outlook open. i run this script and nothing. My setup here is Win7 64 with 32 bit outlook 2010. i have this similarly as a snippet in an application and i get an "Error: Variable must be of type object" error. and of course it lists a line number that is not possible to dicern or find...any ideas?? could the issue be the setup i am currently running? thanks,

My bad...just goes to show you that even when you think you know what youre doing, you (me) can still screw up...controlclick on the control number fixed the whole dang thing...thanks for making me go back and RTM.

MPH...thanks but the windows wont close without an action or click on them and i cant get the click to take place... thanks for the idea though

Psalty, I am responsible to ensure my end users don't install software that is not approved by the company I work for. We have blocks in place to keep these things from running via ePO etc. but in order to then clean it from the systems remotely without having to force the end user to come into the office is where this comes into play for me. I create the packages to send out via SCCM and we can then do a silent uninstall. Used to be simple up to WinXP...here is the sample I have right now...the first 3 lines should be enough but the uninstall doesnt go silent...causes 3 prompts. This app is considered spyware according to threatexpert: (I am not one to just drop links into forums ) #RequireAdmin AdlibRegister("MyAdlib") Run(@ProgramFilesDir & '\Software Informer\unins000.exe /S /v') WinWait('Software Informer Uninstall','Software Informer uninstall complete.') Func myadlib() If WinExists('Uninstall', 'Would you like to keep your settings?') Then WinActivate('Uninstall', 'Would you like to keep your settings?') ControlClick('Uninstall', '&No', 1) EndIf If WinExists('Software Informer Uninstall', '&Yes') Then WinActivate('Software Informer Uninstall', '&Yes') ControlClick('Software Informer Uninstall', '&Yes', 1) EndIf If WinExists('Software Informer Uninstall','Software Informer uninstall complete.') Then ControlClick('Software Informer Uninstall', '&Ok', 1) EndIf EndFunc ;==>myadlib

I am having a similar issue i know on 64 bit Win7...havent tried it yet on 32 bit to see if the results are the same. A WinWait never identifies the window, the Adlib doesnt do what its supposed to on the windows when they pop up. I am trying to do a silent uninstall of an unapproved software

Nevermind...I just need to take more time off during the weekend. I figured it out in about 10 minutes tonight. Please disregard.

I am trying to figure out how to read a text or log file to see if any of the special characters ^!{ exist anywhere in the file. I havent been able to figure this out and its driving me nutz cause i am sure it is not or shouldnt be that difficult. any help would be appreciated. thanks all.

Does anyone have an idea on how to search the registry for say all keys with the same name? I am looking to search the hkcu for all keys with value 001f6700 exists. then i want to see whether the value 001e3001 exists in the same subkey

Awesome...can you say "DUHHHH!" boy do i feel stupid. thanks a lot for seeing what i had right infront of me...gotta create the folders first. One of those dayz

first of all, love autoit...i have recently run into a problem with running scripts on some machines. I get the error "Unable to open file". i have rewritten the script on one occasion in ver 2.64 and it ran fine. I didnot do that with this one i just wrote. It ran fine on one WinXP machine SP1 patched but did not run on another same image as the first. Any ideas?? I even ran other 3.0 scripts on the failed machine and they ran fine. thanks,