none
Local and Remote Logon Unavailable on 2003 Servers after EP 2012 Upgrade

    Question

  • We have several 2003 servers in our infrastructure which ALL failed to upgrade from FEP 2010 to EP 2012.  All of our 2008 and 2008 R2 servers upgraded without issue.  The 2003 servers are a mix of physical and virtual (VMware) systems. 

    All failures messages show in SCCM as:  Failed to trigger EP Installer to install with error code = 0x80004005

    Now we cannot Remote Desktop to any of these servers and console access for both physical and virtual systems shows a grey screen with a mouse but no dialogue box.  If we power cycle the server the dialogue box is intially displayed but will only allow one logon and then exhibit the same behavior of blank screen with mouse.  Ctrl-Alt-Del does nothing at this screen.

    I saw the Microsoft hotfix 981889 (KB976759), which addresses RDP disconnect issues but it does not mention 2003 Server as a target OS.  Is there a similar hotfix for the Server 2003/Windows XP platforms?

    Thursday, May 03, 2012 4:58 PM

Answers

  • Hi,

    We had the same problem in our Enviroment.  We had FEP 2010 Earlier and we upgraded to SCEP 2012 and got this issue.

    We were unable to remote into the W2K3 servers alone. The server would stop responding some time after a reboot. The screen would go black as soon as we try to take MSTSC rdp. But we can remote into the W2K8 boxes fine.

    The answer could be a little varying.  Anyhow, let me try to make it a little step wise.

    1. We went and installed Windows installer 4.5 on all windows server 2003 machines.

    2. We removed the CCM client using CCMsetup.exe /uninstall command.

    3. We rebooted the machine.

    4. Removed Installer entries related to FEP in the registry. (upgrade codes if any too)

    5. Installed CCM setup again. This time we got it install like cheese and works fine.

    6. In some machines, we had to remove the local group policy files from C:\windows\system32\grouppolicy - (its a hidden file) -  then ran gpupdate /force, a few minutes later we got the scep to work automatically.

    I would actually like to give you the exact registry key you want to look for in the registry. but quickly not in mind. will post it soon.

    Thanks,

    Krishna.

    Tuesday, July 24, 2012 3:07 AM

All replies

  • Personally I've not seen that problem on 2003 OS machines. Maybe be other folks here have seen that but I guess calling MS support remains the best way for your situation.

    Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

    Sunday, May 06, 2012 3:45 PM
  • Hi Paul,

    Just out of curiousity, did you ever get this problem resolved? I'm dealing with the exact same problem on some of my Win2K3 servers at the moment.

    EP 2012 installed fine on some, but fails on most and then I'm unable to logon to the server desktop, just as you had.

    Hope to hear from you soon!

    Regards,
    Arjan.

    Wednesday, July 18, 2012 7:15 AM
  • Any error message in %systemdrive%\WINDOWS\CCM\Logs\EndpointProtectionAgent.log?

    Wednesday, July 18, 2012 8:03 AM
  • Hi,

    The following entries are written in the log (error messages are present):

    <![LOG[Endpoint is triggered by message.]LOG]!><time="07:43:49.792-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="fepsettingendpoint.cpp:55">
    <![LOG[File C:\WINDOWS\ccmsetup\SCEPInstall.exe version is 2.2.903.0.]LOG]!><time="07:43:49.792-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentutil.cpp:499">
    <![LOG[Unable to query registry key (SOFTWARE\Microsoft\Microsoft Security Client), return (0x80070002) means EP client is NOT installed.]LOG]!><time="07:43:49.792-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentutil.cpp:149">
    <![LOG[AM Policy XML is ready.]LOG]!><time="07:43:49.813-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentutil.cpp:314">
    <![LOG[Handle EP Deployment Policy.]LOG]!><time="07:43:49.813-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:780">
    <![LOG[Disable Startup Signature Update equals to false.]LOG]!><time="07:43:49.813-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:352">
    <![LOG[Add the Disable Startup Signature Update settings to policy xml successfully.]LOG]!><time="07:43:49.855-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:356">
    <![LOG[Create Process Command line: "C:\WINDOWS\ccmsetup\SCEPInstall.exe" /s /q /policy "C:\WINDOWS\CCM\EPAMPolicy.xml".]LOG]!><time="07:43:49.855-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentutil.cpp:602">
    <![LOG[Waiting for signal time-out]LOG]!><time="09:47:28.513-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="3" thread="4536" file="epagentutil.cpp:437">
    <![LOG[Start to send state message.]LOG]!><time="09:47:28.513-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:159">
    <![LOG[Send State Message with topic type = 2001, state id = 4, and error code = 0x80004005]LOG]!><time="09:47:28.513-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:166">
    <![LOG[State 4 is NOT changed. Skip update registry value]LOG]!><time="09:47:28.513-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:183">
    <![LOG[Failed to trigger EP Installer to install with error code = 0x80004005.]LOG]!><time="09:47:28.513-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="3" thread="4536" file="epagentimpl.cpp:399">
    <![LOG[Register a timer here to check whether definition get updated in 30 minutes.]LOG]!><time="09:47:28.513-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentimpl.cpp:1006">
    <![LOG[FW Provider is NOT installed yet.]LOG]!><time="09:47:28.545-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="4536" file="epagentutil.cpp:778">
    <![LOG[File C:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi installation failed because another program is installing (1618)]LOG]!><time="09:47:31.542-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="2" thread="4536" file="epagentutil.cpp:836">
    <![LOG[Failed to install FW MSI with error = 0x80070652.]LOG]!><time="09:47:31.542-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="3" thread="4536" file="epagentimpl.cpp:763">
    <![LOG[Endpoint is triggered by Timer.]LOG]!><time="10:17:28.011-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="1" thread="5740" file="fepsettingendpoint.cpp:263">
    <![LOG[Failed to retrieve definition version from WMI.]LOG]!><time="10:17:28.105-120" date="07-18-2012" component="EndpointProtectionAgent" context="" type="3" thread="5740" file="epagentimpl.cpp:1024">

    Wednesday, July 18, 2012 8:35 AM
  • File C:\WINDOWS\ccmsetup\WindowsFirewallConfigurationProvider.msi installation failed because another program is installing (1618)]"

    Isn't that message unambiguous?

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, July 18, 2012 8:39 AM
  • The SCEP installation never finishes, it just seems to hang, although the Event Viewer shows a Installation completed successfully message.

    Maybe this is why the WindowsFirewallConfigurationProvider is trying to start? SCEP is believed to have installed correctly, when in fact it hasn't, so the further necessary configuration settings continue?

    Regs,
    Arjan.

    Wednesday, July 18, 2012 8:42 AM
  • Hi,

    We had the same problem in our Enviroment.  We had FEP 2010 Earlier and we upgraded to SCEP 2012 and got this issue.

    We were unable to remote into the W2K3 servers alone. The server would stop responding some time after a reboot. The screen would go black as soon as we try to take MSTSC rdp. But we can remote into the W2K8 boxes fine.

    The answer could be a little varying.  Anyhow, let me try to make it a little step wise.

    1. We went and installed Windows installer 4.5 on all windows server 2003 machines.

    2. We removed the CCM client using CCMsetup.exe /uninstall command.

    3. We rebooted the machine.

    4. Removed Installer entries related to FEP in the registry. (upgrade codes if any too)

    5. Installed CCM setup again. This time we got it install like cheese and works fine.

    6. In some machines, we had to remove the local group policy files from C:\windows\system32\grouppolicy - (its a hidden file) -  then ran gpupdate /force, a few minutes later we got the scep to work automatically.

    I would actually like to give you the exact registry key you want to look for in the registry. but quickly not in mind. will post it soon.

    Thanks,

    Krishna.

    Tuesday, July 24, 2012 3:07 AM
  • Hi,

    Thanks for your reply.
    I've been working with Microsoft the last week to get this resolved and in the end it came down to doing about the same you said in your post.

    I didn't think about the Uninstaller regkeys myself, so that definitely helped when they told me about them.

    Anyway, my servers are almost all up and running with SCEP normally now!

    Regards, Arjan.

    Wednesday, July 25, 2012 6:27 AM
  • Thank you for the information Krishna!  I admit I had kind of given up on this post after a month or so.  I did try the installer 4.5 and it worked on one system without making any other changes.  I will try the step outlined on the last stubborn two server to see if I can get them to behave.  And thank you to Garth Jones for marking this as the answer!
    Friday, January 04, 2013 1:06 AM