i am going to install "System Center Service Manager Web Portal" , so there are two option 1- web content server. 2-SharePoint web part.
if i only install web content server, is it provide me web console or not ?
and what is the benefit to integrate with SharePoint ?
In Self Service Portal all his components are web parts. So if you don't install the second option you don't be able to see the Self Service Portal forms and views.
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 do not see the option to easily configure App Service Authentication on Web Apps for Linux. I am using SSL and custom domain name.
Thanks
If you are looking for an option through the Azure Portal, then this will help.
As per the Azure Web App on Linux documentation Limitations, The Azure portal shows only features that currently work for Web App on Linux and hides the rest. As Microsoft enable more features, they will be visible on the portal.
Some features, such as virtual network integration, Azure Active Directory/third-party authentication, or Kudu site extensions, are not available yet. Once these features are available, Microsoft will update the documentation and blog about the changes.
I created an API app for MS Azure, but it runs on url like: https://microsoft-apiapped89163604714d21b7e4a3424ed82d50.azurewebsites.net/...
Can I switch it to my own domain name somehow?
You can, but unfortunately there is currently a limitation that will prevent the API App from working properly. There is a list of known limitations and issue which you can find here. The fix will be available quite soon but I don't have a specific ETA to share.
Once this is fixed, you can customize the domain by:
Going to the API App blade.
On the blade, find the "API App host" property on the Essentials and click it.
This will open the API App host blade. Click on "Settings" from the toolbar on the top.
Then find the "Custom domains and SSL" setting and customize the domain.
Effectively, once you're done with Step 2, you can follow the guide of Customizing the domain of a Web App, as both API Apps and Web Apps share the same underlying infrastructure. The guide is available here
Hope it helps.
I have been trying to setup Web Deploy on my Windows 2012 server running IIS 8. I have installed Web Deploy using Platform installer but when I right click my website and select deploy, there is no option for Configure Web Deploy Publishing as various documentation suggests.
I found this posting where the individual had the same problem. Turns out that he needed to install "Web Deploy 3.5 for Hosting Servers" on top of the other Web Deploy packages in web platform installer. Once I did this and restarted IIS the option became available.
Seems counter-intuitive to me since I am not a hosting provider and just wanted to host my application on my own server. I am not sure why the Web Deploy 3.5 package was not enough.
I had additional problems getting Web Deploy configured. This article on Web Deploy error codes helped me troubleshoot the problem. Another article on Configure the Web Deployment Handler was essential in solving the permissions issue allowing the web deploy user to create directories and files.
For me the reinstall of Web Deploy didn't work. But I fixed it.
Go into the Server Manager, Roles, click on IIS, click on Add Role Services, check the Management Service. Close that out. Reopen IIS Manager, and voila the option is available!
For Windows2012 R2 server, options is in'Web Server (IIS)' -> 'Management Tools' –> 'Management Service'
P.S. Some additional steps could be required, as of #Gaui experience.
Afterwards go to Programs and Features, find Web Deploy, click Change and check/install all checkboxes/features.
You need to install Management Service before you install Web Deploy. If you haven't uninstall Web Deploy and reinstall it and it should work.
UPDATED:
Follow these steps:
type programs and features (in the menu search box)
Go to WEB DEPLOY (install it from web platform installer in case you don't have it)
Select WEB DEPLOY and click the change option at the top
Check and install ALL options available
Wait to install and close/reopen IIS GUI
the options should appear when you right click over the site.
I had the same issue and installing "Web Deployment Tool 2.1" from the Web Platform installer fixed the issue.
Installing "IIS Management Service" from Web platform would show up all the required items.
coad comment was the solution for me. I was using Web Deploy 3.6 on IIS 8.5. Removed 3.6 and install 3.5 and it worked.
Be ware !! Web Deploy 3.6 doesn't work with IIS 8.5.9600.16384 ... after installation, server restart - the deploy menu doesn't appear in IIS manager console Web Deploy 2.0 how ever doesn't suffer this issue Best Regards,
I kept on right clicking on the web application instead of web site.
One can have multiple web applications under a web site. There is also a sub menu in the context menu when you right click the web application but it is "missing" the item "Configure Web Deploy Publishing...". This is because you configure web deploy publishing for web site and not for web application.
So to sum it up
Web site has this option
Web application doesn't have it
I am using Windows Azure, and find it a lot difficult and useless make a new "Package" each time you make a small change, and want to test it on the Cloud. I heard about the opportunity to update the web roles without re-deploy the whole instance each time (about 15 minutes), and do a Web Deploy - upload just the modified files (some seconds).
None of the resources found on the web seems to describe this particular situation.
There are tutorials, on how to enable Web Deploy on Azure Web Roles, but not a one how to set it up. [This tutorial is showing the settings, but not for Azure]
To enable web deploy you first need to be able to do a standard Publish (not Package) from the CloudConfiguration project.
there are some good tutorials how to do that.
While the Publish dialog is open, make sure to select this option, and make a normal publish.
After this configuration is published, you are ready to set up the Publish settings for the Web Role project. Note, the CloudCongiguration project is used for Package deployment, and the Web project is used to deploy to Azure via Web Deploy as deploying to normal web hosting.
When you click on the "Publish" context menu of the Web project, a "Publish Web" dialog appears. All settings are easy to guess/standard, except the second tab: Connection.
Here the things go little hard, if you have not messed with Web Deployment before.
Must select the Web Deploy method
The URL to your Web Role (DNS or IP address found on Windows Azure Management portal)
The name of the web site in the IIS on the Host machine. In our case this is the Azure WebRole instance. So Login via RDP, start "Server Management", navigate to: Roles->WebServer(IIS)-> Internet Information Services Manager. In the Connections Pane (The Left part of the Manager) expand the tree-view pointing to the "localhost" service -> Sites -> and there you find the Website Name (should be something like : xxxxx_IN_0_Web)
This is the username you use for RDP connections /and the password below/
is that strange URL, that is pointing to the Web deploy Service, that will eventually update our website content.
you can check, if the Package deployment went OK, in the Azure Management portal, on the Overview page of the web deployment if the port 8172 is open.
Now "Validate Connection" should succeed!
If not, try "http://{0}.cloudapp.net//MSDEPLOYAGENTSERVICE" for Destination URL