Peter Selch Dahl

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,

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

Hi,

Yesterday I visited a smaller customer that had decided to do the implementation of FEP 2010 them self. Nothing wrong in that, but somewhere a long the way something had gone terrible wrong with the installation.

Error

The FEP 2010 reporting (SQL reporting services) component didn't show any data. I just stated "No Data" and "Error: Subreport could not be shown".

After doing some troubleshooting I found that I couldn't access the Microsoft SQL 2008 Analysis services using the Microsoft SQL Management studio. None of the customers services accounts had access to connect to the service.

We decided to reinstall the FEP 2010 reporting component after re-installing the Microsoft SQL 2008 Analysis service. After completing the installation everything worked.

 /Peter Dahl

When you try to install the Microsoft Forefront TMG 2010 Service Pack 1 you get an error saying:

Setup cannot modify or create the registry entry System\CurrentControlSet\Services\Tcpip\Parameters.

Solution:

If you downloaded the service pack from the Microsoft Download Center, do the following:

1. Press the SHIFT key and right-click on the .MSP file, and then select Copy as path.
   
   
2. Right-click the Command Prompt icon, and then select Run as administrator.
   
   
3. Right-click the Command Prompt window and select Paste.
   
   
4. Follow the instructions in the wizard.

Source: http://technet.microsoft.com/en-us/library/ff717843.aspx

Hi UAG folks,

During a deployment of UAG 2010 in a test lab I bumped into a small issue with getting UAG to update the GPO policies in Active Directory.

When you click "Apply Now" and execute the Poweshell it will output within the UAG console and you might get an error if you use special characters in either your username or "%TEMP%" user environment variable.

It doesn't seem that the script was build with support for error handling and  expecting special characters within the %TEMP% variable.

The error you might get..

failed. Windows cannot open the file named c:\users\\AppData\Local\Temp\......

Workaround/Fix

To get around this issue the easy way is to change the %TEMP% variable. You could decide to use a more normal username that doesn't include special characters...

Changing the %TEMP% variable.

See this Microsoft KB article for more information.

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

Powershell and Special Chars:

http://msdn.microsoft.com/en-us/library/dd878238(VS.85).aspx

Peter Dahl