Jump to content


Peter van der Woude

Moderators
 View Profile  See their activity

  • Posts

    2925

  • Joined

  • Last visited

  • Days Won

    79

 Content Type 

Everything posted by Peter van der Woude

  1. Peter van der Woude
    You can click the queries together in the Criteria tab and you will get something like this (for Server 2012): select * from SMS_R_System inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_OPERATING_SYSTEM.Version like "%6.2%" and SMS_G_System_OPERATING_SYSTEM.Name like "%Server%" Also you don't need to split up you collections, as the client will only install updates that it needs (and are relevant).
  2. Peter van der Woude
    It's a no go and it won't work either, as the client will never know that the sources are there. The client checks with the MP (which checks the DB) for available locations and if you manually copy files it's never registered and in the wrong format. Why not just schedule the deployment to one DP alone, if that's all you want??
  3. Peter van der Woude
    It all depends on the requirements and possibilities... It's also possible to just deploy a site system with a dp/mp, or even point them to your existing site...
  4. Peter van der Woude
    Have you seen this: http://social.technet.microsoft.com/Forums/en-US/74268c42-14f9-4822-88ea-4093970ae767/sccm-2012-network-access-account-password-problem
  5. Peter van der Woude
    To keep it al nice and easy, there is another method to install .NET 3.5 during a task sequence and that is with using the MDT integration. Select the .NET 3.5 feature in the Install Roles and Features -step and create a Task Sequence variable that set the variable WindowsSource to the (networkshare) location with the SXS folder.
  6. Peter van der Woude
    When you migrated the information, then, yes the client knows the history. Otherwise use a new application and configure a detection rule.
  7. Peter van der Woude
    That's why you should beat Niall with installing it first
  8. Peter van der Woude
    When the client installation starts, check the log files (in the ccmsetup folder).
  9. Peter van der Woude
    It's even here in the guide: http://www.windows-noob.com/forums/index.php?/topic/8451-how-can-i-install-system-center-2012-r2-configuration-manager/
  10. Peter van der Woude
    You first need to uninstall the old Windows ADK and then install the new Windows ADK for Windows 8.1.
  11. Peter van der Woude
    Sorry, missed that part... No need to look in that log file when you are booting from a media. There should be local log files, like a smsts.log on the system then.
  12. Peter van der Woude
    Global Conditions are not meant for targeting... I think this post will answer your question: http://social.technet.microsoft.com/Forums/en-US/3a737afa-26e8-4881-9105-a9c42055ca67/how-to-create-a-global-condition-based-on-computersusers-active-directory-group
  13. Peter van der Woude
    I would try to scope the job to things that I know, I can deliver within a specific time (like an installation, os deployment, that many different driver packages, etc). The rest that the customer wants can be done against a rate per hour.
  14. Peter van der Woude
    - Procedure is fine. - The SMSPXE.log - Sometimes it helps to first update and refresh the All Systems and the specific deployment collections. - Normal
  15. Peter van der Woude
    They can run perfectly fine next to each other. Just make sure that the boundaries for (auto) assignment do not overlap, as that's the part that causes all the problems. Something that can stop the most problems is to not let your 2007 site sign in the ad, then there is no automatic way that your clients find that site (unless manually specified during the client install).
  16. Peter van der Woude
    When the client install is enable in your client settings, then run a machine policy update and it should start within a few minutes.
  17. Peter van der Woude
    It is possible to import and export lots of objects (including their content). I've just never had any reason to do that, because every customer is different. Every customer has its own applications, applications get renewed, deployment requests, etc.
  18. Peter van der Woude
    Yes, that is possible if you're not using SCCM for your deployments.
  19. Peter van der Woude
    I would start by checking the WindowsUpdate.log.
  20. Peter van der Woude
    Or just configure the Apply Windows Settings -step in the task sequence.
  21. Peter van der Woude
    Start by looking at the WindowsUpdate.log for errors. Also, it seems to timeout, which could also indicate that it's somehow waiting for input.
  22. Peter van der Woude
    The SYSTEM account of the site server.
  23. Peter van der Woude
    If you're not using it, yet, then just start over. Saves a lot of unnecessary troubleshooting.
  24. Peter van der Woude
    Not sure, you might check if there is something like that between the Status Message Queries. Also, it doesn't have to be that somebody enabled and disabled the (automatic) Client Push Installation, it can also be that somebody right-clicked a collection and did an Install client action.
  25. Peter van der Woude
    You shouldn't configure WDS. Just install it, don't touch it, install a PXE service point and let it use WDS.
×
×
  • 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.