Self Service Password Reset

[boomam]

One of the requirements for the program in the readme is AD but I'm not sure if that means it needs to be installed on a DC but that would make sense.

I have it installed on a DC here and if you had installed on a DC and working at the last place and it's not on a DC at the new place and doesn't work then sounds like a plan to me.

Ben

Right, ive got it AD installed on our IIS now, basic, no DNS/DHCP/Global Catalogue on it, just the AD.

However when i select the list of domain controllers, it lists:
AD01 - DCType=GC - Online.
AD02 - DCType=GC - Online.
IIS - DCType=DC - Online.
IIS - DCTyle=GC - Unavailable.

Why is the IIS listed twice? Is it because its only a DC with no global catalogue, so it lists the GC version as unavailable?
If i use a 2k3 MMC to see what DCs there are, it just lists AD01, AD02 & IIS.

[Irazmus]

Which version of SSPR are you running?

Up to version 2.1 SSPR needed to be run on a DC, from 2.2 onwards this limitation was removed and SSPR will run on a member server.

[boomam]

Which version of SSPR are you running?

Up to version 2.1 SSPR needed to be run on a DC, from 2.2 onwards this limitation was removed and SSPR will run on a member server.

Not sure which version, how do i tell?

Ive removed the AD off IIS, and put it back on with a full DNS & Global catalogue, but its still listing it twice? Once with its actual name, and once with its old name that it originally had for about a week?

Ideas on that?

It'll be sometime before i know if this change has made much difference to SSPR.

[Irazmus]

Not sure which version, how do i tell?

The version number should be listed in the readme file.
Alternatively, if your copy includes LoginAdmin.dll and cred.ini then you have 2.2 or 2.2.1, if not you're likely using 2.0 or 2.1.

Ive removed the AD off IIS, and put it back on with a full DNS & Global catalogue, but its still listing it twice? Once with its actual name, and once with its old name that it originally had for about a week?

Ideas on that?

None spring to mind right now, but others know AD much better than I do.

[boomam]

The version number should be listed in the readme file.
Alternatively, if your copy includes LoginAdmin.dll and cred.ini then you have 2.2 or 2.2.1, if not you're likely using 2.0 or 2.1.

Its got the loginadmin.dll.

On a side note, adding AD to the IIS still doesnt fix the problem. .
Its odd, because it says it has reset the password, but it doesnt reset.
If i do the same change in AD, the password changes instantly?

[Irazmus]

In that case I'd check the credentials in cred.ini (and the user's AD rights). If they check out, unregister and reregister LoginAdmin.dll
regsvr32.exe /u C:\Inetpub\LoginAdmin.dll
regsvr32.exe C:\Inetpub\LoginAdmin.dll

If that still doesn't solve it, we'll have to do some more digging.

[boomam]

In that case I'd check the credentials in cred.ini (and the user's AD rights). If they check out, unregister and reregister LoginAdmin.dll
regsvr32.exe /u C:\Inetpub\LoginAdmin.dll
regsvr32.exe C:\Inetpub\LoginAdmin.dll

If that still doesn't solve it, we'll have to do some more digging.

Ive unregistered and reregistered the dll, and ive removed AD/GC/DNS from the IIS as it doesnt need it anymore.
Just waiting for it to restart and we'll see how it goes...

[boomam]

Nope, still doesnt work. .

[Kevin_Beaumont]

When I log in as a test account and register for the service, it appears to register fine but when I look at the database the 'username' field is empty.

Any ideas anyone?

Folks, has anybody else seen this one? I've got the same problem. I can register, I can update, but I can't reset (says the username isn't found) or get in the admin directory:

"error '80005000'

/admin/auth.asp, line 35"

From what I can see it can't determine the CurrentUser, not sure why...

Obviously, it isn't much use without the admin interface or the reset directory working

Cheers!

[rvdmast]

error 80005000 usually indicates an invalid path. Which to me suggests that there is something wrong with your FQDN variable (in line 35).
Did you modify the FQDN= line in config.asp to reflect your domain name?
Are you sure it's correct?

[Kevin_Beaumont]

Turned out I'd messed up and set the permissions wrong on the folders - I'd given full Anonymous access to everything, which obviously doesn't work.

[plexer]

Glad to see people are still ticking over with this.

Ben

[Kevin_Beaumont]

Our implementation stalled as we use thin client (Windows Server 2003, Remote Desktop to the servers) and the "Password Reset" window doesn't appear on the login screen for obvious reasons

[plexer]

Sorry can you clarify for me why it doesn't work on a thin client setup?

Thanks.

Ben

[rvdmast]

I'm guessing here, i think what he means is that SSPR itself works just fine, but the trick to get a password reset button on the login screen ( the C+A+D screen) doesn't work, because in a terminal server/thinclient environment there is no C+A+D screen.
Because the login screen is handled by the thinclient OS.

Just as there is no C+A+D screen when you use mstsc.exe to connect to a remote server: the login is handled by mstsc.exe

If he used my application to get a reset button on the login screen, it probably displays only on the login screen of the server's console.