如何在LG android移动版4.0中运行我的android程序？(How can i run my android program in LG android mobile version 4.0? [closed])

 不幸的是，Ansible不会在这种情况下帮助你。 
 
 最好的方法是使用相同的参数单独调试DSC部件。 在这种情况下，它很糟糕，因为这是一个很大的问题。 如果成功，您将设置CA. 如果可以的话，为了理智，可以部署一个可以继续拆卸和提升的测试环境。 
 
 如果你很幸运，你会发现Test方法中没有任何改变的问题。 
 
 第一步，转到运行win_dsc的主机上。 打开PowerShell。 
 
 创建一个包含DSC模块所有参数的[hashtable] ，如下所示： 
 
if (-not $cred) {
    $cred = Get-Credential # maybe just run this once in your session?
}

$params = @{
    IsSingleInstance = $true
    CAType = 'EnterpriseRootCA'
    CryptoProviderName = 'RSA#Microsoft Software Key Storage Provider'
    KeyLength = 2048
    HashAlgorithmName = 'SHA256'
    ValidityPeriod = 'Years'
    ValidityPeriodUnits = 99
    PsDscRunAsCredential = $cred
}
 
 接下来，直接调用DSC资源，让我们使用Test方法： 
 
Invoke-DscResource -Name AdcsCertificationAuthority -ModuleName ActiveDirectoryCSDsc -Property $params -Verbose -Method Test
 
 看看它吐出来的是什么。 它可能会因类似的错误而失败。 希望它能做到。 如果没有，请尝试使用Get方法，如果Set使用它但Test没有。 这不太可能，但如果可能的话，你想避免Set 。 
 
 如果所有运行顺利，请使用方法Set运行。 如果成功，请返回ansible并找出不同之处（用户ansible是否正在进行身份验证，因为它具有调用DSC的权限？）。 
 
 如果您在任何时候出现故障并希望深入挖掘，则可以调试实际的DSC调用。 这有点令人费解。 
 
 首先， Enable-DscDebug -BreakAll 。 
 
 接下来，打开一个单独的PowerShell ISE窗口（这是我的偏好，使事情变得更容易）。 然后，在同一原始窗口（而不是新的ISE窗口）中重新运行之前执行的Invoke-DscResource命令。 
 
 它将中断，它将为您提供一系列命令来运行以连接到调试会话。 该列表将包括Enter-PSHostProcess 。 在ISE窗口的终端中运行这些命令。 
 
 您将进入正在运行的DSC过程，您将看到该模块的源代码，并能够逐步完成它并找出出现了什么问题。 
 
 此时，您可能会发现您传递的参数不太正确，并且您可以通过调整它来修复调用。 那很好。 
 
 您可能会发现模块中存在错误，在这种情况下，您可以报告它，甚至提供带有拉取请求的修复程序; 这需要时间。 
 
 在此期间，您可以自己克隆模块并使用不符合PR要求的快速修复将其分发到您的服务器。 
 
 这里有很多可能性，但是如果你发现了实际的错误，它可能需要一个关于如何处理这个特定问题的新问题。 
 
 笔记 
 
 我发现在调试过程中，大约一半的时间连接到会话导致完全卡住的调试会话无效。 在这种情况下，使用他们给你的PID并终止进程。 无论如何，你可能必须在运行之间执行此操作，不要害怕它。 
 
 最后，在尝试再次使用DSC之前（例如来自Ansible）， 不要忘记禁用调试！ 
 
Disable-DscDebug
 
 （强烈建议您在禁用调试后终止进程） 

Ansible will not help you in this situation, unfortunately.
 
The best way to go is to debug the DSC part separately, with the same parameters. In this case, it kind of sucks because this is a big ask. If it succeeds, you're going to have your CA set up. If you can, deploy a test environment that you can keep tearing down and bringing up, for sanity's sake.
 
If you're lucky you'll find the problem in the Test method that doesn't change anything.
 
First step, go onto the host that you are running win_dsc against. Open PowerShell.
 
Create a [hashtable] that contains all of the parameters to your DSC module, so something like this:
 
if (-not $cred) {
    $cred = Get-Credential # maybe just run this once in your session?
}

$params = @{
    IsSingleInstance = $true
    CAType = 'EnterpriseRootCA'
    CryptoProviderName = 'RSA#Microsoft Software Key Storage Provider'
    KeyLength = 2048
    HashAlgorithmName = 'SHA256'
    ValidityPeriod = 'Years'
    ValidityPeriodUnits = 99
    PsDscRunAsCredential = $cred
}
 
Next, invoke the DSC resource directly, let's use the Test method:
 
Invoke-DscResource -Name AdcsCertificationAuthority -ModuleName ActiveDirectoryCSDsc -Property $params -Verbose -Method Test
 
See what it spits out. It will probably fail with a similar error. Hope that it does. If it doesn't, try the Get method in case Set uses it but Test doesn't. It's unlikely, but you want to avoid Set if possible.
 
If all that runs smoothly, run with method Set. If it succeeds, go back to ansible and figure out what's different (does the user ansible is authenticating as have permission to invoke DSC?).
 
If you get a failure at any point and want to dig deeper, you can debug the actual DSC invocation. It's a little convoluted.
 
First, Enable-DscDebug -BreakAll.
 
Next, open a separate PowerShell ISE window (this is my preference, makes things easier). Then, re-run the Invoke-DscResource command you did before, in the same original window (not the new ISE window).
 
It will break, and it will give you a series of commands to run to connect to the debug session. The list will include Enter-PSHostProcess. Run those commands in the terminal in the ISE window.
 
You'll be entered into the running DSC process, and you will see the source code of the module and be able to step through it and figure out what's going wrong.
 
At this point, you may find that a parameter you passed is not quite right, and that you can fix the invocation by tweaking it. That's good.
 
You may find there's a bug in the module, in which case you can report it or even offer a fix with a pull request; this will take time.
 
In the meantime, you can clone the module yourself and distribute it to your servers with a quick fix that wouldn't meet the requirements for a PR.
 
There's a lot of possibilities here but if you find the actual error it may warrant a new question as to how to deal with that specific problem.
 
Notes
 
I've found that during the debug process, about half the time connecting to the session leads to a complete stuck debug session that doesn't work. In that case, use the PID they gave you and kill the process. You may have to do this between runs anyway, don't be afraid of it.
 
And finally, before attempting to use DSC again (like from Ansible), don't forget to disable debugging!
 
Disable-DscDebug
 
(strongly encourage you to kill the process after disabling the debugging as well)