Blog - Title

May, 2009

  • RSAT Release Candidate for Windows 7... ehh... Release Candidate

    Ned here again. The Remote Server Administration Tools (RSAT) have been released for Win7 RC. Grab them from:

    http://www.microsoft.com/downloads/details.aspx?FamilyID=f6c62797-791c-48e3-b754-c7c0a09f32f3&displaylang=en

    Here are the installation requirements:

    Supported Operating Systems: Windows 7
    Remote Server Administration Tools for Windows 7 RC can be installed on computers that are running the Professional, Enterprise, or Ultimate editions of Windows 7 RC.

    Remote Server Administration Tools for Windows 7 RC runs on both x86- and x64-based editions of Windows 7 RC, and can be used to manage roles and features that are running on either the Server Core or full installation options of the x64-based Windows Server 2008 R2 operating system. Remote management is also supported for some roles and features that run on Windows Server 2008 or Windows Server 2003.

    Remote Server Administration Tools for Windows 7 RC should not be installed on a computer that is running the Windows Server 2003 Administration Tools Pack or Windows 2000 Server® Administration Tools Pack. Remove all versions of Administration Tools Pack or Remote Server Administration Tools for Windows Vista SP1 from the computer before you install Remote Server Administration Tools for Windows 7 RC.

    Only one copy at a time of Remote Server Administration Tools for Windows 7 RC can be installed on a computer. Before you install a new package, remove any existing copies of Remote Server Administration Tools for Windows 7 RC. This includes any copies that are in different languages.

    And as if you didn't already know, Client and Server OS RC's are out and available to all...

    http://www.microsoft.com/windowsserver2008/en/us/R2-Download.aspx

    http://www.microsoft.com/windows/windows-7/download.aspx

    As always, feel free to post issues or questions in our Comments section below.

    - Ned Pyle

  • New Directory Services KB Articles 4/26-5/2

    New KB articles related to Directory Services for the week of 4/26-5/2.

    970770

    Differences in NTDS Writer PostSnapshot behavior on Server 2003 vs Server 2008

    958058

    When you try to log on to a Windows XP SP3-based computer by using a roaming profile, the roaming profile cannot load.

    960898

    Name resolution is broken between a Windows Server 2003-based parent domain and its child domains, and among the child domains, when scavenging is configured on both the parent and child DNS zones

    970875

    Large Kerberos tokens cause WinRM requests to fail

    970879

    Blank Desktop on Windows Vista or Windows Server 2008

  • Printing and Active Directory

    Some concepts and troubleshooting methods regarding printing and Active Directory from our friends over at AskPerf.

    http://blogs.technet.com/askperf/archive/2009/05/05/printing-and-active-directory.aspx

  • Event ID 22 on a Windows 2008 Terminal Services Licensing Server

    Hi all, Akhlesh here. Recently I’ve seen a few cases where the customers were getting event ID 22 on their Windows 2008 Terminal Services Licensing server (TSLS):

    Log Name: System
    Source: Microsoft-Windows-TerminalServices-Licensing
    Date:
    Event ID: 22
    Task Category: None
    Level: Warning
    Keywords: Classic
    User: N/A
    Computer:
    Description:
    The Terminal Services license server "TS licensing server name" does not have any
    Terminal Services client access licenses (TS CALs) installed and registered with
    the Microsoft Clearinghouse for product "Windows Server 2003 - Terminal Server Per
    Device CAL Token". Therefore, the Terminal Services license server cannot issue TS
    CALs of the type "Windows Server 2003 - Terminal Server Per Device CAL Token" to
    the terminal server "IP of a TS". To resolve this problem, install additional TS
    CALs as required.

    Before I talk about the cause and resolution of this event, please follow the steps given below and make sure that the given conditions are true in your scenario*:

    • Your Windows 2008 TSLS is activated. How to Activate a Terminal Services License Server?
    • Terminal Services Licensing service is running on that TSLS.
    • Your Windows 2008 TSLS is a member of "Terminal Services License Servers" group in the Active Directory.
    • Your Windows 2008 TSLS is listed in the site in AD sites and services (if it is a DC).
    • The Terminal Server listed in the event is able to access your Windows 2008 TSLS i.e. TSLS discovery process is working fine and we are able to open TSLS snap-in from the Terminal Server. If you are using a GPO to publish the TSLS, make sure that the GPO is getting applied on that Terminal Server.
    • Please check and make sure that the users are able to connect to the Terminal Server listed in the event.
    • Please check and make sure that we have enough CALs available on the Windows 2008 TSLS and those CALs are getting issued to the clients

    *If all the points given above are true in your case, you can ignore this event.

    Now, let’s discuss why this warning event is still getting logged on that TSLS even when all the points discussed above are true in your scenario:

    It looks like your TSLS is working the way it should. You are getting the event because of client machines which took TS CALs from a Windows 2003 TS Licensing Server which has been decommissioned in your domain. At the renewal time of the CALs for those clients, the TS forwarded the requests to the new w2k8 TSLS. The new TSLS didn’t find the references of those clients in its database so it couldn’t renew the CALs, therefore a warning event was resulted.

    But after that it must have issued CALs to those clients (assuming that we have enough CALs available). This event is showing the IP of the TS because TS will interact with TSLS on client's behalf for the issuance of the TS CAL.

    The event will stop occurring once TS CALs on all the clients will be renewed. To prove this theory, you can take a client machine for which the CALs is about to expire in the next few days. Then connect to a w2k3 TS, see if you get an event on w2k8 TSLS. Then check the list of issued CALs and see if that client is listed on the new TSLS or not.

    - Akhlesh Sharma

  • SYSVOL migration from FRS to DFSR - Whitepaper Released

    Ned here. It's done, it's out, come get it, stop yelling at me! :-)

    SYSVOL Replication Migration Guide: FRS to DFS Replication (TechNet Version)
    SYSVOL Replication Migration Guide: FRS to DFS Replication (Word Doc Version)

    Be sure to also run through some of these (possibly) useful accompanying pieces:

    Verifying File Replication during the Windows Server 2008 DFSR SYSVOL Migration – Down and Dirty Style
    DFSR SYSVOL Migration FAQ: Useful trivia that may save your follicles
    KB968733 (hotfix for migration under certain RODC scenarios)
    KB967326 (hotfix for migration under disjoint name space scenarios)

    - Ned 'Yes, my middle name is DFSR' Pyle

  • Overview of New MPSReports Data Collection Tool

    Here is a nice overview of the new MPSReports and what it collects. Proactively running this before contacting support has been known to greatly reduce time to resolution. :-)

    http://blogs.technet.com/askperf/archive/2009/05/01/two-minute-drill-the-new-mps-reports.aspx

  • 8-bit Awesomeness

    Ned here. If you're having a lazy friday and don't feel like working too hard (don't lie!), take a trip over to:

    http://www.microsoft.com/click/serverquest/

    Come on, you know you want to...

    - Ned Pyle