通过MDT任务序列安装Citrix VDA
在Microsoft MDT中，如何根据上一个错误代码引用另一个任务序列？
尝试通过任务序列安装VDA。根据Citrix文档。
“如果返回代码为3，请重新启动计算机，然后将控件传递给SCCM任务3。” 这是怎么做的。以下来自Citrix文档。
使用SCCM的示例安装顺序 以下示例显示了安装序列。
SCCM任务1：通过重新启动机器来准备机器。
SCCM任务2：启动VDA安装。 将 /leet， /noreboot和 /noreSume选项添加到命令行选项中。 运行您选择的VDA安装程序（本地图像或最小安装程序之一）。 SCCM必须捕获返回代码。 如果返回代码为0或8，则安装已完成，并且需要重新启动。 如果返回代码为3，请重新启动计算机，然后将控件传递给SCCM TASK3。
SCCM任务3：继续VDA安装。 如果SCCM任务2未返回0或8，则必须在重新启动完成后继续安装。
SCCM任务3重复直到VDA安装程序返回0或8（表示成功的安装）或3（表示SCCM任务3必须重复）。将任何其他返回代码视为错误，SCCM Task3应报告错误并停止。 在大多数情况下，通过运行适当的VDA安装程序（Xendesktopvdasetup.exe）恢复VDA安装线参数。 （VDA安装程序使用安装程序的第一运行期间保存的参数。） 注意VDA安装程序的返回代码。 0或8：成功，安装完成，重新启动。 3：安装尚未完成。重新启动机器并重复SCCM任务3，直到返回0或8。将任何其他返回代码视为错误，而SCCM Task3应报告错误并结束。
In Microsoft MDT how to I reference another Task Sequence based on the previous Error code?
Trying to install VDA via Task Sequence. As per Citrix documentation.
"If a return code is 3, restart the machine and then pass control to SCCM TASK3."
How is that done. Below is from the Citrix Docs.
Example installation sequence using SCCM
The following example shows the installation sequence.
SCCM TASK1: Prepare the machine by restarting the machine.
SCCM TASK2:Start the VDA installation.
Add the /quiet, /noreboot, and /noresume options to your command line options.
Run the VDA installer of your choice (local image or one of the minimal installers).
SCCM must capture the return code.
If the return code is 0 or 8, the installation is complete, and a restart is needed.
If a return code is 3, restart the machine and then pass control to SCCM TASK3.
SCCM TASK3:Continue VDA installation.
If SCCM TASK2 does not return a 0 or 8, the installation must be continued after the restart completes.
SCCM TASK3 repeats until the VDA installer returns a 0 or 8 (indicating a successful installation), or 3 (indicating SCCM TASK3 must be repeated). Treat any other return code as an error, and SCCM TASK3 should report an error and stop.
Resume the VDA installation by running the appropriate VDA installer (XenDesktopVdaSetup.exe for most cases, or XenDesktopRemotePCSetup.exe if VDAWorkstationCoreSetup_XXXX.exe was used) from the location where it was copied (as described in Define the task sequence), with no command-line parameters. (The VDA installer uses the parameters it saved during the first run of the installer.)
Watch for the return code from the VDA installer.
0 or 8: Success, installation complete, restart required.
3: Installation is not complete. Restart the machine and repeat SCCM TASK3 until a 0 or 8 is returned. Treat any other return code as an error, and SCCM TASK3 should report an error and end.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
总的来说，在ts中，最后一步的返回代码保存在
_smstslastactionretcode（任务序列变量文档），因此您可以根据TS变量的值包含一个条件后，将其包含一步。您可能还需要将原始TS步骤标记为“继续错误”返回代码。
也就是说，作为一般信息，我不确定如何对这些Citrix说明做什么。对我来说，它的读者为：如果是0或8重新启动，如果重新启动也是3。而且，如果您在步骤2和3之间重新启动，则“最后执行”可能是重新启动，因此您必须将这些内容放入组中。 （我个人认为，如果供应商的设置缺乏鲁棒性，那么TS设置可以提供解决此问题的复杂性，这也有点荒谬。我宁愿尝试将我的系统纳入返回的状态价值永远不会是3（无论是什么意思，可能在之前重新启动吗？），然后有99％的系统返回0并用手修复我的1％。通过该方法完美地修复（如果他们知道如何修复它为什么失败？）和“重复SCCM task3直到返回0或8”的指令向我读到，好像它只会导致某些机器进入无限循环有一次...
In general in a TS the return code of the last step is saved in
_SMSTSLastActionRetCode(Task sequence variables documentation)So you can include a step afterwards with a condition based on the value of the TS variable. You will probably also need to mark the original TS step as "Continue on Error" because I think any return code other than 0 (and maybe 3010) is treated as error and only on a "Run Command Line" step you can specify different allowed return codes.
That being said as general information I am not sure what to make of those citrix instructions. To me it reads as: If it is 0 or 8 reboot if it is 3 reboot as well. And if you have a reboot between Step 2 and 3 the "Last Execution" might be the reboot so it could be that you have to put that stuff in a group. (Also it is in my personal opinion a little bit ridiculous to think if a vendor has a setup that lacking in robustness that a TS setup can offer the complexity to fix this. I would rather try to get my systems into a state where the return value can never be 3 (whatever that means, probably rebooting before?) and then have 99% system returning 0 and fix my 1% by hand. MY feeling would be that if there can really be that many failures they might also not always be perfectly remedied by that method (if they know how to fix it why does it fail?) and the instruction "repeat SCCM TASK3 until a 0 or 8 is returned" to me reads as if it will only lead to some machine entering an infinite loop at one point...