vRealize Automation 7 (vRA 7)和vRA6比起来有很多增强和改进。网上有大量的文章介绍这方面以及安装方法。vRA7的初始设置和vRA6有很大不同。以下是我的一些经验,可以帮你快速搭建实验环境。
Access Deny When Run PowerShell Scripts
Access deny when run PowerShell script
Access deny when run PowerShell script
Disable default tab in Visual Studio
Validating connection result of Connect-VIServer is trick since VMware doesn’t use the standard way of throwing errors.
I built a simple Auto Deploy environment by vSphere 6.5 on nested environment. I created virtual ESXi hosts on a physical ESXi host to do the testing. The whole configuration was smoothly, I’m impressed Auto Deploy can be implemented in few hours. One thing bothered me was networking. New ESXi hosts cannot get IP addresses … Read more
vRealize Automation 7 (vRA 7)和vRA6比起来有很多增强和改进。网上有大量的文章介绍这方面以及安装方法。vRA7的初始设置和vRA6有很大不同。以下是我的一些经验,可以帮你快速搭建实验环境。
当创建虚拟机的时候你可能需要将虚拟机根据不同的属性放入不同的OU中,比如根据角色、组、用户组等。在vRealize Automation Center (vRA)中可以很轻易地创建一个下拉菜单实现这类属性的选择,但是这类属性的值往往都以字符串的形式传递到vRO中,而vRO的活动目录工作流中并没有提供字符串转OU对象的功能。
When you put virtual machine to particular OU, you may refer to virtual machine properties, such as ‘server role’, ‘server group’ or ‘user group’…etc. It’s easy to set a drop-list in blueprint of vRealize Automation Center (vRA) to let users choose this kind of properties but hard to create a computer account in corresponded OU location in vRO. That’s because vRA passes most of values to vRO as strings, Active Directory workflows in vRO do not provide a way to convert string to OU.
You almost can do everything as long as vRealize Automation Center (aka vRA) and vRealize Orchestrator (aka vRO) are integrated. I think that’s the hard part if you are newbie like me. After reading lot of articles, I learned how it works. Following is my experience, please let me know if you see anything wrong.
把vRA和vRO结合在一起几乎可以做任何事情。如果你和我一样是新手,和uijuede 得整合这块比较难,最近阅读了一些这方面的文章,算是有所了解了。以下是我的见解,如果有问题留言给我。