1 Reply Latest reply on Apr 14, 2010 4:22 PM by 807578

    Star Office 9 on Windows Server 2008 64Bit with Citrix Xen App 5.0

      Good day,
      I have Star Office 9 already installed on my private PC and now want to install it also on Terminal Sever with OS Windows 2008 64 Bit and Citrix Xen App 5.0 . Is there anybody who has experience with such an installation, can inform me if it works and maybe what I have to consider on installation ??
      Thanks for your help
        • 1. Re: Star Office 9 on Windows Server 2008 64Bit with Citrix Xen App 5.0
          Here's what I have been doing to get OpenOffice.org working
          on our Citrix Farm using a Win2K/Win2K3 mixed-mode domain.
          the same applies to StarOffice.

          These were the goals:

          - Give any user who wants/has to work with an Office Suite
          access to OpenOffice.org by simply putting him into a

          - The installation must work in a way the user does not have
          to interact (read: I do not want to allow his interaction
          because he is definitely going to make the wrong choices)

          The painful way to the goal (as far as I got now):

          Note 1: While most files are included here, some are missing
          (like 100kb registry settings) but can be requested
          from the author.

          Note 2: Some of the scripting is ugly and may be useless.
          It has evolved quite a bit since I started it, so
          it's kinda messy. Nevertheless it works quite well
          here, so I wouldn't want to touch it...


          This solution consists of the following parts:

          - modified setup file (optional)
          - responsefiles f�r base and workstation (=user) installation
          - installation script
          - domain logon (sub)script

          I modified the setup file (setup.inf) to stop the installer from giving me things
          I don't want. I have tried numerous ways to do this with StarBasic but failed.
          I tried the forums, I had contact with Sun developers - it simply wouldn't work
          the way it was supposed to.

          The installation script is simple. It's just there to make life a little easier
          for the sorry guy who has to install a new machine. I tried to use a packager
          to do the base installation and it horribly barfed, but then again that was in
          the days before 1.1.x. It works like this so I left it untouched.

          The major part is the domain logon script. There, we check if the user has access
          to OpenOffice.org, check for the presence of various files and try to build his
          environment as needed, taking various quirks and problems into account.

          The logon script needs a connection to a share on a fileserver/SAN/NAS. For us,
          it's still a fileserver, but it's the one holding the profiles, too, so if this
          one wouldn't be available login would be broken, anyway. I did this so I could
          slipstream newer files to the users' workstation installation if I needed to, later on.


          In my installation folder, I have the following files:

          dir install ; OpenOffice.org files (incl. modified setup.inf)
          file common.xcu ; Modified common.xcu where I set an additional
          ; template folder, for example
          file instbase.rsp ; Responsefile for base installation
          file instuser.rsp ; Responsefile for user's workstation installation
          file jobs.xcu ; Modified jobs.xcu (removed registration request)
          file MasterInstall.kix ; Script to install on a Citrix machine
          file OpenOffice-Associations.reg ; Override for document type associations
          file wkix32.exe ; kixtart w32 executable

          To install, make a shortcut to "wkix32.exe MasterInstall.kix" and doubleclick Wink
          You should be administrator on the Citrix machine, of course. As you can see from
          the script, installation mode is switched on automatically.

          Set your '$destination' as needed!


          ========== MasterInstall.kix ==========

          ; OpenOffice.org 1.1.2 Master-Installation f�r Citrix
          ; Installiert OpenOffice nach D:\Programme\OpenOffice
          ; wgi 2004/04/28 (identisch mit OpenOffice 1.1.1)
          DEBUG Off
          ; Installation anhand des Response-Files
          $Destination = "D:\Programme\OpenOffice\"
          shell "change user /install"
          ? "Installiere nach "+$Destination
          ; *
          ; * This would be a good place to copy some of the fonts
          ; * or other stuff to the machine
          ; *
          shell ".\install\setup.exe -r:..\instbase.rsp"
          SHELL "regedit /s OpenOffice-Associations.reg"
          SHELL "change user /execute"
          MessageBox("Installation nach "+$Destination+" beendet.","Total sch�n, ey ;-)",64,60)

          ========== MasterInstall.kix ==========

          Let's have a look at instbase.rsp:


          ========== instbase.rsp ==========


          wgiModule=gid_Module_Prg_Wrt_Bin,gid_Module_Prg_Wrt_Help, [.......]



          Sub PreSetup
          End Sub

          Sub PostSetup
          SetReboot( False )
          End Sub

          ========== InstBase.rsp ==========

          Some leftover stuff from trying to exclude some modules here, I just didn't clean it up.
          Remember to set 'DESTINATIONPATH' to what you need.

          Note that we do a "INSTALL_NETWORK". Although most people in the forums agreed that it doesn't work, it does - at least since 1.1.0.

          Near the end of Masterinstall.kix I import some registry settings. For some reason,
          OpenOffice.org's method of setting the associations does not work for me on a Citrix
          (Terminal Server) machine, although it seemed to be the right way to do it. Worked
          on XP workstations, for example, but it looks like Terminal Servers treat this differently.

          So I exported the registry settings, changed the tree to HKEY_LOCAL_MACHINE, imported them again and voila, it works. File can be requested from the author, unfortunately you'd have to replace all occurences of the path to your own path.
          Should be easier to repeat the described process.

          At this point, we're all set with out new Citrix machine. We can take a look at the
          Domain logonscript now.