Administrators Guide: Wyse WSM™ Release 5.0.1
Transcription
Administrators Guide: Wyse WSM™ Release 5.0.1
Administrators Guide Wyse WSM™ Release 5.0.1 Issue: 053013 PN: 883874-03 Rev. E IMPORTANT: This is a living document with ongoing changes Copyright Notices © 2013, Wyse Technology LLC. All rights reserved. This manual and the software and firmware described in it are copyrighted. You may not reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, any part of this publication without express written permission. End User License Agreement (“License”) A copy of the Wyse Technology End User License Agreement is included in the software and provided for your reference only. The License at http://www.wyse.com/license as of the purchase date is the controlling licensing agreement. By copying, using, or installing the software or the product, you agree to be bound by those terms. Trademarks The Wyse and PocketCloud logos and Wyse and PocketCloud are trademarks of Wyse Technology LLC. Other product names mentioned herein are for identification purposes only and may be trademarks and/or registered trademarks of their respective companies. Specifications subject to change without notice. Restricted Rights Legend You acknowledge that the Software is of U.S. origin. You agree to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end-use and country destination restrictions issued by U.S. and other governments. For additional information on exporting the Software, see http://www.microsoft.com/exporting. Ordering Information For availability, pricing, and ordering information in the United States and Canada, call 1-800-GET-WYSE (1-800-438-9973) or visit us at wyse.com. In all other countries, contact your sales representative. Contents 1 Introduction 1 About this Guide 2 Finding the Information You Need in this Guide Wyse Technical Support 2 Related Documentation and Services 2 Wyse Online Community 2 2 2 How to Build Your WSM Environment 3 Standard or Advanced: Which WSM Environment is for You? Building a Standard WSM Environment 3 Building an Advanced WSM Environment 4 3 3 Configuring and Managing: Using the Administrator Console 5 WSM Functional Areas 5 Getting Started as an Administrator 6 Logging In 6 Understanding the Overview Page 7 Navigating in WSM 8 Filtering Feature 8 Using Messages, Warning Signs, and Quick-Links 8 Logging Out 8 Details About Using Active Directory Integration 9 Understanding the Levels of Active Directory Integration 9 Using Active Directory Integration with and without SSL 9 4 Sites 11 About Sites 11 Managing Sites 12 Creating a Headquarters Site 14 Creating a Linked Site 15 Editing Sites 16 Working with Sites 18 Customizing Linked Sites 18 Linked Site Use Cases 19 About Site Groups 21 Managing Site Groups 21 Adding Site Groups 22 Editing Site Groups 23 Details Tab 23 Sites Tab 25 Managing Site Templates 26 Adding Site Templates 27 Working with Site Templates 29 iv Contents 5 Operating Systems 31 About OS Images 31 Managing Operating Systems 33 Registering OS Images 35 Editing OS Images 37 Details Tab 37 Site Groups Tab 39 Site/Site Templates Tab 40 Server Groups Tab 40 Streaming Servers Tab 41 Patches Tab 41 Content Distribution Tab 42 6 Applications 43 Managing Application Images and Application Licenses 43 Registering Application Images 46 Editing Application Images 48 Details Tab 48 Site/Site Templates Tab 49 Server Groups Tab 50 Streaming Servers Tab 50 Licenses Tab 51 Patches Tab 51 Content Distribution Tab 52 Adding Application Licenses 53 Editing Application Licenses 54 Application License Details Tab 54 User Groups Tab 55 How to Publish Applications 56 Installation Requirements and Recommendations 56 Hardware and Software Requirements 56 About Publishing Performance 57 Preparing a Dedicated Machine 57 Setting-up Disk Space for Publishing 57 Installing WSM Publisher 58 Publishing Steps 59 7 Servers 67 Managing Servers 67 Editing Servers 69 Managing Services for a Server 71 Managing Server Groups 72 Understanding the Default and User-Created Server Groups Adding Server Groups 75 Editing Server Groups 76 Details Tab 76 Servers Tab 77 Device Groups Tabs 77 OS Images Tabs 78 App Images Tab 78 8 Devices 79 Managing Devices 80 Adding Devices 82 Editing Devices 84 Sending Commands to Devices 87 Importing Devices from a File 88 73 v Contents Managing Device Groups 89 Understanding the Default and User-Created Device Groups 90 Adding a Device Group 92 Editing Device Groups 94 Details Tab 94 Devices Tab 95 Reassigning Devices to a Different Device Group 97 Sending Commands to Devices in a Device Group 99 Managing Device Templates 100 Adding Device Templates 102 Editing Device Templates 104 Changing the Device Group Assignment for a Device Template Adding an OS Image to a Device Template 107 9 106 Users 109 About User Management: If Your WSM is Integrated with Active Directory Read this First 109 Managing Users without Active Directory Integration 110 Adding Users without Active Directory Integration 112 Editing Users without Active Directory Integration 113 Details Tab 113 User Groups Tab 114 Changing User Passwords without Active Directory Integration 115 About User Group Management: If Your WSM is Integrated with Active Directory Read this First 116 Managing User Groups 117 Adding User Groups 119 Adding User Groups without Active Directory Integration 119 Adding User Groups with Active Directory Integration 120 Editing User Groups 121 Editing User Groups without Active Directory Integration 121 Details Tab 121 Users Tab 122 Applications Tab 122 Editing User Groups with Active Directory Integration 123 10 Settings 125 Database Configuration 126 Database Connection Tab 126 Database Backup Tab 127 Renaming an SQL Server Tab 127 Database Others Tab 128 Active Directory Configuration 129 AD Configuration Tab 129 Active Directory Others Tab 130 Content Distribution Settings 131 CDS Configuration Tab 131 CDS Others Tab 133 Site Configuration Settings 134 Site Configuration Tab 134 Site Configuration Others Tab 136 Device/Server Settings 138 Device Tab 138 Server Tab 139 Password/License 141 Passwords Tab 141 License Tab: Importing Server Licenses 142 vi Contents Logs/Misc Tab 143 Managing Settings 144 Managing Active Directory Domains 146 Active Directory Domains Page 146 Adding Domains 148 Editing Domains 149 Importing User Groups from a Domain Managing Virtual Centers 152 11 151 Reports 157 Overview of the Reports Page Transaction History 159 Alerts History 160 Client Report 160 License Usage Report 161 Standard Usage Report 161 Activation Report 162 Subscription Report 162 157 12 WSM Web 163 Accessing and Using WSM Web 163 Administrators 163 Dispatchers 163 Operators 163 Understanding the WSM Web Page 164 Viewing Server Information 166 Viewing OS Image Information 167 OS Image Status Details 168 Viewing Application Image Information 169 Application Image Status Details 170 Viewing Device Information 171 Performing Deployment Tasks 172 Assigning an OS Image to a Site Group 173 Viewing OS Image Assignment Information for a Site Group 174 Viewing Content Connections 174 A System Maintenance 175 Managing Passwords Used by WSM 175 Backing Up the WSM Database for System Recovery 176 About WSM Server Services 176 Understanding and Using the Log Files of WSM 176 About WSM System Monitoring 177 B Load Balancing 179 How Load Balancing Works 179 Using Server Groups and Device Groups 179 How WSM Selects Boot Servers in the Server Group Volatile and Persistent Cache Mode 181 Setup for Load Balancing 181 C 180 Updating OS Images and Application Images 183 Updating an OS Image 183 Updating an Application Image 187 Preparing an Application Image Update 188 vii Contents D Using the Wyse UniPlat Tool 191 Installing Wyse UniPlat Tool 191 About the Wyse UniPlat Tool 192 Creating a Backup Windows Partition 192 Restoring a Windows Partition 192 Creating a UniPlat Disk File 193 Creating the Initial File 193 Setting UniPlat Disk File Properties 193 Information Properties Tab 194 Description Properties Tab 194 Options Properties Tab 194 Inserting Files into a UniPlat Disk File 195 Restoring a UniPlat Disk File to a Partition 196 Creating a Single OS Image that Supports Multiple Hardware Platforms 196 Requirements for a UniPlat Disk File and Supported Platforms 196 Creating a Combined UniPlat Disk File 197 Reinstalling Drivers for the Current Platform 199 Creating a “Golden” OS Image from Current OS Images 200 Hardware and Partition Requirements 200 Creating the Golden Image 201 Checking and Changing the HAL of a Computer 202 Checking the HAL on a Computer 202 Changing the HAL on a Computer 203 Limitations and Known Issues 204 E Multicast Streaming 205 Overview 205 How Multicast Streaming Works 205 Configuring Multicast Streaming 208 WSM Multicast Best Practices 209 WSM Multicast Q&A 210 Using the Multicast Streaming Service Log File F 218 Installing and Building Your WSM Environment: Detailed Procedures 223 Step 1: Preparing 224 Pre-Installation Checklist (Required for All Environments) 224 Planning for WSM Sites (Advanced Environments Only) 225 Hardware Requirements 225 Software Requirements 226 System Security and Credentials 226 Server to Server Communication Ports 227 Configuring the DHCP Server 228 Server License Files 228 Installing Microsoft SQL Server Using the WSMSuite.exe File 228 Step 2: Installing and Configuring the WSM Core Server 229 Step 3: Starting the WSM Core Server for the First Time 235 Step 4: Installing and Configuring the WSM Client 239 Step 4-A: Preparing the Reference Device Used for WSM Client Installation 239 Step 4-B: Installing the WSM Client on the Reference Device 241 Step 4-C: Capturing the OS Image from the Reference Device to the Core Server 246 Step 5: Installing and Configuring a WSM Edge Server 250 Additional Details You May Need 256 Installing Your Own SQL Server 256 Installing SQL Server 2005 Express, SQL Server 2005 SP1 or Later, SQL Server 2008 Express, or SQL Server 2008 256 Installing the Latest Microsoft SQL Server Service Pack 257 viii Contents Booting WSM via PXE, Non-PXE, and Cloud Desktop Device BIOS 258 PXE and Non-PXE Boot-Up Processes 258 PXE and Non-PXE Boot-Up Requirements 259 PXE and Non-PXE Boot-Up Features 259 Non-PXE Bootstrap Deployment 260 Entering Network Configuration Information for Non-PXE Boot-Up 262 Expanding an Existing Virtual Disk 263 Using a VHD Image 265 Troubleshooting 266 Active Directory: Connection Error Messages when Enabling Active Directory 266 Audio: Solving Audio Problems in the Streaming Environment 266 Core Server: Verifying that WSM Core Server Services are Running 267 Database: Verifying that the WSM Database is Operational and Configured Correctly 267 Hostname and IP Address: Performing Changes 267 Login Error: You Encounter an Error While Trying to Access the WSM Login Page 268 Network Device: Error Messages When Adding a Network Device from Active Directory 268 ODBC: Verifying that the ODBC is Operational and Configured Properly 269 OS Image: Capturing an OS Image after Cancelling the Capture Process 269 OS Image: Re-configuring an OS Image 269 WSM Services: Verifying a Successful Installation by Viewing the WSM Services 270 Uninstalling: How to Uninstall WSM Software 272 Error Codes 272 G Users Guide 275 Logging In 275 Using the Microsoft Icons and Notifications Feature (Windows 7 Users Only) 277 Overview of the Client Applications Console 278 Which Applications are Available to You 278 Which Applications You Can Use 279 What You Have Accomplished 279 How to the Manage and Use Your Applications 280 Subscribing to an Application 280 Unsubscribing from an Application 281 Enabling Applications for Offline Use 281 Disabling Applications from Offline Use 282 Details About Working Offline and Online 282 Knowing Whether You are Offline or Online 282 Choosing to Work Offline or Online 283 Provisioning Your Mobile Thin Client 283 Using XNetClean in Windows 7 (Windows 7 Users Only) 284 H Manually Publishing Applications 285 Publishing Steps (Manual) 285 WSM Publisher File Types 292 Setting Access Tokens 293 Viewing Appsets 295 Viewing the Contents of an Appset 295 Extracting a File from an Appset 295 Testing and Optimizing 296 Loading Appsets 296 Testing Appsets 296 Delivery Testing 297 Application Testing 297 ix Contents Correcting Common Problems 298 Microsoft Icons do not Appear 298 File Associations not Set Properly 298 Miscellaneous Errors 298 Modifying and Updating Appsets 299 Modifying the List of Supported Operating Systems 299 Adding, Removing, or Modifying AppEvent DLLs 299 Details on Handling AppEvents 300 AppEvent Types 301 AppEvent Handlers 301 Handler Configuration 302 Configuration Macro 303 Environment Variables 304 Handling AppEvent Example 304 Publishing Instructions 305 Including Handler Executables in the Appset 305 Setting-up the Registry Configuration 305 Adding the CAED to the Appset 305 I Cloud Desktop Client Configuration and Troubleshooting 307 Configuration 307 Cloud Desktop BIOS Setup Screen Configuration Server Configuration 309 Cloud Desktop Troubleshooting 310 Tables 311 307 x Contents 1 Introduction WSM is a software-based thin-computing solution that allows IT staff to deploy a standardized operating system and applications to stateless thin computers (or thin-computing devices) from a central location. By streaming the entire operating system and applications, WSM makes it possible for thin computers to operate just like a PC, but without the local storage. Streaming the operating system and applications independent of each other makes it easier for IT to backup, update, manage, maintain, and support many desktops with minimal staff. This solution improves security, lowers IT costs, and provides the power and flexibility of a personal computer for the end user while providing the management benefits of thin computing to the IT administrators. WSM streams Windows operating systems and applications on-demand from a server to network computing devices without requiring a local hard drive, local operating system, or local management. By streaming the Windows operating system and applications when users request them, WSM provides users with all of the power of a personal computer, but with lower up-front and ongoing costs, as well as improved security and manageability. With WSM, you can standardize operating system images across your organization and deliver applications based on user roles and responsibilities. Administrators can easily provision new applications or updates to existing applications without having to modify the operating system image. WSM further expands the portfolio of the thin computing solutions that are available from Wyse Technology and allows you to expand the benefits of thin computing throughout your enterprise. In addition to reducing IT costs associated with deploying and maintaining software across the enterprise, WSM helps eliminate downtime when deploying patches to both operating systems and applications. Simply rebooting the device ensures that the client software is upgraded to the latest version. IT administrators also enjoy granular control to ensure consistency of the deployed software across the enterprise. The stateless nature of the devices (unless connected to the corporate network) contribute to a secure environment, while due to the protected system drive, IT departments can quickly recover from virus attacks and other security hazards. Wyse Technology products easily recover from either a hardware failure (by replacing the device) or from a software failure (by overwriting the virtual system drive). 2 Chapter 1 About this Guide This guide is intended for administrators of the WSM system. It provides information and detailed system configurations, to help administrators install, design, and manage a WSM environment. It also explains how to use WSM, manage the availability of software applications for distribution to subscribers, manage application subscription licenses, install and configure published applications, provide subscriber profile and billing information for efficient application usage tracking, and control subscriber access to the WSM system. Finding the Information You Need in this Guide You can use either the Search window or Find toolbar to locate a word, series of words, or partial word in an active PDF document. For detailed information on using these features, refer to the Help in your PDF reader. Wyse Technical Support To access Wyse technical resources, visit http://www.wyse.com/support. If you still have questions, you can submit your questions using the Wyse Self-Service Center at http://support.wyse.com/selfservice.html or call Customer Support at 1-800-800-WYSE (toll free in U.S. and Canada). Hours of operation are from 6:00 A.M. to 5:00 P.M. Pacific Time, Monday through Friday. To access international support, visit http://www.wyse.com/global. Related Documentation and Services Users Guide: Wyse WSMTM has been discontinued and incorporated into this guide. Installation Guide: Wyse WSMTM has been discontinued and incorporated into this guide. Publisher Guide: Wyse WSMTM has been discontinued and incorporated into this guide. Advanced Administrators Guide: Wyse WSMTM has been discontinued and incorporated into this guide. Wyse Cloud Software is available on the Wyse Web site at: http://www.wyse.com/products/software. Wyse Online Community Wyse maintains an online community where users of our products can seek and exchange information on user forums. Visit the Wyse Online Community forums at: http://community.wyse.com/forum. 2 How to Build Your WSM Environment A WSM environment can be as simple or as complex an you need (see "Standard or Advanced: Which WSM Environment is for You?"). Once you decide what kind of WSM environment you need (or at least want to start with), you can begin building it. After you become familiar with your WSM environment (and how it works for you), you can modify your environment (reduce or expand the items you need) at any time. Standard or Advanced: Which WSM Environment is for You? While several factors can influence the WSM environment you need to build, typically the deciding factor is whether or not you need a central point or “Headquarters” to control and manage other geographically dispersed locations or “Sites” that can run WSM independently (although each Site has a full WSM installation, all management and administration is performed from a central point): • If Headquarters are Sites are not required - You can start with a Standard WSM Environment and then modify from there (see "Building a Standard WSM Environment"). • If Headquarters are Sites are required - You can start with an Advanced WSM Environment and then modify from there (see "Building an Advanced WSM Environment"). IMPORTANT: Given the flexibility WSM offers, be sure to consult with your Wyse representative on how to build the WSM environment that is best for you. Building a Standard WSM Environment To build a Standard WSM Environment, you must: 1. Meet all pre-installation requirements as described in "Step 1: Preparing." 2. Install and configure the WSM Core Server as described in "Step 2: Installing and Configuring the WSM Core Server." 3. Log on to the WSM Administrator Console of the Core Server to use the Configuration Wizard to add your Core Server License (required) and enable Active Directory integration with WSM (optional) as described in "Step 3: Starting the WSM Core Server for the First Time." 4. Install and configure the WSM Client as described in "Step 4: Installing and Configuring the WSM Client." 5. (Optional) Install and configure an Edge Server as described in "Step 5: Installing and Configuring a WSM Edge Server." 4 Chapter 2 Building an Advanced WSM Environment To build an Advanced WSM Environment, you must: 1. Meet all pre-installation requirements as described in "Step 1: Preparing." 2. Install and configure the WSM Core Server as described in "Step 2: Installing and Configuring the WSM Core Server." 3. Log on to the WSM Administrator Console of the Core Server to use the Configuration Wizard to add your Core Server License (required) and enable Active Directory integration with WSM (optional) as described in "Step 3: Starting the WSM Core Server for the First Time." 4. Create a Headquarters to control and manage other sites as described in "Creating a Headquarters Site." 5. Install and configure the WSM Client as described in "Step 4: Installing and Configuring the WSM Client." 6. Install and configure the WSM Core Server for a Linked Site as described in "Step 2: Installing and Configuring the WSM Core Server." 7. Log on to the WSM Administrator Console of the Core Server to use the Configuration Wizard to create a Linked Site as described in "Creating a Linked Site." 8. (Optional) Install and configure an Edge Server as described in "Step 5: Installing and Configuring a WSM Edge Server." 3 Configuring and Managing: Using the Administrator Console This chapter provides a brief overview of the functional areas within the WSM system and how to use the Administrator Console to configure and manage your WSM environment. It also provides important information on the general features to help you quickly get started as a WSM administrator. In addition, this chapter contains important information to help you decide whether or not you want to integrate Active Directory with your WSM system. Topics include: • "WSM Functional Areas" • "Getting Started as an Administrator" • · "Logging In" · "Understanding the Overview Page" · "Navigating in WSM" · "Logging Out" "Details About Using Active Directory Integration" · "Understanding the Levels of Active Directory Integration" · "Using Active Directory Integration with and without SSL" WSM Functional Areas The WSM Administrator Console is divided into several functional areas: • Overview - Allows you to quickly view important summary information for each functional area of the WSM system. • Sites - Allows you to configure and manage the WSM Sites, Site Groups, and Site Templates (see "Sites"). • OS (Operating System Images) - Allows you to configure and manage the WSM Operating System Images used for streaming (see "Operating Systems"). • Applications (Application Images) - Allows you to configure and manage the WSM Application Images (used for streaming) and Application Licenses (see "Applications"). • Servers - Allows you to configure and manage the WSM Servers and Server Groups (see "Servers"). • Devices - Allows you to configure and manage the WSM Devices, Device Groups and Device Templates (see "Devices"). • Users - Allows you to configure and manage the WSM User Groups and Users (see "Users"). • Settings - Allows you to configure and manage the system settings of WSM (see "Settings"). • Reports - Allows you to create and view the WSM reports (see "Reports"). In WSM, each functional area has a set of automated tools that helps you to perform your administrator duties and daily activities in that functional area. WSM tracks the status of each of the functional areas necessary to successfully maintain your WSM environment. 6 Chapter 3 TIP: WSM supports Microsoft Internet Explorer (IE) 9.x. IMPORTANT: In addition to the functional areas, the WSM Administrator Console provides a WSM Web link, allowing privileged users to open and use the WSM Web. The WSM Web allows users to monitor WSM Servers, Devices, OS Image and Application Image assignments, and distribution information for all WSM Sites. In addition, users with Administrator or Dispatcher privileges can also schedule and deploy OS Images and OS Image Patches from WSM Web (see "WSM Web"). Getting Started as an Administrator One of the best ways to get started as a WSM administrator is to become familiar with the system and learn how to get where you want to go. After you are familiar with the general features, you can refer to the sections of this guide for more details on specific areas. Topics include: • "Logging In" • "Understanding the Overview Page" • "Navigating in WSM" • "Logging Out" Logging In IMPORTANT: If you have never started WSM and this is your first log-in, refer to "Step 3: Starting the WSM Core Server for the First Time." To log in any time after you have completed your first log-in to WSM, be sure to use your correct Admin Username (default is admin) and Password (default is admin). CAUTION: It is highly recommended that you change your password (see "Passwords Tab"). TIP: If your database has connection problems, the Database Configuration page will automatically appear instead of the Login page. For information on configuring the database, refer to "Database Configuration." To log in to the Administrator Console: 1. Open the Administrator Console Login page by clicking Start > WSM Server > WSM Admin Console on the machine to which you have installed the WSM Core Server (you can also use your Web browser from any machine with access to the WSM Core Server and go to: http://<ipaddress>:8080/admin/). Figure 1 Login page 2. Enter your Admin Username and Password. 3. Click Login to open the Overview page. Configuring and Managing: Using the Administrator Console 7 Understanding the Overview Page The Overview page allows you to quickly view important status information about the WSM system and recent events that have been performed in the system. By clicking a link in the Configuration Warnings area, you can undertake a task or address an issue. Figure 2 Overview page Links on the Overview page include: • About - Provides the WSM Suite Modules (server, client, utilities, and publishing installation packages), Product Licensing information, and other important information. This link is also located on the main page of each functional area. • WSM Web - Allows users to monitor WSM Servers, Devices, OS Image and Application Image assignments, and distribution information for all sites. In addition, users with Administrator or Dispatcher privileges can also schedule and deploy OS Images and OS Image Patches from WSM Web. This link is also located on the main page of each functional area (see "WSM Web"). • Help - Provides documentation and information to help you with task and concept details. This link is also located on the main page of each functional area. • Logout - Allows you to log out of the WSM system. This link is also located on the main page of each functional area. • Functional Areas - Located across the top, these links provide you with quick access to the main functional areas. Functional area links are also located across the top of the main page of each functional area. • Configuration Warnings - Allows you to quickly go to functional areas of the system that require your attention. • Last 5 Events - Provides information on the most recent events of your WSM system (you can use the More Events link to display a Transaction History Report of all events). 8 Chapter 3 Navigating in WSM Navigating in WSM is as easy as clicking your mouse button. WSM is a fully integrated system, allowing you to perform your daily administrator activities quickly and efficiently. WSM is easy to use because common navigation and process features are available throughout the system. For example, you can sort lists according to a heading by clicking on the column heading you want. You can also list your selected heading in ascending or descending order by clicking on that column heading again. Filtering Feature While in WSM, you can filter and sort through various lists to organize items in ways that are helpful to you (click the magnifying lens to expand the filtering feature). For example, you can filter and sort a list of servers by Name, IP Address, OS Image, Application Image, and Status. The WSM filtering feature helps you to locate and go to what you want quickly and efficiently. In some areas, there are multiple filtering steps to help you find the item you want. For example, on the Applications page you can filter by server first, and then filter by application name. Using Messages, Warning Signs, and Quick-Links In addition to the Configuration Warnings area on the Overview page, drop-down messages, warning signs, and Quick-Links are also available throughout the system to help you run and maintain your WSM environment. Logging Out To log out of WSM, click the Logout link. This link is always available in the upper-right corner of the Administrator Console. Configuring and Managing: Using the Administrator Console 9 Details About Using Active Directory Integration This section contains important information about Active Directory to help you decide whether or not you want to integrate Active Directory with your WSM system. IMPORTANT: AD integration should be configured before any Devices or Users are added to the WSM console, otherwise these must be deleted to enable AD integration. Understanding the Levels of Active Directory Integration WSM integrates with Active Directory on two major levels: • Device (Computer Account) Level - On a device level, WSM will automatically manage the creation and maintenance of the computer accounts in the appropriate Active Directory Organizational Unit. • User Level - On a user level, WSM will re-use the group structure that is created in Active Directory. You do not have to re-create the users and groups, that are needed for application assignment, within WSM. An additional user level benefit is single sign-on capability; where user credentials entered during the Windows log-on are used for WSM application streaming authentication. TIP: If Active Directory integration is not enabled, then a user must enter user credentials as follows: For an OS Image mode of Persistent Cache (Shared Mode) - Only the first time they log in to WSM. For an OS Image mode of Volatile Cache (Shared Mode) - Each time they log in to WSM. IMPORTANT: For information on cache modes of an OS Image, see "About OS Images." Using Active Directory Integration with and without SSL WSM can operate with or without Secure Sockets Layer (SSL) with respect to the Active Directory connection. This option is controlled through a WSM system setting (Enable SSL Connection) on the Active Directory Configuration page (see "Active Directory Configuration"). In Active Directory integration without SSL, the communication between the Administrator Console, Active Directory server, and a WSM Server occurs using a non-SSL protocol. The OS Authentication Service must be run with a domain account that has privileges to add and modify computer accounts in Active Directory (members of the default group named Account Operators or Domain Administrators have the privilege to create and maintain computers accounts). The user account and password used while adding the domain must also have these same privileges. For convenience, you can use the same username and password for both the computer account and user account, although it is not necessary. The WSM Server will use these credentials to connect to Active Directory and perform all operations on the device/computer accounts in Active Directory. In Active Directory integration with SSL, WSM uses SSL for communications with the Active Directory server. The digital certificate installed on the Domain Controller can be either a third party certificate or a Microsoft Certificate Authority (CA). In the Microsoft Certificate Authority case, the certificate must be an Enterprise Root CA. Using Active Directory integration with SSL, you have the flexibility to: • Trust any secure Domain Controller - The WSM Server will work with any Domain Controller which has a digital certificate installed. • Enforce the Domain Controller certificate - The digital certificate installed on the Domain Controller must be imported into WSM. After the certificate is imported into WSM, the WSM Server will communicate only with the Domain Controllers that have this certificate. Thus, the enforcement of the certificate is carried out by WSM before the communication between WSM and the Domain Controller can be established. 10 Chapter 3 This page intentionally blank. 4 Sites This chapter describes how to perform routine Site, Site Group, and Site Template management tasks using the Administrator Console. Topics include: • "About Sites" • "Managing Sites" • · "Creating a Linked Site" · "Editing Sites" "Working with Sites" · "Customizing Linked Sites" · "Linked Site Use Cases" • "About Site Groups" • "Managing Site Groups" • · "Adding Site Groups" · "Editing Site Groups" "Managing Site Templates" · • "Adding Site Templates" "Working with Site Templates" About Sites WSM supports the concept of Sites, whereby geographically dispersed locations can run WSM independently; each with its own database instance, yet configured and managed from a central location (Headquarters). Each WSM Site includes a Core Server, database, and optionally, streaming servers. This allows remote offices or locations to continue normal operations even if network connectivity to the central-office or Headquarters is interrupted. All WSM Sites are based on Site Templates and the Site Template can contain the entire configuration information for a Site or remain empty if you want the Site to run independently. A Site Template specifies the OS and Application Images as well as Server Group, Device Group, Device Template, User Groups, and other key parameters. Any change made to a Site Template is propagated automatically to all of the Sites that are “linked” to that Site Template. Thus, Site Templates make it easy to configure and manage large numbers of Sites. Some large WSM deployments may configure and manage hundreds of remote Sites through just one or two Templates. Other deployments may choose to use one Site Template for each Site Group or use a unique Site Template for each of their individual Sites. TIP: For more information on Site Templates, see "Managing Site Templates." 12 Chapter 4 The high-level sequence of steps for setting up a Site-based deployment is: 1. Select one of your Sites to be designated as Headquarters. This is the central Site from which configuration, deployment, and management operations can be initiated (for Sites that are not locally managed). Convert this Site from a Stand-Alone Site to a Headquarters Site using the steps in "Creating a Headquarters Site." 2. From the WSM Administrator Console at the Headquarters Site, create one or more Site Templates using the steps in "Adding Site Templates." This includes registering and configuring OS and Application Images, Server Groups, Device Groups, Device Templates, and User Groups that will be used by the Site Templates. These Site Templates will be used during the creation and configuration of remote Sites. 3. From the WSM Administrator Console at each remote WSM installation, convert its Site category from a Stand-Alone Site to a Linked Site, as described in "Creating a Linked Site." Note that remote Sites cannot be added directly from Headquarters; the operation must be initiated from the remote Site. TIP: For more information on Site-based deployment and Linked Site use cases, see "Working with Sites." Managing Sites The Sites page (Sites > Sites) allows you to quickly view and manage the WSM Sites that are available (see Table 1). It also allows you to easily display the Sites you want by using the filtering feature. TIP: Every new Core Server installation is set up as a Stand-Alone Site by default and can be configured manually to become a Headquarters or Linked Site by using the WSM Sites Configuration page as described in "Site Configuration Settings." If ever needed in the future (after your Core Server installation is complete for your Site), you can reassign a Site category using the WSM Sites Configuration page. Figure 3 Sites page Although the Sites page shows you all of the Sites available in the WSM system, you can use the following guidelines to view the Sites you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Site (use only letters, numbers, dashes, spaces, the @ character, and periods). • Site Category - Category of a Site (all, Stand-Alone, Linked, Site Template, Headquarters) • Site Group - Name of the Site Group to which the Site is assigned. • Max Rows - Maximum number of rows to display on a page (enter the number). After entering your criteria, click Filter to view the results. You can then select the Sites you want, and begin performing your tasks. 13 Sites Table 1 provides a quick overview of routine Site tasks. Table 1 Routine Site Tasks Tasks You Can Do How Details Add a Stand-Alone Site to the system. Use the Core Server installation procedures in "Step 2: Installing and Configuring the WSM Core Server." After adding a Stand-Alone Site, you can keep it, or convert it to a Headquarters Site or a Linked Site. To configure a Site to be a Headquarters, see “Creating a Headquarters Site” on page 14. To configure a Site to be a Linked Site, see “Creating a Linked Site” on page 15. NOTE: You can reassign a Site category by using the WSM Sites Configuration page as described in "Site Configuration Settings." Create a Headquarters Site. Use the Core Server installation procedures in "Step 2: Installing and Configuring the WSM Core Server" to add a Stand-Alone Site, and then convert it to a Headquarters Site. “Creating a Headquarters Site” on page 14. Create a Linked Site. Use the Core Server installation procedures in"Step 2: Installing and Configuring the WSM Core Server" to add a Stand-Alone Site, and then convert it to a Linked Site. “Creating a Linked Site” on page 15. Edit a Site in the system. On the Sites page, click the Name link of the Site you want to edit and make your changes. “Editing Sites” on page 16. Delete a Site from the system. On the Sites page, select the check box next to the name of the Site you want in the Name area, click Delete, and confirm the deletion. The Site is deleted and is no longer shown in the list of available Sites on the Sites page. You can only delete Linked Sites from Headquarters; a local (default) site cannot be deleted. 14 Chapter 4 Creating a Headquarters Site 1. After using the Core Server installation procedures in "Step 2: Installing and Configuring the WSM Core Server" to add a Stand-Alone Site, log in to the WSM Administrator Console at the location of the installation. 2. Click Settings to open the Settings page, and then click Site > Site Configuration tab to open the WSM Sites Configuration page. Figure 4 Site Configuration page - Headquarters Site example 3. Select the Headquarters Site option. 4. Enter the Name of the Site. 5. Enter the Site Description. 6. Select the options you want. TIP: For detailed information on using the available options, see "Working with Sites." 7. Click Setup Site. After creating the Headquarters Site, you can view the Server Details page to see that the Headquarters Core Server Services are successfully running (Status is Up on each service) by clicking the Servers tab, and then clicking the Name link of the Headquarters Core Server. 15 Sites Creating a Linked Site 1. After using the Core Server installation procedures in "Step 2: Installing and Configuring the WSM Core Server" to add a Stand-Alone Site, log in to the WSM Administrator Console at the location of the installation. 2. Click Settings to open the Settings page, and then click the Site Configuration link to open the WSM Sites Configuration page. Figure 5 Site Configuration page - Linked Site example 3. Select the Linked Site option, and then configure the following (all items/instructions should be provided by the Headquarters Administrator): • Enter the Name of the Site. Note that the site name must be unique, and not already registered at Headquarters. • Enter the Site Description. • Enter the Site Code. This can be a maximum of five characters, and is used as a prefix to the device-template name, when creating names for new devices in the system. It is recommended that this code is an abbreviation of the Site name, or otherwise indicative of this Site. This will result in device-names that clearly indicate which Site they belong to. Note that the device-name is also used as the hostname of the device, and will be registered into Active Directory if Active Directory integration is enabled. • Enter the Headquarters Server IP. • Select or clear the Headquarter in Https check box. CAUTION: Selecting this option will cause the remote Site to use HTTPS for all communication with the Headquarters site. If you select this option, you must have registered a server certificate at the Headquarters Site. Further, if the server certificate is not signed by a well-known CA, you will need to register the Root CA certificate with WSM before attempting to convert this remote Site to a Linked Site. • Enter the Site Template Name. • Enter the Site Group Name. 4. Click Setup Site. After creating the Linked Site, you can view the Server Details page to see that the Linked Site Core Server Services are successfully running (Status is Up on each service) by clicking the Servers tab, and then clicking the Name link of the Linked Site Core Server. 16 Chapter 4 Editing Sites TIP: After editing the settings, be sure to click Save Changes (the Site is then modified and can be viewed in the list of available Sites on the Sites page). Summary (To Edit): On the Sites page (Sites > Sites), click the Name link of the Site you want to edit to open and use the Site Details page. CAUTION: The Site Details page you see depends on which Site you select. If you click on a “local” Site name (using either the Administrator Console at Headquarters, or using the Administrator Console at a remote Site), the local Site view will be displayed (Figure 6). However, if you click on the Site name of any Linked Site using the Administrator Console at Headquarters, the Linked Site view will be displayed (Figure 7). Tasks (links) available for use on the Site Details page depend on the type of Site you are modifying (you will only see links that are relevant to your task). Figure 6 Site Details page - local Site view Figure 7 Site Details page - Linked Site view from Headquarters Detailed Guidelines (To Edit): • Enter a Name (you cannot change the name of a Linked Site until after you reassign a Linked Site category to a Stand-Alone Site by using the WSM Sites Configuration page as described in "Site Configuration Settings"). • (Optional) Enter a Description. • The Site Group of the Site is shown. • The Site Type of the Site is shown. • (Headquarters Only) The Site Template of the Headquarters is shown. 17 Sites • Optional Related Tasks you can perform using the Site Details page: • (Remote Site Details page, at Headquarters) Refresh Site - Click the Refresh Site link to send a message to the remote Site to synchronize with Headquarters (to obtain updated configuration information from Headquarters and send updated status information to Headquarters). • (Site Details page at the Administrator Console of a Remote Site - not Headquarters) Sync with Template - Click the Sync with Template link to have the remote Site synchronize with Headquarters (to obtain updated configuration information from Headquarters and send updated status information to Headquarters. • (Local Site Only) Change the Core Server Assignment - Use the Change Core Server Assignment drop-down to select the Core Server. • (Local Headquarters or Stand Alone Site Only) Aggregate Local Data - Click Aggregate Local Data to update the data that will be used in the aggregated reports (see "Overview of the Reports Page"). • (Site Templates Only) Generate a Site Template XML - Click the Generate Site Template XML link to open and use the File Download dialog box (Site Template XMLs are used for disaster recovery purposes in large WSM environments with complex Site designs and are discussed in Advanced Administrators Guide: Wyse WSMTM). • (Local Site and Templates Only) Add a Server Group to this Site - Click the Add Server Group to this Site link to open and use the Adding Server Group wizard (see "Adding Server Groups"). • (Local Site and Templates Only) Add a Device Group to this Site - Click the Add Device Group to this Site link and follow the wizard (see "Adding a Device Group"). • (Local Site and Templates Only) Edit a Server Group belonging to this Site Click a Name link in the Server Groups Belonging to area to open and use the Server Group Details page (see "Editing Server Groups"). • (Local Site and Templates Only) Edit a Device Group associated with this Site Click a Name link in the Device Groups Associated with area to open and use the Device Group Details page (see "Editing Device Groups"). • (Local Site Only) Edit a Server belonging to this Site - Click a Name link in the Servers Belonging to area to open and use the Server Details page (see "Editing Servers"). • (Local Site Only) Edit a Device belonging to this Site - Click a Name link in the Devices Belonging to area to open and use the Devices Details page (see "Editing Devices"). • (Local Site Only) Delete a Device belonging to this Site - Select the check box next to the name of the Device you want in the Devices Belonging to area, click Delete Selected, and confirm the deletion. • (Local Site Only) Send supported commands to Devices in the system - Select the Devices you want and click Send Command to open and use the Send Device Command page (see "Sending Commands to Devices"). • (Local Site Only) Abort the previously scheduled commands to Devices in the system - Select the Devices you want, click Abort Command to open a message confirming the removal of the commands, and then click OK to abort the commands. • (Local Site Only) Edit an OS Image associated with this Site - Click a Name link in the OS Images Associated with area to open and use the OS Image Details page (see "Editing OS Images"). • (Local Site Only) Edit an Application Image associated with this Site - Click a Name link in the Application Images Associated with area to open and use the Application Image Details page (see "Editing Application Images"). 18 Chapter 4 Working with Sites This section contains expanded information on Site-based deployment and Linked Site use case recommendations. Customizing Linked Sites All WSM Sites are based on Site Templates and the Site Template can contain the entire configuration information for a Site or remain empty if you want the Site to run independently. The behavior of Linked Sites can be controlled (from the Headquarters Administrator Console Only) using the following options (see "Linked Site Use Cases" for recommendations): • Allow Multiple Server/Device Groups for Site Template (on the Site Configuration page; see "Site Configuration Settings") - The Allow Multiple Server/Device Groups for Site Template option controls how many User-Created server and device groups can be assigned to a Site Template (if not selected the Site Template server and device groups are limited to only one User-Created Server Group and only one User-Created Device Group; if you want to use multiple User-Created server and device groups, be sure to select this check box). • Preserve Linked Site Local Data (on the Site Configuration page; see "Site Configuration Settings") - By default, all locally created Server Groups, Device Groups, and Device Templates are deleted during the Site Template synchronization. If the Preserve Linked Site Local Data option is selected, then locally created entities are not deleted during the Site Template synchronization. However, if there is a conflict (for example, an image exists at a Linked Site that has the same name as a Headquarters image), entities can be deleted from a Linked Site during the Site Template synchronization. • Locally Managed Sites (on the Site Configuration page; see "Site Configuration Settings") - By default, WSM does not allow Site administrators to register OS Images or Application Images from a Linked Site (they can only be registered from Headquarters). However, when the Locally Managed Sites option is selected, OS Images or Application Images can be registered from a Linked Site. Although WSM does not enforce any naming convention, it is recommended that entities created from a Linked Site follow a naming convention (such as prefixing the names with a Site code) so that there is no naming conflict with any Headquarter entities. when the Locally Managed Sites option is selected, the Preserve Linked Site Local Data option is automatically enabled for the locally managed Sites so that locally created entities are not deleted during Site Template synchronization. Note that the names of all entities (such as OS Images, Application Images, Server Groups, Device Groups, and Device Templates) inherited from the Site Template are suffixed with (HQ) to differentiate them from locally created entities in the relevant summary pages. Note also that changes made to the entities inherited from the Headquarters Site Template are overwritten during next Site Template synchronization (for example, if a Site administrator deletes a Device Group inherited from the Headquarters Site Template, the Device Group will be restored during the next Site Template synchronization. • Allow HQ Image Patch at Linked Site (on the Settings page; see "Managing Settings") - By default, WSM does not allow Linked Site administrators to create OS Image and Application Image patches at the Linked Site if the base Image was originally registered at Headquarters. However, when the Allow HQ Image Patch at Linked Site option is selected, Linked Site administrators can create an image patch at the Linked Site (instead of at the Headquarters Core Server) for the image that was originally registered at Headquarters. Use the following general guidelines: a. Follow the normal OS Image or Application Image patch procedure, however, for an OS Image patch, finalize the patch at the Linked Site. This will create a delta for the 19 Sites OS Image patch. The OS Image patch will not be distributed to the streaming servers of the Linked Site, nor will the patch be pre-processed. b. Copy the patched Image and corresponding delta file to the Headquarters Streaming directory. c. Register the OS Image or Application Image patch with the existing delta at Headquarters. For an OS Image patch, be sure that the name of the OS Image patch you are registering at Headquarters exactly matches the name of the OS Image patch that was finalized at the Linked Site. d. After the OS Image or Application Image patch is validated at Headquarters, it will be pre-processed and enabled for distribution. Note that at the Linked Site, after the content scheduling, the synchronization period configuration will schedule the patch for deployment. Note also that the Linked Site where the patch was originally generated will also schedule the patch for deployment. e. After the OS Image or Application Image patch has been deployed/enabled on Linked Site core servers, the patch will be scheduled to be deployed to Linked Site streaming servers. Linked Site Use Cases Note the following use cases and recommendations. Case 1: Uniform Linked Sites with a Single OS Image Use the following recommendations: • Allow Multiple Server/Device Groups for Site Template option - If all your devices boot using the same OS Image, and the servers at the Linked Site can be used in a load-balanced environment, then a single Server Group and a single Device Group can meet the requirements and it is recommended that you clear (do not select) the Allow Multiple Server/Device Groups for Site Template option on the Site Configuration page. The advantage in doing so is that any new edge server added to the Linked Site is moved to the User-Created Server Group and server image assignments are automatic. In addition, any new devices are automatically moved to the User-Created Device Group and device image assignments are automatic. • Preserve Linked Site Local Data option - If your Linked Sites are uniform, but need multiple/different Device Templates, then it is recommended that you select the Preserve Linked Site Local Data option on the Site Configuration page. Otherwise, locally created entities would be deleted during Site Template synchronization. • Locally Managed Sites option - If most of your Linked Sites are similar (for example, you have the same OS Images, Application Images, User Groups, Server Groups, Device Groups) and image management can done at Headquarters, then it is recommended that you clear (do not select) the Locally Managed Sites option on the Site Configuration page. This will centralize management and provide highly scalability (less administrative overhead). Case 2: Uniform Linked Sites with Multiple OS Images Use the following recommendations: • Allow Multiple Server/Device Groups for Site Template option - If the devices in your Linked Sites require different OS Images, then they must be put into different groups and it is required that you select the Allow Multiple Server/Device Groups for Site Template option on the Site Configuration page. Note that in this case the server and device group assignments are not automatic. The Linked Site administrator must use the Administrator Console to assign servers to the appropriate groups and devices to the appropriate groups. • Preserve Linked Site Local Data option - If your Linked Sites require locally created entities (such as Device Templates), then it is recommended that you select the Preserve Linked Site Local Data option on the Site Configuration page. 20 Chapter 4 Case 3: Linked Sites that are Not Uniform Use the following recommendation: • Locally Managed Sites option - If your Linked Sites are different from each other and have little commonality, then it is recommended that you select the Locally Managed Sites option on the Site Configuration page. This will allow a locally managed Linked Site to register OS Images and Application Images, and also allow the patching of these images from the Linked Site. 21 Sites About Site Groups TIP: Site Groups are intended only for environments with a large number of WSM Sites. First time users and or users with small deployments can skip this section. Site Groups enable you to organize or group together several Sites for easier management. The grouping of Sites can be done in any manner that suits your needs. There are no hard rules on the number of Sites per Site Group. Some groups may have just one Site each, while other groups may have dozens or even hundreds of Sites. Typically, grouping is based on the following factors: • Geographic - Where Sites may be grouped together based on their location (such as a building, campus, city or state). • Load-balancing and Throttling of Content Distribution (deployment of OS Images, Application Images, and Patches) - Images can be deployed on a Site Group basis (one or more groups at a time). For deployments with hundreds or thousands of Sites, this is a convenient way to deploy images to many remote Sites with a single mouse click. Administrators can control the load on their WAN by using smaller numbers of Sites in each group and by using the bandwidth throttling features (Limit Content Distribution Bandwidth and Allow Alternative Bandwidth options on the Site Group Details page) as needed (see also Limit Global Content Distribution Bandwidth in "Content Distribution Settings"). • Customized OS Images for Different Sites - If one set of Sites will share a common OS Image, and a different set will be using a different OS Image, it would be convenient to organize them into different Site Groups (note that in this case, you would use a different Site Template for each group). Managing Site Groups The Site Groups page (Sites > Site Groups) allows you to quickly view and manage the Site Groups that are available (see Table 2). It also allows you to easily display the Site Groups you want by using the filtering feature. Figure 8 Site Groups page Although the Site Groups page shows you all of the Site Groups available in the WSM system, you can use the following guidelines to view the Site Groups you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Site Group (use only letters, numbers, dashes, spaces, the @ character, and periods). 22 Chapter 4 After entering your criteria, click Filter to view the results. You can then select the Site Groups you want, and begin performing your tasks. Table 2 provides a quick overview of what you can do using the Site Groups page. Table 2 Routine Site Group Tasks - Site Groups page Tasks You Can Do How Details Add a Site Group to the system. Click the Add button and follow the wizard. “Adding Site Groups” on page 22. Edit a Site Group in the system. Click a Name link in the Site Groups page and make your changes. “Editing Site Groups” on page 23. Delete a Site Group from the system. Select the check box next to the name of the Site Group you want in the Site Groups area, click Delete, and confirm the deletion. The Site Group is deleted and is no longer shown in the list of available Site Groups on the Site Groups page. You can also delete a Site Group by using the Delete this Site Group link on the Site Group Details page. Deleting a Site Group reassigns all Sites in the group to the Default Site group. IMPORTANT: You cannot delete the Default Site group. Adding Site Groups Summary (To Add): On the Site Groups page (Sites > Site Groups), click the Add button and follow the wizard. Detailed Guidelines (To Add): 1. On the Site Groups page (Sites > Site Groups), click the Add button to open the Add Site Group wizard. Figure 9 Add Site Group wizard 2. Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and periods). 3. (Optional) Enter a Description. 4. Click Next to open the Assign Sites page. 5. Determine the Sites you want to include in the Site Group using the assignment page. 6. Click Finish. The Site Group is added to the list of Site Groups on the Site Groups page. 23 Sites Editing Site Groups TIP: After editing the settings, be sure to click Save Changes (the Site Group is then modified and can be viewed in the list of available Site Groups on the Site Groups page). Summary (To Edit): On the Site Groups page (Sites > Site Groups), click the Name link of the Site Group you want to edit to open and use the Site Group Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "Sites Tab" Details Tab (Default Group Only) Information is displayed (you cannot edit the information). Figure 10 Site Groups: Details tab - Default Site Group Figure 11 Site Groups: Details tab - Non-Default Site Group 24 Chapter 4 (Non-Default Groups Only) Summary (To Edit): Use the Details tab to enable and configure the settings for the current Site Group. After configuring, be sure to click Change Configuration to save your settings. Detailed Guidelines (To Edit): • Enter the Name. • (Optional) Enter a Description. • You can also use the Limit Content Distribution Bandwidth and Allow Alternative Bandwidth options as needed to limit the bandwidth of content distribution transfer for files (OS Images, Application Images, and Patches) that are copied to a Linked Site from the Headquarters repository (if these options are not used, the maximum possible bandwidth will be used by system). Enter the start and end times for the Bandwidth limitations you enter (in kilobytes per second). Be aware that: · The Linked Site must be synchronized using a template synchronization for any changes to be effective. · If the current time does not fall within the start and end time range for the Limit Content Distribution Bandwidth setting, the content distribution transfer is paused, unless the Allow Alternative Bandwidth option is used. If paused, the status of the content distribution is appropriately changed in the Content Distribution Summary page (Settings > Track Content Distribution). · If the current time does not fall within the start and end time range for the Allow Alternative Bandwidth setting, the content distribution transfer is paused. If paused, the status of the content distribution is appropriately changed in the Content Distribution Summary page (Settings > Track Content Distribution). TIP: The Limit Content Distribution Bandwidth and Allow Alternative Bandwidth options allow the Headquarters Administrator to override the Limit Global Content Distribution Bandwidth option settings on the Content Distribution Settings page (see "Content Distribution Settings") and control/limit the bandwidth of content distribution transfer for files that are copied to a Linked Site from the Headquarters repository. Note that a Linked Site Administrator can further override these option settings for the individual Linked Site by using the Limit Global Content Distribution Bandwidth option on the Content Distribution Settings page of the Administrator Console of the Linked Site. Administrators can view log files for the following strings to check various metrics during content distribution transfer: —Site Bandwidth is set to: —Transferred (xyz) Megabytes. Current File Transfer Bandwidth (kbytes/sec): “ —Bandwidth has changed to: • Optional Related Tasks you can perform using the Site Group Details page: • Move Sites to a Different Site Group - Click the Move Sites to Different Site Group link to open and use the Move Sites wizard. CAUTION: You cannot move the Headquarters Site from the Default Site Group to another user-created Site Group. 25 Sites Sites Tab Summary (To Edit): You can use the Sites tab to reassign Sites (click the Reassign Sites button and follow the wizard) and to open the Site Details page for a selected Site (click on the Site name in the Name area - see "Editing Sites"). Figure 12 Site Groups: Sites tab Detailed Guidelines (To Reassign): • Select the Sites you want to move. • Select the Site Group to which you want to assign the Site. 26 Chapter 4 Managing Site Templates The Site Templates page (Sites > Site Templates) allows you to quickly view and manage the WSM Site Templates that are available (see Table 3). It also allows you to easily display the Site Templates you want by using the filtering feature. Figure 13 Site Templates page Although the Site Templates page shows you all of the Site Templates available in the WSM system, you can use the following guidelines to view the Site Templates you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Site Template (use only letters, numbers, dashes, spaces, the @ character, and periods). After entering your criteria, click Filter to view the results. You can then select the Site Templates you want, and begin performing your tasks. Table 3 provides a quick overview of what you can do using the Site Templates page. Table 3 Routine Site Template Tasks - Site Template page Tasks You Can Do How Details (Headquarters Only) Add a Site Template to the system to manage the Linked Sites associated with it. Click the Add button and enter the required information on the Create Site Template page. “Adding Site Templates” on page 27. Delete a Site Template from the system. Select the check box next to the name of the Site you want in the Sites area, click Delete, and confirm the deletion. The Site is deleted and is no longer shown in the list of available Sites on the Sites page. Sites 27 Adding Site Templates (Headquarters Only) Site Templates allow you to easily manage the Linked Sites associated with them. All WSM Sites are based on Site Templates and the Site Template can contain the entire configuration information for a Linked Site or remain empty if you want the Linked Site to run independently. You can use one Site Template for each Site Group or use a unique Site Template for each of their individual Sites. Use the following high-level sequence of steps for creating a Site Template: 1. From the Sites page, add a Site Template (Sites > Site Templates > Add). This Site Template contains the information you want to be used by the Linked Sites. By default, a Site Template requires at least one Server Group, one Device Group, one Device Template, and one OS Image (provided by Headquarters or the Linked Site). Note that if the Locally Managed Sites check box (on the Site Configuration page - see "Site Configuration Settings") is not selected, WSM enforces the rules for the Site Template and these required Site Template server and device groups must be User-Created and not defaults (for locally managed Sites, WSM does not enforce any rules for the Site Template as Server Groups, Device Groups, and images can be added from the Linked Site). Note also that if the Allow Multiple Server/Device Groups for Site Template check box (on the Site Configuration page) is not selected, these required Site Template server and device groups are limited to only one User-Created Server Group and only one User-Created Device Group (if you want to use multiple User-Created server and device groups, be sure to select the Allow Multiple Server/ Device Groups for Site Template check box - see "Site Configuration Settings"). TIP: For more information on Site-based deployment and Linked Site use cases, see "Working with Sites." 2. Create a Server Group for the Site Template. 3. Add an OS Image and assign it to the Site Template. 4. Assign the OS Image to the Server Group of the Site Template. 5. Once the OS Image is ready, change the mode to Shared Persistent or Shared Volatile and click the Allow Content Distribution link on the Content Distribution tab of the OS Image Details page. IMPORTANT: For information on cache modes of an OS Image, see "About OS Images." 6. Create a Device Group for the Site Template and assign it to the Server Group you created. 7. Assign the OS Image to the Device Group. 8. Create a Device Template for the Site Template and assign the Device Group to it. 9. You now have the minimum information needed for a Site. At this point, you can also assign Application Images to the Site Template and the Server Group of the Site Template. Summary (To Add): On the Site Templates page (Sites > Site Templates > Add), click the Add button to open and use the Create Site Template page. Detailed Guidelines (To Add): 1. On the Site Templates page, click the Add button to open the Create Site Template page (Sites > Site Templates > Add). 28 Chapter 4 Figure 14 Create Site Template page 2. Enter a Site Template Name (use only letters, numbers, dashes, spaces, the @ character, and periods). 3. (Optional) Enter a Site Template Description. 4. Enter a Server Group Name. 5. Enter a Device Group Name. 6. Enter a Device Template Name. 7. Enter an OS Image. 8. Click Create Template. The Site Template is added to the list of Site Templates on the Site Templates page. CAUTION: A Site Template configuration is not complete (so you can use it to manage your Linked Sites) until you add the following: Server Group - On the Site Template Details page, click the Add Server Group to this Site link to open and use the Add Server Group wizard (see "Adding Server Groups"). Device Group - On the Site Template Details page, click the Add Device Group to this Site link and follow the wizard (see "Adding a Device Group"). Device Template - On the Settings page, click the Manage Device Templates link, and then add a device template (see "Adding Device Templates"). OS Image - On the Operating Systems page, click the Add OS Image link to open and use the Add OS Image wizard (see "Registering OS Images"). Sites 29 Working with Site Templates When working with Site Templates be aware of the following features: • Publishing and Restoring a Site Template - With this feature a Site template will be available to a Linked Site only after it is published at Headquarters. Different versions of Site Templates can be published, but only the latest published version of a Site Template is synchronized with the Linked Site. Previous versions of WSM generated the Site Template XML every time it was requested by a Linked Site. This process can be a performance issue and susceptible to damage caused by user errors. • Restoring a Site Template to the Last Published Version - This feature allows administrators to revert data for a Linked Site that may been changed after the Site Template was published. 30 Chapter 4 This page intentionally blank. 5 Operating Systems This chapter describes how to perform routine Operating System (OS) Image management tasks using the Administrator Console. Topics include: • "About OS Images" • "Managing Operating Systems" · "Registering OS Images" · "Editing OS Images" About OS Images An OS Image is a file representing a snapshot of a Windows Operating System installation on a device. An OS Image contains what is found on a physical Hard Disk Drive (HDD), such as disk partitions and a file system containing files and folders. Unlike a physical HDD, an OS Image appears as a file representing a “virtual” disk drive and resides at the WSM Server. A device can be booted from this virtual disk drive via WSM over the network, providing the same user experience as booting from a physical HDD with a Windows OS installed. Data Contents of an OS Image: • OS Data - The files and folders that comprise the Windows OS installation. This data is copied from the Windows installation on the physical HDD of the reference device you denote as the default device that will be used to apply updates or patches that are needed to an OS Image (see "Updating OS Images and Application Images"). • Meta Data - The OS Image attributes used and maintained by WSM. For example, name, version, descriptions, cache modes, multicast, and safe boot settings. Supported Formats of an OS Image: • Legacy - A WSM proprietary format that is supported in all WSM releases. The instructions in this chapter describe how to create an OS image in a Legacy format. • VHD - Virtual Hard Disk (VHD) is a file format adopted by Microsoft to represent a virtual hard disk drive format supported by Microsoft Virtual PC and Virtual Server. WSM v5.0.1 and later supports the VHD image format. For instructions on how to create a new VHD OS Image and how to convert an existing VHD image for WSM streaming, see "Using a VHD Image." States of an OS Image: • Unregistered - When an OS image is first created, it is not registered to the WSM database. An unregistered OS Image can be booted to the reference device from the Core Server only. It cannot be shared by multiple devices and cannot be booted from a non-Core Server. Any changes made to the OS image will be written directly to the OS Image file. After the administrator has completed customizing the OS image and has it ready for deployment to other devices (for example, installs additional applications or drivers, changes the wallpaper, joins the domain, configures KMS licensing behavior and so on), the administrator can register the OS Image using the WSM Administrator Console. 32 Chapter 5 • Registered - Once an OS image is registered, it is added to the WSM database and put into “shared” mode. The registered OS Image can be assigned to servers or server groups, as well as devices or device groups, and can be used to boot multiple devices. Further updates to the OS image will no longer be written to the OS image directly and will affect only specific devices and partitions. To update the OS data within an OS image so that the changes are available to all devices after it is registered, the “Patching” process must be used. Both the Patch Os Directly and Patch operations are available for OS Images in this state (for instructions on how to perform OS patching, see OS patching). In addition, administrators can also update the meta data of the OS Image, and can unregister an OS Image from WSM database if the OS Image is no longer used. • Distributed - Before an OS Image is distributed, it remains in the Core Server and can be streamed from the Core Server only. To make the OS Image available from other servers, it must first be “distributed” to other servers and Linked Sites. Once an OS Image is distributed, the OS Image meta data cannot be changed. Administrators can update the OS Data only through the “Patching” process (the “Patch Os Directly” process is no longer available for distributed OS Images (for instructions on how to perform OS patching, see OS patching). Cache Modes of an OS Image Once an OS Image is registered to the WSM database, multiple devices can boot from the same OS Image simultaneously. Similar to a physical HDD, the Operating System writes to the virtual disk (the OS Image) constantly during a streaming session. WSM protects the OS image from being modified by different streaming sessions for different devices by redirecting all updates to the OS Image to individual write cache files. There is one unique write cache file for each OS Image partition for each client device. Therefore, updates to cache files affect only specific OS Image partitions for specific devices. The write cache files, together with the read-only OS image, define the virtual disk content for a specific streaming session. Each cache file can be in either Persistent cache mode or Volatile cache mode: • Persistent cache mode - In this mode the Write Cache file is persistent across reboots (that is, any changes made to the OS Image are stored and are available to users when they reboot their device). • Volatile cache mode - In this mode the Write Cache file is discarded when the device reboots (that is, after the device reboots the device is always returned to the original base OS Image - resulting in a pristine image every boot). Volatile cache mode is best suited for classrooms and kiosks where user changes do not need to be maintained. TIP: Different cache modes can be selected for different partitions within the same OS Image. Note that when a partition within an OS Image is patched, all cache files associated with the patched OS Image partition will be discarded. Gold OS Images Using WSM, a single OS Image can be streamed to multiple client devices as long as the devices have similar hardware characteristics. In specific, the mother board, the PXE capable network card, and the video card must be the same. For example, all Wyse Z class thin client devices can be streamed from an OS Image created from a Z class reference device. Instructions in this chapter describe how to create an OS Image to support a single hardware platform. A gold OS Image refers to an OS image which supports multiple heterogeneous client platforms where the mother board, network card, or video card are different. For example, a gold OS Image can be created to boot both Wyse Z class thin clients and Dell Optiplex 9010 desktops. For instructions on how to create a gold OS Image, see "Using the Wyse UniPlat Tool." Operating Systems 33 Multicast Delivery of an OS Image By default, OS Image data is delivered to devices via Unicast packets. Multicast is a mechanism used in UDP communication to efficiently deliver a set of packets to multiple clients. It is a one-to-many communication. Instead of sending the same packets repeatedly for each recipient, the source sends the packets only once for all recipients who are listening at that time. WSM can use the multicast protocol to deliver a portion of a common OS image to multiple client devices which share the same OS Image. This feature reduces network traffic significantly when multiple clients share the same OS Image boot up simultaneously. IMPORTANT: In order to use Multicast for an OS Image, all partitions within the image must be in Volatile cache mode. TIP: For more information on using multicast, go to the Wyse Knowledge Base and search for WSM Multicast Streaming: Best Practices. Managing Operating Systems The Registered OS Image page (OS > Registered) and Unregistered OS Image page (OS > Unregistered) allow you to quickly view and manage the WSM operating systems that are available (see Table 4). Although, the Registered OS Image page shows you all of the registered Operating System Images available in the WSM system, you can use the filtering feature to view the operating systems you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of an operating system for client support (use only letters, numbers, dashes, spaces, the @ character, and periods). After entering your criteria, click Filter to view the results. You can then select the OS Images you want, and begin performing your tasks. Figure 15 Registered OS Image page 34 Chapter 5 Figure 16 Unregistered OS Image page Table 4 provides a quick overview of routine management tasks. Table 4 Routine Operating System Management Tasks Tasks You Can Do How Details Register an OS Image to the system for streaming. On the Unregistered OS Image page (OS > Unregistered), click the Register button for the Unregistered OS Image to open and use the Register Operating System page. “Registering OS Images” on page 35. IMPORTANT: To allow the OS Image to be streamed, be sure to use the Server Groups tab to open and use the Assign Server Groups For OS Image page as described in "Editing OS Images." Edit an OS Image in the system. On the Registered OS Image page (OS > Registered), click the Name link of the Operating System you want to edit to open the OS Image Details page, and then use the tabs to edit the settings. “Editing OS Images” on page 37. Unregister an OS Image from the system. On the OS Image Details page (OS > Registered > Name link), click the Unregister button for the Registered OS Image to remove it from WSM use. The OS Image is no longer shown in the list of available OS Images on the Registered OS Image page. Operating Systems 35 Registering OS Images CAUTION: If no file exists for you to select, you must capture an OS Image and place the file into the OS Images folder located where you installed the WSM Core Server as described in "Step 2: Installing and Configuring the WSM Core Server" (for example, C:\Program Files\Wyse\WSM\StreamingDir\OS Images). Summary (To Register): On the Unregistered OS Image page (OS > Unregistered), click the Register button for the Unregistered OS Image you want to open and use the Register Operating System page. Detailed Guidelines (To Register): 1. On the Unregistered OS Image page (OS > Unregistered), click the Register button for the Unregistered OS Image you want to open the Register Operating System page. Figure 17 Register Operating System page 2. Select the First Partition Mode for the OS Image (select the cache mode for each partition within the OS Image - either Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode)). Persistent Cache (Shared Mode) and Volatile Cache (Shared Mode) are the operating system options in which OS Images can be delivered to the device (see "About OS Images"). 3. Click Register. The OS Image is added to the list of available OS Images on the Registered OS Image page. Clicking the name link for a registered OS Image opens the OS Image Details page to allow you to make further configurations if necessary (see "Editing OS Images"). IMPORTANT: If the OS Image you want to register was captured but never streamed, you must be sure to use the Assign Reference Device drop down list of the OS Image to view instructions for booting the OS Image from a reference device before registering the OS Image. A newly created OS Image must be streamed to a reference device at least once before it can be registered. Use the Assign Reference Device button to assign the OS Image to a new reference device or to switch to a different reference device for the OS Image. At this point, the OS Image has been registered at the Core Server only. It is not yet available at streaming servers or at remote Sites. You may want to customize this OS Image further, before making it available to other servers. The following are possible next steps: • Start booting multiple devices from this OS Image on the Headquarters Core Server. • Further customize the image before distributing to other servers/Sites (you can do so by using the Patch Os Directly or Patch process as described in "Updating an OS Image"). 36 Chapter 5 • If this is a newly captured OS Image, it is recommended that you boot a device from this OS Image at least once, before setting it in shared mode (either Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode)). This will allow peripheral discovery and driver registration to finish, and avoids messages such as new hardware discovered or reboot your system. This is also a good time to review and customize the OS Image to suit your needs. After customizing has been completed, shut down the device. • Distribute the image to other servers/Sites. Note that once the image is distributed, the meta data of the OS Image cannot be changed. To distribute the image, click the Distribute link on the Content Distribution tab of the OS Image Details page. Until you click this link, the OS Image will not be copied to streaming servers or to remote Sites. Note that this is a one-time operation for each OS Image. Once you have clicked the Distribute link for an OS Image, the OS Image is effectively locked down, and no configuration changes can be made to the OS Image from that point onward. Changes to the content of the OS Image can be done only through the OS Image Patch Process. • To allow the OS Image to be streamed from streaming servers, the OS Image must be assigned to those servers. Click the Assign link on the Server Groups tab to open and use the Assign Server Groups For OS Image page as described in "Editing OS Images." Note that if the OS Image has been assigned to a Site Template, be sure to assign the OS Image to the Server Group that is associated with that Site Template. TIP: Once an OS Image has been assigned to a Server Group, the OS Image will automatically be copied to all of the streaming servers in that Sever Group. You can track the content distribution process from the OS Image Content Distribution tab by clicking on the name of the image/patch. (Content Distribution Features: For Remote Sites Only) After registering the OS Image to the system for use and preparing the image for distribution as described above, you must assign the image to the Site Groups and schedule the distribution of the image to those Site Groups. Follow these steps: • Click the Assign link on the Site Groups tab, and then select the Site Groups to which you want to deploy the OS Image. • Click the Update OS Version link on the Site Groups tab, and then select the version of the OS Image to deploy and the Site Groups to which you want the OS Image deployed (for newly registered OS Images, there will be only one version). Verify that the Version Deployed column lists the correct OS Image for each Site Group. • Click the Schedule link in the Deployment Date column on the OS Image Details page to open and use the Deployment Date page (select the date and time you want the Site Group to start the content distribution, and then click Schedule). A copy will be scheduled to all Sites in the Site Groups. The Core Server at each of the remote Sites will copy the OS Image, and then automatically schedule a copy to each of the streaming servers that belong to the Server Groups to which the OS Image was assigned. • You can track the progress of the copy operations using the Aggregated Servers/ Images Report page (found on the Reports page). Note that data in this report is updated periodically, based on the Aggregation Period specified in the Systems Settings page. Note that until the OS Image becomes available at a remote Site, it cannot be streamed to devices at that Site. You can track the content distribution process at the remote Site (using the WSM Administrator Console at that remote Site) from the OS Image Content Distribution tab by clicking on the name of the image/patch. Operating Systems 37 Editing OS Images CAUTION: You must shut down all devices currently streaming from this OS Image before editing the OS Image. TIP: After editing the settings, be sure to click Save Changes (the OS Image is then modified and can be viewed in the list of available OS Images on the Registered OS Image page). Summary (To Edit): On the Registered OS Image page (OS > Registered), click the Name link of the Operating System you want to edit to open the OS Image Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "Site Groups Tab" • "Site/Site Templates Tab" • "Server Groups Tab" • "Streaming Servers Tab" • "Patches Tab" • "Content Distribution Tab" Details Tab Summary (To Edit): Use the Details tab to edit the general settings for the OS Image. Figure 18 OS Image Details page - Details tab Detailed Guidelines (To Edit): • Enter the Name of the OS Image for client support (use only letters, numbers, dashes, spaces, the @ character, and periods). • The File Name is shown. 38 Chapter 5 • The Image Version is shown for the WSM VDisk Image Creation Utility. You can enter the Version you want for the OS Image (this helps keeping track of various patches generated from this OS Image; note that each patched image must be assigned a higher Version number than the original one). • Select the First Partition Mode, Second Partition Mode, and Third Partition Mode for the OS Image (either Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode)). Persistent Cache (Shared Mode) and Volatile Cache (Shared Mode) are the operating system options in which OS Images can be delivered to the device (see "About OS Images"). • Select the Reference Device if needed. A reference device is needed only when performing OS patching. Change this setting if you want to patch this OS Image using a different reference device. • Depending on whether or not you want to enable multicast for the OS Image, select or clear the Enable Multicast check box (if you enable multicast, you must enter the Multicast IP Address and Multicast Time To Live, select the Multicast Invite Type, and enter the Multicast Invite Period). Multicast can be enabled only if all partitions within the OS Image are set to Volatile Cache Mode. For more information on using multicast, go to the Wyse Knowledge Base and search for “WSM Multicast Streaming: Best Practices.” • Advanced options (click the Advanced Expand Arrow) · The Image Header Version is shown (used by WSM internally). · The Base Format is shown (both Legacy and VHD image formats are supported). · Depending on whether or not you want to enable safe boot for the OS Image, select or clear the Safe Boot check box. NOTE: Safe Boot is enabled by default. On some images, enabling Safe Boot may shorten boot-up time, however, it may cause boot failure. Therefore, try disabling this setting if you want to see if it has a positive impact to the boot time. Enable this setting if there is no significant gain or devices fail to boot. · The OS Image ID is shown (WSM assigns a unique ID for all newly created OS Images and uses this ID internally). Operating Systems 39 Site Groups Tab Summary (To Edit): Use the Site Groups tab to edit the Site Group settings for the OS Image. Figure 19 OS Image Details page - Site Groups tab Detailed Guidelines (To Edit): • Change a Site Group Assignment for the OS Image - Use the Assign button to open and use the Assign Site Groups for OS Image page (allows you to assign an OS Image to a Site Group). Use the Unassign button to unassign a selected OS Image from a Site Group. • Deploy a New OS Image Version for a Site Group - Click the Update OS Version button to open and use the wizard. • Edit an OS Image Deployment Date for a Site Group - Click the Schedule link in the Deployment Date area to open and use the Deployment Date page. • Edit a Site Group associated with the OS Image - Click a Name link in the Site Groups Name area to edit the Site Group associated with the OS Image (see "Editing Site Groups"). 40 Chapter 5 Site/Site Templates Tab Summary (To Edit): Use the Site/Site Templates tab to edit the Site and Site Template settings for the OS Image. Figure 20 OS Image Details page - Site/Site Templates tab Detailed Guidelines (To Edit): • Change a Site/Site Template Assignment for the OS Image - Use the Assign button to open and use the Assign Sites for OS Image page (allows you to assign an OS Image to a Site/Site Template). Use the Unassign button to unassign a selected OS Image from a Site/Site Template. • Edit a Site associated with the OS Image - Click a Name link in the Name area to edit the Site associated with the OS Image (see "Editing Sites"). Server Groups Tab Summary (To Edit): Use the Server Groups tab to edit the Server Group settings for the OS Image. Figure 21 OS Image Details page - Server Groups tab Detailed Guidelines (To Edit): • Change a Server Group Assignment for the OS Image - Use the Assign button to open and use the Assign Server Groups for OS Image page (allows you to assign an OS Image to a Server Group). Use the Unassign button to unassign a selected OS Image from a Server Group. • Edit the Server Group associated with the OS Image - Click a Name link in the Name area to edit the Server Group associated with the OS Image (see "Managing Server Groups"). Operating Systems 41 Streaming Servers Tab Summary (To Edit): Use the Streaming Servers tab to edit the Streaming Server settings for the OS Image. Figure 22 OS Image Details page - Streaming Servers tab Detailed Guidelines (To Edit): • Edit the Server associated with the OS Image - Click a Name link in the Name Group area to edit the Server associated with the OS Image (see "Editing Servers"). Patches Tab Summary (To Edit): Use the Patches tab to edit the Patch settings for the OS Image. Figure 23 OS Image Details page - Patches tab Detailed Guidelines (To Edit): • Start Patch Process for this OS Image - Click the Patch OS Directly button (or the Patch button if image is distributed) to open and use the Patching OS Image page (see "Updating an OS Image"). • Start Patch Process for this OS Image with an existing delta file - Click the Patch Existing Delta link to open and use the Select OS Image Copy page. Use this process only with OS Images for which a delta file already exists. • Rollback an OS Image to the previous version - Click the Rollback link and confirm. 42 Chapter 5 Content Distribution Tab Summary (To Edit): Use the Content Distribution tab to edit the Distribution settings for the OS Image. Figure 24 OS Image Details page - Content Distribution tab Detailed Guidelines (To Edit): • Allow Distribution of the OS Image - Click the Distribute button and confirm (allows the distribution and use of the OS Image). • View the Content Distribution Details of an OS Image - Click a Name link in the Name area to open the Content Distribution Details page for the OS Image. 6 Applications This chapter describes how to perform routine Application Image and Application License management tasks using the Administrator Console. Topics include: • • "Managing Application Images and Application Licenses" · "Registering Application Images" · "Editing Application Images" · "Adding Application Licenses" · "Editing Application Licenses" "How to Publish Applications" Managing Application Images and Application Licenses The Registered Applications page (Applications > Registered) and the Unregistered Applications page (Applications > Unregistered) allows you to quickly view and manage the WSM Application Images and Application Licenses that are available (see Table 5). Although the Registered Applications page shows you all of the registered Application Images and Application Licenses available in the WSM system, you can use the filtering feature to view the Application Images and Application Licenses you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of an Application Images or Application Licenses for client support (use only letters, numbers, dashes, spaces, the @ character, and periods). After entering your criteria, click Filter to view the results. You can then select the Application Images and Application Licenses you want, and begin performing your tasks. Figure 25 Registered Application Image page 44 Chapter 6 Figure 26 Unregistered Application Image page Table 5 provides a quick overview of routine management tasks. Table 5 Routine Application Management Tasks Tasks You Can Do How Details Register an Application Image to the system for streaming. On the Unregistered Application Image page (Applications > Unregistered), click the Register button for the Unregistered Application Image to open and use the Register Application System page. “Registering Application Images” on page 46. Edit an Application Image in the system. On the Registered Applications page (Applications > Registered), click the Name link of the Application Image you want to edit to open the Application Image Details page, and then use the tabs to edit the settings. “Editing Application Images” on page 48. Unregister an Application Image from the system. On the Applications Details page (Applications > Registered > Name link), click the Unregister button for the Registered Application to remove it from WSM use. The Application Image is no longer shown in the list of available Application Images on the Registered Applications page. Add an Application License to the system to enforce application licensing policies. On the Licenses tab of the Application Image Details page (Applications > Registered > Name link > Licenses), click the Add button and follow the wizard. “Adding Application Licenses” on page 53 45 Applications Table 5 Routine Application Management Tasks, Continued Tasks You Can Do How Details Edit an Application License in the system. On the Licenses tab of the Application Image Details page (Applications > Registered > Name link > Licenses), click the Name link of the Application License you want to edit to open the Application License Details page, and then use the tabs to edit the settings. “Editing Application Licenses” on page 54. Delete an Application License from the system. On the Licenses tab of the Application Image Details page (Applications > Registered > Name link > Licenses), select the check box next to the name of the Application License you want in the Name area, click Delete, and confirm the deletion. The Application License is deleted and is no longer shown in the list of available Application Licenses on the Applications page. 46 Chapter 6 Registering Application Images CAUTION: If no file exists for you to select, you must copy an Application Image and place the file into the Application Images folder located where you installed the WSM Core Server; for example, C:\Program Files\Wyse\WSM\StreamingDir\APPimages. Summary (To Register): On the Unregistered Application Image page (Applications > Unregistered), click the Register button for the Unregistered Application Image you want to open and use the Register Application Image page. Detailed Guidelines (To Register): 1. On the Unregistered Application Image page (Applications > Unregistered), click the Register button for the Unregistered Application Image you want to open the Register Application Image page. Figure 27 Registered Application Image page 2. Enter the Name of the Application Image (use only letters, numbers, dashes, spaces, the @ character, and periods). The the File Name of the Application Image is shown. 3. (Optional) Enter a Description. 4. Depending on whether or not you want to automatically subscribe this Application Image (with user unsubscribe flexibility) to an end user when the user first logs on to the WSM Client, select or clear the Auto Subscribe Application check box (note that after the user has been subscribed to the application during the first login, the user has the option of unsubscribing from this application at any time thereafter). 5. Depending on whether or not you want to automatically subscribe this Application Image (without user unsubscribe flexibility) to an end user when the user first logs on to the WSM Client, select or clear the Mandatory Application check box (note that after the user has been subscribed to the application during the first login, the user will not have the option of unsubscribing from this application; if the user tries to unsubscribe, a message displays stating that the application is mandatory and cannot be unsubscribed). 6. The Application Image is added to the list of available Application Images on the Registered Applications page. At this stage, the Application Image has been registered at the Core Server only. It is not yet available at streaming servers or at remote Sites. To prepare the Application Image for deployment to remote servers and Sites (if any), follow these guidelines: • Click the Distribute link on the Content Distribution tab of the Application Image Details page. Until you click on this link, the Application Image will not be copied to streaming servers or to remote Sites. Note that this is a one-time operation for each Application Image. Once you have clicked the Distribute link for an Application Image, Applications 47 the Application Image is effectively locked down, and no configuration changes can be made to the Application Image from that point onward. • To allow the Application Image to be streamed from streaming servers, the Application Image must be assigned to those servers. Click the Assign link on the Server Groups tab to open and use the Assign Server Groups For Application Image page as described in "Editing Application Images." Note that if the Application Image has been assigned to a Site Template, be sure to assign the Application Image to the Server Group that is associated with that Site Template. (Content Distribution Features: For Remote Sites Only) Unlike OS Images, Application Images are automatically copied to all remote Sites to which the Application Image has been assigned. You can track the progress of the copy operations using the WSM Monitor. Note that until the Application Image becomes available at a remote Site, it cannot be streamed to devices at that Site. You can track the content distribution process at the remote Site (using the WSM Administrator Console at that remote Site) from the OS Image Content Distribution tab by clicking on the name of the image/patch. 48 Chapter 6 Editing Application Images TIP: After editing the settings, be sure to click Save Changes (the Application Image is then modified and can be viewed in the list of available Application Images on the Registered Applications page). Summary (To Edit): On the Registered Applications page (Applications > Registered), click the Name link of the Application Image you want to edit to open the Application Image Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "Site/Site Templates Tab" • "Server Groups Tab" • "Streaming Servers Tab" • "Licenses Tab" • "Patches Tab" • "Content Distribution Tab" Details Tab Summary (To Edit): Use the Details tab to edit the general settings for the Application Image. Figure 28 Application Image Details page - Details tab Detailed Guidelines (To Edit): • Enter the Name. • (Optional) Enter a Description. • Enter the Version. • Depending on whether or not you want to automatically subscribe this Application Image (with user unsubscribe flexibility) to an end user when the user first logs on to the WSM Client, select or clear the Auto Subscribe Application check box (note that 49 Applications after the user has been subscribed to the application during the first login, the user has the option of unsubscribing from this application at any time thereafter). • Depending on whether or not you want to automatically subscribe this Application Image (without user unsubscribe flexibility) to an end user when the user first logs on to the WSM Client, select or clear the Mandatory Application check box (note that after the user has been subscribed to the application during the first login, the user will not have the option of unsubscribing from this application; if the user tries to unsubscribe, a message displays stating that the application is mandatory and cannot be unsubscribed). • The Distribution Type, File Name, Application Image ID, File ID, Is Enabled, and Allow Distribution are shown. Site/Site Templates Tab Summary (To Edit): Use the Site/Site Templates tab to edit the Site and Site Template settings for the Application Image. Figure 29 Application Image Details page - Site/Site Templates tab Detailed Guidelines (To Edit): • Change a Site Assignment for the Application Image - Use the Assign button to open and use the Assign Sites for Application Image page (allows you to assign an Application Image to a Site/Site Template). Use the Unassign button to unassign a selected Application Image from a Site/Site Template. • Edit a Site associated with the OS Image - Click a Name link in the Name area to edit the Site associated with the Application Image (see "Editing Sites"). 50 Chapter 6 Server Groups Tab Summary (To Edit): Use the Server Groups tab to edit the Server Group settings for the Application Image. Figure 30 Application Image Details page - Server Groups tab Detailed Guidelines (To Edit): • Change a Server Group Assignment - Use the Assign button to open and use the Assign Server Groups for App Image page (allows you to assign an Application Image to a Server Group). Use the Unassign button to unassign a selected Application Image from a Server Group. • Edit the Server Group associated with the Application Image - Click a Name link in the Name area to edit the Server Group associated with the Application Image (for details on editing a server group, refer to "Managing Server Groups"). Streaming Servers Tab Summary (To Edit): Use the Streaming Servers tab to edit the Streaming Server settings for the Application Image. Figure 31 Application Image Details page - Streaming Servers tab Detailed Guidelines (To Edit): • Edit the Servers associated with the Application Image - Click a Name link in the Name Group area to edit the Servers associated with the Application Image (see "Editing Servers"). 51 Applications Licenses Tab Summary (To Edit): Use the Licenses tab to add, edit, and delete the Application Licenses for the Application Image. Figure 32 Application Image Details page - Licenses tab Detailed Guidelines (To Edit): • Add an Application License for this Image - Click the Add button to open and use the Add Application License wizard (see "Adding Application Licenses"). • Delete this Application License - Click the Delete button to delete a selected Application License. • Edit the Application License associated with the Application Image - Click a Name link in the Name area to edit the Application License associated with the Application Image (see "Editing Application Licenses"). Patches Tab Summary (To Edit): Use the Patches tab to edit the Patch settings for the Application Image. Figure 33 Application Image Details page - Patches tab Detailed Guidelines (To Edit): • Add a Patch for this Application Image - Click the Patch button to open and use the Patching Application Image page (see "Updating an Application Image"). 52 Chapter 6 Content Distribution Tab Summary (To Edit): Use the Content Distribution tab to edit the Distribution settings for the Application Image. Figure 34 Application Image Details page - Content Distribution tab Detailed Guidelines (To Edit): • Allow Distribution of the Application Image - Click the Distribute button and confirm (allows the distribution and use of the Application Image). • View the Content Distribution Details of an Application Image - Click a Name link in the Name area to open the Content Distribution Details page for the Application Image. 53 Applications Adding Application Licenses Summary (To Add): On the Licenses tab of the Application Image Details page (Applications > Registered > Name link > Licenses), click the Add button and follow the wizard. Detailed Guidelines (To Add): 1. On the Licenses tab of the Application Image Details page (Applications > Registered > Name link > Licenses), click the Add button to open the Add Application License wizard. Figure 35 Add Application License wizard 2. Complete the Add Application License page using the following guidelines: • Enter the Name of the Application License you want to add (use only letters, numbers, dashes, spaces, the @ character, and periods). • The name of the Application Image is displayed. • Select a Sessions per User option (either a custom amount or Unlimited). If you select a custom amount, enter the number of Sessions. Be aware that once an Application License is in use, Sessions per User cannot be edited. • Select a Duration option (either a custom amount or Unlimited). If you select a custom amount, enter the number of Days. • Select a Maximum Concurrent Sessions option (either a custom amount or Unlimited). If you select a custom amount, enter the number of Sessions. 3. Click Next to open the Assign to a Group page. TIP: If you do not have User Groups, click Finish to complete adding the Application License. The Application License is added to the list of available Application Licenses on the Applications page and can now be used to enforce application licensing policies. 4. Select the User Groups you want to include using the assignment page. 5. Click Finish. The Application License is added to the list of available Application Licenses on the Applications page and can now be used to enforce application licensing policies. 54 Chapter 6 Editing Application Licenses TIP: After editing the settings, be sure to click Save Changes (the Application License is then modified and can be viewed in the list of available Application Licenses on the Applications page). Summary (To Edit): On the Licenses tab of the Application Image Details page (Applications > Registered > Name link > Licenses), click the Name link of the Application License you want to edit to open the Application License Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Application License Details Tab" • "User Groups Tab" Application License Details Tab Summary (To Edit): Use the Application License Details tab to edit the general settings for the Application License. Figure 36 Application License Details tab Detailed Guidelines (To Edit): • Enter the Name for the Application License. • The Application Image and Sessions per User are shown. • Select a Duration option (either a custom amount or Unlimited). If you select a custom amount, enter the number of Days. • Select a Maximum Concurrent Sessions option (either a custom amount or Unlimited). If you select a custom amount, enter the number of Sessions. TIP: If you do not have User Groups, click Save Changes to complete editing the Application License. The Application License is modified and saved to the list of available Application Licenses on the Applications page and can now be used to enforce application licensing policies. 55 Applications User Groups Tab Summary (To Edit): Use the User Groups tab to edit the User Group settings for the Application License. Figure 37 User Groups tab Detailed Guidelines (To Edit): • Change a User Group Assignment - Use the Assign button to open and use the Assign Groups for Application License page (allows you to assign an Application License to a User Group). Use the Unassign button to unassign a selected Application License from a User Group. • Edit the User Groups associated with the Application License - Click a Name link in the Name area to edit the User Groups associated with the Application License (for details on editing a user group, refer to "Editing User Groups"). 56 Chapter 6 How to Publish Applications This section describes how to use WSM Publisher to publish applications and to make them available for distribution. Throughout this section, WSM Publisher is also referred to as the Publisher. Publishing means to re-package a software application into a form that can be streamed to client machines. To publish an application, it is first installed on a platform that is dedicated to publishing and has WSM Publisher installed. WSM Publisher determines how the installed application works in the Windows environment and packages the required components and configuration information into a compressed, encrypted application set, called an appset. The application being published is referred to as the target application. The appset is loaded on WSM servers and the target application becomes available for clients through streaming from the WSM servers. The Publisher determines the required components and configuration for the appset by comparing snapshots of the system state prior to and after the target application is installed on the publishing machine. The differences identified in the files and settings are stored in a build file, which in turn is used to create an appset. The appset contains all the files, folders, and registry settings needed to reproduce the application on the client user’s PC. Variations among applications and installation can sometimes make publishing seem complex. For example, many applications integrate themselves deeply into the Windows operating system environment. Software vendors also use different installation programs (such as InstallShield and InstallAnywhere). Moreover, some applications integrate with other applications. To reduce this complexity, this section presents a best-practice approach to help ensure smooth and successful publishing. "WSM Publisher File Types" describes the various file types used by WSM Publisher. Topics include: • "Installation Requirements and Recommendations" • "Publishing Steps" Installation Requirements and Recommendations Topics include: • "Hardware and Software Requirements" • "About Publishing Performance" • "Preparing a Dedicated Machine" • "Setting-up Disk Space for Publishing" • "Installing WSM Publisher" Hardware and Software Requirements Normally, you should publish an application on the same OS as the OS used on the user’s target desktop. In addition to WSM Publisher requirements, each machine must meet or exceed the system requirements of the application being published. The following requirements have been established based on acceptable compression and encryption performance. • Operating System: Windows XP or later • CPU: 1.5 GHz CPU or higher • RAM: 512 MB • Disk Space: 40 GB Applications 57 About Publishing Performance The publishing process is both I/O- and CPU-intensive, and performance measurements have shown that the following criteria, in decreasing order, have the greatest effect on publishing speed: • Publishing on a physical machine instead of a virtual machine (>30% speed improvement*) • SCSI instead of IDE hard drives • Faster front side bus • Faster processor • Dual processor instead of single processor (<10% speed improvement*) * These measurements are provided only as a reference. Actual results may vary greatly based on your hardware and software system configuration. Preparing a Dedicated Machine It is recommended that you use a dedicated machine so that the Publisher does not notice any software, files, or registry information other than information for the Windows OS. The dedicated machine should have all the latest OS service packs installed. It is assumed that the OS service packs fix any bugs in the OS but do not cause any application-specific files or registry settings to be copied into the system that could cause an application installer to take an erroneous path. It is also recommended that you use a disk-imaging or ghosting application to establish a clean machine for a new application-publishing project. The disk image of a dedicated machine is saved as a read-only file (for example, WinXP_base.dsk). Setting-up Disk Space for Publishing To ensure adequate disk space, WSM Publisher requires a segmented drive space for the application to be published. You can install or rename drives via the Computer Management feature in Windows XP or later. To re-partition a drive, use a third-party application such as Partition Magic. • Name the new drive space O: (letter O). Either install an additional hard drive or re-partition your current drive, or change the drive letter mapping. • If there is only one partition (for example, C:), either install an additional hard drive or re-partition your current drive. • If you have two or more partitions (for example, C: and D:) you must either rename one partition to “O:” or re-partition one of the drives. 58 Chapter 6 Installing WSM Publisher TIP: WSM Publisher will be installed in the Program Files folder on your C: drive. The installer for the Publisher is available from the WSM Administrator Console > Installers link > Application Publisher link. Figure 38 About page 1. On your dedicated Publisher machine, double-click on the WSMPublisher.exe file to open the installation wizard. 2. Click Next. 3. Read the license agreement, select I accept the terms in the License Agreement, and then click Next. 4. Click Next to begin installation. 5. After the installation is complete, click Finish. TIP: To launch WSM Publisher, click Start | Programs | WSM Publisher, and select WSM Publisher. 59 Applications Publishing Steps IMPORTANT: Supported platforms include Windows XP and Windows 7. TIP: For information on manually publishing Applications, see "Manually Publishing Applications." Express mode publishing uses default values to simplify Application packaging. If you want to manually edit the build (for example to include additional files or settings), compress, encrypt the appset or work with prefetching, this is only available in manual mode. To start the publisher in manual mode, the link in the start menu must be extended with /manual. IMPORTANT: All software to be installed should be accessible from the Publisher machine before you proceed. In this example the set-up program for Adobe Reader is available from the O:\ drive: Figure 39 Adobe example 1. Launch WSM Publisher (Start | Programs | WSM Publisher, and then select WSM Publisher). Figure 40 Application information - pre-snapshot 2. Enter the application information for the pre-snapshot, and then click Next to create the pre-snapshot. 60 Chapter 6 Figure 41 Application information - post-snapshot destination 3. Enter the destination drive used for application packaging (in our example, O) for the post-snapshot. 4. Launch the installer for your application (in our example, Adobe Reader) and change the installation destination to the directory path recommended by the Publisher (in our example, O:\Adobe Reader\InstallDir). Figure 42 Application installation path 5. Click Next. Figure 43 Application installation update option 6. Select the manual update option and click Install. 61 Applications Figure 44 Application shortcut properties 7. After the installation is finished, inspect the application shortcuts and ensure that the Start in: field is not empty, as this can lead to issues while starting a streamed application. Delete such shortcuts and replace all of them with ones that you have created manually. Figure 45 Application Start menu shortcut Be sure to also replace the shortcut in the Start menu. 8. Launch the application to verify it has been installed successfully and that the shortcuts are working properly. 9. Return to the WSM Publisher wizard. 62 Chapter 6 Figure 46 Application information - post-snapshot 10.Click the Application Install button create the post-snapshot. 11. , Click Next to create the Application Set. Figure 47 Application Set creation process 12.After the Application Set is created the Summary screen appears. Figure 48 Application Set Summary screen 13.Click Finish. 63 Applications 14.Copy the Application Set to the Core servers StreamingDir\Appimages directory. Figure 49 StreamingDir\Appimages directory 15.Register the application in the WSM Admininstrator Console and create an Application License so users can subscribe to the application. Figure 50 Register and License TIP: See “Registering Application Images” on page 46 and “Adding Application Licenses” on page 53 for more details. 16.Assign the Application to the Server group hosting the Core and Edge server, and then remove it from the Default Server Group to avoid unnecessary warnings. Figure 51 Server Groups 17.In our example a perpetual license for the Administrators and users of WSMGroup1 is created. 64 Chapter 6 Figure 52 Add a license Figure 53 Add a license step 1 Figure 54 Add a license step 2 Figure 55 Perpetual License 18.Test the application. On a streamed client, login as a user which is member of one of the groups to which the license is assigned, open the WSM Client, and then subscribe to the application. 65 Applications Figure 56 Subscribe to the application TIP: See “Subscribing to an Application” on page 280 for more details. 19.The application is now listed under Subscribed Applications. Figure 57 Subscribed Applications 20.Launch the Application to verify it is working as expected. 21.After you have verified the application is working as expected, enable the distribution to remote servers. Figure 58 Enable distribution TIP: See “Content Distribution Tab” on page 52 for more details. The pre-processing and copy will start automatically when the Content Distribution agents on the servers check their queue. 66 Chapter 6 Figure 59 Content distribution The Edge server will automatically copy the Application, as it belongs to the same server group. Once the copy and CRC check is successful, the Version Deployed column is updated. Figure 60 Streaming Servers 7 Servers This chapter describes how to perform routine Server and Server Group management tasks using the Administrator Console. Topics include: • "Managing Servers" · • "Editing Servers" "Managing Server Groups" · "Understanding the Default and User-Created Server Groups" · "Adding Server Groups" · "Editing Server Groups" Managing Servers TIP: During a Server installation, configuration settings are made through an installation wizard. After your Server installation is complete, you can then edit and delete a Server by using the Servers page. For information on adding a Server by using the installation procedures in "Step 2: Installing and Configuring the WSM Core Server," refer to Table 6. The Servers page (Servers > Servers) allows you to quickly view and manage the WSM Servers that are available (see Table 6). Figure 61 Servers page Although the Servers page shows you all of the Servers available in the WSM system, you can use the filtering feature to view the Servers you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Server for client support (use only letters, numbers, dashes, spaces, the @ character, and periods). • IP Address - IP Address of the Server. • Status - Status of the Server (all, Up, or No Response). 68 Chapter 7 • OS Image - Name of the OS Image to which the Server is assigned. • Application Image - Name of the Application Image to which the Server is assigned. After entering your criteria, click Filter to view the results. You can then select the Servers you want, and begin performing your tasks. Table 6 provides a quick overview of routine management tasks. Table 6 Routine Server Management Tasks Tasks You Can Do How Details Add a Server to the system. Use the Edge Server installation procedures in "Step 5: Installing and Configuring a WSM Edge Server." After you have installed an Edge Server according to the procedures in "Step 5: Installing and Configuring a WSM Edge Server," the Edge Server is automatically added to the list of Servers available on the Servers page and the Default Server Group. NOTE: To assign an OS Image use the Synch Server Group Assignment link on the OS Image Details page; to assign an Application Image use the Synch Server Group Assignment link on the Application Image Details page. Edit a Server in the system. On the Servers page (Servers > Servers), click the Name link of the Server you want to edit to open and use the Server Details page. “Editing Servers” on page 69. Delete a Server from the system. CAUTION: Best practices to delete an Edge Server from the console is to uninstall it. The Delete button should only be used to remove orphaned entries. WARNING: Re-installing the WSM Server software is the only way to add an accidentally deleted Edge Server. IMPORTANT: You cannot delete the Core Server. Only Edge Servers can be deleted. On the Servers page (Servers > Servers), select the check box next to the name of the Server you want in the Name area, click Delete, and confirm the deletion. The Server is deleted and is no longer shown in the list of available Servers on the Servers page. 69 Servers Editing Servers TIP: After editing the settings, be sure to click Save Changes (the Server is then modified and can be viewed in the list of available Servers on the Servers page). Summary (To Edit): On the Servers page (Servers > Servers), click the Name link of the Server you want to edit to open and use the Server Details page. Figure 62 Server Details page Detailed Guidelines (To Edit): • The Name and Type (for example, Core Server—or Streaming Server for an Edge Server) of the Server are shown. • (Optional) Enter a Description. • Enter the IP Address of the Server (before editing the Server IP Address, you must stop all of the Server services; after all Server editing is complete, be sure to start all of the Server services). • Enter the Streaming Directory containing your OS Images and Application Images (before editing the Server Streaming Directory, you must stop all of the Server services; after all Server editing is complete, be sure to start all of the Server services). • The Status of the Server is shown. • The WSM Version running on the Server is shown. • Optional Related Tasks you can perform using the Server Details page: • Manage a Service associated with the Server - Click a Service Name link in the Services area (see "Managing Services for a Server"). For example, the Enable Device Discovery feature of the DHCP Proxy Service allows you to configure the WSM Server to automatically add new devices to the system (this feature setting is on a per Server basis). You can use the Enable Device Discovery feature by selecting the Enable Device Discovery check box in the DHCP Proxy Service page (click the DHCP Proxy Service link in the Services area to open the DHCP Proxy Service page). If the Enable Device Discovery check box is cleared, the WSM Server will only respond to devices which are already included in the WSM Database. If the Enable Device Discovery check box 70 Chapter 7 is selected, any new device will be added to the WSM system using the WSM device templates (for information on using device templates, refer to "Adding Device Templates"). If Active Directory integration is enabled, the new device will be added to the WSM system based on the appropriate device template that is applicable. • Stop or Start a Service - Click the Start link (to start the service) or Stop link (to stop the service) for the service you want in the Services area (you can also use the Start All link or Stop All link). The Status list shows whether or not a service is running (Up) or stopped (Down) for the Server. • View a Service log - Click the View Log link to view the service log you want in the Services area. • Edit the OS Image associated with the Server - (Servers in Default Server Group Only) Click a Name link in the OS Images Streamed By area (see "Editing OS Images"). CAUTION: WSM helps you avoid making changes to OS Images that are currently in use by others. In some cases where you want to modify an OS Image (but receive a message that you are unable to modify an OS Image at this time) and you know that no one else is using it, clicking the Release Lock link on the OS Image Details page allows you to reset the lock on the OS Image and make the modifications you want. • Optional Related Tasks you can perform using the Server Details page: • Delete this Server - (Edge Servers Only) Click the Delete this Server link to delete the Server. CAUTION: Before deleting a Server, all of the assigned OS Images and Application Images must be unassigned from the Server. In addition, you must also shut down the devices which are booted from that Server. • Edit the Application Images associated with the server - (Servers in Default Server Group Only) Click a Name link in the Application Images Streamed By area to open and use the Application Image Details page (see "Editing Application Images"). • View an Application Image log - (Servers in Default Server Group Only) Click the View Log link to view the Application Image log you want in the Application Images Streamed By area. 71 Servers Managing Services for a Server While editing a Server (Servers > Servers > Name link), you can quickly access and manage a Service for a Server by clicking a Service Name link in the Service Name area. Figure 63 Service Details page - OS Authentication Service example The Service Details page shows you the Service Type, Server, Port, and Status of the Service you selected. Depending on the Service you selected, you may be allowed to modify the Port that the Service uses. However, in all Service cases you will be able to use the Start link (to start the service) or Stop link (to stop the service), and the View Log link (to view the log for the service). After you complete your modifications on the Service Details page, be sure to click Save Changes. The Service is then modified and can be viewed in the list of Services on the Server Details page. CAUTION: If your DHCP Server and DHCP Proxy Service are running on the same machine, be sure to select the 4011 Port option. 72 Chapter 7 Managing Server Groups TIP: Server Groups make it easier to assign OS Images, Application Images, and Device Groups because you can assign them to all of the Servers in a Server Group at the same time rather than to each Server individually. For example, to assign the same OS Image to five different Servers, first create a Server Group that includes the Servers and then assign the OS Image to the Server Group. Additionally, whenever you add a Server to an existing Server Group, that Server is automatically assigned the OS Images and Application Images of that Server Group. The Server Groups page (Servers > Server Groups) allows you to quickly view and manage the WSM Server Groups that are available (see Table 6). Figure 64 Server Groups page Although the Server Groups page shows you all of the Server Groups available in the WSM system, you can use the filtering feature to view the Server Groups you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Server Group (use only letters, numbers, dashes, spaces, the @ character, and periods). • Application Image - Name of the Application Image to which the Server is assigned. • OS Image - Name of the OS Image to which the Server is assigned. After entering your criteria, click Filter to view the results. You can then select the Server Groups you want, and begin performing your tasks. 73 Servers Table 6 provides a quick overview of routine management tasks. Table 7 Routine Server Group Management Tasks Tasks You Can Do How Details Add a Server Group to the system. On the Server Groups page (Servers > Server Groups), click the Add button and follow the wizard. “Adding Server Groups” on page 75. Edit a Server Group in the system. On the Server Groups page (Servers > Server Groups), click the Name link of the Server Group you want to edit to open the Server Group Details page, and then use the tabs to edit the settings. “Editing Server Groups” on page 76. Delete a Server Group from the system. On the Server Groups page (Servers > Server Groups), select the check box next to the name of the Server Group you want in the Name area, click Delete, and confirm the deletion. The Server Group is deleted and is no longer shown in the list of available Servers on the Server Groups page. Deleting a Server Group reassigns all Servers in the group to the Default Server Group. IMPORTANT: You cannot delete the Default Server Group. Understanding the Default and User-Created Server Groups WSM provides two types of Server Groups, Default and user-created. The Default Server Group is created automatically. Administrators can create user-created Server Groups as needed. Servers cannot belong to more than one Server Group. Each Server must be in the Default Server Group or a user-created Server Group. TIP: You can move Servers in and out of the Default Server Group as they are needed in user-created Server Groups. You can also move Servers directly from one user-created Server Group to another. Attributes of each Server Group include: • Default Server Group: • WSM creates the Default Server Group during installation or during an upgrade. The Default Server Group is automatically assigned to the first Core Server installation. There is only one Default Server Group. Its purpose is to store Servers until, if necessary, they are assigned to a user-created Server Group. • All Servers in the Default Server Group must be treated the same and share OS Image, Application Image, and Default Device Group assignments. • Servers in the Default Server Group must be managed (for OS Image, Application Image, and Default Device Group attributes) using the Server Group Details page in the Administrator Console. • You can move Servers in and out of the Default Server Group as they are needed in user-created Server Groups. • You cannot delete or modify the Default Server Group. 74 Chapter 7 • User-Created Server Group: • Administrators create user-created Server Groups as needed. • All Servers in a user-created Server Group must be treated the same and share OS Image, Application Image, and Device Group assignments. • Servers in a user-created Server Group must be managed (for OS Image, Application Image, and Device Group attributes) using the Server Group Details page in the Administrator Console. • Servers in the same user-c reated Server Group do automatic load balancing and failover. • You can move Servers directly from one user-created Server Group to another. • When you reassign a Server to a user-created Server Group, its previous OS Image, Application Image, and Device Group assignments are automatically stripped away; it adopts the OS Image, Application Image, and Device Group assignments of the user-created Server Group to which it was reassigned. • You can delete or modify a user-created Server Group. Deleting a user-created Server Group reassigns all Servers in it to the Default Server Group. 75 Servers Adding Server Groups Summary (To Add): On the Server Groups page (Servers > Server Groups), click the Add button and follow the wizard. Detailed Guidelines (To Add): 1. On the Server Groups page (Servers > Server Groups), click the Add button to open the Add Server Group wizard. Figure 65 Add Server Group wizard 2. Complete the Add Server Group page using the following guidelines: • Enter a Name. • Enter a Description. 3. Click Next to open the Assign Sites page. 4. Select the Sites you want to include using the assignment page. 5. Click Next to open the Assign Servers page. 6. Select the Servers you want to include using the assignment page. 7. Click Finish. The Server Group is added to the list of available Server Groups on the Server Groups page. 76 Chapter 7 Editing Server Groups TIP: After editing the settings, be sure to click Save Changes (the Server Group is then modified and can be viewed in the list of available Server Groups on the Server Groups page). Summary (To Edit): On the Server Groups page (Servers > Server Groups), click the Name link of the Server Group you want to edit to open the Server Group Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "Servers Tab" • "Device Groups Tabs" • "OS Images Tabs" • "App Images Tab" Details Tab Summary (To Edit): Use the Details tab to edit the general settings for the Server Group. Figure 66 Details tab Detailed Guidelines (To Edit): • Enter the Name. • (Optional) Enter a Description. • Site Name is shown. 77 Servers Servers Tab Summary (To Edit): Use the Servers tab to edit the Server settings and assignments for the Server Group. Figure 67 Servers tab Detailed Guidelines (To Edit): • Add or remove a Server to or from the Server Group - Click the Reassign Servers button for your selected Servers to open and use the Move Servers From Server Group page. • Edit an Server associated with this Server Group - Click a Name link in the Name area to open and use the Server Details page (see "Editing Servers"). Device Groups Tabs Summary (To Edit): Use the Device Groups tab to edit the Device Group settings and assignments for the Server Group. Figure 68 Device Groups tab Detailed Guidelines (To Edit): • Edit an Device Group associated with this Server Group - Click a Name link in the Device Groups Associated with area to open and use the Device Group Details page (see "Editing Device Groups"). 78 Chapter 7 OS Images Tabs Summary (To Edit): Use the OS Images tab to edit the OS Image settings and assignments for the Server Group. Figure 69 OS Images tab Detailed Guidelines (To Edit): • Edit an OS Image associated with this Server Group - Click a Name link in the OS Images Associated with area to open and use the OS Image Details page (see "Editing OS Images"). App Images Tab Summary (To Edit): Use the App Images tab to edit the Application Image settings and assignments for the Server Group. Figure 70 App Images tab Detailed Guidelines (To Edit): • Edit an Application Image associated with this Server Group - Click a Name link in the Name area to open and use the Application Image Details page (see "Editing Application Images"). 8 Devices This chapter describes how to perform routine Device and Device Group management tasks (with and without Active Directory integration) using the Administrator Console. Topics include: • • • "Managing Devices" · "Adding Devices" · "Editing Devices" · "Sending Commands to Devices" · "Importing Devices from a File" "Managing Device Groups" · "Understanding the Default and User-Created Device Groups" · "Adding a Device Group" · "Editing Device Groups" "Managing Device Templates" · "Adding Device Templates" · "Editing Device Templates" 80 Chapter 8 Managing Devices TIP: Depending on whether or not Active Directory is enabled, some procedures may be different. For example, while adding a device with Active Directory enabled, you must select an Active Directory Organizational Unit. The Devices page (Devices > Devices) allows you to quickly view and manage the WSM Devices that are available (see Table 8). Figure 71 Devices page Although the Devices page shows you all of the Devices available in the WSM system, you can use the filtering feature to view the Devices you want (click the magnifying lens to expand the filtering feature): • IP Address - IP Address of the device. • OS Image - Name of the OS Image that is assigned to device. Use the OS Image Select link to select the OS Image. • MAC Address - MAC Address of the device. • Device Status - Status of the device. • Connection Type - (all, Network, or Mobile Disconnected) • Active Server - Name of the server to which the device is assigned. Use the Active Server Select link to select the server. After entering your criteria, click Filter to view the results. You can then select the Devices you want, and begin performing your tasks. 81 Devices Table 8 provides a quick overview of routine management tasks. Table 8 Routine Device Management Tasks Tasks You Can Do How Details Add a Device to the system. On the Devices page (Devices > Devices), click the Add button to open and use the Add Devices page. “Adding Devices” on page 82. NOTE: The Reference Device is used as a Default device when updating an OS Image, as described in "Updating an OS Image." Edit a Device in the system. On the Devices page (Devices > Devices), click the Name link of the Device you want to edit to open and use the Device Details page. “Editing Devices” on page 84. Delete a Device from the system. On the Devices page (Devices > Devices), select the check box next to the name of the Device you want in the Devices page, click Delete, and confirm the deletion. The Device is deleted and is no longer shown in the list of available Devices on the Devices page. CAUTION: With Active Directory integration, deleting a Device also deletes the computer account of the Device from Active Directory. Send supported commands to Devices in the system. On the Devices page (Devices > Devices), select the Devices to which you want to send a command, and then click Send Command to open and use the Send Command page (supported commands include Reboot, Shut down, and Wake on LAN). “Sending Commands to Devices” on page 87. Abort the previously scheduled commands to Devices in the system. On the Devices page (Devices > Devices), select the devices for which you want to abort previously scheduled commands, click Abort Command to open a message confirming the removal of the commands, and then click OK to abort the commands. Import devices from a file into the system. On the Devices page (Devices > Devices), click the Import Devices button to open and use the Import Devices page. “Importing Devices from a File” on page 88. IMPORTANT: WSM requires that the import file has a list of all MAC addresses of the devices present in this file. The separators supported are comma, space, or end of line (that is, each MAC address of the device is on a new line in the file). You can find the MAC ID of a Wyse thin client on a sticker on the device (Wyse thin client MAC addresses start with 00 80 64). For MAC addresses of other WSM supported devices, contact the manufacturer. 82 Chapter 8 Adding Devices Summary (To Add): On the Devices page (Devices > Devices), click the Add button to open and use the Add Devices page. Detailed Guidelines (To Add): 1. On the Devices page (Devices > Devices), click the Add button to open the Add Device page. Figure 72 Add Device page 2. Complete the Add Device page using the following guidelines: • Enter a Name. • Enter a Description. • Enter a Mac Address. • Select a Device Group. • Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). • (For Active Directory integration only) Select the Active Directory Organizational Unit (for example, wsm.com/CN=Computers). • Determine the OS Images you want to include. • Determine the Streaming Server you want to include. Devices 83 3. Click Save Changes. The Device is added to the list of available Devices on the Devices page. WARNING: If you added a mobile device, do not use the device while the provisioning process is being completed. A message informs you when OS provisioning is complete. Moreover, although the OS has been provisioned for Mobile mode, users still need to provision the applications that will run on the mobile device when their device is disconnected. To provision applications, the user must reboot the device and log on while the device is connected to the network. Users must not disconnect the device from the network or use the device for any purpose while applications are being provisioned. Applications must be made available for offline use by the user using the WSM Client. 84 Chapter 8 Editing Devices TIP: After editing the settings, be sure to click Save Changes (the Device is then modified and can be viewed in the list of available Devices on the Devices page). CAUTION: Some fields on the Device Details page can be edited only if you are working with Devices assigned to the Default Device Group. TIP: Instructions in this section are for a network device, mobile device, or Reference Device. Summary (To Edit): On the Devices page (Devices > Devices), click the Name link of the Device you want to edit to open and use the Device Details page. Figure 73 Device Details page Detailed Guidelines (To Edit): • Enter the Name. • (Optional) Enter a Description. • Enter the MAC address of the device. • The IP Address of the device (and Reference Device for the Reference Device) is shown. • Select the Device Group to which you want the device assigned (the Device is assigned the OS Image and Streaming Server that is assigned to the Device Group you selected). (Devices assigned to the Default Device Group Only) Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). • (Devices assigned to the Default Device Group Only) Select the Boot Selection Mode for the device (First Disk, First Available, or User Select). TIP: First Disk (default) specifies that the device will always boot from the first OS Image that is assigned to it. Devices 85 First Available is the mode that is used for failover purposes. In this mode you can specify the same OS Image on multiple servers and use that specification as the assignment for two or more OS Images available. Thus, the device will try and connect to the first server, and if the server is not available, the device will try and connect to the remaining assigned servers as specified. User Select is the mode that allows users to specify from which OS Image the device should boot. A menu is displayed for the user when the device boots, allowing the user to specify the OS Image and server combination. • (For Active Directory Integration Only) The Active Directory Organizational Unit is shown (for example, wsm.com/CN=Computers). • Device Group, Server Group, and Image Name are shown. • Status is shown: • • Authenticated - WSM Server has authenticated the device and identified the operating system image assigned to it. • Boot Aborted - Boot process has aborted for some reason (such as a network connection failure between the device and WSM Server, no VDisk is available, insufficient resource at the WSM Server to process the device request, or a timeout is reached on waiting for user input from the device). • Booting - Device is booting up and trying to connect to the WSM Server for authentication (new device or existing device). • Disconnected - WSM Server is not receiving heartbeats from the device beyond the Device Heartbeat Timeout as defined in the Systems Setting page. The resources held by the device are released and the device can be treated as down. The device can reconnect to the WSM Server later without reboot provided that the VDisk image associated to the device has not been changed. • Down - Device has been shut down. The shutdown process can be initiated by a WSM administrator from the administrator UI or the user of the device. Down indicates a clean shutdown. • No Response - Device is not sending heartbeats to the WSM Server indicating a forced shutdown, power failure, or network connection failure. • Reconnect aborted - Reconnection attempts have failed. The device is not functional until a successful reboot. • Reconnecting - Device is trying to reconnect to the WSM Server after a connection failure. • Starting OS - WSM Server has transferred control to the Operating System for the device and Operating System is starting up. • Up - Device is up and sending heartbeats to the WSM Server. Optional Related Tasks you can perform using the Device Details page: • Remove an OS Image - (Devices in Default Device Group Only) Click the Remove OS Image link in the Assigned Operating System Images area for the OS Image you want to remove from the device. NOTE: If you want to change an OS Image assignment for the next device boot, then you can use the Update OS Image link. • Add an OS Image - (Devices in Default Device Group Only) Click the Add OS Image link in the Assigned Operating System Images area and select the OS Image you want to assign to the device ). • Update an OS Image- (Devices in Default Device Group Only) Click the Update OS Image link in the Assigned Operating System Images area for the OS Image you want to update for the device. • Reset a Device State - Click the Reset Device State button in the Assigned Operating System Images area for the OS Image and OS Server association you want to clear the Write Cache for the device (to clear all Write Caches associated with the device be sure to click each Reset Device State button that appears). CAUTION: You cannot successfully use the Reset Device State link if the OS 86 Chapter 8 Image and OS Server combination is currently being used (a currently being used message appears at the top of the Network Device Details page). In such a case, you must first shut down the device, and then use the Reset Device State button. Using the Reset Device State button will cause all changes made to the OS Image by this device to be lost. 87 Devices Sending Commands to Devices Summary (To Send): On the Devices page (Devices > Devices), select the Devices to which you want to send a command, and then click Send Command to open and use the Send Command page (supported commands include Reboot, Shut down, and Wake on LAN). Detailed Guidelines (To Send): 1. On the Devices page (Devices > Devices), select the Devices to which you want to send a command. 2. Click Send Command to open the Send Command page. Figure 74 Send Command page 3. Select the command (Reboot, Shut down, or Wake on LAN) you want to send to the devices. 4. Complete one of the following: • To send the command now, select Send command now. • To send the command with a time delay, select Schedule command with time delay and enter a Time Delay in seconds (default is 300). • To send the command later, select Schedule for later to open and use the calendar (select the date, enter a time, and click Done). 5. Click Done to send the command (according to your schedule or Time Delay) and return to the Devices page. TIP: You can remove previously scheduled commands by going to the Devices page (Devices > Devices), selecting the devices, clicking Abort Command to open a confirmation message, and then clicking OK. 88 Chapter 8 Importing Devices from a File Summary (To Import): On the Devices page (Devices > Devices), click the Import Devices button to open and use the Import Devices page. IMPORTANT: WSM requires that the import file has a list of all MAC addresses of the devices present in this file. The separators supported are comma, space, or end of line (that is, each MAC address of the device is on a new line in the file). You can find the MAC ID of a Wyse thin client on a sticker on the device (Wyse thin client MAC addresses start with 00 80 64). For MAC addresses of other WSM supported devices, contact the manufacturer. Also note that you can also specify hostname by using <mac>,<hostname>. MAC-address and hostname must be separated by a comma; requires a new line for each device. Caution Be sure the Device Template you want to use exists in the system (see "Adding Device Templates") before importing devices. Figure 75 Import Devices page Detailed Guidelines (To Import): 1. Select the Device Template you want to use (to set the attributes you want on Devices that are automatically added to the WSM system). 2. Enter the Device Import File (you can use Browse to find and select a file). The Device Group and other information for the Device Template are shown. 3. Click Import Devices. The devices are imported into the system and are shown in the list of available Devices on the Devices page. 89 Devices Managing Device Groups TIP: Device Groups allow you to easily group and manage devices with similar attributes from a single place, the Device Groups page. The Device Groups page (Devices > Device Groups) allows you to quickly view and manage the WSM Device Groups that are available (see Table 8). Figure 76 Device Groups page Although the Device Groups page shows you all of the Device Groups available in the WSM system, you can use the filtering feature to view the Device Groups you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Device Group (use only letters, numbers, dashes, spaces, the @ character, and periods). • OS Image - Name of the OS Image that is assigned to Device Group. Use the OS Image Select link to select the OS Image. After entering your criteria, click Filter to view the results. You can then select the Device Groups you want, and begin performing your tasks. 90 Chapter 8 Table 9 provides a quick overview of routine management tasks. Table 9 Routine Device Group Management Tasks Tasks You Can Do How Details Add a Device Group to the system. On the Device Groups page (Devices > Device Groups), click the Add button to open and use the Add Device Groups page. Click the Add button and use the Add Device Groups page. “Adding a Device Group” on page 92. Edit a Device Group in the system. Click a Name link in the Device Groups page and make your changes. “Editing Device Groups” on page 94. Delete a Device Group from the system. Select the check box next to the name of the Device Group you want in the Device Groups page, click Delete, and confirm the deletion. The Device Group is deleted and is no longer shown in the list of available Device Groups on the Device Groups page. You can also delete a Device Group by using the Delete this Device Group link on the Device Group Details page. Deleting a device group reassigns all devices in the group to the Default device group. You cannot delete the Default server group. CAUTION: Deleting a device group also clears all image assignments from the devices in the device group. Understanding the Default and User-Created Device Groups WSM provides two types of Device Groups, Default and user-created. The Default Device Group is created automatically. Administrators can create user-created Device Groups as needed. Devices cannot belong to more than one Device Group. Each Device must be in the Default Device Group or a user-created Device Group. TIP: You can move Devices in and out of the Default Device Group as they are needed in user-created Device Groups. You can also move Devices directly from one user-created Device Group to another. Attributes of each Device Group include: • Default Device Group: • WSM creates the Default Device Group during installation or during an upgrade. The Default Device Group is automatically assigned to the Default Server Group. There is only one Default Device Group. Its purpose is to store Devices until, if necessary, they are assigned to a user-created Device Group. • All Devices in the Default Device Group can be treated individually and can have their own unique Device Class, Connection Type, Server Group, and OS Image assignments. • Devices and Device Templates in the Default Device Group cannot boot in Load Balanced mode. • Devices in the Default Device Group can be managed (for Device Class, Connection Type, Server Group, and OS Image attributes) using their respective Administrator Console pages. Devices • 91 • You can move Devices in and out of the Default Device Group as they are needed in user-created Device Groups. • Because the Default Device Group permits individual Devices to have unique Device Class, Connection Type, Server Group, and OS Image assignments, a Device in a user-created Device Group retains its Device Class, Connection Type, Server Group, and OS Image assignments when it is reassigned to the Default Device Group. • You cannot delete or modify the Default Device Group. User-Created Device Group: • Administrators create user-created Device Groups as needed. • All Devices in a user-created Device Group must be treated the same and share Device Class, Connection Type, Server Group, and OS Image assignments. • By default, Load Balanced is the boot selection mode for Devices and Device Templates in a user-created Device Group. In Load Balanced boot mode, the system notes which Server in a Server Group is least loaded and assigns that Server Group to a particular Device in the Device Group (see "System Maintenance"). • Devices in a user-created Device Group must be managed (for Device Class, Connection Type, Server Group, and OS Image attributes) using the Device Group Details page in the Administrator Console. • You can move Devices directly from one user-created Device Group to another. • When you assign a Device to a user-created Device Group, its previous Device Class, Connection Type, Server Group, and OS Image assignments are stripped away; it adopts the Device Class, Connection Type, Server Group, and OS Image assignments of the user-created Device Group to which it was reassigned. • You can delete or modify a user-created Device Group. Deleting a user-created Device Group reassigns all Devices in it to the Default Device Group. 92 Chapter 8 Adding a Device Group Summary (To Add): On the Device Groups page (Devices > Device Groups), click the Add button to open and use the Add Device Group page. Detailed Guidelines (To Edit): 1. On the Device Groups page (Devices > Device Groups), click the Add button to open the Add Device Group page. Figure 77 Add Device Group page 2. Complete the Add Device Group page using the following guidelines: • Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and periods). • Enter a Description. • Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). • Select a Site/Template. • Select a Server Group (selecting a new Server Group clears the previous OS Image assignment for all the devices in Device Group). • (Devices assigned to a User-Created Device Group Only) Select the Boot Selection Mode for the Device Group (First Disk, First Available, User Select or Load Balancing). TIP: First Disk (default) specifies that the devices in the Device Group will always boot from the first OS Image that is assigned to the Device Group. First Available is the mode that is used for failover purposes. In this mode you can specify the same OS Image on multiple servers and use that specification as the assignment for two or more OS Images available. Thus, the devices in the Device Group will try and connect to the first server, and if the server is not available, the devices will try and connect to the remaining assigned servers as specified. User Select is the mode that allows users to specify from which OS Image the devices in the Device Group should boot. A menu is displayed for the user when the devices boot, allowing the user to specify the OS Image and server combination. Devices 93 Load Balancing is the mode that allows WSM to automatically specify from which OS Image the devices in the Device Group should boot (see "Load Balancing"). Select an OS Name (selecting a new OS Name clears the previous OS Image assignment for all the devices in Device Group). 3. Click Save Changes. The Device Group is added to the list of available Device Groups on the Device Groups page. 94 Chapter 8 Editing Device Groups CAUTION: You can edit a user-created Device Group only; you cannot edit the Default Device Group. TIP: After editing the settings, be sure to click Save Changes (the Device Group is then modified and can be viewed in the list of available Device Groups on the Device Groups page). Summary (To Edit): On the Device Groups page (Devices > Device Groups), click the Name link of the Device Group you want to edit to open the Device Group Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "Devices Tab" Details Tab Summary (To Edit): Use the Details tab to edit the general settings for the Device Group. Figure 78 Device Group Details tab Detailed Guidelines (To Edit): • Enter the Name. • (Optional) Enter a Description. • Select a Server Group (selecting a new Server Group clears the previous OS Image assignment for all the devices in Device Group). • Site Name is shown. • Site Group Name is shown. • Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still 95 Devices be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). • (Devices assigned to a User-Created Device Group Only) Select the Boot Selection Mode for the Device Group (First Disk, First Available, User Select or Load Balancing). TIP: First Disk (default) specifies that the devices in the Device Group will always boot from the first OS Image that is assigned to the Device Group. First Available is the mode that is used for failover purposes. In this mode you can specify the same OS Image on multiple servers and use that specification as the assignment for two or more OS Images available. Thus, the devices in the Device Group will try and connect to the first server, and if the server is not available, the devices will try and connect to the remaining assigned servers as specified. User Select is the mode that allows users to specify from which OS Image the devices in the Device Group should boot. A menu is displayed for the user when the devices boot, allowing the user to specify the OS Image and server combination. Load Balancing is the mode that allows WSM to automatically specify from which OS Image the devices in the Device Group should boot (see "Load Balancing"). Select an OS Name (selecting a new OS Name clears the previous OS Image assignment for all the devices in Device Group). Devices Tab CAUTION: If a device group is associated with a Site template, you must refer to the Sites associated with the Site Template to view or edit devices. Summary (To Edit): Use the Devices tab to edit the Device settings and assignments for the Device Group. Figure 79 Device Group Devices tab Detailed Guidelines (To Edit): • Delete a Device from the Device Group - Click the Delete button to delete a selected Device from the Device Group. • Send supported commands to Devices in the system - Select the Devices you want and click Send Command to open and use the Send Command page (see "Sending Commands to Devices in a Device Group"). 96 Chapter 8 • Abort the previously scheduled commands to Devices in the system - Select the Devices you want, click Abort Command to open a message confirming the removal of the commands, and then click OK to abort the commands. • Add or remove a Device to or from the Device Group - Click the Reassign Devices button to open and use the Move Devices from Device Group page (see "Reassigning Devices to a Different Device Group"). • Reset the state of Devices belonging to this Device Group - (Devices assigned to a User-Created Device Group Only) Select the Devices you want and click the Reset button to clear the Write Cache for the devices belonging to this Device Group. Note that if Device Group belongs to a load balanced Server Group, the Write Cache for the devices will be reset for all the servers in the Server Group. However, if the Device Group belongs to a non load-balanced Server Group, you can select the devices you want to reset. CAUTION: You cannot successfully use Reset if the OS Image and OS Server combination is currently being used (a currently being used message appears at the top of the Network Device Details page). In such a case, you must first shut down the devices, and then use Reset. Using Reset will cause all changes made to the OS Image by the devices to be lost. • Edit a Device belonging to this Device Group - Click a Name link in the Name area to open and use the Device Details page (see "Editing Devices"). 97 Devices Reassigning Devices to a Different Device Group Summary (To Reassign): While editing a Device Group (Devices > Device Groups > Name link > Devices tab), you can reassign Devices in a Device Group to a different Device Group by selecting the Device you want in the Name area, and then clicking the Reassign Devices button to open and use the Move Devices from Device Group page. Detailed Guidelines (To Reassign): 1. On the Devices tab of the Device Group Details page (Devices > Device Groups > Name link > Devices tab), select the Device you want in the Name area, and then click the Reassign Devices button to open the Move Devices from Device Group page. Figure 80 Move Devices from Device Group page 2. Select the Device Group to which you want the selected Devices assigned. 3. Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). • (Devices assigned to a User-Created Device Group Only) Select the Boot Selection Mode for the Device Group (First Disk, First Available, User Select or Load Balancing). TIP: First Disk (default) specifies that the devices in the Device Group will always boot from the first OS Image that is assigned to the Device Group. First Available is the mode that is used for failover purposes. In this mode you can specify the same OS Image on multiple servers and use that specification as the assignment for two or more OS Images available. Thus, the devices in the Device Group will try and connect to the first server, and if the server is not available, the devices will try and connect to the remaining assigned servers as specified. User Select is the mode that allows users to specify from which OS Image the devices in the Device Group should boot. A menu is displayed for the user when the devices boot, allowing the user to specify the OS Image and server combination. 98 Chapter 8 Load Balancing is the mode that allows WSM to automatically specify from which OS Image the devices in the Device Group should boot (see "Load Balancing"). 4. Select an OS Name (selecting a new OS Name clears the previous OS Image assignment for all the devices in Device Group). 5. Select the Streaming Server you want. 6. Click Save Changes. 99 Devices Sending Commands to Devices in a Device Group Summary (To Send Commands): While editing a Device Group (Devices > Device Groups > Name link > Devices tab), you can send supported commands (and schedule supported commands to be sent) to selected Device Groups (supported commands include Reboot, Shut down, and Wake on LAN) by selecting the Device you want in the Name area, and then clicking the Send Command button to open and use the Send Command page. Detailed Guidelines (To Send Commands): 1. On the Devices tab of the Device Group Details page (Devices > Device Groups > Name link > Devices tab), select the Device you want in the Name area, and then click the Send Command button to open the Send Command page. Figure 81 Send Command page 2. Select the command (Reboot, Shut down, or Wake on LAN) you want to send to the devices. 3. Complete one of the following: • To send the command now, select Send command now. • To send the command with a time delay, select Schedule command with time delay and enter a Time Delay in seconds (default is 300). • To send the command later, select Schedule for later to open and use the calendar (select the date, enter a time, and click Done). 4. Click Done to send the command (according to your schedule or Time Delay) and return to the Devices page. TIP: You can remove previously scheduled commands by going to the Device Group Details page (Devices > Device Groups > Name link > Devices tab), selecting the devices, clicking Abort Command to open a confirmation message, and then clicking OK. 100 Chapter 8 Managing Device Templates The Device Templates page (Devices > Device Templates) allows you to quickly view and manage the WSM Templates that are available (see Table 10). It also allows you to easily display the Device Templates you want by using the filtering feature. Figure 82 Device Templates page Although the Device Templates page shows you all of the Device Templates available in the WSM system, you can use the following guidelines to view the Device Templates you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Device Template (use only letters, numbers, dashes, spaces, the @ character, and periods). • Server - Name of the server to which the Device Template is assigned. Use the Server Select link to select the server. • Device Group - Name of the Device Group to which the Device Template is assigned. Use the Device Group Select link to select the Device Group. • Subnet Address - Subnet Address of the Device Template. • Connection Type - (all, Network, or Mobile Disconnected) After entering your criteria, click Filter to view the results. You can then select the Device Templates you want, and begin performing your tasks. 101 Devices Table 10 provides a quick overview of what you can do using the Device Templates page. Table 10 Routine Device Template Tasks - Device Templates page Tasks You Can Do How Details Add a Device Template to the system. Click the Add button and follow the wizard. “Adding Device Templates” on page 102. Edit a Device Template in the system. Click a Name link in the Device Templates page and make your changes. “Editing Device Templates” on page 104. Edit a Site in the system. Click a Site Name link in the Device Templates page and make your changes. “Editing Sites” on page 16. Delete a Device Template from the system. Select the check box next to the name of the Device Template you want in the Device Templates page, click Delete, and confirm the deletion. The Device Template is deleted and is no longer shown in the list of available Device Templates on the Device Templates page. You can also delete a Device Template by using the Delete this Device Template link on the Device Template Details page. 102 Chapter 8 Adding Device Templates Summary (To Add): On the Device Templates page (Devices > Device Templates), click the Add button to open and use the Add Device Template page. Detailed Guidelines (To Add): 1. On the Device Templates page (Devices > Device Templates), click the Add button to open the Add Device Template page. TIP: After a device template is added for WSM use, the Device Template can be used to set the attributes you want on Devices that are automatically added (whether through discovery or importing from files). You can only add a Device Template to an existing OS Image. For information on adding an OS Image, refer to "Registering OS Images." For information on importing Devices from a file, refer to "Importing Devices from a File." Figure 83 Add Device Template wizard 2. Complete the Add Device Template page using the following guidelines: • Enter a Name. • (Optional) Enter a Description. • If desired, select Specify a Subnet Range to enable, and then enter the Subnet Address and Subnet Mask. Note that only one Device Template without a Subnet Mask can be added to the WSM system. • (For Active Directory integration only) Select the Active Directory Organizational Unit (for example, wsm.com/CN=Computers). Note that the Organizational Unit you assign to the template will take precedence over the Default OU for the Domain. • Select a Site/Template. • Select a Server Group. • Select a Device Group. Devices • 103 Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). 3. Click Save Changes. The Device is added to the list of available Device Templates on the Device Templates page. 104 Chapter 8 Editing Device Templates TIP: After editing the settings, be sure to click Save Changes (the Device Template is then modified and can be viewed in the list of available Device Templates on the Device Templates page). CAUTION: Some options on the Device Template Details page can be edited only if you are working with Device Templates assigned to the Default Device Group or a User-Created Device Group. Summary (To Edit): On the Device Templates page (Devices > Device Templates), click the Name link of the Device Template you want to edit to open and use the Device Template Details page. Figure 84 Device Template Details page Detailed Guidelines (To Edit): • Enter the Name. CAUTION: A device template name cannot exceed 5 characters for a Site Template. • (Optional) Enter a Description. • (Device Templates assigned to the Default Device Group Only) Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force Provision option of either Enabled or Disabled). TIP: In Network mode, the device must always have a LAN connection to a WSM Server. In Mobile mode, the device can be disconnected from a WSM Server and still be operational. A Force Provision option of Enabled automatically provisions the mobile device with an OS Image when connected to, and booting from, a WSM Server. A Force Provision option of Disabled allows the user to provision the mobile device with an OS Image when desired (by right-clicking the WSM Client icon in the system tray and selecting Provision Disk). • (Device Templates assigned to the Default Device Group Only) Select the Boot Selection Mode for the device (First Disk, First Available, or User Select). TIP: First Disk (default) specifies that the device will always boot from the first OS Image that is assigned to it. First Available is the mode that is used for failover purposes. In this mode you can specify the same OS Image on multiple servers and use that specification as the Devices 105 assignment for two or more OS Images available. Thus, the device will try and connect to the first server, and if the server is not available, the device will try and connect to the remaining assigned servers as specified. User Select is the mode that allows users to specify from which OS Image the device should boot. A menu is displayed for the user when the device boots, allowing the user to specify the OS Image and server combination. • The Device Group, Server Group, and Image Name are shown. • (Device Templates assigned to the Default Device Group Only) Select an Image Name (selecting a new OS Image Name clears the previous OS Image assignment). • (For Active Directory Integration Only) The Active Directory Organizational Unit is shown (for example, wsm.com/CN=Computers). • If desired, select Specify a Subnet Range to enable, and then enter the Subnet Address and Subnet Mask. • Select the Status of the device template (Enabled or Disabled). For a device template to be Enabled you must assign an OS Image to it. • Optional Related Tasks you can perform using the Device Template Details page: • Add a Device Template - Click the Add Device Template link to open and use the Add Device Template wizard (see"Adding Device Templates"). • Delete this Device Template - Click the Delete this Device Template link to delete the device template. • Add or remove a Device Template to or from the Device Group - Click the Change Device Group link to open and use the wizard. • (Device Templates assigned to the Default Device Group Only) Add an OS Image Click the Add OS Image link to open and use the Add OS Image page (see "Adding an OS Image to a Device Template"). 106 Chapter 8 Changing the Device Group Assignment for a Device Template Summary (To Change): While editing a Device Template on the Device Template Details page (Devices > Device Templates > Name link > tab), you can assign a Device Template to all Devices in a user-created Device Group or to individual Devices in the Default Device Group by using the wizard. Detailed Guidelines (To Change): on the Device Template Details page (Devices > Device Templates > Name link > tab), 1. Click the Change Device Group link to open the Assign Device Groups For Device Template wizard. Figure 85 Assign Device Groups For Device Template wizard 2. Determine the Device Groups you want to include using the assignment page: • User-created Device Group - Select a user-created Device Group and click Next. The Device Template is assigned the OS Image and Streaming Server that is assigned to the Device Group you selected. Click Finish to return to the Device Template Details page. • Default Device Group - Select the Default Device group and click Next to open the Assign an OS Image page. 3. Determine the OS Image you want to include using the assignment page. 4. Click Next to open the Assign a Server page. 5. Determine the Server you want to include using the assignment page. 6. Click Finish. 107 Devices Adding an OS Image to a Device Template While editing a Device Template in the Default Device Group on the Device Template Details page, you can add an OS Image to a Device Template by using the following guidelines: 1. Click the Add OS Image link to open the Add an OS Image wizard. Figure 86 Add an OS Image wizard - Device Templates 2. Select the OS Image you want and click Next to open the Select a Streaming Server page. 3. Select the Streaming Server you want to assign to the Device Template. 4. Click Finish to return to the Device Template Details page. 108 Chapter 8 This page intentionally blank. 9 Users This chapter describes how to perform routine User and User Group management tasks using the Administrator Console. It also provides information to help you manage the Users and User Groups in your WSM system (with and without Active Directory integration). Topics include: • "About User Management: If Your WSM is Integrated with Active Directory Read this First" • "Managing Users without Active Directory Integration" · "Adding Users without Active Directory Integration" · "Editing Users without Active Directory Integration" • "About User Group Management: If Your WSM is Integrated with Active Directory Read this First" • "Managing User Groups" · "Adding User Groups" · "Editing User Groups" About User Management: If Your WSM is Integrated with Active Directory Read this First TIP: If your WSM system is not integrated with Active Directory, you can skip this section and go directly to "Managing Users without Active Directory Integration." If your WSM system is integrated with Active Directory, be aware of the following rules and relationships: • Users of the imported User Groups will automatically be added to the WSM User Name list on the Users page. • You must manage all Users by using Active Directory, not WSM. • Users must exist in Active Directory before they can exist in WSM. • To be included in WSM, Users must be marked as active in Active Directory. • User passwords are set and verified using/within Active Directory. • Users cannot be deleted from Active Directory using WSM. • Deleting a User Group by using WSM also removes the Users of that group from the WSM system. • You can filter and view Users using WSM (Users page). You can also click on a Name link on the Users page to view User details. However, you cannot edit Users or User settings using WSM. TIP: On the User Details page, you can also click the link of the Domain name to open the Active Directory Domain Details page (for details on editing a domain, refer to "Editing Domains"). • User settings and modifications you make using/within Active Directory will automatically update in WSM according to the settings you configure as described in "Active Directory Configuration." 110 Chapter 9 Managing Users without Active Directory Integration The Users page (Users > Users) allows you to quickly view and manage the WSM Users that are available (see Table 11). It also allows you to easily display the Users you want by using the filtering feature. Figure 87 Users page - without Active Directory integration Although the Users page shows you all of the Users available in the WSM system, you can use the following guidelines to view the Users you want (click the magnifying lens to expand the filtering feature): • User Name Contains - Name of a User (use only letters, numbers, dashes, spaces, the @ character, and periods). • Status - Status of the User (all, Enabled, or Disabled). After entering your criteria, click Filter to view the results. You can then select the Users you want, and begin performing your tasks. 111 Users Table 11 provides a quick overview of what you can do using the Users page. Table 11 Routine User Tasks - Users page Tasks You Can Do How Details Add a User to the system (your WSM system is not integrated with Active Directory). Click the Add button and use the Add Users wizard. “Adding Users without Active Directory Integration” on page 112. Edit a User in the system (your WSM system is not integrated with Active Directory). Click a Name link in the Users page and make your changes. “Editing Users without Active Directory Integration” on page 113. Quickly enable or disable a User in the system (your WSM system is not integrated with Active Directory). Click the Enable or Disable link in the Status list for the User. While you can enable or disable a User while editing a User (on the User Details page), you can quickly do this task directly on the Users page. Delete a User from the system (your WSM system is not integrated with Active Directory). Select the check box next to the name of the User you want in the Users page, click Delete, and confirm the deletion. The User is deleted and is no longer shown in the list of available Users on the Users page. You can also delete a User by using the Delete this User link on the User Details page. After deleting a User, a User attempting to access a subscribed application (or refreshing the list of available applications) will receive a message informing the User that the subscription to the application is no longer active. 112 Chapter 9 Adding Users without Active Directory Integration Summary (To Add): On the Users page (Users > Users), click the Add button to open and use the Add User wizard. Detailed Guidelines (To Add): 1. On the Users page (Users > Users), click the Add button to open the Add User wizard. Figure 88 Add Users wizard 2. Enter the User Name, Password, and password confirmation (Re-enter Password). 3. (Optional) Enter the First Name, Last Name, and Email address of the User. TIP: If User Groups exist in your WSM system, you can click Next and use the assignment page to determine the User Groups to which you want to assign the User. 4. Click Finish. The User is added to the list of available Users on the User page and can now subscribe, activate, and run WSM operating systems and applications. 113 Users Editing Users without Active Directory Integration TIP: After editing the settings, be sure to click Save Changes (the User is then modified and can be viewed in the list of available Users on the Users page). Summary (To Edit): On the Users page (Users > Users), click the Name link of the User you want to edit to open the User Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "User Groups Tab" Details Tab Summary (To Edit): Use the Details tab to edit the general settings for the User. TIP: To change the Password of a User, click the Change Password button to open and use the Settings Change Password page (see "Changing User Passwords without Active Directory Integration"). Figure 89 User Details page - Details tab - without Active Directory integration Detailed Guidelines (To Edit): • Enter the User Name. • (Optional) Enter the First Name, Last Name, and Email address of the User. • Select the Status of the User (Enabled or Disabled). 114 Chapter 9 User Groups Tab Summary (To Edit): Use the User Groups tab to edit the User Group settings for the User. Figure 90 User Details page - User Groups tab - without Active Directory integration Detailed Guidelines (To Edit): • Change a Group Assignment for a User - Use the Assign button to open and use the Assign User Groups for User page (allows you to assign a User to a User Group). Use the Unassign button to unassign a selected User from a User Group. • Edit the User Groups associated with the User - Click a Name link in the Name area to open and use the User Group Details page (see "Editing User Groups without Active Directory Integration"). • Show or hide the Application Licenses associated with the User - Click the Show or Hide link for a User in the Application Licenses list to show or hide the Application Licenses associated with the User. If you show the Application Licenses of a User, you can then click on the link for an Application License to open and use the Application License Details page (see "Editing Application Licenses"). 115 Users Changing User Passwords without Active Directory Integration Summary (To Change): While editing a User (Users > Users > Name link), click the Change Password button to open and use the Change Password for User page. Detailed Guidelines (To Change): 1. On the Users Details page (Users > Users > Name link), click the Change Password button to open the Change Password for User page. Figure 91 Change Password For User page 2. Enter the New Password. 3. Enter the password again in the Re-enter Password box. 4. Click Update Password. 116 Chapter 9 About User Group Management: If Your WSM is Integrated with Active Directory Read this First TIP: If your WSM system is not integrated with Active Directory, you can skip this section. If your WSM system is integrated with Active Directory, be aware of the following rules and relationships: • WSM integrates with Security Groups. • Security Groups are flat in structure and unique across all organizational structures. • Access to application licenses is granted through Security Groups (this model is based on the Windows file sharing security model). • User Groups are created in Active Directory, not in WSM. • To be included in WSM, User Groups must be marked in Active Directory. • User Passwords are set and verified using/within Active Directory. • User Groups cannot be deleted from Active Directory using WSM. • You can add and delete User Groups using WSM. You can edit the OS Images, Application Images, and Application Licenses associated with the User Group using WSM. However, you cannot edit User Groups and other User Group settings using WSM (you must use Active Directory). • User group settings and modifications you make using/within Active Directory will automatically update in WSM according to the settings you configure as described in "Active Directory Configuration." 117 Users Managing User Groups The User Groups page (Users > User Groups) allows you to quickly view and manage the WSM User Groups that are available (see Table 11). It also allows you to easily display the User Groups you want by using the filtering feature. Figure 92 User Groups page Although the User Groups page shows you all of the User Groups available in the WSM system, you can use the following guidelines to view the User Groups you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a User Group (use only letters, numbers, dashes, spaces, the @ character, and periods). • Application - Name of the application to which the User Group is assigned. Use the Application Select link to select the application you want. • Status - Status of the User Group (all, Enabled, or Disabled). After entering your criteria, click Filter to view the results. You can then select the User Groups you want, and begin performing your tasks. Table 11 provides a quick overview of what you can do using the User Groups page. Table 12 Routine User Group Tasks - User Groups page Tasks You Can Do How Details Add a User Group to the system (your WSM system is not integrated with Active Directory). Click the Add button and follow the wizard. “Adding User Groups without Active Directory Integration” on page 119. Add a User Group to the system (your WSM system is integrated with Active Directory). Click the Import link and use the Import Group from Active Directory page. “Adding User Groups with Active Directory Integration” on page 120. Edit a User Group in the system (your WSM system is not integrated with Active Directory). Click a Name link in the User Groups page and make your changes. “Editing User Groups without Active Directory Integration” on page 121. Edit a User Group in the system (your WSM system is integrated with Active Directory). Click a Name link in the User Groups page and make your changes. “Editing User Groups with Active Directory Integration” on page 123. Edit a Domain in the system (your WSM system is integrated with Active Directory). Click a Domain link in the User Groups page and make your changes. “Editing Domains” on page 149. 118 Table 12 Chapter 9 Routine User Group Tasks - User Groups page , Continued Tasks You Can Do How Details Quickly enable or disable a User Group in the system (it does not matter whether or not your WSM system is integrated with Active Directory). Click the Enable or Disable link in the Status list for the User Group. While you can enable or disable a User Group while editing a User Group (on the User Group Details page), you can quickly do this task directly on the User Groups page. IMPORTANT: Active Directory is not involved with this procedure, enabling or disabling a User Group by using WSM does not affect User Groups and Users in Active Directory. Delete a User Group from the system (your WSM system is not integrated with Active Directory). Select the check box next to the name of the User Group you want in the User Groups page, click Delete, and confirm the deletion. The User Group is deleted and is no longer shown in the list of available User Groups on the Device Groups page. After deleting a User Group, a User attempting to access a subscribed application (or refreshing the list of available applications) will receive a message informing the User that the subscription to the application is no longer active. IMPORTANT: Deleting a User Group by using WSM does not remove the Users of that group from the WSM system. Delete a User Group from the system (your WSM system is integrated with Active Directory). Select the check box next to the name of the User Group you want in the User Groups page, click Delete, and confirm the deletion. The User Group is deleted and is no longer shown in the list of available User Groups on the User Groups page. After deleting a User Group, a User from that group attempting to access a subscribed application (or refreshing the list of available applications) will receive a message informing the User that the subscription to the application is no longer active. IMPORTANT: Deleting a User Group by using WSM does remove the Users of that group from the WSM system, however, it does not remove the User Group or Users of that group from Active Directory. 119 Users Adding User Groups As a WSM administrator you can add a User Group. Once a User Group is added, you can then add members (Users) who can subscribe, activate, and run WSM operating systems and applications for that User Group. TIP: You can only add a member (User) to an existing User Group. If WSM is integrated with Active Directory, members (Users) are automatically added to the group according to your Active Directory settings. For information on adding User Groups without Active Directory integration, refer to "Adding User Groups without Active Directory Integration." For information on adding User Groups with Active Directory integration, refer to "Adding User Groups with Active Directory Integration." Adding User Groups without Active Directory Integration Summary (To Add): On the User Groups page (Users > User Groups), click the Add button and follow the wizard. Detailed Guidelines (To Add): 1. On the User Groups page (Users > User Groups), click the Add button to open the Add User Group wizard. Figure 93 Add User Group wizard 2. Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and periods). 3. Click Next to open the Assign Users page. 4. Select the Users you want to include using the assignment page. 5. Click Next to open the Assign Application Licenses page. 6. Select the Application Licenses you want to include using the assignment page. 7. Click Finish. The User Group is added to the list of available User Groups on the User Groups page. 120 Chapter 9 Adding User Groups with Active Directory Integration Summary (To Add): To add (import) a User Group for WSM use, click the Import link on the User Groups page to open and use the Importing User Group from Active Directory wizard. Detailed Guidelines (To Add): 1. On the User Groups page (Users > User Groups), click the Import link to open the Importing User Group from Active Directory wizard. Figure 94 Import User Group from Active Directory page 2. Select the User Groups you want by using the following guidelines: • Enter the group name you want in the Group Name Contains text box (use only letters, numbers, dashes, spaces, the @ character, and periods). • Enter the LDAP Context Root. • Enter the Max Results limit (zero to the limit of all Users in Active Directory). • After entering your filter criteria, click Filter to view the results. • Scroll through the list of User Groups and select the Group Names you want. 3. After selecting the User Groups you want, click Next, and then follow the wizard to assign application licenses and add the group. The User Group is added to the list of available User Groups on the User Groups page. TIP: Users of these imported User Groups will automatically be added to the WSM User Name list on the Users page. Users 121 Editing User Groups For information on editing User Groups without Active Directory integration, refer to "Editing User Groups without Active Directory Integration." For information on editing User Groups with Active Directory integration, refer to "Editing User Groups with Active Directory Integration." Editing User Groups without Active Directory Integration TIP: After editing the settings, be sure to click Save Changes (the User Group is then modified and can be viewed in the list of available User Groups on the User Groups page). Summary (To Edit): On the User Groups page (Users > User Groups), click the Name link of the User Group you want to edit to open the User Group Details page, and then use the tabs to edit the settings. Detailed Guidelines (To Edit): • "Details Tab" • "Users Tab" • "Applications Tab" Details Tab Summary (To Edit): Use the Details tab to edit the general settings for the User Group. Figure 95 User Groups Details page - Details tab - without Active Directory integration Detailed Guidelines (To Edit): • Enter the Name. • Select the Status of the User Group (Enabled or Disabled). 122 Chapter 9 Users Tab Summary (To Edit): Use the Users tab to edit the User settings for the User Group. Figure 96 User Groups Details page - Users tab - without Active Directory integration Detailed Guidelines (To Edit): • Change a User Assignment - Use the Assign button to open and use the Assign Users For Group page (allows you to assign a User to a User Group). Use the Unassign button to unassign a selected User from a User Group. • Edit a User associated with the User Group - Click a Name link in the Name area to open and use the User Details page (see "Editing Users without Active Directory Integration"). Applications Tab Summary (To Edit): Use the Applications tab to edit the Application License settings for the User Group. Figure 97 User Groups Details page - Applications tab - without Active Directory integration Detailed Guidelines (To Edit): • Change an Application License Assignment - Use the Assign button to open and use the Assign Application Licenses For Group page (allows you to assign an Application License to a User Group). Use the Unassign button to unassign a selected Application License from a User Group. • Edit the Application License associated with the User Group - Click a Name button in the Name area to open and use the Application License Details page (see "Editing Application Licenses"). 123 Users Editing User Groups with Active Directory Integration TIP: After editing the settings, be sure to click Save Changes (the User Group is then modified and can be viewed in the list of available User Groups on the User Groups page). If you are using WSM integrated with Active Directory, you can edit the OS Images, Application Images, and Application Licenses associated with the group. In addition, you can select the Status of a group (Enabled or Disabled) and delete a User Group from WSM. On the User Groups page (Users > User Groups), click the Name link of the User Group you want to edit to open the User Group Details page, and then use the following guidelines: Figure 98 User Group Details page - with Active Directory integration • The Name and Organizational Unit of the User Group are shown. • The Domain of the User Group is shown, however, you can edit the Domain. Click the link of the Domain to open and use the Active Directory Domain Details page (see "Editing Domains"). • Select the Status of the User Group (Enabled or Disabled). • Optional Related Tasks you can perform using the User Group Details page: • View a User associated with the User Group - In the Users tab, click a Name link to view the User Details page. • Change an Application License Assignment - In the Applications tab, select the check box next to the Name and click Assign in the Applications tab to open and use the Assign Application Licenses For Group page. • Edit the Application License associated with the User Group - Click a Name link in the Application Licenses Assigned To area to open and use the Application License Details page (see "Editing Application Licenses"). • • Delete this Group - Click the Delete this Group link to delete the User Group. • Import a User Group from Active Directory - Click the Import a User Group from Active Directory link to open and use the Import Groups from Active Directory page (see "Importing User Groups from a Domain"). • View a User associated with the User Group - Click a Name link in the Users Belonging To area to view the User Details page. • Change an Application License Assignment - Click the Change Application License Assignment link to open and use the Assign Application Licenses For Group page. 124 Chapter 9 This page intentionally blank. 10 Settings This chapter describes how to perform routine system management tasks using the Administrator Console. It also provides information to help you manage the system settings of your WSM system. Topics include: • "Database Configuration" • "Active Directory Configuration" • "Content Distribution Settings" • "Site Configuration Settings" • "Device/Server Settings" • "Password/License" • "Logs/Misc Tab" • "Managing Settings" • "Managing Active Directory Domains" • · "Active Directory Domains Page" · "Adding Domains" · "Editing Domains" "Managing Virtual Centers" 126 Chapter 10 Database Configuration Summary (To Configure): During the installation of a Core Server or Edge Server, database configuration settings are made through an installation wizard (for information on the initial installation and configuration settings of a database, refer to the procedures in "Step 2: Installing and Configuring the WSM Core Server" and "Step 5: Installing and Configuring a WSM Edge Server"). After the WSM system installation is complete, you can edit the database configurations by using the Database Configuration page (Settings > Database). Detailed Guidelines (To Configure): • "Database Connection Tab" • "Database Backup Tab" • "Renaming an SQL Server Tab" • "Database Others Tab" Database Connection Tab CAUTION: Changing configuration parameters from the Database Connection tab will cause an attempt to change database configurations for all active WSM servers in your system. Figure 99 Database Connection tab CAUTION: When editing the database configuration of an existing WSM Core Server, all of the related WSM Services (except for the WSM Administration Service) in the Core Server (as well as in any Edge Servers) must first be stopped. For information on stopping WSM Services from within the Administrator Console, refer to "Managing Services for a Server." Detailed Guidelines (To Configure): • Enter the Primary Database Server (default is localhost). • (Optional) Enter the SQL Server Port. The SQL Server port is optional if you are using the default port or SQL Browser service is running and no firewall is blocking the Browser service (UDP port 1434) access from WSM. • Enter the Database Server IP. • Enter the Database Name (default is StreamingDB). • Enter the User Name (default is wsmdb). • Enter the Password (default is password@123). 127 Settings Database Backup Tab Summary (To Configure): Use the Database Backup tab to enable and configure the database backup for the current Site. After configuring, be sure to click Change Configuration to save your settings. Figure 100 Database Backup tab Renaming an SQL Server Tab Summary (To Configure): Use the Rename SQL Server tab to rename an SQL Server Metadata name (so that it is consistent with the name of the host on which it is running). After configuring, be sure to click Change SQL Server Name to save your settings. Figure 101 Rename an SQL Server tab 128 Chapter 10 Database Others Tab Summary (To Configure): Use the Database Others tab to configure database backup and cleanup intervals. Figure 102 Database Others tab Detailed Guidelines (To Configure): • Database Backup Interval - Enter the time in minutes (default is 5 minutes). This interval defines the number of minutes between database backups. Note that this setting will not take effect until the WSM Administration Service is restarted on the Core Server of a Site. • Database Cleanup Interval - Enter the time in hours (default is 24 hours). This interval defines the interval for the task that cleans up the database tables (synchronization logs and old aggregation tables in WSM database). Aggregated site data is cleaned up from old tables if a site has been upgraded and new aggregation tables contain data for a site. 129 Settings Active Directory Configuration Summary (To Configure): WSM can be integrated with an Active Directory server for improved User and User Group management. You can enable (and configure) or disable Active Directory use within the WSM system by using the Active Directory Configuration page (Settings > AD). TIP: To select or clear the Enable Active Directory Integration check box, all Devices, Device Templates, Users, and User Groups must be deleted from the WSM system. Detailed Guidelines (To Configure): • "AD Configuration Tab" • "Active Directory Others Tab" AD Configuration Tab TIP: If you select the Enable Active Directory Integration check box, the Active Directory Configuration page expands. Figure 103 Active Directory Configuration tab TIP: After configuring the settings, be sure to click Update Active Directory Settings to save your settings. You can verify that Active Directory integration is correctly configured when you can successfully import User Groups and Users from Active Directory. Detailed Guidelines (To Configure): • Synchronizing Polling Frequency - Enter the Synchronizing Polling Frequency (number of seconds between synchronizing the members of User Groups between Active Directory and the WSM database; the default is 600 seconds, however, you can turn off the feature by setting the time to 0). • Enable SSL Connection - If desired, select to enable SSL (for information on using Active Directory integration with SSL, refer to "Details About Using Active Directory Integration"). IMPORTANT: If you enable SSL, be sure to import a certificate to allow SSL connections to be established with Active Directory as described in Table 13, "Routine Active Directory Domain Tasks - Active Directory Domains page." • Active Directory Domains - (Optional) Click the Active Directory Domains link to open the Active Directory Domains page (for details on managing Active Directory Domains, refer to "Managing Active Directory Domains"). • Reset - Use Reset to clear any changes you made (before clicking Update Active Directory Settings). 130 Chapter 10 Active Directory Others Tab Figure 104 Active Directory Others tab Detailed Guidelines (To Configure): • Use Alias for OU - If desired, you can select to display the alias name of the organization unit rather than the full name. • Re-use Device Names in AD - If desired, you can select to reuse a device entry in Active Directory while adding a device. Note that this setting will not take effect until the WSM Administration Service is restarted. 131 Settings Content Distribution Settings Summary (To Configure): Use the Content Distribution Settings page (Settings > CDS) to configure compression, http based distribution for Sites, client check-in intervals and cancellation thresholds, simultaneous download limits, and bandwidth control for all Sites. TIP: You can also monitor clients that are currently connected, waiting, disconnected, and have completed their downloads using WSM Web (see "Viewing Content Connections"). Detailed Guidelines (To Configure): • "CDS Configuration Tab" • "CDS Others Tab" CDS Configuration Tab Figure 105 CDS Configuration tab Detailed Guidelines (To Configure): • Enable Compression - Select to enable transfer of the OS Images and Application Images in a compressed format. The images will be uncompressed after they have been transferred to the destination. A folder for the compressed images will be created 132 Chapter 10 under the osimages and appimages directories where the compressed images will be stored. • Enable http based distribution for Sites - Select if you want to distribute content to the Core Server of a Linked Site using HTTP. This feature is only available for a Headquarters-based architecture. Note that the Core Server of each Linked Site will download content using http. Edge Servers for each Linked Site will use TCP/IP to download content from the Core Server of the Linked Site. · URL - (Only enabled after Enable http based distribution for Sites is enabled) Enter the Streaming Directory URL of the Headquarters Core Server. · Username and Password - (Only enabled after Enable http based distribution for Sites is enabled) Enter the Username and Password of the Headquarters Core Server. • Checkin Interval (Minutes) - Enter the number of minutes that a connected client should wait before checking in with headquarters. This allows the system to keep track of connected clients and ensure the connection is still valid. • Automatic Cancellation Threshold - Enter the threshold value for which a system waits before the system assumes that a connected client has lost its connection. For example, if you enter 3 for this value, the system will wait 3 times the expected check-in interval before assuming a client to be disconnected. • Limit Client Connections - Select if you want to limit simultaneous downloads from a Linked Site to Headquarters (to prevent the system from becoming un-responsive or slow, if number of simultaneous image downloads from Headquarters to Linked Sites reach a certain threshold). · Maximum number of simultaneous downloads - (Only enabled after Limit Client Connections is enabled) Enter the maximum number of clients you want to download content simultaneously. · Waiting Client Checkin Interval (Minutes) - (Only enabled after Limit Client Connections is enabled) Enter the number of minutes that a Linked Site should wait before attempting to check-in and retry a download request. The system denies a content download request if the Maximum number of simultaneous downloads is reached. • Limit Global Content Distribution Bandwidth - Select if you want to control the content download bandwidth for all sites (be sure to select the Start Time, End Time, and then enter the Bandwidth you want). Note that you can override these global settings for Site Groups by navigating to the Site Group Details page, or for an individual Linked Site by navigating to this Settings page on the Administrator Console of the Linked Site (see also "Editing Site Groups"). • Allow Alternative Bandwidth - (Only enabled after Limit Global Content Distribution Bandwidth is enabled) Select if you want a second control of the content download bandwidth for all sites (be sure to select the Alternative Bandwidth Start Time, Alternative Bandwidth End Time, and then enter the Alternative Bandwidth you want). Note that you can override these global settings for Site Groups by navigating to the Site Group Details page, or for an individual Linked Site by navigating to this Settings page on the Administrator Console of the Linked Site (see also "Editing Site Groups"). 133 Settings CDS Others Tab Figure 106 CDS Others tab Detailed Guidelines (To Configure): • Content Scheduler Interval - Enter the time in minutes (default is 5 minutes). This interval defines the interval for the task that automatically schedules OS Image, OS Image Patch, and Application Image content distribution to remote WSM Servers. • Content Distribution Client Interval - Enter the time in minutes (default is 1 minute). This interval defines the interval for the task that checks for scheduled or pending OS and Application Image copy or patch operations, including retries. • Enable Fast Patch - If selected, the WSM Fast Patch feature is enabled at remote servers and sites. This feature provides a mechanism to speed up the rate at which an remote site is updated to the latest version of an image. The process skips intermediate copy operations and/or checksum validations, and only the final image is validated. This feature can be useful in cases where a new Site is added to the WSM system after several patches have been deployed to other Sites that have been in the system for a significant amount of time. Note that WSM still preserves the ability to roll back to the prior image version (a dull image of the last-but-one version is preserved to enable a rollback to the prior version). • Forc e Version 5 Distribution - If selected, allows you to force WSM to use the new method even for OS images with version 4.x header. Note that the linked site must be updated to WSM 5.0.1 or this option will not work on that linked site. 134 Chapter 10 Site Configuration Settings Summary (To Configure): During the installation of a Core Server or Edge Server, Site configuration settings are made through an installation wizard. After the WSM system installation is complete, you can edit the Site configurations by using the Site Configuration page (Settings > Site). Detailed Guidelines (To Configure): • "Site Configuration Tab" • "Site Configuration Others Tab" Site Configuration Tab TIP: If you want to change a Headquarters to a Linked Site you must first change the Headquarters to a Stand-Alone Site and then change it to a Linked Site. Figure 107 Site Configuration tab - Headquarters Site example Detailed Guidelines (To Configure): • Synchronization Logs - Click the Synchronization Logs link to open the Synchronization page and view the synchronization process log entries for Headquarters to Site and Site to Headquarters. • Change Remote Service Password - Click the Change Remote Service Password link to open and use the Change Password page. If you change the Remote Service Password at Headquarters, you must change it on all Linked Sites. All Linked Sites must match the Headquarters Remote Service Password. Settings • 135 Choose a Site Category - You can select the Site category you want using the following guidelines: · Stand-Alone Site to Headquarters Site - See "Creating a Headquarters Site." · Stand-Alone Site to Linked Site - When changing a Stand-Alone Site to a Linked Site, be aware that the Linked Site will be periodically synchronized with a Site Template at Headquarters. Depending on configurations, prior entities created at the Linked Site such as images, server groups, and device groups, may be deleted during this process (see "Creating a Linked Site"). · Linked Site to Stand-Alone Site - When changing a Linked Site to a Stand-Alone Site, entities that the Linked Site inherited from the Site Template at Headquarters remain as is. However, the Linked Site is no longer synchronized with Headquarters and does not send its status information to Headquarters for reporting. · Headquarters Site to Stand-Alone Site - When changing a Headquarters Site to a Stand-Alone Site, be aware that the Headquarters cannot be changed if it is currently linked to other Linked Sites. • Name of the Site and Site Description - Enter the name and description you want. Be sure that the Name of the Site is unique across your organization. • Allow Multiple Server/Device Groups for Site Template - If selected, WSM will allow you to assign multiple Server Groups and Device Groups to a Site Template. However, WSM will not automatically assign servers to Server Groups and devices to Device Groups during a Site Template synchronization; you must assign these servers and groups manually. • Preserve Linked Site Local Data - If selected, WSM will preserve locally created entities like Server Groups, Device Groups, and so on, while synchronizing with the Site Template. If the check box is cleared, locally created entities are deleted during Site Template synchronization. • Locally Managed Sites - If selected, WSM will create links that will aggregate the data of the Linked Site at Headquarters, however, the Linked Site will not synchronize with the Site Template at Headquarters allowing the Linked Site to be managed locally. 136 Chapter 10 Site Configuration Others Tab Figure 108 Site Configuration Others tab - Headquarters Site example Detailed Guidelines (To Configure): • Aggregation Period - Enter the time in minutes (default is 5 minutes). This interval defines the time period between two occurrences of the aggregation process that propagates this site data to Headquarters. • Synchronization Period (with Site Template) - Enter the time in minutes (default is 60 minutes). This interval defines the number of minutes between two occurrences of the synchronization process that synchronizes this site with its site template at Headquarters. Note that you can view the synchronization process log entries for Site to Headquarters (and the Site Template synchronizations) on the Synchronization page (click the Site Configuration link on the Settings page, and then click the Synchronization Logs link on the WSM Sites Configuration page to open the Synchronization page). • Randomized Initial Time Range to Check In with HQ - Enter the time in minutes (default is 1 minute). Each Service that periodically checks in with Headquarters will randomly select a time between 0 and the threshold minutes specified to sleep before checking in with Headquarters for the first time. Note that this setting will not take effect until the WSM Administration Service is restarted. • Randomized Initial Time Range to Start Content Transfer - Enter the time in minutes (default is 1 minute). The Content Distribution Service will randomly select a time between 0 and the value in minutes you specify to sleep before starting content download from Headquarters to a Linked Site Core Server. Randomized delay will be used to sleep before starting the content distribution only if an administrator limits the connection bandwidth. Settings 137 • HQ manages Site Admin and Operator Password - If selected, WSM will not allow a Site Administrator (siteadmin) user password change from a Linked Site. It can only be managed from Headquarters. • Abort Site Conversion on Conflict - If selected, conflicts between a Stand-Alone Site and template on OS/Application Images will stop the conversion to a Linked Site. • Allow Template Change - If not selected, Site Templates are locked down at Headquarters. • Allow HQ Image Patch at Linked Site - If selected, allows you to patch the Headquarters OS and Application Images for the Linked Site from the Linked Site. • Max Rows per Page - Enter the maximum number of entries displayed in the aggregation reports and Sites page. • Enable Proxy DHCP Device Discovery - If selected, the device discovery flag for proxy DHCP service will be automatically enabled at a Linked Site. 138 Chapter 10 Device/Server Settings Summary (To Configure): Use the Device/Server Settings page (Settings > Device/Server) to configure general Device and Server check-in and monitoring settings. Detailed Guidelines (To Configure): • "Device Tab" • "Server Tab" Device Tab Figure 109 Device tab Detailed Guidelines (To Configure): • Client Statistics Log - If desired, you can select to record boot time statistics (such as last boot time, number of reboots, and so on) for a client. • Device Heartbeat Interval - Enter the time in seconds (default is 30 seconds). A client device that is up and running periodically informs its status to the server via a heartbeat. This heartbeat interval defines the number of seconds between two heartbeats sent by the device. • Device Heartbeat Timeout - Enter the time in minutes (default is 30 minutes). If the server does not receive a heartbeat within this allowed time limit, it will treat the client as Down and release resources held by the client. Note that if the client device later attempts to reconnect to the server and the resources are still available, the reconnect request will be granted and the client device will resume processing from where it was interrupted. • Device Boot Timeout - Enter the time in minutes (default is 5 minutes). If a client device does not complete boot-up processing within this time limit, it is marked as Down and its resources are released. Note that if the device is still actively booting up 139 Settings and if it is far enough along in the initialization process, it may re-establish communications with the server and complete its boot process. • Device Name Separator - Enter the character (default is _). This is the character used to separate the Device Template name and sequence number while generating a Device name from a Device Template. Note that this setting will not take effect until the WSM Administration Service is restarted. • Delete Write Cache on Shutdown - If selected, write cache files for volatile partitions on devices are deleted when the devices are shut down. Server Tab Figure 110 Server tab Detailed Guidelines (To Configure): • Server Monitoring Tasks Interval - Enter the time in seconds (default is 10 seconds). This interval defines the number of seconds between these tasks being run. Note that this setting will not take effect until the WSM Administration Service is restarted. • Services Monitoring Tasks Interval - Enter the time in seconds (default is 10 seconds). This interval defines the number of seconds between these tasks being run. Note that this setting will not take effect until the WSM Administration Service is restarted on all Core and Edge Servers. • Enable DHCP Proxy Service - If desired, you can select to enable the DHCP Proxy Service. If checked, the DHCP Proxy Service will be enabled and managed by the WSM Administration Service. If checked, be sure to shut down other DHCP Proxy Services that may be running on all the Core and Edge Servers. Note that after enabling the DHCP Proxy Service, you must restart the Admin Service on each WSM Server (both Core and Edge Servers). The Admin Service starts the DHCP thread during start-up if the appropriate flags are set in the WSM database. In addition, note that the enabled DHCP Proxy Service will appear in the Services list on the Server Details page where you can start and stop the service as described in 140 Chapter 10 "Editing Servers." However, you cannot view a separate log file for the DHCP Proxy Service as logs for this service are integrated with the other service logs listed on the Server Details page. • Enable TFTP Service - If desired, you can select to enable the TFTP Service. If checked, the TFTP Service will be enabled and managed by the WSM Administration Service. If checked, be sure to shut down other TFTP Services that may be running on all the Core and Edge Servers. Note that after enabling the TFTP Service, you must restart the Admin Service on each WSM Server (both Core and Edge Servers). The Admin Service starts the TFTP thread during start-up if the appropriate flags are set in the WSM database. In addition, note that the enabled TFTP Service will appear in the Services list on the Server Details page where you can start and stop the service as described in "Editing Servers." However, you cannot view a separate log file for the TFTP Service as logs for this service are integrated with the other service logs listed on the Server Details page. 141 Settings Password/License Summary (To Configure): Use the Password/License Settings page (Settings > Password/License) to configure general Password and Server License settings. Detailed Guidelines (To Configure): • "Passwords Tab" • "License Tab: Importing Server Licenses" Passwords Tab TIP: While a Headquarters administrator can always change the Site User Password for any Site User, the Headquarters administrator can prevent the Site Administrator from changing the siteadmin Password by selecting the HQ manages Site Admin and Operator Password check box on the Site Configuration Others tab (see "Site Configuration Others Tab"). Figure 111 Passwords tab Summary (To Configure): Select the user you want (admin, siteadmin, dispatcher, operator, siteoperator), enter the new password in the required boxes, and then click Update Password. 142 Chapter 10 License Tab: Importing Server Licenses Summary (To Configure): After initially logging in to the installation of a WSM Core Server and importing a Server License (see "Step 3: Starting the WSM Core Server for the First Time"), you can view the Server License information (valid dates and so on) or import a new Server License for the WSM system by using the License tab (use the Browse button to find and select your license file, and then click Import Server License). TIP: For information on Server License files, see "Server License Files." Figure 112 License tab 143 Settings Logs/Misc Tab Summary (To Configure): Use the Logs/Misc Settings page (Settings > Logs/Misc) to configure general log, aggregation thread pool size, and aggregation queue size settings. Figure 113 Settings tab Detailed Guidelines (To Configure): • Log Level for Log Files - Select the either Error, Warning, Info, Notify, Verbose, or Debug. The log level is a system-wide setting that determines the lowest level of messages to be logged in all log files for Services and applications. For example: if set to Error, only error messages are logged; if set to Debug all messages are logged. Note that this setting will not take effect until the WSM Administration Service is restarted. • Log File Size Limit - Enter the size (in kilobytes) up to a maximum of 102400 KB. Note that this setting will not take effect until the WSM Administration Service is restarted. If the log exceeds the maximum limit, then a .bak file is created. • Synchronization Log Retention Period - Enter the time in days (default is 5 days). This interval defines the number of days synchronization logs are kept in the database. • Aggregation Thread Pool Size - Enter the Thread Pool Size (default is 64). This is the aggregation thread pool size on Headquarters. You must restart the Headquarters server for this setting to take effect. • Aggregation Queue Size - Enter the Queue Size (default is 512). This is the aggregation queue size on Headquarters. You must restart the Headquarters server for this setting to take effect. 144 Chapter 10 Managing Settings Summary (To Configure): Clicking the Settings link on any functional area main page opens the Settings page. This page allows you to quickly view and manage the WSM system settings that are available. Figure 114 Settings page Detailed Guidelines (To Configure): TIP: After you have finished configuring the settings, be sure to click Update Settings to save your settings. Use Reset to clear any changes you made (before clicking Update Settings). • Connection Timeout for Synchronizing OS Image Properties - Enter the time in seconds (default is 10 seconds). When changing OS image property information (such as mode) on the OS Image Details page, a connection is established with each streaming server hosting the same OS image to synchronize the changes. • Licensing Model - Select either Fixed or Concurrent. A Fixed licensing model limits the total number of devices that can be added to WSM. A Concurrent licensing model limits the number of devices that can be UP at a certain time. • Connection Timeout for Adding a Virtual Center - Enter the time in seconds (default is 30 seconds). When adding a Virtual Center, WSM tries to establish a connection to the Virtual Center to validate the input data. If the connection details are incorrect, it can take a significant amount of time for the HTTP connection to time out. This field allows the administrator to set a time-out value in addition to the HTTP connection time-out value so that the UI does not remain in waiting mode for a long time. • Perform OS Image Synchronization- Select either Synchronously or Asynchronously. Synchronization of OS Image property changes can happen either synchronously or asynchronously upon submitting the form on the OS Image Details page. Note that if there are many streaming servers upon which synchronization must occur, it is recommended that this option be set to Asynchronously. • Enable OS Image Synchronization Daemon - If desired, you can select to enable the OS Image Synchronization Daemon. If you enable the OS Image Synchronization Daemon, enter the Retry Failed OS Image Synchronization Every time in seconds (default is 60 seconds). Note that if synchronization of OS Image property changes fails on a streaming server for any reason, a daemon thread (if enabled) will retry the synchronization for a specified interval until successful. Settings • 145 Optional Related Tasks you can perform using Quick-Links on the Settings page: · Manage OS Classes - Allows you to add, edit, and delete OS Classes (see "Managing Operating Systems"). · Manage Device Classes - Allows you to add, edit, and delete Device Classes (see "Managing Devices"). · Manage Device Templates - Allows you to view and manage the available WSM templates (see "Managing Device Templates"). · Active Directory Configuration - Allows you to enable or disable Active Directory (see "Active Directory Configuration"). · Content Distribution Configuration - Allows you to open and use the Content Distribution Setting page to configure compression, http based distribution for Sites, client check-in intervals and cancellation thresholds, simultaneous download limits, and bandwidth control for all Sites (see "Content Distribution Settings"). · Track Content Distribution - Allows you to open and use the Content Distribution Summary page to track content distribution status and progress (you can click on the Name link of a Content Entry to view the Content Distribution Details page for the entry). · Database Configuration - Allows you to access and edit the database configuration of a Core Server or Edge Server (see "Database Configuration"). · Site Configuration - Allows you to select a Site category for the current WSM installation (see "Site Configuration Settings"). · Virtual Center Configuration - Allows you to configure virtual center access from WSM (see "Managing Virtual Centers"). · Import Devices from File - Allows you to import Devices into the system from a file (see "Importing Devices from a File"). · Apply a Site Template - Allows you to open and use the Apply Site Template page to apply a Site template (XML file that has been generated by WSM) to a Site (Site template XMLs are used for disaster recovery purposes in large WSM environments with complex Site designs and are discussed in Advanced Administrators Guide: Wyse WSMTM). · OS Image Cleanup Configuration - Allows you to open and use the OS Image Cleanup Settings page to configure the settings you want for OS Image cleanup (select the Delete Older or Rolled-back OS Images check box and then configure the available settings you want). This feature is useful after a number of patches are deployed, as WSM servers can run out of disk space (WSM retains a full copy of all prior images). It allows you to control images you want to keep (deleting images from all servers other than the server where the image was registered - for example, images and their patches registered on the core servers of HeadQuarters and Linked Sites will not be deleted). 146 Chapter 10 Managing Active Directory Domains This section describes how to perform routine Active Directory Domains tasks in the WSM system. It provides information on adding, editing, and deleting Active Directory Domains by using the Active Directory Domains page. Active Directory Domains Page Clicking the Active Directory Domains link from the Active Directory Configuration page (or the Domains link in the Category area of the Overview main page) opens the Active Directory Domains page. This page allows you to view and manage Active Directory Domains that are managed by WSM. It also allows you to easily display the Active Directory Domains you want by using the filtering feature. Figure 115 Active Directory Domains page Although the Active Directory Domains page shows you all of the Domains managed by the WSM system, you can use the following guidelines to view the domains you want (click the magnifying lens to expand the filtering feature): • Name Contains - Name of a Domain (use only letters, numbers, dashes, spaces, the @ character, and periods). • Status - Status of the Domain (all, Enabled, or Disabled). After entering your criteria, click Filter to view the results. You can then select the Domains you want, and begin performing your tasks. 147 Settings Table 13 provides a quick overview of what you can do using the Active Directory Domains page. Table 13 Routine Active Directory Domain Tasks - Active Directory Domains page Tasks You Can Do How Details Add a Domain to the system. Click the Add Domain link and follow the wizard. “Adding Domains” on page 148. Edit a Domain in the system. Click a Name link in the Domains area and make your changes. “Editing Domains” on page 149. Quickly enable or disable a Domain in the system. Click the Enable or Disable link in the Status list for the Domain. While you can enable or disable a Domain while editing a Domain (on the Active Directory Domain Details page), you can quickly do this task directly on the Active Directory Domains page. Delete a Domain from the system. Select the check box next to the name of the Domain you want in the Domains area, click Delete Selected, and confirm the deletion. The Domain is deleted and is no longer shown in the list of available Domains on the Active Directory Domains page. You can also delete a Domain by using the Delete this Domain link on the Active Directory Domain Details page. IMPORTANT: Domains can be only deleted from a WSM Server if all of the User Groups imported from that domain are deleted from the WSM system as described in "Managing User Groups." Import a certificate to allow SSL connections to be established with Active Directory (you are using Active Directory integration with SSL). Click the Import Certificate link and use the Import Certificates page. After importing the certificate into the system. The certificate is shown in the list of available certificates on the Active Directory Domains page (the certificate now allows SSL connections to be established with Active Directory). If you are using Active Directory integration without SSL, you will not see the Import Certificate link as it is not needed for this mode of operation. Delete a certificate from the system (you are using Active Directory integration with SSL). Select the check box next to the name of the certificate you want in the Certificates area, click Delete Selected, and confirm the deletion. The certificate is deleted and is no longer shown in the list of available certificates on the Active Directory Domains page. 148 Chapter 10 Adding Domains Summary (To Configure): On the Active Directory Domains page, click the Add Domain link to open and use the Add Domain page. Detailed Guidelines (To Configure): 1. On the Active Directory Domains page, click the Add Domain link to open the Add Domain page. Figure 116 Add Domain page 2. Enter the Domain Name (use the full Domain Name; for example, wsm1.com). 3. (Optional) Enter the DC Hostname or IP Address. 4. Enter the Active Directory User (be sure that this User is a member of the Account Operators group). 5. Enter the Password. 6. (Optional) Select the Enable Kerberos Authentication to enable verification of a user or host identity. 7. Select the Status (Enabled or Disabled). 8. Click Finish. The Domain is added to the list of available domains on the Active Directory Domains page. 149 Settings Editing Domains Summary (To Configure): On the Active Directory Domains page, click the Name link of the Domain you want to edit to open and use the Active Directory Domain Details page. TIP: After editing the settings, be sure to click Save Changes (the Domain is then modified and can be viewed in the list of available Domains on the Active Directory Domains page). Figure 117 Active Directory Domain Details page Detailed Guidelines (To Configure): • Enter the Domain Name (use the full Domain Name; for example, wsm1.com). • (Optional) Enter the DC Hostname or IP Address. • Enter the Active Directory User. • Enter the Password. • The Connection Status is shown. • (Optional) Select the Enable Kerberos Authentication to enable verification of a user or host identity. • Select the Status (Enabled or Disabled). • Default OU (for new devices) is shown, however, you can click the Select link to open the Select an Organization Unit dialog box and select the an OU from the list (be sure to click Done to save your selection). • Optional Related Tasks you can perform using the Active Directory Domain Details page: • Add a new Domain - Click the Add a new Domain link to open and use the Add Domain wizard (see "Adding Domains"). • Import User Groups from a Domain - Click the Import Groups from this Domain link to open and use the Import Groups from Active Directory page (see "Importing User Groups from a Domain"). 150 Chapter 10 • Edit the User Groups associated with a Domain - Click a Name link in the Contains These Groups area to open and use the User Group Details page (see "Editing User Groups with Active Directory Integration"). • Add a Device OU where new devices can be added to Active Directory - Click the Add a device OU link to open and use the Add Device Organizational Unit page. Note that when entering the Name of the OU, use only letters, numbers, dashes, spaces, the @ character, and periods, as special characters may cause problems when importing User Groups and Users. When entering the Context Path of the OU, use the following examples for formatting, ou=FinanceOU,dn=wsm1, dn=com. The Device OU added is available for you to use when adding and editing Devices and Device Templates. • Delete an OU managed by the Active Directory Domain - Select the check box next to the name of the device organizational unit you want in the Device Organizational Unit Managed by area, click Delete Selected, and confirm the deletion. The device organizational unit is deleted and is no longer shown in the list of available device organizational units on the Active Directory Domain Details page. Note that device organizational units can only be deleted if the Device OU does not contain computer accounts for the devices added to the WSM system. 151 Settings Importing User Groups from a Domain While editing a Domain Active Directory Domain Details page, you can import User Groups from a Domain by using the following guidelines: 1. Click the Import Groups from this Domain link to open the Import Groups from Active Directory page. Figure 118 Import User Groups from Active Directory page 2. Select the User Groups you want by using the following guidelines: • Enter the Group Name Contains (use only letters, numbers, dashes, spaces, the @ character, and periods). • (Optional) Enter the LDAP Context Root. • Enter the Max Results Limit (zero to the limit of all User Groups in Active Directory Domain). • After entering your filter criteria, click Filter to view the results. • Scroll through the list of User Groups and select the check box for the User Group Name you want (you can use the Select All or Deselect All links to select User Groups in the list). 3. After selecting the User Groups you want, click Import Selected. The User Groups you selected are added to the Name list on the Active Directory Domain Details page. Note that Users of these imported User Groups will automatically be added to the WSM User Name list on the User Group Details page. 152 Chapter 10 Managing Virtual Centers This section describes how to create virtual machines by using the WSM in conjunction with the VMWare Virtual Center software. To create virtual machines in WSM, you must first create a template from a “model” virtual machine in the VMWare Virtual Center and then use the template in WSM. The virtual machines you create in WSM can then be managed from the Settings page by clicking Virtual Center Configuration and using the Virtual Centers page. TIP: After your initial virtual machine creation, you can skip steps that are not necessary (for example, you can skip to step 3 and continue to create virtual machines based on the same configurations you originally made in steps 1 and 2). Step 1: Create a Virtual Machine Template in VMWare Using the VMWare Virtual Center, create a “model” virtual machine with the parameters you want for the virtual machines you want to create in WSM. That is, select the operating system type, memory settings, and so on that you want to duplicate later in the virtual machines you will create in WSM. After creating the model, create a template from that virtual machine to use in WSM. Step 2: Add a Virtual Center in WSM To add a virtual center in WSM (where you will use the template): 1. On the Systems Settings page, click the Virtual Center Configuration link to open the Virtual Centers page. TIP: In future use after adding a virtual center, you can click on a virtual center Host link to open the Virtual Center Details page and view its details. Figure 119 Virtual Centers page 2. Click the Add Virtual Center link to open the Adding Virtual Center wizard. 153 Settings Figure 120 Add Virtual Center wizard 3. Complete the Add Virtual Center page using the following guidelines: · If you need to import a certificate in order to communicate with the Virtual Center over SSL, click the import the SSL certificate link to open and use the Import Certificate page (enter the Name, Certificate File location, and click Finish). Note that the default location of the certificate is C:\Documents and Settings\All Users\Application Data\VMWare\VMWare VirtualCenter\SSL. • Enter the Virtual Center Hostname or IP Address (the address of the server where the virtual center will run). • (Optional) Enter the Virtual Center Port (port number). • Select the Enable SSL Connection check box if the virtual center is only accessible by SSL. Note that if the virtual center is only accessible by SSL (default), an administrator must be sure to import an SSL certificate. • Select the Validate Server Certificate check box if you want to enable certificate validation. • Enter the User ID (your user ID). • Enter the Password (your password). • Enter the Data Center Name. 4. Click Next to open Assign Templates page. 5. Determine the templates you want to include using the assignment page. 6. Click Finish. After you click Finish, WSM tests the connection to the virtual center to ensure that it is valid, and then adds the valid virtual center to the list of virtual centers on the Virtual Centers page. 154 Chapter 10 Step 3: Create Virtual Machines 1. On the Systems Settings page, click the Virtual Center Configuration link to open the Virtual Centers page. 2. Click on a virtual center link to open the Virtual Center Details page Figure 121 Virtual Center Details page 3. Click Create Virtual Machine to open the Create Virtual Machine page. TIP: For future creations or when editing a Virtual Center, you can use the Change Template Assignment link to open the Assign Templates page and select the template you want from the list of All Unassigned Templates, click Add to assign the template, and then click Done. Figure 122 Create Virtual Machine page 4. Use the following guidelines: • Select the Template Name (the template on which you want to base the virtual machine). • Enter the VM Name prefix (used for the first half of the name you want to use for the virtual machine). • Enter the Start sequence number (used for the second half of the name you want to use for the virtual machine). Settings 155 • Enter the Number of Virtual Machines that you want to create. • Enter the Folder for the VMs (you can enter the folder name or full folder path excluding the data center name in the format: Engineering/Software/Virtual Machines). • Click Create. After you click Create, the virtual machines are added to the list of virtual machines on the Virtual Machines page. TIP: In future use after adding a virtual machine, you can open the Virtual Centers page and click on the View status of last virtual machine creation request link to open the Virtual Machines page and view its details. 156 Chapter 10 This page intentionally blank. 11 Reports This chapter provides instructions on using the Administrator Console to display and generate various reports on your WSM environment. Topics include: • "Overview of the Reports Page" • "Transaction History" • "Alerts History" • "Client Report" • "License Usage Report" • "Standard Usage Report" • "Activation Report" • "Subscription Report" Overview of the Reports Page The Reports page (click Reports from any functional area main page) allows you to quickly generate all of the WSM reports that are available. Figure 123 • Reports page Aggregated Reports for Sites running WSM versions earlier than 4.0 ONLY (at Headquarters, these reports include information that is aggregated from all its linked sites running WSM versions earlier than 4.0 only; at a Stand-Alone Site running WSM versions earlier than 4.0 or at a Linked Site running WSM versions earlier than 4.0, these reports include information only from that Site): • Aggregated Servers - Details on server and service status information. • Aggregated Servers/Images - Details on server and image information. • Aggregated Devices - Details on device information. 158 Chapter 11 TIP: While Aggregated Reports continue to display report information on Sites that have not yet upgraded to WSM 4.0, information on Servers, OS Images, Application Images, and Devices in the WSM 4.0 system can be found in the filtered views of the WSM Web (see "WSM Web"). IMPORTANT: If you do not have Sites running WSM versions earlier than 4.0, the Aggregated Reports will display blank. • CSV Reports: CSV Reports - Reports that can be exported to a file in CSV format. Other • Audit Reports: Transaction History - Details on the history of transactions performed by the Administrator. • Alert Reports: Alerts History - Details on the history of generated alerts. • Client Report - Details on all the unique clients that have connected to the server. • License Usage Report - Details on all current application usage. • Standard Usage Report - Details on past application usage for all Users and User Groups. • Activation Report - Details on all application activations and deactivations. • Subscription Report - Details on which users are subscribed to which applications. TIP: You can sort report lists according to a heading by clicking on the column heading you want. You can also list your selected heading in ascending or descending order by clicking on that column heading again. NOTE: CSV Reports you can generate and export to CSV files include: AggregatedDevices, AggregatedServer Image, AggregatedServers, sites that have not checked in the last two days, sites that have not checked in the last five days, and sites that have not checked in the last thirty days. Figure 124 CSV reports 159 Reports Transaction History TIP: You can enter the Number of Entries you want to display and click Filter. Use the Transaction History report (Reports > Transaction History) to display an historical log of selected actions by WSM users such as the following notable actions: • Publishing of a Site Template • OS Image and Application Image registration/deletion • Adding/Updating/Deleting of entities such as Site Group, Site, and Reference Site • Changes to Systems Settings • Site Group/Image deployments Figure 125 Transaction History report 160 Chapter 11 Alerts History TIP: You can enter the Number of Entries you want to display and click Filter. Use the Alerts History report (Reports > Alerts History) to display entries of selected alerts by WSM such as a server being down. Figure 126 Alert History report Client Report Use the Client Report page (Reports > Client Report) to generate a report that includes information on all unique clients that have connected to the server. Figure 127 Client Report page 1. On the Reports page, click Client Report to open the Client Report page. 2. Select the report criteria you want by using the following guidelines: • Enter a user Group Name or a User Name (use only letters, numbers, dashes, spaces, the @ character, and periods). • To view usage for all Users/all User Groups, leave the corresponding entries blank. 3. After entering your report criteria, click Display Report to generate the report. 161 Reports License Usage Report Use the License Usage Report page (Reports > License Usage Report) to generate a report that includes information on all current application usage. Figure 128 License Usage Report page 1. On the Reports page, click License Usage Report to open the License Usage Report page. 2. Select the report criteria you want by using the following guidelines: • Enter a user Group Name or a User Name (use only letters, numbers, dashes, spaces, the @ character, and periods). • To view usage for all Users/all User Groups, leave the corresponding entries blank. 3. After entering your report criteria, click Display Report to generate the report. Standard Usage Report Use the Standard Usage Report page (Reports > Standard Usage Report) to generate a report that includes information on past application usage for all Users and User Groups. Figure 129 Standard Usage Report page 1. On the Reports page, click Standard Usage Report to open the Standard Usage Report page. 2. Select the report criteria you want by using the following guidelines: • Enter a user Group Name or a User Name (use only letters, numbers, dashes, spaces, the @ character, and periods). • To view usage for all Users/all User Groups, leave the corresponding entries blank. 3. After entering your report criteria, click Display Report to generate the report. 162 Chapter 11 Activation Report Use the Activation Report page (Reports > Activation Report) to generate a report that includes information on all application activations and deactivations. Figure 130 Activation Report page 1. On the Reports page, click Activation Report to open the Activation Report page. 2. Select the report criteria you want by using the following guidelines: • Enter a user Group Name or a User Name (use only letters, numbers, dashes, spaces, the @ character, and periods). • To view usage for all Users/all User Groups, leave the corresponding entries blank. 3. After entering your report criteria, click Display Report to generate the report. Subscription Report Use the Subscription Report page (Reports > Subscription Report) to generate a report that includes information on which Users are subscribed to which applications. Figure 131 Subscription Report page 1. On the Reports page, click Subscription Report to open the Subscription Report page. 2. Select the report criteria you want by using the following guidelines: • Enter a user Group Name or a User Name (use only letters, numbers, dashes, spaces, the @ character, and periods). • To view usage for all Users/all User Groups, leave the corresponding entries blank. 3. After entering your report criteria, click Display Report to generate the report. 12 WSM Web This chapter describes how to access and use the WSM Web page. It provides information and instructions to help you monitor WSM Servers, Devices, OS Image and Application Image assignments, and distribution information for all sites. In addition, it provides information to help administrators and dispatchers perform routine deployment tasks (schedule and deploy OS Images and OS Image Patches from WSMWeb). Accessing and Using WSM Web Access to WSM Web and the features you can use depend on your role. Administrators Administrators have full privileges to all WSM Web features. Access includes: • Clicking the WSM Web link from any functional area main page of the Administrator Console. • Opening a Web browser from any machine with access to the WSM Core Server, going to: http://<ipaddress>:8080/wsmweb/, and then logging in using your correct Admin Username (default is admin) and Password (default is admin). Dispatchers Dispatchers can: • View and monitor all pages of WSM Web. • Deploy OS Images to Site Groups (see "Performing Deployment Tasks"). Access includes: • Opening a Web browser from any machine with access to the WSM Core Server, going to: http://<ipaddress>:8080/wsmweb/, and then logging in using your correct Dispatcher Username (default is dispatcher) and Password (default is dispatcher). Operators Operators can: • View and monitor all pages of WSM Web. Access includes: • Opening a Web browser from any machine with access to the WSM Core Server, going to: http://<ipaddress>:8080/wsmweb/, and then logging in using your correct Operator Username (default is operator) and Password (default is operator). 164 Chapter 12 Understanding the WSM Web Page The WSM Web page allows you to quickly view important information about the WSM Servers, OS Images, Application Images, and Devices in the system. It consists of the Navigation Tree (left pane) and Content Area (right pane). While Administrators, Dispatchers, and Operators can view/monitor WSM Web information, only Administrators and Dispatchers can use the deployment view to undertake a deployment task. In general: • Monitor View - When viewing/monitoring WSM Web information, use the Navigation Tree to select the Site Groups you want (expand the tree nodes as needed; the selected tree node will display in bold) and view the relevant Site Group information for your selection. For example, if you select All Site Groups, information on all of your Site Groups will be included in the Content Area. Likewise, if you select a specific Site Group, only information on that specific Site Group will be included in the Content Area. • Deployment View - While in the deployment view (click the Deployment View link), use the Navigation Tree to select the OS Images, Site Groups, and Content Connections you want (expand the tree nodes as needed; the selected tree node will display in bold) and view the relevant information for your selection. For example, if you select OS Images, information on all of your OS Images (such as Site Groups that have an OS Image/patch deployed or scheduled) will be included in the Content Area. Likewise, if you select a specific OS Image, only information on that specific OS Image (such as Site Groups that have that specific OS Image/patch deployed or scheduled) will be included in the Content Area. Figure 132 WSM Web Home page - administrator example Tabs on the WSM Web page include: • Server - Details on server and service status information (see "Viewing Server Information"). • OS - Details on server and OS Image information (see "Viewing OS Image Information"). • Application - Details on server and Application Image information (see "Viewing Application Image Information"). • Devices - Details on device information (see "Viewing Device Information"). WSM Web 165 Links on the WSM Web page include: • Home - Opens the WSM Web home page. • Deployment View (Administrators and Dispatchers Only) - Opens the Overview page, where you can quickly see the OS Image and Site Group deployment information (total, disabled, unassigned) of your WSM system (see "Performing Deployment Tasks"). • Hide/Show Navigation Tree - Allows you to hide and show the navigation tree for optimal viewing. • WSM Admin - Allows administrators to view and use the WSM Administrator Console. • About - Provides information about the WSM software and product license. • Sign Out - Allows you to log out of the WSM system. 166 Chapter 12 Viewing Server Information The Server page (click the Server tab) displays important information on server and service status. Figure 133 Server page - administrator example Although the Server page can show you server and service status information aggregated from all linked site groups, you can use the Navigation Tree (click the folders you want) and the following guidelines to view the information you want: • Name Contains - Name of a Server for client support (use only letters, numbers, dashes, spaces, the @ character, and periods). • IP Address - IP Address of the Server. • OS Service Status - Status of the OS Service (all, Up, or Down). • App Service Status - Status of the Application Service (all, Up, Down, Idle, or Error). • Server Status - Status of the Server (all, Up, or No Response). • Page Size - Maximum number of rows to display on a page (enter the number and press Enter). TIP: Use the Not check boxes to search for the all remaining options in the list except the option you selected. When you change search criteria, the table is refreshed with the new search result. You can use Reset to clear any current filter selections you have entered. 167 WSM Web Viewing OS Image Information The OS page (click the OS tab) displays important information on server and OS Images. Figure 134 OS page - administrator example Although the OS page can show you server and OS Image information aggregated from all linked site groups, you can use the Navigation Tree (click the folders you want) and the following guidelines to view the information you want: • Deployed Image Name Contains - Name of the OS Image to which a Server is currently assigned (use only letters, numbers, dashes, spaces, the @ character, and periods). • Pending Image Name Contains- Name of the OS Image to which a Server will be assigned.(use only letters, numbers, dashes, spaces, the @ character, and periods). • Image Status - Select the status you want included (Completed, Scheduled, In Progress, Cancelled, or Failed). For OS Image status details, see "OS Image Status Details." • Page Size - Maximum number of rows to display on a page (enter the number and press Enter). TIP: Use the Not check boxes to search for the all remaining options in the list except the option you selected. When you change search criteria, the table is refreshed with the new search result. You can use Reset to clear any current filter selections you have entered. 168 Chapter 12 OS Image Status Details OS Image status details/sub-categories include the following: • • • • • Completed: • Completed • Completed, Ready for Distribution Scheduled: • Scheduled • Prescheduled • Fast copy scheduled • Scheduled To Site • Fast patch scheduled In Progress: • Assigned • In Progress • Patch In Progress • CRC Check In Progress • Source CRC Computation In Progress • Source CRC Computation Completed • Compression In Progress • Decompression In Progress • Compression Completed • Parent Image CRC Check In Progress • Parent Image CRC Check Failed • Merged Content CRC In Progress • Fast patch in progress • Waiting For Connection Slot • Download paused Cancelled: • Cancellation Requested • Canceled Failed: • Failed • Source CRC Computation Failed • Patch Failed • CRC Comparison Failed • Compression Failed • Decompression Failed • Fast patch failed • Merged Content CRC Failed 169 WSM Web Viewing Application Image Information The Application page (click the Application tab) displays important information on server and Application Images. Figure 135 Application page - administrator example Although the Application page can show you server and Application Image information aggregated from all linked site groups, you can use the Navigation Tree (click the folders you want) and the following guidelines to view the information you want: • Deployed Image Name Contains - Name of the Application Image to which a Server is currently assigned (use only letters, numbers, dashes, spaces, the @ character, and periods). • Pending Image Name Contains- Name of the Application Image to which a Server will be assigned.(use only letters, numbers, dashes, spaces, the @ character, and periods). • Image Status - Select the status you want included. For Application Image status details, see "Application Image Status Details." • Page Size - Maximum number of rows to display on a page (enter the number and press Enter). TIP: Use the Not check boxes to search for the all remaining options in the list except the option you selected. When you change search criteria, the table is refreshed with the new search result. You can use Reset to clear any current filter selections you have entered. 170 Chapter 12 Application Image Status Details Application Image status details/sub-categories include the following: • • • Completed: • Completed • Completed, Ready for Distribution • App Patch Completed Scheduled: • Scheduled • Prescheduled • Scheduled To Site In Progress: • • • Assigned • In Progress • Patch In Progress • CRC Check In Progress • Source CRC Computation In Progress • Source CRC Computation Completed • App Prefetch In Progress • App Prefetch Completed • App Notification In Progress • App Notification Completed • App Patch In Progress • Compression In Progress • Decompression In Progress • Compression Completed • Parent Image CRC Check In Progress • Parent Image CRC Check Failed • Merged Content CRC In Progress • Waiting For Connection Slot • Download paused Cancelled: • Cancellation Requested • Canceled Failed: • Failed • Source CRC Computation Failed • App Prefetch Failed • Patch Failed • CRC Comparison Failed • App Notification Failed • App Patch Failed • Compression Failed • Decompression Failed • Merged Content CRC Failed 171 WSM Web Viewing Device Information The Device page (click the Device tab) displays important information on devices. Figure 136 Device page - administrator example Although the Device page can show you device information aggregated from all linked site groups, you can use the Navigation Tree (click the folders you want) and the following guidelines to view the information you want: • Name Contains - Name of a device (use only letters, numbers, dashes, spaces, the @ character, and periods). • OS Name Contains - Name of the OS Image to which the device is assigned (use only letters, numbers, dashes, spaces, the @ character, and periods). • IP Address - IP Address of the device. • Device Status - Status of the device. • MAC Address - MAC Address of the device. • Page Size - Maximum number of rows to display on a page (enter the number and press Enter). TIP: Use the Not check boxes to search for the all remaining options in the list except the option you selected. When you change search criteria, the table is refreshed with the new search result. You can use Reset to clear any current filter selections you have entered. 172 Chapter 12 Performing Deployment Tasks The Deployment Overview page (click the Deployment View link in the Navigation Tree) allows you to quickly view important deployment information about the OS Images and Site Groups in the system. By using the pages displayed by your Navigation Tree selections, you can undertake routine deployment tasks (schedule and deploy OS Images and OS Image Patches from WSMWeb). Figure 137 Deployment Overview page - administrator example Table 14 provides a quick overview of what you can do using the Deployment Overview page. Table 14 Routine Deployment Tasks Tasks You Can Do How Details Schedule an OS Image for Site Group assignment. Click the OS Image link you want in the Navigation Tree, select the Site Groups to which you want to assign the OS Image, click Schedule OS Patch, and follow the wizard. “Assigning an OS Image to a Site Group” on page 173. View OS Image assignment information for a Site Group. Click the Site Group link you want in the Navigation Tree to open the SiteGroup OS page. “Viewing OS Image Assignment Information for a Site Group” on page 174 Use the Content Connections page to view (and assist you in) your OS Image and Site Group assignments. Use the Content Connections page (click Content Connections in the Navigation Tree) to view (and assist you in) your OS Image and Site Group assignments. “Viewing Content Connections” on page 174 173 WSM Web Assigning an OS Image to a Site Group Summary (To Assign): To assign an OS Image to a Site Group for WSM use, click the OS Image link you want in the Navigation Tree and follow the wizard. TIP: You can also use the Site Group Name Contains and Page Size filters to find the Site Group you want; you can also use the Content Connections page to assist you in your assignments (see "Viewing Content Connections"). Detailed Guidelines (To Assign): 1. On the Deployment Overview page, click the OS Image link you want in the Navigation Tree to open the OS Assignment wizard. Figure 138 OS Assignment page 2. Select the Site Groups to which you want to assign the OS Image. 3. Click Schedule OS Patch to open the Schedule Patch page. Figure 139 Schedule Patch page 4. Click Submit. The OS Image is now scheduled for deployment and can be viewed on the Content Connections page (see "Viewing Content Connections"). 174 Chapter 12 Viewing OS Image Assignment Information for a Site Group Use the SiteGroup OS page (click the Site Group link you want in the Navigation Tree) to view OS Image assignment information for a Site Group. Figure 140 SiteGroup OS page Viewing Content Connections Use the Content Connections page (click Content Connections in the Navigation Tree) to view (and assist you in) your OS Image and Site Group assignments. Figure 141 Content Connection page A System Maintenance This appendix contains information to help you successfully maintain your WSM system. Managing Passwords Used by WSM WSM uses three sets of username and password credentials. Use the following guidelines to manage the passwords used by WSM: Caution It is strongly recommended to use an appropriate password security policy. • WSM Database – If you need to change the database user account password (default is password@123), you must change the account password on the database itself and then restart the WSM Administration Web Service (on the server go to Start | Administrative Tools | Services, right-click WSM Administration Web Service, and click Restart). The next time you login to the Administrator Console, the Database Configuration page displays allowing you to edit the database configurations (including the user account Password). After changing the database configurations you must restart all services on all servers for the changes to take effect. • Windows Service – If you change the Windows system password for the administrator user account and it affects any WSM services, then you must update any affected WSM service listed in the Windows Services Console. For example, if the WSM Administration Web Service is started by that administrator user account, then you must change the password in the Properties dialog box of the WSM Administration Web Service (on the server go to Start | Administrative Tools | Services, right-click WSM Administration Web Service, click Properties, click the LogOn tab, and then enter and confirm the new password for the account). • WSM Administrator Console – To change the administrator account password for the WSM Administrator Console, log in to the Administrator Console, click the Settings tab, click Change Admin Password, and use the Change Admin Password page (if you have remote Sites, you can also use the Change Site User Password link to change passwords for your Site Users —siteadmin, dispatcher, operator, siteoperator). • WSM Remote Service Account - To provide authentication between the Headquarters and Linked Sites for communication over https. 176 Appendix A Backing Up the WSM Database for System Recovery It is highly recommended that you back up the WSM Database for system recovery purposes. WSM stores all system, topology, user, application, and usage data in the WSM Database. By backing up the WSM Database you can recover all WSM system data. Use standard backup procedures common to database servers. For fault-tolerant systems, it is also recommended to replicate the database for fail-over. About WSM Server Services Each WSM server (Core Server or Edge Server) provides these services: • WSM Administration Web Service - Provides an administration interface (Administrator Console) for WSM. • OS Authentication Service - Prevents unauthorized devices from connecting to the WSM system. It informs each device which OS Image it is configured to receive. • OS Streaming Service - Responds to OS Image requests from client devices. • Application Authentication Service - Manages and tracks application licenses; meters application usage. • Application Streaming Service - Services end-user application client requests. • Monitor Service - Monitors and controls the WSM services on the WSM server. This service detects errors and outages, allows you to stop and start the servers, and monitors server load. • Content Distribution Service - Synchronizes the repositories of OS Images and Application Images between the Core Server and remote servers. • Multicast Boot Service - Multi-casts an OS Image to devices when the system is set up to provide the OS Image in multi-cast mode. • DHCP Proxy Service - Responds to requests from PXE devices; prevents WSM servers from responding to PXE requests from “outside” devices that are not part of the WSM system. • TFTP Service - Allows for thin client booting, data transfer, and so on. Understanding and Using the Log Files of WSM Errors pertaining to WSM and related components are logged to the System Event Viewer. Descriptions of errors regarding licensing, server connections, database problems, configuration errors, and so on, are available through the System Event Viewer. WSM stores log files in the WSM Database and on your file system. These files have a set size limit (default is 10,000,000 bytes) and will rollover when they become larger than the limit (making the system self-maintaining). The Profile Log is a log of communication statistics on the server side providing information on how long the request queue is at a given time, the effective bandwidth amount of requests received so far, and the type of requests received so far. It is located at the /server-install/log folder with the name in the format of: prof-<server-id>-<random>.txt. Format: Date [universal-time] [start-time] [delta-time] [request-count] [S/M] [CLIENT/CACHE] [IP address] [app-id] [fileID,pageID] (S=single, M=multiple) System Maintenance 177 About WSM System Monitoring WSM includes built-in monitoring tools that can be used to watch and check the health of the WSM system. After login to the Administrator Console, the System Overview page appears allowing you to quickly view important summary information for each functional area of the WSM system. The System Overview page also provides links to all of the functional areas so you can easily perform many of the administrator duties that are required to run and maintain your WSM environment. For example, the System Overview page allows you to quickly see that a server requires your attention (as WSM notes this server issue in the Requires Attention area) and provides you a link to the server page that you need to address the issue. For fault-tolerant provider systems, it is recommended to have system hardware monitoring in place. Third-party system monitoring software can be configured to watch and report on system status, including: • Ping availability and response times • % CPU Utilization • Memory Available • Bandwidth consumption The following list provides a few examples of system monitoring software: • Tivoli by IBM • Big Brother by Quest software • Nagios by Nagios • Performance Monitor by Microsoft 178 Appendix A This page intentionally blank. B Load Balancing This appendix provides information on the load balancing feature of the WSM system. It explains how load balancing works and how to set up your system for load balancing. How Load Balancing Works Load balancing permits a device to be boot from and be serviced by more than one server. In this way, Application Images and OS Images can be delivered more reliably and quickly from servers to thin clients. When the load is too heavy on one server, requests made to that server are given to a different server instead. The workload is distributed evenly—it is balanced—across all the servers in the group so that each server does roughly the same amount of work. If a server goes down, the thin client can boot from a different server and still obtain the OS Images and Application Images it needs. Load balancing offers these benefits: • Faster response time because servers share the workload. No single server is overloaded when others are idling. • Improved scalability because adding servers only requires you to place the servers in a server group. Thin clients can start using the server as soon as images are ready. • Improved fault tolerance because there is no single point of failure as there is when only one server serves all clients. Using Server Groups and Device Groups Load balancing makes use of server groups and device groups to stream OS Images to thin clients. Because each device in a device group is assigned the same server group and OS Image, each device in the group can boot from any server in the server group to which it belongs. If one server in the group is overworked, another server can take on its workload. This setup ensures that devices are always being served efficiently by servers. 180 Appendix B Figure 142 Load balancing setup TIP: In previous versions of WSM, you could configure a device to boot from up to four servers. However, administrators had to configure the devices to boot from the different servers and track where devices boot. Load balancing replaces this boot configuration process with the server group and device group concept. How WSM Selects Boot Servers in the Server Group With load balancing, WSM selects a server in a server group to provision the device when you boot it. This selection is based on the number of devices currently booted from the server and the responsiveness of the server. WSM uses this process to select which server in the server group to boot from: 1. Finds out the load (number of devices booted from a server) for each server from the server group. 2. Selects a few of the least loaded servers from all servers in the server group. 3. Sends a request to the servers. 4. Selects the server that responds first. TIP: WSM may select a different server for a device each time it boots up. However, if a network outage occurs, WSM reconnects the device to the same server it was connected to when the outage occurred. This ensures that any write cache maintained for the device is preserved as long as the device is up for a session (until the next boot). Load Balancing 181 Volatile and Persistent Cache Mode The load balancing setup works seamlessly when the OS Image is in Volatile Cache mode. In this mode, each boot deletes changes made during the previous session. However, if the OS Image is Persistent Cache mode (and is required to preserve the changes made across multiple sessions), the write cache folder must be shared across all the servers. If it is not shared across all server, the device may select a different server during the next boot, and if the new server does not have access to the same write cache file, changes made during the previous session are not available. Setup for Load Balancing Follow these general guidelines to use the load balancing feature of WSM: NOTE: These guidelines work only for User-Created Server Groups, not the Defualt Group. 1. Create a server group with all the servers that you want to configure for load balancing. Typically, this server group includes all servers on the same site or location. Load balancing requires servers to have good network connectivity with the devices they serve. For more information, see "Adding Server Groups." 2. Assign OS Images to the server group you created. For more information on using the the Change Server/Server Group Assignment link on the OS Image Details page, see "Editing Device Groups." 3. Ensure the destination servers are in ready state. 4. Create a device group and assign all the devices that you want to configure for load balancing to the device group.If devices need different OS Images, assign them to different groups. For more information, see "Adding a Device Group." 5. Assign the server group you created in Step 1 to the device group you created in Step 4. For more information, see "Editing Device Groups." 6. Assign the OS Image to the device group. For more information, see "Editing Device Groups." 182 Appendix B This page intentionally blank. C Updating OS Images and Application Images This appendix provides information and instructions on updating the OS Images and Application Images in your WSM system. Updating an OS Image While editing an OS Image, you can update the OS Image by using the Patch button and completing the required steps. Changes to an existing OS Image can be either configuration changes or operating system patches that are delivered by the vendor which are deemed to be necessary by you the administrator. TIP: Before you begin updating an OS Image, be sure you have denoted the Reference Device you want to use, as described in "Editing Devices." The Reference Device is a device of the Default Device Group which you denote as the Default device that will be used to apply updates or patches that are needed to an OS Image. By default, the first device that is added to the WSM system is denoted as the Reference Device. However, you can change the Reference Device at any time. On the Network Device Details page for a Reference Device, you can view the Reference Device notice in the Attention area at the top of the page. On the Network Device Details page for all other devices of a Default Device Group, you can use the Make this the Reference Device link to make a device the Reference Device. Having a Reference Device is optional for the normal operation of WSM. However, if you want to update an operating system, you must denote a device as the Reference Device (on the OS Image Details page) before you can use the Patch button and proceed with updating the OS Image. For example, if a Reference Device does not exist in the system, you must specify a Reference Device from the available devices in the system before updating an OS Image. It is recommended that you do not select an end-user device for use as the Reference Device. This will allow you to apply updates to an operating system without affecting end users. The Reference Device must be on the same network as that of the WSM Core Server (that is, the Reference Device must be able to boot directly from the WSM Core Server). Updating an OS Image consists of: • "Step 1: Preparing the OS Image for Updating" • "Step 2: Starting the Patch Process" • "Step 3: Applying the Patch on the Reference Device" • "Step 4 Finalizing and Scheduling the Deployment of the Patch" TIP: The updating process is designed so that it does not interfere with your current WSM environment. During the updating process your WSM environment continues to stream the currently active OS Image. Your WSM environment will stream the new updated OS Image only after the updated OS Image is ready and you schedule it for deployment. 184 Appendix C Step 1: Preparing the OS Image for Updating 1. Go to the WSM Core Server machine where the OS Image that you want to update resides (for example, Base Image). Caution Ensure that this OS Image is either in Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode), as described in "Editing OS Images." 2. Create a copy of the OS Image in the same directory (be sure to rename the OS Image so that you can recognize it later - for example, Base Image v2). Step 2: Starting the Patch Process 1. On the OS Image Details page (for the OS Image you want to update), click the Patch button to open the Select OS Image Copy page. Caution If there is no Reference Device, you will receive an error. You must denote the Reference Device you want to use as described in "Editing Devices," and then return to this page to start the patch process. Figure 143 Select OS Image Copy page 2. Use the following guidelines: • Enter the Patch Name. • Select the File Name (be sure to select the OS Image you created in "Step 1: Preparing the OS Image for Updating" (for example, Base Image 2). • Enter the Version. • After completing the entries, click Finish. The OS Image patch is automatically assigned to the Reference Device. TIP: You can be sure to identify that the OS Image patch copy was created by clicking the Name link of the OS Image on the Operating Systems main page to open the OS Image Details page, and then viewing the Status of the OS Image patch copy as Patch Copy Created in the Image Hierarchy area. Caution If the Reference Device is full or if the Reference Device is not a device of the Default Device Group, you will receive an error. Updating OS Images and Application Images 185 If the Reference Device is full (there is a limit of four OS Images that can be assigned to a Reference Device), you must remove one of the OS Images and add the OS Image patch as described in "Editing Devices," and then return to the OS Image Details page to click the Assign Patch to the Reference Device link. The OS Image patch is now assigned to the Reference Device. Continue with "Step 3: Applying the Patch on the Reference Device." If the Reference Device is not a device of the Default Device Group, you must change the Device Group assignment of the device (so that the device is of the Default Device Group) as described in "Editing Devices," and then return to the OS Image Details page to click the Assign Patch to the Reference Device link. The OS Image patch is now assigned to the Reference Device. Continue with "Step 3: Applying the Patch on the Reference Device." Step 3: Applying the Patch on the Reference Device This is a manual step. After the Reference Device (which is in the User Select Boot Selection Mode) completes the boot process and connects to the WSM Server, it provides you with an option to select the proper OS Image patch from which to boot. 1. Select the OS Image patch (for example, Base Image V2) that you have added to the system. 2. Apply the OS Image patch (be sure you have completed any changes that you want to be available for all users). 3. Shut down the Reference Device. 186 Appendix C Step 4 Finalizing and Scheduling the Deployment of the Patch TIP: This step compares the original OS Image and the patch OS Image, and then creates a delta file (a file which includes only the changes that were made to the original OS image) that will be sent to the servers (this reduces the bandwidth requirements for patch deployment in cases where you have multiple servers to which this image must be deployed). 1. On the OS Image Details page (for the OS Image you want to update), click the Finalize Patch link to create the delta between the Active OS Image that is currently Streaming your operating system (for example, Base Image) and the patched OS Image (for example, a patched Base Image 2). TIP: After clicking the Finalize Patch link, a warning appears for finalizing a patch before the patch has been deployed to all servers. The process of creating the delta file may take several minutes. You can check to see that the process has been completed by viewing the OS Image Details page for the OS Image (showing the Status of the OS Image patch copy as Patch Finalized). When the process is complete, you will have a delta file (between the currently active OS Image and the OS Image patch) ready to be scheduled for deployment. TIP: You can track the content distribution process from the OS Image Content Distribution tab by clicking on the name of the image/patch. If you click the Cancel link in the Schedule column of the Content Distribution Summary page, the content distribution will be cancelled and show a state of Cancellation Requested. After the state changes to a canceled state, you can use the Reschedule link to schedule the distribution of the OS Image. If you have missed the opportunity to cancel the content distribution, you can use the Rollback link on the OS Image Details page. Once the schedule is completed, the WSM Content Distribution Service will automatically schedule the copy of the patch (delta) file to the different Edge servers (or remote servers in the case of Linked Sites) which have been previously assigned the OS Image. Once this delta file copy is completed, the process on the servers will then merge these changes into a copy of the original OS Image in its own repository and make it available for the devices that are using these servers. TIP: To see that the patch has been deployed by the servers, you can check the Version Deployed column of the servers in the Servers Streaming area of the OS Image Details page. As the devices using the OS Image in your WSM are rebooted, they will begin using the new updated OS Image. The design of the patch process reduces end-user downtime during patch deployment. The newly patched OS Image is only applied as a pending update to the Network Device OS assignment. Users can continue to use the original OS Image until they reboot the Network Device. Once the Network Device reboots, it will begin using the newly patched OS image. Updating OS Images and Application Images 187 Updating an Application Image On the Registered Applications page (Applications > Registered), click the Name link of the Application Image you want to edit to open the Application Image Details page, and then use the Patch tab to edit the settings. TIP: If you need to prepare an Application Image update for use as a patch, refer to "Preparing an Application Image Update." Summary (To Edit): While editing an Application Image, you can update the Application Image by using the Patches tab to edit the Patch settings for the Application Image. Click the Patch button to open and use the Patching Application Image page. Figure 144 Application Image Details page - Patches tab Detailed Guidelines (To Edit): 1. Click the Patch button to open and use the Patching Application Image page. Figure 145 Patching Application Image page 2. Select the File Name you want to use for the Application Image update (patch). 3. Enter the Name. 4. (Optional) Enter the Description. 5. Enter the Version. 6. Click Finish. The Application Image is updated and can be viewed in the list of available Application Images on the Applications page. 188 Appendix C TIP: The updated Application Image is immediately deployed to all of the Edge servers to which the original image was assigned. As soon as the deployment is completed, the end user will see a message that the application has been updated and to save their work if they are actively using this application. The end user will see the original Application Image being unsubscribed and the new Application Image being subscribed. This update process has been automated to ensure that the user has the latest Application Image, once you update the Application Image. Preparing an Application Image Update TIP: In general, it is recommended that you store the application environment in which you originally create an Application Image for future use. If you are using an existing application environment, complete the following (if you do not have an existing application environment, create a new Application Image and copy the Application Set to the repository as described in Publishing): 1. Apply the patch or make updates to the existing application environment. 2. Take a snapshot of the changes. 3. Create an Application Set using the snapshot created before the application was installed and the new snapshot (see Publishing). 4. Create an Application Set. 5. Be sure to create a new GUID for the Application Set ID. 6. Copy the Application Set created to the repository. Updating OS Images and Application Images This page intentionally blank. 189 190 Appendix C D Using the Wyse UniPlat Tool This appendix describes how to install and use the Wyse UniPlat Tool. It provides information on how to create backup files with the tool and use the backup files to create “golden” OS images for use with WSM. Wyse UniPlat Tool (UPT) is part of the WSM Client Utilities package. Using the UPT, you can create a single hard-disk image (“golden” image) that can be used on multiple hardware platforms. After you create the golden image, you can convert it into an OS image and stream the image to multiple platforms using WSM. This process allows you to easily create a universal image for use with various platforms. Installing Wyse UniPlat Tool TIP: Wyse UniPlat Tool will be installed in the Program Files folder on your C: drive. The installer for the tool is available from the WSM Administrator Console > Installers link > Client Utilities link. Figure 146 About page Use the following guidelines: 1. Double-click the WSM Client Utilities.exe to open the installation wizard and click Next. 2. Click Install to start the installation. 3. Click Finish when the installation is complete. 192 Appendix D About the Wyse UniPlat Tool Use UPT to create and handle UniPlat disk files. A UniPlat disk file is an image (or copy) of a disk or directory. You use UniPlat disk files to re-create disks or directories on different systems. TIP: To run Wyse UniPlat Tool, you must have an account with administrator privileges. To launch Wyse UniPlat Tool, click Start and select All Programs | Wyse | WSM Client Utilities | Wyse Universal Platform Tool. After you launch Wyse UniPlat Tool, the UPT application window appears divided vertically into two panes: • On the left-hand pane, you can browse directories and select UniPlat disk files. • On the right-hand pane, you can see the properties of the currently selected file (if a file is selected). To perform actions on a UniPlat disk file, click an icon on the toolbar or select an option on the File menu. Figure 147 Wyse UniPlat Tool Interface Creating a Backup Windows Partition Use the following guidelines to use UPT to back up a Windows partition on a client machine: 1. Install and run UPT on the machine on which you will back up the Windows partition. 2. In UPT, create a UniPlat disk file on a mapped drive on the network or an external hard disk (see "Creating a UniPlat Disk File"). 3. In UPT, back up the Windows partition on the client machine (typically the C: drive) to the newly created UniPlat disk file. You can use this file to restore the partition. Restoring a Windows Partition In order to restore a Windows partition, the machine to which the partition will be restored needs at least two pre-formatted partitions: • The partition from which Windows currently boots up (named the boot partition). Using the Wyse UniPlat Tool • 193 The partition to which UPT will restore the backed-up Windows partition (named the destination partition). TIP: Alternatively, one can boot the machine with an OS image using WSM technology, and restore the backed-up Windows partition to a physical hard disk attached to the machine. In this case, only one partition is needed in the local hard disk. Use the following guidelines to restore a Windows partition to a hard drive: 1. On the machine to which the Windows partition is to be restored, install and launch Wyse UniPlat Tool. 2. Using UPT, restore the UniPlat disk file from a mapped network drive or external hard disk to the destination partition. After the restore, the destination partition is made the active partition, and the machine boots up from the destination partition on this and subsequent reboots (in order for this to happen, you must have selected the This Image Is Bootable option in the Properties dialog box; see "Setting UniPlat Disk File Properties"). Wyse UniPlat Tool can also be used to back up or restore only a selected subfolder within the Windows partition. Creating a UniPlat Disk File A UniPlat disk file contains backup files. Initially when you create the file, it is empty. After you create it, the next step is to insert backup files into the UniPlat disk file with the Wyse UniPlat Tool backup feature. Creating the Initial File Use the following guidelines to create the initial UniPlat disk file: 1. On the client machine with the files you want to copy, start Wyse UniPlat Tool. 2. In the left-hand pane, select the directory where you want the UniPlat disk file to reside. TIP: Store UniPlat disk files on a mapped drive or external hard disk; the UniPlat disk file should not reside on the hard disk being copied. You can click the Map Drive icon in the toolbar to create a new mapped drive to another computer. 3. Click Create on the toolbar. UPT creates a new UniPlat disk file named New File.wup. 4. Select the file, click Rename, and enter a new name for the UniPlat disk file. Setting UniPlat Disk File Properties The properties of a UniPlat disk file help you identify the file, and more importantly, allow you to prepare the file for use with WSM. To establish the properties of a UniPlat disk file, select it and click Properties on the toolbar. You see the Properties dialog box. Select a tab — Information, Description, or Options — and adjust the values. 194 Appendix D Information Properties Tab Use the Information tab of the Properties dialog box to describe the UniPlat disk file. For example, you can enter an author and company name. UPT does not interpret these fields; they are for use by administrators. Description Properties Tab Use the Description tab of the Properties dialog box to write a description of the UniPlat disk file. UPT does not interpret these fields; they are for use by administrators. Options Properties Tab Use the Options tab of the Properties dialog box to set the capture and restore options. Capture options are found at the top of the dialog box; restore options are on the bottom. Figure 148 Properties dialog box - Options tab Capture Options: Capture options are used for backups. The Capture option on the Options tab is: • Prepare Image for Wyse OS Streaming: Check this box if you intend to use this image to generate an OS image to deploy with WSM technology. UPT will launch SelectNIC.exe to select the network adapter that will connect to the WSM Server before backing up the Windows session. (This option has no effect if you are not backing up a bootable image.) Restore Options: Restore options are used for restorations. The Restore options on the Options tab are: • Delete All Files Before Restoring: Clears the destination directory of all files and subfolders prior to the restoration of a UniPlat disk file. • This Image Is Bootable: Makes the destination partition bootable after the restoration. Check this field if you are restoring an entire bootable partition. Checking it ensures that the destination partition is made active. The boot.ini and drive letter assignment for the destination partition will be fixed accordingly so that Windows can boot from this partition after the restoration. · Keep Critical Drivers from Current Windows Session: Check this box if you are installing a UniPlat disk file that was captured from a different platform. Due to hardware differences between the restored image and the current platform, the current platform may become unbootable after the restoration because it may lack the appropriate disk controller driver necessary for booting up. This option causes all drivers and binaries critical for booting up the current platform to be copied from the current Windows session to the destination partition. It also copies over driver installation files (such as .inf files and driver binaries) from the current Windows Using the Wyse UniPlat Tool 195 session to the destination partition. These files may come in handy when re-installing drivers for the current platform after the image is restored and booted up. Note that the current Windows session should be the same Windows version as the restored image; otherwise, the driver files copied from the current Windows session may not be usable on the restored image. TIP: You do not need to enable this option if you are restoring a UniPlat disk file that was captured from the same platform because all the drivers should already be in place in the UniPlat disk file. · Perform Post Restore Fix Up Only: This option is mainly for debugging purposes. Enabling it causes all post-restoration fix-up operations that make the destination partition bootable to be performed without restoring files from the UniPlat disk file first. This option can be used if you have gone through the restoration operation once but Windows failed to boot up from the destination partition. In this case, one or more post-restoration operations may not have completed successfully. Select this option to attempt the post-restoration fix-ups again without going through the whole restore process. Inserting Files into a UniPlat Disk File After creating a UniPlat disk file, the next task is to insert one or more files (up to and including a backup of an entire partition) into the UniPlat disk file. Use the following guidelines to insert files into a UniPlat disk file: 1. Start Wyse UniPlat Tool. Warning Close all open applications except Wyse UniPlat Tool before inserting files in the UniPlat disk file. Otherwise, you may capture locked or intermediate files. 2. Select a UniPlat disk file on the left side of the window. 3. Examine the Capture options of the file. Make sure the correct options are selected. 4. Click Backup on the toolbar to open the Backup dialog box. Figure 149 Backup dialog box 5. Enter the directory you want to back up or use Browse to find and select the directory you want. Select the root drive of the current Windows session if you want to capture a bootable Windows image. TIP: You cannot back up from a Windows session that is currently streamed from WSM. You can, however, restore a UniPlat disk file to the hard disk while you are booting up from a streaming Windows session. 6. Click Go. All files and subdirectories in the directory you selected are added to the UniPlat disk file. 196 Appendix D Restoring a UniPlat Disk File to a Partition Use the following guidelines to restore a UniPlat disk file to a partition: 1. In Wyse UniPlat Tool, select the UniPlat disk file with the backup files. 2. Examine the Restore options of the UniPlat disk file to make sure you selected the correct options (see "Setting UniPlat Disk File Properties"). 3. Click Restore on the toolbar to open the Restore dialog box. Figure 150 Restore dialog box 4. Enter the directory where the files will be restored. If you are dealing with a bootable image that captured the entire partition of a Windows session, you normally restore it to the root of the destination partition. 5. Click Go to restore the files. Creating a Single OS Image that Supports Multiple Hardware Platforms This section explains how to create a single UniPlat disk file that supports multiple Windows-based hardware platforms. It describes the requirements and how to create a combined OS UniPlat disk file that supports multiple platforms. Requirements for a UniPlat Disk File and Supported Platforms In order to support multiple hardware platforms with the UniPlat disk file, the platforms must meet these requirements: • The HAL (Hardware Abstraction Layer) of the UniPlat disk file must be compatible with all platforms being supported, and for this to occur, the Windows OS installed on each platform must use the lowest common HAL across all platforms (see "Checking and Changing the HAL of a Computer" for details on how to select the lowest common HAL). • The Windows OS on all supported platforms must be the same version and service pack level. Windows XP Home or Professional with Service Pack 2 or above is recommended. • In order to use Wyse UniPlat Tool to prepare a single UniPlat disk file for multiple hardware platforms, each platform needs at least two partitions formatted to the appropriate file system (NTFS is recommended). The partitions must be large enough to accommodate Windows installations for all platforms being supported. (If you are able to boot up a platform from an OS image using Wyse Streaming technology, only one local hard disk partition is required.) Using the Wyse UniPlat Tool 197 Creating a Combined UniPlat Disk File This section explains how to create a combined UniPlat disk file to support multiple hardware platforms if an OS image does not already exist for any of the target platforms. Creating the combined image involves backing up the Windows installation to a UniPlat disk file, restoring it to a partition on another platform, and then rebooting from a second partition on the other platform. Figure 151 shows an overview of the steps required to create a combined UniPlat disk file (PF1 represents Platform 1, Part 1 represents Partition 1, and so on). Figure 151 Overview of steps to create a combined UniPlat disk file To create a single OS image that supports multiple hardware platforms: Step 1: Create and back up the UniPlat disk file 1. Install Windows OS, required drivers, and Wyse UniPlat Tool on one of the partitions on the platform. In the illustration, install on Platform 1 (PF1), Partition 1 (Part1). 2. Launch UPT from Platform 1 to back up the Windows root drive (e.g., C:\) of this platform to a UniPlat disk file (IMG1.wup in the illustration) on a shared network folder or external hard disk (see "Creating a UniPlat Disk File" for details). TIP: If you intend to create an OS image for streaming from the final combined image, select the Prepare Image for Wyse OS Streaming option on the Options tab of the Properties dialog box before starting the back up process (see "Setting UniPlat Disk File Properties" for details). 198 Appendix D Step 2: Restore the UniPlat disk file to a partition on the next platform 1. Install Windows OS, required drivers, and Wyse UniPlat Tool on one of the partitions on the next platform. In the illustration, install on Platform 2 (PF2), Partition 1 (Part1). Make sure both platforms have the same HAL, Windows OS version, and service packs. 2. Launch UPT from Platform 2 (PF2) to restore the UniPlat disk file (IMG1.wup in the illustration) to the root drive of Partition 2 (e.g. D:\) (this partition must be pre-formatted). Make sure the following options are chosen on the Options tab of the Properties dialog box: · Select Delete All Files Before Restoring. This option ensures that all files from destination partition (Part2 of Platform 2) are deleted before the restoration. · Select This Image Is Bootable. This option ensures that the destination partition (Part2 of Platform 2) is bootable after the restoration. · Select Keep Critical Drivers from Current Windows Session. This option ensures that critical drivers and registries (e.g., disk controller driver) required for platform 2 to boot up are copied over from the Windows session of platform 2 (Part1 of Platform 2) to the destination partition, and that driver installation files (e.g., network/display/audio/… drivers) for platform 2 are copied over from the Windows session of platform 2 to the destination partition. · Do Not select Perform Post Restore Fix Up Only. 3. After the restoration, make sure that no error message is displayed in the UPT dialog box. Step 3: Reboot the platform 1. Reboot the platform (PF2 in the illustration). This platform boots to the newly installed partition (Part 2 in the illustration). When Windows discovers new hardware on the platform, it starts the Found New Hardware Wizard and prompts you to install drivers. 2. Direct the Found New Hardware Wizard to the C:\Windows\inf folder to find the appropriate driver installation files (see "Reinstalling Drivers for the Current Platform" for details). After all drivers for platform 2 are re-installed, the resulting image can run on platform1 and 2. Repeat steps these for more platforms if needed. You can reuse the UniPlat disk file to back up the new combined image. Optionally, use UPT to restore the final image to each supported platform to verify the functionality. Using the Wyse UniPlat Tool 199 Reinstalling Drivers for the Current Platform After you restore a UniPlat disk file that was not captured from the current platform, you have to reinstall drivers for the platform. You have to do this because the newly restored partition does not have the drivers to support the current platform. If you selected the Keep Critical Drivers from Current Windows Session option when you created the UniPlat disk file (see "Setting UniPlat Disk File Properties"), drivers for the current platform are already in the newly restored partition. You just need to point the Windows Found New Hardware Wizard to the correct location of these drivers for installation. Use the following guidelines to point Windows to drivers for the current platform: 1. When the Found New Hardware Wizard appears, select the Yes, This Time Only option and click Next. 2. Select the Install from a List or Specific Location (Advanced) option and click Next. 3. Select the Include this Location in the Search check box. Figure 152 Found New Hardware Wizard 4. Enter the path to C:\WINDOWS\inf in the text box, and click Next. After Windows finds the appropriate .inf file for the target hardware, it looks for the driver binaries. These binaries are typically located either in the C:\WINDOWS\system32 or C:\WINDOWS\system32\drivers folder. Some hardware components need to install .hlp files. These files are typically located in the C:\WINDOWS\help folder. You can use Browse to find the needed file. If the needed file does not exist in the destination partition, look for it in the other partition from which Windows used to boot up, if this partition is still accessible. 200 Appendix D Creating a “Golden” OS Image from Current OS Images This section explains how to prepare a single OS image for multiple hardware platforms when individual OS images are currently available for some of the target platforms. For the purposes of this discussion: • There are three different hardware platforms named PF1, PF2, and PF3. • Each platform has a corresponding OS image named OS1, OS2, or OS3 from which the platform can be booted up using WSM technology. • The goal is to prepare a single OS image (named OS123) from which all three platforms (PF1, PF2, and PF3) can be booted up using WSM technology. This image is referred to as the “golden” OS image. Figure 153 Using a golden OS image to boot all platforms Hardware and Partition Requirements The minimum hardware requirements for creating a golden OS image are as follows: • Each platform device must have a local hard disk with one primary Master Boot Record (MBR)-type partition formatted to NTFS. • The partitions must be large enough to accommodate the desired Windows installation of all platforms (PF1, PF2, and PF3 in our example). • The requirements on existing OS images for platform 2 and 3 (i.e., OS2 and OS3 in our example, but not OS1; because hard disk Windows installation is required for platform 1, OS1 is not used) are as follows: · In order to share the same Windows OS image across multiple hardware platforms, the HAL (Hardware Abstraction Layer) of the golden image must be compatible with all platforms. This means the OS Image for PF2 and PF3 must already be using the lowest common HAL across all three platforms (see "Checking and Changing the HAL of a Computer" for details on how to confirm that the lowest common HAL is used). If the OS images are using different HALs, they cannot be used to create a golden image. · The Windows OS on all supported platforms must be the same version and service pack level (Windows XP Home or Professional with Service Pack 2 or above is recommended). If the platforms are of different service pack levels, you can bring the OS images up to sync by installing the appropriate service pack. Using the Wyse UniPlat Tool 201 Creating the Golden Image Use the following guidelines to create a golden OS Image that supports multiple Windows-based hardware platforms: 1. Install Windows OS, required drivers, and Wyse UniPlat Tool on a hard disk partition of PF1. Make sure this Windows installation is the same version and service pack level as OS2 and OS3. Make sure as well that the lowest common HAL across all three platforms are used in this Windows installation. 2. Boot up PF1 from the hard disk, and launch UPT to back up the Windows root drive (e.g., C:\) of PF1 to a UniPlat disk file (e.g., IMG123.wup) on a shared network folder or an external hard disk. Before you start the back up process, select the Prepare Image for Wyse OS Streaming option on the Options tab of the Properties dialog box. 3. Boot up PF2 from OS2 using WSM technology. If it is not installed already, install Wyse UniPlat Tool on OS2. Launch UPT from OS2 to restore IMG123.wup to the root drive of the PF2 local hard disk. Make sure the following Restore options on the Options tab of the Properties dialog box are selected before you start the restore process: · Select Delete All Files Before Restoring. This option ensures that all files from the destination partition are deleted before the restoration. In this case, all files from the PF2 local hard disk partition are deleted before the restoration. · Select This Image Is Bootable. This option ensures that the PF2 hard disk partition is bootable. · Select Keep Critical Drivers from Current Windows Session. This option ensures that critical drivers and registries (e.g., disk controller driver) required for PF2 boot up are copied over from OS2 to the PF2 local hard disk partition, and that driver installation files (e.g., network/display/audio/… drivers) for PF2 are copied over from OS2 to the PF2 local hard disk partition · Do Not select Perform Post Restore Fix Up Only. 4. After the restoration, make sure that no error message is displayed in the UPT dialog box. 5. Reboot PF2 to the local hard disk. PF2 boots to the newly restored local hard disk partition. When Windows discovers new hardware on PF2, it starts the Found New Hardware Wizard and prompts the user to install drivers. 6. Direct the Wizard to the C:\Windows\inf folder to find the appropriate driver installation files (see "Reinstalling Drivers for the Current Platform" for details). 7. After all drivers for PF2 are re-installed, reboot PF2 to the local hard disk if prompted by Windows. This PF2 hard disk Windows installation can now run on both PF1 and PF2. 8. Repeat Steps 2 through 7, but this time boot up PF3 and complete the process with this platform so that the PF3 installation can now run on PF1, PF2, and PF3. Optionally, with PF3 booted up from a local hard disk, you can launch UPT to back up the Windows root drive (e.g., C:\) of PF3 to a UniPlat disk file (e.g., IMG123.wup) on a shared network folder or an external hard disk. Check the Prepare Image for Wyse OS Streaming option on the Options tab of the Properties dialog box before you start the back up process (see "Setting UniPlat Disk File Properties" for details). The resulting IMG123.wup file is good for PF1, PF2 and PF3. This UniPlat disk file can be useful for disaster recovery or to generate a golden image for additional hardware platforms. 202 Appendix D Optionally, boot up each platform from the corresponding OS image using WSM technology, and use UPT to restore IMG123.wup to the hard-disk partition of PF1, PF2 and PF3. Verify that each restoration of IMG123.wup is bootable and functional for all three platforms. With PF3 booted from the local hard disk, install WSM Client on PF3. Use the WSM virtual disk capturing tool to capture an OS image (VD123) from the PF3 hard disk. The resulting OS image is capable of booting up all three platforms using WSM technology. TIP: When installing WSM Client on PF3, you may see an error message telling you that “the file osmsmdf.sys on (unknown) is needed.” To locate the requested file, use Browse to locate and enter the following in the Copy files From field: c:\windows\system32\drivers. Checking and Changing the HAL of a Computer To share the same golden OS image across multiple hardware platforms, the HAL (Hardware Abstraction Layer) of the image must be compatible with all platforms. HAL is the OS programming interface that serves as an interface between a system's hardware and software. Windows XP offers six HALs. From most to least compatible, they include: • Standard PC • MPS Uniprocessor PC • MPS Multiprocessor PC • Advanced Configuration and Power Interface (ACPI) PC • ACPI Uniprocessor PC • ACPI Multiprocessor PC Warning Standard PC, the most compatible HAL, lacks some important features such as automatic computer turn off upon shutdown. This section explains how to check which HAL a PC uses and change the HAL if necessary. Checking the HAL on a Computer Use the following guidelines to check the HAL on each computer for which you want to create a golden OS image: 1. Start the PC. 2. Click Start and select Control Panel. 3. In the Control Panel, select the System icon to open the System Properties dialog box. (If you do not see the System icon, click the Switch to Classic View link.) 4. Select the Hardware tab. 5. Click Device Manager to open the Device Manager window. Using the Wyse UniPlat Tool 203 6. Open the Computer folder to view the HAL. Note the HAL on each PC and which is the lowest common HAL. Figure 154 Device Manager window Changing the HAL on a Computer Caution You cannot change the HAL on an OS image directly because doing so yields an unbootable OS image. To change the HAL on an OS image, start by changing the HAL on a Windows session booted from your local hard disk. Then, after all drivers for the new HAL are installed, install the WSM Client and use the WSM virtual disk capturing tool to capture the OS Image. Use the following guidelines if you need to change the HAL on a PC: 1. Open the Control Panel and select the System icon to open the System Properties dialog box. 2. Select the Hardware tab and click Device to open the Device Manager window. 3. Open the Computer folder to view the HAL. 4. Right-click the HAL and select Properties to open the Properties dialog box. 5. Select the Drivers tab and click Update Driver. 6. Select the Yes, This Time Only option and click Next 7. Select the Install from the List or Specific Location (Advanced) option and click Next. 8. Select the Don’t Search, I Will Choose the Driver to Install option and click Next. 9. Make sure the Show Compatible Hardware check box is selected 10.Select the desired HAL and click Next. Windows will install the new HAL and reboot the computer. After the reboot, you may be prompted to install newly found hardware drivers. 204 Appendix D Limitations and Known Issues These issues apply to bootable UniPlat disk files only. If you are not backing up and restoring the entire Windows partition, these issues do not apply. • Restoring a bootable UniPlat disk file on a live partition (the partition from which Windows is currently running) is not supported. • The destination partition on which the UniPlat disk file restores must be a primary MBR-type partition. UPT does not support GPT-type partitions or dynamic-disk or non-simple volumes (i.e., a spanned/Mirrored/Striped/RAID-5 volume). • Wyse UniPlat Tool does not provide a unique computer name or IP address for the restored Windows session. All configurations, including computer name and IP configurations from captured Windows sessions, are carried over. Enabling DHCP in your source Windows session is recommended. • When the Keep Critical Drivers from Current Windows Session option is enabled, UPT attempts to copy driver binaries and registries from the current Windows session to destination partition. If the current Windows session is of a different version or service pack level than the target restored image, the copied drivers and registries may not be compatible. • If the first client device has PS2 kbd/mouse and the second has USB kbd/mouse, after restoring the first client image to the second client device, the kbd/mouse of the second client device may not function because it is missing the necessary USB controller driver even if the Keep Critical Drivers from Current Windows Session option is elected before restoring. This is because when the second device boots up with many uninstalled drivers, the hardware manager enumerates new hardware. It may find other cards (e.g., display, audio, or network) before the USB Controller. At that time, the OS will prompt the user to install the new hardware automatically. The user is supposed to click OK to let Windows install the driver automatically, but because the USB controller is not installed yet, the USB kbd/mouse does not function, and the user cannot get the Hardware Installation Wizard to move on. The workaround is to make sure that the PS2 kbd/mouse is available on the second device. After getting past this point, the USB controller is enumerated and installed on the second device, and the USB kbd/mouse will work. E Multicast Streaming This chapter describes how to use Multicast Streaming. Overview Multicast is a mechanism used in UDP communication to efficiently deliver a set of packets to multiple clients. It is a one-to-many communication. Instead of sending the same packets repeatedly for each recipient, the source sends the packets only once for all recipients who are listening at that time. An IP Multicast group address is used by sources and the receivers to send and receive content. Sources use the group address as the IP destination address in their data packets. Receivers use this group address to inform the network that they are interested in receiving packets sent to that group. Wyse Streaming Manager can use multicast protocol to deliver a portion of a common virtual disk image to multiple client devices which share the same virtual disk. This feature reduces network traffic significantly when multiple clients sharing the same image boot up simultaneously. This paper discusses best practices when using WSM’s multicast feature. How Multicast Streaming Works When a virtual disk is set to Volatile Cache mode, its contents remain the same on each boot up. Every time the Windows session in such a virtual disk starts, Windows requests the same set of disk sectors in the exact same sequence until a certain point. This sequence is user independent, and hence can be applied to all client devices booted from the same virtual disk. Multicast streaming makes use of this characteristic and streams such a disk sector sequence via multicast protocol to a number of client devices which boot up at the same time. Before a virtual disk can be multicast, the WSM streaming server must learn the start up sequence by booting up one client device on this virtual disk and recording the disk sector sequence the client device requests. This process is called the “learn” mode. The outcome of learn mode is an .abs file associated with such a virtual disk. Once the .abs file for a virtual disk is available, the WSM streaming server is ready to multicast this virtual disk. The next time any client devices boot up and request streaming from such a virtual disk, the streaming server will establish a multicast session in “normal” mode. The following handshake process takes place between the streaming server and clients: 1. Once the client boots up to an appropriate point where its drivers are ready to support multicast, the client sends an Internet Group Management Protocol (IGMP) report packet to join the WSM multicast group. This causes the routers and switches to forward WSM multicast traffic to the client’s port. The WSM client also sends a READY message to the WSM server at a 1 second interval. 2. The server starts a new invitation period if one is not already active. The server multicasts the INVITE message containing a list of the clients accepted to the multicast session. 206 Appendix E 3. After receiving the INVITE message, the client determines if it is in the list of accepted clients by examining the client list contained within the invitation. If the client is not in the list and wishes to join the session, the client responds to the server with an RSVP message. 4. If the multicast session has not reached its maximum clients capacity (currently set to 200), the server will add the client’s MAC ID to the list when the next INVITE message is sent 5. Once the client recognizes its MAC ID in the next invitation message, the client enters a wait state and waits for packets from the server (If the client does not receive an INVITE message containing its MAC ID within 90 seconds, the client abandons the multicasting option and continues to boot normally). 6. The server sends INVITE messages repeatedly with the complete list of clients until one of the following: a. The number of clients accepted into the session reaches the maximum allowable. b. The invitation period expires. This is configurable via Multicast Invite Type and Multicast Invite Period value as described in "WSM Multicast Best Practices." c. This is the first time this virtual disk has booted in multicast mode (that is, the server has to enter “learn” mode) 7. Once the invitation period is completed, the server will transmit all of the sectors recorded into the .abs file to the clients prior to the OS requesting them. This allows the clients to read the requested sectors from a cache rather than sending a read request for each of these sectors. 8. The clients will begin to receive numerous packets of data marked with the appropriate sequence number. 9. Periodically, the server pauses transmission of the data and checks if all accepted clients have received all packets sent so far. If the server does not receive an ACK from all clients, the server continues to send the check message until all clients ACK or are purged by inactivity. 10.Once all packets recorded in the .abs file are sent, the server ends the multicast session by sending an END message. 11. Upon receiving the END message from the server, the client will resume its boot process. During this time, the client will satisfy read requests from the OS by first searching the cached disk sectors before issuing a normal unicast read request to the WSM streaming server. Multicast Streaming Figure 155 WSM Multicast Streaming - Normal Mode Handshakes 207 208 Appendix E Configuring Multicast Streaming Multicast is a per-virtual-disk image setting. It is available only for a virtual disk image that is in Volatile Cache (Shared Mode). For a virtual disk that contains more than one partition, all partitions must be in Volatile Cache (Shared Mode). Use the WSM Administrator Console to configure multicast settings for an individual virtual disk. Use the following guidelines: Figure 156 Administrator Console • Enable Multicast - Select to enable multicast for this image. • Multicast IP Address - The streaming server uses this multicast group IP Address to deliver this virtual disk image. This address must be selected carefully (see "WSM Multicast Best Practices"). • Multicast Time To Live - This refers to the normal TTL field in the IP header. It sets an upper limit on the number of routers through which a datagram can pass. A value of 0 (default) is translated to 1 at run time. This means the multicast source (WSM streaming server) must be within one hop (router) away from the recipients (WSM clients). Select a value that fits your network topology. Setting this number to an unnecessary large value creates excessive multicast traffic on the network. • Multicast Invite Type - Fixed indicates that the WSM streaming server will wait for the Multicast Invite Period after the first client joins before it starts multicasting. Variable indicates that the WSM streaming server will wait for one more Multicast Invite Period, if another client joins between the last client and the Multicast Invite Period. • Multicast Invite Period –This is the time the WSM streaming server will wait and invite clients to join the multicast session before it starts multicasting. If set to 0 (default), the invite duration will be read from registry settings HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OSMAbs\Parameter s\InviteDuration (currently set to 10000 milliseconds). Otherwise the value configured for the individual virtual disk image will be used. Multicast Streaming 209 WSM Multicast Best Practices In Internet Protocol version 4 (IPv4), the Class D addresses, 224.0.0.0 to 239.255.255.255, are used for multicasting. It is recommended that you use the multicast IP address range 239.0.0.0 to 239.255.255.255 for WSM multicast streaming. The Internet Assigned Numbers Authority (IANA) has reserved this address range as Administratively Scoped addresses for use in private multicast domains. Network administrators are free to use multicast IP addresses in this range inside of their domain without fear of conflicting with others elsewhere in the Internet, so long as such multicast traffic will not be passed to the Internet cloud. In fact, it has become a common practice to block multicast traffic in these ranges from entering or leaving an Autonomous Domain. The Administratively Scoped addresses can be reused in different regions of the network. Network administrators should configure their multicast routers to insure that multicast traffic in the Administratively Scoped address range does not cross into or out of their multicast domain. It is also recommend that you assign a distinct multicast IP address for different virtual disk images to avoid possible multicast address collisions. For example: Vdisk1 - 239.1.0.0 Vdisk2 - 239.2.0.0 Vdisk3 - 239.3.0.0 This practice ensures that all WSM multicast sessions can be run in parallel without interfering with each other, regardless of how your WSM environment is set up (see "WSM Multicast Q&A" for scenarios where problems can occur if distinct multicast addresses are not used). For virtual disk version 3.0 or later, if the 3rd and/or 4th multicast IP address octet is configured as 255, the WSM multicast server and client will automatically replace it with corresponding octet(s) of the WSM streaming server IP from which the virtual disk image is streamed. For example: • If VDisk’s multicast IP is configured as 239.1.255.255: · When this image is streamed from WSM streaming server 192.168.1.99, the multicast address will be 239.1.1.99. · • • When this image is streamed from WSM streaming server 192.168.2.98, the multicast address will be 239.1.2.98. If VDisk’s multicast IP is configured as 239.1.0.255: · When this image is streamed from WSM streaming server 192.168.1.99, the multicast address will be 239.1.0.99. · When this image is streamed from WSM streaming server 192.168.2.98, the multicast address will be 239.1.0.98. If VDisk’s multicast IP is configured as 239.1.255.0: · When this image is streamed from WSM streaming server 192.168.1.99, the multicast address will be 239.1.1.0. · When this image is streamed from WSM streaming server 192.168.2.98, the multicast address will be 239.1.2.0. This process allows a single image to be multicast from different servers over different multicast sessions. 210 Appendix E WSM Multicast Q&A Q: Is the Wyse WSM multicast protocol compatible with Protocol Independent Multicast (PIM) and or Distributed Virtual Reality Multicast Protocol (DVRMP)? A: From a network point of view, the multicast communications happens in 2 steps: 1. Registration: receivers (for example, WSM clients) which listen to a specific multicast group, register to the router via IGMP protocol. 2. Delivery: Router delivers multicast packets from the sender (WSM streaming server) to receivers (WSM clients) according to Multicast Routing Protocol (DVRMP, MOSPF, or PIM). DVRMP and PIM are protocols used among routers to ensure multicast packets are forwarded to appropriate network port(s) without flooding the network. It is transparent to the multicast hosts. Thus, WSM servers or clients do not care whether DVRMP or PIM is used. All WSM clients and servers do is register to a router via IGMP. The communication between WSM clients and the server is done via WSM’s private protocols over User Datagram Protocol (UDP), and is transparent to the routers. Q: Does WSM multicast use well known multicast IP address (for example, 224.x.x.x) in addition to a user-entered multicast IP address (for example, 239.x.x.x)? A: No. The WSM server uses a user-entered multicast IP address only. Q: How many multicast IP addresses can be used? A: There is no limitation on the number of multicast IP addresses Wyse supports, as long as they are within the range of 224.0.0.0 – 239.255.255.255. Q: What User Datagram Protocol (UDP) port numbers are used? A: The WSM server sends packets via port number 10704 and listens to port number 10703. A WSM client sends via port number 10703 and listens to port number 10704. Q: How does a multicast IP address translate into MAC address? A: Internet Assigned Numbers Authority (IANA) has reserved the MAC address range of 01-00-5e-00-00-00 to 01-00-5e-7f-ff-ff for multicast. To map an IP multicast address to a MAC-layer multicast address, the low order 23 bits of the IP multicast address are mapped directly to the low order 23 bits in the MAC-layer multicast address. Because the first 4 bits of an IP multicast address are fixed according to the Class D convention, there are 5 bits in the IP multicast address that do not map to the MAC-layer multicast address. Therefore, it is possible for a host to receive MAC-layer multicast packets for groups to which it does not belong. However, these packets are dropped by IP once the destination IP address is determined. Figure 157 Multicast IP address translated into MAC address Multicast Streaming 211 For example, the multicast IP address 239.1.0.99 becomes 01-00-5e-01-00-63 Q: How many multicast streams are supported in one server? A: The WSM server handles one multicast session at one time. Once a multicast session has started for clients requesting the same image, other clients requesting different multicast image will be served after the first multicast session is completed (provided that the clients have not timed-out on waiting for their multicast session to establish). However, multiple multicast sessions from multiple WSM streaming servers can be run in parallel. Q: If a virtual disk image is replicated to two WSM servers, and two devices are assigned to stream from each server exclusively, will the two devices boot up from different multicast streams even if their virtual disk images share the same multicast IP? A: Yes. The two devices will boot up from their assigned server via multicast. Each server will initiate a multicast session to feed their clients. For VDisk version 2.0 or earlier: since both sessions bear the same multicast group IP, duplicate data will be sent from the two sessions and are received by all recipients who joined the multicast group. This creates some inefficiency, but will not affect client device booting. 212 Appendix E Figure 158 Same images v2 or earlier multicast from different servers Multicast Streaming 213 For Vdisk version 3.0 or later, if the 3rd and or 4th octet of the multicast IP is configured as 255, the multicast IP will be replaced by corresponding octet of the streaming server IP. Hence, different multicast cast addresses will be used when streaming from different servers and no inefficiency will be introduced. Figure 159 Same images v3 or later multicast from different servers 214 Appendix E Q: What happens if I assign the same multicast address to multiple images? A: In a network where multiple WSM streaming servers are present, and each server is trying to multicast a different virtual disk image to different clients at the same time, the clients may receive disk data from different multicast sessions. Since these data comes from different images, they are not compatible. This causes client malfunction or Blue Screen of Death (BSOD). Figure 160 Different images bearing same multicast address Multicast Streaming 215 Q: What happens if multiple clients that use the same virtual disk image request multicasting from different WSM servers at the same time? A: Since the different copies of virtual disk image that reside at different servers bear the same multicast IP address and they are to be multi-casted on the same network at the same time, multicast address collision happens as in the above case. However, although the clients may receive disk data from different multicast sessions, since they are from the same virtual disk image, the data are compatible and clients will boot up successfully. Figure 161 Same images multicast from different servers 216 Appendix E Q: Do I need special configurations on my network to enable multicast? A: Yes. All routers/switches/firewalls along the path between the WSM streaming server(s) and client(s) must be configured to allow WSM multicast traffic to be forwarded (consult your routers/switches/firewalls documentation). If your routers/switches/firewalls are not configured properly, WSM multicast packets will not be forwarded to appropriate WSM client devices, causing multicast failure. Q: Why do I see a good number of unicast packets when booting a client from a multicast image? A: Only a portion of the virtual disk image is multicast to a client. During a client boot up process, the client uses unicast to read disk data from the server before its multicast driver is up and running. The client also switches back to unicast when Windows starts the login process. Q: How do I know if a WSM server has gone through multicast learn mode for a specific virtual disk image successfully? A: After the learn mode has been completed successfully for a virtual disk image, an .abs file bearing the same name as the virtual disk image will be generated at the WSM streaming server <WSM streaming directory>\OSImages folder. Alternatively, you can examine the OSMAbsServer.log file under the <WSM install directory>\log folder at the WSM streaming server where such a client was boot up from. Q: How do I know if a client is actually using multicast to boot up? A: On WSM releases earlier than version 3.0, there is no indicator to confirm this and you must examine the OSMAbsServer.log file under the <WSM install directory>\log folder on the WSM streaming server where such a client was boot up from. On WSM release 3.0 or later, the OSMTray.exe (resides at system tray) displays the following multicast related boot statistics: • Multicast Bytes count - Indicates the number of bytes retrieved via the multicast session during boot time. The closer this number is to the Boot “Bytes” value, the more effective multicast is on this image. If this number is 0, multicast was not used. • Multicast Pkts lost during boot - indicates the number of multicast packets lost during boot time. The lower this number is, the more reliable the multicast session. Figure 162 Multicast related boot statistics Multicast Streaming Figure 163 217 WSM Virtual Disk Status Q: If the WSM Core Server has gone through learn mode for a specific virtual disk image and the image is replicated to the edge server afterward, does the edge server need to go through learn mode for this image again? A: Yes, the .abs file is not populated to the edge server with the virtual disk image. Thus, the edge server receiving the multicast virtual disk will need to generate the .abs file through a learn mode again. Alternatively, you can copy the corresponding .abs file from the Core Server to the edge server manually to skip the learn process. 218 Appendix E Using the Multicast Streaming Service Log File The WSM Multicast Service generates detail messages to the OSMAbsServer.log file located at the <WSM install directory>\log folder on the WSM streaming server. This file provides information on the process and result of all multicast sessions initiated from this server. To examine the multicast service log, do one of following: • In the WSM Administrator Console, click Servers to open the Servers page, click the Name link of the target server from the list of servers to open the Server Details page, click the View Log link of the Multicast Boot Service. • Open the <WSM install directory>\log\OSMAbsServer.log file directly using any text file editor. Optionally, follow these steps to obtain a clean (easier to read) OSMAbsServer.log file showing only messages for the current multicast session: 1. In the WSM Administrator Console, click Servers to open the Servers page, click the Name link of the target server from the list of servers to open the Server Details page, click on the Stop link of the Multicast Boot Service. 2. Delete (or rename) the existing <WSM install directory>\log\OSMAbsServer.log file. 3. Start Multicast Boot Service from the WSM Administrator Console, (on the Server Details page of the server, click on the Start link of the Multicast Boot Service). 4. Start the WSM client devices that are to be boot up via multicast. Multicast Streaming 219 Figures 164 is a sample log file showing a successful multicast session in learn mode. Figure 164 Successful multicast session in learn mode 220 Appendix E Figures 165 is a sample log file showing a successful multicast session in normal mode. Figure 165 Successful multicast session in normal mode Multicast Streaming 221 Figures 166 is a log file showing a failed multicast session (one possible reason is network a mis-configuration). Figure 166 Failed multicast session 222 Appendix E This page intentionally blank. F Installing and Building Your WSM Environment: Detailed Procedures This appendix provides the detailed procedures you need to build the WSM environment you want. After deciding what kind of WSM environment you want (see "How to Build Your WSM Environment"), you can simply follow the steps in this appendix that you need and ignore the steps that you do not need. For example, if you do not need an Edge Server, you can skip the instructions on installing one. TIP: Using the What’s Next Sections of this Appendix: Depending on your desired environment (standard or advanced), you can follow the recommended for users who want a standard WSM environment option, or follow the options you need for the installation of an advanced WSM environment. In all cases, it is recommended to follow the What’s Next sections for convenient installation and configuration. IMPORTANT: If you plan to install and configure WSM components on multiple machines, you will repeat some of the installation and configuration procedures in this appendix. Likewise, you must also complete the pre-installation requirements for each related machine you intend to use. This appendix includes: • "Step 1: Preparing" • "Step 2: Installing and Configuring the WSM Core Server" • "Step 3: Starting the WSM Core Server for the First Time" • "Step 4: Installing and Configuring the WSM Client" • "Step 5: Installing and Configuring a WSM Edge Server" • "Additional Details You May Need" · "Installing Your Own SQL Server" · "Booting WSM via PXE, Non-PXE, and Cloud Desktop Device BIOS" · "Troubleshooting" · "Uninstalling: How to Uninstall WSM Software" · "Error Codes" 224 Appendix F Step 1: Preparing Use the following sections as needed to prepare for your WSM environment: • "Pre-Installation Checklist (Required for All Environments)" • "Planning for WSM Sites (Advanced Environments Only)" Pre-Installation Checklist (Required for All Environments) Before you begin building your WSM environment, make sure you have met the requirements on this checklist: • If you are planning to install and use a WSM Headquarters with Linked Sites, be sure to plan accordingly as discussed in "Planning for WSM Sites (Advanced Environments Only)." • Obtain and configure all hardware and software, as necessary (see "Hardware Requirements" and "Software Requirements"). • Install a supported server system on all server machines. Be sure that all systems are up-to-date with current Microsoft service packs, patches, and updates (see "Software Requirements"). • Install Microsoft Internet Explorer (IE) 9.x on all machines. • Obtain administrator rights and credentials on all systems involved with the installations. You will also need to understand the credentials required by WSM (see "System Security and Credentials"). • Ensure that all required server to server communications ports are available and open for proper communication between servers (see "Server to Server Communication Ports"). • Install and configure a DHCP Server on your network to provide IP addresses to your clients (see "Configuring the DHCP Server"). • Obtain a Server License File for each Stand-Alone or Headquarters Core Server you will install. WSM Server License files are provided to you when you register your product using the registration code sent to you in e-mail from Wyse (see "Server License Files"). • Use the WSMSuite.exe file to easily and automatically install everything you need for an SQL Server 2008 Express installation (see "Installing Microsoft SQL Server Using the WSMSuite.exe File"), if you do not already have a supported SQL Server installed and configured for use with WSM. Be sure the server is running before you begin installing WSM. • If you already have a supported SQL Server installed and configured for use with WSM, be sure you are running the latest Microsoft SQL Server Service Pack (see "Installing the Latest Microsoft SQL Server Service Pack"). • If you are planning to integrate Active Directory with WSM (see "Details About Using Active Directory Integration"), be sure that the Core Server and the Active Directory Server are part of the Domain before the administrator of the local system begins installing a WSM Core Server. • Obtain and prepare a Reference Device for WSM Client installation as discussed in "Step 4-A: Preparing the Reference Device Used for WSM Client Installation." What’s Next After you have completed all pre-installation requirements, continue with "Step 2: Installing and Configuring the WSM Core Server." Installing and Building Your WSM Environment: Detailed Procedures 225 Planning for WSM Sites (Advanced Environments Only) WSM supports the concept of “Sites”, whereby geographically dispersed locations can run WSM independently, each with its own database instance, yet managed from a central location. Each WSM Site is a fully-capable WSM installation, including a Core Server, database, and optional Edge servers. This allows remote offices or locations to continue normal operations even if network connectivity to the central-office or Headquarters is interrupted. Although each Site has a full WSM installation, all management and administration is performed from a central point. Use the following definitions when planning for WSM Sites: • Site: A local group of a Core Server and Edge servers that use a local database and can function independently from other Sites or Headquarters. There are three types of Sites: Headquarters, Linked Site, and Stand-Alone Site. • Headquarters: A special Site that is the focal point of WSM Administration, to control and manage other Sites. All administration activities, including OS and Application Image assignment and deployment, and server and device management, are performed from this location. • Linked Site: A Site that is “linked to” or managed by a Headquarters Site. Administration activities of Linked Sites are performed from the Linked Site. • Stand-Alone Site: A Site that is not linked to or managed by any other Site. For example, an existing WSM 2.x installation with a single database and Core Server would be considered a “Stand-Alone Site” in WSM 3.x terms (even if the servers were physically located at geographically dispersed locations). TIP: A WSM Site is not directly related to a physical location nor bounded by physical boundaries (such as a city or district). Administrators have complete flexibility in choosing how to organize their Sites. For example, you can set up a WSM Site for each city, or for each building in a campus, or, for a single floor in a building. You can even set up multiple “Sites” in a single room. Hardware Requirements Each machine must meet or exceed the minimum system requirements shown in Table 15 (these requirements may vary due to application and operating system sizes). Table 15 Server Hardware Requirements Category Minimum Requirements Recommended CPU 1 GHz CPU 2 GHz Dual Core or higher RAM 1 GB 2 GB or higher Disk Space 20 GB + AppSets size 100 GB (RAID) + AppSets size (if applicable) Network Interface Card (NIC) 100 Mbps 1 Gbps 226 Appendix F Software Requirements In addition to the WSM software, you must install the software shown in Table 16 on each server. Installing the latest version of each software package is highly recommended. Table 16 Server Software Requirements Component Software Requirements Operating System Microsoft Windows XP Pro SP3 or later, Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2 Database Server Microsoft SQL Server 2005, 2005 Express, 2008, or 2008 R2 Express Directory Service (optional) Microsoft Active Directory System Security and Credentials To keep the system secure, WSM uses various credentials. Most of these credentials are common for system administrators. The only new credential is for the WSM system itself. The following require passwords when they are installed: • WSM Database - The database requires a username and password for executing SQL queries. Each server in WSM requires this password to access the database. This information is stored encrypted in the Windows registry after installation. The default account is wsmdb; the default password is password@123. • Windows Service - All WSM servers are required to run as Windows Service with local system privileges. Caution If you plan to integrate Active Directory with WSM without SSL, you must ensure that the WSM OS Authentication Service is running with the credentials of an Active Directory user with privileges to create and manage computer accounts (for example, a member of the Account Operator group). In addition, this user must be a member of the local administrators group of the server, otherwise, the OS Authentication service cannot start when being configured to run with the credentials of the Active Directory user. For more information about integrating Active Directory with WSM without SSL, refer to "Using Active Directory Integration with and without SSL." Figure 167 WSM OS Authentication Service Properties - Log On Installing and Building Your WSM Environment: Detailed Procedures 227 • WSM Admin Account - To administer the WSM provider environment, a default account named admin must be created in the system. This account enables you to log on for the first time and to configure the system. It is highly recommended that you change the default password (admin) after you log in for the first time. • WSM Dispatcher Account - To view aggregated reports from all WSM sites (including Headquarters) and to schedule/deploy OS Images and patches to site groups. It is highly recommended that you change the default password (dispatcher) after you log in for the first time. • WSM Operator Account - To view aggregated reports from all WSM sites (including Headquarters). Operators cannot change WSM configurations. It is highly recommended that you change the default password (operator) after you log in for the first time. • WSM Site Admin Account - To provide limited access for Site-local login, an account named SiteAdmin must be created in the system. This account enables a Site administrator to log on to the remote Site only. It is highly recommended that you change the default password (admin) after you log in for the first time. Note that the Headquarters administrator can login to any Site. • WSM Site Operator Account - To view aggregated reports from Linked Sites only. Site Operators cannot change WSM configurations. It is highly recommended that you change the default password (operator) after you log in for the first time. • WSM Remote Service Account - To provide authentication between the Headquarters and Linked Sites for communication over https. Server to Server Communication Ports The following is a list of servers and default Server/Server communication ports (ensure that these ports are open for proper communication between servers): • OS Authentication Service (Default Port: 6910; you can use the Administrator Console to stop the service and configure to a different port) • OS Streaming Service (Default Port: 6911; you can use the Administrator Console to stop the service and configure to a different port) • Application Authentication Service (Default Port: 8001; you can use the Administrator Console to stop the service and configure to a different port) • Application Streaming Service (Default Port: 8002; you can use the Administrator Console to stop the service and configure to a different port) • Monitor Service (Default Port Range: 5000-5100) • Content Distribution Service (Default Port: 20248) • Multicast Boot Service (Default Port: 10703) • DHCP Proxy Service (Default Port: 67; you can use the Administrator Console to stop the service and configure to 4011, if the DHCP Server is running on the currently selected WSM Server) • Administration Service (Default Port: 8080) • SQL Port (Default Port: 1433) • If you have a firewall enabled on the server where the WSM Server software will be installed, you must also ensure that the following ports are configured as follows: · Content Distribution Service Client Port (Default Port: 20248) · NetBIOS Name Service (Default Port: 137) · TFTP Service (Default Port: 69) 228 Appendix F Configuring the DHCP Server A DHCP Server must be installed and configured on your network to provide IP addresses to your clients. The DHCP options shown in Table 17 must be specified. Table 17 DHCP server options DHCP Option Number Purpose DHCP Option Value for the Thin Client 03 Gateway Specific to the network. If a DNS server is not on the local area network, be sure to specify the IP address of the gateway for the local area network in which the client resides. 06 IP Address of the DNS Server Specify the IP address of DNS server that contains the record for the boot server. 60 Vendor Class Identifier (Use Only if the DHCP Server is on the Same Machine as the WSM Server) - Set to PXE Client (“Configure DHCP option 60 to ‘PXEClient’” in the server properties). Server License Files Before the end of the 90 day “grace” period, you must obtain and add a WSM Server License file for each Stand-Alone or Headquarters Core Server installation (to start the WSM system and register network devices). WSM Server License files are provided to you when you register your product using the registration code sent to you in e-mail from Wyse. Wyse uses these license files to control client seats and prevent software piracy. A WSM Server License file is encrypted using a PKI to sign each key (based on X.509 SSL Certificate). You need a license file for any of the following reasons: • Adding additional network devices • License expiration License files are stored in the database in an encrypted format. You can add the license file to the system by using the Administrator Console (after the Core Server installation is complete). For instructions on importing a license file, refer to "Step 2: Installing and Configuring the WSM Core Server." For more details on the Administrator Console, refer to "Configuring and Managing: Using the Administrator Console." Installing Microsoft SQL Server Using the WSMSuite.exe File In most cases, you can install an SQL Server on the same machine as the WSM servers for a single-server installation. To do so, it is highly recommended that you use the WSMSuite.exe file to easily and automatically install everything you need for an SQL Server 2008 Express installation (including Microsoft .Net Framework 3.5.1). Simply double-click the WSMSuite.exe file and follow the wizard. For instructions on installing your own SQL Server, refer to "Installing Your Own SQL Server." Caution During the installation, do not close the Ready to Install the Program window (which continues to show in the background during installation) and do not click Install more than once. Doing either of these will prevent a successful installation. Installing and Building Your WSM Environment: Detailed Procedures 229 Step 2: Installing and Configuring the WSM Core Server Although you can select custom installation configurations during the installation, it is recommended that you use the default configurations. TIP: Use these instructions to install a Core Server that you can later designate as a Headquarters or a Linked Site as discussed in "Managing Sites." 1. Double-click the WSMSuite.exe to open the Installation Wizard. Figure 168 Installation Wizard - Core Server 2. Click Next to open the License Agreement window. Figure 169 License Agreement - Core Server 3. After reading the agreement, select the I accept the terms in the license agreement option and click Next to open the WSM Server Information window. 230 Appendix F Figure 170 WSM Server Information - Core Server 4. Select the This is a new WSM installation option (to install the Core Server). 5. Click Next to open the Setup Type window. Figure 171 Setup Type - Core Server 6. Depending on the setup you want, complete one of the following: • (Recommended) If you want to use the default Destination Folder, default Streaming Server, and default Database Server, select the Typical option, and then click Next to open the Database Server and Authentication Information window and continue with step 10 (for default values used in the Typical option, refer to steps 7, 8, and 9). • If you want to select your own Destination Folder, Streaming Server, or Database Server, select the Custom option, and then click Next to open the Destination Folder window and continue with step 7. Installing and Building Your WSM Environment: Detailed Procedures Figure 172 231 Destination Folder - Core Server 7. Click Next to accept the default Destination Folder (C:\Program Files\Wyse\WSM) and open the Streaming Directory Information window. Figure 173 Streaming Directory Information - Core Server TIP: The Streaming Directory is where the Write Cache files, OS Images, and Application Images will be stored. Since this directory can become very large, consider putting it on a drive with enough disk space available. 8. Click Next to accept the default Streaming Directory (C:\Program Files\Wyse\WSM\StreamingDir) and open the Database Server window. 232 Appendix F Figure 174 Database Server - Core Server 9. Use the following guidelines: • Enter the Database Name to use for the SQL server (default is StreamingDB). Do not use special characters for the Database Name. • Enter the Username for the database (default is wsmdb). • Enter the Password for the database (default is password@123). • Confirm the password by re-typing it in the Re-Type Password box. • Click Next to open the Database Server and Authentication Information window. Figure 175 Database Server and Authentication Information - Core Server 10.Use the following guidelines: • CAUTION: By default the hostname of the local machine displays. If the SQL server is on a different machine, be sure to enter the SQL Server Name (hostname of the destination machine) in the Database box (do not use (local)). • Enter the Login ID and Password needed to connect to the database server in the appropriate boxes (note that the password for the SA user of the WSMSuite.exe file for an SQL Server 2008 Express installation is password@123). • Click Next to open the Ready to Install the Program window. Installing and Building Your WSM Environment: Detailed Procedures Figure 176 Ready to Install the Program - Core Server 11. Click Install to begin the installation. Figure 177 Installing WSM Core Server Caution Do not interrupt the installation. During the installation, the WSM Server Configuration window opens. Figure 178 WSM Server Configuration - Core Server 233 234 Appendix F 12.Select the Network Adapter to use, select the IP Address to use from the IP Address list, and then click OK to save the configurations, close the WSM Server Configuration window, and open the Installation Wizard Completed window. Figure 179 Installation Wizard Completed - Core Server 13.Click Finish to close the Installation Wizard. What’s Next After you successfully install the WSM Core Server, continue with "Step 3: Starting the WSM Core Server for the First Time," where you will use the Configuration Wizard (that appears after you logon to the WSM Administrator Console of the Core Server for the first time) to add your Core Server License (required) and enable Active Directory integration with WSM (optional). Installing and Building Your WSM Environment: Detailed Procedures 235 Step 3: Starting the WSM Core Server for the First Time After you successfully install the WSM Core Server, you must logon to the WSM Administrator Console of the Core Server to use the Configuration Wizard to add your Core Server License (required) and enable Active Directory integration with WSM (optional). 1. Open the WSM Administrator Console login page by clicking Start > WSM Server > WSM Console on the machine to which you have installed the WSM Core Server (you can also open a Web browser from any machine with access to the WSM Core Server and go to: http://<ipaddress>:8080/admin/). Figure 180 Login page 2. Enter the Admin Username (default is admin) and Password (default is admin) and click Login to open the Configuration Wizard. Figure 181 Configuration Wizard 3. Select the Stand-Alone option and click Setup Site to open the Import Server License page. TIP: If you have already created a Headquarters and are now creating the Core Server for a Linked Site, it is recommended that you select the Stand-Alone option, complete the initial setup, and later convert the Stand-Alone Site to a Linked Site (see "Managing Sites"). Note that Linked Sites or a Stand-Alone Site you intend to convert to a Linked Site do not need to import a license; you can click Skip when prompted for a license in the next step). (Advanced Users Only) If you select the Linked Site option here, WSM Services will be automatically restarted after the site configuration is completed and you will need to login again. If you try to login before the services have restarted, you will get an error message; retry after a few seconds. 236 Appendix F 4. Click Browse to find and select the license.txt file (provided to you by Wyse), and then click Import Server License to import the license and view the licence details. 5. Click Next to open the Active Directory Configuration page. 6. Depending on whether or not you want to enable Active Directory integration with WSM, select or clear the Enable Active Directory check box: TIP: For information to help you decide whether or not you want to integrate Active Directory with your WSM system (or if you need to configure or re-configure Active Directory in the future), refer to "Details About Using Active Directory Integration." For Linked Sites, clear the Enable Active Directory check box as Headquarters will provide the Active Directory integration. • If you clear the Enable Active Directory check box, click Finish to view the System Overview Congratulations page, and continue with step 17. • If you select the Enable Active Directory check box, the Configure Active Directory page expands (continue with step 7). 7. Enter the Group Synchronizing Polling Frequency time (number of seconds between synchronizing the members of user groups between Active Directory and the WSM database; default is 600 seconds; you can turn off the feature by setting the time to 0). 8. Click Next to open the Add Domain page. 9. Enter the Domain Name of Active Directory. 10.(Optional) Enter the DC Hostname or IP Address of Active Directory. Note that this optional field should only be used if it is required to point to a single DC rather than using the default DNS lookup mechanism to find the nearest DC (which is recommended). Therefore, this field should not be used unless there is a special reason. 11. Enter the Active Directory User (this can be the same user being used for running the OS Authentication Service—see "System Security and Credentials"). TIP: A user with privileges to create and manage computer accounts is needed for Active Directory integration. By default, members of the group named Account Operators or Domain Administrators have these privileges. 12.Enter the Password. 13.Enable Kerberos Authentication (optional or based on requirement). 14.Click Add Domain to add the domain and open the Import Groups page (the domain is added to the list of available domains on the Active Directory Domains page). 15.Select the user groups you want to import into the WSM database by using the following guidelines: • Enter the group name you want in the Group Name Contains box (use only letters, numbers, dashes, spaces, the @ character, and periods). • Enter the LDAP Context Root. • Enter the Max Results Limit (0 to the limit of all users in Active Directory). • After entering your filter criteria, click Filter to view the results. • Scroll through the list of groups and select the check boxes for the Group Names you want. 16.Click Finish to view the System Overview Configurations page. Users of these imported groups will automatically be added to the WSM User Name list on the Users page of the Administrator Console. Installing and Building Your WSM Environment: Detailed Procedures Figure 182 237 System Overview Configurations page 17.After completing the Configuration Wizard, you can view the Server Details page to see that the Core Server Services are successfully running (Status is Up on each service) by clicking the Servers tab, and then clicking the Name link of the Core Server. Figure 183 Core Server Details page 238 Appendix F What’s Next Depending on what you need for your WSM environment, do one of the following: • If you just configured and want to keep a Stand-Alone Site, continue with "Step 4: Installing and Configuring the WSM Client." • If you want to create a Headquarters and Linked-Site environment, refer to "Managing Sites." • If you just configured a Linked Site, you can do one of the following: · If you want to install Edge servers, continue with "Step 5: Installing and Configuring a WSM Edge Server." · If you do not want to install Edge servers, you are finished with WSM installation and can configure the rest of the WSM system according to your environment needs by following the appropriate procedures in this guide. For example, you may want to use the WSM Administrator Console to “register” (add) the OS Image to the WSM system and assign it to your WSM Servers and devices for streaming. Installing and Building Your WSM Environment: Detailed Procedures 239 Step 4: Installing and Configuring the WSM Client WSM Client software adds the required drivers and functions for base OS streaming to the Client operating system. It also enables application streaming and subscriptions for individual client users. An easy-to-use operating system image creation tool is included in the WSM Client software, which is used to create a base OS Image that can be provisioned to client devices in your WSM environment. Although you can select custom installation configurations during the installation, it is recommended that you use the default configurations. Warning Do not install WSM Client software on a Linked Site. Step 4-A: Preparing the Reference Device Used for WSM Client Installation WSM Client installation takes place on a Reference Device (PC, Wyse client device, or virtual machine) that contains the Windows XP Professional SP2, Windows XP Professional SP3, or Windows 7 Enterprise or Professional VL Edition operating system (that you will later stream to your clients). If using a Wyse client device as a Reference Device, you must also have the device drivers for your specific Wyse client device installed on the operating system (obtained from the Wyse Web site). The Reference Device must be a client device of the type that you will use in your client environment (the client devices to which you will stream the OS Image—PC, Wyse client device, or virtual machine). For example, if you will use a specific Wyse client product in your WSM environment, then you must use that specific Wyse client product for the Reference Device. Thus, all devices of that specific Wyse client product in your WSM environment will be able to use the OS Image created specifically for them. If you will use multiple types of Wyse client products in your WSM environment, then you must use multiple Reference Devices accordingly (you will assign the OS Images to the clients for which they were created using the WSM Administrator Console later). Caution It is highly recommended that the Reference Device be reserved for administrator Reference Device use only. Keeping a “clean” Reference Device can facilitate installations, deployments, patches, and OS Image testing. In addition, note that the Network card driver cannot be updated after the WSM Client has been installed and therefore the latest and greatest NIC-driver should be installed before installing the WSM Client on the Reference Device. A Reference Device for WSM Client installation can be physical machine (using WSM in a physical environment) or a virtual machine (using WSM in a VMware environment): • If the Reference Device is a physical machine: a. Use a USB CD-ROM drive to install the Windows XP Professional SP2, Windows XP Professional SP3, or Windows 7 Enterprise or Professional VL Edition operating system (be sure to configure the operating system to meet the needs of all client devices that will boot from it later). TIP: When installing the operating system, be sure to boot the Reference Device from the USB CD-ROM drive. If the Reference Device tries to boot from a blank flash drive, 240 Appendix F you will see a disk error. To ensure the Reference Device boots from the external USB CD-ROM drive, you must set the USB DVD drive to be the first boot device. For most Wyse clients and appliances, you can use the one-time boot menu: Attach the USB CD-ROM drive to the client. During boot, press and hold the P key. Select the USB Drive option and press Enter. For Wyse mobile clients, you can enter and change the BIOS Setup Utility: During boot, press and hold the F2 key. Enter the password Fireport (this is case sensitive) and press Enter. Select the Boot Device option and press Enter. Select the USB Drive option and move it to the 1 position by using the + key. Save the BIOS settings and reboot (you can return the original BIOS setup options at a later date if needed). b. (Optional) If using a Wyse client device, download and install the client device drivers you need for your specific device class (if you are using a Z00D for example, go to http://www.wyse.com/serviceandsupport/support/downloads.asp, select Z00D under Cloud PCs in the Product Downloads (Active) box, click Search, click the File Name link for the driver zip, and then use the File Download dialog box to install the drivers onto the supported Windows operating system). c. After you have installed the operating system (and if necessary, the device drivers) on the Reference Device, you are ready for the WSM Client software installation and can continue with "Step 4-B: Installing the WSM Client on the Reference Device." • If the Reference Device is a virtual machine: a. Create a target VM machine on an ESX Server as described on the VMware Web site. b. Install the supported Windows operating system (be sure to configure the operating system to meet the needs of all client devices that will boot from it later). c. After you have installed the operating system on the Reference Device, you are ready for the WSM Client software installation and can continue with "Step 4-B: Installing the WSM Client on the Reference Device." Installing and Building Your WSM Environment: Detailed Procedures 241 Step 4-B: Installing the WSM Client on the Reference Device TIP: Be sure you have completed all Reference Device requirements as described in "Step 4-A: Preparing the Reference Device Used for WSM Client Installation" before you begin installing the WSM Client on the Reference Device. 1. Log in to the Administrator Console, click the About link on the top-right corner of the Overview page to open the About WSM page (containing the WSM Suite Modules, Product Licensing information, and other important information), and then click on the WSM Client link to download and install WSM Client. 2. Double-click WSMClient.exe to open the InstallShield Wizard. Figure 184 InstallShield Wizard - WSM Client 3. Click Next to open the End User License Agreement window. Figure 185 License Agreement - WSM Client 4. After reading the agreement, select the I accept the terms in the license agreement option and click Next to open the Customer Information window. 242 Appendix F Figure 186 Customer Information - WSM Client 5. Enter the User Name and Organization, and then click Next to open the Destination Folder window. Figure 187 Destination Folder - WSM Client 6. Click Next to open the Ready to Install the Program window. TIP: If you have multiple Network adapters, then the Select Network Adapter window will be displayed prompting you to select the Network adapter. Select an Ethernet network adapter that supports PXE boot and is connected to a network reachable by the WSM streaming server. Installing and Building Your WSM Environment: Detailed Procedures Figure 188 243 Ready to Install the Program - WSM Client 7. Click Install to begin the installation. Figure 189 Installing WSM Client Caution Do not interrupt the installation. During the installation, the Found New Hardware Wizard opens. Figure 190 Found New Hardware Wizard - WSM Client 8. Select the Install the software automatically (Recommended) option and click Next to begin installation. 244 Appendix F Figure 191 Installing hardware - WSM Client After the software is installed, the Completing the Found New Hardware Wizard window appears. Figure 192 Completing the Found New Hardware Wizard - WSM Client 9. Click Finish to close the wizard and open the WSM Client Config Wizard. Figure 193 WSM Client Config Wizard Installing and Building Your WSM Environment: Detailed Procedures 245 10.Use the following guidelines to complete the WSM Client Config Wizard: • Enter the Authentication Server Info IP Address to be used by the WSM OS Authentication Service (this address is the same as the Core Server). The default Port information is automatically entered. • Enter the Imaging Server Info IP Address to be used by the WSM OS Streaming Service (this address is the same as the Authentication Server Info IP Address). The default Port information is automatically entered. • Enter the Web Server Info Port address, if necessary. This is the port on which the Web server runs. The default is entered automatically. • Enter the IOS Max Packet Length. This is the maximum data size of OS streaming packets sent from the server to the client; the default value is 1420. If your network requires a custom MTU (Maximum Transmission Unit) for IP packets (to meet encryption or other types of requirements), you can adjust this number to restrict the size of the packets. Set the value to 1370 to yield an MTU of 1398 (the maximum OS streaming data size [1370], plus the UDP header size [8], plus the IP header size [20]). Matching this value to the OS Streaming Max Packet Size registry setting on WSM servers is recommended. This field is used when either the WSM Client or Server is a version earlier than WSM 3.6.1 (with WSM 3.6.1 or later, the client auto-discovers MTU on boot up). TIP: The default Client Info IP Address and Port, Subnet Mask, and Gateway IP Address are automatically entered. • Click OK to close the WSM Client Config Wizard and open the InstallShield Wizard Completed window. Figure 194 InstallShield Wizard Completed - WSM Client 11. Click Finish to close the InstallShield Wizard. 12.After completing the procedures in this section, restart the system (escape out of the network boot by pressing ESC). You now have the Windows OS Image you need (including the WSM Client software, imaging tools, virtual applications, and if necessary, the device drivers) for your WSM environment on the Reference Device. 13.Continue with "Step 4-C: Capturing the OS Image from the Reference Device to the Core Server." 246 Appendix F Step 4-C: Capturing the OS Image from the Reference Device to the Core Server IMPORTANT: For information on how to prepare an existing VHD file (and how to create a new VHD file) for WSM streaming, see "Using a VHD Image." TIP: Be sure you comply with all Microsoft operating system licensing requirements before capturing and streaming your Windows OS. After installing the WSM Client software, you must capture the OS Image from the Reference Device to the Core Server for streaming. TIP: Be sure you have all peripherals (with proper device drivers installed) you want to use (for example, keyboard, mouse, printers and so on) connected before you begin capturing the OS Image to the Core Server. OVERVIEW NOTE: There are generally 3 steps required to capture a virtual disk. For Windows 7, the first step involves capturing the primary image. After reboot and during the second step, the process to capture locked files will begin automatically (note that for Windows XP, steps 1 and 2 are combined). After reboot and during the third and final step, the following window will appear. Figure 195 WSM Client - Virtual Disk Image Creation (Step 3 of 3) The dialog box itself also involves KMS licensing and is explained in the Windows 7 Licensing Best Practices document on the Wyse knowledge base. Note also that you should test the image to make sure it is working properly before completing this final step. Use the following guidelines to capture the OS Image: 1. After installing the WSM Client software, open the WSM VDisk Image Creation Utility window (Start > All Programs > Wyse > WSM Imaging Tools > Virtual Disk Image Creation). Figure 196 OSMVDiskImage.exe location Installing and Building Your WSM Environment: Detailed Procedures 247 NOTE: You can also open the WSM VDisk Image Creation Utility window by double-clicking the OSMVDiskImage.exe file (the default location is C:\Program Files\Wyse\WSM\os). Figure 197 WSM VDisk Image Creation Utility window 2. Use the following guidelines: • Enter the VDisk size in MB (the maximum virtual disk size is 102400 MB/100 GB). • Enter a VDisk Name. • (Optional) Enter a Description for the disk. • Depending on whether or not you want to integrate WSM with Active Directory, select or clear the Enable Active Directory Integration check box; to integrate WSM Client authentication with Active Directory (Single Sign On). • Depending on whether or not you want to move the User Profiles to a separate partition, select or clear the Move User Profiles to a separate partition check box. TIP: In older versions of WSM, if the base OS image was updated, all user information was lost because the write cache had to be discarded. Since WSM 3.0, WSM has the ability to separate the user data from the system information by placing the User Profiles folder on a different partition. This enhancement allows user profiles and data to persist even when the base OS image is updated. If you select this option, the WSM VDisk Image Creation Utility will automatically calculate a size for the new partition based on the specified size for the entire VDisk. When the Move User Profiles to a separate partition option is used, the resulting VDisk contains two partitions. Each of these partitions has its own cache mode so that you can control how data is stored on each partition. If the system partition is updated, the information in the User Profile partition is treated as still valid and will be kept. When capturing a VDisk with the Move User Profiles to separate partition option selected, a reboot is required to finish the VDisk creation. • Depending on whether or not you want to move the Page File to a separate partition, select or clear the Move Page File to a separate partition check box. TIP: You can also move the Page File to a separate partition of the VDisk. This allows excluding updates to the Page File when performing OS patching, resulting a smaller patch file to be distributed to the streaming servers. • (User Recommended Partition Sizes option is disabled if you are only creating a one partition virtual disk) Depending on whether or not you want to use 248 Appendix F recommended partition sizes, select or clear the Use Recommended Partition Sizes check box. Clearing this check box allows you to manually enter the sizes you want for each partition (CAUTION: the total of all partition sizes must add up to the VDisk size). • Use the Advanced Optimizations dialog box (click Advanced Optimizations) to enable options. Each option is a service or option within Windows that is normally enabled by default, but are now disabled to improve Virtual Disk performance. Figure 198 Advanced Options - Windows XP example TIP: The WSM VDisk Image Creation Utility calculates the minimum required size for the VDisk and will not allow you to create a VDisk that is smaller than this required size. 3. Click Create VDisk to begin building the virtual disk. After building is complete, the Done message appears in the WSM VDisk Image Creation Utility window (the OS Image capturing process is complete) and you will be prompted to reboot. Note also that you should test the image to make sure it is working properly before completing this final step (for example, boot the OS Image to the reference device. TIP: After Virtual Disk image creation is complete, the OS Image is displayed in the WSM Administrator Console under Unregistered OS Images section as Captured and ready to stream. When you are ready to stream the OS Image, you must then click Register and select the cache modes desired to display the OS Image in the Registered OS Images section where it will be available to be assigned to your devices. For information on expanding an existing Virtual Disk image, see "Expanding an Existing Virtual Disk" What’s Next Depending on what you need for your WSM environment, do one of the following: • If you do not want to create a Linked Site or install Edge Servers, you are finished with WSM installation and must now use the WSM Administrator Console to “register” (add) the OS Image to the WSM system and assign it to your WSM Servers and devices for streaming (see "Registering OS Images"). For information on using the WSM Administrator Console, refer to "Configuring and Managing: Using the Administrator Console." TIP: This is recommended for users who want a standard WSM environment. • If you want to create a Linked Site to be controlled by an existing Headquarters, continue with "Step 2: Installing and Configuring the WSM Core Server." Installing and Building Your WSM Environment: Detailed Procedures • 249 If you want to install Edge servers for use with a Core Server, continue with "Step 5: Installing and Configuring a WSM Edge Server." 250 Appendix F Step 5: Installing and Configuring a WSM Edge Server Although you can select custom installation configurations during the installation, it is recommended that you use the default configurations. 1. Log in to the Administrator Console, click the About link on the top-right corner of the Overview page to open the About WSM page (containing the WSM Suite Modules, Product Licensing information, and other important information), and then click on the WSM Server link to download and install WSM Server. 2. Double-click WSMServer.exe to open the Welcome window. Figure 199 Installation Wizard - Edge Server 3. Click Next to open the License Agreement window. Figure 200 License Agreement - Edge Server 4. After reading the agreement, select the I accept the terms in the license agreement option and click Next to open the WSM Server Information window. Installing and Building Your WSM Environment: Detailed Procedures Figure 201 251 WSM Server Information - Edge Server 5. Select the This server belongs to the following WSM installation option and enter the Core server IP address for connection to the Core Server. 6. Click Next to open the Setup Type window. TIP: If the WSM Edge Server cannot connect to the Core Server Registry (for example, the remote registry is disabled on the Core Server for security reasons), then a warning message appears. Click OK to close the warning message and open the Setup Type window. Figure 202 Setup Type - Edge Server 7. Depending on the setup you want, complete one of the following: • (Recommended) If you want to use the default Destination Folder, default Streaming Server, and default Database Server, select the Typical option, and then click Next to open the Database Server and Authentication Information window and continue with step 10 (for default values used in the Typical option, refer to steps 7, 8, and 9). • If you want to select your own Destination Folder, Streaming Server, and Database Server, select the Custom option, and then click Next to open the Destination Folder window and continue with step 7. 252 Appendix F Figure 203 Destination Folder - Edge Server 8. Click Next to accept the default Destination Folder (C:\Program Files\Wyse\WSM) and open the Streaming Directory Information window. Figure 204 Streaming Directory Information - Edge Server TIP: The Streaming Directory is where the Write Cache files, OS Images, and Application Images will be stored. Since this directory can become very large, consider putting it on a drive with enough disk space available. 9. Click Next to accept the default Streaming Directory (C:\Program Files\Wyse\WSM\StreamingDir) and open the Database Server window. Figure 205 Database Server - Edge Server 10.Use the following guidelines: Installing and Building Your WSM Environment: Detailed Procedures • Enter the Database Name created while installing the Core Server (default is StreamingDB). Do not use special characters for the Database Name. • Enter the Username for the database (default is wsmdb). • Enter the Password for the database (default is password@123). • Confirm the password by re-typing it in the Re-Type Password box. 253 Warning Be sure to use the same information that you entered in the Database Server window when you installed your Core Server as described in "Step 2: Installing and Configuring the WSM Core Server." • Click Next to open the Database Server and Authentication Information window. Figure 206 Database Server and Authentication Information - Edge Server 11. Use the following guidelines: • CAUTION: Be sure to enter the SQL Server Name where the Core Server is installed in the Database box (do not use (local)). • Enter the Login ID and Password needed to connect to the database server in the appropriate boxes (note that the password for the SA user of the WSMSuite.exe file for an SQL Server 2008 Express installation is password@123). • Click Next to open the Ready to Install the Program window. Figure 207 Ready to Install the Program - Edge Server 12.Click Install to begin the installation. 254 Appendix F Figure 208 Installing WSM Edge Server Caution Do not interrupt the installation. During the installation, the WSM Server Configuration window opens. Figure 209 WSM Server Configuration dialog box - Edge Server 13.Select the Network Adapter to use, select the IP Address list to use, and then click OK to save the configurations, close the WSM Server Configuration window, and open the Installation Wizard Completed window. Installing and Building Your WSM Environment: Detailed Procedures Figure 210 255 Installation Wizard Completed - Edge Server 14.Click Finish to close the Installation Wizard. What’s Next Depending on what you need for your WSM environment, do one of the following: • If you want to install and configure additional Edge Servers, repeat the procedures in "Step 5: Installing and Configuring a WSM Edge Server." • If you do not want to install and configure additional Edge Servers, you are finished with WSM installation and can configure the rest of the WSM system according to your environment needs by following the appropriate procedures in this guide. For example, you may want to use the WSM Administrator Console to “register” (add) the OS Image to the WSM system and assign it to your WSM Servers and devices for streaming. 256 Appendix F Additional Details You May Need This section includes: • "Installing Your Own SQL Server" • "Booting WSM via PXE, Non-PXE, and Cloud Desktop Device BIOS" • "Expanding an Existing Virtual Disk" • "Using a VHD Image" • "Troubleshooting" • "Uninstalling: How to Uninstall WSM Software" • "Error Codes" Installing Your Own SQL Server In special cases of a large production environment, it is recommended that you install the Database Server on a server machine that is separate from the WSM servers. WSM supports three databases: SQL Server 2005 Express, SQL Server 2005 SP1 or later, SQL Server 2008 Express, and SQL Server 2008. Make sure that your network is configured to allow all servers to communicate with your database on the configured SQL port. All servers will authenticate with the database using configured credentials. CAUTION: You should refer to the documentation provided by the database vendor for complete installation instructions, performance enhancements, and setup. IMPORTANT: In most cases, you can install an SQL Server on the same machine as the WSM servers for a single-server installation. To do so, it is highly recommended that you use the WSMSuite.exe file to easily and automatically install everything you need for an SQL Server 2008 Express installation (see "Installing Microsoft SQL Server Using the WSMSuite.exe File"). Installing SQL Server 2005 Express, SQL Server 2005 SP1 or Later, SQL Server 2008 Express, or SQL Server 2008 1. Start SQL Server installation. 2. Select the Server Components, Tools, Books Online, and Samples option. 3. Click Next to accept the licensing terms and conditions. 4. Click Install to install software components required prior to installing SQL Server. 5. Click Next when the component installation is complete (it may take several minutes for the components to be installed and configured). 6. After a system configuration check is complete and the Microsoft SQL Server Installation dialog appears, click Next to open the Registration Information dialog box. 7. Clear the Hide Advanced Configuration Options check box. 8. After the next system configuration check is complete, click Next. 9. Enter your name and company name, and then click Next. 10.Select the components SQL Server Database Services, select the Workstation Client components, and then click Next. 11. Select Default instance (don’t specify a named instance), and then click Next. 12.Select Use the Local System Account, and then click Next. 13.Select Mixed Mode as your Authentication mode, enter a password (CAUTION: Note this password as it must be entered later during WSM installation; you can enter the Installing and Building Your WSM Environment: Detailed Procedures 257 default password@123 that the WSM installation will expect, however, it is recommended to use a password that is different than this default password for additional security), and then click Next. TIP: Verify that the database is configured to run in Mixed Mode for authentication. WSM uses both ODBC and JDBC to communicate with the database using SQL authentication. If Mixed Mode is not selected, the servers cannot communicate with the database. This setting is located under the Security tab of the database properties labelled SQL Server and Windows NT. 14.Select the SQL Collations option, select Dictionary Order, Case-Insensitive, for Use with 1252 Character Set, and then click Next. 15.Clear both of the error usage and reporting boxes, and then click Next. 16.Click Install to start the installation (the installation may take several minutes). 17.After all components have been installed and configured, click Next. 18.Review the installation summary and click Finish. 19.After installation is complete, be sure to enable the Named Pipes and TCP/IP protocols for SQL Server by opening the SQL Server Configuration Manager and enabling the protocols (for each, right-click and select Enable). Figure 211 SQL Server Configuration Manager TIP: If you plan to install the database on a separate server, install SQL Server Client Tools on the same machine that will host the WSM Server software. Installing the Latest Microsoft SQL Server Service Pack It is highly recommended that you download and install the latest service pack for the SQL Server version that you are using. For complete information on SQL service packs, refer to the Microsoft Web site. TIP: If you are given the option to modify the Authentication Mode during service pack installation, be sure to select Mixed Mode to allow the WSM Core Server software to access the database. 258 Appendix F Booting WSM via PXE, Non-PXE, and Cloud Desktop Device BIOS This section discusses PXE and non-PXE boot-up processes and how to boot WSM clients on networks that do not support PXE or that have not been configured to support PXE or standard DHCP. In addition, WSM also supports booting through Cloud Desktop devices on specific Dell PC models. PXE and Non-PXE Boot-Up Processes This section compares the PXE and non-PXE boot-up processes. In each environment, the bootstrap file resides in a different location: • PXE environment: The WSM PXE bootstrap file (vldrmi13.bin) resides on a network TFTP server that is accessible by the WSM client. • Non-PXE environment: The WSM non-PXE bootstrap file (secrmi13.bin) resides on a hard disk, floppy disk, or USB key attached to the WSM client. Table 18 displays the boot-up process in PXE and non-PXE environments. Table 18 Boot-up process in PXE and non-PXE environments PXE Boot-Up Non-PXE Boot-Up 1 The WSM client boots up with the LAN/ PXE boot option enabled. The WSM client boots up to the hard disk, floppy disk, or USB-key device. 2 In BIOS, the PXE client is executed. BIOS loads and initiates the WSM non-PXE bootstrap file from the hard disk, floppy disk, or USB-key device. 3 The BIOS PXE client obtains network configurations and boot-server information from the DHCP server (for this to occur, the DHCP or proxy DHCP server must support PXE extended protocol). The WSM non-PXE bootstrap file tries to obtain network configurations from the standard DHCP server. If DHCP fails, the user can enter network configurations manually. (These statically configured network settings are saved in permanent storage so that they can be used on subsequent boot-ups.) 3A The BIOS PXE client downloads and executes the WSM PXE bootstrap file from the WSM server using TFTP. 4 The WSM PXE bootstrap file communicates with the WSM Login server and starts the streaming process. The WSM non-PXE bootstrap file communicates with the WSM login server and starts the streaming process. Installing and Building Your WSM Environment: Detailed Procedures 259 PXE and Non-PXE Boot-Up Requirements Table 19 displays the requirements for PXE and non-PXE boot-up. Table 19 Requirements for PXE and non-PXE boot-up Non-PXE Boot-Up Must support PXE v2.0 or later. (PXE is not used, but the UNDI APIs within PXE support must be present for the non-PXE bootstrap file to communicate with the network. Some BIOS do not load UNDI support when the PXE Boot option is not used. A WSM non-PXE bootstrap will fail with a “No APIs” error when running on such BIOS.) If the non-PXE bootstrap file resides on a USB key, the BIOS must support booting to a USB key. DHCP server Must support PXE. Support is optional. If not supported, the user can enter a static IP for the WSM client. WSM bootstrap The WSM bootstrap file The WSM bootstrap file must be installation must reside on a TFTP programmed into the WSM client hard server that the WSM client disk, floppy disk, or USB key. This is a can access over the manual process. See “Non-PXE network. This file location is Bootstrap Deployment” for details. established during the WSM server installation. WSM Client BIOS PXE Boot-Up Must support PXE v0.99 or later. PXE and Non-PXE Boot-Up Features Table 20 displays the features in PXE and non-PXE boot-up. Table 20 Features of PXE and non-PXE boot-up Use DHCP Use statically entered network configuration (IP, gateway, subnet mask, DNS servers, domain name) WSM login server IP PXE Boot-Up Yes No Non-PXE Boot-Up Yes (optional) Yes (if DHCP fails) Hard-coded in the bootstrap file upon WSM installation No DNS lookup on hostname “WSMServer” or if DNS fails, manually entered Yes Dynamically obtain new WSM login servers list from existing login server Save login servers list to permanent No storage; use saved settings on subsequent boot-ups G key reset (pressing the G key on N/A boot-up restores the WSM bootstrap file to default settings) Yes Yes 260 Appendix F Non-PXE Bootstrap Deployment To boot a WSM client on a network that does not support PXE, the bootstrap file must reside on a local storage device attached to the WSM client, and the WSM client BIOS must be able to boot to the storage device where the non-PXE bootstrap file is installed. This section contains the deployment options and setup instructions for booting a WSM client from a non-PXE bootstrap file on a floppy disk, hard disk or flash drive, or USB key. Wyse supports these non-PXE boot media and WSM client combinations: • Wyse thin client, mobile client, or appliance: USB key, USB floppy disk. • X86-based PCs: Hard disk, built-in and USB floppy disk. • VMware virtual session: Floppy disk (in floppy disk image file format). Launching Non-PXE from a Floppy Disk The WSM non-PXE boot floppy image file can be downloaded from the Wyse Knowledge Base at: www.wyse.com/serviceandsupport/support/kbase.asp. To configure a VMware virtual session floppy device: 1. Select the WSM non-PXE boot floppy image file. 2. Connect at power up. 3. Power up the virtual session when you have finished configuring the virtual session floppy device. To configure Wyse thin clients and X86-based PCs: 1. Use any third-party tool (such as dskimage) to program a 1.44MB floppy disk from the WSM non-PXE boot floppy image file. 2. Configure the WSM Client BIOS to boot from the built-in or USB floppy disk. 3. Plug in the WSM non-PXE boot floppy and power up the WSM client. Launching Non-PXE from a Hard Disk or Flash Drive This section explains how to prepare a non-PXE hard disk or flash drive for WSM non-PXE bootstrap and how to boot from a non-PXE hard disk or flash drive. Step1: Preparing the Hard Disk or Flash Drive Use the WSM Bootstrap Utility to prepare a hard disk or flash drive so that you can use it for a WSM non-PXE bootstrap. This application is available in the Client Utilities package. TIP: You cannot create a bootstrap partition on a bootstrap partition previously created by the WSM Bootstrap Utility. Even if you specify the size of the partition to be the required 8MB, Windows in most cases rounds the size of the partition to less than 8MB, rendering the bootstrap invalid. To create a new bootstrap partition, either erase the old partition and allocate 8MB or more to it, or create a new partition larger than 8MB. After you start the utility, the WSM Bootstrap Utility dialog box appears. Installing and Building Your WSM Environment: Detailed Procedures Figure 212 261 WSM Bootstrap Utility dialog box To prepare a hard disk or flash drive for a WSM non-PXE bootstrap: 1. In the Available Disks list, select a drive connected to the system. Network drives and mapped drives are not listed. 2. In the Drive to Format list, select the drive you want to format as the drive for the WSM non-PXE bootstrap (if a hard disk has existing partitions, all available partitions will be listed in the Drive to Format list). After selecting a drive, review the Drive Details area to make sure the drive is sufficient for the WSM non-PXE bootstrap: · Type: Lists the type of drive. Hard disks and flash drives are fixed. · Format: Lists the format that the drive supports—FAT, FAT32, or NTFS. · Capacity: Lists the storage capacity of the drive. The minimum capacity requirement for a non-PXE boot partition is 8MB. · Partition: Indicates whether the partition you selected is an active partition. 3. Click Create to begin creating a non-PXE bootstrap partition on the drive you selected. The WSM Bootstrap Utility: • Changes the drive’s partition information to show 8MB only. TIP: Even if the drive being partitioned is more than 8MB in size, if you select it as the WSM non-PXE bootstrap drive, its size is reduced to 8MB and the remaining capacity is wasted. However, you can reuse the wasted space by creating another drive using the Windows Disk Management Console. • Formats the drive with the FAT12 format, makes it Active (bootable), and installs the WSM non-PXE bootstrap. Warning The partition will be re-partitioned and reformatted. Any existing files on the partition will be erased. TIP: In the case of a raw disk with no existing partitions, clicking Create begins creating a non-PXE bootstrap partition on the raw disk. The utility creates an 8MB partition in FAT12 format, makes it bootable, and installs the non-PXE bootstrap file. Step 2: Booting from a Non-PXE Hard Disk or Flash Drive To boot from a non-PXE hard disk or flash drive: 1. Make sure your WSM client BIOS is configured to boot from the local hard disk. 262 Appendix F 2. Start the WSM client. Launching Non-PXE from a USB Key To prepare a USB key as the WSM non-PXE bootstrap partition, the USB flash key must be pre-formatted to a bootable hard drive in the FAT16 or FAT32 format. You can format drives for FAT16 or FAT32 with any third-party tool that creates bootable USB keys. TIP: The Wyse® USB Firmware ToolTM provides a simple USB imaging solution to help you quickly and easily image supported devices. For information on using the Wyse USB Firmware Tool, refer to the Users Guide: Wyse USB Firmware ToolTM. Step 1: Preparing the USB Key To prepare the non-PXE USB key: 1. Use a third-party tool to format a USB key to a bootable hard drive in FAT16 or FAT32 format (note that floppy drive partitions are not acceptable). 2. With the USB key plugged in, launch the WSM Bootstrap Utility. 3. Select the drive letter to which the USB key is mounted and click Create. The WSM Bootstrap Utility installs a WSM non-PXE bootstrap file on the USB key. The drive is not re-formatted; any existing files on the drive are preserved. Step 2: Booting from a Non-PXE USB Key To boot to the WSM client: 1. Configure the WSM client BIOS to boot to the USB key (For specific models and product instructions, refer to the Users Guide: Wyse USB Firmware ToolTM). 2. Start the WSM client. Entering Network Configuration Information for Non-PXE Boot-Up In a network that does not have a DHCP server, the WSM non-PXE bootstrap file cannot obtain the network configuration information from a standard DHCP server. To provide this information, the user must enter a valid IP address for the client computer, and optionally, the Gateway IP, subnet mask, and DNS IP on the initial screen (you can press Esc to bypass a specific input request if you do not know the information being requested). Finally, the user must enter at least one WSM Authentication Server IP address so that the client computer can boot up through the WSM server. TIP: Network configuration information is saved in permanent storage so that it can be used on subsequent boot-up. To erase previously entered network configurations, press the G key on client boot. Users will then be presented with a G-key menu with one of the options displayed as “<option number>: Clear previously saved network configurations and Login Server lists?”. Enter <option number> and confirm the operation by typing yes when prompted. Installing and Building Your WSM Environment: Detailed Procedures 263 Expanding an Existing Virtual Disk This section describes how to expand an existing virtual disk. An existing virtual disk can be expanded by using the VdiskImageCreation.exe tool (Start > All Programs > Wyse > Wyse Imaging Tools). The additional disk space can be used for extending the current system partition, or creating a new partition to store future applications and data. Use the following guidelines: 1. Boot a WSM client device from hard disk and launch the Add Edit Virtual Disk Utility. (Start > All Programs > Wyse > Wyse Imaging Tools > Add Edit Virtual Disk Utility). The utility can also be launched manually from: C:\Program Files\Wyse\WSM\os\VDiskImageCreation.exe. Figure 213 Add Edit Virtual Disk Utility 2. Select the Existing Disk option and then select the existing VDisk you would like to resize. The size and version are automatically displayed once the VDisk is selected. You can then specify a new desired size and click Start to begin the resize operation. NOTE: From release 3.1 and later, the VDisk extension operation also promotes the vdisk to latest version (for example, if a version 2 VDisk is extended, it is promoted to version 4 and is multi-partitions capable). 3. If the target VDisk is an older version or not yet streamed and is in private mode (all partitions) then the VDisk is immediately extended. If you are trying to extend a newer VDisk or if the VDisk is not in private mode, then its size cannot be changed directly. Starting with WSM 5.0, you must make a copy of the existing VDisk and switch each partition cache mode to private. The new VDisk name will have _copy appended to it (for example, R_XP_8046 would become R_XP_8046_copy. 4. The <VDISK_NAME> is now expanded to the desired size message is displayed. However, the additional space is not yet usable. If you want to create a new partition or expand the last partition to use the new disk space, you must first map the VDisk as a non-removable drive and then reboot the system. If you select yes for the Do you want to map the VDisk as a non-removable drive now? message, then the VdiskImageMap tool is launched; if not, then the process ends. 5. In the VdiskImageMap Utility window, select the target VDisk name from drop-down list, and then select the Map as non-removable disk option to display the Map Image message informing you that the VDisk will be mapped on the next boot (so a reboot is 264 Appendix F required at this point). Note that another message displays to inform you of the steps to take after reboot and provides an option to Reboot Now. Figure 214 VDisk Image Mapping Utility After client reboot, observe from the disk manager that the target VDisk has some unallocated space right after the existing OS partition. Figure 215 Disk Manager If you want to expand the existing VDisk system partition to use the unallocated disk space: - If running on Windows 7, then select the appropriate disk from disk manager (disk 2 in example above) and then select Extend Volume. - If running on Windows XP, open a command windows, run diskpart.exe, and then run the following commands: diskpart >> list volume diskpart >> select volume <vdisk volume number> diskpart >> extend diskpart >> exit Observe from the disk manager that the target VDisk OS partition is expanded. Shut down the client. If want to create a new partition from the unallocated disk space: Use disk manager to create and format a new partition from the unallocated disk space. Shut down client. 6. (Optional) If this was a VDisk _copy, then use the WSM Administrator Console to re-register the new VDisk and set the desired cache mode for each partition. The VDisk is now ready to use. Installing and Building Your WSM Environment: Detailed Procedures 265 Using a VHD Image This section describes how to prepare an existing VHD file (and how to create a new VHD file) for WSM streaming. NOTE: Virtual Hard Disk (VHD) is a file format which represents a virtual hard disk drive (HDD). VHD files are supported by Microsoft Virtual PC and Virtual Server. A VHD file may contain what is found on a physical HDD, such as disk partitions and a file system containing files and folders. Use the following guidelines: 1. In this step you will make the VHD file streamable. Be sure the WSM Client is installed on the client device as described in "Step 4-B: Installing the WSM Client on the Reference Device." After installation, launch the VHDHelper.exe from WSM Client Utilities install folder, select the VHD file to convert to a streamable image, and then press Start (click OK when complete). Figure 216 VHDHelper NOTE: VHDHelper updates a few registries within the .vhd file to make it streamable. A streamable VHD file is no longer bootable from a hard disk. If you want to keep a .vhd file bootable to HDD, make a copy of the target VHD file and run VHDHelper on the copy. You can also convert the .vhd file back to HDD bootable later using the VHDHelper tool. Note also that WSM does not provide a tool to adjust the size of a VHD VD. If you need a VHD VD of a different size than the current .vhd file, use Windows DiskPart or a third party VHD resizing tool to adjust the VHD file to the desired size before running VHDHelper. 2. In this step you will copy the streamable VHD file to a WSM streaming server. Be sure the target VHD file is unmounted from the client device host OS, and then copy the .vhd file to the osimages folder of the Streaming Directory on the WSM Core server (for example, C:\Program Files\Wyse\WSM\StreamingDir\osimages). 3. In this step you will create a WSM VD wrapper file. On the WSM server, open a command window with Administrator privileges, change directory to the WSM Install folder (for example, C:\program files\wyse\wsm\os), and run vdtool.exe -createvd <name and path of target vhd file> (for example, vdtool.exe -createvd...\StreamingDir\osimages\Z-FixedVHD.vhd). You should now see a new wrapper file Z-FixedVHD being created under the osimages folder. This VHD VD (formed by 2 files: Z-FixedVHD + Z-FixedVHD.vhd) can now be registered to the WSM database, switch to persistent or volatile cache mode, and then assign to devices for streaming from the WSM Administrator Console. 266 Appendix F Troubleshooting This section contains information and help on installation, setup, conflicts, and general troubleshooting. For a complete list of error codes and descriptions, refer to "Error Codes." This section includes: • "Active Directory: Connection Error Messages when Enabling Active Directory" • "Audio: Solving Audio Problems in the Streaming Environment" • "Core Server: Verifying that WSM Core Server Services are Running" • "Database: Verifying that the WSM Database is Operational and Configured Correctly" • "Hostname and IP Address: Performing Changes" • "Login Error: You Encounter an Error While Trying to Access the WSM Login Page" • "Network Device: Error Messages When Adding a Network Device from Active Directory" • "ODBC: Verifying that the ODBC is Operational and Configured Properly" • "OS Image: Capturing an OS Image after Cancelling the Capture Process" • "OS Image: Re-configuring an OS Image" • "WSM Services: Verifying a Successful Installation by Viewing the WSM Services" Active Directory: Connection Error Messages when Enabling Active Directory Problem: After enabling and configuring Active Directory for the first time (as described in "Step 3: Starting the WSM Core Server for the First Time"), clicking Finish produces an error stating that Active Directory cannot be connected. Solution: Use the following procedures: • Be sure that the Core Server and the Active Directory server are part of the Domain before the administrator of the local system begins installing the WSM Core Server. • Ensure that the display name for the Active Directory User is the same as the user name used for connecting to Active Directory. • Ensure that you can ping the Domain (for example, wsm.com). • Try to disable Kerberos if enabled. Audio: Solving Audio Problems in the Streaming Environment Problem: All non-administrator users on the locally streamed OS Image are having audio problems. Solution: Use the following procedures: 1. Shut down all client devices booted from this OS Image. 2. Boot one client device from the OS Image. 3. Login to the client device as an administrator and set the registry values as follows: A DWORD value named SType must be created and set to 19601 (decimal) in both of the following keys: • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Efsd\ • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OTFileSpoofer\ Installing and Building Your WSM Environment: Detailed Procedures 267 4. Shut down the client device. 5. Change the OS Image mode back to either Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode) using the Administrator Console (for procedures on editing an OS Image, refer to "Editing OS Images." 6. Login as a non-administrator user, and verify that the audio is working properly. Core Server: Verifying that WSM Core Server Services are Running To verify that WSM Core Server services are running (if using Headquarters and Linked Sites, be sure to also verify Core Servers on all Linked Sites): 1. Log in to the WSM Administrator Console. 2. Click the Servers tab to open the Servers page. 3. Click the Name link of the Core Server to open the Server Details page. 4. Ensure that the Core Server Services are successfully running (Status is Up on each service). If necessary (any service Status is Down), click the Start All link next to the Status list to start all services on the Core Server. Database: Verifying that the WSM Database is Operational and Configured Correctly To verify that the WSM Database is operational and configured correctly: 1. Using SQL Server Enterprise Manager, verify that the StreamingDB database exists. To verify that SQL Server user account wsmdb is set up correctly, open Enterprise Manager, expand your SQL Server tree to expand the Security folder, click Users, verify that wsmdb exists and that it has the proper permissions (by right-clicking the wsmdb name, selecting Properties, clicking the Database Access tab, selecting StreamingDB, and then verifying that the db_owner and Public boxes are selected). 2. Verify that the ODBC Connection is configured correctly: a. Open the Control Panel, choose Administrative Tools, and click Data Sources (ODBC). b. Click on the System DSN tab, enter StreamingDB, and then click Configure to open the Microsoft SQL Server DSN Configuration dialog box. c. Click Next, and then click Client Configuration. to open the Add Network Library Configuration dialog box. d. Select the TCP/IP option, enter the appropriate IP information for your SQL Server, and then click OK. e. Click Next to finish establishing the ODBC database connection. f. Click Test Data Source, and then click Next to determine whether the ODBC connection has been set up correctly (you should see the Tests Completed Successfully message to know that the server installation setup is now complete). Hostname and IP Address: Performing Changes If the Hostname or IP Address of a server is changed, WSM will attempt to automatically detect and reconfigure itself: • IP address of a Core Server or an Edge Server is changed — If the IP address of a Core Server or an Edge Server changes, there is an automatic update of the corresponding WSM Data. If for any reason this automatic update fails, a message is 268 Appendix F displayed in the Overview page of the Administrator Console to reflect this inconsistency. In this situation, you must reconfigure the system manually according to your required configurations (for configuration guidelines, refer to "Editing Servers." • Name of a Core Server or an Edge Server is changed — If the name of a Core Server or an Edge Server changes, there is an automatic update of the corresponding WSM Data. If for any reason this automatic update fails, a message is displayed in the n the Overview page of the Administrator Console to reflect this inconsistency. In this situation, you must reconfigure the system manually according to your required configurations (for configuration guidelines, refer to "Editing Servers." • Hostname of the SQL Server machine is changed — If the hostname of the SQL Server machine is changed, SQL Server must be re-configured to continue to function correctly. If your SQL Server is on the same machine as your WSM Server software and you have used the default WSM password (password@123), then WSM will automatically reconfigure the SQL Server. If for any reason this automatic update fails, or SQL Server is installed on a different machine than your WSM Server software, a message is displayed in the Overview page of the Administrator Console to reflect this inconsistency. Use the link provided in this message to open a page where you can enter a username and password and make this update manually. WSM will then reconfigure SQL Server. Login Error: You Encounter an Error While Trying to Access the WSM Login Page Problem: You are logging in to the Administrator Console and you encounter an error message: Solution: Use the following procedures in the order presented: 1. Ensure your WSM Administration Web Service is running (see "WSM Services: Verifying a Successful Installation by Viewing the WSM Services"). If you still encounter the error, go to Step 2. 2. Ensure that your database is correctly configured and running. If you still encounter the error, go to Step 3. 3. Open the registry at HKLM\System\CurrentControlSet\Services\WSMAdminService, add a multi-string key called DependOnService, set the value to MSSQLSERVER, and then reboot the Core Server. Network Device: Error Messages When Adding a Network Device from Active Directory Problem: You are trying to add a Network Device from the WSM Administrator Console and you encounter an error message. Solution: Use the following procedures in the order presented: 1. Ensure that the Network Device is created in Active Directory. 2. If you are using Active Directory integration without SSL, change the OS Authentication Service to run using a user account with Account Operator credentials. 3. Ensure that the Active Directory connection Status is Up. Installing and Building Your WSM Environment: Detailed Procedures 269 ODBC: Verifying that the ODBC is Operational and Configured Properly To allow communication between the WSM Server and the database, the installer creates and configures an Open Database Connectivity (ODBC) connection. Use the following guidelines to verify that the ODBC Data Source is configured properly: 1. Open the Control Panel, choose Administrative Tools, and click Data Sources (ODBC). 2. Click on the System DSN tab and click Configure to open the Microsoft SQL Server DSN Configuration dialog box. 3. In the Name box, enter StreamingDB; in the Which SQL Server do you want to connect to? box, enter the IP address of your SQL Server; and then click Next. 4. Select the With SQL Server authentication using a login ID and password entered by the user option (for the question: How should SQL Server verify the authenticity of the login ID?). 5. In the Login ID box, enter wsmdb; in the Password box, enter the password for wsmdb; then click Next. 6. Select the Change the Default Database To check box, select StreamingDB in the list, and then click Next. 7. Click Next to finish establishing the ODBC database connection. 8. Click Test Data Source, and then click Next to determine whether the ODBC connection has been set up correctly (you should see the Tests Completed Successfully message to know that the server installation setup is now complete). OS Image: Capturing an OS Image after Cancelling the Capture Process Problem: A user cancels the OS Image capture process and then cannot restart the capture process again. Solution: Reboot the Reference Device to the hard disk, and the start the OS Image capture process again as described in "Step 4-C: Capturing the OS Image from the Reference Device to the Core Server." OS Image: Re-configuring an OS Image If you want to copy or move an OS Image from one Core Server (for example, a lab environment) to another Core Server (for example, a production server), then that OS Image must first be re-configured. Similarly, if you want to change the current Active Directory integration mode (Enabled or Disabled), then that OS Image must be re-configured. TIP: The re-configuration procedures must be done on a client machine that has been booted from this OS Image. For procedures on adding an OS Image and assigning it to a server, refer to "Managing Operating Systems." To reconfigure an OS Image: 1. (This step is only required if you want to change the current Active Directory integration from Disabled to Enabled) Join the OS Image to the Domain you specified (when you added the OS Image using the Administrator Console) by using the Microsoft procedures for joining a Domain, reboot the system, and then continue with Step 2. 2. Login as a user with administrator privileges on the Reference Device and locate WSMClientPostConfig.exe (default location is C:\Program Files\Wyse\WSM\os). 270 Appendix F Figure 217 WSMClientPostConfig.exe 3. Double-click the WSMClientPostConfig.exe file to open the WSM Client Post Configuration window. 4. Use the following guidelines: • Depending on whether or not you want to integrate WSM with Active Directory, select or clear the Enable Active Directory Integration check box. • If you want to change the WSM Core Server settings, select the WSM Core Server settings check box and enter the new IP Address of the Core Server, and Port settings of the WSM OS Streaming Server. • Click OK. 5. Shut down the Reference Device. 6. Log in to the Administrator Console and edit the OS Image so that either the Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode) option is selected for Mode. For procedures on editing an OS Image, refer to "Editing OS Images." 7. If the intention of this re-configuration was to move the OS Image to a different Core Server, the OS Image can be now copied to that new Core Server, and added to the new Core Server using the Administration Console. For procedures on adding an OS Image to a server, refer to "Registering OS Images." After completing the procedures in this section the OS Image is ready to be used by multiple client machines. WSM Services: Verifying a Successful Installation by Viewing the WSM Services A successful installation can be verified by: 1. Clicking Start > Control Panel > Administrative Tools > Services, and viewing that the following services are running in the Services folder (to start, stop, or restart a service, right-click on the service file and select the option you want from the menu): • WSM Administration Web Service - Provides an administration interface for WSM (Administrator Console). Installing and Building Your WSM Environment: Detailed Procedures 271 • WSM Monitor - Monitors and controls WSM services on the machine to which it is loaded. • WSM Multicast Boot Service - Allows you to multi-cast the operating system information to devices when the system is setup to provide the OS Image in multi-cast mode. • WSM OS Authentication Service - Allows you to manually start and stop the authentication service for WSM. • WSM OS Streaming Service - Allows you to manually start and stop the streaming service for WSM. Figure 218 Services folder and WSM files 2. Logging in to the WSM Administrator Console, clicking the Servers tab to open the Servers page, clicking the Name link of the Core Server to open the Server Details page, and viewing that the following services are running (to start or stop services, click the appropriate Start, Stop, Start All, Stop All link available for the services): • OS Authentication Service - Allows you to manually start and stop the authentication service for WSM (same as WSM OS Authentication Service in the Services folder). • OS Streaming Service - Allows you to manually start and stop the streaming service for WSM (same as WSM OS Streaming Service in the Services folder). • Application Authentication Service - Manages subscriber licenses and metering application usage. • Application Streaming Service - Services end-user application client requests. • Monitor Service - Monitors and controls WSM services on the machine to which it is loaded. • Content Distribution Service - Allows you to synchronize the repositories of OS and Application images between the Core and remote servers. • Multicast Boot Service - Allows you to multi-cast the operating system information to devices when the system is setup to provide the OS Image in multi-cast mode. • DHCP Proxy Service - Allows you to prevent any unauthorized devices from connecting to the WSM system. It also prevents WSM from responding to other PXE requests from devices that are not part of the WSM system. • TFTP Service - Allows for thin client booting, data transfer, and so on. 272 Appendix F Figure 219 Core Server Details page - verifying services Uninstalling: How to Uninstall WSM Software To uninstall WSM software, use the Windows Add or Remove Programs tool (follow the Windows procedures for removing a program). TIP: Some uninstallations may require a reboot. Error Codes This section includes errors that you may encounter in a displayed message or log file. For information and help on installation, setup, conflicts, and general troubleshooting, refer to "Troubleshooting." Table 21 Error codes, symbolic representation, and error description Code Symbolic Representation Error Description 2 OTERROR_AI_BAD_XML_FORMAT Missing configuration data for the AutoInstall routine. 4 OTERROR_AI_SYSCHECK_REJECTED Failed AutoInstall system check because of existing MacID. 10 OTERROR_AI_ENVTEST_BAD_OS Unsupported Operating System version. Installing and Building Your WSM Environment: Detailed Procedures Table 21 273 Error codes, symbolic representation, and error description, Continued Code Symbolic Representation Error Description 15 OTERROR_AI_ENVTEST_NO_APPSERV Could not ping the Application server, probably because of an Application server outage or a firewall issue. 16 OTERROR_AI_ENVTEST_NO_SLIMSERV Could not ping the Application Authentication Server, probably because of a Application Authentication Server outage or a firewall issue. 26 OTERROR_AI_TERMINAL_SESSION_DET Client cannot be installed using Terminal Services. 3002 to 3008 OTERROR_EMS* Network communication time-out. 3024 to 3030 OTERROR_EMS_PROXY* Proxy issues with authentication or proxy gateway detection. 5006 OTERROR_SLIM_AT_ALREADY_HELD User attempted to run more sessions of an application than allowed (for information on application license management, refer to "Managing Application Images and Application Licenses." 5010 OTERROR_SLIM_USER_DISABLED Disabled or deleted user attempted to run an application session. 7003 OTERROR_APS_BAD_PAGE_NUMBER The page requested is not valid. Either the appset has been unloaded or published incorrectly. 8001 OTERROR_DB_CONNECT_FAILURE Servers could not connect to the database. Be sure that the ODBC and JDBC configurations are correct and the database is up. 10021 OTERROR_MONITOR_TERMINATED Monitor terminated. 100020 OTERROR_OUT_OF_MEMORY AutoInstall component cannot download the configuration XML, usually because of an old AutoInstall version. 274 Appendix F This page intentionally blank. G Users Guide This appendix is intended for users of the WSM Client system. It provides instructions on how to manage and use the applications that the administrator has made available. It also provides mobile users with detailed information about working offline (when not connected to a WSM server). Topics include: • "Logging In" • "Overview of the Client Applications Console" • "How to the Manage and Use Your Applications" • "Details About Working Offline and Online" • "Provisioning Your Mobile Thin Client" • "Using XNetClean in Windows 7 (Windows 7 Users Only)" Logging In On your initial use, you must use the Username and Password (provided to you by your administrator) to log in to the WSM Client. After your initial login, username and password credentials may or may not be required from you. TIP: Depending on the system settings configured by your administrator, the Login dialog box may not appear after your initial login. In such a case, the WSM Client Applications Console may appear automatically after thin client start, or you can open the console manually as described in "Overview of the Client Applications Console." Figure 220 Enter your Username and Password and click OK To log in: 1. Enter your Username. 2. Enter your Password. 3. Click OK. TIP: If you have trouble logging in, you can try clicking Start | Programs | WSM Client and using the Stop WSM Client and Start WSM Client options to stop and restart the WSM Client before attempting to log in again. 276 Appendix G After successfully logging in, the WSM Client icon and WSM Virtual Disc icon appear in the system tray located in the lower-right corner of the screen. TIP: Windows 7 users must use the Microsoft icons and notifications feature to display of the WSM Client icon and WSM Virtual Disc icon (see "Using the Microsoft Icons and Notifications Feature (Windows 7 Users Only)"). Figure 221 WSM Client icon (left) and WSM Virtual Disc icon (right) The color of the WSM Client icon depends on your WSM Client status in relation to the WSM Server: • No color: Your WSM Client is connected to the server. • Green: Your WSM Client is communicating with the server (for example, to fetch data or subscribe to an application). • Red: Your WSM Client is not connected to the server. • Yellow: Your WSM Client is trying to connect to the server. TIP: For troubleshooting purposes, your System Administrator may ask you to double-click the WSM Virtual Disc icon to read system settings in the Mobile Mode Status dialog box. 277 Users Guide Using the Microsoft Icons and Notifications Feature (Windows 7 Users Only) After successfully logging in, the WSM Client icon and WSM Virtual Disc icon can be shown (along with all hidden system tray icons) by clicking the Show hidden icons button in the system tray (located in the lower-right corner of the Windows 7 taskbar). Figure 222 Click the Show Hidden Icons button To have the icons always showing in the system tray: 1. Right-click the taskbar and select Properties to open the Taskbar and Start Menu Properties dialog box. Figure 223 Taskbar and Start Menu Properties 2. On the Taskbar tab, click Customize to open the Icons and Notifications dialog box. Figure 224 Icons and Notifications 3. Select the Show icon and notifications option for the WSM Client, and then click OK until you close all dialog boxes. 278 Appendix G Overview of the Client Applications Console Do either of the following to open the WSM Client Applications Console: • Double-click the WSM Client icon (located in the system tray). • Right-click the WSM Client icon and select Available Applications or Activated Applications from the menu. TIP: You can periodically check to see which new applications are available to you by using the WSM Client icon. The console provides three tabs to quickly show: • "Which Applications are Available to You" • "Which Applications You Can Use" • "What You Have Accomplished" Which Applications are Available to You The Unsubscribed Applications tab lists the applications that are available to you and to which you can subscribe (see "Subscribing to an Application"). Your administrator determines which applications are on this list. Figure 225 Unsubscribed Applications tab shows what is available Along with the list of applications, the Unsubscribed Applications tab shows you: • Status - The status of an application on this tab can be either New or Inactive. Applications with a status of New are applications that your administrator recently made available to you. Applications with a status of Inactive are applications that have been available for some time. • Offline Access - (Mobile Users Only) Indicates whether you can (Enabled) or cannot (Disabled) use the application when your WSM Client is not connected to a WSM Server (see "Details About Working Offline and Online"). • Account - Indicates the WSM account used to authenticate to the WSM system. • Group - Indicates the name of the WSM User Group to which your administrator assigned the license to use the application. 279 Users Guide Which Applications You Can Use The Subscribed Applications tab lists the applications to which you have subscribed and are able to use. It also allows you to unsubscribe from an application (see "Unsubscribing from an Application") and to enable or disable offline use of an application (see "Enabling Applications for Offline Use"). Figure 226 Subscribed Applications tab shows what you can use Along with the list of applications, the Subscribed Applications tab shows you: • Status - The status of an application on this tab can be either Ready or Not Accessible. Applications with a status of Ready are applications that you use now. Applications with a status of Not Accessible are applications that are not available at this time (for example, all user licenses for this application are currently being used). • Offline Access - (Mobile Users Only) Indicates whether you can (Enabled) or cannot (Disabled) use the application when your WSM Client is not connected to a WSM Server (see "Details About Working Offline and Online"). • Account - Indicates the WSM account used to authenticate to the WSM system. • Group - Indicates the name of the WSM User Group to which your administrator assigned the license to use the application. What You Have Accomplished The Status tab shows you the actions that you initiated within the console (such as subscribing or unsubscribing). TIP: The information on this tab shows you what you have already accomplished. For example, mobile users can use this tab to easily see if they have enabled an application for offline use before disconnecting from a WSM Server. 280 Appendix G How to the Manage and Use Your Applications Using the WSM Client Applications Console, you can quickly manage the applications to which you will subscribe, unsubscribe, and work with offline. TIP: Closing the WSM Client Applications Console only closes the window; the WSM Client and all subscribed applications that are running continue to run (the WSM Client icon also remains active in the system tray). Subscribing to an Application Before you can use an application, you must subscribe to it (“install” it). To subscribe to an application, select the application you want on the Unsubscribed Applications tab of the WSM Client Applications Console and click Subscribe. TIP: If you receive an error while subscribing, contact your administrator. Figure 227 Select an Unsubscribed Application and click Subscribe After subscribing to an application, you can open the application for use by clicking Start | Programs and selecting the application from the menu. TIP: If you are a mobile user, you can also enable subscribed applications for offline use (see "Enabling Applications for Offline Use"). 281 Users Guide Unsubscribing from an Application To unsubscribe from an application, select it on the Subscribed Applications tab of the WSM Client Applications Console (see Figure 226) and click Unsubscribe. Figure 228 Select a Subscribed Application and click Unsubscribe After unsubscribing from an application, the application is removed from the Start | Programs menu, and you cannot use the application until you subscribe to it again. TIP: Applications that are configured as mandatory by the administrator cannot be unsubscribed. If you try to unsubscribe to a mandatory application, a “cannot unsubscribe” message appears. Enabling Applications for Offline Use Before you can use an application when you are offline, you must subscribe to the application while you are online, and then enable the application for offline use while you are online. TIP: Only mobile users can enable applications for offline use. For information on working offline, refer to "Details About Working Offline and Online." After subscribing to the application as described in "Subscribing to an Application," you can enable the application for offline use by selecting the application on the Subscribed Applications tab of the WSM Client Applications Console and clicking Offline Enable. Warning Do not disconnect from the WSM Server while applications you are enabling for offline use are being downloaded. If you disconnect, the applications will not be installed correctly. After the application is successfully enabled and ready for offline use (the Offline Access for the application displays as Enabled), you can disconnect from the WSM Server and work offline as described in "Choosing to Work Offline or Online." TIP: When you are working offline, only the icons of applications enabled for offline use appear on your screen. If you cannot find the shortcut icon of an application, ensure that you enabled the application for offline use. 282 Appendix G Disabling Applications from Offline Use After you are finished using an application offline, you can disable the application from offline use while you are online. Disabling applications from offline use clears disk space on your thin client for other purposes. TIP: Only mobile users can disable applications from offline use. For information on working offline, refer to "Details About Working Offline and Online." After enabling an application for offline use as described in "Enabling Applications for Offline Use," you can disable the application from offline use by selecting the application on the Subscribed Applications tab of the WSM Client Applications Console and clicking Offline Disable. After the application is successfully disabled from offline use (the Offline Access for the application displays as Disabled), you can begin performing thin client tasks. Warning Do not disconnect from the WSM Server while applications you are disabling from offline use are being uploaded. If you disconnect, the applications will not be updated correctly. Details About Working Offline and Online Working offline means to work with applications without being connected to a WSM Server. Mobile users can use their applications offline as described in "Enabling Applications for Offline Use." Whether or not you can work offline depends on the system that your administrator configured for you: • Network mode: The thin client must be connected to the WSM Server in order to run applications. • Mobile mode: The thin client can run applications whether or not it is connected to a WSM Server. Applications can be fully downloaded to your thin client so you can use them offline. Knowing Whether You are Offline or Online Do either of the following: • Move your mouse pointer over the WSM Client icon and read the pop-up message that appears. The Running message indicates you are online; the Offline message indicates you are offline. • Check the WSM Client icon color. If the color of the icon in the system tray is red, you are offline; other colors indicate some kind of online state (see "Logging In"). • Right-click the WSM Client icon and look at the Work Offline option on the menu. If a check mark appears next to this option, you are offline; if no check mark appears next to this option, you are online and connected to a WSM Server. Users Guide 283 Choosing to Work Offline or Online Do either of the following: • Use the WSM Client Icon - Right-click the WSM Client icon and click Work Offline on the menu to toggle the option to the setting you want. Selecting it (so the check mark appears next to this option) disconnects you from the WSM Server so you can work offline; selecting it (so that the check mark is removed from this option) connects you to the server so you can work online. • Use the WSM Client Applications Console - Open the WSM Client Applications Console (see "Overview of the Client Applications Console") and click File | Work Offline to toggle the option to the setting you want. Selecting it (so the check mark appears beside this option) disconnects you from the WSM Server so you can work offline; selecting it (so that the check mark is removed from this option) connects you to the server so you can work online. Provisioning Your Mobile Thin Client WSM uses the term provisioning to describe how data (such as operating systems and applications) is sent from the WSM Server to mobile thin clients. System administrators can provision mobile thin clients in two ways: • Forced provisioning is enabled: Whenever the thin client boots, it connects to the WSM Server automatically and is provisioned with a new operating system (if a new operating system is available). • Forced provisioning is disabled: Provisioning is not automatic. To initiate provisioning manually, right-click the WSM Client icon in the system tray and select Provision Disk. NOTE: During manual provisioning you are given an option to cancel the provisioning and an option to save a partition before it is automatically deleted. Also note that up to three automatic reboots may happen during the provisioning process before a device actually boots to the provisioned disk. Caution Do not use your mobile thin client while it is being provisioned. You must wait until the “OS provisioning is complete” message appears before performing any thin client tasks. In addition, you must reboot your thin client and log in to the operating system so that the new operating system will take effect. 284 Appendix G Using XNetClean in Windows 7 (Windows 7 Users Only) In Windows 7, the WSM XNetClean utility (used to clean WSM Client information such as subscribed applications information, cached WSM data, temporary WSM files, and WSM user credentials) must be run using the Run as administrator option to ensure correct and complete XNetClean behavior. 1. Go to the folder that contains the WSM XNetClean utility (default is C:\Program Files\Wyse\WSM). Figure 229 Run as administrator option 2. Right-click the XNetClean shortcut icon and select Run as administrator. H Manually Publishing Applications This appendix Topics include: • "Publishing Steps (Manual)" • "WSM Publisher File Types" • "Setting Access Tokens" • "Viewing Appsets" • "Testing and Optimizing" • "Loading Appsets" • "Testing Appsets" • "Correcting Common Problems" • "Modifying and Updating Appsets" • "Case Studies xxxdo we have new case studies to place here" • "Details on Handling AppEvents" • "AppEvent Types" • "AppEvent Handlers" • "Handler Configuration" • "Configuration Macro" • "Environment Variables" • "Handling AppEvent Example" • "Publishing Instructions" Publishing Steps (Manual) IMPORTANT: Supported platforms include Windows XP and Windows 7. Step 1: Prepare the Publishing Environment Preparation is critical to trouble-free publishing. A properly configured publishing environment is one in which the recommended hardware and operating system that are dedicated to publishing and can be imaged and restored easily. Each application to be published must be installed on a platform that has no other applications installed other than perhaps a ghosting application which is used for imaging and restoration. To reduce the artifacts that can be introduced into the system, you should always use a “clean” system for publishing. For more information on preparation, refer to "Installation Requirements and Recommendations." Step 2: Run Publisher Express to Create the Appset After preparing the publishing environment, run the Publisher Express wizard to create your application set (appset). 1. Open the Publisher Express wizard (Start > All Programs > WSM Publisher > WSM Publisher). 286 Appendix H Figure 230 Publisher Express wizard - Step 1 2. Enter the Application Name and optional Application Description. Figure 231 Publisher Express wizard - Step 1 Advanced 3. (Optional) Advanced Options (click Advanced Options) include optional Activation Message, Vendor Name, and Author Name. 4. Click Next to create a first snapshot. This snapshot (default snapshot filename is 1.ss) is stored in %USERPROFILE%\My Packages\AppName. For example: In Windows XP, it is stored in C:\Documents and Settings\User\My Documents\My Packages\AppName. In Windows 7, it is stored in C:\Users\User\Documents\My Packages\AppName. TIP: This snapshot of the system reflects the system state before the application is installed. This snapshot will be compared with a second snapshot of the system after the application has been installed. The differences between the snapshots are used to determine the files, configuration, and registry information that is needed to stream the application to the client. The first snapshot is saved as the pre-installation snapshot file. 5. Install the application to the folder path that is recommended by the Publisher Express wizard (shown in the Installation Info area). This folder was created when you installed/ started Publisher. TIP: Publisher creates the destination folder for the application which you can use with the installer. Publisher at startup creates a folder named C:\WSM_O. This folder is mounted as the next available drive letter. If such a drive letter is already mounted due to an earlier appset publishing process, it will be used again instead of mounting a new Manually Publishing Applications 287 drive letter. In the following figure, the free drive letter happens to be E:. Note on auto-mount feature: There are certain installers which use MSI service for installation. Such installers fail to install applications to/from a virtual disk. Publisher Express mounts such a virtual disk as the next available drive letter. Therefore, some application installers work while others fail. For the sake of consistency, the current auto-mount feature is disabled. As a result, Publisher always expects you to have an additional drive where the application is installed and that path is specified as the installation path in Publisher Express. 6. After you install the application to the folder, return to the Publisher Express wizard, be sure the drive letter and folder of the Destination Installation Folder is correct, and then click Done. Figure 232 Publisher Express wizard - Step 2 7. Click Next to create a second snapshot, build, and appset. All files (the second snapshot file, build file, and appset file) are stored at same location where the first snapshot was stored (for example, %USERPROFILE%\My Packages\AppName). 8. This snapshot (default snapshot filename is 1.ss) is stored in %USERPROFILE%\My Packages\AppName. For example: In Windows XP, it is stored in C:\Documents and Settings\User\My Documents\My Packages\AppName. In Windows 7, it is stored in C:\Users\User\Documents\My Packages\AppName. TIP: This snapshot of the system reflects the system state before the application is installed. This snapshot will be compared with a second snapshot of the system after the application has been installed. The differences between the snapshots are used to determine the files, configuration, and registry information that is needed to stream the application to the client. The first snapshot is saved as the pre-installation snapshot file. 9. Upon successful appset creation, the Publisher Express wizard displays the path to the created appset and directs you to copy it to the StreamingDir\ appimages folder on the WSM server. TIP: Upon appset creation failure, the Publisher Express wizard displays the path to the error logfile. 288 Appendix H Figure 233 Publisher Express wizard - Step 3 10.Click Finish. The Show Application Set in Folder check box is selected by default. It will launch Windows Explorer and navigates to the location of the appset. Intermediate files (1.ss, 2.ss, and AppName.aeb) are deleted by default at the end of publishing process. IMPORTANT: The appset created by Publisher Express will have following default configuration: • Compression enabled using LZHL • No Encryption • No Prefetching • No CustomApp Event DLL set • Supported Operating Systems include only the current OS on which the appset is published • Shortcuts are moved to point to O: • No Reboot required after appset subscribe • Target mount path on the client is O:\AppName Step 3: Copy the Final Appset (AES File) to WSM Servers A broad test of the standard features in the application can be performed. For example, all menu options can be tested to verify that all parts of the application are installed and captured. If the application does not work as expected, some part of the target application installation may not have been completed. For example, you can go back to the application installation and perform modifications, generate a new appset, and test again. After you determine that the appset is satisfactory and the application functions as intended, you can load the appset (AES file) to the WSM servers (StreamingDir\appimages directory) for WSM use. TIP: The Project Wizard is available to guide you through some of the steps. It covers all of steps 2 through 6, and part of step 7 (the macro-based cleanup section). You also have the option of performing the steps individually. You can obtain a quick online reference of these steps by choosing Help | Publishing Steps (selecting the Publishing Steps command from the Help menu). A pane with a yellow background appears with the various steps listed, as shown in Figure 234: Manually Publishing Applications Figure 234 289 Publishing steps - docked If you prefer for these steps to be displayed in a floating window, click on one of the edges of the pane and drag it out to undock it. You can dock it back by clicking on the floating window’s title bar and dragging it to one of the main window’s edges. Figure 235 Publishing steps - undocked Step 1: Prepare the Publishing Environment Preparation is critical to trouble-free publishing. A properly configured publishing environment is one in which the recommended hardware and operating system that are dedicated to publishing and can be imaged and restored easily. Each application to be published must be installed on a platform that has no other applications installed other than perhaps a ghosting application which is used for imaging and restoration. To reduce the artifacts that can be introduced into the system, you should always use a “clean” system for publishing. For more information on preparation, refer to "Installation Requirements and Recommendations." Step 2: Create an Installation Folder After preparing the publishing environment, you create an installation folder for the target application. This folder must be created before you take the first snapshot of the system. For more information on this step, refer to "Creating Build Files." 290 Appendix H Step 3: Take a Pre-installation System Snapshot After the system is clean, you take the first snapshot. This snapshot of the system reflects the system state before the application is installed. This snapshot will be compared with a second snapshot of the system after the application has been installed. The differences between the snapshots are used to determine the files, configuration, and registry information that is needed to stream the application to the client. The first snapshot is saved as the pre-installation snapshot file. For more information on this step, refer to "Creating Build Files." Step 4: Install the Application and Run it Once After you create the first snapshot, you install the target application. Many application installers have a simple install mode (usually the default) and a custom install mode. To publish, however, it is best to use the custom install feature and install all the components. Because the components are all on-demand, it makes sense to publish everything possible for the target application. After you install the application, you run it to verify that all components are properly installed, and then you test all application menu options and features. For more information on this step, refer to "Creating Build Files." Step 5: Take a Post-installation System Snapshot After the target application has been installed and run, it is time for the post-installation snapshot. This snapshot is taken in exactly the same fashion as the first snapshot; however, the second snapshot shows the changes in the system due to the installation, which is all the files and configuration setup required for the target application. If target application or system changes are required, you would do them before the second snapshot is taken. There is no limit to the number of snapshots that you can make. You can make changes at any time and take another snapshot. To publish a new application, however, you must set up a new environment in place of the existing one. For more information on this step, refer to "Creating Build Files." Step 6: Create the Build File from the Snapshots The pre-installation snapshot is compared to the post-installation snapshot file to determine what has changed on the system after the target application was installed. This difference ideally contains only the target application. However, during the installation it is possible to pick up unwanted artifacts. The output from the comparison of the snapshots is the build file. The build file contains all of the files and Windows registry entry differences between the two system states. Most if not all of the files and entries are specific to the target application; however, sometimes artifacts are introduced into the process. Artifacts are any system information not related to the target application. For example, if you browsed the Internet after installing the target application, temporary files would be created on your system and would likely appear in the build file. Some artifacts can cause problems with the published application. For more information on this step, refer to "Creating Build Files." Step 7: Clean-up the Build File The most involved part of publishing is cleaning the build file and identifying and removing artifacts. This may seem complex at first, but requires only a simple understanding of how the Windows file system and registry work. After you have published a few applications, you will learn to quickly recognize patterns in the build file and identify and remove artifacts. Keep in mind that cleaning up the build file can be an iterative process that requires testing between each successive build file. You can open the build file as necessary to modify it. Manually Publishing Applications 291 As a learning aid, two case studies have been provided for your review. Macros are available to speed up the clean-up process. Macros contain pre-recorded actions for cleaning the build file. In fact, in many cases the macros supplied with WSM Publisher are adequate to clean the build file. For more information on this step, refer to "Modifying Build Files." Step 8: Create the Appset File After the build file is clean, you can generate the application set, called the appset. During this process, you can specify the target operating systems. Several options are available for optimizing the appset (such as compression, encryption, and the inclusion of a prefetch file when recreating the appset for republishing), but you can skip these the first time around and then come back to them after testing the appset to optimize it. For more information on this step, refer to "Generating Appsets." Step 9: Test the Appset The appset is loaded onto a server for testing. Testing does not need to be rigorous functional testing, but rather a broad test of the standard features in the application. For example, all menu options should be tested to verify that all parts of the application are installed and captured. If the application does not work as expected, some part of the target application installation or cleaning of the build file was not completed. You need to go back to the build file and perform additional cleaning or modifications, generate a new appset, and test again. For more information on this step, refer to "Testing and Optimizing." Step 10: Create the Final Optimized Appset After you determine that the appset is satisfactory and the application functions as intended, you can optimize the appset with compression, encryption, and the inclusion of a specific prefetch file when recreating the appset for republishing. Once optimized, the appset is complete and can be loaded on the WSM servers for user subscriptions. For more information on this step, refer to "Testing and Optimizing." 292 Appendix H WSM Publisher File Types WSM Publisher uses various types of files that are briefly described in Table 22 along with their associated file extensions. Double-clicking on any of these files from within Windows Explorer opens the file in WSM Publisher or an appropriate editor (depending on the file type). More details on each file type are given in the sections where the file type is primarily used. . Table 22 WSM Publisher File Types Ext. Description Double-click action .aeb WSM Publisher Build Contains a list of files and registry entries changes that are needed to generate an appset. Opens build in WSM Publisher .aec WSM Publisher Configuration Contains configuration information used to build an appset (for example, installation folder, target OS, etc.). Opens configuration file in Notepad .aem WSM Publisher Macro Stores recorded actions that can be replayed on an application build. Opens macro in WordPad .aep WSM Publisher Project Keeps track of state and configuration information used by the Project Wizard. Opens project in WSM Publisher .aes WSM Application Set Contains a repackaged version of an application that is ready for on-demand delivery to WSM clients via a WSM server. Opens appset in WSM Publisher .apm WSM Publisher Macro Log Keeps a running log of all actions performed during the editing of an application build. Opens macro in WordPad .ss WSM Publisher Snapshot Stores an image of the current state of a machine’s files and registry entries. Opens WSM Publisher (however, the contents are not viewable) Manually Publishing Applications 293 Setting Access Tokens Access tokens are used to track usage on the client system and to apply security to files. With the access tokens enabled, the user cannot update, copy, or delete the file when the application is activated on the client machine. You can apply access tokens to executable files, libraries, or sensitive materials that should not be copied. To apply access tokens on files, use the Toggle Access Token command and select from the following settings: • Access token required - All selected files will have access tokens enabled. • Based on name (.EXEs only) - By selecting access tokens required and based on names, this applies access tokens only to executable files (.exe) that are in the set of selected files. You can easily check whether an access token has been set for a file by looking in the right pane under the Access Token Requested column. To set access tokens: 1. Locate a file for which an access token should be set. Follow these steps to use the Publisher’s Find feature to locate the file: a. From the Edit menu, select Find. b. In the Find field, enter the appropriate file extension (for example, “.exe”). Figure 236 Find c. Clear the Registry Keys and Folders check box and make sure the Registry Values and Files is selected, and then click Find Next. From this point on, you can simply press the F3 key to go to the next occurrence of the search string. 2. Right-click on the file and select Toggle Access Token (if you wish to set an access token for all files or executables under a given folder, then right-click on the folder instead and select Toggle Access Token) to open the Toggle Access Token For Files dialog box. Figure 237 Toggle Access Token For Files 294 Appendix H 3. Select the Access token required check box. 4. If the item is a folder, you can select the Recursive check box to have the change apply recursively to all files and subfolders under the selected folder. In this case, you should select the Based on name (.EXE only) check box if you want access tokens to be set only for .EXE files. 5. Click OK for the change to take effect. 6. Repeat the above steps for all files or folders for which an access token should be set. TIP: If you have not saved the build file since the last changes made to it, an error message is displayed. Save the file and try again. If you have not set any access tokens, a warning is displayed and you are asked whether or not you wish to continue. In this case, select No, set appropriate access tokens, and try again. 7. On the File menu, select Save Build to save the changes you made to the build file. Manually Publishing Applications 295 Viewing Appsets There may be times when you need to view the contents of an appset for troubleshooting purposes, or to extract a file from it. WSM Publisher allows you to open an appset and view its contents as described in the following steps. Viewing the Contents of an Appset To view the contents of an appset: 1. From the File menu, select Open Application Set. 2. Select the appset that you wish to view and click Open. 3. In the left pane, select the section of the appset that you wish to view, and its contents will be shown in the right pane. Figure 238 Appset Viewer Extracting a File from an Appset To extract a file from an appset: 1. From the File menu, select Open Application Set. 2. Select the appset that you wish to view and click Open. 3. In the left pane, click on Files. The list of all files contained in the appset will appear in the right pane. 4. Right-click on the file you wish to extract and select Extract File from the menu. 5. Navigate to the location where you wish to save the file and enter a name for it or keep the default name. 6. Click Save. 296 Appendix H Testing and Optimizing After you have created an appset you can load it on an WSM server for testing and optimization. The appset is subscribed to from a client and then tested for complete delivery of contents and application functions. After eliminating any problems, and republishing if necessary, you can optimize the appset (for additional streaming efficiency) with compression, encryption, and the inclusion of a specific prefetch file when recreating the appset for republishing. TIP: It is recommended that you avoid testing on a publishing machine. Loading Appsets This section contains information on copying an appset to the depot folder on a server machine. To load an appset: 1. Locate the AES file for the newly created appset file. The location was specified when you created the installation folder. 2. Locate the application server folder that was created during the installation of the Application Server. 3. Copy the AES file into the folder (for example, depot) created during installation of the application server. 4. Open a Web browser and go to the URL for the Application Server to open the Login page. 5. Log in with the administrator user ID and password established during the application server installation. 6. Use the procedures in the "Registering Application Images" (to Register an Application Image to the system for streaming), and then assign it to a server and a user. You can now test the application. TIP: For more information on WSM Web page settings, see "WSM Web." Testing Appsets Testing is required to make sure that all features work in the published appset. You should complete all testing before you create the final appset. After the appset is loaded on a server, you can activate it from a client to test the features and functions of the application. Do not use the publishing machine for testing. Keep in mind that the prime objective of testing the application and its features is to verify that they are included in the appset package. After you complete testing and have confirmed that the published application functions completely, you can leave the appset on the server for streaming, and also install it on additional servers as needed. Refer to the Administrators Guide: Wyse WSMTM for further details. Testing comprises delivery testing and package testing. Delivery testing verifies that the appset is properly installed on the target system. Package testing is done to verify that all features of the target application are included in the appset. You should perform these tests on all of the target operating systems and service pack versions. Manually Publishing Applications 297 Delivery Testing To validate an appset for a complete delivery, activate the appset and, after activation has been completed, begin the testing as described in "Application Testing." An improperly published appset may contain artifacts (for example, system drivers, broken system files) that can cause a target system to misbehave. Use the following guidelines: • Make sure that the application desktop and Start Menu icons appear in the appropriate locations. • Make sure that the file associations of the existing application and the appset application work by following these guidelines: • Double-click a file for the appset to load. • Double-click a .txt file for Notepad to open. • From a command line, start Notepad to verify that the Windows shell command path functions. • Start Internet Explorer and make sure that the Windows shell does not cause Installer pop-ups to occur and that Web browsing is functional. • Start the appset application and measure the startup time. • Use Wordpad to make sure that all system fonts are working properly. Application Testing To verify that the appset contains all the necessary components of the target application, start the appset and do the following to test the application: 1. Make sure that the application started properly. 2. Click each menu item of the application to make sure that they operate properly. 3. If the application supports printing, print a document. 4. Use the application as a general user (for example, create a document and save it). 5. Exit the application to verify proper shutdown. 298 Appendix H Correcting Common Problems When you test an appset and encounter errors, you most likely need to republish. However, you need to know what to fix before republishing. The following sections offer tips and guidelines for correcting typical problems. Microsoft Icons do not Appear Some of the newer MSI-installation based applications use special Windows Installer shortcuts. When you install these applications to publish, disable the shortcuts to a regular .lnk file. Use the command: msiexec.exe /i "*.msi" DISABLEADVTSHORTCUTS=1 to disable them. However, if you installed and published the application without running the previous command, there will be some unwanted behavior. When you subscribe to an application that has installer shortcuts, the shortcuts appear as unknown files in the start menu (sometimes, they will not appear at all). If you click on any of them, you will more than likely get an MSI pop-up. There are two solutions to this problem: • Run the msiexec command upon installation if you're just beginning to publish. • However, if the appset has already been published, you must edit the program shortcuts manually. Create new shortcuts with the same names as the old ones and set them to target their corresponding .exe files. This can be tedious, but it is much quicker than re-installing the application using the msiexec command. File Associations not Set Properly File associations for some applications sometimes do not get set properly when you test an appset. One example would be creating a .doc file from a published version of MS Word and receiving an error message as a result. To solve this problem, go back to the publishing image, create the appropriate file type from the application being published (for example, Word), and then double-click that file to open the application. Take another snapshot, create a build, and republish. Miscellaneous Errors Occasionally there are errors that can be difficult to track down. If you have the client testing machine available, you can use the Event Viewer to view a detailed description of any system/application errors that occurred during testing. You can also check the client machine for the suspected missing files to verify if they are included in the appset. Manually Publishing Applications 299 Modifying and Updating Appsets There are many reasons why you may want to make changes to an existing appset, including: • Modifying the list of supported operating systems • Adding, removing, or modifying AppEvent DLLs • Adding, removing, or modifying files and registry entries • Modifying appset configuration parameters Some of these changes require that an application be republished. Because republishing can be time-consuming, WSM Publisher offers the ability to make certain changes without the need to republish the application (the first three items listed do not require republishing). Modifying the List of Supported Operating Systems An appset may be initially marked to run on the OS of the publishing system. Later, testing may reveal that the appset may also run properly on other operating systems, or other OS/ SP combinations. Conversely, testing may reveal that the appset does not run properly on an OS for which it was marked. In such cases, you need to modify the target operating systems that are marked for the appset. To modify the supported operating systems: 1. From the Tools menu, select Update OS Support. The Supported Operating Systems dialog appears. 2. Click Browse, navigate to the location of the appset that you want to modify, and double-click it. The content type of the selected appset will be shown as Unicode, Non-unicode, or Unknown. 3. Select the supported OS/SP combinations as described in "Step 2: Selecting Operating Systems." 4. Click Update to initiate the update process. Adding, Removing, or Modifying AppEvent DLLs After publishing an application, appset testing may reveal some problems that cannot be resolved by simply changing the build file. In this case, you may have to use an AppEvent DLL to perform special actions. You may also wish to change or remove an existing AppEvent DLL. To add, change, or remove an AppEvent DLL: 1. From the Tools menu, select Update Custom DLL. The Update Custom DLL in Application Set File dialog appears. 2. Do one of the following: • If you want to remove an existing AppEvent DLL, select the Remove Custom DLL Only option. • If you want to add new AppEvent DLL or change an existing one, select the Custom DLL File option and then specify the path of the new AppEvent DLL file in the field. 300 Appendix H 3. Specify the path of the appset file that you want to update in the Target Application Set File field. 4. Make sure that the New Application Set ID option is selected. If you want to change the ID that is automatically generated for you, click Generate. CAUTION: You should always generate a new ID for an appset, even if you intend to overwrite the old appset on the application server. Although you could use the same appset ID if you first remove the old appset from the application server, doing so would invalidate all subscriptions associated with the old appset! So, if your intent is to upgrade existing users to the new appset, you should use the upgrade process documented in the Administrators Guide: Wyse WSMTM instead. One situation where you may actually want to use the same appset ID is for testing purposes only, but never for a released appset. 5. Click Start to initiate the update process. Details on Handling AppEvents To convert a locally installed application into an application capable of being streamed on a network, the Publisher takes a snapshot of the states of the installed application and records them in the appset file. When an application is activated by the user, those states are re-created on the user’s system. Sometimes, however, the re-created static states of the application do not allow it to run. In these cases, it may be necessary to adjust those states or the run-time environment before, during, or after activation, to allow the application to run properly. In other words, it may be necessary to automate certain actions that cannot be captured in an appset. For example, it may be necessary to configure all the plug-ins that the application provides for office suites and browser applications. It may also be necessary to configure virtual printers that the application requires. Another example is a video game that runs a video performance application during the installation process to configure the game parameters. It may also be necessary to start a program in the background that should always be running. To allow such adjustments to be made dynamically, for example upon activation of the application, WSM Client provides an event-driven framework that can be used to trigger the execution of custom code in response to a variety of events called AppEvents. The custom code that is used to handle a particular AppEvent is called an AppEvent handler. These AppEvent handlers are executed by a special dynamically linked library (DLL) called Custom AppEvent DLL (CAED) that must be included in the appset during the publishing process. The CAED must be configured to execute the appropriate AppEvent handler for a given AppEvent. This can be done either through a provided GUI-based Publisher macro or directly in the user’s system registry. The CAED does not contain the AppEvent handlers. Instead, this custom code is implemented in a separate module that the CAED can call. This provides great flexibility to customers because it allows them to develop AppEvent handlers in their programming language of choice, thereby leveraging available programming skills and perhaps even existing code. Manually Publishing Applications 301 AppEvent Types Table 23 lists the various types of AppEvents that WSM Client sends out to the CAED and indicates when each AppEvent is sent out. . Table 23 AppEvents and descriptions AppEvent Description ClientStartup Sent as the client is starting up. ClientExit Sent as the client is shutting down. PreInstall Sent immediately prior to an appset being activated. PostInstall Sent immediately after an appset has been activated. PostAppStart Sent after the application starts (if an access token has been set for the executable). PostAppExit Sent after the application exits (if an access token has been set for the executable). PreUninstall Sent immediately prior to an appset being deactivated. PostUninstall Sent immediately after an appset has been deactivated. AppEvent Handlers When one of the above events occurs, the CAED will execute the corresponding event handler, which is configured by the customer either during the publishing process or directly on the client machine. Event handlers may be configured with a command line (executable and parameters), working directory and blocking time-out (how long to wait for the handler to complete before returning control back to the client), and these settings are stored in the registry. A WSM Publisher macro is available to aid in the configuration of event handlers by setting-up the registry appropriately. For most AppEvents, it is recommended that the executables and registry settings associated with the AppEvent handlers be included in the appset during the publishing process. In this way, they become automatically available once the appset has been activated, and up until deactivation takes place. This approach will work fine for the following events: ClientStartup, ClientExit, PostInstall, PostAppStart, PostAppExit, PreUninstall. However, it will not work for the PreInstall and PostUninstall events. Indeed, because these two events are fired at a time when the appset is not yet, or is no longer, activated, the executables and configuration settings associated with their handlers will not be available if located in the appset. To handle these two events, the executables and registry settings must be made available on the client machine by some other means prior to application activation, and should still be available immediately after deactivation. Note that even if a handler’s executable is local to the user’s machine, the event handling mechanism will not work unless the handler’s configuration settings are also present on the user’s machine at the time of activation because, without these settings, there would be no way for the CAED to determine what handler to which to dispatch the event. Also note that only one handler may be configured per AppEvent. Additionally, AppEvent handlers have no control over client actions. So, for example, it would not be possible for a handler to prevent an appset from being started, activated, or deactivated. 302 Appendix H Handler Configuration Handlers are configured in the registry in a structure that is simple and makes it easy to customize the various handler properties. The basic registry structure is shown in the following figure and is located directly under registry key HKEY_CURRENT_USER\Software\Wyse\Wyse WSM: Figure 239 Registry Structure This diagram depicts the hierarchy of registry keys that are used by the Custom AppEvent framework. Each appset that has been configured with Custom AppEvent handlers will have a key under the CustomAppEvent root key named according to the unique application ID (UAID), which is a GUID. Each appset can have one handler for each of the defined events, as shown in Figure 239. Each handler key will have several values corresponding to the configuration settings mentioned earlier (see Table 24). 303 Manually Publishing Applications . Table 24 Value names and types - requirements and descriptions Value Name Type Required or Optional Description LaunchCmd REG_SZ Required Command line to execute. The string must include the module executable and, optionally, command line arguments. The module name must be enclosed in double quotes if it contains spaces to indicate where the file name ends and the arguments begin. WorkingDir REG_SZ Optional Initial drive and directory for the handler. The string must be a full path that includes a drive letter. If omitted, no working directory may be assumed. Blocking REG_DWORD Optional Amount of time (in seconds) to wait for the process to complete. The maximum possible value is 5 minutes (300 seconds). If omitted or if set to zero, no blocking is performed. As indicated earlier, it is possible to configure handlers to execute from files that are included within the appset itself. Paths for special folders may be specified using their symbolic representation instead of the actual folder path. For example: [OT_APPDIR] = O:\{appid} [OT_INSTALLDIR] = O:\{appid}\INSTALLDIR [OT_SYSTEMDRIVE] = C: [OT_WINDOWS] = C:\Windows [OT_SYSTEM] = C:\Windows\System32\ TIP: WSM Publisher will automatically translate instances of the installation folder path to the appropriate symbolic representation (that is, [OT_INSTALLDIR]). Configuration Macro To assist publishers in configuring handlers during the publishing process, a Publisher macro (CustomAppEvent.aem) is provided that prompts the user for the information necessary to configure the handler registry keys. The publisher is initially required to provide the application ID for the appset being published. The publisher is then asked to provide values for each handler as defined in the previous section. All data supplied by the publisher is added to the registry keys in the appset and are subsequently created on the client machine when appsets are activated. 304 Appendix H Environment Variables It is sometimes necessary for a handler to have some information about the running application or the current user in order to accomplish its task. The CAED provides such information to every handler that it calls through environment variables (see Table 25). . Table 25 Environment Variable names and descriptions Environment Variable Name Description/Comments STREAMING_INSTALLDIR Folder where the application is installed. STREAMING_USERNAME User name of the currently logged on user. STREAMING_USERDOMAIN Domain under which the current user is logged. STREAMING_UAID Application ID – a GUID that uniquely identifies the application to WSM. STREAMING_EVENT Name of the AppEvent. See "AppEvent Types." TIP: Handlers are executed as the current user, and in their own process. Handling AppEvent Example This section presents a very basic example to illustrate the handling of an AppEvent. Suppose that we want to have end users log what they intend to do every time they run a certain WSM-based application and that the log entries must be made in a text file named with their user name. One way to accomplish this is to set the LaunchCmd registry value to notepad.exe “C:\%STREAMING_USERNAME%.txt” in the PostAppStart key located under our application’s key (that is, the one named with the corresponding UAID). This will now cause the desired log file to open in Notepad every time our application starts. If the file does not exist, Notepad will create it after asking the user for confirmation. Of course, in reality there are more appropriate tools to accomplish the proposed goal, but this example was based on Notepad for the sake of simplicity, and because it is easy enough to try out. Manually Publishing Applications 305 Publishing Instructions This sections provides instructions that one must follow, beyond the normal publishing steps, in order to use the CAED. Including Handler Executables in the Appset To include handler executables in the appset, simply insert the corresponding files in the application build before creating the appset with the Insert File command. TIP: If you want to handle the PreInstall or PostUninstall events, it will be necessary to make the executables available on the client machines independently of the appset before the latter is activated. Setting-up the Registry Configuration To configure the handler settings in the registry, you should run the CustomAppEvent.aem macro after the build has been created, and before you create the appset. Alternatively, you may enter the appropriate registry settings manually. Adding the CAED to the Appset To add the CAED to the appset, be sure to specify the CustomAppEvent.dll file in the AppEvent DLL field in the Advanced page of the Appset Creation Wizard. 306 Appendix H This page intentionally blank. I Cloud Desktop Client Configuration and Troubleshooting This appendix includes information on Dell Wyse Cloud Desktop client configuration and troubleshooting. Dell Wyse Cloud Desktop is a feature that allows supported Dell OptiPlex and Precision desktop systems to directly boot to a WSM environment without the use of PXE. Topics include: • "Configuration" • "Cloud Desktop Troubleshooting" Configuration Cloud Desktop systems are shipped from Dell and configured to automatically boot to WSM. However, there are options that can be configured via the system BIOS setup screen or from the WSM Administrator console that allow further configuration. Cloud Desktop BIOS Setup Screen Configuration To enter the BIOS setup screen on your Dell Wyse Cloud Desktop system, press and hold the F2 key when you see the Dell splash screen. To enable the Cloud Desktop feature: 1. Under General > Boot Sequence, the Onboard NIC option should be selected as the first boot device in the Boot Sequence area, and the Legacy option should be selected in the Boot List Option area. Figure 240 Boot Sequence 308 Appendix I 2. Under System Configuration > Integrated NIC, select the Enabled w/Cloud Desktop option in the Integrated NIC area. Figure 241 Integrated NIC 3. Under Cloud Desktop > Server Lookup Method, select the Server Lookup Method option (to specify how the Cloud Desktop software will look up server addresses) in the Server Lookup area. Figure 242 Server Lookup Method Cloud Desktop Client Configuration and Troubleshooting 309 Table 27 lists the various desktop configuration options and their descriptions. . Table 26 Desktop configuration options and descriptions Desktop Configuration Option Description Server Lookup Method The factory default setting is DNS Specifies how the Cloud Desktop software will look up server addresses. DNS — Cloud Desktop software will obtain the server IP address using the Domain Name System (DNS) protocol. Static IP — Cloud Desktop software will use static server IP addresses Server IP Address The factory default setting is 255.255.255.255 Specifies the primary static IP address of the Cloud Desktop Server with which the client software communicates. Server Port The factory default setting is 06910 Specifies the primary IP port of the Cloud Desktop server with which the client software communicates. Client Address Method The factory default setting is DHCP Specifies how the client will obtain its IP address. DHCP — Client will obtain the IP address using the Dynamic Host Configuration Protocol (DHCP). Static IP — Client will use a static IP address. Client IP Address The factory default setting is 255.255.255.255 Specifies the static IP address of the client. Client Subnet Mask The factory default setting is 255.255.255.255 Specifies the subnet mask of the client. Client Gateway The factory default setting is 255.255.255.255 Specifies the gateway of the client. Advanced Turns on Verbose Mode for advanced debugging. Server Configuration To set up your WSM environment to allow Cloud Desktop configured systems to boot without further configuration, do the following: 1. Make use of DHCP for client IP address assignment. 2. Make use of DNS for domain name lookup. 3. Register your WSM server on your domain with a name of CDServer. 310 Appendix I Cloud Desktop Troubleshooting Table 27 lists conditions, various error messages that may be seen on the Cloud Desktop client system during boot for those conditions, and recommended actions to take for troubleshooting purposes. . Table 27 Conditions, error messages, and actions Condition Error Message Action Network Cable is disconnected "Initializing UNDI…UNDI_INITIALIZE failed: 0061 Media Test failure, check cable Press ESC key to abort" Check that the network cable is properly connected to the system and that link lights are present. DHCP server not responding "Requesting DHCP IP. Please wait… DHCP ERROR - Timeout Press ESC key to abort" Check that the DHCP server is working properly. DNS server not responding "Cloud Desktop Server name: WSMServer Sending domain name query to server …" "Cannot resolve IP address in DNS server. Please check your DNS server and setting Press ESC key to abort" Check that the DNS server is working properly. WSM Server not found from DNS lookup "Cannot resolve IP address in DNS server. Please check your DNS server and setting Press ESC key to abort" Check that the DNS server is working properly and that the WSM server is registered with the domain. The default WSM server domain lookup name is CDServer. WSM Server is not responding "Connecting to the Cloud Desktop services. Please wait… Authentication server: <server ip>:<server port>" "Timeout communicating with Cloud Desktop server, trying next server… No reachable Cloud Desktop server Press ESC key to abort" Check that the WSM server can be reached via ping. Check that the WSM server authentication service is started. WSM bootstrap cannot be downloaded "Loading SROM BIN from <Server ip>:<Server port>…" "…FAIL Press ESC key to abort" Check that the WSM server can be reached via ping. Check that the WSM server services are started. 311 Tables 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Routine Site Tasks 13 Routine Site Group Tasks - Site Groups page 22 Routine Site Template Tasks - Site Template page 26 Routine Operating System Management Tasks 34 Routine Application Management Tasks 44 Routine Server Management Tasks 68 Routine Server Group Management Tasks 73 Routine Device Management Tasks 81 Routine Device Group Management Tasks 90 Routine Device Template Tasks - Device Templates page 101 Routine User Tasks - Users page 111 Routine User Group Tasks - User Groups page 117 Routine Active Directory Domain Tasks - Active Directory Domains page Routine Deployment Tasks 172 Server Hardware Requirements 225 Server Software Requirements 226 DHCP server options 228 Boot-up process in PXE and non-PXE environments 258 Requirements for PXE and non-PXE boot-up 259 Features of PXE and non-PXE boot-up 259 Error codes, symbolic representation, and error description 272 WSM Publisher File Types 292 AppEvents and descriptions 301 Value names and types - requirements and descriptions 303 Environment Variable names and descriptions 304 Desktop configuration options and descriptions 309 Conditions, error messages, and actions 310 147 Administrators Guide Wyse WSMTM Release 5.0.1 Issue: 053013 Written and published by: Wyse Technology LLC, May 2013 Created using FrameMaker® and Acrobat®