module 4: desktop management
DESCRIPTION
Module 4: Desktop Management. Agenda. Desktop deployment Options and process Persistent vs Non-Persistent Desktops Template Usage Desktop Configuration Options Maintenance Windows Searching and filtering. Understanding Desktop Deployment. Desktop Deployment. VM is created - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/1.jpg)
MODULE 4: DESKTOP MANAGEMENT
![Page 2: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/2.jpg)
Agenda
• Desktop deployment– Options and process
• Persistent vs Non-Persistent Desktops• Template Usage• Desktop Configuration Options• Maintenance Windows• Searching and filtering
![Page 3: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/3.jpg)
UNDERSTANDING DESKTOP DEPLOYMENT
![Page 4: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/4.jpg)
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
![Page 5: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/5.jpg)
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
![Page 6: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/6.jpg)
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
App layer
App layer
App layer
Personalization Layer
![Page 7: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/7.jpg)
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
![Page 8: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/8.jpg)
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!
![Page 9: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/9.jpg)
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
![Page 10: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/10.jpg)
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
![Page 11: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/11.jpg)
Pers vs Non-Pers Desktop
![Page 12: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/12.jpg)
Desktop Configuration Options
• Non-Unidesk settings:– Broker/ Pool configuration– Desktop Name– Network– OS Type (for VMware)– Number of CPUs– Memory (VM RAM)– Pagefile size (Windows)– Core Dump Type (Windows)
![Page 13: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/13.jpg)
Desktop Configuration Options
• Unidesk Specific Settings:– Template– CachePoint or Cluster assignment– Persistent or Non-Persistent– OS Layer and App Layers – Pers Layer size (thin provisioned) and backup
settings– Desktop Maintenance Schedule
![Page 14: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/14.jpg)
DESKTOP CREATIONLAB
![Page 15: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/15.jpg)
UNIDESK TEMPLATES
![Page 16: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/16.jpg)
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
![Page 17: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/17.jpg)
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
![Page 18: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/18.jpg)
CREATING AND USING A TEMPLATELAB
![Page 19: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/19.jpg)
MAINTENANCE WINDOWS
![Page 20: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/20.jpg)
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
![Page 21: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/21.jpg)
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.
![Page 22: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/22.jpg)
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
![Page 23: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/23.jpg)
CREATING AND USING MAINTENANCE SCHEDULES
LAB
![Page 24: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/24.jpg)
SEARCHING AND FILTERING FOR DESKTOP UPDATES
![Page 25: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/25.jpg)
Search Wizard…
![Page 26: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/26.jpg)
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
![Page 27: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/27.jpg)
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
![Page 28: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/28.jpg)
FILTERING AND DESKTOP UPDATESLAB
![Page 29: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/29.jpg)
QUESTIONS YOU MAY SEE AGAIN
![Page 30: Module 4: Desktop Management](https://reader035.vdocument.in/reader035/viewer/2022062814/568167e5550346895ddd5063/html5/thumbnails/30.jpg)
• 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?