Tag Archives: Horizon View

VCAP-DTD | What materials I used to study

As part of my recent studies towards the VMware VCAP-DTD I used various training materials, so, I thought I would cobble a post together letting everyone know what I used, and what I thought was best.

Before anyone asks, no, I didn’t use an exam cram, that’s what makes the VMware VCAP exams different to many other industry qualifications, it’s one you can be proud of achieving through dedication and hard work as you can’t cheat!

I was lucky enough to attend the two day instructor led View design workshop to kick off my studies, however I think this course can really be hit or miss depending on the students in attendance. Unfortunately, I found myself in a fairly quiet group, so most of the banter I looked forward to, discussing other peoples design decisions didn’t happen and at times I found myself and the instructor having one to one design discussions with the rest of the group looking on and sometimes looking a bit lost. Don’t get me wrong, this is not a dig toward the instructor, in fact I thought he was actually very good, if it wasn’t for his persistence with the remainder of the students it would have been a boring couple of days with little takeaway. Overall, I’d recommend the class, however just hope you get an active group if you are planning on attending. Even though the course wasn’t spectacular discussion wise, the course material was good and very comprehensive and ended up played a major part in my study.

After the course, with the exam booked (with plenty of time to study further) I downloaded the blueprint and used this as the base of my study. I can’t recommend highly enough to know the exam blueprint inside out. Everything asked of you in the exam is covered off in the blueprint. Read all the suggested material as everything is in there. Head over to Jason Langer’s site, he has kindly downloaded all the material and bundled together in a single zip file, even putting all the files into their respective objective folders. Good work Jas, thanks!!!

After reading through all the official VMware material, I re-visited some of the books I had in my collection around VMware View.  I’ve mentioned these before, they can be found here.

At this point, I started my own study guides, which of course can be found here. Where I took each objective from the blueprint and wrote study notes on each element to ensure I was going to be comfortable with every section of the blueprint. The info in my study guides is a mixture of real world experience and information obtained from all the above sources, but hopefully written in a way which is simple to understand and to digest. Hopefully it will assist many of you looking to sit the exam. They are not intended to suggest that the official courses are not worthwhile, or the books are not worth reading, far from it. I’ve just cobbled together my study notes and posted them in the hope they help others as they helped me pass the tough, but passable VCAP-DTD.

I also signed up to Trainsignal. At $49 a month with no contract tie-in, or $39 a month when you sign-up for a year, I think these are simply fantastic value for money. Whilst perhaps the material they have doesn’t have direct relevance to the VCAP-DTD exam, they do have a series on View, although more aimed at the VCP-DT, they have a series on VMware vSphere design by the one and only Scott Lowe which is simply brilliant and is a fantastic aid in this exam. I’ve started some of the other courses on their site recently to assist with other studies and I cannot recommend them highly enough. With their recent acquisition by Pluralsight, you now have a whole heap more content available at the same price as before!! If you are not already a member I’d seriously recommend you take a look here

I also wrote a post on the exam experience which can be found here

VCAP5-DTD Exam Experience

So, today, Tuesday 10th September 2013, I sat my first ever VCAP exam (the VCAP-DTD) and I’m delighted to say I passed. I thought, as I have blogged about the exam already and worked through the exam blueprint, I would talk a little about the exam and hopefully try and pass on some useful tips/information.

Disclaimer: I’ve obviously accepted the NDA before sitting the exam, so I will not release any direct information on the exam, so please don’t ask!

I’ve already blogged about the exam in some detail over on my VCAP5-DTD page so I won’t repeat that here, go take a look if you are not already up to date.

The exam itself is, as others have said in their exam experience blogs, is tough. Very tough. It not only tests your ability to design large scale and complex VMware View environments, you need to be able to design the supporting components that the View infrastructure will reside on (vSphere, Network and Storage).

The multiple choice questions are more complex and tougher than those set out in the VCP exams, as you would expect being the advanced certification, however I believe these questions are very fair. The drag and drop style questions are tricky too and require some working out, don’t whizz through these questions, take your time, as I would image these are some big hitters on the overall exam scoring (I don’t know this, I’m just assuming). The Visio style diagram questions are again tough, (see a pattern emerging here?) however contain all the information you need and more to successfully answer the question.

In no particular order, here is what I would recommend to any people planning to sit the exam:

  • Time is of the essence in the exam, with 195 minutes available, I ran out of time when reviewing some the of the questions I flagged to return to at the end. Ensure you don’t get bogged down with the Visio style questions.
  • Take care to read the questions multiple times. At times, you may think you don’t have all the required information. It will be there, in-fact I found there was more than needed, so ensure you understand what the question is asking of you, especially with the Visio and drag and drop style questions.
  • Take extra laminate sheets in for your workings out. You WILL need them, I took 3 sheets and used up both sides of all, with little space for the last few questions.
  • In contrast to what I stated over on the VCAP5-DTD page, I did have access to a calculator within the exam. Perhaps they realised some of the maths you need to do is simply too much of an ask given the type of exam and time restraints. Perhaps others can let me know if they have experienced any different lately?
    • Even with a calculator, be prepared to size your designs from raw numbers.
  • Know how to size environments of all sizes. Ensure you know how many infrastructure components (vCenter, Security Servers, Connection Servers, Load balancers) are required to support varying sizes of scenarios.
  • Understand the storage options available to you in VMware View, and be prepared to be questioned on all of them.
  • Be prepared to answer question on VMware ThinApp and ensure you understand Load Balancing concepts and methods of 2 factor authentication.
  • Read the exam blueprint, know it inside out. It’s there for a reason and covers everything you need to pass the exam. I did, and I passed at first attempt.

With regard to study materials, what would I suggest? My VCAP5-DTD study guides of course, they helped me pass! Aside from these be sure to check my list of books, I used them all at various points, also check out the APAC vBrownBag’s previous recordings as these were also very valuable. Finally, after some general advice from my esteemed Xtravirt colleague Gregg Roberston, practise diagramming different scenarios. I got some Magic Whiteboard from Amazon and drew out countless scenarios until I could do them fairly quickly. It think this helped in the exam.

So, onto the next exam(s)… VCP-IAAS, VCAP-DCA and VCAP-DCD – Yes I am a glutten for punishment.

Thanks for reading and if you are sitting an exam soon, good luck!


VCAP-DTD | Objective 6.3 | Determine Management Requirements for a View Client Design

Determine patching requirements

Depending on the client being used there are a number of methods that can be utilised.

Zero clients have no operating system and no local storage, therefore no OS patches are required, not anti virus or anti spyware. There maybe occasional firmware updates to the hardware, however this will be managed by the vendors propriety software. Wsye for example, have Wyse device manager, Samsung utilise MagicRMS.

Thin Clients will again have their own management software that will allow for updates to be sent, however for those clients running embedded versions of Windows, patch updates and AV solutions will need to be managed via another product. Windows WSUS is an option, however there are more comprehensive solutions available such as Shavlik, Lumension and even SCCM.

Fat clients can continue to be managed as they have been managed previously.

Normally little consideration needs to be given to mobile devices as software is updated from their respective App stores. If your design will need to accommodate a large number of mobile devices, then a MDM solution should be considered.

Establish software distribution requirements

Most thin and zero clients will already come pre-installed with the View client so nothing will need to be installed here, the updates will be managed though the broker software.

For traditional fat clients, then GPO could be used, alternatively, Lumension or SCCM.

Identify client peripheral requirements

This has already been discussed in Objective 6.1, refer back to this post.

Establish security requirements

This has already been discussed in Objective 6.1, refer back to this post.

VCAP-DTD | Objective 6.2 | Determine Session Connectivity Requirements for a View Client Design

Establish session mobility requirements (e.g., Follow Me, etc)

Does the business already have an investment in a follow me solution?

How do people print now?

Will that solution integrate with the built-in ThinPrint features of VMware View, or will a further investment be required?

Print jobs can severely affect bandwidth and responsiveness, if possible, use follow me/location based printing to avoid transferring bits over the RDP or PCoIP remote display channels.

Some consideration here, should also be given as to what will happen when a user disconnects from an active session. For example, a user is in a client meeting at a remote location, connected to their View desktop via an iPad. They have made various notes throughout the meeting and at the end simply disconnect. They then travel home or back to a corporate office and login again, will their disconnected session take them to where they left off?

If this is required you need to carefully think about how long you leave ‘disconnected’ sessions available for, as potentially, these desktops could just be sat there for a number of hours or day consuming resource when they don’t need to be.

Establish remote access requirements

The requirements for remote access should come from the business. It will be up to you to determine the number of security servers, the connection protocols, and consider using tags for remote access.

In most cases not all users will require remote access, therefore they could potentially be a separate use case, but that would probably be too easy. If  remote access is required, will the business be happy with the users getting the full feature desktop they have when residing on the corporate LAN or will a different restricted desktop be made available (where tags will come in to play).  I’ve seen people struggle with tags so here area few snippets that you should be aware of when using tags.

  • The tags are applicable to Connection Servers only and not Security Servers
  • Any Security Servers paired to a Connection Server works exactly like the Connection Server
  • If a load balancer is used in front of a group of Security Servers or Connection Servers they must be tagged in the exact same way
  • A single Connection Server or single Desktop Pool can have multiple tags
  • Multiple Connection Servers and Desktop Pools can have the same tag
  • Desktop Pools that do not have any tags can be accessed through any Connection Server
  • View Connection Servers that do not have any tags can only access the desktop pools that also do not have any tags
  • Tags have a higher priority to user entitlement pools
Depending on the remote location, thought will need to be given as to which connection protocol will be used, and therefore will you give users the ability to choose their own protocol?
VMware and Teradici have provided the following guidelines for remote access:

Determine applicable session behaviour requirements for the design (e.g., disconnect, logoff, timeout)

This type of information should be given to you again from the business, else you will need to probe for the answers in the design workshops. As briefly mentioned earlier, if disconnected machines are never logged off, sessions can (but not in the same way as with old terminal server sessions) become stale, and consume resource for no reason.

It is likely you will use different policies for different pools. For example, a dedicated assignment pool may not have any disconnect sessions, or potentially they logoff times will only be once a week to keep inline with company policy. Floating desktops or kiosk style may have a much shorter policy and perhaps could be logged off every evening or at the end of every business day. Discuss the options with the business to make suitable plan.

Identify display protocol requirements to satisfy the design

VMware have worked hard with Teradici to promote the PCoIP protocol and will try to push this over RDP where possible. Refer to the above table to determine which protocol is suitable for your desktop pool assignments. Perhaps with more IT savvy users you let them choose their type of protocol instead of forcing the users to use one desktop internally and potentially another externally.

Is multimedia required within the desktops? If so, you will want to try and ensure that all desktops requiring multimedia content are using the PCoIP protocol for improved performance. If the desktop is a simple task worker desktop with a few applications on then you will probably find that RDP is sufficient and will allow for users connecting in.

Ensure GPO is reviewed to make the most out of your chosen connection protocol. For example, disable the build to lossless feature in limited bandwidth situations etc.

VCAP-DTD | Objective 6.1 | Create a Physical View Client Design

Determine the number and types of access endpoints required for the design (e.g., zero client, thin client, fat client, etc.)

You will normally be presented this type of information during the initial design workshops. In most cases, one of your requirements will be, “the solution must support x users” or “the solution must support x concurrent sessions”. If in the rare situation a business doesn’t know how many users/desktops the infrastructure will be required to support, then you can use capacity planning tools to assist in information gathering.

It is worth clarifying from the start the expected growth required from the design so that these factors can be accounted for.

Each type of endpoint has it’s benefits and drawbacks.

Thin Clients

  • Power on and present the View desktop seamlessly
  • Lower cost and reduced support requirement
Zero Clients
  • No operating system
  • No local storage
Thick Clients
  • Repurpose traditional PCs or laptops (no cost outlay)
  • Apple Mac systems (BYOD)

It’s not mentioned in the blueprint, however tablets should also be considered:


  • Apple iPAD
  • Android
For each device the following should be investigated against the design:
  • What OS version is installed, will it require AV and patching?
  • Will it require firmware updates?
  • Will it support multiple monitors?
  • What are the multimedia requirements?
  • Is there a need for local permanent storage?
  • What are the peripheral port access requirements?
  • Are there any special network requirements such as VPN?
  • Where will the device be located, will there be any support and access constraints?
  • Are the user devices mobile?
  • What is the end user capabilities and profile?
  • Will local mode desktops be used?

Identify security requirements for the View Clients

Generally security requirements will already be governed and the View solution will need to fit those requirements. The main considerations client wise, will be if there is a requirement for VPN  and smart card authentication as these will limit the choices of end clients available to use.

Items such as security servers, two factor authentication etc aren’t really an issue for client devices.

Determine connectivity requirements for the View Clients

At this stage we should already be aware of where our users will be connecting from and specifically (for client selection) have a looked at the protocol they will be using, PCoIP or RDP?

Establish multimedia capabilities

If our design determines the requirements for multimedia then we need to ensure that the end clients will support it too!

Multimedia redirection (MMR) redirects the output of multimedia codecs that are running on the remote desktop tot he local client. The local client system renders the full motion video and audio. Windows XP and Vista support MMR, Windows 7 does not.

If there is a requirement for HD video within a Windows 7 desktop, then typically 2vCPUs and 1GB RAM will be required for PCoIP to play 420p and 720p formatted videos. For 1080p, the windows may need to be smaller to get HD quality.

Network latency will be critical for acceptable multimedia performance, and on some links may prove challenging.

Establish peripheral requirements

USB redirection is provided with the View Client running on Windows 7, Windows XP and Windows XP embedded. VMware recommends that an assessment is carried out capturing the USB requirements for all users. Include all USB devices, including:

  • Blackberrys
  • iPhones
  • USB drives
  • USB printers
  • USB Webcams
  • USB headsets
  • etc etc etc etc

During the PoC phase all of these devices should be tested and verified as working.

Printer redirection is key and often overlooked. Ensure the client device supports print redirection and meets the location awareness requirements.

The client device that gets selected will need to supply enough ports. Support for some peripherals may require drivers to be installed on the desktop.

VCAP-DTD | Objective 5.5 | Create a Tiered Physical View Storage Design

Based on business and technical requirements, determine tiered storage configuration

View Composer supports the use of tiered storage. Generally, in most scenarios, the replica is placed on a separate high performance datastore such as an EFD. Doing so will give us a slight saving in shared storage and will give you much faster read operations. The replica storage must still be shared so that all hosts running desktops within the linked clone pool can access the replica’s disks.

It’s worth noting here, if the replica disk is placed on local storage, all the linked clones in that pool must be placed on local storage.

When moving the replica to a separate datastore you reduce each linked-clone dat store by the size of the replica. A replica is required for each pool, so if you have multiple pools allocated to the same datastore, the saving is equal to the sum of all replicas.

When placing the replica on EFD storage, you reap the following benefits:

  • EFD supports much higher I/O than SAS or SATA disk
  • EFD responds to high read rates, such as boot storm or logon operations
    • During a boot lor login event the ration is 80/20 RW
    • A large percentage of reads are from the replica, therefore placing it on faster storage enhances performance massively
I thought it worth mentioning that desktop VMs cannot write to the replica, therefore it is important to understand that an EFD will not improve write I/O.

Determine content to be tiered and appropriate placement within tiers

Aside from replica, the Windows profile can be redirected to a persistent disk. Typically profiles and user data are redirected to network shares, leveraging a lower-tier storage such as NFS data stores.

Replica – EFD


Persistent disks – NFS (typically)

Disposable Disk (If used) – same datastore as the OS disk.

Establish sizing for each storage tier in the design

Help with sizing will come from the analysis already done on the existing environment. Remember that placing the replica on EFD will reduce the shared storage requirements overall. Keep in mind a replica is required for each pool!

Further work will be done on this when I finish the objectives and run through a mock design.

VCAP-DTD | Objective 5.4 | Determine Performance Requirements for a View Physical Storage Design

Establish IOPS Requirements

IOPS requirements will be made available from capacity planning reports and analysis.

Way back in Objective 1.2 I went into some detail on how to calculate IOPS, so click the link and re-visit that page.

Jim Moyle has written a great white paper Windows 7 IOPS for VDI: Deep Dive, I’d highly recommend giving this paper a thorough read.

Establish throughput requirements

Throughput requirements will be made available from capacity planning reports and analysis.

Determine storage network requirements

Shared storage should be presented to hosts by using redundant SAN fabric that encompasses redundant storage adapters in each host, SAN switches, and storage array processors. View desktops can be deployed on FC, iSCSI, NFS and locally attached storage each with their own benefits and downsides. Business requirements will usually play a large part in the storage decision for VDI.

Remember, if using jumbo frames to increase MTU size and potentially improve performance, to ensure the MTU setting is changed end to end. From the physical switch down to the vNIC in the desktop, else you could start seeing issues with network fragmentation.

VCAP-DTD | Objective 5.3 | Create a Physical Design for Desktop Application Storage

Identify the applications required for the design

This is very difficult to do manually with a tool that can go away and look what is installed on desktops and how often they are used. Pay extra attention to web applications. It’s a common mistake to see that IE6 for example ls installed on a machine and it’s accessed x number of times throughout the day, however what is IE6 accessing. Real world experience shows that some web apps aren’t compatible with some web browsers so take care to audit what is actually going on within the web browser itself.

If moving between OS’s ensure that compatibility checks are done and the application vendors will support the application in a VDI environment and, if applicable, support the application being virtualised with ThinApp.

Speak to stakeholders within the project and get them to sign off applications as they are discovered and packaged either embedded within a virtual desktop or virtualised with ThinApp. Try to ensure the business provide you with step-by-step instructions on how the applications should be installed, removing the need for any guess work.

Determine the appropriate deployment method for each application (e.g., ThinApp streamed, ThinApp deployed, native install etc)

Testing will prove what is the best fit for the environment here as different environments will vary.

In general, I prefer to use streaming, when desktops are local and network performance is not an issue. This works great also, for floating desktops as there is no need to install anything into the desktop and the applications are simply streamed as required. For streaming to work successfully client must have a minimum 100Mbps LAN access to the ThinApp repository. The connection must be reliable and have low latency. 1GB would be recommended.

ThinApp deployed comes into play when perhaps bandwidth is at a minimum or for certain power users that have the ability to install applications locally. ThinApp deployed will create an MSI that allows the application to run locally.

Native installs will work best with heavy power users that need to make modifications to applications. Also, some applications simply cannot be virtualised, so then a native install is the only option. I’ve found that Microsoft Office, whilst it can be virtualised, tends to perform better when installed locally. Generally all users will use some function of Office so, generally, it’s easier ti simply install natively.

Establish Application Capacity Requirements

The analysis tools mentioned already will help you monitor how much disk space each application will use.

VCAP-DTD | Objective 5.2 | Create a Physical Design for View Pool Storage

Determine the base image/template requirements for the design

Firstly and perhaps most obviously we need to have an understanding as to what OS levels we are going to be deploying and supporting with the View environment. Windows XP, Windows 7, Windows 8? Then what versions are we going to support, 32 bit or 64 bit.

Will we lock the desktop down and reduce some of the common performance grabbing features such as Aero themes, screen savers etc.

What is going to be installed locally in the desktop, any applications that cannot be delivered by an alternative method (ThinApp?). Perhaps we need a master image to span multiple countries or support mull-lingual users in which case do we need to install extra language packs into the image?

Establish replica requirements

Simply put, this should be placed on the tastes disk we have available to us. If we have flash brilliant, if not then the next highest tier is a must.

Ensure the replica does not reside on the same LUN as the linked clones as this will reduce performance.

Identify linked clone requirements (e.g, OS disk)

Each linked clone disk is small, starting at 16MB of space for each 2GB of disk. Remember they are sparse disks, so we only need to account for changed blocks. These will only tend to grow quickly with persistent desktops, so if we have a pool of power users that we know will be installing multiple applications then we need to be aware that their disks may grow quicker than anticipated.

When we use linked clones we are restricted to 8 host per cluster, therefore, we may need to place the linked clones in a separate cluster of their own. We should look to limit the number of VMs in a linked clone pool to 512 as the refresh and recompose events will create significant I/O. 512 is recommended and also the supported maximum.

We should also look to design a maximum of 128 linked clones per VMFS datastore. NFS can achieve up to 256 linked clones per datastore.

These numbers will all depend on the workload requirements. We should look to group VMs that are running similar workloads to be able to better monitor and predict performance.

Determine the amount of estimated data growth and the impact on the design

Data growth is tricky to estimate and depends on a number of factors related to the way the infrastructure is setup. For example, if you have a desktop pool for call centre users, they will more than likely be using a floating desktop. Their profiles could reside on a network share, and the applications could reside in a ThinApp repository. This use case is likely to have little to no growth.

Another example, could be a developer pool. They may well use persistent desktops, still with their profiles residing on a network share but with the ability to store data locally and the power to install applications to their desktop, growth is potentially likely to be high.

As users interact with linked-clone desktops, the OS disks will expand as write operations update file blocks. A desktop refresh operation restores the OS disks to their original state and size, thus reducing storage consumption. VMware therefore recommend to regularly refresh linked clones (preferably at logoff) to limit storage growth, especially when the storage overcommit level is set to aggressive. Worth noting here, that the refresh operation does NOT affect persistent disks. Ideally, pool settings should be configured to refresh the desktop at logout for both dedicated and floating pools.

Whilst it doesn’t directly lower storage consumption pay attention to the rebalance operation and the schedule it runs at. If an environment consists of large linked-clone pools and uses multiple data stores, the storage space may not be used efficiently. The rebalance option saves storage space on overloaded data stores and ensures that none are underused. Rebalancing also allows you to add new data stores to the capacity inventory and remove existing datastores.

Ensure disk space is monitored closely to ensure that you don’t experience any outages due to lack of space.

Establish persistent disk requirements

The persistent disk allows each dedicated assignment linked clone to store the user profile, settings and data. When using floating desktops, user specific data does not need to be preserved, sp persistent disks are not available.

Generally, in most ideal situations, the profile data will be stored centrally on a network and persistent disks will not be required, however in some cases where profile data may become very large, performance may be enhanced by attaching a persistent disk to a users desktop.

Power users are an ideal use case for a persistent disk, as they will likely be heavy application users and are likely to have the ability to install applications locally on their desktops.

You can store persistent disks on the same datastore as the OS disk or on a different datastore.

Establish disposable disk requirements

When you create a linked clone pool, you can configure a separate, non-persitent disk to store the guest OS’s paging and temp files that are generated during user sessions. When the linked clone is powered off, View Manager replaces the disposable disk with a copy of the original disk that View Composer created with the linked clone pool. Linked clones can increase in size as users interact with their desktops. Using disposable disks can save storage space by slowing the growth of linked clones. For design purposes, it is worth noting though, that the disposable disk is stored on the same dat store as the OS disk.

Determine full clone requirements

Full clones will probably have a limited use case within most VDI deployments. Primarily this will be because of the disk space they consume. Most task workers that do not have elevated permissions within their desktops to perform administrative tasks or install software in their desktop should have no requirement for a full clone. Whilst you can still provide linked clone desktops with the ability to install software locally, you run the risk of loosing this data of a refresh or recompose action is performed on that pool.

Full clone desktops should be used for persistent desktops that will require some sort of DR. I say this because you cannot replicate a linked clone desktop to another site using such services such as SRM. If the desktop was a full clone, it could be replicated an imported into another View Manager in a DR site.

Establish persona requirements (e.g, central profile store, View Virtual Profiles, etc)

Refer back to Objective 3.1 and review the requirements for the virtual profile repository again.  This covers off some of the requirements for creating the profile repository. Sizing the profile repository is crucial for success.

For the exam especially, remember you need a View Premier licence to enable and use View persona Management.

If deploying ThinApp’s to the desktop, the ThinApp sandbox can be included in the users profile.

If supporting multiple OS’s remember that Windows XP uses v1 profiles, where as Vista and Win7 use v2. Users cannot access the same profile if switching between desktops that use different profile versions.

Utilise GPO to add the View Persona Management (ADM) template (ViewPM.adm) ready for configuration and deployment. You are able to embed this in the local computer policy not he template or parent VM, but this is not going to work particularly well when changes need to be made, without re-composing existing desktops.


VCAP-DTD | Objective 5.1 | Create a Physical Design for View Infrastructure Storage

Size the Events database

I’ve already covered off sizing the events database in Objective 3.2, however to recap:

Looking through release notes and other documentation, I haven’t managed to find any officially supported calculators. You can however, assume that 2.5MB per desktop per month is required for the overall sizeof the events database. In real life, 1-1.5MB is a more realistic figure, however this depends on how many refresh, logoff and recompose actions take place.

Size the View Composer database

I’ve already covered off sizing the events database in Objective 3.2, however to recap:

Again, I can’t find any official documentation or calculators that help with this sizing, however you can safely assumed that your composer database will never get close to 5GB in size. Sizing for 5GB is a safe bet.

Determine storage requirements for the Transfer Server repository

The View Transfer server has specific storage requirements which I have touched upon already in Objective 3.1:

A View Transfer server must have access to the data stores that store the desktop virtual disks to be transferred. The data stores must be accessible from the ESXI host on which the View Transfer server VM is running on.

View Transfer server can transfer a maximum of 60 disks concurrently. During a transfer operation, a local desktop’s virtual disk is mounted on the transfer server. The transfer server VM must have 4 SCSI controllers, with each having 15 slots. This config supports 60 disks to be attached to the server at any one time. This number is likely to never to be the limiting factor and network constraints  will be reached before then.

Remember that VM must be configured with an LSI Logic parallel SCSI controller. This is not the default when running through the VM creation wizard for Windows Server 2008 R2.

Other than the storage controllers, the transfer server should have 20GB storage assigned for the repository (VMware recommendation). This should reside on a network share and not on local storage. The share on which the repository resides, must have enough space to store the staid image files. Image files are the View composer base images. These disk images are sparsely provisioned. This means that only blocks with data are stored. For example, a 40GB base image may only have 7GB worth of data, therefore only providing decent space savings.

Although not a storage requirement, remember that the transfer server should use VM hardware version 7 or 8.

Determine storage requirements for infrastructure virtual machines (e.g., vCenter servers, View servers, etc.)

At this stage, we should already have set out what we need to support our View infrastructure. This will include number of:

  • vCenter Servers
  • VUM Servers
  • SQL Servers
  • AD Servers
  • Connection Servers
  • Transfer Servers
  • Security Servers
  • File Servers
  • vCNS Servers
  • vCOPS for View

Each of these will have their own storage requirements, I’d like to think that is this information was needed, they would make it available to you in the exam.