Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Resume from standby issue

Created: 09 Dec 2010 | 5 comments
jasonfo's picture
0 0 Votes
Login to vote

Deployment Solution 6.9 SP3.

When we use Verdiem Surveyor to put a system to standby then wake it up dagent does not work properlly. 

 

We get a message saying "waiting for clients to accept connection..." or we get a black screen with nothing else.

Comments

Thomas Baird's picture
09
Dec
2010
0 Votes 0
Login to vote

are you putting the DS to sleep, or the clients?

"Waiting for clients to accept connection" or black screen - sounds like the DS console.  Why on earth would you put a server to sleep?

Thomas Baird
Endpoint Management Specialist 

Remember to give a thumbs-up to any post that is helpful.
It notifies readers of the forum that there's useful information in that thread.

jasonfo's picture
09
Dec
2010
0 Votes 0
Login to vote

Issue when the client resumes

Issue when the client resumes from standby we cannot remote into the client pc using out deployment console software. Not putting the server to sleep.

Thomas Baird's picture
09
Dec
2010
0 Votes 0
Login to vote

oh - this is a remote control issue!

Sorry, the title and description didn't mention remote control.  All of the symptoms now make sense.

 

What OS is on these?  Can you use AClient instead of DAgent?

Thomas Baird
Endpoint Management Specialist 

Remember to give a thumbs-up to any post that is helpful.
It notifies readers of the forum that there's useful information in that thread.

jasonfo's picture
09
Dec
2010
0 Votes 0
Login to vote

XP on the OS. Client is

XP on the OS. Client is Aclient. I was looking at a Windows 7 system when I wrote "dagent".

Thomas Baird's picture
14
Dec
2010
0 Votes 0
Login to vote

I have no information on this.

I'm sorry.  I've looked.  A guess would be that the way the program is putting the system to sleep is cutting the connection without letting AClient know it has been cut.  Thus, when AClient comes back up, it "thinks" it's still connected and then doesn't try to connect.

But that's my guess.

There is a refresh interval for the agents you could try to establish, or you could perhaps run a script that relaunches AClient when it wakes up, but I'm frankly not sure.

Thomas Baird
Endpoint Management Specialist 

Remember to give a thumbs-up to any post that is helpful.
It notifies readers of the forum that there's useful information in that thread.