WOL works within the same subnet. For WOL to work across subnets, you need to make some changes in the router to forward WOL broadcast packets.



Similar documents
High Availability Configuration

Mobile App Quick Start

Audit Management Reference

For Active Directory Installation Guide

Asset Inventory Reference

Software Distribution Reference

SSL Management Reference

ZENworks Mobile Management 3.0.x Deployment Quick Start

Remote Management Reference

Novell ZENworks 10 Configuration Management SP3

System Planning, Deployment, and Best Practices Guide

TeamViewer 9 Manual Wake-on-LAN

Out-of-Band Management Reference

ZENworks Adaptive Agent Reference

Server Installation Guide ZENworks Patch Management 6.4 SP2

Database Maintenance ZENworks Mobile Management 2.7.x August 2013

Patch Management Reference

Administration Quick Start

Remote Management Reference

Server Installation ZENworks Mobile Management 2.7.x August 2013

User Guide Novell iprint 1.1 March 2015

Certificate Management

Patch Management Reference

Database Management Reference

Novell Identity Manager Resource Kit

Full Disk Encryption Agent Reference

Generating an Apple Push Notification Service Certificate

Full Disk Encryption Pre-Boot Authentication Reference

Patch Management Reference

Novell Open Workgroup Suite Small Business Edition Helpdesk

Installation and Configuration Guide

Administration Guide Messenger 2.2 July 30, 2013

Installation and Configuration Guide

TeamViewer Manual Wake-on-LAN

Novell SUSE Linux Enterprise Virtual Machine Driver Pack

Novell LDAP Proxy Server

Android App User Guide

Installation Guide. Novell Storage Manager for Active Directory. Novell Storage Manager for Active Directory Installation Guide

Jobs Guide Identity Manager February 10, 2012

2 Downloading Access Manager 3.1 SP4 IR1

Novell Sentinel Log Manager 1.2 Release Notes. 1 What s New. 1.1 Enhancements to Licenses. Novell. February 2011

Windows Client User Guide

Configuring File Servers and Active Directory with Domain Services for Windows-Lab

ATT8367-Novell GroupWise 2014 and the Directory Labs

Administration Guide Messenger 3.0 February 2015

Troubleshooting: 2 Solutions to Common Problems

This Readme includes information pertaining to Novell Service Desk 7.0.

User Self-Administration

NOVELL ZENWORKS ENDPOINT SECURITY MANAGEMENT

Upgrade and Migration Guide

2 Configuring GroupWise Mobility Service to Support Microsoft Outlook Clients

NetIQ Sentinel Quick Start Guide

User Source and Authentication Reference

Novell Identity Manager

Migration Tool Administration Guide

Advanced User Guide Vibe 4.0 March 2015

Password Management Guide

Asset Management Reference

Web Application User Guide

Managing Macintosh OS-X with Novell ZCM 11.2 Lecture

Advanced edirectory Troubleshooting in Linux Lab

Novell Access Manager

NetIQ Operations Center 5: The Best IT Management Tool in the World Lab

Policy Guide Access Manager 3.1 SP5 January 2013

Aurora. Version 1.0. Installation and Administration Guide. June 2012

Migration Tool Administration Guide

How To Manage Storage With Novell Storage Manager 3.X For Active Directory

Web Application User Guide

Administration Guide Modular Authentication Services (NMAS) April 2013

Novell Identity Manager Driver for Remedy Action Request System (ARS)

ZENworks Virtual Appliance Deployment and Administration Reference

Client User Guide GroupWise 2014 April 2014

Client User Guide GroupWise 2014 R2 November 2015

Android App Release Notes

User Application: Design Guide

Administration Guide. Novell Storage Manager for Active Directory. Novell Storage Manager for Active Directory Administration Guide

System Administration Guide

ZENworks 11 Support Pack 4 Management Zone Settings Reference. May 2016

2 Installing Privileged User Manager 2.3

Administration Guide GroupWise Mobility Service 2.1 February 2015

Advanced Bundle Management Concepts with ZCM 11 Lab

SSL VPN Server Guide Access Manager 3.1 SP5 January 2013

Installation Guide Identity Manager August 31, 2012

Novell Remote Manager Administration Guide

Novell Distributed File Services Administration Guide

WebAccess User Guide GroupWise 2014 August 2014

Administration Guide Certificate Server May 2013

WebAccess Mobile User Guide

Administration Guide. . All right reserved. For more information about Specops Gpupdate and other Specops products, visit

SSL VPN User Guide Access Manager 3.1 SP5 January 2013

Intel Active Management Technology with System Defense Feature Quick Start Guide

Novell Identity Manager

User Guide. SUSIAccess. Remote Device Management

SyAM Software Management Utilities. Creating Templates

WakeMyPC technical user guide

Discovery, Deployment, and Retirement Reference

Catalyst Layer 3 Switch for Wake On LAN Support Across VLANs Configuration Example

Administration Guide Novell Filr May 2014

Full Disk Encryption Policy Reference

Novell Storage ServicesTM File System Administration Guide for Linux

Transcription:

ZENworks 11SP3 Using Wake-on-LAN February 2014 Novell Wake-on-LAN (WOL) is a feature available on devices and is used to remotely wake up devices that are in shutdown, sleep, or hibernate mode. To perform WOL, you need to enable the WOL option along with certain hardware settings on the device. Wake-on-LAN works only on physical devices with wired network connections. WOL works within the same subnet. For WOL to work across subnets, you need to make some changes in the router to forward WOL broadcast packets. See the following sections for more information. Section 1, Prerequisites, on page 1 Section 2, Wake- on-lan on Windows, on page 1 Section 3, Wake-on-LAN How it Works, on page 3 Section 4, Wake-on-LAN in ZENworks Control Center, on page 4 Section 5, Workflow Diagrams, on page 5 Section 6, Wake-on-LAN Scenarios, on page 7 Section 7, Troubleshooting Wake-on-LAN, on page 8 Section 8, Legal Notices, on page 9 1 Prerequisites The device should be Connected to a power source Connected to a network through a LAN A managed device that is registered to the ZENworks Management Zone The proxy server should be registered to the ZENworks Management Zone if the target device is in different subnet. 2 Wake- on-lan on Windows For Windows-managed devices, enable the following hardware settings before you start using Wakeon-LAN Section 2.1, Enabling Wake-on-LAN in BIOS, on page 2 Section 2.2, Enabling Wake-on-LAN in Network Adapter, on page 2 ZENworks 11SP3 Using Wake-on-LAN 1

2.1 Enabling Wake-on-LAN in BIOS To enable the Wake-on-LAN option in the BIOS set up of the device: 1 Enter BIOS Setup during boot up. 2 Go to the Power menu. 3 Set Wake-on-LAN to Power On. 4 Save and exit the BIOS Setup. 2.2 Enabling Wake-on-LAN in Network Adapter See the following sections for more information on enabling WOL in the network card for different Windows platforms: Section 2.2.1, Windows XP, on page 2 Section 2.2.2, Windows 7, on page 2 Section 2.2.3, Windows 8, on page 3 NOTE: Administrative rights are required for this process. Configuration of the network card can vary depending on the type of network adapter and operating system version. 2.2.1 Windows XP To enable Wake-on-LAN for the network card on Windows XP devices: 1 Open the Control Panel of the managed device. 2 Click Administrative Tools > Computer Management > Device Manager. 3 Go to Network Adapters > right click on the required network adapter > Properties. 4 Click Power Management. 5 Check all wake-on-lan options in the Wake-on-LAN section. 6 Click OK. 2.2.2 Windows 7 To enable Wake-on-LAN for the network card on Windows 7 devices: 1 Open the Control Panel of the managed device, then click Administrative Tools. 2 Click Computer Management > Device Manager. 3 Click Power Management > Network Properties. 4 Under Network Adapters, select the required network adapter, then click Properties. 5 Click Power Management. 6 Check the Allow this device to wake the computer option. 7 Click OK. 2 ZENworks 11SP3 Using Wake-on-LAN

2.2.3 Windows 8 To enable Wake-on-LAN for the network card on Windows 8 devices: 1 Open the Control Panel of the managed device, then click System and Security. 2 Under Power Options, click the Change what power buttons do link. 3 Click the Change settings that are currently unavailable link. 4 Check the Turn on fast startup (recommended) option. 5 Click Save Changes. NOTE: On a Windows 8 device, WOL is not supported in shut-down mode and it is supported in Sleep or Hibernate mode. 3 Wake-on-LAN How it Works After enabling the WOL related hardware settings, you can start performing WOL task. The WOL task involves a ZENworks Primary, a proxy server and, a target managed device. Proxy : The proxy server can either be a Linux or a Windows device and should also be registered to ZENworks management zone. The proxy server can also be a virtual machine or a physical device. NOTE: The proxy server can either be a managed device or a Satellite. The Linux proxy server is supported beginning with ZENworks 11.2.4. The following sections provide information about how WOL works: Section 3.1, Waking Up Managed Devices which are in Same Subnet, on page 3 Section 3.2, Waking Up Managed Devices which are in Different Subnet, on page 3 Section 3.3, Magic Packets, on page 4 3.1 Waking Up Managed Devices which are in Same Subnet Once the WOL task is initiated on the specified schedule, the ZENworks Primary sends magic packets directly to the target managed device. In this case, the use of a proxy server is optional because the ZENworks Primary itself acts as a proxy server as the target managed device and the ZENworks Primary are in the same subnet. 3.2 Waking Up Managed Devices which are in Different Subnet Once the WOL task is initiated on the specified schedule, the ZENworks Primary sends magic packets to the configured proxy server to wake up the target managed device. In this case, you need to choose a satellite server or a managed device as a proxy server to forward magic packets to the target device. ZENworks 11SP3 Using Wake-on-LAN 3

3.3 Magic Packets Magic Packet is a broadcast for the particular subnet which contains the hardware or MAC address of a specific network card. This packet sends signals to the motherboard. The managed device receives this packet, checks if it contains correct information, then activates the power supply and boots the system. The WOL packets can only be sent through the local network. Magic packets broadcasted within the subnet contain the subnet information, network broadcast address, and the MAC address of the target computer s network card. For details, see Section 5.2, WOL - What happens in the background?, on page 6. 4 Wake-on-LAN in ZENworks Control Center Using ZENworks Control Center you can perform the WOL task either through Quick Task or through the bundle distribution schedule. The following sections provide information about performing WOL in ZENworks Control Center: Section 4.1, Performing Wake-on-LAN through Quick Task, on page 4 Section 4.2, Performing Wake-on-LAN through Bundle Distribution, on page 5 Section 4.3, Performing Wake-on-LAN through the Command Line Interface, on page 5 4.1 Performing Wake-on-LAN through Quick Task To wake up a managed device through Quick Task. 1 In ZENworks Control Center click Devices > s or Workstations. 2 Select the check box next to the target workstation or a server. 3 Go to Quick Task, then select Wake Up. 4 In the Wake Up dialog box, specify the following: 4a Automatically detect the server : Use this option when the ZENworks Primary and the target managed device are in the same subnet. In this case, the Primary itself acts as the proxy server. When this option is selected, ZENworks automatically detects the Primary closest to the target managed device. 4b Use the following devices: Use this option when the ZENworks Primary and the target managed device are in different subnet. Click Add to select a Satellite or a managed device as a proxy server that is located in the same subnet of the target managed device. NOTE: Proxy server should be a managed device or a Satellite. The Linux proxy server is supported from 11.2.4 onwards.you can configure more than one proxy server for sending wake-on-lan magic packets. If one proxy server is not reachable, then the ZENworks Primary server sends magic packets to the next available proxy server. 5 Click Show Advanced Options to specify the IP address of the selected proxy server that is used for sending the magic packets to the target device. Specifying the IP address of a proxy server is required in a context where a particular device acting as a proxy server has more than one IP address. Automatically detect the IP address: Select this option if you want ZENworks to automatically detect the IP address of the proxy server where the magic packets would be sent to the managed device. 4 ZENworks 11SP3 Using Wake-on-LAN

Use the following IP address: After selecting this option, enter the IP address of the proxy server, then click Add to specify the IP address or addresses other than the default. Number of Retries: The default value is 1. However, you can change it to any number between 0 and 5. Time interval between Retries: The default value is 2 minutes. However, you can change it to any value between 2 and 10 minutes. 4.2 Performing Wake-on-LAN through Bundle Distribution The WOL feature in ZENworks Control Center allows you to perform bundle management operations on powered off devices by waking them up automatically. To wake up a managed device through bundle distribution: 1 In ZENworks Control Center, click Bundles. 2 Select the check box next to the required bundle. 3 Click Action > Assign to Device. 4 Select a target device, then click OK. The target device is listed in the Assign Bundle page. 5 Select the required shortcut location, then click Next. 6 Select the Distribution Schedule on the schedules page. 7 Click Next, then select the Wake-on-LAN (Applies to Devices only) check box on the Bundle Distribution Schedule page. 8 Click Options to use a different proxy server. Click Show Advanced Options to change the default Proxy and IP details. For details, see Step 4 and Step 5 in Section 4.2, Performing Wake-on-LAN through Bundle Distribution, on page 5. 9 Click Next. The distribution schedule details are displayed. 10 Click Finish. After the bundle with distribution schedule is assigned to the managed device with the WOL option configured, the managed device is woken up according to the schedule, and then the bundle is assigned and distributed. 4.3 Performing Wake-on-LAN through the Command Line Interface You can perform Wake-on-LAN on workstations and servers through the command line interface: Waking up a workstation: See workstation-wakeup (ww) (workstation object path) [...] [options] in ZENworks 11 SP3 Command Line Utilities Reference. Waking up a server: See server-wakeup (sw) (server object path) [...] [options] in ZENworks 11 SP3 Command Line Utilities Reference. 5 Workflow Diagrams Section 5.1, WOL - Steps Performed in ZENworks Control Center, on page 6 Section 5.2, WOL - What happens in the background?, on page 6 ZENworks 11SP3 Using Wake-on-LAN 5

5.1 WOL - Steps Performed in ZENworks Control Center This diagram shows how to use the WOL feature through Quick Task in ZENworks Control Center. Primary Automatically detect the server option proxy server the target device Administrator logs in to ZENworks Control Center the Wake Up option from Quick Tasks Navigates to the target device Managed Devices Satellite Use the following devices option IP address Clicks Show Advanced Options Additional Configuration Workstation Clicks OK Wake-on-LAN task is submitted successfully Submit Use the following IP address option 10.25.25.25 Automatically detect the IP address option Sets Number of Retries Sets Time Interval between Retries NIC1 10.25.25.25 NIC1 10.25.25.25 10.25.25.25 10.25.25.25 10.25.25.25 10.25.25.25 NIC2 NIC3 NIC2 NIC3 5.2 WOL - What happens in the background? This diagram shows how the actual WOL task is carried out in the background when initiated. Primary Automatically detect the server option Configured proxy server the Wake Up option from Quick Tasks WOL task initiated ZENworks Primary Managed Devices Proxy server goes to the ZENworks Primary Proxy server fetches the WOL task data Satellite Use the following devices option Sending magic packets Proxy server not reachable Devices in different subnet Fails to wake up the device WOL task status update sent Subnet check - Fail WOL task failure status update sent Subnet check Subnet check - Pass Proxy server reachable Devices in same subnet Successfully wakes up the device WOL task successful status update sent Proxy server 6 ZENworks 11SP3 Using Wake-on-LAN

6 Wake-on-LAN Scenarios ZENworks Primary Use Case1 ZENworks Proxy Target Managed Devices Subnet 1 101.99.95.XXX Subnet 1 101.99.95.XXX Subnet 1 (101.99.95.XXX) ZENworks Satellite Use Case 2 Subnet 1 101.99.95.XXX Subnet 2 101.99.98.XXX Subnet 2 (101.99.98.XXX) Managed device/satellite server Use Case 3 Subnet 3 101.99.101.XXX Subnet 3 (101.99.101.XXX) Managed device/satellite server Use Case 4 NIC1 Subnet 4 IP1 101.99.165.XXX Subnet 4 (101.99.165.XXX) NIC2 IP2 10.99.80.XXX NIC3 IP3 138.99.50.XXX This diagram shows Subnet 1, Subnet 2, Subnet 3, and Subnet 4 respectively. All devices that are located in these four subnets are managed by a ZENworks Primary server located in Subnet 1. Section 6.1, Use Case 1, on page 7 Section 6.2, Use Case 2, on page 8 Section 6.3, Use Case 3, on page 8 Section 6.4, Use Case 4, on page 8 6.1 Use Case 1 An administrator wants to wake up devices located in Subnet 1. In this case the Primary itself acts as a proxy server because the target managed devices and the Primary are in the same subnet. ZENworks 11SP3 Using Wake-on-LAN 7

6.2 Use Case 2 An administrator who wants to wake up devices located in Subnet 1 and Subnet 2 in a single WOL task must specify the following as proxy servers: A Satellite or a managed device that is located in Subnet 2. A Primary or a Satellite or a managed device that is located in Subnet 1. As a result, the target managed devices located in both Subnet 1 and Subnet 2 will get magic packets from those proxy servers that are also located in the subnet of the target devices. 6.3 Use Case 3 An administrator who wants to wake up only those devices that are located in Subnet 3 must specify a Satellite or a managed device as a proxy server that is located in the subnet of the target device. 6.4 Use Case 4 An administrator who wants to wake up devices located in Subnet 4 and must specify a proxy server that has multiple NICs or IP addresses. Then the WOL task is performed based on one of the following options selected: Automatically detect the IP address: If the administrator selects this option, then ZENworks wakes up the devices that are reachable and that have IP addresses that match the subnet of the target device. Use the following IP address: If the administrator selects this option, then ZENworks uses the IP address to wake up the devices that are reachable and that are in the subnet of the target managed device. 7 Troubleshooting Wake-on-LAN WOL is not supported in shutdown mode on a Windows 8 managed device on page 8 WOL is not supported in shutdown mode on a Windows 8 managed device Explanation: Action: When you do a standard shutdown on a Windows 8 device, the device goes into a hybrid shutdown state. Windows 8 does not support Wake-on-LAN in hybrid shutdown mode. It does support it in sleep or hibernate mode. If you deactivate the fast startup option, the Windows 8 device will be in hibernation when shutdown. To perform WOL task on a Windows 8 device, deactivate the fast startup option: 1 Open the Control Panel of the managed device. 2 Click System and Security. 3 Under Power Options, click the Change what power buttons do link. 4 Click the Change settings that are currently unavailable link. 5 Uncheck the Turn on fast startup (recommended) check box. 8 ZENworks 11SP3 Using Wake-on-LAN

8 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals. Copyright 2014 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. Novell, Inc. 1800 South Novell Place Provo, UT 84606 U.S.A. www.novell.com Online Documentation: To access the latest online documentation for this and other Novell products, see the Novell Documentation Web page (http://www.novell.com/documentation). Novell Trademarks For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/ company/legal/trademarks/tmlist.html). Third-Party Materials All third-party trademarks are the property of their respective owners. ZENworks 11SP3 Using Wake-on-LAN 9