Install VConnect RP
Ensure following install happens ONLY in the specific stamp identified to install the Resource Provider UI. Rest of the stamps are just connected to and installation of RP is not required.
HOST VM
On AzS Development Kits, sign in to the physical host.
On multi-node integrated systems, the host must be a system that can access admin and tenant endpoints.
Note: All steps in Prerequisites should be taken care before proceeding with the deployment steps below.
Open a new elevated (administrative) PowerShell console and change to the directory where the files have been extracted (c:\CloudAssert\VConnectMSM). Use a new window to avoid problems that might arise from incorrect PowerShell modules that are already loaded on the system. If you don't have this installer please reach out to our team and we will provide you with latest installer and trial license.
Ensure 2 certificate files (.pfx and .cer) [as in Prerequisites -> Certificate section] are present in the Cert folder as follows:
The file name must not contain any special characters
Only a *.cer and *.pfx exists in this Cert folder
The certificates must be placed in in this folder every time before retrying the deployment
3. Backup the Cert folder, in case we have to retry the deployment need the files to be replaced here
4. Run InstallVConnect.ps1 and specify the required parameters
Parameter Name | Description | Required |
DefaultProvider SubscriptionId | Go to Admin Portal -> Login as Service Admin -> Subscriptions -> Default Provider Subscription -> Get the GUID | Required |
AdminArm Endpoint | Admin ARM endpoint URL | Required |
ServiceAdminDirectory TenantName | Directory tenant name Of the service admin user | Required |
ServiceAdmin | Go to Admin Portal -> Login as Service Admin -> Subscriptions -> Default Provider Subscription -> Check if role is Owner Eg: admin@contosotest.onmicrosoft.com | Required |
ServiceTenantDirectory TenantName | Directory tenant name Of the service tenant user. If not provided, ServiceAdminDirectoryTenantName will be used | Optional |
Tenant SubscriptionId | GUID of the Tenant Subscription where Cloud Assert components need to be deployed | Required |
ServiceTenant | Tenant Subscription administrator account login user name. If not provided above ServiceAdmin credential can be used. | Optional |
VmLocal AdminPass | Password for the new VM that will host the resource provider IIS components. The user name is .\vconnectrpadmin. | Required |
PfxPassword | Password for azure stack .pfx file in Step 2 | Required |
SqlServerName | IP Address. Specify instance if exists. Eg: 192.168.102.32 | Required |
SqlDbName | Friendly name Eg: CloudAssert.VConnect | Required |
SqlUser | SQL Server authentication user name Eg: cadbadmin | Required |
SqlPass | SQL server sa admin credential password | Required |
ConfigureMsm | For Multi Stamp Management components installation, set this value as true | |
SetupBilling AndDacm | For Multi Stamp Management components installation, set this value as true in case Billing MSM is not installed already. | Required |
BillingApiUserName | Local Web user that will be created and used to access the Cloud Assert Billing API service. Eg: apiadmin | Required |
BillingApi Password | Password for above BillingApiUser | Required |
BillingDatabase Name | Billing database name Eg: cloudassert.billing | Required |
DacmDatabase Name | DACM database name Eg: cloudassert.dacm | Required |
Disconnected | If the AzS environment this RP is getting installed is in disconnected mode, pass value $True. For normal connected deployments this parameter is optional. | Optional |
Uninstall | For installation, no need to pass this parameter. For un-install, set it to true to un-install VConnect. | Optional |
5. Window will be prompted to get the password for the service admin and service tenant if the service tenant user is specified.
6. A pop up will appear with end user license agreement, once reviewed click Accept. The installation will continue and complete once all steps succeed.
This RP deployment step for a Multi node environment may take 60-75 minutes to complete. For ASDK, it may take 90 - 100 minutes.
Verify deployment in Azure Stack Portals
In Admin Portal -> Resource Groups, Select the system.[location].cloudassert.vconnect resource group and verify if the deployment succeeded.
In Tenant Portal -> Resource Groups, Select the system.[location].cloudassert.vconnect.rp resource group and verify if the deployment succeeded.
In SQL Database Server, ensure the databases CloudAssert.VConnect, CloudAssert.Billing and CloudAssert.Dacm are populated with tables
In Resource Provider VM, verify necessary web sites are installed:
Go to Tenant Portal -> All Resources -> VConnectVM1000 -> Overview -> DNS Name (last item)
Copy the value and remote into this resource provider VM
User name: vconnectrpadmin, Password: as specified in the above installation step
Go to inetmgr, ensure following 5 custom web sites are present
In the same Resource Provider VM, go to Control Panel -> Programs -> Programs and Features -> verify 3 services DACM (Cost Management agent service), Billing API and VConnect API exist and are running properly
If any of the above verification steps fail, reach out to us to fix the issues and retry the InstallVConnect.ps1 following instructions below
If all verification steps passed, proceed to License Activation
Retry instructions
In case this step of the deployment needs to be re-run:
Perform Step 2 in the above install instructions to place the certificate files in the appropriate folder in the install path
Run InstallVConnect.ps1 and specify the required parameters
Last updated
