SBS 2008 — connecting drives

On SBS 2003 if you wanted to enable files and folders to be transferred between the remote computer and your computer you had to check a box.  And if you were running Vista you had to run IE as administrator for the drive mappings to work.

In the 2k8 era you have to use the RDP client to have the same functionality through TSgateway.  At first I had a hard time getting my head around using the rdp client.  I kept thinking to myself “But I don’t want 3389 opened up”.  Finally it dawned on me.  TSgateway uses 80/443.  It’s not going over anything but SSL traffic the entire way.

Once you log into the Remote Web Workplace on the SBS 2008 box, you then need to ensure that your RDP client/TSGateway has the necessary information. 

Strike that, I did it to myself again.  I don’t need to log into RWW.  The TSGateway is all I need to do this.

On the TS Gateway screen put in the name of the RWW access URL.

Then on the “connect to computer”, use the Computername.domain.local in the front box

When you click connect, you will get the warning you are attaching drives, click details to confirm that the drives are being connected

And you will now see the drives connected remotely

Yeah I’m in a HyperV where I have a SBS2008 and a XP sp3 machine going from the XP sp3 to the SBS box 🙂

3 Thoughts on “SBS 2008 — connecting drives

  1. Cool, now there is another way to bypass RWW Guard 2008.
    The first way is to browse directly to OWA.

  2. I see you are using the discontinued Wake On Lan addin for RWW.
    I was too, is there a suitable replacement for SBS 2008?

    It was great – staff don’t connect often but could remotely boot their PCs. The staff that need it all have vPro machines so there are more possibilities but for now just leaving the PCs on.

  3. Hey Luke,

    I am not sure where you got your information, but you are mis-informed as to the intent of what RWWGuard is. Going directly to OWA or using TS Gateway is not bypassing RWWGuard. You are simply going directly to the application in question.

    RWWGuard is designed to offer strong authentication to the actual Remote Web Workplace (RWW) login. Nothing more. Nothing less. You will not be able to log into RWW when RWWGuard is installed unless you match an appropriate authentication policy.

    If you want to protect OWA and TS Gateway entry points, then you need to install and configure the appropriate agents that come with your strong authentication server.

    If you use our AuthAnvil product in conjunction with RWWGuard, to protect OWA you should be using the AuthAnvil Web Logon Agent, or redirecting direct OWA access to /remote. And if you want to prevent users from using TS Gateway directly for interactive logon, then you should be using the AuthAnvil Windows Logon Agent for Windows XP and Windows Server 2003 systems, or the AuthAnvil Credential Provider for Vista and Windows Server 2008 systems. All this comes free with your subscription to AuthAnvil.

    If you are a client of ours, please feel free to read through all the documentation we have in the Customer Portal, as it will clearly help you to understand how to install and configure these agents. If you are using a competing strong authentication server, then I urge you to check in with them to see how they recommend you protect these entry points into your network.

    TS Gateway is an awesome enhancement to Windows Server 2008, which we see being leveraged in RWW. But its not a bypass for RWW. It’s a different entry point all together. Actually, RWW uses TS Gateway extensively to offer the remote desktop connections in SBS 2008 instead of using the proxied RDP it used to use in SBS 2003.

    If you are (or even if you aren’t) a client of ours and want some clarity on this, please feel free to contact me. You can reach me at dana(a)

Post Navigation