Jump to content


daniz

Established Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by daniz

  1. Not sure but i think you have to use different advertisements/collections if you want to use different boot images and not advertising both TS at the same time to the computer. Try to fix your boot image instead search the .inf files to see if the same vendor id is in different drivers. Try to use as few drivers as possible. Add and remove drivers until you get it working.
  2. WDS cache issue, restart WDS service to see if it helps. For a more permanent "fix" http://blog.danovich.com.au/2010/03/23/windows-deployment-services-wds-cache/
  3. Go to update repository > search folders > right click > create new search folder. Check the box you want and then click the blue link in the bottom field. Here you can add a list of criterias. Good Luck!
  4. 1. To explain: you only need to clear a pxe boot when using mandatory advertisement. If you have the problem try restarting the WDS service of the PXE server. If it works it is the WDS PXE cache that is causing the problem. http://www.myitforum.com/articles/1/view.asp?id=12603 http://blog.danovich.com.au/2010/03/23/windows-deployment-services-wds-cache/ If this is the problem make sure you change the correct registry key. The key is different for x64 and x86 versions of windows server. 2. Hopefully solved by 1. 3. I would start by looking at the client c:\windows\system32\ccm\logs\locationservices.log check so the client is in a defined site and so on.
  5. I would check locationservices.log to see that the client is recieving FQDN for the MP. Use the trace32 log parser from SCCM toolkit v2 to view the log files. My guess is that your boundaries are wrong. I know that using 10.1.2.0 with subnet mask 255.255.248.0 doesn't work as it should. I think this will result in the boundary actually beeing 10.1.2.0 with subnet mask 255.255.255.0. If this is the case switch to using IP-ranges instead.
  6. 1. Are you using non-mandatory OS advertisements? If you are pressing F12 two times to enter the installations there is no PXE advertisement to clear. If you are using mandatory advertisements and you can't clear it I have to agree it is strange. I have seen strange behavior if you have duplicate objects, some beeing obsolete, but then you simple have to clear all of the objects with the same name. Remember to update All systems collection to make sure you are seeing any duplicate objects. 2. I find removing and then re-adding computer objects and adding them to a collection in the wizard is a bit buggy, so I think this behavior is "normal". 3. If you are using mandatory advertisements they are not going to show in the run advertised programs. If you are using non mandatory advertisements i have to agree it is strange but start by checking log files to make sure there is nothing wrong with boundarys and so on.
  7. OK, A couple of things: Is the client on the same subnet as the PXE-server? It doesn't say in your text. If not then make sure a IP-helper for the client subnet is pointing to the PXE-servers IP. Is the WDS service started on the server? Are there any WDS log entrys in the application event log of the server?
  8. Go to %windir%\system32\CCM\Logs on the client and look at LocationServices.log to make sure the client is assigned to the site (use the trace32 log parser inluced in the sccm toolkit v2). If it doesn't find the site i would look at boundaries again. And what parameters do you use when you install the client? Have you installed the server locator point role on the SCCM server and is the AD schema extended?
  9. Are the boundary set for the subnet/AD site where the clients in the child domain are located? Does the client push account have permissions on the clients? You can define several accounts for client push if that helps
×
×
  • 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.