Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. That sounds a lot like a "known" timings issue with SSD drives in combination with Applications. A workarround is a new variable, named SMSTSMPListRequestTimeout, that is introduced since R2 (see also: http://technet.microsoft.com/en-us/library/hh273375.aspx). Make this timeout higher and you should be OK.
  2. Did you clean up the AD after decomissioning your CM07 environment?
  3. Did it by any change restart before the application installations and do those devices contain SSD drives?
  4. It's not finding any applications... Look at the execution of the PowerShell script in the SMSTS log file. It might be that it ran in an error. Funny thing is that the task sequence will just continue...
  5. Use a Set dynamic variable step to set a task sequence variable based on the gateway. The variable can be used for the next steps.
  6. That's what the documentation is for I did a quick search for you and here is some Trend Micro documentation: http://docs.trendmicro.com/all/ent/endenc/v5.0/en-us/TMEE_5.0_IMG.pdf Chapter 6 is about the client installation and you should look specifically at the part about Automated Deployment.
  7. Multiple collections should definitly be possible. As it's been a while since I created that little script, I can't remember if I tested with multiple deployments to one collection. Theoratically, looking at the code, it should be possible,
  8. Did you configure the Software Inventory? Also I've got the feeling that this post is the same as this: http://social.technet.microsoft.com/Forums/en-US/5e3c4874-ef0b-4108-9309-05ec0cd8326c/conditional-windows-software-update?forum=configmanagersecurity#e6969024-75ed-4905-8214-f2c5cbfcea67
  9. Are the both deployed as available?
  10. Doesn't the EXE accept parameters?
  11. That's indeed the way to go, because the script queries for the collection membership of the user (and not the user group).
  12. No, but I can also not imagine a situation where you've got to add a driver package to multiple task sequences. Main reason because a driver packages is usually OS bound and in most cases a task sequence also...
  13. What if you deploy the EXE? Does it work then?
  14. No, I would just create a collection based on your requirement and use the current collection as limiting collection.
  15. I indeed thought you've still got to manually update the distribution point.
  16. Your welcome. I'm not sure about the maximum number of applications, I haven't stressed it yet. I would guess that it would be 99, but indeed knowing the normal limit it makes me doubt.
  17. There is no real documentation about which boot file is used, but the behavior that is seen is that the boot image of the task sequence that is advertised as last to the client is used.
  18. Actually it's still the pretty much the same as it was in CM07. The main difference is that you now also have boundary groups and that they are actually used for content assignment. Everything "under the hood" about DP selection is still the same. The principle of slow and fast boundary (groups) already existed in CM07.
  19. Are you deploying the task sequence to the collection in which the computer object exists?
  20. Could very well be a permission issue. The computer account running the script needs to have read permissions in ConfigMgr. This would probably mean that you would need to give the domain computers the read-only analyst rights.
  21. Correct, that's your input parameter.
  22. Those are two generic objects that are not location or ip bound, so that is not possible. You can filter in a task sequence itself on, for example the gateway of the client running the task sequence.
  23. Yes. They will scan with the SUP and download with their DP.
  24. You're doing something wrong with your input variables and I just noticed it based on the log file, while you already posted them before. It should be something like below. The resource name will be added as input variable. param ( [string]$ResourceName, [string]$SiteCode="YourSiteCode", [string]$SiteServer="YourSiteServer", [string]$Container="YourContainer" )
  25. If the clients are within the boundary group of the secondary site they should be looking at that server for their content. You can check the locationservices.log for the server that the client is really using for its download.
×
×
  • 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.