powershell - 适用于 ARM 的 Azure DSC 扩展，powershell 脚本不会更新-6ren

powershell - 适用于 ARM 的 Azure DSC 扩展，powershell 脚本不会更新

转载作者：行者123 更新时间：2023-12-03 05:58:19

我在获取 DSC 扩展以更新 Azure 中 ARM 配置的 VM 上的资源时遇到问题。

这是我正在使用的 ARM 模板资源:

{
      "name": "[concat(parameters('vmName'),'/dscExtension')]",
      "type": "Microsoft.Compute/virtualMachines/extensions",
      "location": "[resourceGroup().location]",
      "apiVersion": "[variables('apiVersion')]",
      "dependsOn": [
        "[concat('Microsoft.Compute/virtualMachines/', parameters('vmName'))]"
      ],
      "tags": {
        "displayName": "Desired State Configuration"
      },
      "properties": {
        "publisher": "Microsoft.Powershell",
        "type": "DSC",
        "typeHandlerVersion": "2.9",
        "autoUpgradeMinorVersion": true,
        "forceUpdateTag": "1.012",
        "settings": {
          "wmfVersion": "latest",
          "modulesUrl": "[concat(parameters('_artifactsLocation'), '/', parameters('DSCConfigurationFile'))]",
          "sasToken": "[parameters('_artifactsLocationSasToken')]",
          "configurationFunction": "[parameters('DSCConfigurationFunction')]",
          "properties": {
          }
        },
        "protectedSettings": { }
      }
    }
  ],
  "outputs": {
  }

我已经尝试过Update the LocalConfigurationManager和 Using the forceUpdateTag ——这两个选项似乎都没有效果。

这是 CommandExecution.log

[05/09/2016 20:17:00.25] Executing: C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\bin\enable.cmd 
[05/09/2016 20:17:02.08] Execution Complete.
######
Execution Output:
Waiting for install to complete...
Install completed.
C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0>powershell.exe -NoProfile -NonInteractive -ExecutionPolicy RemoteSigned -File C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\bin\enable.ps1 -StartAsyncProcess  0<nul 
VERBOSE: [2016-05-09T20:17:01] Retrieving status of current request...
VERBOSE: [2016-05-09T20:17:02]     Sequence Number     : 0
VERBOSE: [2016-05-09T20:17:02]     Previous Sequence   : 0
VERBOSE: [2016-05-09T20:17:02]     RebootPending       : False
VERBOSE: [2016-05-09T20:17:02]     RebootNodeIfNeeded  : False
VERBOSE: [2016-05-09T20:17:02]     UseExisting         : False
VERBOSE: [2016-05-09T20:17:02]     State               : Completed
VERBOSE: [2016-05-09T20:17:02] The request for Sequence Number 0 was already processed; will exit.
C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0>exit 0 


Execution Error:

######
Command C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\bin\enable.cmd of Microsoft.Powershell.DSC has exited with Exit code: 0
Plugin (name: Microsoft.Powershell.DSC, version: 2.17.0.0) completed successfully.

值得注意的是，有多个 commandexecution*.log 文件正在输出，每个部署一个，但只有 1 个 DscExtensionHandler*.log

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----         5/9/2016   8:17 PM           1331 CommandExecution.log
-a----         5/9/2016   8:15 PM           1331 CommandExecution_12.log
-a----         5/9/2016   8:12 PM           1331 CommandExecution_11.log
-a----         5/9/2016   8:09 PM           1331 CommandExecution_10.log
-a----         5/9/2016   8:07 PM           1331 CommandExecution_9.log
-a----         5/9/2016   8:05 PM           1331 CommandExecution_8.log
-a----         5/9/2016   8:03 PM           1331 CommandExecution_7.log
-a----         5/9/2016   8:01 PM           1331 CommandExecution_6.log
-a----         5/9/2016   7:59 PM          24686 DscExtensionHandler.0.20160509-195436.log
-a----         5/9/2016   7:54 PM           2305 CommandExecution_5.log

这是最新的 DscExtensionHandler*.log

(C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\Status\0.status)
    VERBOSE: [2016-05-09T19:54:58] Get-DscLocalConfigurationManager: 

    ActionAfterReboot              : ContinueConfiguration
    AgentId                        : E3E292F1-161F-11E6-80C8-000D3A3076AA
    AllowModuleOverWrite           : False
    CertificateID                  : 
    ConfigurationDownloadManagers  : {}
    ConfigurationID                : 
    ConfigurationMode              : ApplyAndMonitor
    ConfigurationModeFrequencyMins : 15
    Credential                     : 
    DebugMode                      : {All}
    DownloadManagerCustomData      : 
    DownloadManagerName            : 
    LCMCompatibleVersions          : {1.0, 2.0}
    LCMState                       : Idle
    LCMStateDetail                 : 
    LCMVersion                     : 2.0
    StatusRetentionTimeInDays      : 10
    PartialConfigurations          : 
    RebootNodeIfNeeded             : False
    RefreshFrequencyMins           : 30
    RefreshMode                    : PUSH
    ReportManagers                 : {}
    ResourceModuleManagers         : {}
    PSComputerName                 : 

    VERBOSE: [2016-05-09T19:54:58] Executing Start-DscConfiguration...
    VERBOSE: [2016-05-09T19:54:58] Settings handler status to 'transitioning' 
    (C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\Status\0.status)
    VERBOSE: [2016-05-09T19:54:58] [VERBOSE] Perform operation 'Invoke CimMethod' with following parameters, ''methodName' = 
    SendConfigurationApply,'className' = MSFT_DSCLocalConfigurationManager,'namespaceName' = 
    root/Microsoft/Windows/DesiredStateConfiguration'.
    VERBOSE: [2016-05-09T19:54:58] [VERBOSE] An LCM method call arrived from computer WB01 with user sid S-1-5-18.
    VERBOSE: [2016-05-09T19:54:58] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]
    VERBOSE: [2016-05-09T19:54:59] [VERBOSE] [WB01]:                            [DSCEngine] Importing the module 
    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DscResources\MSFT_RoleResource\MSFT_RoleResource
    .psm1 in force mode.
    VERBOSE: [2016-05-09T19:54:59] [VERBOSE] [WB01]:                            [DSCEngine] Importing the module 
    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DscResources\MSFT_ScriptResource\MSFT_ScriptReso
    urce.psm1 in force mode.
    VERBOSE: [2016-05-09T19:54:59] [VERBOSE] [WB01]:                            [DSCEngine] Importing the module 
    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DscResources\MSFT_PackageResource\MSFT_PackageRe
    source.psm1 in force mode.
    VERBOSE: [2016-05-09T19:54:59] [VERBOSE] [WB01]:                            [DSCEngine] Importing the module 
    C:\Windows\system32\WindowsPowerShell\v1.0\Modules\PSDesiredStateConfiguration\DscResources\MSFT_ServiceResource\MSFT_ServiceRe
    source.psm1 in force mode.
    VERBOSE: [2016-05-09T19:54:59] [VERBOSE] [WB01]:                            [DSCEngine] Importing the module C:\Program 
    Files\WindowsPowerShell\Modules\xWebAdministration\1.10.0.0\DscResources\MSFT_xWebsite\MSFT_xWebsite.psm1 in force mode.
    VERBOSE: [2016-05-09T19:55:00] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[File]textfile]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[File]textfile]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]textfile] The system cannot find the file 
    specified.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]textfile] The related file/directory is: 
    C:\dsc.txt.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[File]textfile]  in 0.0310 seconds.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]  [[File]textfile]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]textfile] The system cannot find the file 
    specified.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]textfile] The related file/directory is: 
    C:\dsc.txt.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ End    Set      ]  [[File]textfile]  in 0.0000 seconds.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ End    Resource ]  [[File]textfile]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[File]HangfireDirectory]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[File]HangfireDirectory]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]HangfireDirectory] The system cannot find 
    the file specified.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]HangfireDirectory] The related 
    file/directory is: C:\inetpub\wwwroot\Onf.Web.Hangfire.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[File]HangfireDirectory]  in 0.0150 seconds.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]  [[File]HangfireDirectory]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]HangfireDirectory] The system cannot find 
    the file specified.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[File]HangfireDirectory] The related 
    file/directory is: C:\inetpub\wwwroot\Onf.Web.Hangfire.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ End    Set      ]  [[File]HangfireDirectory]  in 0.0940 seconds.
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ End    Resource ]  [[File]HangfireDirectory]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[WindowsFeature]IIS]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[WindowsFeature]IIS]
    VERBOSE: [2016-05-09T19:55:01] [VERBOSE] [WB01]:                            [[WindowsFeature]IIS] Importing the module 
    MSFT_RoleResource in force mode.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[WindowsFeature]IIS] The operation 
    'Get-WindowsFeature' started: Web-Server
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[WindowsFeature]IIS] The operation 
    'Get-WindowsFeature' succeeded: Web-Server
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[WindowsFeature]IIS]  in 1.3380 seconds.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Skip   Set      ]  [[WindowsFeature]IIS]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ End    Resource ]  [[WindowsFeature]IIS]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[WindowsFeature]ApplicationInitialization]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[WindowsFeature]ApplicationInitialization]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[WindowsFeature]ApplicationInitialization] 
    Importing the module MSFT_RoleResource in force mode.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[WindowsFeature]ApplicationInitialization] The 
    operation 'Get-WindowsFeature' started: Web-AppInit
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[WindowsFeature]ApplicationInitialization] The 
    operation 'Get-WindowsFeature' succeeded: Web-AppInit
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[WindowsFeature]ApplicationInitialization]  in 
    0.2500 seconds.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Skip   Set      ]  [[WindowsFeature]ApplicationInitialization]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ End    Resource ]  [[WindowsFeature]ApplicationInitialization]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[Script]DownloadWebDeploy]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[Script]DownloadWebDeploy]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[Script]DownloadWebDeploy] Importing the module 
    MSFT_ScriptResource in force mode.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[Script]DownloadWebDeploy]  in 0.0930 seconds.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]  [[Script]DownloadWebDeploy]
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[Script]DownloadWebDeploy] Importing the module 
    MSFT_ScriptResource in force mode.
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[Script]DownloadWebDeploy] Performing the 
    operation "Set-TargetResource" on target "Executing the SetScript with the user supplied credential".
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[Script]DownloadWebDeploy] GET 
    http://download.microsoft.com/download/0/1/D/01DC28EA-638C-4A22-A57B-4CEF97755C6C/WebDeploy_amd64_en-US.msi with 0-byte 
    payload
    VERBOSE: [2016-05-09T19:55:02] [VERBOSE] [WB01]:                            [[Script]DownloadWebDeploy] received 5951488-byte 
    response of content type application/octet-stream
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]: LCM:  [ End    Set      ]  [[Script]DownloadWebDeploy]  in 0.7570 seconds.
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]: LCM:  [ End    Resource ]  [[Script]DownloadWebDeploy]
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[Package]InstallWebDeploy]
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[Package]InstallWebDeploy]
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Importing the module 
    MSFT_PackageResource in force mode.
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] 
    Validate-StandardArguments, Path was C:\WindowsAzure\WebDeploy_amd64_en-US.msi
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] The path extension was 
    .msi
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Parsing 
    {ED4CC1E5-043E-4157-8452-B5E533FE2BA1} as an identifyingNumber
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Parsed 
    {ED4CC1E5-043E-4157-8452-B5E533FE2BA1} as {ED4CC1E5-043E-4157-8452-B5E533FE2BA1}
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Ensure is Present
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] product installation 
    cannot be determined
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] product as boolean is 
    False
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] The package Microsoft 
    Web Deploy 3.6 is not installed
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[Package]InstallWebDeploy]  in 0.0930 seconds.
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]  [[Package]InstallWebDeploy]
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Importing the module 
    MSFT_PackageResource in force mode.
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] 
    Validate-StandardArguments, Path was C:\WindowsAzure\WebDeploy_amd64_en-US.msi
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] The path extension was 
    .msi
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Parsing 
    {ED4CC1E5-043E-4157-8452-B5E533FE2BA1} as an identifyingNumber
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Parsed 
    {ED4CC1E5-043E-4157-8452-B5E533FE2BA1} as {ED4CC1E5-043E-4157-8452-B5E533FE2BA1}
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Ensure is Present
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] product installation 
    cannot be determined
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] product as boolean is 
    False
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] The package Microsoft 
    Web Deploy 3.6 is not installed
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] 
    Validate-StandardArguments, Path was C:\WindowsAzure\WebDeploy_amd64_en-US.msi
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] The path extension was 
    .msi
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Parsing 
    {ED4CC1E5-043E-4157-8452-B5E533FE2BA1} as an identifyingNumber
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Parsed 
    {ED4CC1E5-043E-4157-8452-B5E533FE2BA1} as {ED4CC1E5-043E-4157-8452-B5E533FE2BA1}
    VERBOSE: [2016-05-09T19:55:03] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Package configuration 
    starting
    VERBOSE: [2016-05-09T19:55:06] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Starting 
    C:\Windows\system32\msiexec.exe with /i "C:\WindowsAzure\WebDeploy_amd64_en-US.msi" /quiet /quiet ADDLOCAL=ALL
    VERBOSE: [2016-05-09T19:55:06] [VERBOSE] [WB01]:                            [[Package]InstallWebDeploy] Starting process 
    C:\Windows\system32\msiexec.exe with arguments /i "C:\WindowsAzure\WebDeploy_amd64_en-US.msi" /quiet /quiet ADDLOCAL=ALL
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ End    Set      ]  [[Package]InstallWebDeploy]  in 265.9510 seconds.
    VERBOSE: [2016-05-09T19:59:29] Settings handler status to 'transitioning' 
    (C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\Status\0.status)
    VERBOSE: [2016-05-09T19:59:29] [ERROR] PowerShell DSC resource MSFT_PackageResource  failed to execute Set-TargetResource 
    functionality with error message: The return code 1603 was not expected. Configuration is likely not correct 
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[Script]SetupWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[Script]SetupWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]:                            [[Script]SetupWebDeploy] Importing the module 
    MSFT_ScriptResource in force mode.
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[Script]SetupWebDeploy]  in 0.0150 seconds.
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ Skip   Set      ]  [[Script]SetupWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ End    Resource ]  [[Script]SetupWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[Service]StartWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[Service]StartWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]:                            [[Service]StartWebDeploy] Importing the module 
    MSFT_ServiceResource in force mode.
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]:                            [[Service]StartWebDeploy] Startup type for service 
    'WMSVC' is 'Manual'. It does not match 'Automatic'.
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[Service]StartWebDeploy]  in 0.0630 seconds.
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]  [[Service]StartWebDeploy]
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]:                            [[Service]StartWebDeploy] Importing the module 
    MSFT_ServiceResource in force mode.
    VERBOSE: [2016-05-09T19:59:29] [VERBOSE] [WB01]:                            [[Service]StartWebDeploy] Service 'WMSVC' already 
    exists. Write properties such as Status, DisplayName, Description, Dependencies will be ignored for existing services.
    VERBOSE: [2016-05-09T19:59:32] [VERBOSE] [WB01]: LCM:  [ End    Set      ]  [[Service]StartWebDeploy]  in 2.4770 seconds.
    VERBOSE: [2016-05-09T19:59:32] [ERROR] PowerShell DSC resource MSFT_ServiceResource  failed to execute Set-TargetResource 
    functionality with error message: Failure starting service 'WMSVC'. Please check the path 
    'C:\Windows\system32\inetsrv\wmsvc.exe' provided for the service. Message: 'Exception calling "WaitForStatus" with "2" 
    argument(s): "Time out has expired and the operation has not been completed."' 
    VERBOSE: [2016-05-09T19:59:32] [VERBOSE] [WB01]: LCM:  [ Start  Resource ]  [[xWebsite]CompanySite]
    VERBOSE: [2016-05-09T19:59:32] [VERBOSE] [WB01]: LCM:  [ Start  Test     ]  [[xWebsite]CompanySite]
    VERBOSE: [2016-05-09T19:59:32] [VERBOSE] [WB01]:                            [[xWebsite]CompanySite] Importing the module 
    MSFT_xWebsite in force mode.
    VERBOSE: [2016-05-09T19:59:36] [VERBOSE] [WB01]:                            [[xWebsite]CompanySite] The Ensure state for 
    website "hangfire.onfulfillment.com" does not match the desired state.
    VERBOSE: [2016-05-09T19:59:36] [VERBOSE] [WB01]:                            [[xWebsite]CompanySite] The target resource is not 
    in the desired state.
    VERBOSE: [2016-05-09T19:59:36] [VERBOSE] [WB01]: LCM:  [ End    Test     ]  [[xWebsite]CompanySite]  in 3.6200 seconds.
    VERBOSE: [2016-05-09T19:59:36] [VERBOSE] [WB01]: LCM:  [ Start  Set      ]  [[xWebsite]CompanySite]
    VERBOSE: [2016-05-09T19:59:36] [VERBOSE] [WB01]:                            [[xWebsite]CompanySite] Importing the module 
    MSFT_xWebsite in force mode.
    VERBOSE: [2016-05-09T19:59:36] [VERBOSE] [WB01]:                            [[xWebsite]CompanySite] Performing the operation 
    "Set Item" on target "Item: ConfirmPreference Value: High".
    VERBOSE: [2016-05-09T19:59:38] [VERBOSE] [WB01]: LCM:  [ End    Set      ]  [[xWebsite]CompanySite]  in 2.9560 seconds.
    VERBOSE: [2016-05-09T19:59:38] [ERROR] PowerShell DSC resource MSFT_xWebsite  failed to execute Set-TargetResource 
    functionality with error message: Failure to add certificate to web binding. Please make sure that the certificate thumbprint 
    "?XXXXXXX" is valid. Error: "Value does not fall within the expected range.". 
    VERBOSE: [2016-05-09T19:59:38] [VERBOSE] [WB01]: LCM:  [ End    Set      ]
    VERBOSE: [2016-05-09T19:59:38] [ERROR] The SendConfigurationApply function did not succeed.
    VERBOSE: [2016-05-09T19:59:38] [VERBOSE] Operation 'Invoke CimMethod' complete.
    VERBOSE: [2016-05-09T19:59:38] [VERBOSE] Time taken for configuration job to complete is 280.052 seconds
    VERBOSE: [2016-05-09T19:59:39] Settings handler status to 'transitioning' 
    (C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\Status\0.status)
    VERBOSE: [2016-05-09T19:59:39] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\ExecutionStatus)
    VERBOSE: [2016-05-09T19:59:39] DSC configuration completed.
    VERBOSE: [2016-05-09T19:59:39] Removing meta.mof and mof files...
    VERBOSE: [2016-05-09T19:59:39] Resetting metaconfiguration...
    0
    VERBOSE: [2016-05-09T19:59:39] Settings handler status to 'error' 
    (C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\Status\0.status)
    VERBOSE: [2016-05-09T19:59:40] Loading Event Source assembly for telemetry...
    VERBOSE: [2016-05-09T19:59:40] [Telemetry] Invoking [Configuration][End] event for telemetry.[Status]: Failure
    VERBOSE: [2016-05-09T19:59:40] Updating execution status (HKLM:\SOFTWARE\Microsoft\Azure\DSC\ExecutionStatus)
    VERBOSE: [2016-05-09T19:59:40] Transitioning to Completed state ...
    VERBOSE: [2016-05-09T19:59:40] Removing file 
    C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\bin\..\DSCWork\ExtensionHandler.Lock.0.dsc
    VERBOSE: [2016-05-09T19:59:40] Removing file 
    C:\Packages\Plugins\Microsoft.Powershell.DSC\2.17.0.0\bin\..\DSCWork\ExtensionHandler.Lock.dsc

上面的脚本来自较旧的部署(dsc 工件已更改)

最后，zip 文件引用似乎总是指向每次部署的相同位置:

{
  "runtimeSettings": [
    {
      "handlerSettings": {
        "protectedSettingsCertThumbprint": "XXXXXXXXXXXX",
        "protectedSettings": "XXXXXXX",
        "publicSettings": {"wmfVersion":"latest","modulesUrl":"https://XXXXXX.blob.core.windows.net/onf-storage-hangfire-artifacts/DSC6451f1662.zip","sasToken":"?sv=2015-04-05&sr=c&sig=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX%3D&se=2016-05-09T23%3A52%3A43Z&sp=r","configurationFunction":"ConfigureWebServer.ps1\\Main","properties":{}}
      }
    }
  ]
}

到目前为止唯一成功的选择是删除虚拟机并从头开始

想法？提前致谢!

最佳答案

每次部署此模板时，您都必须更新“forceUpdateTag”的值，否则请求将被忽略。如果您每次都更新“forceUpdateTag”但仍然没有任何反应，请从虚拟机收集日志并共享。日志收集工具可用@https://github.com/PowerShell/xDscDiagnostics

关于powershell - 适用于 ARM 的 Azure DSC 扩展，powershell 脚本不会更新，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/37120522/

文章推荐： javascript - 删除动态添加的字段时出错

文章推荐： meteor - 如何取消部署 meteor 应用程序？

文章推荐： javascript - Angular $uibmodal 异步解析

文章推荐： visual-studio-2010 - Visual Studio 不允许我将项目拖放到其中？

powershell - 实现 PowerShell PSProvider *in* PowerShell
我正在寻找实现 PowerShell 提供程序在电源外壳。我一直在想，如果我只是定义类型，然后将它们导入我的 session (导入模块)，我应该能够让它们可用。例如，这个不工作但它沿着我想
powershell - Powershell:与x86 powershell/ise一起运行的脚本
我创建的脚本使用了组件，这些组件仅在32位版本的Powershell中可用。默认情况下，Windows使用Powershell x64执行脚本，这会导致一些错误。是一种在脚本开头设置值以强制Win
powershell - 如何检测 Powershell 中的 Powershell 嵌套？
是否可以从 Powershell 中检测它是否是嵌套 shell？如果我打开 Powershell 或 cmd.exe 窗口，然后输入 powershell 在那里，是否有一个神奇的 $host.s
powershell - 如何为同一台机器自动化 PowerShell 或 PowerShell Core
随着 PowerShell Core 的发布，应用程序在使用托管自动化库 (system.management.automation) 时如何选择调用哪个版本的 Powershell(Powershe
powershell - 如何在企业中使用 PowerShell 和 PowerShell 模块
最近，我加入了我企业的 Windows 团队，凭借我的开发人员背景(一般是 Java、.NET 和 Web)，我很快就对 PowerShell 产生了兴趣。我可以看到它比普通的旧批处理文件、VB 更有
powershell - 如何在另一个 powershell 脚本中包含另一个 powershell 脚本文件？
假设我有一个 powershell 脚本，它在我当前路径的相对路径中包含一个 Powershell 哈希。让我们称之为“name.ps1”，它包含: $names = @{ "bob" = "b
powershell - 为 Powershell 模块添加 Powershell 管理单元并多次导入
我想为我正在构建的自定义 Powershell Commandlet 使用 SqlServerCmdletSnapin。如果我将以下代码添加到 PSM1 的开头: if ( (Get-PSSnapin
powershell - 使用来自另一个 powershell 脚本的参数调用 PowerShell 脚本
如何调用从 PowerShell 脚本中获取命名参数的 PowerShell 脚本？ foo.ps1: param( [Parameter(Mandatory=$true)][String]$a=''
powershell - 何时选择开发 PowerShell 模块而不是 PowerShell 脚本
我即将为 Windows 管理员编写一个 PowerShell 脚本，以帮助他们完成与部署 Web 应用程序相关的某些任务。有什么理由让我应该赞成或排除开发 PowerShell 模块 (.psm1
powershell - 如何在不关闭 powershell 控制台的情况下从 Powershell 模块函数返回非零退出代码？
我的 powershell 模块有一个函数，我希望它返回一个非零退出代码。但是，作为一个模块函数，当我运行 Import-Module 时，它会加载到 powershell 控制台的上下文中。所以，当
powershell - 使用参数从 powershell 中调用 powershell 脚本时遇到问题
我在这个问题上花了最后 4 个小时，非常感谢您提供的任何意见。我需要使用不同的凭据调用 powershell 脚本并将参数传递给该脚本。安装 WISEScript 中包装的程序后，此脚本开始收集机
powershell - 有没有办法让我在 powershell 运行时以编程方式获取 Powershell 输入和输出？
我有一个场景，我需要将 powershell 命令的命令和输出转发到另一个进程以进行日志记录和处理。我希望这个控制台尽可能接近 powershell，因此不希望将它简单地托管在另一个控制台程序中。
powershell - 在 PowerShell 脚本中调用其他 PowerShell 脚本
我正在尝试让一个主 PowerShell 脚本运行所有其他脚本，同时等待 30-60 秒以确保完成任务。我尝试过的所有其他操作都不会停止/等待第一个脚本及其进程完成，然后才能同时完成所有其他脚本，并且
powershell - 如何从 Powershell 打开 Powershell 控制台窗口
我正在编写一个脚本来使用多个 plink (PuTTY) session 作为 Windows 版本的 clustersh。然而，我陷入困境，因为我想从 powershell 打开多个 Powersh
powershell - 如何从 Powershell 运行 Powershell x86？
我读了这个答案:How to Open Powershell from Powershell start powershell 这将打开基础的大分辨率 PS 实例。如何打开 PS(x86)？最佳答案
powershell - 我可以在 PowerShell 退出时将 PowerShell 历史记录写入文本文件吗？
我很想知道我们是否可以在 Powershell 中做到这一点。使用 Out-File 命令，我们可以通过管道将其输出写入文件。这样我就可以将我所有的历史命令发送到一个文本文件中。问题是我可以在每次
powershell - Powershell 中的管道
我在 about_Pipelines 阅读了有关 PowerShell 中的管道工作原理的信息，并了解到管道一次传送一个对象。所以，这个 Get-Service | Format-Table -Pr
powershell - powershell 启动过程出错
我正在尝试像这样从 powershell 启动一个进程:- $proc = (start-process $myExe -argumentList '/myArg True' -windowStyle
powershell - 表达式或语句中的意外标记 - powershell
## To run the script # .\get_status.ps1 -Hostname -Service_Action -Service_Name #$Hostname = "hos
powershell - Powershell 输出的自定义字体颜色
让我们使用 powershell 命令 Write-Host "red text"-Fore red这会在红色前景中显示“红色文本”。但是，您希望文本以稍微亮一点的方式显示字体颜色，浅红色。有没有

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

powershell - 适用于 ARM 的 Azure DSC 扩展，powershell 脚本不会更新