The Chrome Remote Desktop installation for Windows can be build by bots now.

chrome/tools/build/win/FILES.cfg

Index: chrome/tools/build/win/FILES.cfg
diff --git a/chrome/tools/build/win/FILES.cfg b/chrome/tools/build/win/FILES.cfg
index 85f8d5115d20ad110d147d4ae648e6b0e7bee140..d6f74000b9d453aac7cdffae2a91d2e70c18532f 100644
--- a/chrome/tools/build/win/FILES.cfg
+++ b/chrome/tools/build/win/FILES.cfg
@@ -415,6 +415,13 @@ FILES = [
   },
   # Remoting files:
   {
+    'filename': 'chromoting.msi',
+    'arch': ['32bit', '64bit'],
+    'buildtype': ['dev', 'official'],

[nsylvain, 2012/04/11 19:47:11]

If this is for "google chrome" only, maybe 'dev' should not be there?

[alexeypa (please no reviews), 2012/04/11 19:52:53]

Not, it is for both dev and official builds. For dev builds one should either
have files from the internal svn or specify wix_path% and platformsdk_path% in
~/.gyp/include.gypi.

[alexeypa (please no reviews), 2012/04/11 19:55:39]

On a second thought though, you may be right. Is FILES.cfg involved in any sort
of build that an external developer can run?

[Michael Moss, 2012/04/11 20:07:17]

FILES.cfg should just be used by the buildbot scripts. I'm not going to worry if
this breaks any other usage.

+    'archive': 'remoting-host.msi',
+    'direct_archive': 1,
+  },
+  {
     'filename': 'remoting-webapp.zip',
     'arch': ['32bit', '64bit'],
     'buildtype': ['dev', 'official'],