What is the difference between these?
Restart IIS via Internet Information Services (IIS) Manager.
Use the IISReset.exe tool.
Restart the IIS services via services.msc.
As far as I know, these 3 options have the same effect.
But we recommend to go for Option1 and Option3. Please refer to this article.
"Use the IISReset.exe tool" simple and user can still use it. But actually it is not supported anymore. Details, you could refer to this article.
Related
Is it possible to remote-connect to an Azure App Service running on Windows with my IIS Manager?
This seems to have been possible according to this blog post by clicking in IIS Manager File -> Connect to a site.
I refer to the steps mentioned in the link shared by you and in the last step I got an error below.
I did some research on it and it looks like managing the App Service from IIS is not supported anymore. I have not got any official link but the below links might give you some information on it.
Microsoft.Web.Configuration.AppHostFileProvider not found after configured Remote IIS Administration for Microsoft Azure Web App
Can no longer manage any Web Apps with IIS Remote Manager - Could not load file or assembly - AppHostFileProvider
I'm not sure for what purpose why you want to. My thoughts is you shouldn't be doing that as it defeat the purpose of PaaS services. Cannot access the iis layer in app service however you can still configure in web.config of your web app.
I've seen this article:
How do I disable SSL fallback and use only TLS for outbound connections in .NET? (Poodle mitigation)
With Azure web apps I didn't know if the IIS sites were already set up to deny earlier versions of TLS/SSL. Or should i implement a code fix like the article recommends.
I suggest that you test your app with https://www.ssllabs.com/ssltest/ or similar. There are a number of other tools (including commandline clients, although I've only used them on Linux) but the SSLLabs test is solid and useful IMO.
That should give you insight into what you may need to tweak to make it as secure as possible.
Note: I'm a Linux guy and know next to nothing about Azure, but unless I'm missing something this seems like a pretty generic question.
Each Azure Web app having default certificate you can see this certificate and it uses TLS 1.2 security certificate.'
In firfox left side of URL on browser you can click on Lock symbol to see certificate. path(Click Lock icon-->click More Information ---Click Certificate) you will see Algo and Certificate details.
Default certificate is secure for internal use in company
As I know, Azure WebApp doesn’t support it at currently. From my experience, since we don’t have enough access to configure anything in the registry in the WebApp. We can use startup task to change registry settings, if it is CloudService.
I also find some materials in the SO, more details please refer to thread.
I have been doing this with webrole. But as I understand windows azure websites: multiple sites hosted in a single webrole.
Q.1. Is it possible to connect to webrole?
Q.2. Is it possible to atleast connect to Azure IIS management console?
Adding to Jeff's answer, while you can't remote debug your website, you can terminal connect to it by going to the scm endpoint of your site: http://{sitename}.scm.azurewebsites.net and selecting "Debug console".
More on this here: https://github.com/projectkudu/kudu/wiki/Kudu-console
It will give you a nice way for managing some aspects of your site (mainly file based) but will not let you do other things like install office for example.
No, with Windows Azure Web Sites it is a managed solution. You can edit web.config and use the management portal, but there is no more direct ways to access the underlying compute resource.
I have a remote Windows 2012 server running IIS 8 from which I am hosting a web application. My local development box is running Visual Studio 2012. Currently I am publishing my app as a web deployment package (.zip), RDP'ing to the production server, copy + pasting to a folder and deploying the application from within IIS. My question is, what changes do I need to make to deploy directly to IIS from Visual Studio 2012 using the web deploy option?
I have tried to follow this guide but it refers to a service URL which I must obtain from my hosting company. I don't have a hosting company, my server is co-located.
I am presented with the following options:
Is the username and password the one I use for the RDP account? I already have Web Deploy 3.0 installed on IIS do I need to enable further settings?
OK I found the solution but it took me a whole day to get it working! Basically the steps are as follows. This is very sketchy but see the detailed guides below which helped me.
Enable the IIS Web Management role feature.
Install Web Deploy 3.0 (or higher). Make sure to customise the install to include the handlers (See notes below). If you're not presented with this option go to add/remove programs, find webdeploy, right click and select "change" option.
In IIS click on the server node and find the "Management Service" icon. Enable remote access and configure a dedicated IIS User for remote deployment (These will be the credentials that will go in the user name and password boxes).
At the site level in IIS assign this user to manage the website.
Make sure port 8172 is open on the web server (you can check this port here).
Try reconnecting from Visual Studio. There was some trial and error here for me but the error messages do link to a MS guide for decoding :)
Even after connecting successfully I had to wrangle with permissions, so my IIS user had sufficient privileges to create the app pool, directories and general file management jobs.
The following links really helped!
Configuring the handler on the web server:
http://www.iis.net/learn/publish/using-web-deploy/configure-the-web-deployment-handler
Connecting via Visual Studio:
http://msdn.microsoft.com/en-us/library/dd465337(v=vs.110).aspx
NOTES:
To ensure the handler is running, login into your IIS server and point your browser to the following URL.
https://<servername>:8172/MsDeploy.axd
F12 to open up the dev tools to see the HTTP response. Also MsDeploy also creates IIS logs in inetpub/logs which should give you some clue if you're having connectivity problems.
I had the same problem and this post was very useful to help me solve the issue. I had anyhow serious troubles while trying to install Web Deploy on my Windows Server 2012. The installation of Web Deploy 3.0 was giving me several errors and it couldn't be completed.
I tried to solve the problem installing "Microsoft Web Platform Installer 5.0" from http://www.microsoft.com/web/downloads/platform.aspx but it didn't solve it.
I thought it was due to Firewall Settings, Authorizations issues, Users without permissions or something like that. Finally I found out it wasn't due to any of the mentioned reasons.
I found the most simple solution and I hope it will help other users too: it was enough to download Web Deploy 3.5 installation directly from Microsoft Website:
http://www.microsoft.com/en-us/download/details.aspx?id=39277
This may sound banal but it solved it. I was able to install "Web Management Service" but not the second needed IIS service "Web Deployment Agent Service".
We have a requirement where we need to have some web services running on a server machine but it does not have IIS available. I came across this article on running asmx without IIS and many other sites/blogs have mentioned this article as well.
http://msdn.microsoft.com/en-us/magazine/cc163879.aspx
Could somebody offer alternatives to above to run asmx web services without IIS installed?
Other option i could find was Cassini - http://ultidev.com/products/cassini/
Windows Azure! That is precisely what it was designed for... it’s cheap and reliable!