RSAT Released for Windows 7

RSAT Released for Windows 7

  • Comments 14
  • Likes

Remoter Server Administrations Tools are RTM, come and get 'em.

Some things to keep in mind:

  1. This version is only for Windows 7 (Business, Professional, and Ultimate).
  2. Make sure to uninstall any RC/Beta/whatever copies of RSAT for Win7 you had previously installed.
  3. Make sure to remove any hacked up Vista RSAT copies you might have installed.
  4. Make sure to remove any hacked up Win2003 ADMINPAK copies you might have installed.

Have fun.

- Ned 'Snap in to a Snap-In' Pyle

  • One thing that still bugs me to no end - the Remote Desktops mmc snapin does not allow you to store the configuration (presumably because it's in %systemroot%\system32) unless you copy tsmmc.msc to a writable location somewhere else (userprofile).

  • That sounds a little irritating - can you give me your exact repro steps so I can take a look at this?

    - Ned

  • Do I correctly understand that these RSAT is not supported for Windows 7 Enterprise,or is it just not mentioned?

  • Ned, Repro:

    Administrative tools > Terminal Services > Remote Desktops > rightclick and choose Author.

    Add a Server (connection), and close the console.

    Settings & connections are not saved.

    I've tried changing the shortcut properties ( the /s switch into /a, or just nothing).

    Author mode or Run as Administrator does not make a difference.

    You really have to save the mmc snapin in a different location (save as) to get any connections to stick (or to store the specific settings for your snapin such as last selected server or even window size/position).

  • @ Shadowman: it is definitely supported with Enterprise. From the download page System Requirements:

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

    @Alt-92: Blerg :(. I'll run a quick repro there and get back to you on this.

    - ned

  • Hi Alt-92,

    I am not able to precisely reproduce this. When I close the console, I am prompted to store my msc file (by default, it wanted the system32 folder, but that isn't going to work so I saved to my desktop). This happens regardless of Author mode or not.

    Are you saying it lets you save your snap-in and doesn't prompt you to save the tsmmc msc file at all?

    - Ned

  • Ned,

    What you're describing is the default behaviour with UAC standard settings, correct.

    Other snapins automatically save their settings on close and generate a cached view in %userprofile%\appdata\roaming\microsoft\mmc without prompting - dfs management console, dns, dhcp, task scheduler etc.

    Incidentally, tsmmc shows the same inconsistent behaviour (compared to other snapins) on Vista and 2008 Server.

  • Ah - that's a key point; happens on Vista/2008 too. Makes us getting a fix rather... unlikely. :|

    I am not using UAC in this scenario, as I am logged on as *the* Administrator. Were you seeing the behavior change if you had UAC completely turned off?

    - Ned

  • UAC off and using a domain account with local administrators groupmembership.

    In that case, using the red X just closes the mmc - no prompts, nae nuthin'. You can tell it doesn't save anything because the window position of the mmc console and the snapin stay exactly the same.

    I've made a recording using PSR on Win7 and a similar recording on Vista, I can probably rustle up one on 2008 as well if you like to have those.

  • Nice. Ok, I'm convinced - I'll file a design change request tomorrow. Absolutely no promises about when or if this ever gets fixed, but at least it will be on record.

    Thanks for the great feedback Alt-92, very appreciated.

    - Ned

  • How do I get back the missing tabs?

    RSAT for Vista finally got back 4 of the 5 missing tabs for ADUC, but RSAT for Windows 7 RTM is still missing them. I assume they should match the names you see in Server 2008 R2:

      •Remote Desktop Services Profile



      •Remote Control


    Since we now have some RODCs on our domain, it would also be nice to have the Password Replication tab.


  • Hi,

    You will see the password replication tab if you were to enable Advanced Features in DSA.MSC. That works already.

    And you will see the various Remote Desktop tabs if you make sure to enable the RSAT feature: "Remote Desktop Services Tools".

    But the missing dialup tab is expected and silly. If any readers here have a Premier contract I *highly recommend* that you open a support case through your TAM and request this be changed through a DCR - I have been trying for nearly a year but have not had enough customers formally request this to back me up.

    I have a KB article on this that for some reason appears to be marked confidential, so only people with Premier contracts can go read it. It's KB 975448. There's no reason it should be confidential though - and I've requested that be fixed just now - so here is the info:


    After you install Remote Server Administration Tools for Windows 7 on a computer that is running Windows 7, the Dial-in tab is missing in the properties of a user account in the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in.


    This issue occurs because the RSAT manifest and the installation package do not include the Rasuser.dll and Rtrfiltr.dll modules that are required to load the Dial-In tab.


    To work around this issue, use one of the following workarounds, as appropriate.

    Workaround 1

    On the computer that is running Windows 7, use Remote Desktop Services to connect to a server that is running Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003. Then, start the Active Directory Users and Computers MMC snap-in on the server.

    Workaround 2 (Windows Server 2008)

    1.  On a server that is running Windows Server 2008, install the Terminal Services role, and then install the Terminal Server role service to enable the use of RemoteApp Manager.  

    2.  Add Active Directory Users and Computers (DSA.MSC) as a remote application.  

    3.  On the computer that is running Windows 7, access the RemoteApp DSA.MSC.  

    Workaround 2 (Windows Server 2008 R2)

    1.  On the server that is running Windows Server 2008 R2, install the Remote Desktop Services role, and then install the Remote Desktop Session Host role service to enable use of RemoteApp Manager.  

    2.  Add Active Directory Users and Computers (DSA.MSC) as a remote application.  

    3.  On the computer that is running Windows 7, access the RemoteApp DSA.MSC.  

    - Ned

  • Thanks -- those tips worked.

    I had alread figured out workarounds #1 and #2 from my old Vista install. But I was having to do them so often that I stopped using RSAT and just used servers to do all my AD work -- not the most efficient way for me to get my work done.

    I don't know if we have a Premier contract any more but will try to pass on the dial-in tab issue through our Enterprise Agreement contacts.

    In the meantime, do you know if can I use the Attribute Editor to manage the "Network Access Permission" values that would show up on the Dial-in Tab? Is there a reference somewhere that defines all the fields that are listed in the Attribute Editor as well as the value options? I know they are the same as what you get in ADSIEdit but I have not found a reference for that either. I figured out some of the other values on the Dial-in tab (callback number, static IP address, static routes) but have not figured out the Network Access Permissions.

    Thanks for your help.

  • Not documented as far as I have found - we expect you to use the tool, not directly edit.