Web Deploy 3.6

[Kandy Swartzel]

Heyfolks, we identified the issue causing Frankfurt region deploys to timeout out intermittently and believe it has now been resolved. Please let us know if you continue to encounter issues, and apologies for the inconvenience caused here.

I initially ran into this issue a handful of times about 2 or 3 weeks ago. Since then everything worked fine, until today. I ran into two timeouts again this morning. Only a cache refresh + manual build solved it.

I am developing an app that helps the (two) administrators of a local charity manage their operation. I have purchased two Starter licences on their behalf. One of the soon-to-be users is not at all computer literate, so I developed a simple little app that helps her in a small way, but mostly that gets her used to using an AppSheet app with its unique UI/UX before I roll out the main app in a month or so. I shared this little app with both admins and with myself under a different identity. (I had to get set up with an email account in the charity's domain in order that I could set up a shared Google Drive for hosting the underlying sheet(s). Google won't let me do that with a personal account.) Because the little app is simple and ready to use, I deployed it, although frankly I don't really understand what "deployment" does.

I was under the impression that, as the developer, I don't need a licence. So why does AppSheet want four -- not three -- licenses? I also thought that I could share apps under development for testing purposes (which is exactly why I shared with both admins rather than just one). I have deleted the share with myself-in-the-charity-domain as I only wanted that for testing purposes. And I have deleted the share with the other admin as she doesn't need the practice. But now I am totally confused about how many licenses I need, how much I can share a developing app for testing purposes, and what the difference is between deploying and sharing.

AppSheet's help confuses me even more. Anybody out there who can explain all this? [1] Do I, as the developer but not user, need a license? [2] Do I need licenses to share an app for testing purposes? [3] What does deploying do, and can I un-deploy? Any help gratefully received.

A Non-Deployed/Prototype app is an apps that has access to nearly all features. Emails and Push Notifications will only go the App Creator and Texts will not be sent at all. Schedule automations will not run automatically. They must be triggered manually for testing. There may be other features disabled I am not thinking of. These apps can have up to 10 test users for FREE - including the developer - no paid Licenses required.

In a Deployed app, the implemented features are analyzed to determine the Plan level requirements - Starter, Core or Enterprise. In so configured apps, each authenticated user adds to the licensed user count (only once per ACCOUNT per month) and yes the "app developer" also counts towards this license count. Technically, AppSheet has not way to tell if the "app developer" is also a user. Once the app is Deployed, license charges begin at the cost based on the required Plan and all features such as Email and Text work normally.

You had described yourself as the "developer" and not the the App Creator. I read into it that you were added as a developer by the App Creator. However, only the App Creator can buy licenses so I should have been able to read between the lines.

I am the App Creator. I have a personal email account (@gmail.com). I wanted to create a shared Google Drive to host the spreadsheets that underlie my app, but Google won't allow you to create a shared Drive unless you have a corporate account so I created another account for myself using the app user's corporate name (@charityname.org). I then used that to create the shared Drive. I moved the sheets from my personal Drive to the shared Drive and modified the app to reflect this.

I then invited the two (real) users, for whom I had paid licences, and myself as me-at-charityname.org so that I could test the app from the users' perspective. Those three plus me-at-outlook.com made Google think I needed four licences rather than two. I un-deployed the app and removed me-at-charityname.org, which seems to have kept the licence bot happy, at least for the time being.

To configure and perform deployments of Office LTSC 2021, including Project and Visio, for users in your organization, you use the Office Deployment Tool (ODT). The Office Customization Tool (OCT) that you previously used for Windows Installer (MSI) is no longer used.

The installation files for Office LTSC 2021 are available on the Office Content Delivery Network (CDN) on the internet instead of on the Volume Licensing Service Center (VLSC). You can install Office LTSC 2021 directly from the Office CDN. Or, you can download the installation files from the Office CDN to a location on your local network, such as a shared folder, and install Office LTSC 2021 from that location. You can use different methods for different sets of devices in your organization. Whichever method you choose, you use the ODT.

Installing directly from the Office CDN requires the least amount of administrative effort and is recommended. But you might have constraints that prevent you from installing directly from the internet. For example, some devices might not have connectivity to the internet or you might have limited bandwidth to the internet.

After you download the Office Deployment Tool, double-click on the officedeploymenttool executable (.exe) file to extract the ODT files. When you're finished, you should have several files: setup.exe and some sample configuration.xml files. For an Office LTSC 2021-specific sample, see Sample configuration.xml file to use with the Office Deployment Tool.

The setup.exe file is the ODT and is a command-line tool that supports downloading and installing Office LTSC 2021. The configuration.xml files are sample files to get you started. You use the configuration.xml file to provide settings for the ODT to use when downloading or installing Office LTSC 2021. The configuration.xml is a simple xml file that can be created and edited in any text editor, such as Notepad. You can name the file anything that you want, as long as it retains the xml file extension.

Once you have a copy of the ODT, you need to create a configuration.xml file. You can create multiple configuration.xml files to be used with the ODT. For example, you can create a configuration.xml file to download and install the 64-bit version of Office LTSC Professional Plus 2021 in English. Then, you can create a different configuration.xml file to install the 32-bit version of Visio LTSC Professional 2021 in French. When you run the ODT from an elevated command prompt, you specify which configuration.xml file to use.

There are a series of settings in the configuration.xml file that you configure to customize the Office LTSC 2021 download or installation. The following table lists the most common settings to configure in the configuration.xml file.

We recommend that you uninstall any previous versions of Office before installing Office LTSC 2021. To help you uninstall versions of Office that use Windows Installer (MSI) as the installation technology, you can use the ODT and specify the RemoveMSI element in your configuration.xml file.

For more information about using RemoveMSI, see Remove existing MSI versions of Office when upgrading to Microsoft 365 Apps. Even though that article is about Microsoft 365 Apps, most of the information also applies to Office LTSC 2021.

To uninstall 2019 versions of Office, Visio, or Project from the device, use the Remove element. You use the Remove element because 2019 versions of Office, Visio, and Project are installed by using Click-to-Run, not Windows Installer (MSI).

Once you have a copy of the ODT and have created your configuration.xml file, you can download the Office LTSC 2021 installation files to your local network. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type this command:

Once you have a copy of the ODT and have created your configuration.xml file (and downloaded the Office LTSC 2021 installation files to your local network, if necessary), you can install Office LTSC 2021. To do that, open an elevated command prompt, go to the folder where you saved the ODT and the configuration.xml file, and type the following command:

You can also use Microsoft Configuration Manager (current branch) to deploy Office LTSC 2021. The Office 365 Client Installation wizard steps you through the process and builds the configuration.xml file for you. There's an entry for Office LTSC Professional Plus 2021 in the wizard. On that same page, you can also select to deploy Project and Visio. To get to the wizard, in the Configuration Manager console, navigate to Software Library > Overview > Office 365 Client Management.

Office LTSC 2021 no longer includes the Teams client app. However, if the Teams client app was previously installed with Office LTSC 2021, it will continue to be automatically updated approximately every two weeks with new features and quality updates. The update process for Teams is different from the update process for other Office apps, such as Word and Excel. For more information, see Teams update process.

3a8082e126