-
Posted to
Web Deployment Tool (MS Deploy)
by
Rene Olesen
on
07-15-2009, 4:36 AM
Hi Moshaikh
I'm sorry if my earlier reply sounded as if I blaime msdeploy. Actually we dont know what went wrong, or where the "error"/limit is. But our first try to get support for the issue was denied because we have used beta software. We started a new case with the focus on the 200 limit, and then the case was accepted, but ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
Rene Olesen
on
07-14-2009, 2:42 AM
Hi David
I'm not sure what your error is about. But as I wrote in my first post, I did manually rename computername_IUSR to IUSR in the xml-files that msdeploy generated. I did this before importing them to the new server.
Now after several months of operation, I can add that the server never came up running like a charm! For some reason the ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
Rene Olesen
on
04-14-2009, 3:53 AM
Hi faith_a
Thank you very much for your reply, I already forgot I did make this post... ':)
#1 and #2 I managed to solve by editing applicationHost.config manually. I changed the folder to another partition and gave these folders modify-access for IIS_IUSRS.
#3 This issue is also gone. I just edited all apppools manually and selecting ...
-
Posted to
Web Deployment Tool (MS Deploy)
by
Rene Olesen
on
02-24-2009, 8:56 AM
After migrating our IIS 6.0 to IIS 7.0 using msdeploy, we experience some problems.
I used msdeploy to generate configurationsfiles without contentfiles. These files I coppied to the new 2008 server, and used msdeploy to import to IIS 7. At first it didn't work, because I had to rename usernames in the config file. Especially IUSR had to be ...