使用Packer在Winodws VMware Workstation Pro上自动部署Windows Server 2016中文版

川长思鸟来 2023-10-01 10:26 12阅读 0赞

Packer 是由 Hashicorp 创建的应用程序，它使 IT 专业人员能够自动执行其 VM 模板生成。随着混合云环境的兴起，它正迅速成为在一个工具下管理每个平台的多个 VM 映像的首选实用工具之一。它自动执行建立全新 VM 的过程，并合并自定义生成脚本以动态自定义 VM，然后转换回模板以用于在云中或本地进行部署。在 VMware 环境中使用 Packer 可以带来以下好处：

*  **与平台无关**– Packer 不仅可以将相同的映像和配置部署到 VMware 环境，还可以将相同的映像和配置部署到 AWS 和 Azure 等公共云提供商。这大大减少了为每个环境维护映像所花费的时间，并确保每个映像都是一致的。
 *  **更快的部署**– 将尽可能多的内容包含在映像生成中，而不是在部署时运行自定义脚本，从而创建更快的 VM 部署。
 *  **自动模板管理**– 现在可以自动执行整个过程，并且可以对计划任务运行 Packer 映像重建，而不是每月对模板手动运行 Windows 更新。
 *  **基础结构即模板的代码**– Packer 允许 IT 专业人员获取其模板内部版本并在代码中对其进行定义。这使我们能够将模板配置存储在源代码管理中，从而可以更轻松地管理和跟踪对模板所做的所有更改。
 *  **开源**\- Packer是一个开源软件，这意味着它是完全免费使用的，这使得它更是必须尝试的。

### 如何安装Packer ###

Packer只是一个可执行文件，可以放在任何文件夹中并从那里执行。您可以[在此处][Link 1]下载Packer。（当前最新版1.7.8）。在我们的示例中，我们将从 Windows 10 计算机运行 Packer。在本例中，packer.exe在C：\\Packer目录中。

Packer使用"builders"来提供为当今各种平台（如Azure，VMware和AWS）生成映像的方法。

现在，我们已准备好开始构建 VMware 模板。

### 在 VMware 中构建基本模板 ###

有两种方法可以构建模板，即 OS ISO 或现有 VM。我们将从头开始，从Windows Server 2016 ISO构建一个VM。Packer 将创建 VM、安装 OS、配置 OS，然后将 VM 转换为模板映像以用于将来的部署。我们需要创建一个Packer配置文件。Packer配置文件以 JSON 格式编写，如下所示。在我的示例中，这些设置是为我的 VMware 环境配置的。我将以下配置另存为名为WindowsServer.Json的文件。

{
    
        "builders": [
    
            {    
                "type": "vmware-iso",
                "communicator": "winrm",
                "disk_size": 61440,
                "disk_type_id": "0",
                "floppy_files": [
                    "{
       {template_dir}}/setup/"
                ],
                "guest_os_type": "windows9srv-64",
                "headless": false,
                "iso_url": "file://F:\\SOFTWARE\\SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-2_MLF_X21-22842.iso",
                "iso_checksum": "c1f8c8325e88f4687eabc4c60a6c3fcb",  
                "winrm_username": "vagrant",
                "winrm_password": "vagrant",
                "winrm_timeout": "6h",
                "skip_compaction": true,
                "vmx_data": {
                    "gui.fitguestusingnativedisplayresolution": "FALSE",
                    "memsize": "2048",
                    "numvcpus": "2",
                    "virtualHW.version": "10",
                    "scsi0.virtualDev": "lsisas1068"
                }
            }
        ],
        "provisioners": [
            {
                "type": "windows-shell",
                "inline": ["dir c:\\"]
            }
        ]
    }

接下来，我们需要创建两个文件。我们需要一个 autounattend.xml 文件来自动安装我们的 Windows Server ISO，一个 vmtools.cmd 文件来启用服务器和客户端之间的 winrm 通信，关闭防火墙，安装 Windows 期间安装 VMware Tools。这些文件将挂载到 VM 的软盘驱动器上，然后在 Windows 安装阶段运行。另请注意，您将需要修改 autounattend.xml 文件以匹配打包程序配置文件中的相同 winrm 凭据。所以现在我有了我的配置文件和一个"setup"文件夹，其中包含用于Windows安装的两个文件：

![在 VMware 中构建基本模板][VMware]

autounattend.xml

<?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SetupUILanguage>
                    <UILanguage>zh-CN</UILanguage>
                </SetupUILanguage>
                <InputLocale>zh-CN</InputLocale>
                <SystemLocale>zh-CN</SystemLocale>
                <UILanguage>zh-CN</UILanguage>
                <UILanguageFallback>zh-CN</UILanguageFallback>
                <UserLocale>zh-CN</UserLocale>
            </component>
            <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Type>Primary</Type>
                                <Order>1</Order>
                                <Size>350</Size>
                            </CreatePartition>
                            <CreatePartition wcm:action="add">
                                <Order>2</Order>
                                <Type>Primary</Type>
                                <Extend>true</Extend>
                            </CreatePartition>
                        </CreatePartitions>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Active>true</Active>
                                <Format>NTFS</Format>
                                <Label>boot</Label>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                            <ModifyPartition wcm:action="add">
                                <Format>NTFS</Format>
                                <Label>Windows 2016</Label>
                                <Letter>C</Letter>
                                <Order>2</Order>
                                <PartitionID>2</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                        <DiskID>0</DiskID>
                        <WillWipeDisk>true</WillWipeDisk>
                    </Disk>
                </DiskConfiguration>
                <ImageInstall>
                    <OSImage>
                        <InstallFrom>
                            <MetaData wcm:action="add">
                                <Key>/IMAGE/NAME</Key>
                                <Value>Windows Server 2016 SERVERDATACENTER</Value>
                            </MetaData>
                        </InstallFrom>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>2</PartitionID>
                        </InstallTo>
                    </OSImage>
                </ImageInstall>
                <UserData>
                    
                    <ProductKey>
                        
                        
                        <Key>6CNGG-BJP34-H923Y-6DMWR-37BMF</Key>
                        <WillShowUI>OnError</WillShowUI>
                    </ProductKey>
                    <AcceptEula>true</AcceptEula>
                    <FullName>Vagrant</FullName>
                    <Organization>Vagrant</Organization>
                </UserData>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <OEMInformation>
                    <HelpCustomized>false</HelpCustomized>
                </OEMInformation>
                <ComputerName>vagrant-2016</ComputerName>
                <TimeZone>China Standard Time</TimeZone>
                <RegisteredOwner/>
            </component>
            <component name="Microsoft-Windows-ServerManager-SvrMgrNc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DoNotOpenServerManagerAtLogon>true</DoNotOpenServerManagerAtLogon>
            </component>
            <component name="Microsoft-Windows-IE-ESC" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <IEHardenAdmin>false</IEHardenAdmin>
                <IEHardenUser>false</IEHardenUser>
            </component>
            <component name="Microsoft-Windows-OutOfBoxExperience" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <DoNotOpenInitialConfigurationTasksAtLogon>true</DoNotOpenInitialConfigurationTasksAtLogon>
            </component>
            <component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SkipAutoActivation>true</SkipAutoActivation>
            </component>
            <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <RunSynchronous>
                    <RunSynchronousCommand wcm:action="add">
                        <Order>1</Order>
                        <Description>Set Execution Policy 64 Bit</Description>
                        <Path>cmd.exe /c powershell -Command "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force"</Path>
                    </RunSynchronousCommand>
                    <RunSynchronousCommand wcm:action="add">
                        <Order>2</Order>
                        <Description>Set Execution Policy 32 Bit</Description>
                        <Path>cmd.exe /c powershell -Command "Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force"</Path>
                    </RunSynchronousCommand>
                    
                </RunSynchronous>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <AutoLogon>
                    <Password>
                        <Value>vagrant</Value>
                        <PlainText>true</PlainText>
                    </Password>
                    <Enabled>true</Enabled>
                    <Username>vagrant</Username>
                </AutoLogon>
                <FirstLogonCommands>
                    <SynchronousCommand wcm:action="add">
                        <Order>1</Order>
                        <CommandLine>cmd.exe /c a:\vmtools.cmd</CommandLine>
                        <RequiresUserInput>true</RequiresUserInput>
                    </SynchronousCommand>
                </FirstLogonCommands>
                <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <NetworkLocation>Home</NetworkLocation>
                    <ProtectYourPC>1</ProtectYourPC>
                </OOBE>
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>vagrant</Value>
                        <PlainText>true</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>vagrant</Value>
                                <PlainText>true</PlainText>
                            </Password>
                            <Group>administrators</Group>
                            <DisplayName>Vagrant</DisplayName>
                            <Name>vagrant</Name>
                            <Description>Vagrant User</Description>
                        </LocalAccount>
                    </LocalAccounts>
                </UserAccounts>
                <RegisteredOwner />
            </component>
        </settings>
        <settings pass="offlineServicing">
            <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <EnableLUA>false</EnableLUA>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim:c:/wim/install.wim#Windows Server 2012 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>

vmtools.cmd

rem basic config for winrm
    cmd.exe /c winrm quickconfig -q
    
    rem allow unencrypted traffic, and configure auth to use basic username/password auth
    cmd.exe /c winrm set winrm/config/service @{AllowUnencrypted="true"}
    cmd.exe /c winrm set winrm/config/service/auth @{Basic="true"}
    
    rem update firewall rules to open the right port and to allow remote administration
    cmd.exe /c netsh advfirewall firewall set rule group="remote administration" new enable=yes
    
    rem restart winrm
    cmd.exe /c net stop winrm
    cmd.exe /c net start winrm
    
    netsh advfirewall set  allprofiles state off
    
    
    e:\setup64 /s /v "/qb REBOOT=R"

然后我们需要一个Windows Server 2016 ISO。下载一个并将其保存到您的磁盘中。并且该位置在我的Packer配置文件中引用。

有很多预先设置工作要做，但自动化模板构建的好处是值得的。现在，让我们验证我们的 json 文件中没有错误。为此，请打开 PowerShell 控制台并将目录更改为 WindowsServer.Json 的位置，然后运行以下语法：

packer.exe validate WindowsServer.Json

我们可以看到我们的模板已经过验证，我们很好运行我们的构建。为此，请键入以下命令：

packer.exe build WindowsServer.Json

Windows Server需要一些时间来安装，然后打包器将安装VMware工具，最后将VM转换为模板：

F:\packer_1.7.8_windows_amd64>packer.exe build WindowsServer.Json
    Warning: Warning when preparing build: "vmware-iso"
    
    Your vmx data contains the following variable(s), which Packer normally sets
    when it generates its own default vmx template. This may cause your build to
    fail or behave unpredictably: numvcpus, memsize, virtualHW.version,
    scsi0.virtualDev
    
    Warning: Warning when preparing build: "vmware-iso"
    
    A shutdown_command was not specified. Without a shutdown command, Packer
    will forcibly halt the virtual machine, which may result in data loss.
    
    
    vmware-iso: output will be in this color.
    
    ==> vmware-iso: Retrieving ISO
    ==> vmware-iso: Trying file://F:\SOFTWARE\SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-2_MLF_X21-22842.iso
    ==> vmware-iso: Trying file://F:/SOFTWARE/SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-2_MLF_X21-22842.iso?checksum=md5%3Ac1f8c8325e88f4687eabc4c60a6c3fcb
    ==> vmware-iso: file://F:/SOFTWARE/SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-2_MLF_X21-22842.iso?checksum=md5%3Ac1f8c8325e88f4687eabc4c60a6c3fcb => F:/SOFTWARE/SW_DVD9_Win_Svr_STD_Core_and_DataCtr_Core_2016_64Bit_ChnSimp_-2_MLF_X21-22842.iso
    ==> vmware-iso: Configuring output and export directories...
    ==> vmware-iso: Creating floppy disk...
        vmware-iso: Copying files flatly from floppy_files
        vmware-iso: Copying directory: F:\packer_1.7.8_windows_amd64/setup/
        vmware-iso: Adding file: F:\packer_1.7.8_windows_amd64\setup\Autounattend.xml
        vmware-iso: Adding file: F:\packer_1.7.8_windows_amd64\setup\vmtools.cmd
        vmware-iso: Done copying files from floppy_files
        vmware-iso: Collecting paths from floppy_dirs
        vmware-iso: Resulting paths from floppy_dirs : []
        vmware-iso: Done copying paths from floppy_dirs
        vmware-iso: Copying files from floppy_content
        vmware-iso: Done copying files from floppy_content
    ==> vmware-iso: Creating required virtual machine disks
    ==> vmware-iso: Building and writing VMX file
    ==> vmware-iso: Starting virtual machine...
    ==> vmware-iso: Connecting to VNC...
    ==> vmware-iso: Waiting 10s for boot...
    ==> vmware-iso: Typing the boot command over VNC...
    ==> vmware-iso: Waiting for WinRM to become available...
        vmware-iso: WinRM connected.
    ==> vmware-iso: Connected to WinRM!
    ==> vmware-iso: Provisioning with windows-shell...
    ==> vmware-iso: Provisioning with shell script: C:\Users\ADMINI~1\AppData\Local\Temp\windows-shell-provisioner3568001239
        vmware-iso:
        vmware-iso: C:\Users\vagrant>dir c:\
        vmware-iso:  Volume in drive C is Windows 2016
        vmware-iso:  Volume Serial Number is 5834-E616
        vmware-iso:
        vmware-iso:  Directory of c:\
        vmware-iso:
        vmware-iso: 2016/09/12  20:45    <DIR>          Logs
        vmware-iso: 2016/07/16  21:23    <DIR>          PerfLogs
        vmware-iso: 2016/09/12  20:45    <DIR>          Program Files
        vmware-iso: 2016/07/16  21:23    <DIR>          Program Files (x86)
        vmware-iso: 2021/12/21  19:51    <DIR>          Users
        vmware-iso: 2021/12/21  19:51    <DIR>          Windows
        vmware-iso:                0 File(s)              0 bytes
        vmware-iso:                6 Dir(s)  53,062,762,496 bytes free
    ==> vmware-iso: Forcibly halting virtual machine...
        vmware-iso: Waiting for VMware to clean up after itself...
    ==> vmware-iso: Deleting unnecessary VMware files...
        vmware-iso: Deleting: output-vmware-iso\vm.scoreboard
        vmware-iso: Deleting: output-vmware-iso\vmware.log
    ==> vmware-iso: Compacting all attached virtual disks...
        vmware-iso: Compacting virtual disk 1
    ==> vmware-iso: Cleaning VMX prior to finishing up...
        vmware-iso: Unmounting floppy0 from VMX...
        vmware-iso: Disabling VNC server...
    ==> vmware-iso: Skipping export of virtual machine...
    Build 'vmware-iso' finished after 19 minutes 23 seconds.
    
    ==> Wait completed after 19 minutes 23 seconds
    
    ==> Builds finished. The artifacts of successful builds are:
    --> vmware-iso: VM files in directory: output-vmware-iso

完成后，我们可以看到新模板在 output-vmware-iso目录中可用：

您可能会想"对于Windows的普通安装来说，这是很多工作"，但是，这只是一个基本的例子。Packer具有"配置器"，它允许我们运行PowerShell脚本，将文件传输到VM以安装应用程序，甚至使用Puppet或Chef等配置管理工具。

注：需要使用VMware Workstation Pro，因为VMware Workstation Player中缺少一些需要的工具程序。并且安装VMware Workstation Pro后，要运行“虚拟网络编辑器”，确定后退出，以避免packer报错。

[Link 1]: https://www.packer.io/downloads.html
[VMware]: https://img-blog.csdnimg.cn/img_convert/b6de2e25363c9f7730732a621dcdc33c.png