2019 Id Checking Guide
An online publication of the Drivers License Guide Co. See other publications: Logout Contact Legal/Disclaimer. Sep 3, 2013 - Checking IDs Every employee. The person has to actually check the ID. In California, I. Get the ID of the person you think is under the age of 30 in your hand to screen it. Don't look at. By David Klemt Jun 21, 2019 5:00am.
-->Applies To: Windows Server 2019, Windows Server 2016
The following information outlines initial planning considerations that you need to review for Key Management Services (KMS) activation involving Windows Server 2019. For information about KMS activation involving operating systems older than those listed here, see Step 1: Review and Select Activation Methods.
Welcome to the. Anheuser-Busch Wholesalers Order Page for the. 2019 DRIVERS LICENSE GUIDE. The Guide covers all U.S. And Canadian ID's in a quick,.
KMS uses a client-server model to active clients. KMS clients connect to a KMS server, called the KMS host, for activation. The KMS host must reside on your local network.
KMS hosts do not need to be dedicated servers, and KMS can be cohosted with other services. You can run a KMS host on any physical or virtual system that is running Windows 10, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows 8.1, or Windows Server 2012.
A KMS host running on Windows 10 or Windows 8.1 can only activate computers running client operating systems.The following table summarizes KMS host and client requirements for networks that include Windows Server 2016, Windows Server 2019 and Windows 10 clients.
Note
- Updates might be required on the KMS server to support activation of any of these newer clients. If you receive activation errors, check that you have the appropriate updates listed below this table.
- If you are working with virtual machines, see Automatic Virtual Machine Activation for information and AVMA keys.
| Product key group | KMS can be hosted on | Windows editions activated by this KMS host |
|---|---|---|
| Volume License for Windows Server 2019 | Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 | Windows Server Semi-Annual Channel Windows Server 2019 (all editions) Windows Server 2016 (all editions) Windows 10 Enterprise LTSC 2019 Windows 10 Enterprise LTSC N 2019 Windows 10 LTSB (2015 and 2016) Windows 10 Professional Windows 10 Enterprise Windows 10 Pro for Workstations Windows 10 Education Windows Server 2012 R2 (all editions) Windows 8.1 Professional Windows 8.1 Enterprise Windows Server 2012 (all editions) Windows Server 2008 R2 (all editions) Windows Server 2008 (all editions) Windows 7 Professional Windows 7 Enterprise |
| Volume License for Windows Server 2016 | Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 | Windows Server Semi-Annual Channel Windows Server 2016 (all editions) Windows 10 LTSB (2015 and 2016) Windows 10 Professional Windows 10 Enterprise Windows 10 Pro for Workstations Windows 10 Education Windows Server 2012 R2 (all editions) Windows 8.1 Professional Windows 8.1 Enterprise Windows Server 2012 (all editions) Windows Server 2008 R2 (all editions) Windows Server 2008 (all editions) Windows 7 Professional Windows 7 Enterprise |
| Volume license for Windows 10 | Windows 7 Windows 8.1 Windows 10 | Windows 10 Professional Windows 10 Professional N Windows 10 Enterprise Windows 10 Enterprise N Windows 10 Education Windows 10 Education N Windows 10 Enterprise LTSB (2015) Windows 10 Enterprise LTSB N (2015) Windows 10 Pro for Workstations Windows 8.1 Professional Windows 8.1 Enterprise Windows 7 Professional Windows 7 Enterprise |
| Volume license for 'Windows Server 2012 R2 for Windows 10' | Windows Server 2008 R2 Windows Server 2012 Standard Windows Server 2012 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Datacenter | Windows 10 Professional Windows 10 Enterprise Windows 10 Enterprise LTSB (2015) Windows 10 Pro for Workstations Windows 10 Education Windows Server 2012 R2 (all editions) Windows 8.1 Professional Windows 8.1 Enterprise Windows Server 2012 (all editions) Windows Server 2008 R2 (all editions) Windows Server 2008 (all editions) Windows 7 Professional Windows 7 Enterprise |
Note
Depending on which operating system your KMS server is running and which operating systems you want to activate, you might need to install one or more of these updates:
- Installations of KMS on Windows 7 or Windows Server 2008 R2 must be updated in order to support activation of clients running Windows 10. For more information, see Update that enables Windows 7 and Windows Server 2008 R2 KMS hosts to activate Windows 10.
- Installations of KMS on Windows Server 2012 must be updated in order to support activation of clients running Windows 10 and Windows Server 2016 or Windows Server 2019, or newer client or server operating systems. For more information, see July 2016 update rollup for Windows Server 2012.
- Installations of KMS on Windows 8.1 or Windows Server 2012 R2 must be updated in order to support activation of clients running Windows 10 and Windows Server 2016 or Windows Server 2019, or newer client or server operating systems. For more information, see July 2016 update rollup for Windows 8.1 and Windows Server 2012 R2.
- Windows Server 2008 R2 cannot be updated to support activation of clients running Windows Server 2016, Windows Server 2019, or newer operating systems.
A single KMS host can support an unlimited number of KMS clients. If you have more than 50 clients, we recommend that you have at least two KMS hosts in case one of your KMS hosts becomes unavailable. Most organizations can operate with as few as two KMS hosts for their entire infrastructure.
KMS can activate physical and virtual computers, but to qualify for KMS activation, a network must have a minimum number of computers (called the activation threshold). KMS clients activate only after this threshold is met. To ensure that the activation threshold is met, a KMS host counts the number of computers that are requesting activation on the network.
KMS hosts count the most recent connections. When a client or server contacts the KMS host, the host adds the machine ID to its count and then returns the current count value in its response. The client or server will activate if the count is high enough. Clients will activate if the count is 25 or higher. Servers and volume editions of Microsoft Office products will activate if the count is five or greater. The KMS only counts unique connections from the past 30 days, and only stores the 50 most recent contacts.
KMS activations are valid for 180 days, a period known as the activation validity interval. KMS clients must renew their activation by connecting to the KMS host at least once every 180 days to stay activated. By default, KMS client computers attempt to renew their activation every seven days. After a client’s activation is renewed, the activation validity interval begins again.
KMS activation requires TCP/IP connectivity. KMS hosts and clients are configured by default to use Domain Name System (DNS). By default, KMS hosts use DNS dynamic update to automatically publish the information that KMS clients need to find and connect to them. You can accept these default settings, or if you have special network and security configuration requirements, you can manually configure KMS hosts and clients.
After the first KMS host is activated, the KMS key that is used on the first host can be used to activate up to five more KMS hosts on your network. After a KMS host is activated, administrators can reactivate the same host up to nine times with the same key.
If your organization needs more than six KMS hosts, you should request additional activations for your organization’s KMS key—for example, if you have ten physical locations under one volume licensing agreement and you want each location to have a local KMS host.
Note
To request this exception, contact your Activation Call Center. For more information, see Microsoft Volume Licensing.
Computers that are running volume licensing editions of Windows 10, Windows Server 2019, Windows Server 2016, Windows 8.1, Windows Server 2012 R2, Windows Server 2012, Windows 7, Windows Server 2008 R2 are, by default, KMS clients with no additional configuration needed.
If you are converting a computer from a KMS host, MAK, or retail edition of Windows to a KMS client, install the applicable KMS Client Setup Key. For more information, see KMS Client Setup Keys.
-->To configure and perform deployments of volume licensed versions of Office 2019, 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 2019 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 2019 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 2019 from that location. You can use different methods for different sets of computers 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 computers might not have connectivity to the internet or you may have limited bandwidth to the internet.
Download the Office Deployment Tool from the Microsoft Download Center
The Office Deployment Tool is a free download from the Microsoft Download Center. We recommend that you always download and use the most current version of the ODT.
After you download the Office Deployment Tool, double-click on the officedeploymenttool executable (.exe) file to extract the ODT files. When you are finished, you should have several files: setup.exe and some sample configuration.xml files. For an Office 2019-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 2019. 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 2019. 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.
Create the configuration.xml
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 would create a configuration.xml file to download and install the 64-bit version of Office Professional Plus 2019 in English and a different configuration.xml file to install the 32-bit version of Visio Professional 2019 in French. When you run the ODT from an elevated command prompt, you specify which configuration.xml file to use.
Tip
Instead of using a text editor to create your configuration.xml, we recommend that you use the Office Customization Tool (OCT). The OCT provides a web-based interface for making your selections and creating your configuration.xml file to be used with the Office Deployment Tool. For more information, see Overview of the Office Customization Tool. Please note that this is different than the Office Customization Tool that you might have used in the past to install volume licensed versions of Office that used Windows Installer (MSI) as the installation technology.
There are a series of settings in the configuration.xml file that you configure to customize the Office 2019 download or installation. The following table lists the most common settings to configure in the configuration.xml file.
| Configuration | configuration.xml setting | Additional information |
|---|---|---|
| Where to download the Office installation files to and where to install Office from For example, servershare (a shared folder on your local network) | SourcePath | If you don’t specify a SourcePath when using the ODT to install Office, the ODT looks for the installation files in the folder it’s located in. If it doesn’t find the Office installation files there, it goes to the Office CDN to get the installation files. We recommend that you install Office directly from the Office CDN, if internet connectivity and network bandwidth make that possible. |
| Which products to download or install For example, Office Professional Plus 2019 | Product ID | Valid values for volume licensed versions of Office 2019 include the following: - ProPlus2019Volume - Standard2019Volume - ProjectPro2019Volume - ProjectStd2019Volume - VisioPro2019Volume - VisioStd2019Volume |
| Use Multiple Activation (MAK) to activate Office 2019 | PIDKEY | Enter the product key for MAK activation. You don’t need to use PIDKEY if you’re activating Office 2019 with Key Management Service (KMS). |
| Which languages to download or install For example, English (en-us) and French (fr-fr). | Language ID | You can install multiple languages at the same time you’re Installing Office 2019, or you can install them later. For more information, see Deploy languages for Office 2019. |
| Which proofing tools to install | Product ID | The Product ID is 'ProofingTools' and is used in combination with the Language ID. For more information, see Deploy languages for Office 2019. |
| Which edition of Office 2019 to download or install. For example, the 64-bit version. | OfficeClientEdition | Valid xml values are '32' and '64.' All Office products on the computer must be of the same architecture. You can’t have both 32-bit and 64-bit Office products installed on the same computer. We recommend 64-bit on computers that have 4 gb or more of memory. But you should assess application compatibility and other factors that might require you to use the 32-bit version. For more information, see Choose between the 64-bit or 32-bit version of Office. |
| Which apps to install For example, all apps except Publisher. | ExcludeApp | By default, all apps included in Office Professional Plus 2019 are installed. For example, to not install Publisher, you can include the following line in your configuration.xml: <ExcludeApp /> For more information, see ExcludeApp element. |
| Where to get security and quality updates from. For example, directly from the Office CDN on the internet. | UpdatePath | The default is to get updates directly from the Office CDN on the internet. This is recommended and requires the least amount of administrative effort. But if you need to update computers that don’t have connectivity to the internet, you can specify that Office gets updates, for example, from a shared folder on your local network. But this means that you must download the updates from the Office CDN and copy them to the shared folder. For more information, see Update Office 2019 (for IT Pros). |
| Which update channel to install from and get updates from | Channel | Office uses the concept of update channels to determine which updates an installed version of Office receives. For more information, see Update channel for Office 2019. |
| Whether to remove previous Windows Installer (MSI) versions of Office before installing Office 2019 | RemoveMSI | This is recommended. For more information, see Remove existing versions of Office before installing Office 2019. |
Tip
More information about these configuration.xml settings is available here: Configuration options for the Office Deployment Tool. Keep in mind that not all the information in that article applies to Office 2019. For example, the settings related to shared computer activation, such as SharedComputerLicensing and SCLCacheOverride, don’t apply to Office 2019.
Sample configuration.xml file to use with the Office Deployment Tool
The following is a sample configuration.xml file that can be used to either download or install the 64-bit version of Office Professional Plus 2019 in English using a shared folder on your local network and activate by using MAK. If you’re using this configuration.xml to install Office 2019, previous Windows Installer (MSI) versions of Office are removed as part of the installation process. Also, even though it’s not specified in the configuration.xml file, updates are automatically enabled and are configured to come directly from the Office CDN, because those are the default settings.
For the PIDKEY, replace #####-#####-#####-#####-##### with your MAK client activation key.
Remove existing versions of Office before installing Office 2019
We recommend that you uninstall any previous versions of Office before installing volume licensed versions of Office 2019. To help you uninstall versions of Office that use Windows Installer (MSI) as the installation technology, you can use the Office Deployment Tool and specify the RemoveMSI element in your configuration.xml file.
Id Checking
There are several ways that you can use the RemoveMSI element when installing volume licensed versions of Office 2019.
- Uninstall all Office products on the computer.
- Identify any existing language resources, like language packs, and install the same languages.
- Keep some Office products and uninstall all other Office products on the computer.
RemoveMSI can be used to uninstall 2010, 2013, or 2016 versions of Office, Visio, or Project that were installed using Windows Installer (MSI).
For more information about using RemoveMSI, see Remove existing MSI versions of Office when upgrading to Office 365 ProPlus. Even though this article is about Office 365 ProPlus, most of the information also applies to volume licensed versions of Office 2019.
Download the Office 2019 installation files
Once you have a copy of the ODT and have created your configuration.xml file, you can download the Office 2019 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:
If you have saved the configuration.xml file with a different name, use that name in the command.
It will look as if nothing is happening, but the download is happening in the background. Once the download is complete, you are returned to a command prompt.
If you want to check that the files are downloading, go to the location you specified for your SourcePath in the configuration.xml file. You should see a folder named “Office” with a subfolder named “Data.” There will also be a folder named with the version number of the download. For example, 16.0.10336.20044. Which files you see and the names of the files depend on whether you are downloading the 32-bit or 64-bit version of Office and which languages you are downloading.
Here some additional details about downloading Office 2019 installation files:
- You must download the 32-bit and 64-bit versions separately.
- All volume licensed versions of Office 2019 – such as Office Professional Plus 2019, Visio Professional 2019, and Project Professional 2019 – are included in the same download, regardless of which products you specify in the configuration.xml file. This helps you save disk space on your local network. The core files for the Office 2019 products are in the stream.x86.x-none.dat or stream.x64.x-none-dat file, depending if it’s the 32-bit or 64-bit version of Office.
Install Office 2019 by using the Office Deployment Tool
Once you have a copy of the ODT and have created your configuration.xml file (and downloaded the Office 2019 installation files to your local network, if necessary), you can install Office 2019. 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:
If you have saved the configuration.xml file with a different name, use that name in the command.
Once the installation is complete, you are returned to a command prompt and you can go open Office 2019 programs you’ve installed.
Install Office 2019 by using System Center Configuration Manager
You can also use System Center Configuration Manager to deploy volume licensed versions of Office 2019. Configuration Manager (Current Branch) has a wizard that steps you through the process and builds the configuration.xml file for you. Earlier versions of Configuration Manager require you to download the ODT and create your own configuration.xml file.
Id Checking Guide 2018
Configuration Manager (Current Branch): If you’re using Configuration Manager (Current Branch), you can use the Office 365 Client Installation wizard to deploy Office 2019. You must be using at least version 1710, but version 1806 is recommended. You’ll see an entry for Office Professional Plus 2019 in the Office 365 Client Installation wizard. On that same page, you can also select to install Project and Visio.
System Center 2012 R2 Configuration Manager: If you’re using System Center 2012 R2 Configuration Manager, the steps are different and much more manual. First you need to get a copy of the ODT from the Microsoft Download Center and create the appropriate configuration.xml file for your deployment. Then, in Configuration Manager, you create an application and a deployment type. After that you distribute the application and then deploy it.
Deploy languages for Office 2019
You can use the ODT and the configuration.xml file to install volume licensed versions of Office 2019, including Project and Visio, in multiple languages. For more details, see Language element.
You can also just install proofing tools by specifying the Product ID as 'ProofingTools' in your configuriation.xml file along with the appropriate Language IDs. Proofing tools packages, which are a new capability for Office 2019, are much smaller than full language packs. Consider deploying proofing tools in cases where users work with documents in multiple languages but don’t need the Office product UI in all those languages. The proofing tools can be installed at the same time you’re installing Office 2019, or you can install them later. They can also be installed whether or not the language pack for a given language is installed.
If you're upgrading from a Windows Installer (MSI) version of Office, you can get Click-to-Run versions of the same language resources – for example, language packs, language interface packs, or proofing tools – installed when you deploy Office 2019. For more information, see Remove existing MSI versions of Office when upgrading to Office 365 ProPlus. Even though this article is about Office 365 ProPlus, most of the information also applies to volume licensed versions of Office 2019.