Author: Halfvares Mats, Teknikhuset AB.

Published: 2005-02-22

Applies to:
  • Content Studio ver. 3.5+

Type: Information

More information

When Content Studio writes the files to disk or sets security on a document system object it replaces all entries containing the BROWSE permission for the alias ANONYMOUS LOGON with the trustee account used to impersonate anonymous users. This account is by default a local account named according to the IUSR_MACHINENAME pattern where MACHINENAME is the netbios name of the local server. During the file writing process Content Studio discovers this account dynamically. One obvious method would be to ask the IIS metabase for this information but normally the Content Studio runtime account has not administrative privileges and cannot access the metabase. Therefore Content Studio must have another method to obtain this information and will use the following methods:
  1. Content Studio tries to obtain a valid account name from the registry in the IIS_AnonymousAccountName string value in the HKEY_LOCAL_MACHINE\SOFTWARE\teknikhuset\Content Studio\3.2 key.
  2. If the registry value is empty or missing or invalid Content Studio looks in the site setting system.Anonymous_Account.
  3. If this value is invalid or empty Content Studio asks the IIS metabase and will likely fail. In this situation Content Studio cannot continue with operation and returns an error message.

Important step 1 in the list above was introduced in version 4.0 build 1009 and is not created by the installation program. Also note that if Content Studio finds a valid account in step 1 or 2 it will not verify that this account really is the account used by the IIS - Content Studio simply trusts the information supplied by the system administrator.