Enhanced Studio Pack on Azure

The Enhanced Studio Pack contains all the tools you need to do world-class development in a single, pre-configured environment. Use these instructions to deploy everything you need with the infrastructure required to support large projects, big files, and all your team members.

Helix Core Version Control

Helix Swarm Code Review

icon-products-hansoft-simple

Hansoft Project Management

Perforce Windows Workstations

Define Your Azure Environment

  1. To deploy your Enhanced Studio Pack on Azure, click on the template link in your email (you should receive one after signing up). It will open the Azure Portal Custom Deployment page after you log into your Azure Account.
    In the template, you will see steps on how to define your Perforce environment. Review each step and select or change options to customize your Perforce Enhanced Studio Pack.
     
  2. Define your parameters:
     

Subscription

You must have an existing subscription to deploy. An Azure account can contain multiple subscriptions.

  1. Select a subscription to host your Perforce Enhanced Studio Pack.
  2. New to Azure? Calculate your potential costs >>  

Resource Groups

When deploying on Azure, multiple resources will be created. This allows you to easily see what items are related to this deployment.

  1. Select an existing resource group or create a new one.
  2. We recommend creating a new resource group that will be specific to this deployment. If you create new, example name: perforce-${environment}-${team/department}

Region

  1. Select the region closest to your end users or a region that meets your compliance/security needs.

Environment

The Environment parameter is used in both resource naming and the tag on all resources.

  1. Environment default is “prod.” We do not recommend changing this name. But it can be done if your needs require it.

Virtual Network Configuration

  1. Use an existing Azure vNet or create a new one.
    We recommend creating a new one. Use your organization’s network naming convention.
  2. To start you must add at least one IP address. We recommend using the public IP address of the machine being used to set up the stack in Azure.
  3. Replace 1.1.1.1 with your IPv4 address. Find your IP address >>
    /32 will remain unless there is a continuous block of IP addresses that need to be whitelisted. You can always add and delete IP addresses after you deploy.

Configure Perforce Tools

Now that you have selected server parameters you can configure Perforce tools.

Perforce Server Configuration

Define how your Helix Core server will be setup.

  1. To set up SSH, upload an existing key or create a new one. Certain admin actions will require SSH access. For example: operating system updates, product updates, reviewing logs, or expanding volume size. Daily use will not require SSH.
  2. The remaining fields in this section can be left as the default. These values are intended to get you started. Depending on how you are utilizing the software and your specific use cases, you may need to increase or decrease. File size and number of files are the largest contributors.
    If you know how much data you are using today, you may consider adjusting your Depot Volume Size to 1.5x your current data usage.
  3. Just looking to deploy Helix Core? Skip ahead and click Launch Your Instance. Otherwise, continue to Configure Additional Tools.

Hansoft Configuration (Optional)

  1. To use the Hansoft project management tool, select ‘True’
  2. Hansoft will be deployed to your Azure environment on its own server. We do not recommend adjusting resource defaults for initial setup.

Not sure you will use Hansoft right away? Deploy now and pause the Hansoft server until you are ready to start using. This will reduce your cloud operating costs.

Swarm Configuration (Optional)

  1. To use the Perforce code review tool, select ‘True’
  2. Swarm will be deployed to your Azure environment on its own server. We do not recommend adjusting resource defaults for initial setup.

Not sure you will use Swarm right away? Deploy now and pause the Swarm server until you are ready to start using. This will reduce your cloud operating costs.

Virtualized Windows Workstation Configuration (Optional)

The virtual Windows workstation contains all the Perforce clients — Helix Sync, Helix Visual Client (P4V) — pre-configured. It also contains additional 3rd party tools and other powerful resources.

Instance size and your use of the software on the workstation will influence the cost of the server needed to support it.

  1. To use a pre-configured Windows Workstation, select ‘True’
  2. Select Resources:
    • Instance types supported are NV-series, NVv3-seriesNVv4-series. Prices will vary based on your selection.
    • Root volume size is highly dependent on your use case. How much data will you check out? How much hard drive space do you want? How much data will be stored?
    • These defaults will be good to get started and can be adjusted at any time.

Launch Your Instance

Once you have defined all parameters, click Launch Your Instance. We recommend keeping your deployment status page open to aid with post deployment configuration. Estimate your monthly expense with the Azure calculator.

Having issues deploying your instance on Azure? Email us >> [email protected]

Locate the Outputs Tab

After your Perforce deployment is complete, you will be on the Overview tab of your Parent Deployment. Please note the Parent Deployment will be named ‘Microsoft.Template-##############’, the hashes will be unique to your deployment.

Microsoft Template

From the sub-navigation of the Parent Deployment click on Outputs.

Microsoft Template

You are now located on the Outputs tab of the Parent Deployment. All outputs needed to connect to your Windows Workstation, Helix Core, Helix Swarm, and Hansoft instances will be located here.

If you navigated away from the deployment progress page you can get to the outputs tab by following the following instructions:

  1. From your Azure account, search for Research Groups. Click on Research Groups.
    Azure Search Account
  2. Click on the name of the Resource Group you created for your Perforce deployment. This will be a unique name you defined when filling out the template.
    Resource Group
  3. From the selected Resource Group sub-navigation menu, select Deployments.

    Resource Group
  4. Here you will see a list of all the Deployments associated with this Resource Group. Scroll to the bottom and click on the Deployment named ‘Microsoft.Template-##############’, the hashes will be unique to your deployment.

  5. You are now located on the Partent Deployment page. Click on Outputs in the sub-nav.

    Microsoft Template
  6. You are now located on the Outputs tab of the Parent Deployment. All outputs needed to connect to your Windows Workstation, Helix Core, Helix Swarm, and Hansoft instances will be located here.

Connect to Your Windows Workstation

After you have completed deployment, you can connect to your Windows Workstation via RDP:

  1. Open your RDP tool of choice.
     
  2. Enter the server you will connect to – value of the PerforceWorkstationPublicIP. Click Connect.
    Note: You can find the workstation server information on the Outputs tab of the Parent deployment. 
     
  3. Enter your Perforce Workstation Credentials
    Username: perforce
    Password: Value for PeforeceWorkstationInstanceID (located on the Outputs tab of the Parent Deployment)

 

Access Helix Visual Client via Windows Workstation

When accessing your workstation for the first time, you need to complete your configuration.

  1. Once you are logged in, a powershell displays. This window will close when the configuration is complete.
    Powershell
    Authenticate your workstation. The password for the server is the value from the P4CommitInstanceID found on the Outputs tab of the Parent Deployment. 
    Helix Core Password
  2. Open Helix Visual Client (P4V) from the desktop icon. In the Open Connection dialog, leave the defaults. Click Okay.

Access Helix Sync via Windows Workstation

Helix Sync allows you to drop and drag assets to securely version any digital asset.

  1. Open the HelixSync desktop icon.
     
  2. In the dialog box, enter your server and username. This is the same information used for Helix Visual Client (P4V). No password is required since you’ve already authenticated the workstation.
     
  3. Get started with Helix Sync.

Connect to Helix Swarm via Windows Workstation

  1. Open Google Chrome.
     
  2. From the bookmarks area or bookmarks bar, click on Helix Swarm. The Helix Swarm login page displays.
     
  3. Enter your credentials:
    Username:  perforce
    Password: P4CommitInstanceID (located on the Outputs tab of the Parent Deployment)
  1. Open connection instructions in Hansoft.txt file located on the workstation desktop.
     
  2. Open the Hansoft Client.
     
  3. Enter the Hansoft IP from the text file into the Hansoft server field of the Hansoft Client window.
     
  4. Enter the Hansoft Port into the Port field of the Hansoft Client window. Click Connect.

    NOTE: You may experience a time out error on your first attempt. Confirm the IP address and port are correct. Select Continue. Trust the server and download any additional versions of Hansoft that may be available.
     
  5. Enter in your credentials:
    Username: Administrator  
    Password: Hansoft VM Instance ID (Listed as HansoftInstanceID located in the on the Outputs tab of the Parent Deployment)

Configure Perforce Products Without Windows Workstation

You can access your Perforce Software without the Windows Workstation.

  1. To connect to Helix Core via Perforce clients, Helix Swarm, or Hansoft you need to use a public IP. These are located in the Outputs tab of the Parent Deployment and are listed as:
    • HansoftPublicIP
    • P4CommitPublicIP
    • SwarmPublicIP
       
  2. Download clients separately.
     
  3. Check out documentation to get started >>

Update Firewall Rules to Allow Additional Users Access

If you have users who will be connecting to Perforce from a different IP address than the one used to deploy the Enhanced Studio Pack, you need to update your firewall rules to grant them access. 

  1. Follow Azure’s instructions on creating a security rule in your network security group.
     
  2. Input a rule for each user/IP address:
     
    • Each user will need to provide you with their IP address in IPv4 format.
       
    • The table below provides the port number for each product the user may need access to:
       
      ProductService TypePort Number
      Helix CoreTCP1666
      Helix SwarmHTTP80
      HansoftTCP52560
      Windows WorkstationTCP3389

Want Help Setting Up Perforce?

Contact our professional services team to talk with our experts. They can optimize your Helix Core servers for top performance.

Do More With P4V

Setting Perforce is easy with our P4V cheat sheet.

Read the Docs

Get step-by-step instructions on how to install, administer, optimize, and use Helix Core.