Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. AFAIK this is always an extra manual (or scripted) action.
  2. Yes that's possible. The only thing you have to look at are the Boundaries/ Boundary Groups, see also: http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/
  3. Depends. Are you only using the integration so you have the extra scripts etc., or also the database?
  4. That message just means that there are at least two deployments to that machine (or the combination of the machine and user) of the application.
  5. You need at least one of the following SQL version: SQL Server 2008 SP2 with CU9, or SQL Server 2008 SP3 with CU4, or SQL Server 2008 r2 SP1 with CU6
  6. AFAIK there is no way of publishing BITS 2.5 via WSUS. You need to deploy it via your old software distribution tool, or manually or whatever… but it needs to be done before installing the new client...
  7. Run it before the Setup Windows -step. To pass the variable on in the Task Sequence use the last part of the script of parko89.
  8. Are you using the default install.wim? If so, then that's your problem. You need to capture your own WIM file, as the default one will always install on D:...
  9. You can use both… the difference is that the exe also checks the prerequisites.
  10. The old client will be upgraded.
  11. What does you package looks like (folders and files) and what is the commandline you're using?
  12. Depends. Is there nothing you need to migrate?
  13. If you're not using MigApp, there won't be any settings of that migrated. Also the reason for not using MigDocs and MigUser together is that you might migrate data double...
  14. You should be able to use Client Push to upgrade the client. If nothing happens, check the ccm.log
  15. You can indeed just run your own custom script from a package or commandline in the task sequence, or you can use the builtin options from MDT for that. If you have MDT integrated, you can use the Gather step to get you a new variable called AsstTag.
  16. I would indeed also use multiple applications with relationships, because keeping them separate gives you more possibilities for examples easy upgrade one part of the installation.
  17. That's not a real error, it just happens when nobody was logged on.. Also I'm wondering what your issue is. This topic is about software advertisement, but when I'm reading your post it looks like you're having problems with software updates...If so, then you shouldn't be looking at the execmgr.log, but at the software update logs.
  18. There is no need for creating new packages every month, but it is needed to clean them every month. And with that I mean removing superceded and expired updates and adding new updates.
  19. Take a look at the ConfigMgr 2012 SDK (which is still a pre-release): http://msdn.microsoft.com/en-us/library/hh948960.aspx
  20. The biggest issue with overlapping boundaries are in the Site Assignment, which occur when a client is in multiple boundaries and by that assigned to different Sites. But if you can cover everyting with IP Subnets- Range I would always prefer that above AD Site. I wrote a post about overlapping boundaries in ConfigMgr 2012 here± http://www.petervanderwoude.nl/post/overlapping-boundaries-and-configmgr-2012/
  21. ConfigMgr still uses the SYSTEM account to perform it´s actions to install software during a Task Sequence. You do need to specify a Network Access account in ConfigMgr, which will be used to access the DP during a Task Sequence.
  22. It's all about fitting it to your needs. The easiest way to deploy different policies to different machines is by using different collections. How you fill these collections doesn't really matter, as long as it makes sense to you. AD Groups can make it easier to manage when more settings for those specific servers depend on it...
  23. Distribution Points in ConfigMgr 2012 are using a contentlibrary with single file storage
  24. That's possible. Wether it's smart or not depends if your lab environment equals your production environment somehow.
  25. That's possible, with for example a run commandline step in a Task Sequence.
×
×
  • 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.