I didn't see any responses so I thought I would throw my miniscule experience in. BTW, this was all done on Updater 2.
We went to MX from 4.01 actually without a hitch but only had the default website defined in IIS. Several months later decided we wanted to host another site for some special customer access. We added the site and followed the instructions found in one of MM's knowledgebase articles to edit the xml file and run the connector batch file only to have CF stop processing all request on ALL sites. After spending another 3 hours trying to get it to work I threw up my hands and restored the server and got everything working. I ended up coming back to it about a month later when I had another weekend I could work on it. In the mean time I read everything I could find on how IIS and CF link together and how ISAPI filters are configured. It ended up being nothing more than that the connector batch file for some reason didn't want to configure IIS's ISAPI filters correctly. When I manually configured the global settings to point to the correct places everything kicked in and started working. So I guess my point, in a round about way, is that if you already have multiple sites setup prior to putting MX on everything probably installs correctly. If you don't and want to add them later it didn't seem to work. Since my problems Updater 3 has come out and MM did some fixes in this area so all this may be moot now. ______________________________________________________ Bill Grover Supervisor MIS Phone: 301.424.3300 x3324 EU Services, Inc. FAX: 301.424.3696 649 North Horners Lane E-Mail: [EMAIL PROTECTED] Rockville, MD 20850-1299 WWW: http://www.euservices.com ______________________________________________________ > -----Original Message----- > From: Dave Watts [mailto:[EMAIL PROTECTED] > Sent: Monday, June 02, 2003 10:33 AM > To: CF-Talk > Subject: RE: Quick note from the CF Team.... > > > > Where the issues come up is when the web server is hosting > > sites on a different drive(s) and are serving web sites > > other than the default wwwroot directory. We call these > > "multi-homed" servers. There are still issues with the > > install, and even greater ones with the updaters. This > > is not just my imagination, nor is it incompetence in > > server administration. This is not hardware problems as > > the server hardware is state of the art. > > Out of curiosity, could you provide a brief summary of these > issues? I've > deployed CFMX on several Windows servers with multiple virtual servers > configured, and without any problems. I'm not saying your > problems aren't > real, I'd just like to know what might be waiting for me next time. > > > The bottom line for me is that if a server product will > > not play nice with my security requirements, it just will > > not get purchased or installed. > > Could you also provide more information about this? I'm > considered a bit > about security, too, but I haven't run into any > security-specific issues > with CFMX. I've actually found CFMX easier to secure than CF > 5, in general. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Host with the leader in ColdFusion hosting. Voted #1 ColdFusion host by CF Developers. Offering shared and dedicated hosting options. www.cfxhosting.com/default.cfm?redirect=10481 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
