RD Gateway and RemoteApp Error: Remote Desktop can't connect to the remote computer "RDS.Domain.Local" for one of these reasons:

We just finished setting up a Windows Server 2012 R2 Standard RDS server and began testing the RD Gateway, RDWeb, and RemoteApp features and hit this:

RemoteApp Disconnected

Remote Desktop can't connect to the remote computer "RDS.Domain.Local" for one of these reasons:

1) Your user account is not authorized to access the RD Gateway "remote.domain.ca"

2) Your computer is not authorized to access the RD Gateway "remote.domain.ca"

3) You are using an incompatible authentication method (for example, the RD Gateway might be expecting a smart card but you provided a password)

Contact your network administrator for assistance.

The third reason is out while the first two are not applicable since our access policies are set up correctly.

Our search brought us to:

• Network Blog: Remote Desktop Gateway client fails authentication with “Your user account is not authorized to access the RD Gateway”

Following Solution 1 we puzzled about trying to figure out where the NPS thing was!

Click on NAP in Server Manager and then right click on the server name. Choose Network Policy Server in the menu.

Once the NPS console comes up right click on the root node NPS (Local) and click Register server in Active Directory.

Click OK twice and then test again.

Good to go!

Philip Elder
Microsoft MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
Third Tier: Enterprise Solutions for Small Business

SSL Certificates: CSR Decoder to Verify Settings

When it comes to creating a certificate request sometimes we can miss a character or typo something.

If the processing takes longer than expected and the certificate provider does not provide much more than a "Processing" status it may be a good idea to verify the settings in the CSR file.

The CSR Decoder site can do that:

• CSR Decoder – Check CSR to verify its contents

We hit a snag with a CSR that was taking too long and sure enough there was a typo in the common name that caused it to hang up.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

RDP Client in Windows 8 and Server 2012 Neat Features

While working from a Windows 8 Enterprise system here in the shop we connected remotely to a Windows Server 2012 Hyper-V environment that we are in the process of setting up for a new client.

A couple of neat new features in the MSTSC (Click Start (WINKey+R) –> Run –> mstsc [Enter]), that is the Microsoft Remote Desktop Connection Client (MicroSoft Terminal Services Client) are the following:

There is a little drop down menu available on the far left of the RDP status bar at the top of the session that gives us access to Windows 8/Server 2012 specific features.

The other thing we noticed was the “wireless” status bars to the right of the Pin.

Click on that and we see the following:

The drop down menu will certainly be handy for windowed RDP sessions since that is how we run most of our remote management sessions.

The connection status bars not so much. It is pretty obvious when we are having connection issues.

Have a great day and thanks for reading! :)

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Remote Desktop Services Error: One or more RD Licensing certificates has expired. Please re-register.

We have an Remote Desktop Services server that did the following when users tried to log in:

Since this particular system was headless we tried the /admin switch on an MSTSC command line start and fortunately we got into the server. A regular RDP file launch or MSTSC GUI client connection would fail with the above.

From the server’s Event Logs:

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          12/21/2012 6:16:51 PM
Event ID:      46
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      RDSServer.DOMAIN.LOCAL
Description:
One or more RD Licensing certificates has expired. Please re-register.

And:

Log Name:      System
Source:        Microsoft-Windows-TerminalServices-Licensing
Date:          12/21/2012 5:50:42 PM
Event ID:      4105
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      RDSServer.DOMAIN.LOCAL
Description:
The Remote Desktop license server cannot update the license attributes for user "FirstLast" in the Active Directory Domain "DOMAIN.LOCAL". Ensure that the computer account for the license server is a member of Terminal Server License Servers group in Active Directory domain "DOMAIN.LOCAL".
If the license server is installed on a domain controller, the Network Service account also needs to be a member of the Terminal Server License Servers group.
If the license server is installed on a domain controller, after you have added the appropriate accounts to the Terminal Server License Servers group, you must restart the Remote Desktop Licensing service to track or report the usage of RDS Per User CALs.
Win32 error code: 0x80070005

According to our search results we need to do the following:

1. Log onto the RD Licensing Server.
2. Start the RD Licensing Manager (LicMgr.exe).
3. Right click on the ServerName and Advanced –> ReActivate Server.
4. Make the following choices:
• 
5. Click Next
• 
6. We then had a successfully re-activated server.
• 

RemoteApps and RDS Desktop sessions were then available!

• QuickBooks via RemoteApp.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

RDP: Set up a Monitor Span for Non-Windows 7 Enterprise/Ultimate End Points

In order to get true multi-monitor client connections going both ends need to be Windows 7 Enterprise and/or Ultimate. Or, when connecting to Remote Desktop Services the client needs to be one of those client OSs.

To get around that for all other client OSs we can do the following:

1. Set up an SSL VPN connection (or PPTP).
• Disable the Use Remote Gateway setting for IPv4 and IPv6.
2. Start –> type: MSTSC [Enter]
• Machine.Domain.Local
• Full Screen
• Redirect needed resources.
• Do not change Gateway settings from default.
3. Save As onto the desktop.
4. Right click RDP file and Open With…
• C:\Windows\notepad.exe
5. Add the following line to the RDP file:
• span monitors:i:1
6. Save the RDP file.
7. Open the VPN connection.
8. Double click on the RDP Desktop file.
9. Log on to the desktop machine.

Users will need to get used to all dialogue boxes saddling the two monitors since that is where the “middle” of the spanned setup is.

The local monitor pair must be side-by-side and the same resolution.

We tested running the RDP file with a Remote Desktop Gateway setting and it seemed to only connect one monitor.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

SBS 2011: Configure SBS Connect Wizard for Windows 8

Our post on tweaking the SBS 2008 Connect Wizard is here:

• MPECS Inc. Blog: SBS 2008: Configure SBS Connect Wizard for Windows 8

The Official SBS Blog Post:

• Official SBS Blog: Using Windows 7 BETA With SBS 2008

There are a few differences in the settings for SBS 2011. Make sure to make a backup of the GP.XML file and the supportedOS.XML files before modifying them in any way.

After installing  the Windows 8 desktop OS:

1. On SBS 2011 Open SBS Native Tools Console.
2. Open the Group Policy Management Console.
1. If it is not there add it and save the MMC so that it is there later.
3. Navigate to the Windows SBS Client Policy GPO and copy the GUID (Unique ID).
4. Paste the GUID into the following path:
1. \Windows\sysvol\domain\Policies\{YOUR-GUID-HERE}\machine\SBS
5. Click Start –> NotePad –> Right click and Run As Admin.
6. File –> Open –> Paste the above path in and open GP.XML.
• Make sure File Type is set to All Files (*.*).
7. Append the following to (Version>= . . . ) found in the GP.XML
• and ‘6.2.8102’
• 
• 
8. Save and close NotePad.
9. Click Start –> NotePad –> Right click and Run As Admin.
1. File –> Open –> Paste the following path and open supportedOS.XML.
• C:\Program Files\Windows Small Business Server\Bin\WebApp\ClientDeployment\packageFiles\
• Make sure File Type is set to All Files (*.*).
10. Replace the supportedOS.XML file contents with the following:
• <SupportedConfigurations>
    <SupportedOS>
      <!-- Name is not used by the code but might be helpful in identifying the OS that is described by these parameters -->
      <!-- ExcludedSuite, RequiredSuite, and RequiredProductType are the numbers as specified in the OSVERSIONINFOEX structure -->
      <!-- Architecture is the number as specified in the SYSTEM_INFO structure –>
•     <OS id="1" Name="Windows XP SP2, x86" Major="5" Minor="1" Build="2600" SPMajor="2" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
      <OS id="2" Name="Windows XP SP2, AMD64" Major="5" Minor="2" Build="3790" SPMajor="2" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
      <OS id="3" Name="Windows Vista, x86" Major="6" Minor="0" Build="6000" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
      <OS id="4" Name="Windows Vista, AMD64" Major="6" Minor="0" Build="6000" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
      <OS id="5" Name="Windows 7, AMD64" Major="6" Minor="1" Build="7000" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
      <OS id="6" Name="Windows 7, x86" Major="6" Minor="1" Build="7000" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
      <OS id="7" Name="Windows 8, AMD64" Major="6" Minor="2" Build="8102" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="9"/>
      <OS id="8" Name="Windows 8, x86" Major="6" Minor="2" Build="8102" SPMajor="" SPMinor="" ExcludedSuite="512" RequiredSuite="" RequiredProductType="1" Architecture="0"/>
    </SupportedOS>
  </SupportedConfigurations>
• 
11. On the Windows 8 system: Open IE and open the http://connect wizard.
12. At the _bottom_ of the IE window click the Turn on Intranet settings button.
• 
13. Click the Yes button to the “Are you sure . . . ?” prompt.
14. Click the Start Connect Computer Program link.
• 
15. Step through the Connect Wizard.

The Windows 8 machine/VM will step through and complete its configuration.

• MPECS Inc Blog Downloads: SBS and Windows 8.ZIP (ZIP File Download)

Please use the supportedOS.XML file and the paths TXT file found in the above ZIP archive. The GP.XML file found in the archive is from an SBS 2008 setup so please ignore it for SBS 2011.

RDP and Windows 8

NOTE: We are experiencing a problem connecting to the VM via RDP on Windows SBS 2011 networks even with the firewall exceptions in place. At this point we are not sure if there is a problem using the RDP client in Windows 7/Windows Server 2008 R2 or if there is a bug in the Windows 8 OS RDP setup.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

VDI: What version of Windows 7 Desktop OS to Install?

When it comes to setting up a client’s Virtual Desktop Infrastructure (VDI), we have already configured their Software Assurance plus MDOP to gain access to VDI.

So, do we install Windows 7 Professional or Windows 7 Enterprise into those VMs?

In many cases there will be no need for Enterprise to be installed for regular VM access.

However, there will be some cases where Enterprise does make sense. One is for a firm or company that uses multiple monitors on their remote and local desktop.

Windows 7 Enterprise and Ultimate give us access to the ability to RDP into the VM and utilize multiple monitors at the source.

Note that both endpoints in the RDP connection must be either Enterprise or Ultimate. No other Windows desktop OS versions support this RDP capability.

Now, depending on the Internet connection the client uses we would tailor a GPO with RDP related settings to limit bit depth to 15bpp and the number of monitors to 2 for smaller connections while we would up the number of monitors for larger connections.

Also note that users connecting to their office desktop via the SBS 2011 Remote Web Access portal that have two monitors hooked up to their home machine will get both monitors in the remote session if using Ultimate at home and Enterprise/Ultimate on their office desktop.

We find that clients that utilize multiple monitors see their user’s productivity increase exponentially.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Video – An Introduction To The SBS 2011 Remote Web Access Portal

The following video gives an overview of the various features to be found in the new SBS 2011 Remote Web Access portal (formerly Remote Web Workplace in SBS 2003 and 2008).

SBS 2011 RWA has the following features:

• Outlook Web App (OWA) for full Outlook like access to our e-mail, contacts, calendars, and more.
• Access to the Companyweb SharePoint site.
• Access to shared folders hosted _on_ the SBS server.
• This new feature allows us to upload and download data as well as work with folders within the share.
• Connection to any desktop, laptop, or other Windows machine that we have been given permission to access.
• Of course that machine needs to be on for access!

The new version of RWA also allows us to customize the portal by adding Web links to various Internet based resources. We can also move the feature access boxes around to suit our tastes.

Please feel free to comment and critique any of the videos we put out.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Remote Desktop Connection Manager – Multiple RDP Sessions Managed Easily

This is a pretty kewl utility:

We can set up all of the servers and desktops that we manage on a regular basis in the Connection Manager and have quick and easy access to them.

• Microsoft Download: Remote Desktop Connection Manager

The RDCM can store credentials as well so we will only allow that to happen on workstations or laptops that are BitLocker enabled.

Hat Tip: Jason Miller

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

SBS v7 – Multi-Monitor Goodness via RDS Gateway (TS Gateway)

One of the neat little advantages of the new RDP protocol version that comes built into Windows Server 2008 R2 and thus SBS v7 is the ability to serve remote desktops out to clients that have multiple monitors and have that remote desktop session _on_ those multiple monitors.

The above screenshot is of the remote desktop session from home that has a 22” wide LCD on the right and an older Acer 19” 4x3 standard aspect ratio LCD on the left.

The 22” is sitting on top of a Mini-ITX system, so it is actually quite a bit higher than the Acer thus the shift between the two screens.

The Remote Desktop Connection Setting

To get the multiple monitor setup to work, we need to enable the following setting in the Remote Desktop Connection client:

Use all my monitors for the remote session

One thing to keep in mind is that with the additional monitors comes the need for additional bandwidth. As a result, for offices with smaller upload speeds, one will need to keep in mind which users should be able to connect with multiple monitors and which ones should not.

Web Site Animation Caveat

It should also be noted that when connected to a remote desktop session and there is a need to browse the Web, that sites that have some sort of animation on them will cause the session to grind virtually to a stop. So, after clicking the next link on the site, be patient as it may take a few rounds of animation for that click to be registered remotely.

Hopefully the next page does not have any animation on it!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Router/Firewall Ports To Forward For Windows Home Server

There are two ports that need to be forwarded at the router/firewall to the Windows Home Server box:

• 443 HTTPS TCP (SSL Web)
• 4125 RDP Proxy Port (RDP connections to the desktops)

Note that the 4125 proxy port is inherited from WHS’s bigger cousin Small Business Server 2003.

Port 80 is optional in that it redirects to 443 anyway. So, we suggest leaving that port closed and remembering the “s” in the WHS URL.

Once the remote access firewall ports are properly configured we see the following on an HP based WHS:

And the following on an Acer based WHS:

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

SBS 2008 – SharePoint Services Service Pack 2 Choke

We have mentioned in the past to hold off on installing that service pack:

• SBS 2008 – Hang On Before Installing WSS SP2

We happened to have one of our SBS 2008 hosting servers come free today, so we took a chance on installing SharePoint v3 Service Pack two and sure enough things went sideways.

The default fix from the SBS Blog does not work for us either:

• Companyweb Inaccessible After SharePoint 3.0 Service Pack 2

Another aspect to this situation: The Service Pack kills the TS Gateway service and thus kills any possibility of gaining remote access to the box via RWW or RDP.

If VPN is not configured on the box, which is the case in many of our client locations, then we would be in a real pickle.

Updating Rule #1: Always have an out-of-band management access on servers being updated.

Some of them are:

• Intel’s Remote Management Module.
• HP’s iLO.
• Dell’s DRAC.
• StarTech’s IP based KVMs and PDUs for no built-in solution.

Otherwise we are asking someone to go to the console to log on and either get the services back up and running, reboot the server, or help with the troubleshooting process. All are not very viable options.

So, now we are in the process of troubleshooting the hosed SharePoint install. Fortunately we have out-of-band access.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Windows 7 – Remote Desktop Multi-Monitor Goodness

The TS Gateway service allows us direct access to our desktops.

The new RDP version allows us to /mulitmon to use the two monitors we have connected to this workstation on the remote desktop:

Here is a list of the new RDP version’s command line switches:

Just remember that the TS Gateway service does allow for direct connections to any TS enabled system inside the SBS network. As a result, it would be a good idea to look at AuthAnvil by Scorpion Software to provide another level of authentication protection.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

A DRAC, Or Any Other Remote Management Tool Will Only Get Us So Far …

Now, what happens if we have set up the server via baseboard level access to the server using the Dell DRAC add-in, or any other baseboard level management module for that manner, and the remote management module has died before we have run the SBS 2008 Getting Started Tasks?

This:

 

We are assisting with the SBS 2008 and Server Core with Hyper-V Role installs on behalf of an I.T. company at a remote client site of theirs.

So, the second option is to temporarily enable port forwarding for Terminal Services 3389 to the new SBS 2008 server so we can keep moving forward.

But, what happens if there was no one around to do that?

To pre-empt this kind of situation we would do one of the following:

• Ship a preconfigured router/firewall device with the USB flash drive that had the Answer File on it.
• Coach our contact through the port forwarding process on their firewall device.

It just goes to show us that there can be no fool-proof method of connecting to a server remotely without some sort of fall-back measure in place.

Once we had the server configured for Remote Web Workplace access the 3389 port forward would be deleted in the firewall device.

In this case, once we have tried a firmware flash to the DRAC, if things still do not work, then we will initiate a support incident with Dell and have someone come out and replace the defective unit.

The DRAC no longer shows up anywhere … it is toast. Warranty replacement time.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

Windows 7 Release Candidate RDP Supports Multi-Monitors!

Need we say more:

Use all my monitors for the remote session

What a huge leap ahead.

Most users that we work with have discovered the significant increase in productivity that two or more monitors can provide for them in their offices. Now they can have that same productivity from home.

The multi-monitor feature will make Windows 7 a very valuable upgrade option for those that connect to their in-house/office systems via the Remote Web Workplace and always have at least two monitors connected to the remote workstation.

It will be a great feature for those that manage networks via remote connections too.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

SBS 2008 – Who is Connected by RDP? TS Gateway Manager Knows

When it is time to install patches or software that may bring about the need for a server reboot, we need to know who is working on what on the server.

For files, the default place to check is in the Sessions node in the Computer Management console. Any open files, where they are located, and who has them open are there.

For remote connections, the VPN is managed by RRAS, so any connections can be found in the Routing and Remote Access node under the same Computer Management console.

For RDP though, we now have the ability to actually see who is connected to any server or desktop resources within the SBS network using the TS Gateway Manager:

TS Gateway Manager

We can see how long they have been connected, to what server or desktop they are connected to, and whether the connection has been idle.

The console can be opened by clicking on the Start button and typing the console name in the Search field. Otherwise it is under the Terminal Services folder nested in the Administrative Tools folder in the All Programs list.

Once we know who to get in touch with to let them know that there is a need to reboot, we can be assured that no one will lose any data.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac! (previous blog post)

Windows Live Writer

SBS 2008 – RWW and IE VBScript RDC Errors

We have a client that was having some issues connecting to their desktop via the Remote Web Workplace. Apparently the Connect button was missing (previous blog post).

Once we had realized that Firefox was being used instead of IE, we still ran into a struggle trying to get their remote desktop connection established.

First off, they were getting this error:

VBScript: Remote Desktop Connection

The Microsoft Terminal Services Client ActiveX control (also known as the Microsoft RDP Client Control) is either not available, or is not enabled. Fore more information about installing and enabling this ActiveX control, see the Microsoft TechNet Web site (http://go.microsoft.com/fwlink/?LinkId=103719).

Now, the above screenshot is showing Internet Explorer 6 since that was the browser that was also installed on their machine when we started the troubleshooting process.

So, we had them run Microsoft Updates until every last update was installed. It took them a while.

Once finished, we had XP indicating Internet Explorer running version 7 with all of the updates applied.

We went back to RWW to try the connection again, but we still ended up with the same puzzling error.

A check in the IE Add-ons manager showed the following:

Microsoft RDP Client Control (redist) msrdp.ocx

Now, take note that the above screenshot was taken on an XP SP2 vanilla install with IE 6. We did not see an Update ActiveX button on the client’s machine. BTW, click on that button in this case, and no update is available!

In fact, when we downloaded the RDC 6.1 Client (KB 952155) from Microsoft’s site, it would not allow us to install it as we received a, “You already have the latest service pack installed so this update does not apply” error.

Indeed, Windows XP Service Pack 3 was installed on this particular machine and the new RDC comes with SP3.

Okay, so we try: Microsoft KB 951607: You cannot connect to a remote computer or start a remote application when you use Terminal Services Web Access or Remote Web Workspace on a Windows XP SP3-based or Windows Small Business Server 2003 SP1-based computer. Nothing applicable here either. Plus, we were trying to connect to the SBS 2008 RWW too.

The key to fixing the problem was found here: Browse Remote Web Workplace from Windows XP SP3 machine on the Technology on the Move blog.

We needed to run the following at the command line after making sure that all browser windows were closed:

Regsvr32 Mstscax.dll [Enter]

After a bit of a pause, a message popped up indicating that the DLL was correctly registered.

Check in the IE Add-ons manager and sure enough the file name has changed:

Microsoft Terminal Services Client Control (redist) mstscax.dll

Once we reconnected to their SBS 2008 RWW, we were able to successfully connect to their desktop.

We used CoPilot for our non-SBS based Remote Assistance needs. This particular client is in the U.S. on the West Coast, so we fired up a one-time session with CoPilot and worked through our troubleshooting process to the above successful conclusion.

One of the main reasons we have stuck with CoPilot is this blog post that has been around for a while on the company’s blog: Customer service as a competitive advantage. They get it.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts will not be written on a Mac until we replace our now missing iMac!

Windows Live Writer

RDP via RWW - Full Screen with Two Different Sized Monitors

One of the more annoying puzzles that needed to be figured out was how to get an RDP session via the Remote Web Workplace to work full screen with monitors connected to the same system that are a different size.

Why was it annoying? Because, with the advent of RWW on SBS 2008 where there is no ability to control the connected desktop's resolution anymore, so we end up with scroll bars and a partial view of the connected desktop if it comes up on the smaller screen.

The RDP session will always come up on the monitor that the IE browser window was in.

Monitor 1 is 1280x1024 - Monitor 2 is 1680x1050

While not a perfect solution, the method to get a full screen RDP session via the RWW to work is as follows:

1. Set the smaller monitor as the Main Monitor.
2. Do not close the Display Settings window.
3. Move the IE browser window to the smaller monitor.
4. Connect to the remote desktop using the Connect to ... Computer link.
5. Log onto the workstation.

Once the logon has completed and the remote computer's desktop has come up, switch the Main Monitor back to the larger of the pair.

When we are working on a workstation with an odd set of monitors like this, we tend to put the client's server or desktop on the larger monitor, and have our reference desktop VM opened up on the smaller monitor in full screen mode.

This method works for both SBS 2003 and SBS 2008 Remote Web Workplace desktop sessions.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

New Mac RDC Client v2.0 does not support TS Gateway

The new Remote Desktop Client for Mac, version 2.0, does not support the new Terminal Services TS Gateway feature.

Since we are in the midst of working with our principle Mac based client on a new solution for their three sites, having the ability to remote into a dedicated desktop for a number of key people at their various sites would just rock!

We just downloaded and installed the new RDC v2 on our iMac that is still running Tiger.

As soon as we ran through the various Preferences for the new RDC with the hope of finding the TS Gateway setting, as it is on the RDC v6.x Windows Platform client, we were disappointed to find nothing there.

And, the comments in this Mac Mojo post confirms that there are others who would like to see the TS Gateway ability in the Mac RDC: RDC Beta Users Update: Making It Work...RDC Beta3 Available Today.

We realize that from a programming perspective, implementing this feature may have not been possible given the time lines for the v2 release. But, there is a definitely a need to implement it in the R2 version or next release of the client ... and soon!

Please note that our iMac's Safari will not load the Blogger site at all. So, this post is coming via one of our Windows systems. We will hopefully be able to flatten it and get Leopard on it soon!

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.

SBS 2008 - HP LaserJet 1320 will not auto install for TS

We blogged a bit about our experiences with HP LaserJets and the automatic driver install built into Terminal Services on SBS 2008: SBS 2008 Terminal Services and HP Printer Drivers

We ran into one printer that had a driver that would not install no matter what we tried. Not only that, the printer would not accept the HP Universal Print Driver either.

That printer was the HP LaserJet 1320.

If there is a need to deploy TS Desktops or Applications and the remote users have a LaserJet 1320, then we need to install the HP LaserJet 1320 onto the LPT1: port to enable the remote users to print.

When we do this, we name the printer DO NOT USE so that the remote users do not mistakenly try and run a print job to it.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists

*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.