As you know, ConfigMgr 2012 is supported on a SQL named instance. However, in this scenario when you try to install a primary site that will be joined to a CAS, you can get the following errors :
In ConfigMgrSetup.log :
ConfigMgr 2012 requires SQL Server to use static port TCP/1433 and TCP/4022 for SQL Service Broker if using a CAS or secondary sites. Since SQL Server named instances default to dynamic ports, if you are using named instances, you must manually reconfigure the named instance to use static TCP/1433.
You need to configure SQL Server to listen on a specific TCP Port (1433). Look at this link
Many people ask the question (Customers, on TechNet Forums, …) and on Forefront Endpoint Protection TechNet documentation we don’t find the name of the file.
People who worked on Forefront Client Security know the file because it is the same.
Location: %allusersprofile%\Microsoft\Microsoft Antimalware\Support
Name: MPLog-XYZ.log (XYZ is the date)
Today when I tried to install the ConfigMgr 2007 client on a Windows Server 2008 SP2 x86 machine I’ve seen the following errors in ccmsetup.log. The client was not installed and the ccmsetup process was blocked.
Couldn't get directory list for directory 'http://<CMName/CCM_Client/ClientPatch'. This directory may not exist. ccmsetup 9/29/2011 3:56:42 PM 3164 (0x0C5C)
Adding file ':80/CCM_Client/i386/wimgapi.msi'">http://<CMFQDN>:80/CCM_Client/i386/wimgapi.msi' to BITS job, saving as 'C:\Windows\system32\ccmsetup\wimgapi.msi'. ccmsetup 9/29/2011 3:56:42 PM 3164 (0x0C5C)
Adding file 'http://<CMFQDN:80/CCM_Client/i386/client.msi' to BITS job, saving as 'C:\Windows\system32\ccmsetup\client.msi'. ccmsetup 9/29/2011 3:56:42 PM 3164 (0x0C5C)
Couldn't get directory list for directory 'http://<CMFQDN/CCM_Client/i386/00000409'. This directory may not exist. ccmsetup 9/29/2011 3:56:42 PM 3164 (0x0C5C)
Starting BITS download for client deployment files. ccmsetup 9/29/2011 3:56:42 PM 3164 (0x0C5C)
Download Update: A recoverable error has occurred. A retry attempt will be made. ccmsetup 9/29/2011 3:56:43 PM 3164 (0x0C5C)
It was an IP v4 network. After many troubleshooting actions, I found that the IP v6 was unchecked in the NIC of the Windows 2008 machine. When I selected it and retried the client installation everything gone WELL !!! I’ve not seen this issue with 2008 R2 nor Vista/7. Anyway, the problem was solved .
To uninstall IE9 with System Center Configuration Manager 2007, you can use the following method :
1. Download IE9 executable file then extract it.
2. You will find three files.
3. Create a CMD or BATCH script.
4. Create a new package in ConfigMgr, its program and add it to the DP.
5. Create an advertisement and make sure that the option “Download content from distribution point and run locally” is selected.
6. Now IE9 can be uninstalled and you will need to reboot the computer to complete the uninstall because we have used /norestart in the script. Also you can force a reboot if this will not create problems with users .
7. You can monitor IE9 uninstall process using the classic methods as ConfigMgr reports, ConfigMgr log files AND also you will find the log file created by the script.
8. If you don’t want to use the software distribution method, you can use a task sequence.
Hope it helps.
Great news !!! System Center Configuration Manager 2007 SP2, R2 and R3 now supports SQL Server 2008 R2 SP1 and SQL Server 2008 SP3. For more details, see Configuration Manager Support Announcements for August 2011
The next generation of Data Protection Manager (DPM) is now downloadable here
Note that Microsoft does not recommend to deploy this Beta into Production. This Beta is not supported by Customer Services and Support (CSS).
When you change SQL services to use the Local System account then you start to install FEP Reporting role, you can see the following error :
The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. (rsReportServerDisabled) Get Online Help Bad Data. (Exception from HRESULT: 0x80090005)
To solve this problem, you have to delete the Encryption Key from SQL Reporting Services Configuration Manager then restart the FEP Reporting installation again.
Dart 7 beta allows Administrators to connect to a WinPE system during an operating system deployment, very interesting !! The following article explains how to add Dart 7 beta to MDT 2010 to monitor your deployments Software Assurance Pays Off – Remote Connection to WinPE during MDT deployments
SQL Server 2008 R2 Service Pack 1 is released, see the Download Link.
Therefore the question is : Is SQL Server 2008 R2 SP1 supported by System Center Configuration Manager 2007 ?
The answer : Not yet, we need to wait 45 days because the ConfigMgr Product Team needs to complete their compatibility tests and after that they will announce support.
Dear Bechir Gharbi,
Congratulations! We are pleased to present you with the 2011 Microsoft® MVP Award! This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in System Center Configuration Manager technical communities during the past year.
The Rollup 1 for FEP 2010 is available. For more details you can refer to these links:
I will try later to create a step by step with screenshots about how to install the rollup.
The SUP/WSUS synch fails with the following error :
SMS WSUS Synchronization failed.
Message: The log for database 'tempdb' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
If tempdb is not available, so don’t worry because it gets recreated after every SQL services restart, therefore the solution is restarting the Windows Internal Database service of WSUS (or SQL service if the WSUS database is stored on SQL server) or reboot the Software Update Point (SUP) server.
Description: You start to install Forefront Endpoint Protection server and you see the following errors :
[Verbose] Process ended. Exit code: 536870913
[Normal] Installation(Install Microsoft Forefront Endpoint Protection 2010 Security Client ) failed.
[Normal]> Error: Setup failed to install Microsoft Forefront Endpoint Protection 2010 Security Client. Failed executable: FepInstall.exe. Exit code: 536870913. Message returned by OS.
Cause: The code 536870913 indicates a corrupted file.
Solution: Re-download again the FEP media.
When you try to access any to FEP 2010 baselines from the Configuration Manager console, you receive this error message HTTP error 404.3 - Not Found -- The page you are requesting cannot be served because of the extension configuration. If the page is a script, add a handler. If the file should be downloaded, add a MIME map.
So, the solution is very simple , look here.
FEP is the next version of Forefront Client Security, the enterprise antivirus solution of Microsoft. FEP 2010 was the first version that builds on Configuration Manager 2007 SP2 R2 or R3 but not Configuration Manager 2012 and because of that, Microsoft provides us FEP 2012. To download the product, go here.
More Posts Next page »