Desktop Deployment VM is created Personalization layer created ‘Boot’ Image created (BIC) VM reconfigured VM Powered on Windows Mini-Setup executes Registration with broker (more in Module 5) Non-persistent reboot
VM Created VM hardware settings – Memory, CPU, network, OS Type, etc VM Name in vCenter The VM is just a shell at this point. Once the VM itself is created Unidesk begins the process of making is an operational VM
Boot Image Creation (BIC) “Boot” image VMDK is wiped Files needed prior to CFS/NTFS start are copied from layers to “boot” image Registry is composited (Blended) and put on “boot” image Boot image is connected to VM as first Disk O/S layer App layer Personalization Layer
BIC of a NEW Desktops Reconnects the boot image to the VM and readies for Power On Iterate through each layer reading the registry changes in to the boot image Iterate through each layer copying bootfiles (App Layers and Pers Layer) OS Layer Bootfiles and Registry and copied (based on bootfiles needed before CFS loads) Repartition and Format (Zero to Boot Image out) Connect MM “boot” disk to CP for updates – You will see reconfigure tasks in vCenter
Power On and Mini-Setup At this point the Pers Layer is a PERSISTENT disk VM is powered on Desktop begins mini-setup reading Unattend.xml Depending on unattend.xml configuration and desktop type VM may reboot once or twice. This runs ONCE only for any machine!
Broker Registration Each broker’s registration process is slightly different. But keys are as follows: – Happens after mini-setup runs – Must have DNS working and firewall ports open – Non-pers desktops will have registration come BEFORE the Disk is “flipped” to non-persistent More on brokers in Module 5
Persistent/Non-Persistent Simple difference is that the Personalization Layer is changed to an independent non- persistent disk Unidesk looks for logout of user and powers off the VM Broker has power options turned on and powers the machine back on This hard restart “flushes” the non-persistent disk
Unidesk Templates Templates are basically a bill of materials for the desktop Contains both Unidesk and non-Unidesk info Not all options have to be configured Templates can be tied to a pool, but don’t have to be
Template Uses Used to build new desktops Used in Searching and Filtering to update desktops (based on a specific template or template association w/ a pool) In later versions will be used to configure Power Management and Power State options
Maintenance Windows Created in the Settings and Configuration tab within System Settings Dictates desktop update behavior based on: – Day of the week – Time of the day – Status of desktop (in use or not) There are 3 default Maint. Windows defined – 24x7 – wait for user to logoff – System Default Maint. Schedule (9pm-5am & Weekends) – Weekends
In Use/Status Option When a user has logged out… – Means they have logged out NOT just disconnected – Must be logged out for 10 minutes minimum As soon as possible – Means even if the user is logged in they get logged out for this update.
Maint. Window Options - Desktop Editing Use existing maint. Schedule set for desktop Execute right now! Specify a time and date regardless of status At next user log out
Search Wizard Contains these words = computer names or owners Have owners in this group = AD or Unidesk Groups CachePoint = Currently associated w/ a specific CP Maintenance Schedule = Self Explanatory Are Using this: – Template = Using that specific template or version – Layer = Using that specific layer or version Has pending configuration changes
Beware Beware of the non-wild card, wild card… Search terms do not use wild cards. A Search for Zoo will return both Zoo and Zoom Search on longer names when possible not just fragments: – MS Office instead of Off
When updating a desktop what are the options available for the maintenance window? You are asked to deploy 50 identical desktops over the next month, what is the easiest way to do this? Can you have a template with no broker configuration defined? You notice your non-persistent desktops reboot after they are built. Is this normal? If so Why?