Author name: Benoit HAMET

The following is applying to TMG too. If you have an internal certificate authority and a GPO which enables automatic certificate enrollment, you may have the following event logged on the Application event log: Event ID: 6 Source: CertificateServiceClient-Autoenrollment Description: Automatic certificate enrollment for local system failed (0x800706ba). The RPC server is unavailable. To solve […]

Today, I discovered that when you rename an AD group used for application authorization in UAG, the new name is not applied to UAG and you are not able to access to the published application anymore. Step to reproduce Create a user group on your AD; for this example, I named it UAG Demo –

After providing contact information on UAG logon page (see previous post), you may also want to provide contact information on application portal. Once again, default settings doesn’t provide contact details and you have to update some files.     To update the Contact us link provided at the bottom left of the page, update the mailto

ForeFront Unified Access Gateway is the Microsoft solution to provide remote and secure access to application (web or legacy) through a portal. However, the default settings doesn’t provide contact information (administrator’s contact) on logon page or portal page. To provide this information on logon page, you have to update the language definition files. By default,

As you may already know, Windows Server 2008 is providing new remote desktop functionality, called Remote Access Gateway, which allow RDP access to internal network without VPN. However, this doesn’t provide detailed security management, especially if you publish RPD gateway through ISA or TMG. To simplify this, you should publish Remote Desktop Access through UAG.