FEP 2010 install Troubleshooting steps
If during the process of moving your environment to FEP 2010, and you should happen to see FEP install failures with an error message of (FEP failed using Package ISV data to calculate precedence from CCM_ISV_SoftwarePolicy. It is required for applying policy. Error: Timeout after waiting 600000ms.) There are a couple of possible fixes from Microsoft suggestions –
1. Wait for CCM client to complete / report to SCCM before pushing software to the system.
2. Attempt to rerun the deployment once you have confirmed the above item.
o Test / review to see if FEP client installed correctly, if not continue
3. Start Powershell on the client by opening Command Prompt and typing Powershell
Run the following Powershell WMI query to check if the CCM_ISV_SoftwarePolicy class exists in WMI:
get-wmiobject -namespace “root/ccm/policy/machine” -class CCM_ISV_SoftwarePolicy
This resulted in the following error:
Get-WmiObject : Invalid class
At line:1 char:14
+ get-wmiobject <<<< -namespace “root/ccm/policy/machine” -class CCM_ISV_SoftwarePolicy
CategoryInfo : InvalidOperation: (:) [Get-WmiObject], ManagementException
+ FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand
Attempts to manually compile the CCM_ISV.MOF file located in the ConfigMgr Client’s cache folder C:WindowsSystem32CCMCache<Package ID> using the following command produced the error below because the mofcomp.exe could not be found:
mofcomp CCM_ISV.MOF
‘mofcomp’ is not recognized as an internal or external command, operable program or batch file.
Run the SET PATH command from the command prompt to determine if the folder, C:WindowsSystem32Wbem, exists and if not add it to the PATH.After adding this path, the application of the FEP policies was successful.
4. Attempt to rerun the deployment once you have confirmed the above item.
o Test / review to see if FEP client installed correctly, if not continue
5. Uninstall the ConfigMgr client
Register MSXML Dlls: To re-register MSXML, click Start, click Run, type the following command, and then click OK:
Regsvr32 “C:WINDOWSsystem32msxml3.dll”
Note This command assumes that you want to reregister MSXML 3.0 and that the .dll file is located in the C:WINDOWSsystem32 folder.
Requested the customer to push the Client Agent again to these systems to re-install it and then to rerun the FEP2010 advertisement.
Re-register the client’s Scripting Libraries: Use the Fix-It from https://support.microsoft.com/kb/949140 (which you did in the past) or perform the registration manualy:
To manually register the scripting components on your computer, use one of the following sets of steps, as appropriate for your situation.
You are running a 32-bit version of the Windows operating system
1. Click Start, click Run, type cmd, and then click OK.
2. Type regsvr32 %systemroot%system32vbscript.dll, and then press ENTER.
3. Type regsvr32 %systemroot%system32jscript.dll, and then press ENTER.
4. Type regsvr32 %systemroot%system32dispex.dll, and then press ENTER.
5. Type regsvr32 %systemroot%system32scrobj.dll, and then press ENTER.
6. Type regsvr32 %systemroot%system32scrrun.dll, and then press ENTER.
7. Type regsvr32 %systemroot%system32wshext.dll, and then press ENTER.
8. Type regsvr32 %systemroot%system32wshom.ocx, and then press ENTER.
You are running a 64-bit version of the Windows operating system, and you receive the error message that is mentioned in the “Symptoms” section while you are using the 64-bit scripting components
1. Click Start, click Run, type cmd, and then click OK.
2. Type %systemroot%system32regsvr32 %systemroot%system32vbscript.dll, and then press ENTER.
3. Type %systemroot%system32regsvr32 %systemroot%system32jscript.dll, and then press ENTER.
4. Type %systemroot%system32regsvr32 %systemroot%system32dispex.dll, and then press ENTER.
5. Type %systemroot%system32regsvr32 %systemroot%system32scrobj.dll, and then press ENTER.
6. Type %systemroot%system32regsvr32 %systemroot%system32scrrun.dll, and then press ENTER.
7. Type %systemroot%system32regsvr32 %systemroot%system32wshext.dll, and then press ENTER.
8. Type %systemroot%system32regsvr32 %systemroot%system32wshom.ocx, and then press ENTER.
6. Re-install the CCMgr Client software
7. Push the Client Agent again to these clients
8. Re-run the FEP2010 advertisement.
o Test / review to see if FEP client installed correctly, if not continue
Sam Westfall, PEI
