This presentation discusses Microsoft Application Virtualization (App-V) infrastructure design and lessons learned from a series of customer deployments. Topics include Management and Reporting Server design, Shared Content placement/replication, Publishing Server placement, load balancing options, Rapid Scale-out solutions, sizing calculations, and data store configuration options. Examples for using Windows PowerShell to automate and bridge product gaps are demonstrated. Use cases discussed include Published Desktops vs. Applications, VDI Density Reduction, and IOPS/Application Footprint Reduction.
Apps should be tested before submission. Every app is unique, so a unique test plan should be created to test the components of each app. When creating the test plan, a few factors should be taken into account: app modules; how those modules interact within the app and in which order they are initialized; and which modules are required for the app to run. Based on this info, the modules should be tested. In this session, Mickey talks about how, through testing, you can ensure the highest quality for your app.
Even though you're watching this on-demand, Mickey wants to help. Post your questions, comments, etc below or tweet it, mentioning @cdndevs.
Infrastructure as a Service è il nuovo modello che permette di creare delle macchine virtuali all'interno di Windows Azure, senza dover acquistare l'hardware, e senza doverlo gestire. Questo permette di avere un servizio on-demand, che abbatte notevolmente i costi. Durante questa sessione vedremo come creare VM remote e come mettere in comunicazione la propria infrastruttura con quella su Azure.