Search

You searched for the word(s): userid:656462

Matching Posts

  • Re: basic way for users to change there own passwords...?

    Great, that helps a lot. It's still not going to solve the problem of legitimate obfuscated error codes (e.g., user does not have rights to change their own password, will get a numerical error, generating a helpdesk call), but the convenience makes it worthwhile. Thanks.
  • Re: basic way for users to change there own passwords...?

    If you've got any links to further reading, I'd sure love to know how to tweak it. It seems like the ideal utility, if you can get around those deficincies.
  • Re: basic way for users to change there own passwords...?

    This, perhaps? http://www.petri.co.il/enable_password_changing_through_owa_in_exchange_2003.htm I wouldn't recommend it. It doesn't work with UPNs, and you have exactly the same problem as you do with the CP: error messages are too technical. Try using that utility to change your password when your account doesn't have the ability to change its own password. The error message you get? A number.
  • Re: basic way for users to change there own passwords...?

    Some of your alternatives: 1) Modify the code in ChangePassword.ascx.cs (part of CorePlugins) to provide more user-friendly feedback. Specifically, the line "lblErrorMsg.Text = MPSUtilities.GetError(mpsResponse)". This will require learning a little C# and getting your hands on a compiler. Maybe someone else here in the group has built a suitable replacement. It's on my own todo list, but it could be months before I get to it. 2) Set up a terminal server or Citrix server and allow users to log on
  • Re: Strange password reset behavior in the Control Panel

    Similar findings at this thread: http://forums.asp.net/thread/1179816.aspx Rebuilding CorePlugins.dll is the solution. Anyone can do this using freely available tools, such as SharpDevelop (or the "free as in beer" version of MSVC#), but as a convenience I've posted a link to a working CorePlugins.dll for download in the thread above, if you're okay with downloading a DLL for your production system from an unknown source.
  • Re: Provisioning with multiple DC’s

    I'm not sure that's possible without source-editing and recompiling several of the MPF's DLLs. They're relying on ADSI to tell them which DC to query; you can tell ADSI to bind to a specific server, but that would have to be done in the source code, based on what I've seen of the code so far. This could be symptomatic of a much bigger problem, though. You may want to scour DNS to ensure both DCs are in sync, and carefully review the event logs of both as well. In our own two-DC environment, for some
  • Re: Users can't change password or update info in the sampleweb

    Yes, it's working for me. I'll still get that very mysterious "constraint violation" error if a user cannot change their own password. The forum doesn't allow attachments, so I've zipped it up and put it here: http://tinyurl.com/rjs8f That ZIP contains CorePlugins.DLL. Copy it (after making a backup of the original) into this folder: C:\Program Files\Microsoft Hosting\Provisioning\Samples\MPSSampleCP\bin (Assuming you haven't moved the CP out of that path, of course.) You shouldn't need to restart
  • Re: MPS on same server as DC?

    Yes. Both Microsoft and VMware have made their software-based solutions free (as in beer), though I didn't get very good results running more than about 4 VMs on a server at once with either of them. Using ESX I get radically better performance and consolidation. Since the consolidated solution only requires 4 servers, though, you could potentially build the whole thing inside VMware Server / Microsoft Virtual Server R2. As an added bonus, you can burn everything to DVD and make your lab completely
  • Re: Users can't change password or update info in the sampleweb

    Aha! I tried one last test. I paid particular attention to everything I was doing in the interest of accuracy, but someone else will need to verify this independently to prove it. I copied the original CorePlugins.dll back into bin. Guess what? 2-field version of the form. Then I wiped and copied the entire CorePlugins project (folder) from its original, and recompiled CorePlugins.dll without making any changes . The size of the DLL changed, and I get the 3-field version of the form. Hypothesis:
  • Re: Users can't change password or update info in the sampleweb

    I did some further investigation - unfortunately, the CP's behavior appears to have changed on me during testing, and now I can't be sure I'm testing accurately. I seem to have fixed the problem, but I don't quite understand why. I got into the CorePlugins project, and edited ChangePassword.ascx.cs, the code-behind for that page. I noticed this section: if ( Utilities . RemoveDCFromLdap ( PreferredDC , CurrentUser . LdapPath ) == Utilities . RemoveDCFromLdap ( PreferredDC , CurrentContext . LDAPPath
Page 1 of 2 (20 items) 1 2 Next >