Custom Technology Solutions, Inc

Corporate Blog

Custom Technology Solutions, Inc - Corporate Blog

First ever SMB Cloud Summit starts to take shape

Preparations for our first ever Cloud Summit – first announced in this blog back in March – are gathering pace.  The summit will bring together our reseller and Managed Services Provider (MSP) partners in the same place for the first time.  We are expecting several hundred delegates to attend from business owners and presidents right through to administrators and marketers. The great majority will be from North America but there will also be allocations from Canada and the Rest of the World too. In addition to showcasing our product portfolio and demonstrating our breadth of expertise across the SMB and the RMM space the event is an  opportunity for partners to learn about how our mobile and cloud software can assist them with business growth and ultimately help them accomplish success. The website is now live, the invitations sent and our sales teams in North Carolina and Ottawa are all geared up for their Summer Recruitment Challenge.  Those team members that successfully rise to challenge and enlist the most partners will win themselves the chance to attend.  As we gear up for the final push for SMB’s single most rousing event of the year I am delighted to have this opportunity to share with you the exciting agenda that is taking shape including: 1. Inspirational speakers We are thrilled to have lined-up some of the industry’s most dynamic presenters to speak about the future direction of business and technology.  Presenting our guest keynote will be Guy Kawasaki .  Currently chief evangelist of Canva , Guy Kawasaki is an executive fellow at the Haas School of Business at U.C. Berkeley. Guy is perhaps best known for his former roles as advisor to the Motorola business unit of Google, chief evangelist of Apple and author of numerous best-selling business books including Art of the Start ; Reality Check ; Selling the Dream and How to Drive Your Competition Crazy . He will deliver a lively and entertaining address about his concepts for the future of the high-tech industry. Kicking off proceedings will be our very own CEO Gary Kovacs who will provide insight into AVG’s vision for the future, the implications for the small business security market online and the need for IT security vendors to look beyond protection for a company’s devices but to its data and people too. 2. Unveiling brand new industry research Gary will be a hard act to follow but I will do my best as I discuss our commitment to building strong, long-lasting partnerships. I will also unveil highlights from our latest research which will ask businesses about their plans to Monetize the Internet of Things and the opportunities this will bring to the Channel. 3. Launching new products Next up, David Haadsma will announce the latest major additions to our product portfolio as well give a sneak preview of AVG SMB’s product roadmap and branding develop. 4. Training, workshops, breakout sessions The Summit is the perfect forum for AVG partners and MSPs to network with their peers and Channel technology providers. You will be able to pose questions to key members of our senior executive team as well as hold technical discussions with engineers and developers in the on-site Tech Lab. From technical training to breakout sessions this event will offer partners a broad spectrum of opportunities to enrich their knowledge and enhance their understanding of how to take their own business forward.  We will also have breakout sessions covering sales, marketing, business, enablement and technology – all of which are essential to today’s ambitious IT providers. 5. Awards Finally at the end of Day Two there will be a gala dinner and an opportunity to pick up AVG awards in a variety of categories. In summary the Cloud Summit is further evidence of our commitment to continuously develop fresh ways for partners to derive value from working with us. Our ambition is to establish this event as one of the best in the industry. A lot of hard work has gone into creating an exciting program of inspirational content and valuable networking opportunities that will help enable sustainable growth and business diversification for all our partners.   I look forward to welcoming you in Arizona. For more information or to register to attend please visit http://www.avgcloudsummit.com/ .

How to link Azure RemoteApp to an existing VNET

My name is Daniel Campos, and I am a program manager intern on the RemoteApp team. On May 12 th , we announced the availability of the preview for the Microsoft Azure RemoteApp Service. Some of our customers asked for more information on how to connect Azure RemoteApp to their existing Azure VNET. This tutorial walks you through the steps of linking Azure RemoteApp to an existing VNET in Azure. During this tutorial we will be referring to the “RemoteApp VNET”, where Azure RemoteApp lives and the “Backend VNET”, where you have your AD/Server or other VMs running. For the purpose of this tutorial I will be starting from scratch. If you already have an azure VNET skip to step 2. I suggest that you fill out a table like the one below so you have your numbers easily available. For my address spaces, both for my Azure VNET and RemoteApp VNET I choose 10.1.0.0/19 and 10.2.0.0/19 for simplicities sake. You should check your VM and VNET specific requirements before settling on a size. DNS IP(must be in backend address space) 10.1.0.0 Backend VNET Address Space 10.1.0.0/19 RemoteApp VNET Address Space 10.2.0.0/19 Gateway IP for Backend VNET   Shared Key   Gateway IP for RemoteApp VNET   1. Create a Backend VNET a. NEW -> NETWORK SERVICES -> VIRTUAL NETWORK -> CUSTOM CREATE b. Choose a name and a location for your backend VNET. c. Enter your DNS server’s IP address. d. Select an address space for your VNET. In my case my Backend VNET will be 10.1.0.0/19 and my RemoteApp VNET will be 10.2.0.0/19. 2. Prepare Backend VNET for VPN. a. NEW -> NETWORK SERVICES -> VIRTUAL NETWORK -> ADD LOCAL NETWORK b. At this point you need to feed the local network a random VPN device IP as our RemoteApp VNET does not exist yet. c. The Address space must be identical to the address space you will be assigning to your Azure RemoteApp VNET. In my case that will be 10.2.0.0/19. d. After the local network has finished creating, switch back to your recently created backend VNET. Click the CONFIGURE tab. Click the Connect to the local network checkbox and choose the local network you just created from the LOCAL NETWORK dropdown. Scroll down to the virtual network address spaces section for the VNET, click add gateway subnet and click SAVE when done. Wait about a minute as your network updates. e. Go back to the VNET dashboard tab and click CREATE GATEWAY in your VNET, two options will pop up, click on Dynamic Routing and prepare to wait, gateway creation is usually about 15-30 minutes. f. After gateway creation had finished your VNET should resemble what is below. g. At this step you will want to update your table with the Gateway IP address. DNS IP(must be in backend 10.1.0.0 Backend VNET Address Space 10.1.0.0/19 RemoteApp VNET Address Space 10.2.0.0/19 Gateway IP for Backend VNET 23.100.42.45 Shared Key   Gateway IP for RemoteApp VNET   3. Create RemoteApp VNET a. NEW -> APP SERVICES -> REMOTEAPP -> CREATE WITH VPN Should look like this b. Next you need to create a RemoteApp virtual network for the RemoteApp Service. From the RemoteApp main screen select the VIRTUAL NETWORKS tab and click CREATE A REMOTEAPP c. Place the RemoteApp VNET in a region close to your backend VNET for best performance. d. Remember the Virtual Network Address Space will be the address space where your Azure RemoteApps Live (i.e. RemoteApp VNET) and the Local Network Address Space is your backend VNET. These 2 must not overlap. e. Next enter your DNS Servers IP address and the VPN IP address that we generated earlier in our Gateway creation (23.100.42.45 for me). You will need to make sure you choose DYNAMIC routing and then you can finish creating your RemoteApp VNET. You will need to wait 15-30 minutes for the RemoteApp VNET to provision. f. After the VNET is done provisioning you will need to write down your shared key and Azure Gateway IP Address. Click on the MANAGE KEY button at the bottom of the screen to obtain this information. g. At this point you should update your table with the Azure Gateway IP address and the shared key. DNS IP(must be in backend 10.1.0.0 Backend VNET Address Space 10.1.0.0/19 RemoteApp VNET Address Space 10.2.0.0/19 Gateway IP for Backend VNET 23.100.42.45 Shared Key WhFVekpMcpgrBmxuX1cEHUYLtMKwMmew Gateway IP for RemoteApp VNET 191.239.33.244 4. VNET to VNET Connectivity a. NETWORKS -> LOCAL NETWORKS Click EDIT at the bottom of the page once you have selected your Local Network b. Replace the VPN Device IP Address with the Azure RemoteApp Gateway IP you just wrote down and click on through to update your local network. c. Run the Azure PowerShell cmdlets i. Download/Install Azure PowerShell Module: http://azure.microsoft.com/en-us/downloads/ ii. Launch Windows Azure Powershell . iii. Add your Azure Account by running add-azureaccount . Be sure to select your subscription that contains RemoteApp. iv. Run Set-AzureVNetGatewayKey –VnetName -LocalNetworkSiteName -SharedKey This will take about 2-5 minutes to finish running. When it is done and successful your command shell should resemble mine. d. After that has finished navigate back to the VNET Dashboard page and in your appropriate VNET click CONNECT , within about 2 minutes Azure will finish connecting. e. After waiting another 5 minutes and refreshing the networking page, there should be traffic between the two. You are now able to use RemoteApp to connect with Azure VNETs. f. Your RemoteApp VNET should switch to be in a ready state about 5-10 minutes after you see that the VNETs are connected. Now that your RemoteApp VNET is connected to your backend VNET you will be able to move forward with setting up your RemoteApp Hybrid Instance. Stay tuned for more blog posts and release updates for Azure RemoteApp in the near future.