Deployment Solution

I need to make a job that will change which server the Dagent is pointing to.  We are currently only pushing Dagents to Windows 7 (preinstalled on our image) so I have already created a job for XP computers to push the inp file, and then the second tasks deletes them from the DS.  This way I know which computers have run the job.  The problem is, I can't push the inp file to the dagent (at least to where it works).  I have tried changing the registry to point to the new server, but haven't had any luck with that, and the job never sees it as actually completing the job as it is waiting for it to report back in.  Even if I restart the services, it just reports back into the original DS.  I know I can select a group of computers and point them to the new DS through the agent settings, but then I have no way of knowning which ones have actually reported in, and which ones are still waiting.  Hence the need to do this in a DS job.

I am going to a newly built DS 6.9 SP4 server, from a DS 6.9 SP4 server.  New name and IP. From Server 2003 to Server 2008 R2.

From the DS console you could change the DAgent properties and also change the DS target. will that work for u?

Highlight a client | Change Agent Settings | Production Agent | change the addess/hostname of the DS

nelson v.

Not sure how you have the DAgents pointing to the server currently (i.e. via IP or via Hostname).  If you are using a hostname, have you thought about putting a CNAME entry in that points the old servername to the new servername?  Another option might be to do the multiple computers and change their agent settings, then on the new server, drag and drop a new job that executes a SQL query to delete the computer out of the old SQL database.  Might be closer to what you are looking for.