Jump to content


Peter van der Woude

Moderators
  • Posts

    2925
  • Joined

  • Last visited

  • Days Won

    79

Everything posted by Peter van der Woude

  1. Make sure that it;s within the OU's that are configured in the discovery. For more information check the adsysdis.log file.
  2. I agree with Garth, look at DirectAccess. If that's not an option, look at Internet Based Client Management.
  3. Then check the SMSTS log file on the client if it recieves an task sequence deployment and check the SMSPXE log file on the server to see if it finds a deployment for that machine.
  4. I'm not really following the idea of putting everything in workflows, but I can imagine that it can be helpful. One thing you do have to look at are the things you can deploy to collections, because you;re missing a lot
  5. Yes, Internet clients are possible and in this scenario your only solution.
  6. I think it;s because of your setting with date released or revised. Also, there is a nice preview button in the ADR to show the results of your criteria.
  7. Do you now have your F8 enabled and can you run an ip config?
  8. I've heard that migrations also work when done from a SP1 site to a R2 site, but officially only migrations from the same version are supported. In that case I would start my new site as clean as possible, with as little as possible changes (meaning upgrades). So, I would start at R2 and upgrade the old also to R2.
  9. Yes, the easiest method is to completely automate the process. Create a build and capture task sequence and use that for your PXE deployment.
  10. Do you see anything arriving at your server-side, maybe in the SMSPXE.log?
  11. That's default behavior and by design. It can't be changed.
  12. Use something like this select Model from Win32_ComputerSystem where Model = "<yourmodel>"
  13. Assuming that you used multiple primary site for the right reason, then yes, install the software update on every primary; Metadata only; It's a filter, so new updates that are within that filter will show, but they won't automatically go to the software update group; Yes, you should distribute the packages to the distribtution points; Yes.
  14. I think I finally figured out what you meant, it's a role that existed in ConfigMgr 2007 (see also: http://technet.microsoft.com/en-us/library/bb680491.aspx).
  15. I don;t see any link with WMI, I would assume that the VLAN switch is the problem. Do you have IP Helpers pointing to the PXE server in the new VLAN? Is there a firewall between the VLANs? You should be able to press F8 before the rebooting starts... You sure you enabled it in the boot image and distributed it?
  16. Have a look at the ServiceWindowManager.log for some more information about the service windows and the availability of them. It might shed some light on the message you;re seeing.
  17. If you press F8, while in WinPE, you should get a command prompt (that's the whole feature). Via that prompt you should be able to navigate to the location of the log file.
  18. You probably need an IP Helper (or DHCP option) to point to your PXE server. For more information, see: http://social.technet.microsoft.com/wiki/contents/articles/12152.pxe-fails-with-pxe-t04-access-violation-and-pxe-e36-error-received-from-tftp-server.aspx
  19. That role doesn't exist, like I mentioned the first time. To manage mobile devices, like iPhone and Android, you need Intune (integration). For more information about Intune see: http://www.microsoft.com/en-us/server-cloud/products/windows-intune/
  20. Do you have F8 enabled in your boot image? If so, use it and try to find the SMSTS log file.
  21. The old applications will still exist if that's what you are asking. Also, see for more information: http://technet.microsoft.com/en-us/library/gg682071.aspx
  22. What kind of information does the WindowsUpdate.log provide?
  23. The whole idea of the application catalog is to target the user, not a different user... AFAIK there is no way arround that.
  24. What's in a firstname... I'm sorry, but I don;t understand what you're saying. The boot images are not listed on the distribution point? If so, then distribute them to it, as they have to be there.
×
×
  • 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.