flyingboz

sample _AD_ChangePassword function, Example 1 is failing with error 2, extended -2147352567 I have tried running as a full domain admin and standard user with same results. Any suggestions to debug? I am running latest production version of au3; server domain is 2012r2, fully patched.

Thanks for the reply / insight. I'm not interested particularly in anything more than a command line interface to allow the user to change their own password. While single-sign on has its uses, its not really germane to the core topic. If I give users full remote desktop access they have the permissions to change their password via the GUI. At its most basic, there should be a command line equivalent that asks the user to enter their old password, then their new one w/ confirmation. Conceptually, there shouldn't need to be any additional proof that the user is who they say they are, they've already been authenticated, and the remoteapp started. I don't think I should need a service or other 'trickery' involved, because I have access to the user environment -- I am setting the user default printer in the batch script that runs each time they initiate the remoteapp.

I'm looking at a situation where a client has an application deployed via RemoteApp, no full RDP desktop or web interface available. As the RemoteApp is published on a network share, it is invoked via a batch file, launched via a published .rdp file. I've run into an issue with being able to allow users to change their own passwords. I don't want to have to deal with changing users passwords, or knowing what they are; if I expire or require a password change, the users are simply locked out, there is no opportunity for them to change their password themselves. Ideally, I'd like to write or find a command line utility I could insert into the batch file that launches the remote app to address this deficiency. I've poked around in the ActiveDirectory UDF, which seems to be a great tool, but without a function written for the use case where the password change is desired to be forced upon the current user ( who is NOT an admin). Note: net user / domain requires admin rights. pspasswd, while awesome, also requires admin rights. Does anyone have a UDF or Function utility that they use to allow a user to change their own domain password from the command line? I've seen a couple of powershell examples, but I'd love to be able to compile or drop in a command line oriented passwd.exe utility that would work similarly to the *nix equivalent. The pspasswd sysinternals utility does not seem to have this use case in mind -- in my tests you have to be an admin to change a password.

Again, pls stop cluttering the thread w/ your personal attacks and close minded attempts to understand what was asked for in the first place.

specifically, the 'myerrfunc' code, and registering the event handler to get an actual error message may prove helpful. I use the cdoMailer extensively, and have found it to be solid, though the methods can be finicky.

Patently untrue for XP. Using only RegWrite and RegRead you can modify HKU trees for non logged on users in xp. I've done it and have working code to prove it. You can prove it to yourself by simply opening the registry as an administrator on an XP workstation, and viewing all of the SIDS that appear under the HKU tree. $username = RegRead("HKU\" & $key_name & "\Software\Microsoft\Windows\CurrentVersion\Explorer", "Logon User Name") Again, patently untrue. You're trying to answer a different question than the one that was asked. I asked for known working, currently being used solutions from someone who is doing this currently. You have thrown up five year old scripts that were not tested with windows 7. If I decide I want help debugging / updating five year old scripts, I'll post code snippets and ask for help in a thread that actually asks for that. I can't judge how helpful you are trying to be, but check my profile -- I've been here since 2003, and this ain't my first rodeo. I've been really patient with you to this point. Someone has done this, and will be by in a day or two, and actually be willing to help out. Until then, stop cluttering up the thread.

group policy editor not available on home editions -- there is a ms database link, however that does provide the mappings for registry / group policy. There may well be hacks involved that allow this edit; but not necessary given that gpedit is a shell to the registry.

What's the current preferred method for interacting with registry hives? I need to be able to modify / create / delete registry entries for users not logged in; and they are no longer accessible directly from the HKU registry branch by default. Ideally, I could get the XP behavior back; where each of the SIDS for users who had been logged on appear in the HKU section of the hive.

Noticed that WinSCP, a nifty little file transfer program, now sports a COM capable module. I was wondering if anyone has played around with it and perhaps gotten some syntax examples or the startings of an au3 compatible library.

_RunReadStd() is your friend.

Use the com error handler functionality to trap the error until it no longer appears.

all sorts of stats available through WMI. Of course, you could always calculate your own as you go. Lots of different metrics for estimating file transfer times; % of bytes, % of files; all pretty much a roll of the dice, esp. if you can't rely on constant b/w, latency, cpu/disk utilizations , etc..

haven't looked at the internals, but they weren't they were (obviously) cast to values which yielded expected functionality.

Umm. That seems a mighty thin hair to split. If code compiles / works as expected under version A, then fails to do so under version A+1 , that, in the world of what's real, is a script-breaking change. Just did another search for "default" in the script breaking changes log, and there is no indication in the "Script Breaking Changes" documentation that the Default keyword was now required, instead of having allowed aliases. Of course, if sophistry and semantics such as that indicated above ("changes that break scripts aren't script breaking changes"), then any further rational discussion is unlikely. Obviously, I will make the indicated changes to unbreak my broken script; and I appreciate the prompt response.

I have a compiled script from 2/2008 which works fine, compiled under whatever the release was at that time. Went to modify the script today, using 3.3.6.1; and was surprised to find that the InputBox() commands no longer appear, but functionally appear to no-op. That is, my inputbox() commands that are nested inside an infinite loop that can only be broken out of with proper user input are now simply infinite loops. I researched the "script breaking changes" link for v3 (http://www.autoitscript.com/autoit3/docs/script_breaking_changes.htm) and there was no mention of inputbox anywhere that I could find. The only change reference I could find related to the default location for inputbox display on multi-monitor setups. this line does not create an input box on 3.3.6.1 ; but did back in the day when it was compiled. $minimum_dollar_amount_to_include = InputBox("Minimum Dollar Amount To Include", "Please Enter a Dollar Threshold. Categories with total receipts less than this threshold will be ignored. Default is All Categories Included.", 0, " ", "-1", "-1", "-1", "-1", "30")