{"id":2744,"date":"2024-05-24T01:51:59","date_gmt":"2024-05-23T23:51:59","guid":{"rendered":"https:\/\/itsimple.info\/?p=2744"},"modified":"2024-05-24T01:52:41","modified_gmt":"2024-05-23T23:52:41","slug":"terminal-server-or-remote-desktop-not-listening-on-port-3389-after-sysprep","status":"publish","type":"post","link":"https:\/\/itsimple.info\/?p=2744","title":{"rendered":"Terminal Server or Remote Desktop Not listening on port 3389 after sysprep"},"content":{"rendered":"\n

Remote Desktop Services is not accepting logons because setup is running.
Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager\/Operational
Source: TerminalServices-LocalSessionManager
Event ID: 34<\/p>\n\n\n\n

If Sysprep is stuck or trying to run repeatedly, it might be necessary to clean up any pending Sysprep state. This typically involves deleting certain registry keys and files associated with Sysprep to reset its state. Here’s how you can clean up the Sysprep run:<\/p>\n\n\n\n

Steps to Clean Up Sysprep State<\/h3>\n\n\n\n
    \n
  1. Stop the Sysprep Process (if running)<\/strong>:<\/li>\n<\/ol>\n\n\n\n
      \n
    • Open Task Manager (Ctrl + Shift + Esc).<\/li>\n\n\n\n
    • Look for any Sysprep-related processes and end them.<\/li>\n<\/ul>\n\n\n\n
        \n
      1. Delete Pending Sysprep Registry Key<\/strong>:<\/li>\n<\/ol>\n\n\n\n
          \n
        • Open the Registry Editor (type regedit<\/code> in the Run dialog and press Enter).<\/li>\n\n\n\n
        • Navigate to the following path:
          HKEY_LOCAL_MACHINE\\SYSTEM\\Setup\\Status\\SysprepStatus<\/code><\/li>\n\n\n\n
        • Delete the GeneralizationState<\/code> key.<\/li>\n\n\n\n
        • You can also try GeneralizationState<\/code> key value 7.<\/li>\n<\/ul>\n\n\n\n
            \n
          1. Delete Sysprep Pending File<\/strong>:<\/li>\n<\/ol>\n\n\n\n
              \n
            • Open File Explorer and navigate to the Sysprep directory:
              C:\\Windows\\System32\\Sysprep<\/code><\/li>\n\n\n\n
            • Delete the Panther<\/code> folder or any files in it that indicate a pending operation, such as setupact.log<\/code> or setuperr.log<\/code>.<\/li>\n<\/ul>\n\n\n\n
                \n
              1. Clear Setup Files<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                  \n
                • Navigate to the following path in File Explorer:
                  C:\\Windows\\System32\\Sysprep\\Panther<\/code><\/li>\n\n\n\n
                • Delete the setupact.log<\/code> and setuperr.log<\/code> files.<\/li>\n<\/ul>\n\n\n\n
                    \n
                  1. Check for Other Pending Operations<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                      \n
                    • Sometimes, other setup files can indicate pending operations. Check and delete any of the following files if they exist:\n
                        \n
                      • C:\\Windows\\Panther<\/code><\/li>\n\n\n\n
                      • C:\\Windows\\System32\\sysprep\\Panther\\setupact.log<\/code><\/li>\n\n\n\n
                      • C:\\Windows\\System32\\sysprep\\Panther\\setuperr.log<\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
                          \n
                        1. Restart the Computer<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                            \n
                          • After cleaning up the registry and deleting pending files, restart the server.<\/li>\n<\/ul>\n\n\n\n

                            Verify and Re-enable Remote Desktop<\/h3>\n\n\n\n
                              \n
                            1. Ensure Remote Desktop is Enabled<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                \n
                              • After rebooting, check if Remote Desktop is enabled:\n
                                  \n
                                • Open System Properties<\/strong> (Right-click on ‘This PC’ -> Properties -> Remote settings).<\/li>\n\n\n\n
                                • Ensure that “Allow remote connections to this computer” is selected.<\/li>\n\n\n\n
                                • Apply the settings.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
                                    \n
                                  1. Restart Remote Desktop Services<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                      \n
                                    • Open an elevated Command Prompt or PowerShell and run the following commands to ensure that Remote Desktop Services are running:
                                      powershell sc config TermService start= auto sc start TermService<\/code><\/li>\n<\/ul>\n\n\n\n
                                        \n
                                      1. Check Event Viewer<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                          \n
                                        • Open Event Viewer and navigate to Applications and Services Logs<\/strong> -> Microsoft<\/strong> -> Windows<\/strong> -> TerminalServices-LocalSessionManager<\/strong> -> Operational<\/strong>.<\/li>\n\n\n\n
                                        • Verify that there are no further errors related to Sysprep or Remote Desktop Services.<\/li>\n<\/ul>\n\n\n\n

                                          Detailed Registry Edit Steps<\/h3>\n\n\n\n
                                            \n
                                          1. Open Registry Editor<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                              \n
                                            • Press Win + R<\/code>, type regedit<\/code>, and press Enter.<\/li>\n<\/ul>\n\n\n\n
                                                \n
                                              1. Navigate to Sysprep Status Key<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                                  \n
                                                • Go to HKEY_LOCAL_MACHINE\\SYSTEM\\Setup\\Status\\SysprepStatus<\/code>.<\/li>\n<\/ul>\n\n\n\n
                                                    \n
                                                  1. Modify or Delete Values<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                                      \n
                                                    • You might see a key named GeneralizationState<\/code>. If it exists, right-click and delete it.<\/li>\n<\/ul>\n\n\n\n

                                                      File Deletion Steps<\/h3>\n\n\n\n
                                                        \n
                                                      1. Open File Explorer<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                                          \n
                                                        • Navigate to C:\\Windows\\System32\\Sysprep\\Panther<\/code>.<\/li>\n<\/ul>\n\n\n\n
                                                            \n
                                                          1. Delete Logs and Pending Files<\/strong>:<\/li>\n<\/ol>\n\n\n\n
                                                              \n
                                                            • Delete any setupact.log<\/code>, setuperr.log<\/code>, or other pending files.<\/li>\n<\/ul>\n\n\n\n

                                                              Conclusion<\/h3>\n\n\n\n

                                                              By cleaning up the Sysprep state and ensuring that Remote Desktop Services are properly configured, you should be able to resolve the issue of Remote Desktop not accepting logons. If the problem persists, further investigation into logs and potential issues with the Sysprep process or Remote Desktop configuration may be necessary.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                                              Remote Desktop Services is not accepting logons because setup is running.Log Name: Microsoft-Windows-TerminalServices-LocalSessionManager\/OperationalSource: TerminalServices-LocalSessionManagerEvent ID: 34 If Sysprep is stuck or trying to run repeatedly, it might be necessary to clean up any pending Sysprep state. This typically involves deleting certain registry keys and files associated with Sysprep to reset its state. Here’s how you […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[21,4,1,14,15],"tags":[],"class_list":["post-2744","post","type-post","status-publish","format-standard","hentry","category-operating-systems","category-tech","category-uncategorized","category-windows","category-windows-server"],"_links":{"self":[{"href":"https:\/\/itsimple.info\/index.php?rest_route=\/wp\/v2\/posts\/2744","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/itsimple.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/itsimple.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/itsimple.info\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/itsimple.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2744"}],"version-history":[{"count":0,"href":"https:\/\/itsimple.info\/index.php?rest_route=\/wp\/v2\/posts\/2744\/revisions"}],"wp:attachment":[{"href":"https:\/\/itsimple.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2744"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/itsimple.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2744"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/itsimple.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2744"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}