Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. You could trigger the client actions to request the policies, to scan for updates and to check the update deployments.
  2. What about the MP itself, does the MPcontrol.log show any further errors?
  3. I've seen tons of cases where there was an overlooked misconfiguration in the boundaries... can you please be more specific about the configured boundaries?
  4. Then dive deeper into the latest version. First of all, its the easiest to setup and second it saves you problems with legacy stuff...
  5. If the machine already exists you can simply move it in the console by right-clicking it.
  6. You can use the same package, but you've got to make sure that the ADRs are not running at the same time. Otherwise they might interfere with each other.
  7. You should adjust the selection criteria of the ADR.
  8. Supersedence shouldn't cause application to update without the new version being deployed to the device. There are some funny things with applications that are part a deployed task sequences that you should look out for..
  9. Is the client installed in the parent VM? If so, have a look at this: http://www.myitforum.com/forums/m237703-print.aspx
  10. To see if the script works with SYSTEM credentials, try running it with PSEXEC.
  11. You definitely should be looking at the SMSPXE.log. This log file should be located in the normal logs folder on the server-side.
  12. You could use a "fake" ADR to simply download the content to the package(s).
  13. The ContentLib is the content library. The content library is available on every site server and distribution point and simply stores all the data of your packages. I wouldn't manually remove those files.
  14. That will happen anyway, no matter what kind of server you put anywhere, every site server and every distribution point has a copy of the content library. So whatever you want to think of, it will happen anyway
  15. In that case, if you're looking for a free solution, look at SCUP.
  16. What do you mean with a management server? Like a mentioned a terminal server with a console? If so, then the console performance will be better when the terminal server is in the US.
  17. You mean the metadata via WSUS, or the real content?
  18. It could be that it can't find the updates and that's why you could look at the variable I mentioned.
  19. If the machine account has access to that share location, then yes. Otherwise make sure the patch is part of your client package and refer to the local location.
  20. You can simply remove the membership of those updates to that group. The ADR won't do that.
  21. What's the error that you get? If it;s about an issue with locating the files then you can try to use the %~dp0 variable.
  22. You can use the PATCH parameter to update the client during the task sequence.
  23. Not seeing anything in this log file. Any more log files available? Also, check if the client installation already started and if so check the log file.
  24. Well, you've answered a big part of the question yourself as it depends a lot on the network speed and latency. Something that could make it more acceptable is to use a terminal server in the US for them to connect to and to manage ConfigMgr. That will already solve a big part of the problem.
×
×
  • Create New...

Important Information

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.