Announcement

Collapse
No announcement yet.

Log off screen freeze in Remote sessions

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Log off screen freeze in Remote sessions

    Hi all,

    I have the problem when logging off the remote sessions. The log off screen freeze and couldn't log off.

    Have you met it and found the solution ?

    Thanks for any help.
    Love in vain is better than love no one.

  • #2
    Re: Log off screen freeze in Remote sessions

    There lots of issues like:

    1. Bad drivers.
    2. Hardware not in the HCL.
    3. Hung application services.
    4. You use old OS/RDP Client or/and not update the current system.

    Please add more information on the server, client and the network.

    Regards,

    Yuval
    Best Regards,

    Yuval Sinay

    LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

    Comment


    • #3
      Re: Log off screen freeze in Remote sessions

      Hi,

      It's a IBM Server with 2 x 3.0GB, Windows 2003 Standard SP1. I think the problem is related to your third reason. I could see there're a lof of errors :

      Windows cannot access the file gpt.ini for GPO CN={6AC1786C-016F-11D2-945F-00C04fB984F9},CN=Policies,CN=System,DC=os,DC=com. The file must be present at the location <\\os.com\sysvol\os.com\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini>. (The system cannot find the file specified. ). Group Policy processing aborted.

      However, I could log off normally from console session.
      Love in vain is better than love no one.

      Comment


      • #4
        Re: Log off screen freeze in Remote sessions

        Please run IBM Update Express 4.02 and upgrade the system drivers + BIOS + Firmware...
        Is the server function as DC?

        http://support.microsoft.com/?id=842804

        http://www.microsoft.com/downloads/d...displaylang=en
        Best Regards,

        Yuval Sinay

        LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

        Comment


        • #5
          Re: Log off screen freeze in Remote sessions

          Originally posted by nguyennp
          Hi,

          It's a IBM Server with 2 x 3.0GB, Windows 2003 Standard SP1. I think the problem is related to your third reason. I could see there're a lof of errors :

          Windows cannot access the file gpt.ini for GPO CN={6AC1786C-016F-11D2-945F-00C04fB984F9},CN=Policies,CN=System,DC=os,DC=com. The file must be present at the location <\\os.com\sysvol\os.com\Policies\{6AC1786C-016F-11D2-945F-00C04fB984F9}\gpt.ini>. (The system cannot find the file specified. ). Group Policy processing aborted.

          However, I could log off normally from console session.
          I had this same problem the other week with a server we had.

          I followed all the documentation from MS and even tried to restore the folders from nother server but was un-successful.

          In the end i had to rebuild the server from scratch.

          My reckoning was that something had happened with the first replication from AD had gone wonky, we are replicating across a WAN link.

          I rebuilt it and all was OK.

          This is the document that i followed.

          http://support.microsoft.com/kb/q290647/

          Comment


          • #6
            Re: Log off screen freeze in Remote sessions

            It's not a DC.
            I forgot this. Our only DC using Windows 2000 Server. The previous admin do something with it so now, all the workstation get that error in the Event Log. Actually, I don't know if that error make the log off screen frezze or not.
            I support there's a Policy couldn't be apply. I intend to remove this Policy but don't know which it is depend on the description of the error.
            Love in vain is better than love no one.

            Comment


            • #7
              Re: Log off screen freeze in Remote sessions

              1. Please backup the servers system state + export the current GPO's by using
              GPMC tool:

              http://www.petri.com/download_gpmc.htm

              2. Vertiy DNS/Network settings on each DC by using DCDIAG, NETDIAG.

              3. Upgrade each DC to be GC and reboot the DCS.

              4. Backup the servers system state + export (again) the current GPO's by using
              GPMC.

              5. Unlink each GPO.

              6. Run:

              http://www.microsoft.com/downloads/d...displaylang=en

              7. Backup the servers system state + export the current GPO's by using
              GPMC.

              8. Reboot the servers and check for error messages.
              Best Regards,

              Yuval Sinay

              LinkedIn: https://www.linkedin.com/in/yuval14, Blog: http://blogs.microsoft.co.il/blogs/yuval14

              Comment

              Working...
              X