SMSWakeup integrates remote wakeup (Wake-On-LAN) technology with Microsoft Systems Management Server (SMS)/System Center Configuration Manager (ConfigMgr), providing administrators with an easy way of ensuring that PCs are fully powered on whenever they are needed.

It ensures that all PCs targeted by an advertisement are turned on and ready to receive it, reducing the chance that a PC will miss a vital patch. Support personnel no longer have to visit each PC, saving time.

Because you can guarantee with SMSWakeUp that each PC will be available when it is needed, the total power consumption of the enterprise will be reduced as PCs can be powered off when not in use.

Although SMSWakeUp can only be used to turn PCs on, it can be used in conjunction with another 1E product, NightWatchman, to turn off PCs. NightWatchman can turn off PCs on demand, or according to a schedule, thereby reducing power consumption. It also saves any open documents thereby ensuring that no data is lost during the shut down.

SMSWakeUp and NightWatchman can be purchased together as a cost effective power management solution in the Patch Management Pack.

Wake-On-LAN is a technology which allows administrators to remotely power on systems from sleep or standby mode. To use Wake-On-LAN technology on a PC, it must be supported by both the operating system and the system hardware.

Wake-On-LAN technology is a result of the Intel-IBM Advanced Manageability Alliance. A Wake-On-LAN aware network adapter is able to draw power from a special power supply that delivers a certain amount of power continually, even when the system is switched off. The network adapter continuously monitors the network watching for a specific type of network packet called a Magic Packet. When it receives that packet it alerts the system to boot into a full power state.

A Magic Packet is a specially-formatted network packet which contains MAC address information. The network card listens out for a magic packet containing its MAC address. Once the packet has been received the network adapter will send a message to the motherboard to initiate boot up.

Magic packets are sent using a directed broadcast, which is a broadcast to all of the machines on a particular subnet. For example, a directed broadcast address could be specified as 192.168.100.255, which would go to all machines on the 192.168.10.x/24 network.

Many administrators turn off routing of subnet-directed broadcasts, because they can be abused by hackers in order to generate large amounts of extra network traffic.

SMSWakeUp provides different installation models for the different types of network configurations that are liable to be encountered. You must decide at installation time which model is most suited to your network. The installation models are:

Installation model Description Master Only Simplest to install Requires directed broadcasts enabled on the network Does not support Policy Refresh Does not support reporting Dedicated Slave Must be installed on master and dedicated slave machines Requires that the dedicated slave machines are left on constantly Does not support Policy Refresh Supports limited reporting Multi-slave Must be installed on all machines Requires that at least one machine per subnet is on when the wakeup request is sent Supports Policy Refresh Supports full wakeup success reporting

SMSWakeUp sends magic packets by directed broadcast. If the routers in your network will pass the broadcast traffic you can use SMSWakeUp with its basic functionality by installing in master only mode.

The SMSWakeUp master service should only be installed on the Primary SMS/ConfigMgr server. The master service monitors SMS/ConfigMgr advertisements and sends the wakeup requests to the slave service when needed. The slave service actually sends the wakeup packets (in master only mode the slave service is still used, it is just installed along with the master service on the Primary SMS/ConfigMgr Server).

When the network infrastructure prevents broadcast traffic, you must use either Dedicated or Multi-Slave installation mode. In dedicated mode the slave service is only installed on a single machine on each IP subnet which must remain on at all times. In Multi-Slave mode the service is installed on all machines throughout the organisation.

If you want to use SMSWakeUp with its full functionality, providing statistical feedback on wakeups and speeding up SMS/ConfigMgr delivery with Policy Refresh you must install in Multi-Slave mode. This is the recommended mode as it will work in all network configurations and provide all SMSWakeUp functionality.

Yes, you must install SMSWakeUp on your central site. Doing this enables you to perform right-click wakeups on collections from the SMS Admin Console.

SMSWakeUp has two component services, the Master service and the Slave service.

The SMSWakeUp Master service
This service integrates directly with SMS/ConfigMgr. It provides an interface that is available through the Administrator console and acts as the central controller for the wakeups. It does this by generating Magic Packets to awaken specific machines, either on user request or as a by-product of a scheduled SMS advertisement. Additionally the SMSWakeUp Master service can be configured to distribute the Magic Packets by communicating over IP with optional SMSWakeUp Slave services.

The SMSWakeUp Slave service
This service is installed on a remote subnet and receives instructions from a specific SMSWakeUp Master service. The slave services can function in either a dedicated or a Multi-Slave mode. The difference being that the dedicated slave mode requires that the machine the slave is running on is permanently powered on and available on the network. In Multi-Slave mode the slaves are dynamically assigned.

SMSWakeUp sends magic packets by directed broadcast. If the routers in your network prevent broadcast traffic you must install SMSWakeUp in either Dedicated or Multi-Slave mode. In dedicated mode the slave service is only installed on a single machine on each IP subnet which must remain on at all times. In Multi-Slave mode the service is installed on all machines throughout the organisation.

In this mode the master SMSWakeUp service then sends wakeup requests directly over IP to the slave service installed on machines on each IP subnet throughout the network and that service will then broadcast the wakeup packets on its particular subnet. Secondary SMS site servers may also be used as slave machines.

SMSWakeup integrates with ConfigMgr 2007 or SMS 2003 SP2 and above.

Additionally it requires the following agents to be enabled:

•	The Hardware Inventory Client Agent
•	The Advertised Programs Client Agent

The following operating system, SMS/ConfigMgr requirements, hardware, power management and network specifications should be met in order for SMSWakeUp to be successfully installed and run.

SMS/ConfigMgr Server Operating System requirements

The SMSWakeUp master and Agent services should install and be configurable on any SMS/ConfigMgr Server running the following Microsoft operating systems:

•	Windows 2003 Server
•	Windows 2000 Server SP4

SMS/ConfigMgr Client Operating System requirements

The SMSWakeUp Agent service should install and be configurable on any workstation with the SMS/ConfigMgr Client installed with the following Microsoft operating systems:

•	Windows Vista
•	Windows XP
•	Windows 2004 SP4 Operating System SMSWakeUp should install and be configurable on any workstation running the following Microsoft operating systems:

     

Systems Management requirements
The following SMS version and agents need to be available.

•	ConfigMgr 2007 or SMS 2003 SP2 and above
•	The Hardware Inventory Client Agent must be enabled
•	The Advertised Programs Client Agent must be enabled
•	Machine must be an SMS/ConfigMgr client

Hardware
To utilise Wake-On-LAN technology you need all of the following hardware configurations:

•	A network card which can support Wake-On-LAN - Your network card vendor can tell you if your network adapter supports Wake-On-LAN. If it does support Wake-On-LAN, it must be configured to enable remote wakeup. Some adapter drivers are disabled by default within the operating system.
•	Wake-On-LAN enabled system BIOS - Wake-On-LAN must be enabled in the system BIOS. This option can usually be found in the 'Boot' menu of the BIOS configuration program.
•	Power management - ACPI should be enabled, otherwise the user of the machine should ensure that it is powered off by hitting the off button after shutdown.

Note: A quick way to tell if a system is Wake-On-LAN ready is to power down the system then look at the network adapter display LED's. If the lights are still on, then chances are that the system is OK. 1E also provide a diagnostic tool called Magic Test that will determine the ability for a single machine to react to a Magic Packet wakeup.

Power Management
Once you are confident that your hardware is Wake-On-LAN enabled you need to check that your operating system satisfies the following power management standard.

•	ACPI - Advanced Configuration and Power Interface is the most recent standard favoured by operating systems such as Windows 2000 and Windows XP.

A quick way to tell if a system is Wake-On-LAN ready is to power down the system then look at the network adapter display LED's. If the lights are still on, then chances are that the system is OK. 1E also provide a diagnostic tool called Magic Test that will determine the ability for a single machine to react to a Magic Packet wakeup.

Your network card must support Wake-On-LAN - Your network card vendor can tell you if your network adapter supports Wake-On-LAN. If it does support Wake-On-LAN, it must be configured to enable remote wakeup. Some adapter drivers are disabled by default within the operating system so you will need to check your network card documentation.

Wake-On-LAN must be enabled in the system BIOS. This option can usually be found in the 'Boot' menu of the BIOS configuration program, but again this is hardware specific so please check the manufacturer's documentation.

Although the software license only needs to be explicitly applied to the master service, you will need to purchase licenses for all the SMS Client seats being serviced.

If SMSWakeup is initially installed using the 30-day evaluation license, it can be relicensed later without requiring re-installation, once a full license has been purchased, by running the following command line:

C:>SMSWakeUp40.exe -relicense=CustID-xxxx-xxxx-xxxx-xxxx

Where CustID-xxxx-xxxx-xxxx-xxxx represents the license key purchased from 1E.

Note: the full license must be applied to every master installation.

You only need to apply the license to the master service, though you need to purchase licenses for all the SMS Client seats being serviced. So to apply the license to an unattended install of the master service you add the following to the msiexec command line for the master service installer:

C> msiexec /i Minislave40.msi SLAVETO="MASTER_SERVER_NAME" PIDKEY=CustID-xxxx-xxxx-xxxx-xxxx /qn

Where MASTER_SERVER_NAME represents the name where the SMSWakeUp Master is installed and CustID-xxxx-xxxx-xxxx-xxxx represents the license key purchased from 1E. Back to top

To obtain a license key for SMSWakeUp or purchase additional licenses for more SMS Clients you should contact sales@1e.com.

Although you must purchase licenses for all the SMS Clients being serviced by SMSWakeUp you only need to apply the licence to the master service. The slave services do not need a license key. SMSWakeUp will manage your licenses centrally which can be confirmed by checking the log file. The first line in the log file should read the status of the license.

The SMSWakeup Master and the Slave services can be upgraded directly from the previous version. Please refer to Section 3 of The SMSWakeUp Installation Guide , particularly to sections 3.6 to 3.8.

The latest version of SMSWakeUp supports encryption for the packets used for communications between the SMSWakeUp master and slaves. If you get this error it usually indicates that some, but not all, of your components are using encryption.

Choosing full encryption when installing SMSWakeUp will set the system to ignore any unencrypted communications. This will prevent the new installation from working in conjunction with an earlier version of SMSWakeUp where encryption was not supported.

Installing SMSWakeUp using partial encryption enables the use of both encrypted and unencrypted packets.

If you are upgrading SMSWakeUp and you decide to utilise encryption, you will either need to roll out the change simultaneously to every machine where SMSWakeUp was installed, or install the system using partial encryption and upgrade all the SMSWakeUp installations incrementally.

You can choose at installation whether you want full, partial or no encryption. The different options behave as follows:

Full Encryption
All communications will be encrypted and any unencrypted packets received will be ignored. This feature cannot be used in conjunction with previous versions of SMSWakeUp as these do not support encryption. For the same reason you cannot install the latest version as a hybrid where some components use no encryption and others use full encryption.

Partial Encryption
Either encrypted or unencrypted communications will be accepted. This is a useful half-way station to a fully encrypted configuration; that caters for the scenario where you upgrading an existing SMSWakeUp installation to use encryption and you do not want to re-install every single component in one go. The new installation will send out encrypted packets but the unencrypted packets sent by the previous version will still work.

No encryption
All packets sent will be unencrypted, in which case SMSWakeUp will behave the same as in previous versions.

The command line to turn on full encryption for the slave service is as follows:

msiexec /i Minislave40.msi ENCRYPTIONLEVEL=2 /qn

Where the values for the encryption level can be as follows:

0=No encryption

1=Partial encryption

2=Full encryption

Dedicated slave mode
In dedicated slave mode the slave services are installed on specific machines on each subnet. At installation time you set the name of the server that is hosting the SMSWakeUp Master service. This establishes the communications between the slave and master services at runtime.

Multi slave mode
When you use SMSWakeUp in its full Multi-Slave mode you must install the SMSWakeUp slave on all of the machines on the remote subnet. The SMSWakeUp master establishes communications automatically with a slave service on the subnet and from then on communicates with that slave. If this slave becomes unavailable, the master will locate another slave on the subnet.

We do not recommend changing the default ports used by SMSWakeUp, however if there is no alternative it is possible to change the ports by editing the following registry keys:

Key Name Description HKLM\SOFTWARE\1E\SMSWakeUp40 TCP_Port master listener port HKLM\SOFTWARE\1E\SMSWakeUp40 SlvTCP_Port slave listener port (must be different if slave on same machine) HKLM\SOFTWARE\1E\SMSWakeUp40\SlaveParam MagicPacket_Port This is the port through which wakeups broadcasts are sent on. This value should be the same as SlvTCP_Port HKLM\Software\1E\minislv slvTCP_Port Slave listening port. Must be different to TCP_Port. Must be same for all Slaves. HKLM\Software\1E\minislv TCP_Port Master listening port. Must be different to slvTCP_Port. Must be same for all Masters.

SMSWakeUp is a Windows only application. Currently there is no support for non-Windows platforms such as UNIX or Linux.

Simply create an advertisement where the command line is given as “cmd.exe /c echo”. This runs a Windows command prompt and immediately exits.

You might want to do this when testing SMSWakeup in your environment, or in order to ensure that your workstations are fully booted at start of business each day.

If you change the IP address for a machine but keep it on the same subnet there should not be a problem, as the Magic Packet is broadcast on the client's subnet to the MAC address of the client machine.

Short term problems may arise if you move a machine to a different subnet; you would then need to ensure that the hardware inventory in SMS is up to date so that SMSWakeUp can send the wakeup signal to the correct subnet.

No. At each polling cycle SMSWakeUp scans the SMS Advertisements for assigned schedules that it has not yet processed. So it only processes a schedule once.

For example, if you have a collection containing 10 machines, and you advertise a package to it with an assigned schedule of 10am SMSWakeUp will wake those 10 systems at 10am. After that time it will not process any further systems added to the collection.

This is machine dependent so you will need to refer to the documentation for your hardware.

This depends on the configuration for the laptop. Laptops are usually configured to not respond to wakeup packets when they are running on batteries. If the laptop is running on mains and not battery power then the wakeup should work as on a standard PC.

By default SMSWakeUp uses TCP and UDP ports 1776 to communicate with the slave services when installed in one of the slave models. You will need to refer to your router documentation to see how to open this port.

Without SMSWakeUp, because magic packets themselves do not have any kind of security, if the unauthorised users are on the local network, or are able to send directed broadcasts into the network you cannot prevent them from waking up PCs by sending their own magic packets. The best way to stop this from happening is by preventing unauthorised users gaining access to your network.

If you are using SMSWakeup in a master/slave configuration, communication between the master and the slaves can be encrypted by installing the SMSWakeUp master and slave services using full encryption mode, see The SMSWakeUp Installation Guide for more details. This will prevent unauthorised users from gaining information about the network when using SMSWakeUp.

Ultimately the worst case is that a machine is powered on, it implies no additional security risks that did not already exist.

Some makes of PC can have a different boot order configured in the BIOS for when they are woken from the network as opposed to when they are physically powered up. For example some HP machines have an option called “Remote Wakeup Boot Source” and this can be set to either “Remote Server” or “Local Hard Drive”.

To wake machines in a sub-collection you need to ensure that you have the Process Sub Collections option turned on. This is done on the Configuration tab in the SMSWakeUp console. The following picture shows the Process Sub Collections option selected.



This option determines whether sub-collections should be included when processing advertisements and defaults to unchecked.

The operational days are set using the Excluded Hours and Operational Days controls on the Configuration tab in the SMSWakeUp Console, as shown in the following picture.


The Excluded Hours section sets a time frame during which wake up requests will be disabled. This allows restrictions to be applied to the service during busy times of the day. The Start control sets the start of the restricted hours period in 24hr format and defaults to 00:00 which equates to no restrictions. The End control sets the end of the restricted hours period in 24hr format and also defaults to 00:00 which equates to no restrictions. The effect of the excluded hours section is also dependent on the Operational Days options.

The Operational Days section determines whether the Excluded Hours options apply for the selected day. If the checkbox is selected for a particular day then the restrictions apply on that day. By default all the days are selected, meaning that if any values are set in the excluded hours they will apply to all the days of the week.

The most likely reason for the problem that you are seeing would be overlapping advertisements pushing the wakeup count to above your 700 License limit.

You should either schedule wakeups so that the wakeup list queue is always below the license limit or, if you have advertisements running concurrently for the same collections you may tick the "check wakeups in name" box in the SMSWakeUp40 administrators console and control wakeups sent in this manner.

This is due to a problem in Windows 2003 that was fixed in SP1. You should install SP1 or apply the hotfix from the following location: http://support.microsoft.com/default.aspx?scid=kb;en-us;899095. The patch doesn’t directly refer to the problem -- which is resolved by the hotfix listed at http://support.microsoft.com/default.aspx?scid=kb;en-us;895477 – but it includes both fixes.

It usually means that either the slave is not installed, not started, or there is a firewall in the way. You should check that the SMSWakeUp Slave is installed and started on the target machine and ensure that the SMSWakeUp communications port, default 1776, is open for both TCP and UDP communications.

For example, the machine with the slave service is running Windows XP SP2, and the firewall is turned on. You need to ensure that port 1776 is open for TCP and UDP communications. This is covered in section 5.3 of The SMSWakeUp Administrator's Guide

In order to run SMS WakeUp from the command line on an administration machine you would run the following command:

Or on the server to wake a single machine:-

or to wake up a collection

This functionality is not supported by SMSWakeup. 1E provide a Wake-On-LAN testing utility called MagicTst.exe which is available for download from the 1E website.

The Multi-Slave Ping cycle is set on the Slave Configuration tab of the SMSWakeUp Admin Console. When in Multi-Slave mode the SMSWakeUp slaves are discovered automatically using ping packets. The Slave portion of this tab allows you to set the number and frequency of pings sent. It also allows you to set the timeout for receiving a response and how often the subnet is rescanned. This enables you to set a balance between successfully finding all the slaves against the amount of network traffic generated. The options in this portion of the dialog are only available when the Multi-Slave Mode checkbox is checked.

Yes. The policy refresh cycle is triggered by making a call to the SMS Advanced client (documented in the SMS 2003 SDK). This call cannot be made remotely so it requires a local agent to make the call. In SMSWakeUp the Slave service is used for this purpose.

1E provide two handy utilities for testing the sending and receiving of magic packets. These tools, named RECVFROM and MAGICTST are available for download from the 1E website.

The magic test
The 1E magictst.exe utility, as seen below, lets you send a magic packet to a single machine to test the functioning of Wake-On-LAN hardware. It can be launched by selecting the Start menu/Programs/SMSWakeUp40/Magic Test item. This item will only have been installed if you chose the Complete option during the SMSWakeUp installation.

For this test you need two PCs, a sender and a target. The sender and target PCs should both be on the same subnet. Follow the steps below to carry out the test.

SMSWakeUp draws SMS client information directly from the SMS database. The client registers its IP and Subnet information as part of the SMS discovery process. VLSM therefore will not affect SMSWakeUp.

See http://www.faqs.org/faqs/cisco-networking-faq/section-37.html for more information about VLSM.