Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Problems with RDP logins and Windows Modules Installer service

Answered Problems with RDP logins and Windows Modules Installer service

  • Wednesday, December 12, 2012 3:37 PM
     
     
    Sign In to Vote
    0

    I have a recurring problem.  It has several symptoms that if I troubleshoot individually gets me no where.  As a group, I've found others that have posted similar problems, but I can't find any solutions. 

    The server is Windows 2008 R2 and is running Remote Desktop Services.

    1.  If there are more than 8-10 users logged in, users will start getting the message "The Group Policy Client service failed the logon. Access is denied" and cannot get logged into the server.  This is true for any domain login including at the console.  Usually I can get logged in as local admin.  If I get a few people logged off, then the others can log in just fine.  This happens for any user after the server has about 10 active sessions so it does not appear to be a user profile issue.

    2.  If I run the SFC /SCANNOW command it fails and says "Windows Resource Protection could not start the repair service."

    3.  If I manually start the Windows Modules Installer service it fails with "Error 1450: Insufficient system resources exist to complete the requested service."

    4.  If I go into Programs in control panel to look at the recent updates, it says "No updates are installed on this computer." in the window where the updates should be listed.

    If I restore it from backup it will work fine for maybe 2 weeks then this problem returns.

    Does anyone have any ideas about this?

    Thanks,  Chris

     

All Replies

  • Wednesday, December 12, 2012 6:59 PM
     
     Answered
    Sign In to Vote
    0

    you may be running out of virtual memory which on a R2 is rare but possible.

    to start with .. check the values of paged/non paged pool in the task manager when the issue occurs.

    take a perfmon capture with memory,physical disk, process,system and processor objects. set sample interval as 30 seconds and let it log for a day. it will be good if we capture the issue while this log is still running.