Deployment Solution

When I push a client to a windows 7 machine, it sets a static route in the client record on the deployment server. All configure jobs then fail with incorrect function. . If I remove the route from the client, all deployment jobs work fine, however I no longer have access to the user network as the gateway is no longer set. If I add back the gateway it adds back the static route and I am unable to run configuration jobs. I am using DS 6.9 SP5 and the client has the lastest version 6.9.496.

Hi,

At times we have seen similar issues, but not only on Win7 clients. There were 2 things to check:

1. How many machines do you serve with trial license or expired license?

2. Sometimes we do have to re-apply the license to get jobs work again.

Hope this is of some help?

-BBC

It is not a license issue and it only happens on Windows 7 machines.

After looking at the problem closer I discovered that it Windows that is creating the the persistent route. So anyone using DS 6.9 should be seeing this problem and if so how did you get around it. Do a route print under the command prompt and you should see your default gateway listed. XP machines do not do this.

All Configuration jobs are failing for me. There's a kb article that says that the agent and Deployment Console don't match, and if you make sure they match, config jobs start working again. Mine do match, but config jobs still fail.

These are Windows 7 Professional, 64bit, and I'm just trying to get them to join the domain.