Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

GarW's Achievements


Newbie (1/14)



  1. Hi Customer has SCCM 2007 SP2 running successfully for some years. However, they want to deploy a fresh SCCM 2007 SP2 installation (with a new site name), unconnected to the original though in the same domain. They are happy to leave the old data behind (collection's packages, Advertisements etc. etc.). They just want a fresh install. They have deployed a new server and are ready to move the site boundaries, and publish the new site data to Active Directory and DNS (removing the old data). What is the best way to handle the clients? Once discovery on the new server takes place will they be visible on that server? Do they have to initiate a Push Installation of the client? I've seen references to having to run a script to change the Site code on the client - is this always necessary? I'm looking for a definitive strategy to handle this if possible, with minimal touch of the clients (XP, W2K3, W2K8). (I've seen and read a lot of threads on a few sites but no definitive answer I can find - if there is one I've missed just point me to it!!) Many thanks in advance
  2. Thanks to all who posted. Got the following from a guy at MS which pointed me to the probem. I had run out of TCP ports and PXE couldn't bind to port 4011. I moved the WDS/PXE Service Point to a new dedicated machine and sorted the problem (Naturally I also had to change the IP Helper address on the router to point to the new IP address of the PXE Service Point - left the helper address to the DHCP server as is). Error 10048 signifies "Only one usage of each socket address (protocol/network address/port) is normally permitted." It indicates that the PXE Service Point is unable to bind itself on port 4011, which is used by PXE Service Point. Do one of the following: Enter the following command in the command prompt on a Windows XP or Windows Server 2003 computer to display the active connections being used by the TCP/IP protocol on this computer: netstat -n This will list the TCP/IP addresses bound to the client computer and the ports on which the TCP/IP addresses are communicating with a remote server. If the listed ports consume all of the available ports then TCP/IP port exhaustion occurs. Enter the following command in the command prompt on a Windows Server 2003-based client computer to display the active connections being used by the TCP/IP protocol: netstat -b This will list the TCP/IP address bound to the client computer, the port on which the TCP/IP address are communicating with a remote server, and the application that is using the ports. This information can help determine which client applications are consuming excessive TCP/IP ports. Disable all 3rd party applications running on the WDS/PXE Service Point Server and try again.
  3. Hi, Thanks for the response. Yes it has - I'm trying to get it to boot to a bare metal build. Advertisment seem OK, MAC address entered properly. Have checked for any old records with that MAC address but none there. Just to satisy my curiosity, would you have any guidance on whether the error event on the PXE_SERVICE_POINT is normal - "PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 10048.". Your interest is really appreciated.
  4. Hi all, Have the common PXE-E53 "No boot filename received" issue, but can't get to the bottom of it this time. DHCP Server and PXE Service Point on different servers, in same subnet. Client in different subnet, IP Helper configured forwarding to both. (Have tried using DHCP Options 60,66,67 with no difference). On SCCM PXE Service Point, WDS running without error. PXE Service Point running, but the following error "PXE Control Manager detected PXE service point is not responding to PXE requests. The error is 10048." PXEControl.log has the following which seems to indicate a bind issue? ) SMS_PXE_SERVICE_POINT successfully STARTED. ******************************************************************************** Configuration and Availability Monitor thread started. Initialized 'SMS Server Availability' performance instance => SMS PXE Service Point. adding address to server list adding address to server list Bind Socket Failed Error initializing PXE client Bind Socket Failed Error initializing PXE client Pxe test request failed, error code is 10048. STATMSG: ID=6319 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PXE_SERVICE_POINT" SYS=xxx36 SITE=SV0 PID=4600 TID=1676 GMTDATE=Fri Nov 12 16:26:29.760 2010 ISTR0="10048" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_PXE_SERVICE_POINT PXE test request failed, status code is -2147014848, 'Error initializing PXE client'. Successfully performed availability check against local computer. Initialization still in progress. Thanks in advance for any ideas of what to check next.
  5. That was just the trick - thank you. Created a new collection with the query "select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMSAssignedSites is not NULL and SMSUniqueIdentifier is NULL". Pointed the latest version of SCCM Collection Commander from http://smscollctr.sourceforge.net/ at this collection and did new GUID generation for the clients in the collection. I had to refresh the Data Discovery Record afterwards and the clients are all reporting correctly now. Thanks very much for the prompt reply and solution - saved me a load of time and made me look like a hereo!
  6. Hi Customer carried out "unusual" upgrade process for sms2003 to Sccm2007R2. Cutting a long story short, many clients think they are in the new SCCM site with the SCCM agent installed successfully. However, although discovered in SCCM, console reports that they do not have agent installed even though it is. SMS_INVENTORY_DATA_LOADER shows many 2703 events. Have found that by regenerating a new GUID on the client they will report properly. Hovever only method I know to do this using Right-Click tools which can only do one client at a time. There are about 2000 clients in this state - another 2000 are fine. Anyone any recommendations on how to tackle this? Thanks in advance.
  • Create New...