Browsed by
Tag: vra

vRealize Automation 7 Installation – minimal deployment

vRealize Automation 7 Installation – minimal deployment

Ones might find it quite difficult to installa new product for the first time. Even though they installed previous version in the past (or particularly because of that!) That’s due to changes in requirements or event different structures of wizard form which requires information in different format. E.g domain administator accound in one version is required in administrator@domain.local format whils in other installation it accepts only domain\administrator format.

Thanks to that I’m going to provide the list of basic steps to install vRealize Automation 7 in minimal deployment.

I assume that you have successfully deployed the vRA appliance and prepared IaaS VM.

  1. I suggest to perform the initial configuration from IaaS VM which will be helpful during IaaS components installation during the process. After accessing the vRA appliance console at port 5480 providing default password, the wizard will start. At this stage you can choose the deployment type. Below you can see description of enterprise deployment. I will choose minimal deployment for now, though. It’s

vrainstall2 vrainstall3

2. Now it’s high time to prepare IaaS server for installation of IaaS components. In vRA 7.x it is much more simplier and faster process. You simply need to install the agent to let the wizard  discover the server and perform necessary steps then.vrainstall4

3. Here you can see that the server is discovered and you can move forward.vrainstall5

4. Next step is to check all the prerequisities and fix them if necessary.vrainstall6

5. Here you can see that there is a lot work to do on a freshly  installed Windows Server.vrainstall7

6. Furtunatelly the wizard will do the job by itself. That’s the time for short break 😉 It takes approximately 15 minutes to perform all steps.vrainstall87. When all tasks are done you can re-run the verification script to confirm that everything is fine and move to the next step.

vrainstall9

8. Provide the FQDN of vRA VM.vrainstall10

9. Here you are going to create a password which will be used by the system administrator account.

vrainstall11

10. Next step is to provide IaaS information, and here is the time to use domain\username format for IaaS Administrator account which should have local admin rights assigned.vrainstall12

11. Here you are going to provide information about the database server. I highly recommend to create new database. Keep in mind that IaaS administrator name which you provided in the previous step must have Sysadmin rights on Database Server. Without that the process will go forward. It will fail during the ending installation step, though. 
vrainstall14

12. For minimal or PoC deployment you can simply leave default values here.vrainstall15

13. The same as previous steps, leave it without changing. Just note the exact agent name which will be required during endpoint creation.vrainstall16

14. Provide the information for vRA self-signed certificates, untill you want to use custom ones.vrainstall17

15.  Provide the information for Web self-signed certificates, untill you want to use custom ones.

vrainstall18

16. Provide information for Manager service certificate.vrainstall19

17. Run the validation which might take about 10 minutes.
vrainstall21

18. Now it’s the time for some kind of backup in case something went wrong. I suggest to take snapshot of IaaS server just in case. Even though validation stage was completed successfully there are some issues which could happen during installation. (I’ve faced a failed installation due to lack of appropriate database permissions)vrainstall22

19. Next just start the installation.
vrainstall2320. If you didn’t miss anything your installation should be successfull 🙂
vrainstall25

21. Next you should provide the license key.vrainstall26

22. Deselect the VMware CEIP agreement checkbox.vrainstall27

23. You can also provide the password for initial config content. It’s expecially usefull in case of PoC installation. By clicking Create Initial Content button a blueprint for default automation on basic vRA configuration will be created and published in default tenant service catalog.

vrainstall28

24. After that you can will see the installation confirmation. Now you can start the play and begin the jurney with you vRA!
vrainstall29

Howto – Using Gmail as an Email server in vRalize Automation

Howto – Using Gmail as an Email server in vRalize Automation

Sometimes it is not possible to use corporation e-mail or deploy dedicated e-mail server expecially when it comes to a lab environment (and you are a little bit lazy like me to do it ;)). A workaround which I found is to configure my personal/fictional accounts profided by Gmail. It is more than enough in case you just want to see how notification or approval workflows work. It might not be enough if you want to deploy a little big bigger deployent with a few Business Groups and users, though. Of course there are plenty of other ways or small mail servers which you can deploy in a few minutes. I find gmail much more intuitive, though.

Anyway I’m going to show you how should Inbound and Outbound servers configurations look like.

Keep in mind the the outboud server is used to send notifications from vRA to users/managers etc. Inbound server is used to receive special kinds of notification by vRA from users. For instance when you are a Business Group Manager and you want to approve a request via e-mail without opening you vRA portal you can simply answer to the e-mail notification you received by clicking the hyperlink provided in that message. In this case you need to Inbound server configured.

Outboud Email configuration:

outbound

Inbound Email configuration:

Inbound

 

Note. Be aware that you have to change restiction policy on you Gmail account – you will receive an e-mail with detailed steps displaying the setting to change it after you click Test Connection in vRA’s e-mail configuration window.