Deploying fix for KB3025417 and SCEP reporting

I am trying to deploy a script that fixes the issue between KB3025417 and the SCEP reporting (Issue).  The command that I am running is the one found in the linked blog post, inserted into a batch file.

Register-CimProvider.exe -ProviderName ProtectionManagement -Namespace root\microsoft\ProtectionManagement -Path "C:\Program Files\Microsoft Security Client\ProtectionMgmt.dll" -Impersonation True -HostingModel LocalServiceHost -SupportWQL -ForceUpdate

I have manually(As Administrator) ran the batch file on several computers, to test.  On half the computers I get the following response:

On the other half, it just runs, some have been running for at least 30 minutes, with no response.  Is anyone else getting similar responses when running the command?

June 26th, 2015 12:04pm

Hi,

It said, Successfully registered the provider.

If this resovled the issue, just ignore it.

Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 1:59am

how are you running the batch file ? To ignore the warning messages for end user,you can run the batch file in silent mode and add exit button end of the code to exit the script after the register command run.
June 29th, 2015 3:17am

A bit off topic, I know. But before you start testing your batch script with ConfigMgr, do note that packages are being run with a 32bit launcher. That won't work with the commandline provided by the ConfigMgr team.

Took me a while to realise. You either have to use the application model, or trick the 64bit file system redirection to use cmd.exe from %SystemRoot%\Sysnative\ instead.

Hope that helps someone.

Free Windows Admin Tool Kit Click here and download it now
June 29th, 2015 7:07am

A bit off topic, I know. But before you start testing your batch script with ConfigMgr, do note that packages are being run with a 32bit launcher. That won't work with the commandline provided by the ConfigMgr team.

Took me a while to realise. You either have to use the application model, or trick the 64bit file system redirection to use cmd.exe from %SystemRoot%\Sysnative\ instead.

Hope that helps so

June 30th, 2015 1:49pm

A bit off topic, I know. But before you start testing your batch script with ConfigMgr, do note that packages are being run with a 32bit launcher. That won't work with the commandline provided by the ConfigMgr team.

Took me a while to realise. You either have to use the application model, or trick the 64bit file system redirection to use cmd.exe from %SystemRoot%\Sysnative\ instead.

Hope that helps so

Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 2:02pm

So I created a batch file to force 64 command prompt, but the Sysnative command does not work, cmd prompt does not resolve it. (I've never used SysNative)
%SystemRoot%\SysNative\cmd.exe /c "%~dp0ReportingFix.bat"
I had to end up using:
%SystemRoot%\System32\cmd.exe /c "%~dp0ReportingFix.bat"
Which shouldn't be an issue since all the Windows 8.1 clients are 64 bit os's.
June 30th, 2015 3:19pm

So I created a batch file to force 64 command prompt, but the Sysnative command does not work, cmd prompt does not resolve it. (I've never used SysNative)
%SystemRoot%\SysNative\cmd.exe /c "%~dp0ReportingFix.bat"
I had to end up using:
%SystemRoot%\System32\cmd.exe /c "%~dp0ReportingFix.bat"
Which shouldn't be an issue since all the Windows 8.1 clients are 64 bit os's.
  • Edited by Evers_mark Tuesday, June 30, 2015 7:18 PM
Free Windows Admin Tool Kit Click here and download it now
June 30th, 2015 7:17pm

For 32bit CMD, use %systemroot%\SysWow64 then check in Task Manager under Process for *32 to indicate the process is 32-bit.

July 3rd, 2015 2:09am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics