Dagent = Massive Problems :(
Here's my situation:
We've been running Deployment Server 6.9 (no sp) with Windows XP clients (all using aclient), everything works great.
A while back I tried to upgrade to 6.9 SP1 and found that having all the clients upgrade to dagent caused massive cpu spikes on our deployment server (Windows 2003 R2, SQL Server 2005). I couldn't resolve the issue, so I reverted back to 6.9 where we've been until now.
I've been starting to prepare our Windows 7 build model and I've built a brand new virtual server for DS 6.9 sp3 (Windows 2008 R2, SQL Server Express 2008). I have been testing with only one client and I've found some pretty massive issues with dagent.
*The cpu pegging bug is still present in sp3. I've narrowed it down to using encryption with the clients. If my lone test client is set to use encrypted communtications with the server, the server will become unresponsive with massive cpu usage in short order. If I turn encryption off on the server and the client, everything works fine. The server stays reponsive. This was never an issue with aclient.
*The remote control feature simply does not work. I'm not sure if I'm missing something basic, but it appears that the remote control feature is simply broken. After right clicking and selecting remote control, it waits for a while, and then eventually fails.
*The server reports the client as being active even while the client is in a suspened state and I can no longer send a wake-on-lan. (not sure if this is a client or server issue)
I have all the latest hotfixes and it still seems like dagent isn't quite ready for primetime. Am I alone with these issues? Maybe SP4 will be addressing many of these problems?
Comments
Dagent remote control Windows 7
If you want to remote control Windows 7 user must be logged in.
You cannot start remote control session if Windows 7 is at login screen.
no dagent problems here
We don't have any problems with the Dagent on our server or clients although we do not use the encrypt session. As for the remote control, what Pashyn said is true, there is no remote control prior to login on Windows 7, if you have issues even when someone is logged in, you might want to restart the server or all the DS services. I had problems with our DS not allowing for remote control of any clients until we did a reboot (I thought it had been rebooted a few times before) and it finally started working. Also make sure your agents are up-to-date for remote control to work correctly.
Well encryption is simply
Well encryption is simply going to be a no-go with Dagent. Remote control is not going to work either.
Aclient could not remote control 1920x1200 desktops and it appears dagent has the same limitation. Very unfortunate.
Remote Control not working until reboot
We experienced similar issues with Remote Control not working with Win7/dagent and found that the problem is actually related to the dagent not updating the inventory for a machine. If you right click on a workstation in the DS console and choose Advanced -> Get Inventory, remote control should work after that. Of course there is still the problem of not being able to remote control a computer at the login screen - but at least this should fix the problem when a user is logged in.
As for remote control at
As for remote control at 1920x1200, just set your color depth to 8-bit (View -> Color Depth -> 8bpp) when remote controlling and you will be able to remote control. This works on both XP (aclient) and Win7 (dagent) machines. (It's ugly - but functional)
Would you like to reply?
Login or Register to post your comment.