Search results matching tag 'iis6 to iis7'

Re: Different Physical Path and Name for migrated application

sasikantt_24 — Wed, 15 Jul 2009 15:02:11 GMT

Yes we can do this. But previously I was writing manifest file which was containing 2 metakey elements. One for application pool and one for web site. Application pool was setting properly for web site with that approach after migration. Also I was writing single ms deploy command to achieve this.But now I have to migrate application pool first and then I have to create web site using AppCmd and then I need to synchronize web site using ms deploy command that you have mentioned above.
With this approach I don’t have application pool set for the web site after synchronization. It’s “DefaultAppPool” and not the application pool that I have migrated.How can I set application pool that I have migrated for the Web site? Should I write AppCmd again to set application pool for the Web site?

Thanks,
Shashikant

Re: Different Physical Path and Name for migrated application

sasikantt_24 — Tue, 14 Jul 2009 06:26:04 GMT

I want separate web site on IIS 7.0 for each application under "Default Web Site" on IIS 6.0.

Thanks,
Shashikant

Auto deploy ASP files

raskado — Tue, 14 Jul 2009 02:20:44 GMT

Hello everyone,

I want to auto deploy ASP files to live server and back up previous files before replacing them, Can anyone please tell how can I do that using Web Deployment Tools? and Is there any guidline or video to illustrate the steps?

I appreciate anyone helps, Thanks

Kiarash

Re: Different Physical Path and Name for migrated application

sasikantt_24 — Mon, 13 Jul 2009 16:03:47 GMT

Thanks moshaikh. I can now change path as well as application name while migrating from IIS 6.0 to IIS 7.0.

Actually my concern is, I have all applications under Default Web Site in IIS 6.0. But after migration I don’t want these applications under Default Web Site.

I want separate Web site for each application.

I tried with following command:

msdeploy –verb:migrate –source:metakey=lm/w3svc/1/root/MyApplication –dest:metakey=lm/w3svc/2/MyApplication,computername=iis7.0server_name

It’s giving me an error.

Error: Metabase keys /lm/w3svc/1/root/MyApplication and /lm/w3svc/2/MyApplicationn are not compatible for syncing

Can you please let me know, how can we move application outside Default Web Site while migration using MS Deploy?

Thanks
Shashikant

msdeply with encryptPassword

Aled — Wed, 01 Jul 2009 16:00:38 GMT

I'm trying to migrate a number of sites from Server 2003 to Server 2008 with msdeploy. All going well until I got to the site that has SSL. This one required me to enter a password when archiving the site using encryptPassword which I did. Now I have come to install it on the new server (2008) it is giving me the following error :

Error: The property 'value' is encrypted. The same password that was used for encryption must be specified in order to continue.
Error count: 1

I am using the same password. I even went back and made another archive just to make sure but I got the same error. I've Googled this error message but it didn't find a single page about it.

The commands I used are :

msdeploy -verb:sync -source:metakey=lm/w3svc/711308 -dest:archivedir=c:\sitearchive\711308,encryptPassword=MyPassKey

msdeploy -verb:migrate -source:archivedir=D:\sitearchive\711308 -dest:metakey=lm/w3svc/711308,encryptPassword=MyPassKey

Can anyone help me with this please?

Thanks
Aled

Re: Different Physical Path and Name for migrated application

sasikantt_24 — Wed, 20 May 2009 14:14:03 GMT

I used following ms deploy commands to change my application name and physical path for migrated application on server where IIS 7.0 is installed, but nothing is updated.

Please find the command and output of the command and kindly correct me, where I am going wrong.

msdeploy -verb:migrate -source:metaKey=lm\w3svc\1\root\MyApplication -dest:auto,computerName=Servername -setParam:type=DestinationVirtualDirectory,value=D:\DeptName-MyApplication,scope="Defaul
t Web Site/MyApplication" -setParam:type=ProviderPath,value= DeptName-MyApplication,
scope="Default Web Site/MyApplication" -enableLink:AppPoolExtension
Action: Updating metaProperty (/lm/w3svc/1/root/MyApplication/UNCPassword)
Action: Updating metaProperty (/lm/w3svc/1/root/MyApplication/UNCPassword)
Action: Updating filePath (D:\DeptName\MyApplication\AppMessages.xml)
Action: Updating filePath (D:\DeptName\MyApplication\MyApplication.asmx)
Action: Updating filePath (D:\DeptName\MyApplication\MyApplication.wsdl)
Action: Updating filePath (D:\DeptName\MyApplication\bin\Some.dll)
Action: Updating filePath (D:\DeptName\MyApplication\bin\MyApplication.dll)
Action: Updating filePath (D:\DeptName\MyApplication\bin\MyApplication.pdb)
Action: Updating filePath (D:\DeptName\MyApplication\Global.asax)
Action: Updating filePath (D:\DeptName\MyApplication\web.config)
Action: Updating metaProperty (/lm/w3svc/1/root/MyApplication/UNCPassword)
Change count: 11

Nothing is updated on server where IIS 7.0 is installed when I migrate Myapplication from server where IIS 6.0 is installed.

Thanks

Re: newbee needs help

vijayam — Tue, 19 May 2009 11:20:19 GMT

Hello,

You send the Error message to the Service image and also any time you asking questions at the time please send me currently.

HTTP Error 404.17 - Not Found

sasikantt_24 — Mon, 18 May 2009 12:20:41 GMT

Hi

HTTP Error 404.17 - Not Found

The requested content appears to be script and will not be served by the static file handler.

I migrated my web service from IIS 6.0 to IIS 7.0 successfully with following steps.

1. I check for dependencies for my web service. I found that web service is dependant on “MyAppPool “

I migrated application using manifest. In manifest I write following things.

</ MyApplication >

2. I use following command to migrate web service.

msdeploy -verb:migrate -source:manifest=D:\ MyApplication.xml -dest:auto,computerName=IIS7.0ServerName

I successfully migrate web service with above steps.

3. When I browse web service I get Http error 404.17 as mentioned above.

Application pool for “MyApplication” is “MyAppPool” after migration. When I change it manually to “DefaultAppPool” everything works fine. But I don’t want to change application pool.

I also tried with changing “Enable 32-Bit Applications” in advanced settings for “MyAppPool” to True. But no luck.

Please help me out, Let me know work around or please guide me if I am doing anything wrong.

Thanks

Change Application Pool to "Classic .Net AppPool" for migrated application.

sasikantt_24 — Sat, 16 May 2009 08:02:33 GMT

Hi,
I have migrated application from IIS 6.0 to IIS 7.0. Default Application Pool for this migrated application is "DefaultAppPool". because of this I am getting Http Error 500.24.

The solution for this problem is, change Application Pool from "DefaultAppPool" to "Classic .Net AppPool". I have done this manually on IIS 7.0 and I am able to browse the site.

I want to know, How can we change application pool when we migrate application using Ms Deploy?

Is there any other work around for Http error 500.24?

Thanks

IIS6 to IIS7 migration

notcon — Thu, 14 May 2009 08:08:21 GMT

Hi,

We have all our sites on a 2003 server running IIS6.

We wish to migrate all these sites (including app pools, user accounts, ftp details but NOT content to our new 2008 server running iis7 and ftp7.5. Thje content will be migrated first separately. We also wish to replace all IP addresses with a new one.

We wish to do this via the archive/package method.

I have tested the deploy tool and can migrate basic site definitions but app pools, users and ftp accounts don't seem to migrate at all.

Please can someone advise as to what commands we need to use.

Thanks.

Nathan