I have the HelpDesk web interface setup and I have a Create User task that our help desk can user to create new users. I have a Property Pattern setup that sets some default values including the User Logon Name (pre-Windows 2000). When I'm creating a new user using that form it populates the User Logon Name (pre-Windows 2000) with the value I've set as the default (%firstname:lower,1%%lastname:lower%) and that in turn populates some other fields that are linked to the %username% alias. If I try to change the value of the User Logon Name (pre-Windows 2000) field it changes and everything in the form updates accordingly but when I click the Create button and the account gets created those changes are thrown out and it users the value from the property pattern.
Perhaps I'm misunderstanding the Default Value of a property pattern property. I thought it would just populate a default value and if it was changed then it would accept that change but it appears that what ever is setup in the property pattern is what will be put in the AD account when it's created. So my question is this (sorry about the long winded explanation): How do I populate an "initial" value but still allow it to be changed on the web form and subsequently put into AD? The reason is that occasionally we have users that end up with the same account name using our naming method and it needs to be changed from what the default is. Hope that all makes sense.