Jump to content


  • 0
alittlelouder

Out-of-Band Management and Wake-on-LAN

Asked by alittlelouder

Question

alittlelouder Newbie

alittlelouder

Posted
Posted

Hey

 

Me again...

 

I've installed the Out-of-Band Management on my SCCM-Server and enabled Wake-on-Lan on the System Site (Doesn't matter if i enable unicast or subnet-broadcast).

If I check the option Wake-on-Lan in an advertisement of a Windows Deployment Task-Sequence the client does not start at the given time. The client stays powered off.

 

The problem is not the switch, neither the client. I've tested wake-on-lan with a freeware tool called "Wake On LAN Ex". If i try to wake up my client with this tool it works.

 

Could anyone help me?

Thank you very much.

 

alittlelouder

 

PS:

I'm having my final thesis of my apprenticeship in 2 weeks, SCCM is a part of it. That's why i ask such a lot questions... =D

 

EDIT:

Environment:

SCCM-Server - Win2k8 Ent. x64

SQL-Server - Win2k8 Ent. x64, SQL2k8 Ent.

Client - Win Vista SP1 Business x86

Share this post

Link to post
Share on other sites

6 answers to this question

Recommended Posts

  • 0
wmmayms Newbie

wmmayms

Posted
Posted

Firstly which version of SCCM are you using? Rightclick on your site and click properties. The information is below the general tab

 

If you look into resource explorer for the object you want to "wol"

 

Is the IP Address/Mac adress spesified here correct?

 

SCCM uses hardware information when sending out the wol packages.

 

what does these logs say?

 

<SCCM instal dir>\logs\wolcmgr.log

<SCCM instal dir>\logs\wolmgr.log

Share this post

Link to post
Share on other sites
  • 0
alittlelouder Newbie

alittlelouder

Posted
Posted

Hey wmmayms

 

Firstly which version of SCCM are you using?

System Center Configuration Manager 2007 (SP1)

Version: 4.00.6221.1000

 

Is the IP Address/Mac adress spesified here correct?

Yes, the MAC-Address is available and correct

 

what does these logs say?

They seem to be fine, i checked them with SMS Trace...

 

Hmm... very strange... It seems to work now... I didn't change anything... :huh:

Emm... Is it possible to make my client start in PXE automatically, I mean without changing any BIOS-Settings...?

 

Thank you

 

alittlelouder

Share this post

Link to post
Share on other sites
  • 0
alittlelouder Newbie

alittlelouder

Posted
Posted

Hey

 

I have to correct my self. I've tested wol on one client and it worked.

Now I've tried the WOL on a second client on wich it didnt work.

 

--> MAC-Address is available

 

Here are the logs for the second job.

 

wolcmgr.log

Persisting job data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_PROCESSDATA'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager processing data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

STATMSG: ID=6504 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_COMMUNICATION_MANAGER" SYS=WIDDPLSCC01 SITE=DPL PID=2004 TID=2576 GMTDATE=Tue Apr 14 09:13:23.380 2009 ISTR0="DPL20003" ISTR1="3" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=422 AVAL0="4cbf18" AID1=421 AVAL1="3" AID2=415 AVAL2="DPL20003" SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager retry for job id='4cbf18' - 1 retries of 3 maximum completed). SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

Persisting job data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager job id='4cbf18' will execute next in at least 60 seconds. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager waiting 60 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager waking up to process new jobs. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_PROCESSDATA'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager processing data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager job id='4cbf18' will execute next in at least 60 seconds. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager waiting 60 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:13:23 2576 (0x0A10)

WOLCManager one or more existing jobs is ready. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:23 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_PROCESSDATA'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:23 2576 (0x0A10)

WOLCManager processing data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:23 2576 (0x0A10)

WOLCManager job id='4cbf18' will execute next in at least 1 seconds. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:23 2576 (0x0A10)

WOLCManager waiting 1 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:23 2576 (0x0A10)

WOLCManager one or more existing jobs is ready. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_PROCESSDATA'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

WOLCManager processing data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

WOLCManager retry for job id='4cbf18' - 2 retries of 3 maximum completed). SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

Persisting job data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

WOLCManager job id='4cbf18' will execute next in at least 60 seconds. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

WOLCManager waiting 60 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:14:24 2576 (0x0A10)

WOLCManager one or more existing jobs is ready. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:24 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_PROCESSDATA'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:24 2576 (0x0A10)

WOLCManager processing data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:24 2576 (0x0A10)

WOLCManager job id='4cbf18' will execute next in at least 1 seconds. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:24 2576 (0x0A10)

WOLCManager waiting 1 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:24 2576 (0x0A10)

WOLCManager one or more existing jobs is ready. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_PROCESSDATA'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

WOLCManager processing data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

WOLCManager retry for job id='4cbf18' has completed (3 retries). SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

STATMSG: ID=6505 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_COMMUNICATION_MANAGER" SYS=WIDDPLSCC01 SITE=DPL PID=2004 TID=2576 GMTDATE=Tue Apr 14 09:15:25.375 2009 ISTR0="DPL20003" ISTR1="3" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=422 AVAL0="4cbf18" AID1=421 AVAL1="3" AID2=415 AVAL2="DPL20003" SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

Persisting job data for job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

WOLCManager waiting 5 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:25 2576 (0x0A10)

WOLCManager one or more existing jobs is ready. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:30 2576 (0x0A10)

WOLCManager executing job id='4cbf18' in state 'STATE_COMPLETE'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:30 2576 (0x0A10)

WOLCManager completing job id='4cbf18'. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:30 2576 (0x0A10)

WOLCManager waiting 3600 seconds for work. SMS_WAKEONLAN_COMMUNICATION_MANAGER 14.04.2009 11:15:30 2576 (0x0A10)

 

wolmgr.log

WOLManager one or more schedules are due. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:23 2580 (0x0A14)

0 WOL client network data processed. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:23 2580 (0x0A14)

STATMSG: ID=6510 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_MANAGER" SYS=WIDDPLSCC01 SITE=DPL PID=2004 TID=2580 GMTDATE=Tue Apr 14 09:13:23.239 2009 ISTR0="DPL20003" ISTR1="3" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=421 AVAL0="3" AID1=415 AVAL1="DPL20003" SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:23 2580 (0x0A14)

WOLManager waiting 3600 seconds for work. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:23 2580 (0x0A14)

WOLManager waking up to process new jobs. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:38 2580 (0x0A14)

STATMSG: ID=6510 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WAKEONLAN_MANAGER" SYS=WIDDPLSCC01 SITE=DPL PID=2004 TID=2580 GMTDATE=Tue Apr 14 09:13:38.192 2009 ISTR0="DPL20003" ISTR1="3" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=421 AVAL0="3" AID1=415 AVAL1="DPL20003" SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:38 2580 (0x0A14)

WOLManager waiting 3600 seconds for work. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:38 2580 (0x0A14)

WOLManager waking up to process new jobs. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:38 2580 (0x0A14)

WOLManager waiting 3600 seconds for work. SMS_WAKEONLAN_MANAGER 14.04.2009 11:13:38 2580 (0x0A14)

 

Thank you!

 

alittlelouder

Share this post

Link to post
Share on other sites
  • 0
anyweb Proficient

anyweb

Posted
Posted
Now I've tried the WOL on a second client on wich it didnt work.

 

make sure that the pc's you are trying to WOL have had a clean shutdown first, a clean shutdown is where you tell the OS to power down using the start menu, a dirty shutdown is done by holding the power switch until all power is cut.

 

PC's in a dirty power down state, can fail to WOL, so be sure to check that....

 

cheers

anyweb

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
Go to question listing
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.