8 Responses to New Articles, Tools, Tips and Tricks: Windows (7 and 2008 R2), PowerShell and Citrix

  1. Kimmo February 11, 2010 at 02:39 #

    Thanks for the links collection.

    • Matt K February 11, 2010 at 17:18 #

      You say not to use UPHClean 2.0 Beta in production… but what about us folk using Win2k3 x64? We have NO choice!

      • Helge Klein February 11, 2010 at 18:26 #

        Good point. UPHClean 1.6d does not work on Windows x64. But then, the beta of UPHClean 2.0 tends to be unstable and cause blue screens from time to time… There is no easy solution to this dilemma, except maybe migrate to 2008 (R2) which has UPHClean’s registry functionality built in. But that is not easy, either…

        • Matt K February 11, 2010 at 21:28 #

          The latest release of the now discontinued UPHClean 2.0 for x64 resolved all BSODs I experienced in testing and I have rolled into production. So I am comfortable with it (although it still has issues working 100% of the time- i.e. some profiles STILL do not unload even with it installed).

          You mileage may vary of course :)

          Still not loving the fact that Microsoft left Windows Server 2003 x64 in the cold with UPHClean for x64!

          • Helge Klein February 11, 2010 at 22:12 #

            I agree, it is unfortunate that 2003 x64 is not covered.
            Another unfortunate thing is that the ability to release open file handles will probabably never be implemented. UPHClean 1.x as well as Server 2008 (R2) only take care of open registry handles.

  2. Drewfus March 1, 2010 at 14:41 #

    regarding UPHClean and your comment “My tip: the beta of 2.0 should NOT be used in production..”

    The author of the tool seems to be fairly happy with the reliability of the most recent beta, and it would seem to be a good way of avoiding slow logoffs and %username%.000x profile paths.

    Can you elaborate on your position on not using UPHClean in XP?

  3. Drewfus March 1, 2010 at 15:17 #

    i somehow missed your comments above. It must be from staying up too late to read your blog. :-)

Leave a Reply