This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- No...
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2009
12:48 AM
Windows 2008 Virtual Directory creation issue
Hello,
We are facing issues in creating virtual directory in a website on Windows Server 2008 which has IIS 7. This virtual directory is added in Internet Information Services view using InstallShield 2009 Premier.
PS: We have added a property (IISPREFERLEGACYOBJECTS) with value 1 which was one of the solution, but of no use.
It would be great if anyone can suggest a solution for this. 🙂
Regards,
Rajeev
We are facing issues in creating virtual directory in a website on Windows Server 2008 which has IIS 7. This virtual directory is added in Internet Information Services view using InstallShield 2009 Premier.
PS: We have added a property (IISPREFERLEGACYOBJECTS) with value 1 which was one of the solution, but of no use.
It would be great if anyone can suggest a solution for this. 🙂
Regards,
Rajeev
(6) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 04, 2009
04:01 AM
Do you want to add a VD to an existing web site or a new one? If an existing one, do you know the port number and site number of the site?
Setting IISPREFERLEGACYOBJECTS to 1, will install compatible with IIS6, but I'm not sure that works, unless the server has been installed with compatability with IIS6 . . .
Setting IISPREFERLEGACYOBJECTS to 1, will install compatible with IIS6, but I'm not sure that works, unless the server has been installed with compatability with IIS6 . . .
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2009
01:35 AM
We want to add the VD to an existing website, we know the IP and port number.
We tried the IISPREFERLEGACYOBJECTS option and we have also installed windows 2008 server with IIS6 compatibility. But this option is failing. Any other solution?
Thanks,
Rajeev
We tried the IISPREFERLEGACYOBJECTS option and we have also installed windows 2008 server with IIS6 compatibility. But this option is failing. Any other solution?
Thanks,
Rajeev
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 05, 2009
02:25 AM
You need the site number as well - I've never tried setting it up with the IP.
What I do, is I run a VBS script that fetches the Site number and port and puts them in two global variables I've made in the property manager - CRMSITEPORT and CRMSITENUMBER . . .
Then in the Internet Information Services window in the install designer, I put [CRMSITEPORT] in the port number of the website and [CRMSITENUMBER] in the site number . . .
See the attachment for my VBS script - it should be stored in a binary in custom actions ...
I didn't write all of the script myself, but took bits and pieces from David Wangs script here:
http://blogs.msdn.com/david.wang/archive/2005/07/13/HOWTO_Enumerate_IIS_Website_Configuration.aspx
BTW. I still set IISPREFERLEGACY to 1, as otherwise it puts the VD in the root of a website (and in my installation it should be in a subfolder).
What I do, is I run a VBS script that fetches the Site number and port and puts them in two global variables I've made in the property manager - CRMSITEPORT and CRMSITENUMBER . . .
Then in the Internet Information Services window in the install designer, I put [CRMSITEPORT] in the port number of the website and [CRMSITENUMBER] in the site number . . .
See the attachment for my VBS script - it should be stored in a binary in custom actions ...
I didn't write all of the script myself, but took bits and pieces from David Wangs script here:
http://blogs.msdn.com/david.wang/archive/2005/07/13/HOWTO_Enumerate_IIS_Website_Configuration.aspx
BTW. I still set IISPREFERLEGACY to 1, as otherwise it puts the VD in the root of a website (and in my installation it should be in a subfolder).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 06, 2009
07:00 PM
Have you confirmed your install package works on Windows XP?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 07, 2009
01:39 AM
Not sure if that question was directed towards me, bu my solution works on both Server 2003 and Server 2008 - never tried on Windows XP though . . .
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 07, 2009
10:27 AM
That question was directed at Rajeev 🙂
I am new myself and I am building my install package on XP for deployment to Windows Server 2008 -
My initial deployment attempts to WS 2008 all failed until I found out about IISPREFERSLEGACYOBJECTS; now the package installs as designed (I use a single Basic MSI package to deploy several chained MSI's, a couple of Window Services, 4 App Pools and 4 Virtual Directories).
But my install also worked/deployed flawlessly on XP! So once I found out about the property, without changing any thing in the package, I simply added it and everything worked perfectly deploying on WS 2008.
So, my *guess* is if an install package fails on XP then setting IISPREFERSLEGACYOBJECTS to install on Windows Server 2008 most likely will not matter...
I am new myself and I am building my install package on XP for deployment to Windows Server 2008 -
My initial deployment attempts to WS 2008 all failed until I found out about IISPREFERSLEGACYOBJECTS; now the package installs as designed (I use a single Basic MSI package to deploy several chained MSI's, a couple of Window Services, 4 App Pools and 4 Virtual Directories).
But my install also worked/deployed flawlessly on XP! So once I found out about the property, without changing any thing in the package, I simply added it and everything worked perfectly deploying on WS 2008.
So, my *guess* is if an install package fails on XP then setting IISPREFERSLEGACYOBJECTS to install on Windows Server 2008 most likely will not matter...