Jump to content

SteveBancroft

Members
  • Posts

    14
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Hello, Our machines with defs v2013.12.09.X have been reporting Trojan.MSIL. The detection seems to be from a Realtek audio driver. We have been using this driver for ages without any issue. To confirm, I redownloaded the driver from Lenovo and Realtek and had the same results. Clients are running 1.75.0.1300 with the 1.3.0.1936 server compatibility. MBAM-log-2013-12-09 (16-29-04).txt
  2. Thank you Jeffrey, that is quite helpful for a quick glance. Now if only we could simply right click on clients and push the upgrade that way... :-)
  3. Thanks Nick. That could be quite helpful for our planned upcomming SCCM push.
  4. We had something similar. We used group policy (GPO) to set the MEEClientService service to delayed start. It resolved the issue for us. I cannot say 100% if this is the same issue, but its worth a shot.
  5. Hello, We recently upgraded our MEE server to the latest 1.3 version. With it, a "different" version of the MEE client is available. The problem is that for whatever reason, the decision was made to not increment the version number of the client. Even though there are changes, new features, and different communication, you chose to keep the client as 1.75.0.1300. This is extremely confusing because from the MEE Server console, or even the client itself, you have no way of knowing if it is running the "new" 1.75 or the "old" 1.75. We are trying to figure out a way of deploying this "update" to 5000+ computers, but we cannot even scan for a certain version of the client! Scanning and deploying from the console is NOT a solution, we cannot do this one-by-one and only detect clients that are online at that time. I am asking that you reconsider this approach and version up the client properly so we can all differentiate which client is which.
  6. Interesting. Thank you for all your help Mehtab. We will plan our upgrade.
  7. Yes I believe so. Would that client be fully compatible with all the new features? My concern is this. If I use the scanner to push the "new" 1.75.0.1300 client from the 1.3 EE server, wouldnt it just say the client is already up to date?
  8. I think that is a pretty major oversight to not increment the version number of a client when something has changed, and there is no other way to differentiate. Are your 1.75.0.1300 clients which were not deployed from the 1.3 sever compatible with the Active Directory integration?
  9. It looks my clients are 1.75.0.1300. Is 1.75.1300 the latest version or was that shorthand like mine was?
  10. I other words, are ALL 1.75.1300 clients already compatible with the new server, or must it be redeployed from the 1.3 EE server to be fully compatible?
  11. Mehtab, Thank you for your reply. The only thing I really do not understand is the versioning of the client. I have already been deploying client version 1.75.1300 to my clients from the 1.2 EE server. Is this same exact client the one that is fully compatible with all features of the 1.3 EE server? If not, why did the version number of client not change?
  12. Hello everyone, We are planning our upgrade to the latest version of the EE Server and I have a few questions. The sticky note here specifically states that the clients need to be upgraded to utilize the new features. We are very excited about AD integration. What I have noticed though, is that the client version has not changed. How am I supposed to tell which client is updated to use the new features? Also, I want to make absolutely sure that if I do an in-place upgrade to the latest server version, that all my clients will continue to at least function. We have 5000+ clients, so reinstalling them is no easy task. How will the server console differentiate which clients are compatible with the new features, and which ones are not? Will I be able to locate the old clients and push the updated client through the console easily? Please let me know how to go about this. Thank you, Steve
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.