Cloud Assert - Help Center

            Hybr Pre-Requisites

            HYBR Application Server 
            • Operating system: Windows Server 2012 / 2016  

            • RAM: 8 GB 

            • Processor: 64 bit, 4 Cores 

            • Hard disk: 100 GB for system drive  

            • Internet connectivity 

            • Web Server (IIS) installed on server machine with .Net Framework 4.7, ASP.Net 4.6 & relevant features 

            • PowerShell 5 or above 


            1. HYBR RP server  

            This is required only if VConnect / Billing related features needs to be installed. 

             

            • Operating system: Windows Server 2012 / 2016  

            • RAM: 12 GB 

            • Processor: 64 bit, 4 Cores 

            • Hard disk: 100 GB for system drive 

            • Internet connectivity 

            • Web Server (IIS) installed on server machine with .Net Framework 4.7, ASP.Net 4.6 & relevant features 

            • PowerShell 5 or above 

            • Static mac address should be assigned 

            1. HYBR Database server 

            • Operating system: Windows Server 2012 / 2016 

            • SQL Server 2016 / 2017  

            • RAM: 12 GB or more 

            • Hard disk: 100 GB for system drive 

            • Processor: 64 bit, 4 Cores 

            1. VConnect Service specific requirement 

            This is required only if you have opted for VConnect feature capability that helps you manage On-premise and Cloud data centers. This must be on application server where VConnect will be installed. 

            VMware vSphere PowerCLI (Supported Versions: 5.5 to 6.3 R1) 

            VMM 2012/2016 Console (Supported Versions: UR10) 

            AWS CLI (Supported Versions: 1.11.10 to 1.11.13) 

            Azure PowerShell (Supported Versions: 1.5 to 3.0) 

             

            1. PowerShell configurations  

            Run the following commands in Command prompt on the Application Server and use appropriate thresholds for your environment 

            • winrm set winrm/config/winrs @{MaxShellsPerUser="500"} 

            • winrm set winrm/config/client @{AllowUnencrypted="true"} 

            Run the following commands in the Windows Power Shell ISE on the Application server and use appropriate thresholds for your environment 

            • Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell\Quotas\MaxShells -Value 500 

            • Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell\Quotas\MaxShellsPerUser -Value 500 

            • Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell32\Quotas\MaxShells -Value 500 

            • Set-Item -Path WSMan:\localhost\Plugin\microsoft.powershell32\Quotas\MaxShellsPerUser -Value 500 

            • Restart-Service winrm 

            1. vSphere specific configuration 

            This is required for only for vCenter integration. 

            • Clusters that will be configured with VConnect must have DRS turned on in vCenter 

            • Ensure that VM Templates in the vCenter environment used for VM provisioning through VConnect, are created with only 1 core per socket and 1 CPU 

            1. WorkFlow SERVICE SPECIFIC REQUIREMENTS 

            Need not share the below details, but be ready with this for workflow configuration 

            Smtp and Imap settings: 

            • Host name 

            • Port number 

            • User name 

            • Password 

            1. Identity Providers 

             

            • Supports Azure Active Directory or ADFS 2016 

            • AAD Pre-requisites 

            • Use this only if cloud admin organization user accounts are maintained in AAD 

            • Refer AAD prerequisites document sent along with this document for steps to retrieve below information. 

            • Directory ID  

            • Application ID  

            • Application Client Secret  

            • AAD user account for Admin (this should belong to the same directory mentioned above) 

            • ‘User’ directory role is enough for admin user 

            • ADFS Pre-requisites 

            • Use this only if cloud admin organization user accounts are maintained in ADFS 

            • Application ID 

            • Application Client Secret 

            • Obtain Authority and Metadata address of ADFS 2016 

            • User account for admin 

            • ‘User’ directory role for admin user is suffice 

            1. Others 

            • Azure storage account. 

            • Standard storage account is


            Updated: 18 Jun 2019 11:12 PM
            Helpful?  
            Help us to make this article better
            0 0