Jump to content


Recommended Posts

Hi, I have enabled PXE, I have confirmed my boot image is setup to work with PXE.  I have confirmed that my c:\RemoteInstall folder is filled with content.  My SMSPXE log shows this.

TST0005 is my x64 boot image

 

Found new image TST00005    SMSPXE    6/17/2021 7:23:19 AM    3368 (0x0D28)
Loaded Windows Imaging API DLL (version '10.0.19041.1') from location 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll'    SMSPXE    6/17/2021 7:23:19 AM    3368 (0x0D28)
Opening image file C:\RemoteInstall\SMSImages\TST00005\boot.TST00005.wim    SMSPXE    6/17/2021 7:23:19 AM    3368 (0x0D28)
Found Image file: C:\RemoteInstall\SMSImages\TST00005\boot.TST00005.wim
 PackageID: TST00005
 ProductName: Microsoft® Windows® Operating System
 Architecture: 9
 Description: Microsoft Windows PE (x64)
 Version:  
 Creator: 
 SystemDir: WINDOWS
    SMSPXE    6/17/2021 7:23:19 AM    3368 (0x0D28)
Closing image file C:\RemoteInstall\SMSImages\TST00005\boot.TST00005.wim    SMSPXE    6/17/2021 7:23:19 AM    3368 (0x0D28)
Found new image TST00019    SMSPXE    6/17/2021 7:23:20 AM    3368 (0x0D28)
Loaded Windows Imaging API DLL (version '10.0.19041.1') from location 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll'    SMSPXE    6/17/2021 7:23:20 AM    3368 (0x0D28)
Opening image file C:\RemoteInstall\SMSImages\TST00019\OEM_BOOT_IMAGE_x64.TST00019.wim    SMSPXE    6/17/2021 7:23:20 AM    3368 (0x0D28)
Found Image file: C:\RemoteInstall\SMSImages\TST00019\OEM_BOOT_IMAGE_x64.TST00019.wim
 PackageID: TST00019
 ProductName: Microsoft® Windows® Operating System
 Architecture: 9
 Description: Microsoft Windows PE (x64)
 Version:  
 Creator: 
 SystemDir: WINDOWS
    SMSPXE    6/17/2021 7:23:20 AM    3368 (0x0D28)
Closing image file C:\RemoteInstall\SMSImages\TST00019\OEM_BOOT_IMAGE_x64.TST00019.wim    SMSPXE    6/17/2021 7:23:20 AM    3368 (0x0D28)
Boot image TST00002 has changed since added    SMSPXE    6/17/2021 7:23:22 AM    3368 (0x0D28)
Loaded Windows Imaging API DLL (version '10.0.19041.1') from location 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll'    SMSPXE    6/17/2021 7:23:22 AM    3368 (0x0D28)
Opening image file C:\RemoteInstall\SMSImages\TST00002\boot.TST00002.wim    SMSPXE    6/17/2021 7:23:22 AM    3368 (0x0D28)
Found Image file: C:\RemoteInstall\SMSImages\TST00002\boot.TST00002.wim
 PackageID: TST00002
 ProductName: Microsoft® Windows® Operating System
 Architecture: 0
 Description: Microsoft Windows PE (x86)
 Version:  
 Creator: 
 SystemDir: WINDOWS
    SMSPXE    6/17/2021 7:23:22 AM    3368 (0x0D28)
Closing image file C:\RemoteInstall\SMSImages\TST00002\boot.TST00002.wim    SMSPXE    6/17/2021 7:23:22 AM    3368 (0x0D28)
============> Received from client:    SMSPXE    6/17/2021 7:28:34 AM    5424 (0x1530)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 210F658A
 Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 88:ad:43:f6:ce:2e:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 1=Discover
  Type=57 Max Msg Size: 05b8
  Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
  Type=97 UUID: 0044454c4c5200104c8057b2c04f4e5931
  Type=94 UNDI: 010310
  Type=93 Client Arch: EFI BC
  Type=60 ClassId: PXEClient:Arch:00007:UNDI:003016    SMSPXE    6/17/2021 7:28:34 AM    5424 (0x1530)
88:AD:43:F6:CE:2E, 4C4C4544-0052-4C10-8057-B2C04F4E5931: Not serviced.    SMSPXE    6/17/2021 7:28:34 AM    5756 (0x167C)
============> Received from client:    SMSPXE    6/17/2021 7:28:37 AM    5424 (0x1530)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 210F658A
 Sec Since Boot: 0 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 88:ad:43:f6:ce:2e:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=54 Svr id: 192.168.001.001
  Type=50 Requested IP: 192.168.001.011
  Type=57 Max Msg Size: ff00
  Type=55 Param Request List: 0102030405060c0d0f111216171c28292a2b3233363a3b3c4243618081828384858687
  Type=97 UUID: 0044454c4c5200104c8057b2c04f4e5931
  Type=94 UNDI: 010310
  Type=93 Client Arch: EFI BC
  Type=60 ClassId: PXEClient:Arch:00007:UNDI:003016    SMSPXE    6/17/2021 7:28:37 AM    5424 (0x1530)
 

 

No errors.  Yet when I F12 any system it never connects to my SCCM server.  I only see press F1 to reboot, f2 to reboot into setup, f5 to run diag.

 

I have even removed the PXE role.  Waited 1 hour and then added it back.     Nothing works.  Very odd, any help would be great.

 

 

 

Share this post


Link to post
Share on other sites

Yes I did enable the boot image for PXE.   I have uninstalled PXE.   Deleted the RemoteInstall folder.  Rebooted.   I added PXE back and I even changed the date of the certificate (self signed cert on DP role)    when I re-add PXE the RemoteInstall folder comes back and it is populated with data.  In fact it has 1.08GB of data/files within it.     Very odd problem 🙂   Any other hints or ideals would be much appreciated.

 

 

 

 

Share this post


Link to post
Share on other sites

are you pxe booting a vm or a real computer ? what does the smspxe.log reveal when you are pxe booting, if you don't see the mac address of the device listed then something is mis-configured on the osd side,

for example, did you deployed anything to the unknown collection(s), did you make the task sequence available to media&pxe ?

Share this post


Link to post
Share on other sites

I have discovered what I feel the problem is.   My DNS is not working.   It was, I was able to PXE and I was able to Join Machines to AD manually.  Now, when I try to join a machine to AD I get these errors.

 

Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

An error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "acme.net".

The error was: "No records found for given DNS query."
(error code 0x0000251D DNS_INFO_NO_RECORDS)

The query was for the SRV record for _ldap._tcp.dc._msdcs.acme.net

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

 

I have run Net Stop Netlogon etc.... I have rebooted the DC.  Nothing seems to fix this.   I have Googled this and so far nothing has fixed it.   The DNS service is up and running.   I can stop/start DNS.   And as I said it was working last month.   

 

 

 

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...