An announcement was made recently on the “Revit Deployment & Management for Medium Sized Offices” Udemy course (see here for more info):

We seem to have just discovered an interesting “bug” in Deployments as they relate to Revit Server. The Rollout Tool offers at least a partial solution, but I would like to collaborate with an office or two who are using Revit Server, and prioritize any additions to the script. If you are using Revit Server, and can spare a little time to discuss the issue and how it might impact your specific configuration, and what the Rollouts can do to help, please email me directly (email hidden). I’ll schedule a GotoMeeting for some time that works for you and we can proceed from there.


Gordon Price

Basically this enables rich client access to Windows Server 2012 … you can install it via Windows Update or:
Download Update for Windows 7 (KB2592687) from Official Microsoft Download Center

To install this update, you must be running Windows 7 SP1 or Windows Server 2008 R2 SP1.

How to enable RDP 8.0 on a remote computer that is running Windows 7 SP1

To enable RDP 8.0 on a remote computer that is running Windows 7 SP1, follow these steps:

Note The following instructions are applicable only for remote computers that are running Windows 7 SP1.

  1. Install the appropriate version of the update package by running the Windows6.1-KB2592687 update file.
  2. Restart the computer.
  3. Open the Local Group Policy Editor.
  4. Enable the Remote Desktop Protocol policy. The setting for this policy is under the following node:
    Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostRemote Session Environment
  5. If the UDP functionality is necessary, enable the RDP Transport policy, and then set the value to Use both TCP and UDP. The setting for
    the RDP Transport policy is under the following node:
    Computer ConfigurationAdministrative TemplatesWindows ComponentsRemote Desktop ServicesRemote Desktop Session HostConnections

    Note Configuring the RDP Transport policy also enables firewall rules to allow the 3389 UDP port.

  6. Restart the computer.

Description of the Remote Desktop Protocol 8.0 update for Windows 7 SP1 and Windows Server 2008 R2 SP1

Revit makes it very easy to produce a LOT of drawings. This can result in a large deliverable. In one recent case, our Tender Issue of drawings consisted of 132 A1 sheets. Using CutePDF (with a couple of handy tweaks), we printed these to a PDF file of around 48 MB.

Depending on your email size policy, a file of this size would take anywhere from 5 to 16 emails to transmit.

To avoid this eventuality, I have explored various options for uploading large files and making them available to our colleagues. FTP seemed to be the answer, but one of our Clients is behind a proxy or firewall system that doesn’t allow FTP access – even with an anonymous account! So it was back to the drawing board…

Therefore, I decided to setup a HTTP server for file access. I downloaded Apache 2.2 (for Windows, without SSL). I took the following steps:

  1. Allowed a port through our firewall and directed it to the PC running Apache. We have a static IP, so I could now access Apache by typing in
  2. Ensured that the opened port setting matched the Apache port in the httpd.conf file
  3. Disabled the ‘Indexes’ feature for a subfolder of the Apache ‘root’ folder (in my case this was C:Program FilesApache Software FoundationApache2.2htdocsFILES).
  4. Created a password for this folder using htpasswd.exe
  5. Enabled password access to the same folder using the following text in httpd.conf

    Options FollowSymLinks
    AuthType Basic
    AuthName “Restricted Files”
    # (Following line optional)
    # AuthBasicProvider file
    AuthUserFile “C:/Program Files/Apache Software Foundation/Apache2.2/password/.htpasswd”
    Require valid-user

Now I can login to the PC running Apache, copy any file I want to serve via HTTP to the password protected folder, and then send a link to any of our colleagues that I want to gain access to this file.I also setup Filezilla FTP Server on another PC in our network, and forwarded port 21 through our router to this PC. I setup a user for a folder on this PC, and disabled all rights apart from ‘read’.I can now send an email that contains two hyperlinks to any large file we wish to transmit, one for FTP and one for HTTP. Both of these links are password protected.And all of this is done using free, open source software!