Blog Comments

  1. TheScarfedOne's Avatar
    • |
    • permalink
    hmmm, definately not needed to do that on mine.
  2. edugeekdan's Avatar
    • |
    • permalink
    The soltuion was to add the Domain prefix to the 'username' box of the rdp session file. Thanks
  3. edugeekdan's Avatar
    • |
    • permalink
    Already tried that one and preseumed it didnt work because its a RDP logon box? also checked all the Remote Desktop Services GPO's and cant find any that are useful.
  4. TheScarfedOne's Avatar
    • |
    • permalink
    @edugeekdan... this one is set in group policy on the server. Create and link a GP for the OU/Machine. The setting is in Computer Configuration > Policies > Windows Settings > Security Options > Interactive Logon: Do not display last username
  5. edugeekdan's Avatar
    • |
    • permalink
    Great Script and this was a major help to me! Thank you.

    Is there anyway to get the last logged in user to the RDP session to be forgotten so it defaults to "use another account" Thanks Dan
  6. TheScarfedOne's Avatar
    • |
    • permalink
    @ICTHUS - the settings are in the zip file attached to the blog post. Its done in the registry.
  7. ICTHUS's Avatar
    • |
    • permalink
    Hso did you change the shell from explorer.exe to mstsc.exe?
  8. TheScarfedOne's Avatar
    • |
    • permalink
    Thin PC is part of Software Assurance under School/Campus and EES Agreements. It was released on 1st July 2011, and should now be showiing up in your Volume Licence Centre. If not, give it a few days, and PM - will get it checked...

    If you happen top be in the Southwest region, I can show you our setup
  9. simpsonj's Avatar
    • |
    • permalink
    Sounds very interesting, especially as I've just started experimenting with Remote Desktops...

    Where did you get WTPC from? Has it been released as part of the MSA/EES agreements? Any licensing issues to be aware of?
  10. SwedishChef's Avatar
    • |
    • permalink
    Best tool i found was, Password Policy - Stronger Windows Passwords | Specops Password Policy there is a free basic version available.

    I also found a "feature" regarding the message box that gets displayed if you try to change to a password that breaks the policy, it seems to allow the default domain setting to take precedence, we had to turn on complex for our whole domain in order to get the correct box displayed, on groups with and without complex enabled.
  11. timbo343's Avatar
    • |
    • permalink
    I have seen it been done on training videos, it seems straight forward to me, just have to remember to goes on groups of users (security groups) rather than OUs.
  12. cookie_monster's Avatar
    • |
    • permalink
    We're using WDS legacy mode on 2003 SP2 in a 2008 domain.
  13. swordfish215's Avatar
    • |
    • permalink
    So RIS will still work if you Upgrade to Server 2008????
    Updated 13th April 2010 at 09:24 AM by swordfish215
  14. EduTech's Avatar
    • |
    • permalink
    Ah so that explains why you were not answering my phones calls and text messages ;-) you can have a break you know matey! i have some news for you lol!! yes it is to do with SharePoint hehe! its all good fun mate!
  15. TheScarfedOne's Avatar
    • |
    • permalink
    @cookie_monster... think you are right, but even with the specify the username/password route - the same thing happens.

    Real pain, and took a while to find out what caused it.
  16. cookie_monster's Avatar
    • |
    • permalink
    Hahaha i've just spent ages trying to fix this and found the same KB to sort it, I thought i'd post my findings here but had a quick search and bang someone has already come accross the issue.

    It's odd as we don't have any clients or servers running less than XP SP2/2003 SP2 can anyone tell me why we need to allow a policy that puts back the encryption to NT4 levels.

    I think it must be something to do with the "DoOldStyleDomainJoin = yes" setting.
  17. ZeroHour's Avatar
    • |
    • permalink
    Thanks for this, very useful to know.
  18. verygreenpc's Avatar
    • |
    • permalink
    Hey Stuart,
    Thanks for pointing me here mate. Feedback has been pro OCS rather than a branded ISP like MSN Messenger or an open source version so far.
    Cheers,
    Col
  19. TheScarfedOne's Avatar
    • |
    • permalink
    UPDATED:
    1. WSS3 and MOSS2007 SP2's both installed and nothing is broken.... yet!! :-)

    2. Server 2008 SP2 installed on most boxes, but now need to resize the OS partition as this wasnt done properly first time grrrr :-(

    3. 1 ICT Suite rebuilding today, the other later in the week.

    4. A skip has taken away most of the junk :-)

    5. Started playing with our Samsung MagicInfo-i system again. New software to tryout....
  20. TheScarfedOne's Avatar
    • |
    • permalink
    Ah - if you had a previous version of the solution on your environment - you would end up with an assembly version mis-match to what is registered as safe in your web.config. Remember - that your web.config reflects the internal unique identifier in the assembly dll. This does change between versions.

    With a copy of the webpart already on a page - you would therefore get this error as the webpart on the page (old version) would not match the assembly.

    Glad you are all sorted - sorry I didnt see the problem sooner to save you some head scratching.
Page 5 of 7 FirstFirst 1234567 LastLast