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
    Nice. Keep us posted.
  2. Peter van der Woude
    You don't need a SUP, but it would have been easy. It's also possible to deploy the updates directly via WSUS and install them during the task sequence. For an example see: http://desktopdeploy.wordpress.com/2011/09/03/use-existing-wsus-to-patch-client-during-configmgr-osd-task-sequence/
  3. Peter van der Woude
    Nope, only one task sequence per stand-alone media. Just create a small HTA to pick an office version and use that as input for the rest of the task sequence.
  4. Peter van der Woude
    The client installation is probably missing BITS. See for the prerequisites: http://technet.microsoft.com/en-us/library/gg682042.aspx
  5. Peter van der Woude
    As always, great post! Small add-on, with a little trick, of using the variable %computername%, it is possible to use the Client Push Installation. See this post: http://www.petervanderwoude.nl/post/using-client-push-installation-on-workgroup-systems-with-configmgr-2012/
  6. Peter van der Woude
    That doesn't look like an error to me... It's a return code 0, and that's a success. You might have to look at the client logs to see what the client is doing.
  7. Peter van der Woude
    So, yes, it means that the package is already successfully distributed to the DP.
  8. Peter van der Woude
    In other words, delete the deployment for the specific collection. This can be done by selecting the task sequence, select the deployments tab and right-click the specific deployment.
  9. Peter van der Woude
    The Content hash has ben successfully verified message shows when content validation is configured on the DP and the content has just been successfully validated.
  10. Peter van der Woude
    Sounds like your client isn't communicating to your Site... After installing the client first look at logs like ClientIDManagerStartup.log, LocationServices.log, ClientLocation.log for information about the assignment and site information.
  11. Peter van der Woude
    Indeed, when you already have the working task sequence, you only need to deploy the devices. It should be possible in 3 months, but always keep in mind that when you run into whatever problem, it might take time to solve it.
  12. Peter van der Woude
    I think you device is getting it's policies, yet. With workgroup devices there are two important things: You need to supply the FQDN of the MP in the installation properties (via SMSMP=) The devices need to be able to resolve de FQDN of the MP.
  13. Peter van der Woude
    You could sent a scheduled/ mandatory task sequence to the clients. But with this it all depends on what you migration project looks like, the timeframe and the people on-site.
  14. Peter van der Woude
    This post answers most of your questions: http://social.technet.microsoft.com/Forums/en-US/aa9aad06-5fc1-425f-83b0-59523724e9d6/problem-with-importing-custom-boot-image-made-from-dart-7 AFAIK, a small catch is that DaRT8 with Windows 7 might have some not working/ compatible tools.
  15. Peter van der Woude
    Take a look at this post, where David explains exactly this: http://www.david-obrien.net/2013/07/23/how-to-edit-configmgr-packages-update-on-schedule/
  16. Peter van der Woude
    I don't have an environment next to me at this moment, so I don't know the exact report, but there should be a report where you can see how many of the targeted devices already received the deployment.
  17. Peter van der Woude
    Correct.
  18. Peter van der Woude
    That message is nothing bad, it just means that the distribution manager has no packages to process.
  19. Peter van der Woude
    Nothing changed on that part. Do you by any change mean the sms_executive? If so, that's something totally different, but also on that area nothing changed.
  20. Peter van der Woude
    That makes sense, because what you see there is only the metadata of the update. When the update is really downloaded it has to be part of a Deployment Package.
  21. Peter van der Woude
    The SUP/WSUS will only get the metadata of the updates. That's is only the information about the update, like information about the OS, what it's for and where to download it. Then the ADR will really download the updates, add them to a package and deploy them to the clients.
  22. Peter van der Woude
    It's actually three phases: The SUP/WSUS will check with Microsoft for new updates. The ADR will download the updates and make them available to the clients. The client will check for available updates. An ADR doesn't matter when the client updates directly from Microsoft Update.
  23. Peter van der Woude
    The ADR makes the new updates available to the client and the Endpoint Protection interval makes sure the client will check for the new available updates.
  24. Peter van der Woude
    Two things: The default run time for a software update was about 20 minutes, I thought. I don't have a 2007 environment in front of me right now but you can find it in the properties of a update (tab maximum run time). The 1800 in the log file is in seconds. So actually it is 30 minutes.
  25. Peter van der Woude
    To remove the client create a package with a program to uninstall the client. You can use a command line like this for the program: scepinstall.exe /u /s.
×
×
  • 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.