Administrators Guide. Wyse WSM Release Issue: PN: Rev. E IMPORTANT: This is a living document with ongoing changes

Transcription

1 Administrators Guide Wyse WSM Release Issue: PN: Rev. E IMPORTANT: This is a living document with ongoing changes

2 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 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 Ordering Information For availability, pricing, and ordering information in the United States and Canada, call GET-WYSE ( ) or visit us at wyse.com. In all other countries, contact your sales representative.

3 Contents 1 Introduction 1 About this Guide 2 Finding the Information You Need in this Guide 2 Wyse Technical Support 2 Related Documentation and Services 2 Wyse Online Community 2 2 How to Build Your WSM Environment 3 Standard or Advanced: Which WSM Environment is for You? 3 Building a Standard WSM Environment 3 Building an Advanced WSM Environment 4 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

4 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 73 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

5 Contents v 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 106 Adding an OS Image to a Device Template 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 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

6 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 151 Managing Virtual Centers Reports 157 Overview of the Reports Page 157 Transaction History 159 Alerts History 160 Client Report 160 License Usage Report 161 Standard Usage Report 161 Activation Report 162 Subscription Report 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 180 Volatile and Persistent Cache Mode 181 Setup for Load Balancing 181 C Updating OS Images and Application Images 183 Updating an OS Image 183 Updating an Application Image 187 Preparing an Application Image Update 188

7 Contents vii 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 218 F 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 Installing the Latest Microsoft SQL Server Service Pack 257

8 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

9 Contents ix 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 307 Server Configuration 309 Cloud Desktop Troubleshooting 310 Tables 311

10 x Contents

11 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).

12 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 If you still have questions, you can submit your questions using the Wyse Self-Service Center at or call Customer Support at 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 Related Documentation and Services Users Guide: Wyse WSM TM has been discontinued and incorporated into this guide. Installation Guide: Wyse WSM TM has been discontinued and incorporated into this guide. Publisher Guide: Wyse WSM TM has been discontinued and incorporated into this guide. Advanced Administrators Guide: Wyse WSM TM has been discontinued and incorporated into this guide. Wyse Cloud Software is available on the Wyse Web site at: 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:

13 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."

14 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."

15 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.

16 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: Figure 1 Login page 2. Enter your Admin Username and Password. 3. Click Login to open the Overview page.

17 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).

18 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.

19 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.

20 10 Chapter 3 This page intentionally blank.

21 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."

22 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, 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.

23 Sites 13 Table 1 Routine Site Tasks Table 1 provides a quick overview of routine Site tasks. Tasks You Can Do How Details Add a Stand-Alone Site to the system. Create a Headquarters Site. Create a Linked Site. Edit a Site in the system. Delete a Site from the system. Use the Core Server installation procedures in "Step 2: Installing and Configuring the WSM Core Server." 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. 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. On the Sites page, click the Name link of the Site you want to edit and make your changes. 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. 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." Creating a Headquarters Site on page 14. Creating a Linked Site on page 15. Editing Sites on page 16. You can only delete Linked Sites from Headquarters; a local (default) site cannot be deleted.

24 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.

25 Sites 15 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.

26 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.

27 Sites 17 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 WSM TM ). (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").

28 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