Peter Selch Dahl

Microsoft is working on issuing future update releases for its Forefront Threat Management Gateway (TMG) and Unified Access Gateway (UAG) products, mostly to help with publishing Exchange 2013.

http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx

http://redmondmag.com/articles/2012/11/26/microsoft-planning-tmg-and-uag-updates.aspx

Bliv lidt klogere på Microsoft Forefront Endpoint Protection 2010 (System Center Endpoint Protection). Se mit indlæg fra Microsoft Campus Days 2011

http://technet.microsoft.com/da-dk/video/i09-forefront-endpoint-protection-2010.aspx

Hi everyone,

For some weird reason you're not able to configure the mobile access for some of the application within the UAG 2010 portal like FileAccess, Portal, etc...

The "checkbox" for the options under "Portal Link" looks like they are disabled. :)

Following the steps below you can manually configure these settings.

 1. Navigate to the root installation of the UAG using Windows Explorer.

 2. Find the file WizardDefaultParam.ini located at the following path \von\conf\wizarddefaut

 3. Locate the section of that application that you would like to change. For example [Portal]

 4. Find the attribute "SupportPda". Change the value from "1" to "3".

 5. Save the settings and restart the UAG console

 6. Re-Create your "Portal" Application.

Now you should see the checkbox is checked, but still greyed out :)

/Peter

Hi,

Just a HeadsUp when designing your Forefront Endpoint Protection 2010 policy collection structure.

If you build your FEP policy assignment collection structure beneath "FEP Collections" watch out if you need to reinstall/repair the FEP installation the sub collections ends up orhpaned and after a reinstallation of the FEP installation you will not be able to see the sub collection in th console any more.

You will also get an error if you try to recreate the structure because the previously created collections still exist in the SCCM database.

"The collection name is already in use. Please enter a different name."

 Follow the steps in this guide to either re-create the collection structure or remove it all together:

http://blogs.technet.com/b/mniehaus/archive/2011/04/21/got-orphaned-collections-in-configmgr.aspx

Thanks to Morten Kløve Simonsen for his input in this mather.

/Peter