Thanks, Sascha, for your answer. My installers will be used by the user, not by me, and I won't my user to use Orca, that is not very friendly for regular user.
I have problems to create sufficient agent installer by Wix (I'm not strong in that field) and currently I suppose to use MSI automation. I have a tool in my server installation that will use Automation to modify server's DNS-name property inside MSI. So as you see I'm writing my little and more friendly Orca, adopted for my single case. Though my solution works for me, it will be interesting to know how my situation should be solved in normal situation, because it is rather a regular case to make Server-Clint installations. Plus, I'd like to add another question :). I'd like to have single installer for both 64 and 32-bit Windows systems. But here I have non trivial case, because I have a driver, that should be placed in C:\Windows\System32\drivers folder. I have 32-bit driver and 64-bit driver. All other binaries are 32-bit. I won't create two installation packages for 32-bit and 64-bit systems, because only one MSI should be uploaded to GPO server. The problem is that 64-bit OS runs 32-bit installer to WOW64 folder any time it tries to get access to System32 folder. My solution is to create c++ custom action dll, that will detect system and turns off Windows system32 folder virtualization to get access to original System32 folder on 64-bit System. In regular case as far as I understand developer should create two installation packages for 32 and 64 bit operation systems. Though it is much more convenient to have one installer in a Active Directory GPO. Thanks. _________________________ WBR, Polazhenko Sergey > -----Original Message----- > From: Sascha Beaumont [mailto:sascha.beaum...@gmail.com] > Sent: Tuesday, July 21, 2009 2:44 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] client setup > > I've got no idea about administrative installs, but you could just use > Orca to create an MST and add the IP to the property table which would > be a lot simpler. > > > On Tue, Jul 21, 2009 at 7:17 AM, Polazhenko Sergey<s_polazhe...@tut.by> > wrote: > > Good day to all Wix Users. > > > > > > I'm running across rather popular situation (on my mind), though > cannot get simple solution. > > > > My product has both server and client. Then I install client I should know > > server IP/DNS name. So, when I create client installer I'd like to have a > > property with server's IP/DNS name inside. Currently I have a solution, that > > uses command line parameter, but it is not enough, because I would like my > > client to be installed trough Active Directory Group Policy (GPO). GPO > > expects msi file without any command line parameters. > > > > It will be nice to have client installer that: > > 1. has administrative mode, which takes server's IP/DNS name > > interactively through UI-dialogs and stores this value inside this MSI. This > > MSI will be uploaded on GPO server. > > 2. during normal installation process (through GPO or manual setup), > > installer should use server's IP/DNS setting from the property, stored > > inside that MSI file. > > > > Thanks! > > __ > > WBR, Polazhenko Sergey ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
