Skip navigation
1 2 Previous Next 18192 Views 26 Replies Latest reply: Apr 8, 2009 2:22 AM by phoffmann RSS
Rookie 45 posts since
Apr 2, 2008

Has received 1 of 9 achievements.
Currently Being Moderated

Mar 17, 2009 9:45 AM

Dos window pop-up

A couple of days ago, I set a new power policy on a particular group of PCs using LANDesk Power Management tool.

I have started to receive a few comments from people using these PCs that they are occasionally seeing a blank dos window pop up a few times a day. It comes up and then disappears very quickly.

I can't prove that this is connected, but it does seem a little suspicious and I can't find anything else that may be causing it.

Anyone come across this before or able to offer a possible explanation??

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    1. Mar 17, 2009 9:56 AM (in response to edwardsp)
    Re: Dos window pop-up

    You can check the SERVICEHOST.LOG client-side (in the "C:\Program Files\LANDesk\Shared Files\" directory by default) to check if anything was coming in via a scheduled task (of any shape or form) from the Core.

     

    Similarly, you can check the local scheduler's log-file (assuming you use 8.8 - which you must "my own duh moment", since you use power management) to check if Local scheduler's running. That should cover most bases I'd imagine?

     

    Paul Hoffmann

    LANDesk EMEA Technical Lead

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    3. Mar 17, 2009 10:18 AM (in response to edwardsp)
    Re: Dos window pop-up

    Well - the key thing you need to know is "when" this window popped up.

     

    The SERVICEHOST logs (with timestamps) the commands sent by the Core, for instance:

    ""

    ...

    Tue, 17 Mar 2009 08:21:50 4228: Public key path C:\Program Files\LANDesk\Shared Files\cbaroot\certs

    Tue, 17 Mar 2009 08:21:50 4228: Anonymous connection established
    Tue, 17 Mar 2009 08:21:50 4228: Request Received "POST /ldapplpcgi.exe HTTP/1.1"
    Tue, 17 Mar 2009 08:21:51 4228: CGI "C:\Program Files\LANDesk\LDClient\ldapplpcgi.exe" launched
    Tue, 17 Mar 2009 08:21:59 4228: EOF encountered parsing HTTP headers, client closed connection.
    Tue, 17 Mar 2009 08:21:59 4228: Service host has finished

     

    <seperator added by me>


    Tue, 17 Mar 2009 09:50:11 2496: Service Host Started, Host <hostname>:9595, Peer 127.0.0.1, IP Address 127.0.0.1
    Tue, 17 Mar 2009 09:50:11 2496: Public key path C:\Program Files\LANDesk\Shared Files\cbaroot\certs
    Tue, 17 Mar 2009 09:50:11 2496: Anonymous connection established
    Tue, 17 Mar 2009 09:50:11 2496: Request Received "POST /ldapplpcgi.exe HTTP/1.1"
    Tue, 17 Mar 2009 09:50:11 2496: CGI "C:\Program Files\LANDesk\LDClient\ldapplpcgi.exe" launched
    Tue, 17 Mar 2009 09:50:15 2496: EOF encountered parsing HTTP headers, client closed connection.
    Tue, 17 Mar 2009 09:50:15 2496: Service host has finished

    ...

    ""

     

    shows LDAPPLCGI being launched (and done so as commanded by the Core) at 8:21 am and again at 9:50 am ... so this is what you're looking for. If a user says "at quarter past 10, I had this flashing thing", you have a look what was started around that time, for instance.

     

    The "Service host started / finished" are seperators for "Core started talking to me / Core finished talking to me".

     

    A Power Manager related thing, would look like this (as taken from your log):

    ""

    Mon, 16 Mar 2009 09:37:02 4816: Service Host Started, Host <host>:9594, Peer 10.225.101.48, IP Address 10.225.61.64
    Mon, 16 Mar 2009 09:37:02 4816: Public key path C:\Program Files\LANDesk\Shared Files\cbaroot\certs
    Mon, 16 Mar 2009 09:37:02 4816: Cached certificate EXPIRED   cached(0) now(128816698227036755)
    Mon, 16 Mar 2009 09:37:03 4816: Caching newly created certificate
    Mon, 16 Mar 2009 09:37:03 4816: X509 Authentication via f28e28bc
    Mon, 16 Mar 2009 09:37:03 4816: Request Received "POST /services/exec HTTP/1.1"
    Mon, 16 Mar 2009 09:37:03 4816: Exec: Exec: Launch request <"cmd" /c del "C:\Program Files\LANDesk\LDCLient\PWMScript.ini"> (sync 1, timeout 1200)
    Mon, 16 Mar 2009 09:37:04 4816: Request Received "POST /services/exec HTTP/1.1"
    Mon, 16 Mar 2009 09:37:04 4816: Exec: Exec: GetStatus: returning status 0 for terminated application c40 (run state 0).
    Mon, 16 Mar 2009 09:37:04 4816: Request Received "POST /services/exec HTTP/1.1"
    Mon, 16 Mar 2009 09:37:04 4816: Exec: Exec: GetStdOut - Returning stdout for application c40
    Mon, 16 Mar 2009 09:37:05 4816: EOF encountered parsing HTTP headers, client closed connection.
    Mon, 16 Mar 2009 09:37:05 4816: Service host has finished

    ""

     

    NOTE -- I've changed the host-names to "<host>" so you can delete the servicehost.log file if you prefer, this way the log entries are anonymous enough to show what to look for.

     

    Does this make more sense to you now?

     

    Paul Hoffmann

    LANDesk EMEA Technical Lead

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    4. Mar 17, 2009 10:20 AM (in response to phoffmann)
    Re: Dos window pop-up

    Or put another way...

     

    ... you're not looking for something "being wrong" ... you're looking for what's been launched (from a LANDesk point of view), and then check if that's the case for all of your DOS-window sightings.

     

    You're not chasing an "error" per se - you're just checking if there's a common launch request of some sort associated with the sightings.

     

    Paul Hoffmann

    LANDesk EMEA Technical Lead

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    6. Mar 18, 2009 7:31 AM (in response to edwardsp)
    Re: Dos window pop-up

    Hmm - so I tried this in my lab, and no luck at all.

     

    I don't get a DOS-window pop up at all (8.8 + SP2A, nothing else) on my client at all. I've tried running the command through various other means, but no DOS-window popup..

     

    There must be a bit more to this story - once you've figured out that last detail, which will hopefully capture the whole story on how to duplicate this / get this behaviour to happen, I'd say raise it as support ticket and we can treat it from there. It's however not a straight forward "this task in local scheduler causes the popup box", as I've had it run a few times now without any CMD-box popping up.

     

    Or at a push, I suppose if we can get a client of yours virtualised, that may do the trick (via VMWare tools).

     

    Paul Hoffmann

    LANDesk EMEA Technical Lead.

  • Jason SupportEmployee 396 posts since
    Dec 16, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    7. Mar 18, 2009 7:53 AM (in response to edwardsp)
    Re: Dos window pop-up

    Paul,

     

    As Paul H. stated I have ran that line on a client of mine and can not get the additional dos window to show up 8.8 sp2 with a few post sp2 patches(nothing PM related however).

     

    If you run that line manually can you duplicate this issue on your clients?

    C:\PROGRAM FILES\LANDESK\LDCLIENT\PWMCFG.EXE /set

     

    If so as Paul stated I would recommend opening a support ticket.

     

    Jason

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    9. Mar 19, 2009 3:28 AM (in response to edwardsp)
    Re: Dos window pop-up

    Well - you log it as a support ticket in the self-service portal as normal. Not quite sure where the question is - so if you could clarify here, that'd be good (it's early morning, I may have missed something obvious).

     

    Bear in mind that - as I pointed out - it would greatly help if you could have a virtualised client ready for us which displays the problem (you can virtualise clients via the following tool from VMWare that's free -- http://www.vmware.com/products/converter/ -- ), you'll probably want to upload this to our FTP.

     

    Yes, it is possible to change the local scheduler to run only every hour - that's a pretty simple change via commandline normally, but we'd need to know abit more information for this (as we need to address the correct task # ).

     

    So in order to help with that, please ensure you include a task-output list in the case you create - you can create that as follows:

     

    1 - on a client, open up a CMD window

    2 - Go to the LDClient directory (by default - "C:\Program Files\LANDesk\LDClient\").

    3 - Run the following command line:

    ""

    localsch /tasks >tasklist.txt

    ""

     

    This will create a text file called "tasklist.txt" with all of the local scheduler's tasks in human readable format, and will give us the info we need.

     

    Thanks.

     

    Paul Hoffmann

    LANDesk EMEA Technical Lead.

  • phoffmann SupportEmployee 2,643 posts since
    Dec 11, 2007

    Has received 7 of 9 achievements.
    Currently Being Moderated
    11. Mar 19, 2009 4:01 AM (in response to edwardsp)
    Re: Dos window pop-up

    Ahh right - now it makes sense.

     

    Support's contact details can be found here:

    http://www.landesk.com/Support/ContactUs/Index.aspx

     

    Access to the Self-service portal can be requested here:

    http://community.landesk.com/support/community/portal

     

    See the link for "How to access the Portal" - it'll tell you the information we'd need (which primarily boils down to the PMA #).

     

    If you're unsure about any of this, feel free to give us a call.

     

    NOTE -- if your shop does not have a Maintenance Agreement with us, I would imagine you have some support agreement with the LANDesk partner you bought LANDesk off, so you'd need to get in touch with them.

     

    I hope that this clarifies things .

     

    Paul Hoffmann

    LANDesk EMEA Technical Lead

  • Employee 5 posts since
    Nov 15, 2007

    Has received 1 of 9 achievements.
    Currently Being Moderated
    12. Mar 19, 2009 2:21 PM (in response to edwardsp)
    Re: Dos window pop-up

    you will not stop it because this command sets the client´s power scheme as defined in you LANDesk power policy deployed to your clients by calling the OS command powercfg.exe (which I assume is responsible for the DOS box you see, every hour because LANDesk offers to change the scheme every hour).   - there is a document under the Power Management section on this site which explains how this works.

     

    Detlef (from Germany)

  • Dave Holland SupportEmployee 822 posts since
    Jan 8, 2008

    Has received 9 of 9 achievements.
    Currently Being Moderated
    14. Mar 31, 2009 8:46 AM (in response to edwardsp)
    Re: Dos window pop-up

    Paul,

     

    What is your Support Ticket #?

     

    I have been unable to find our support ticket in our ticketing system.

     

    I will ask this question of the Power Management developers and find an answer for you.

1 2 Previous Next

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 20 points
  • Helpful Answers - 10 points
LANDESK Community powered by Jive SBS® 4.5.7.1  |  Legal Notices  |  Privacy Policy  |  Icon 

TweeterOn Twitter  |  Icon FacebookOn Facebook © 2007 LANDESK Software