This post is about deploying an instance of Seafile using Docker on a non-standard port (i.e. not 80 and 443). The reason to deploy the app on a non-standard port is usually because there is already another webserver running on that port (in my case Apache 2). In such scenarios, it is necessary to set up a reverse proxy so the Seafile port can be exposed by Apache on ports 80/443. Under typical circumstances, deploying Seafile on a standard port would mean that the app would host itself without the need for Apache 2 at all. This post also assumes Ubuntu 16.04 as the operating system, but in theory should apply to other Linux OS’s.

The process can be split into multiple parts:

1. Setup Docker
2. Deploy Seafile
3. Configure Apache 2
4. Setup systemd
5. Setup e-mail (optional)
6. Backing up the image
7. Troubleshooting

Setup Docker

This guide won’t go into depth on how to setup Docker, but rather the setup guide and more information about what Docker is can be found here: https://docs.docker.com/get-started/

Deploy Seafile

The key page in the Seafile documentation for deploying Seafile within Docker can be found here: https://github.com/haiwen/seafile-docker. The command I used is as follows:

docker run -d --name seafile \
  -e SEAFILE_SERVER_HOSTNAME=seafile.example.com \
  -e SEAFILE_ADMIN_EMAIL=me@example.com \
  -e SEAFILE_ADMIN_PASSWORD=a_very_secret_password \
  -v /opt/seafile-data:/shared \
  -p 8000:80 \
  seafileltd/seafile:latest

I recommend setting up Seafile with an actual secret password because it’s not easy to change once it’s set up.

Note that the port argument shows 8000:80. It means that Docker will use the host port 8000 and the container will use port 80 – meaning that using Docker will interpret requests from my host OS on port 8000 as requests on port 80 in the container. 8000 was used on my setup because port 80 was already used.

Once the command is executed, the necessary files will be downloaded and the container will start and will be accessible on port 8000.

There is also an option to setup Seafile with an SSL cert from Let’s Encrypt, but I didn’t do this because I already had a cert that I wanted to reuse.

Once the server is up, navigate to https://seafile.example.com/sys/settings/ and change SERVICE_URL and FILE_SERVER_URL to match your domain name.

Configure Apache 2

Adding a reverse proxy on Apache 2 will allow Apache 2 to route requests to port 8000, which will go to port 80 in the container. The main reference for this section is this: https://manual.seafile.com/deploy/deploy_with_apache/. This is done by adding a new site to Apache 2. The following configuration assumes that a LetsEncrypt SSL certificate is used.

cd /etc/apache2/sites-available
sudo nano seafile.conf

<IfModule mod_ssl.c>
<VirtualHost *:443>
    ServerName seafile.example.com
    ServerAdmin me@example.com

    RewriteEngine On

    # ModSecurity does not process requests.  There is a hard limit of 1 GB
    # with ModSecurity.
    SecRuleEngine Off

    # Whitelist internal IPs for mod_evasive
    DOSWhitelist 192.168.1.*

    <Location /media>
        Require all granted
    </Location>

    # Stuff for seafile server
    ProxyPass /seafhttp http://127.0.0.1:8082
    ProxyPassReverse /seafhttp http://127.0.0.1:8082
    RewriteRule ^/seafhttp - [QSA,L]

    # Stuff for seahub
    SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
    ProxyPreserveHost On
    ProxyPass / http://127.0.0.1:8000/
    ProxyPassReverse / http://127.0.0.1:8000/

    ErrorLog ${APACHE_LOG_DIR}/seafile_error.log
    CustomLog ${APACHE_LOG_DIR}/seafile_access.log combined

    Include /etc/letsencrypt/options-ssl-apache.conf

    SSLCertificateFile /path/to/cert/file.pem
    SSLCertificateKeyFile /path/to/cert/key/file.pem
</VirtualHost>
</IfModule>

I’ve added my local domain to the whitelist so that mod_evasive doesn’t think my local host is a threat.

There are two sets of ProxyPass and ProxyPassReverse lines. The reason for this is that Seafile is split up into Seahub and Seafile, where one uses port 8082 (by default), while the other uses 8000. These two lines are essentially what allows Apache to read requests from port 443 and pass them on to the container.

Once the file is saved, execute the following

sudo a2ensite seafile.conf
sudo service apache2 reload

Navigating to the site at the Apache 2 defined port should now load Seafile without having to go to port 8000.

Setup systemd

systemd allows the Docker container to be started up on boot, and be controlled like this:

sudo service seafile start/stop/restart

The configuration is as follows:

sudo nano /etc/systemd/system/seafile.service

[Unit]
Description=Seafile Server
After=network.target mysql.service

[Service]
Type=oneshot
ExecStart=/usr/bin/docker container start seafile
ExecStop=/usr/bin/docker container stop seafile
ExecReload=/usr/bin/docker container restart seafile
RemainAfterExit=yes
User=root
Group=root

[Install]
WantedBy=multi-user.target

Once the configuration is saved, shut off the existing running instance of Seafile and then let systemd start it up for you.

sudo systemctl daemon-reload
sudo service seafile start

At this point, Seafile should start automatically on boot, with Apache 2 doing a reverse proxy to the true Seafile port.

Setup e-mail (optional)

Optionally, Seafile can be configured to send e-mails. The reference is here: https://manual.seafile.com/config/sending_email/. The config file should be under:

/opt/seafile-data/seafile/conf/seahub_settings.py

I happen to be using Gmail SMTP, so at the end of the file I’ve added

EMAIL_USE_TLS = True
EMAIL_HOST = 'smtp.gmail.com'
EMAIL_HOST_USER = 'me@example.com'
EMAIL_HOST_PASSWORD = 'password'
EMAIL_PORT = 587
DEFAULT_FROM_EMAIL = EMAIL_HOST_USER
SERVER_EMAIL = EMAIL_HOST_USER

Backing up the image

After setting everything up, you’ll probably want to backup the Docker image. First, print out the list of running containers

sudo docker ps

Then take a snapshot of the current running state:

docker commit -p <container ID> <whatever you want to call this snapshot>

Running this command lists all the images and should show this newly saved image:

sudo docker images

I don’t have a private docker repository, so I saved the image to the disk and backed up the file by doing the below. Just make sure to actually move the image to an actual backup location.

sudo docker save -o <whatever path you want>/<filename>.tar <the name used earlier>

The image should be backed up now. To restore the image, it’s a matter of running this:

sudo docker load -i <path to the backup file>

Listing the images as above should show that the image was successfully loaded. Running this starts it back up again.

sudo docker run <container name>

Troubleshooting

Seafile logs can be helpful if it doesn’t start up correctly. These can be found at:

/opt/seafile-data/logs/seafile

There may be a need to ssh into the Docker container. The command for that is:

sudo docker exec -it seafile /bin/bash

A couple weeks ago, a classmate of mine invited me to participate in the UBC Engineering Competition in Senior Design.  After checking the calendar to see if I was free that day, I accepted.  I later found out that the winners of this competition would represent UBC in the Western Engineering Competition in Saskatoon, which will take place in January.  The problem with this was that three out of the four people on my team had a Co-op work term (myself included).  Despite the fact that we knew we weren’t going to the competition, we went to compete anyway.  There was little pressure for us, and winning or losing didn’t matter.

Some time later, I realized that my friend’s birthday party was the day before the competition, which meant I probably wasn’t going to get a lot of sleep.  Indeed I was right.  I got home at about 2:30 in the morning and had to arrive at the competition at 8:30.  Before I slept, I read an email that told us to read over the competition materials and to prepare a PowerPoint presentation template for the competition.  Seeing that we weren’t aiming to win the competition, I neglected to do any of this preparation.  My teammates neglected this as well.

On the morning of the competition, we went through all the registration procedures and find out what the design problem was.  Our task was to build an autonomous vehicle that could transport an object and bring it back to the starting location.  The only parts we were given was the Vex Robotics Kit, which came with a microcontroller, motors, wheels, and parts to build the frame.  We would be scored on how many objects we picked up, the weight of the vehicle, and the team’s presentation performance.

Since we didn’t really aim to win the competition, the team ended up being super chill through the entire competition.  One of the officials said to us, “Your team is the least stressful team we’ve seen!”  We made so many lame/funny/stupid jokes during the competition and had such great laughs.  Throughout the entire competition, I was probably super sleepy, and found no time to rest at all.  Despite the fact that we didn’t aim to win, we still tried hard in the competition.

Our strategy was simple: KISS.  Keep It Simple Stupid.  We realized that in the 5 hours we were given to design it, we did not have time to make anything complex.  It made the most sense.

The biggest design issue was the question of how the vehicle was going to know how to return back to its starting location after it leaves.  The only sensors we were given were buttons that would be pressed when the vehicle ran into an object.  None of these sensors would help us achieve this.  We thought of making the robot do a 180 degree turn, but this was difficult since we didn’t really have a way of measuring how many degrees the vehicle had turned.  We tried to time it, but the time it took to turn varied depending on how heavy the cargo was.  One of my teammates came up with the terrific idea of not rotating at all.  The vehicle would drive straight, pick up and then go in reverse back to the starting location.  We would then orient the vehicle in another direction to pick up the next object (we were allowed to do this since teams are allowed to touch their vehicle when it is in the starting location).

Going with this strategy, the vehicle would drive in a straight line toward the target object.  A sensor placed in the front of the object would be activated when the vehicle hit the object.  This would signal a cage to come down and enclose the object.  Then the vehicle would go in reverse back to its starting location.  The cage was simply a “fence” that was initially raised and then lowered to enclose the object.

After a lot of testing, we were quite confident that ours was going to work.  While doing all of this testing and designing, one of my group members made the PowerPoint presentation.  It basically talked about how the device worked and our design strategy.

The only preparation for the presentation that we had was just 5 minutes of telling who would present which slide.  When it came time for us to present, we looked at the slide and pretty much made up what we were going to say on the spot.  Because of this, our presentation seemed quite natural.  The fact that we all worked on the project allowed us to all know what we were talking about, so we didn’t stutter a lot.  I figure we did okay on the presentations.  Nothing spectacular.

After the presentations, each team took turns demonstrating their device.  There were a few designs that were definitely innovative, ambitious, and simple.  Among these, there was one that lowered a large arm onto the ground and sweep in a 360 to catch all the objects and return them all home at the same time.  It was a interesting design, but there was no way for the robot could do a perfect 360, since it was impossible to get the timing for it right and the power the motors gave would not be enough to move the entire load.  There was also a design that relied on randomly searching the entire field for an object and then moving around the perimeter of the field to return home.  This was the most ambitious design, but it didn’t work out because its random searching didn’t find any objects to grab.  Another team relied on the same principle as ours but were heavier.

As each team demonstrated their vehicle, it became apparent that our team had a big chance of winning.  We were very confident that we would get at at least one object, and our vehicle was the lightest one.  The team with the lightest vehicle would score the most points in terms of weight.  But for object retrieval, no team retrieved more than one object.  It was either one or zero.  If our vehicle grabbed even one object, we would be in first place for vehicle performance.  When it became our team’s turn to demo, our vehicle worked exactly the way we wanted it to.  We grabbed one.  We went on the grab another, but due to us failing to aim the vehicle properly, we failed to grab a second.  But it didn’t matter, we were in the lead in points.  Since no team grabbed more than one, we placed first in terms of vehicle performance.  We had a chance to win.

After the officials calculated the totals of all the scores, my team placed first out of twelve teams!  The best part about this is that even though we did zero preparation, we came out on top because we executed our design strategy better than the other teams.  We made use of the testing time to make sure our project actually worked.  It seemed like a lot of the projects weren’t tested that thoroughly, but that might have to do with the intense time pressure and a complex design.  The lack of pressure to win allowed us to perform so much better.

• Rogers Wireless: [10-digit phone number]@pcs.rogers.com
• Fido: [10-digit phone number]@fido.ca
• Telus: [10-digit phone number]@msg.telus.com
• Bell Mobility: [10-digit phone number]@txt.bell.ca
• Kudo Mobile: [10-digit phone number]@msg.koodomobile.com
• MTS: [10-digit phone number]@text.mtsmobility.com
• President’s Choice: [10-digit phone number]@txt.bell.ca
• Sasktel: [10-digit phone number]@sms.sasktel.com
• Solo: [10-digit phone number]@txt.bell.ca
• Virgin: [10-digit phone number]@vmobile.ca

http://smartcanucks.ca/how-to-send-free-text-messages-to-rogers-fido-telus-bell-virgin-cell-phones-canada/

UPDATE: This set of instructions works for the Office 2010 Technical Preview as well.

Based on: https://answers.microsoft.com/en-us/msoffice/forum/all/trying-to-install-office-2010-but-getting-error/4a5e022f-13f1-42bb-ad66-f6dccfd44d40

To automatically uninstall the 2007 Microsoft Office suite, follow the steps in the following Microsoft Knowledge Base article: http://support.microsoft.com/kb/971179/

How do I uninstall the 2007 Office suites if I cannot uninstall it by using the “Add or Remove Programs” feature?

The steps provided in the ‘More Information’ section of this article provide the details of the removal performed by the solution in 971179.

You may find it easier to follow the steps if you print this article first.

First, verify that you cannot uninstall the 2007 Microsoft Office system by using Add or Remove Programs (or Programs and Features)

To verify that you cannot uninstall the 2007 Microsoft Office system by using Add or Remove Programs (or Programs and Features in Windows Vista), follow these steps.

For Windows XP or Windows Server 2003:

1. Click Start, click Run, type control appwiz.cpl in the Open box, and then press ENTER.
2. Click to select the 2007 Office system product from the application list, and then click Remove.

For Windows Vista:

1. Click Start, type prgrams and features in the Search box, and then press ENTER.
2. Click to select the product to be uninstalled from the listing of installed products, and then click Uninstall/Change from the bar that displays the available tasks.

If you were able to uninstall the 2007 Microsoft Office system by using Add or Remove Programs, you are finished. If you were unable to uninstall the 2007 Microsoft Office system, you may have issues with the Add or Remove Programs dialog box, or some 2007 Microsoft Office components may not be uninstalled. In these cases, you may be unable to reinstall the 2007 Microsoft Office system. Go to the next section to uninstall the 2007 Microsoft Office system by using an alternative method.

If Add or Remove Programs does not uninstall the 2007 Microsoft Office system, use this alternative method to uninstall

Use this method only if the Add or Remove Programs method did not work for you. Using this method does not completely uninstall the 2007 Microsoft Office system. After you use this method, you can reinstall the 2007 Microsoft Office system.

Note You must be logged on to Windows with a user account that is a computer administrator to complete this method. If this is your personal computer, you are likely already logged on with an administrator account. If this is a computer that is part of a network, you might have to ask the system administrator for help.

To uninstall the existing 2007 Microsoft Office system if you cannot uninstall it by using the Add or Remove Programs feature, follow these steps:
Step 1: Remove any remaining Windows Installer packages of the 2007 Microsoft Office system:

1. Click Start, click Run, type installer, and then click OK.
   This process opens the %windir%Installer folder.
2. On the View menu, click Details.
   Important To use the View menu in Windows Vista, you must press the ALT key first to display the menu bar, and then click the View menu.
3. On the View menu, click Choose Details.
4. Click to select the Subject check box, type 340 in the Width of selected column (in pixels) box, and then click OK.
   Note It may take several minutes for the subjects to appear next to each .msi file.
5. For Windows XP or Windows Server 2003, on the View menu, point to Arrange icons by, and then click Subject.
   For Windows Vista, on the View menu, point to Sort By, and then click Subject. In Windows Vista, a User Account Control dialog box may be displayed with the following warning:
   An unidentified program wants access to your computer

   Click Allow when you see this warning message.

6. For each .msi file where the subject is “Microsoft Office Product_Name 2007,” right-click the .msi file, and then click Uninstall.
   Note Product_Name is a placeholder for the name of the 2007 Microsoft Office product.

Step 2: Stop the Office Source Engine service:

1. For Windows XP and Windows Server 2003, click Start, click Run, type services.msc in the Open box, and then click OK.
   For Windows Vista, click Start, click Start Search, type services.msc, and then press ENTER.
2. In the Services window, determine whether the Office Source Engine service is running. If this service is running, right-click Office Source Engine, and then click Stop.
3. Close the Services window.

Step 3: Remove any remaining 2007 Microsoft Office installation folders

1. For Windows XP and Windows Server 2003, click Start, click Run, type %CommonProgramFiles%\Microsoft Shared in the Open box, and then click OK.
   For Windows Vista, click Start, click Start Search, type %CommonProgramFiles%\Microsoft Shared, and then press ENTER.
   Note On a computer that is running a 64-bit version of Windows Vista, type %CommonProgramFiles(x86)%\Microsoft Shared, and then press ENTER.
2. If the following folders are present, delete them:
   • Office12
   • Source Engine
3. For Windows XP and Windows Server 2003, click Start, click Run, type %ProgramFiles%\Microsoft Office, and then click OK.
   Note On a computer that is running a 64-bit version of Windows XP, type %ProgramFiles(x86)%\Microsoft Office, and then press ENTER.
   For Windows Vista, click Start, click Start Search, type %ProgramFiles%\Microsoft Office, and then press ENTER.
   Note On a computer that is running a 64-bit version of Windows Vista, type %ProgramFiles(x86)%\Microsoft Office, and then press ENTER.
4. On the root folder of each hard disk drive, locate and then open the MSOCache folder. If you cannot see the MSOCache folder, follow these steps:
   1. Open Windows Explorer, and then on the Tools menu click Folder Options.
   2. Click the View tab.
   3. In the Advanced settings pane under Hidden files and folders, click Show hidden files and folders.
   4. Click to clear the Hide protected operating system files check box, and then click OK.
5. Open the drive_letter:\MSOCache\All Users folder, and then delete every folder that has the following text in the folder name: 0FF1CE

   Note This text contains a zero and a one for the letters “O” and “I.”

Step 4: Remove any remaining 2007 Microsoft Office installation files

1. For Windows XP and Windows Server 2003, click Start, click Run, type %appdata%\microsoft\templates, and then click OK.
   For Windows Vista, click Start, click Start Search, type %appdata%\microsoft\templates, and then press ENTER.
2. Delete the following files:
   • Normal.dotm
   • Normalemail.dotm
3. For Windows XP and Windows Server 2003, click Start, click Run, type %appdata%\microsoft\document building blocks\Language_ID, and then click OK.
   For Windows Vista, click Start, click Start Search, type %appdata%\microsoft\document building blocks\Language ID, and then press ENTER.
   Notes
   • If you cannot open this folder because the folder does not exist, go to step 6.
   • Language_ID is a placeholder for the four-digit number that represents the language of the 2007 Microsoft Office system. For example, if you use the English version of the 2007 Microsoft Office system, the Language_ID value is 1033. If the Language_ID is not known, type %appdata%microsoftdocument building blocks, and then open the subfolder in that location.
4. Delete the Building blocks.dotx file.
5. For Windows XP and Windows Server 2003, click Start, click Run, type %temp%, and then click OK.
   For Windows Vista, click Start, click Start Search, type %temp%, and then press ENTER.
6. On the Edit menu, click Select All.
7. On the File menu, click Delete.
8. For Windows XP and Windows Server 2003, click Start, click Run, type %AllUsersprofile%\Application Data\MicrosoftOfficeData, and then click OK.
   For Windows Vista, click Start, click Start Search, type %AllUsersprofile%\Application DataMicrosoftOfficeData, and then press ENTER.
9. Delete only the Opa12.dat file.

Step 5: Remove the registry subkeys of the 2007 Microsoft Office system

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: http://support.microsoft.com/kb/322756/

1. Locate and then delete the registry subkeys of the 2007 Microsoft Office system if they are present. To do this, follow these steps:
   1. For Windows XP and Windows Server 2003, click Start, click Run, type regedit, and then click OK.
      For Windows Vista, click Start, click Start Search, type regedit, and then click OK.
   2. Click the following subkey:
      HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
   3. On the File menu, click Export, type DeletedKey01, and then click Save.
   4. On the Edit menu, click Delete, and then click Yes to confirm the deletion.
   5. For each registry subkey in the following list, repeat steps 1a through 1d. Change the name of the exported key by one for each subkey.
      For example, type DeletedKey02 for the second key, type DeletedKey03 for the third key, and so on.
      Note In the following registry keys, the asterisk character (*) represents one or more characters in the subkey name.
      32-bit versions of Microsoft Windows:
      • HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Delivery\SourceEngine\Downloads\*0FF1CE}-*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\*F01FEC
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\*F01FEC
      • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
      • HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Win32Assemblies\*Office12*

        64-bit versions of Microsoft Windows:

      • HKEY_CURRENT_USER\Software\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\DeliverySourceEngineDownloads\*0FF1CE}-*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*0FF1CE*
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\UpgradeCodes\*F01FEC
      • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\*F01FEC
      • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ose
      • HKEY_CLASSES_ROOT\Installer\Features\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Products\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\UpgradeCodes\*F01FEC
      • HKEY_CLASSES_ROOT\Installer\Win32Assemblies\*Office12*
2. Locate the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

   Note On a computer that is running a 64-bit version of Windows, locate the following registry subkey instead:

   HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall
3. On the File menu, click Export, type UninstallKey01, and then click Save.
4. Under the Uninstall subkey that you located in step 2, click each subkey, and then determine whether the subkey has the following value assigned to it:
   • Name: UninstallString
   • Data: file_name path\Office Setup Controller\Setup.exe path
     Note In this example, file_name is a placeholder for the name of an installation program, and path is a placeholder for the file path.
5. If the subkey contains the name and the data that are described in step 4, click Delete on the Edit menu. Otherwise, go to step 4.
6. Repeat steps 4 and 5 until you locate and then delete every subkey that matches the name and the data that are described in step 4.
7. Close Registry Editor.

Step 6: Restart the computer

Restart the computer. If the uninstall was successful, you are finished and can now reinstall the 2007 Microsoft Office system if you want. If the uninstall was not successful, go to the “Next Steps” section.

Additional registry information

HKEY_CURRENT_USER\Software\Microsoft\Office\Common\UserInfo

Shadow subkeys for Windows Server 2003 and for earlier versions of Windows Server:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software\Microsoft\Office\12.0

Shadow subkeys for Windows Server 2008:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\Software

Source: http://support.microsoft.com/default.aspx/kb/928218