http://www.windowsnetworking.com/kbase/WindowsTips/WindowsXP/AdminTips/Security/RemoveSavedPasswords.html

1. Click Start and select Run

2. In the Open field type “rundll32.exe keymgr.dll, KRShowKeyMgr”

Looks like the user information is stored in a table called STAF

The scenario is this… We have several similar systems (same target type) with different approvers. So, a user could fill out a request for access to system1, system2, and system3. BUT, in 7.80, there is no granularity in the request. If the approver for system3 logs in, and approves the request, then the user by default would be granted access to system1 and system2.

Making a separate workflow for each system involves too much overhead and maintenance.  The best option would be to only allow the user to request one system at a time, and handle figuring out who the approver is as a separate issue. The question is how to restrict the user to a single choice.

The answer is to make a copy of the *.xslt file, and replace “checkbox” with “radio” so that the user is presented with a Radio Button interface. I am using – not the default *.xslt, but instead the BuildIdentityMapCtrl.xslt.

Here are lines 246 thru 250 – yours may differ….

<xsl:template name=”BuildSortTableRows”>
<!– output the addline –>
<xsl:text disable-output-escaping=”yes”>tSORTTABLE_</xsl:text>
<xsl:value-of select=”../../../../name”/>
<xsl:text disable-output-escaping=”yes”>.AddLine(“&lt;center&gt;&lt;INPUT TYPE=‘radio’ NAME=’</xsl:text>

The confgiuration managers are 32-bit applications.

The 32-bit ODBC Data Soruce Administrator must be used to configure DSNs for 32-bit applications to use.

To run the 32-bit version of the ODBC Administrator, in the Windows Run dialog box, type: %windir%\syswow64\odbcad32.exe

System data sources created in the 64-bit ODBC administrator are only visible to 64-bit applications. System data sources created in the 32-bit ODBC administrator are only visible to 32-bit applications. 32-bit driver data sources are stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ODBC\ODBC.INI (which is only visible to 32-bit applications) rather than the standard location, HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI.

32-bit ODBC drivers are available to 32-bit applications running in the WOW64 layer, but not to 64-bit applications.

On 64-bit Windows platforms, there is both a 32-bit and a 64-bit version of ODBC Administrator. The 64-bit ODBC Administrator is located in the standard location: Administrative tools in Control Panel. The 64-bit version of the ODBC Administrator only lists 64-bit ODBC drivers and data sources.

Make sure you have the 32 bit version of the ODBC driver.

Additionally, if you are using 7.80 or higher, the 64 bit system hosting IIS and the CF (Connector Framework) must be switched into 32 bit compatibility mode along with having the 32 bit version of the .NET framework. (The CF is where the PMM or Connector that needs ODBC is actually being executed.) This same requirement applies to the CFM (Connector Framework Manager) in order to configure the targets in the Connector Configuration Manager.

See KB from Microsoft …

http://support.microsoft.com/kb/894435

==========

By the way, I switched what I was doing to use the ADO connector instead.

The documentation on page 297: Configuring_PMMs_Connectors_and_Agents.pdf
AdminUser — The name of the Microsoft SQL Server administrative user that can log on to the SQL server. This user must be a SQL login user, a member of the SQL Server SECURITYADMIN fixed server role, and the DB_ACCESSADMIN database role.

• I am told it does support named instances.. such as Server\Instance, but since I am not yet able to establish a connection, I cannot verify this.   *When you get the connector to work, it works as show.
• Basically, your server has to be mixed mode, and the privileged account must be a SQL (not windows, not domain) account
• There is a configuration parameter that is not mentioned in the documentation…IgnoreAccessGroup. I don’t have a clear understanding of what this is, and I don’t know if it’s ok to leave this unassigned. (*When you get the connector to work, it will tell you valid settings are yes or no)
• I am using the same configuration information that I used to set up the PMM, which is working, so I know that I have the correct user name and password, BUT I cannot get the AMM to configure correctly. I keep getting an “unable to verify connection”.  *You need the patch below.

The Connector and PMM for Microsoft SQL Server depend upon the SQL-DSO activeX object, which is no longer distributed with the SQL Server client that is packaged with SQL Server 2008 and 2008 R2. To address this missing dependency, download and install Microsoft SQL Server 2005 Backward Compatibility Components on the Courion Server, or on the CF/CFM machine running the Connector/PMM accessing SQL Server 2008. This assumes you have installed the SQL Client Software, as directed in the prerequisites for the Connector/PMM for SQL Server:

The SQL Server client must be installed on each server in which the Connector
Framework or Connector Framework Manager is installed. Note that the SQL
Server Management Studio Express client cannot be used—you must install the
regular SQL Server client.

Microsoft SQL Server 2005 Backward Compatibility Components are packaged with the Microsoft SQL Server 2008 Feature Pack, available at the following Microsoft Downloads location:

Microsoft SQL Server 2008 Feature Pack, August 2008

http://www.microsoft.com/download/en/details.aspx?id=16177

http://www.bimonkey.com/2009/09/ssis-derived-column-forcing-data-type-changes/
He’s right. If you open the advanced editor, it’s right there.

Just a list of tools that are handy to use with Courion….

• http://www.modelsphere.org/open_modelsphere.html Data modelling
• http://notepad-plus-plus.org/ Text editor
• http://www.ldapbrowser.com/ LDAP Browser (works with Active Directory as well)
• http://www.vbsedit.com/ visual basic editor, but also has great examples
• http://Liberkey.com portable application suite
• http://stepshot.net/ documentation generation
• http://www.quest.com/toad/ SQL Server tool. There are free and paid versions, but the paid one is MUCH better (and expensive)
• http://www.latticesoft.com/ XML and XSLT editing.

The WordPress.com stats helper monkeys prepared a 2011 annual report for this blog.

Here’s an excerpt:

A New York City subway train holds 1,200 people. This blog was viewed about 4,200 times in 2011. If it were a NYC subway train, it would take about 4 trips to carry that many people.

Click here to see the complete report.

http://opensource.com/life/11/11/introduction-kdenlive

I found the default identitymap *.xslt (ACCreateFormCtrls.xslt) to be a bit complex…with something like 30 (maybe more) imports. Which one of the 30 to edit? making sure you don’t break something else, etc.
However, there’s a simpler way.
There is an *.xslt called BuildIdentityMapCtrl.xslt, which is very monolithic.
I simply made a copy of this file, and pointed the identitymap screen to this copy, and deleted out the information we didn’t want. Now I have an *.xslt file that is less than 400 lines long, and doesn’t import any other files… Simpler to debug, modify, and, yes, comprehend.