Jump to content

GoalTrain

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral
  1. We have a few clients that are unable to register with the Management Console. I've read other forums and confirmed the clock is in sync. We've tried installing remote and locally on the system with the same result. From mee.log: 2014-07-28 11:31:10.483 INFO ComputerInstall.Execute: IP Address [x.x.x.x] execution result: Passed The installation procedure has ended before the client registered 1.75.0.1300 From "Remote Install Service Log" section of mee.log: 2014-07-28 11:30:30.360: The client version is: 1.75.0.1300 2014-07-28 11:30:30.650: Client Register Thread Entry. 2014-07-28 11:30:30.652: ****ERROR*****: Internet is disconnected, sccomm cannot register client. The client is on the network and able to reach the Internet. The Management Console is able to push to the client over the network. The client system's firewall is disabled. This is only happening to a select few systems within our deployment. Any help would be appreciated. We have been troubleshooting this problem for some time now.
  2. For those getting the following error when running the SFC command in Windows 7: "Windows Resource Protection could not start the repair service". Check to see if the wcp.dll exists in C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f\. Many of our systems were missing wcp.dll and were resolved by copying wpc.dll from a working Windows 7 computer or Windows 7 install disk. Make sure the system drive is offline when performing the copy. This can be accomplished by copying the file in system recovery mode. After restoring wcp.dll, running the SFC command ran successfully and resolved many of the missing DLL errors. Restoring the ATL90.DLL and COMCTL32.DLL worked only worked when copying from a working system/install DVD while the system disk was offline in Windows recovery mode. Hope this helps.
  3. HOBOcs, I tried building a Windows system with the OS on the D drive. I connected the hard drive from one of the "black screen" systems and mounted the drive as the C drive. I then copied the Quarantine directory from C drive to the D drive, opened MBAM and restored all the files to the C drive. However, this still did not work even after restoring all the files it could. Many didn't restore since there were system files in place. Did you try running the SFC command from Windows recovery console? This resolved about half of our black screen systems. Steps: 1. Run "bcdedit | find "osdevice" to figure out the drive. 2. Run "sfc /scannow /offbootdir=c:\ /offwindir=c:\windows" 3. Reboot and boot into safe mode 4. Run latest MBAM fix
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.