I need some clarification if you don't mind. Install a windows agent (if it doesn't talk then we can at least look at a wireshark or agent logs) Make sure the latest 3.3 RU2 was installed. If it was my environment I would restart the server services. If there were several clients and they were all working just not the boot dvd then it could be one direction of things to look for related to drivers on the boot disk (even though it is able to get to the M drive I have seen built in drivers perform poorly and updateing them fixes issues) but since there aren't any clients to comare if the server is talking to any one there is a lot of unknown. Restarting them then takes care of that issue if that was what is going on.īeing that there aren't any clients it is hard to know. Restart the services on the server system? I have seen where the services will be listed as running but they won't be working. So was your boot DVD created with this same version of the server? If the server was updated as an example maybe the client boot dvd would have an outdated agent in it? Just trying to think of things that could be problematic.ĭoes the client system when you install the agent show up in the console?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |