Office web apps unattended server installation - installation

Our IT-department wants a script for everything that should be installed on any of our servers. They don't want to use installation wizards and click next-next-next (don't ask me why)
We need to install Office Web Apps Server to be used with our SharePoint 2013 solution.
Is it possible to install this without having to use the wizard? (with a script)

in Office Web Apps server folders, there is a folder called Files\setupsilent\ where you will find config.xml. this file contain information about silent installation of Office Web Apps Server.
call the installer like this (if your Office Web Apps server installer is extracted in c:\OWA)
setup.exe /config files\setupsilent\config.xml
this will be complete silent setup. You will not see any screens. If you like to see wizard and progress bar proceeding automatically (passive), you can change the
"Display Level="none" in this config.xml
to
Display Level="basic"
hope it helps.

Related

Deployed application using InstallShield does not work

If you see below image, there are two applications deployed to IIS.
QManualDeployment - This is deployed using Visual studio Publish feature.
InstallShieldPOCWebApplication - This is deployed using InstallShield installation tool.
Option 1 is working without any issues, but as you see InstallShieldPOCWebApplication it looks like foder rather than web site. Also it does not work.
How can I deploy application as website using INSTALLSHIELD
Here is my IIS Settings from InstallShield Tool
Default Web Site is a website. QManualDeployment is a virtual directory / application off of Default Web Site.
In InstallShield, it isn't enough to just author all of your directories/files into components. You also have to define the IIS configuration.
I'm not sure if you are using InstallShield Express, Professional/Premier of Limited Edition so I can't give you more direction then that.
I faced same issue with Post owner, after run Install Shield setup file, it show a folder in IIS and I resolved by right click to folder name and convert to Application.
I share for whom concerned.
After that we can select suitable application pool as

How to Deploy a Windows Service using Visual Studio 2017 Community

Working with VS2017 Community I have written a service that works on my local machine. I followed the instruction here:
https://learn.microsoft.com/en-us/dotnet/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer
and installed it successfully using Installutil.exe (as per instructions in above link). All good.
I now want to deploy that across six servers in our organisation. In Microsoft's documentation about installing services (https://learn.microsoft.com/en-us/dotnet/framework/windows-services/how-to-install-and-uninstall-services) it says:
If you’re a developer who wants to release a Windows Service that users can install and uninstall you should use InstallShield
and links to a page that applies to VS2012 (can't post any more links as my reputation<10)
I have downloaded and installed the "Microsoft Visual Studio 2017 Installer Projects" package, which allows me to create a Setup Project. When I run it, it installs the project output correctly (i.e. copies the exe & dll files to the correct folder in Program Files) but does not create the service.
There's a detailed post about deploying services on this site (question 9021075) but when I follow those instructions I get a 1001 error on Install.
All the documentation I can find refers to earlier versions of VS or the previous Installer package, so I'm not even certain if I can do it with the software I am using.
So, with VS2017 Community using Microsoft Visual Studio 2017 Installer Projects, how to I create a stand-alone Installer to deploy a service that works correctly when installed locally using InstallUtil?
Or can I use InstallUtil on the target machines? I think I'd need to install Visual Studio on them for that, which I'd prefer not to. Is there a quicker way?
I only have 6 servers to install this on, so even some manual work-around might do.
Thank you for the responses. I now have a solution. I found InstallUtil on the Target Server (in my case it was in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 but search will find it). I copied and added that to my project as content so when I now deploy it, I have InstallUtil in the same folder as my EXE.
To install, I run CMD as admin, cd to project folder and issue command:
installutil.exe myService.exe
This is a one-off task. Once the service is working, to update it I just need to stop it, upload the new myService.exe (& any DLLs) to overwrite the old ones and restart it again.
Further information about settings you're using for the serviceProcessInstaller1 and serviceInstaller1 files will be needed to debug this issue, as the 1001 error raised by the installer is a generic error.
An alternative way of doing this is to use Topshelf, which is a framework for hosting services written using the .NET framework. It simplifies the creation of services, allowing developers to create a simple console application that can be installed as a service using Topshelf. The reason for this is simple: It is far easier to debug a console application than a service. And once the application is tested and ready for production, Topshelf makes it easy to install the application as a service.
Alternatively, you could use InstallUtil.exe. It is part of the .NET Framework, so no need to install Visual Studio.

How to create thin setup for Windows MSI Installer?

We have windows application in which we distribute whole MSI package to the client in zip form. We are now up for licensing feature and we want to allow users to work in thin setup just like if you download Visual Studio to install, it will download the files from the server and install it rather than we download whole 20GB VS setup from the server.
We want to use the web-based installer in which we can manage the licensing features too.
Can anyone help or redirect to useful links? It will be a pleasure.

How to install Web Deploy for Hosting Servers on Windows Server 2016

The Web Platform Installer fails to install Web Deploy for Hosting Servers on Windows Server 2016.
To fix this, first install the missing components using Server Manager, Manage, Add Role and Features. I think these are the ones required: Logging Tools, Request Monitor, .Net Extensibility, ASP.Net, ISAPI Extensions, ISAPI Filters, Management Service. I ended up with the following for my needs.
Next install Web Deploy 3.6 for Hosting Servers using the Web Platform Installer. (If it fails, note which components it depended on, install as above and try again.)
At this stage if you look for Deploy again in the Platform Installer it won't be installed, even though it says it was successful.
Go to Control Panel, Add or Remove Programs, find Web Deploy and choose Modify, Next, then Change.
Set IIS Deployment Handler to Entire feature will be installed, Next etc.
The Deploy menu will now appear in IIS Manager (restart it first if you already had it open) and Web Platform Installer will see that it's installed.
I tried to follow franzos answer and even though it worked in the end and resolved my issue, there was one detail missing:
At this stage if you look for Deploy again in the Platform Installer
it won't be installed, even though it says it was successful.
Go to Control Panel, Add or Remove Programs, find Web Deploy and
choose Modify, Next, then Change.
Set IIS Deployment Handler to Entire feature will be installed, Next
etc.
On my windows server core there is no "Control Panel" or other access to "Add or Remove Programs"
What resolved it for me was downloading the .msi package for WebDeploy to the server and running it from cmd.
msiexec /L msdeployinstall.log /I <path_to_msi>
This runs the installation wizard and you can change the installation with:
Set IIS Deployment Handler to Entire feature will be installed, Next etc.
as described by franzo.
Best regards and thanks for the advice.
I just ran into this on a fresh azure server 2022 node and after doing all of Franzo's stuff it still didn't work.
I decided to connect the IIS on the new node to the IIS on the old node just to see what it did... I hit "Connect to a Server...", put in the IP of the old node, and when it connected it told me the new node was missing some extensions. The web deploy was one of them and it installed it for me.

Automatic installer for a web app on Windows 7 (or higher)

I have a web application implemented in ASP.NET MVC3 and SQL Server 2008 Express. It's relatively small so I can deploy it in local computer of my clients (Windows 7 or higher).
Currently, I deploy it manually by create new web site in IIS, copy published files to the folder of website, install SQL Server 2008R2 and use Management Studio to restore database with some initial data.
It's OK with me but not with my clients. They can't do the same things. What I want is an automatic installer, my clients just need to click a few buttons to get all done.
Specifically, this automatic installer must do the following things:
Install SQL Server 2008R2 Express and restore the initial database.
Install IIS7 (if it's not enabled in Windows 7).
Create a new app pool (V4) and a new Web Site use this pool. Then copy published files to the folder of the Web Site.
The installler can run aspnet_regiis command and grant permission for NETWORK SERVICE account to TEMP folder. This is required for web site to run.
The installer can copy some fonts to Font folder of Windows.
I see many app can do this automatic installer, but after googling I can't find a thorough solution to try.
Please give me some advice on this. Thanks in advance!
If you want a free solution, WiX is what you need, but it will take you some time to learn using it if you never created a package with it.
A more easy to use, and also powerful, but payed tool, is Advanced Installer, you need Professional edition, but you can try it for free with the 30 days trial mode. It has predefined prerequisite for SQL Server Express, built-in support to install IIS entities, and set file/folder permissions. Bassically all the requirements you need.
To enable any IIS feature you can simply add a PowerShell script.

Resources