SMS_PXE_Service_Point Errors

[TazBaz]

I'm currently running on a VMWare enviroment with Windows 2k8 R2

 

I have these errors

 

 

 

The solutions I have tried

• Installed WDS without doing Config and installed PSP after it
  
• Deleted the folder inside RemoteInstall SMSImages (can't remember the exact name)
  

Here is the PXESetup.log

 

 

<01-02-2012 20:47:26> ====================================================================
<01-02-2012 20:47:26> SMSPXE Setup Started....
<01-02-2012 20:47:26> Parameters: F:\PROGRA~2\MICROS~2\bin\i386\ROLESE~1.EXE /deinstall /siteserver:SCCM01 SMSPXE
<01-02-2012 20:47:26> Deinstalling the SMSPXE
<01-02-2012 20:47:26> Enabling MSI logging.  pxe.msi will log to F:\Program Files (x86)\Microsoft Configuration Manager\logs\pxeMSI.log
<01-02-2012 20:47:26> Deinstalling SMSPXE, with product code {C63C1FBD-C9C8-469D-8ADE-12387FB5EA75}
<01-02-2012 20:47:28> SMSPXE deinstall exited with return code: 0
<01-02-2012 20:47:28> Deinstallation was successful.
<01-02-2012 20:47:28> Removing PXE Registry.
<01-02-2012 20:47:35> ====================================================================
<01-02-2012 20:47:35> SMSPXE Setup Started....
<01-02-2012 20:47:35> Parameters: F:\PROGRA~2\MICROS~2\bin\i386\ROLESE~1.EXE /install /siteserver:SCCM01 SMSPXE
<01-02-2012 20:47:35> Installing Pre Reqs for SMSPXE
<01-02-2012 20:47:35> 		======== Installing Pre Reqs for Role SMSPXE ========
<01-02-2012 20:47:35> Found 1 Pre Reqs for Role SMSPXE
<01-02-2012 20:47:35> Pre Req MSXML60 found.
<01-02-2012 20:47:35> No versions of MSXML60 are installed.  Would install new MSXML60.
<01-02-2012 20:47:35> Enabling MSI logging.  msxml6_x64.msi will log to F:\Program Files (x86)\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<01-02-2012 20:47:35> Installing F:\Program Files (x86)\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<01-02-2012 20:47:35> msxml6_x64.msi exited with return code: 0
<01-02-2012 20:47:35> msxml6_x64.msi Installation was successful.
<01-02-2012 20:47:35> 		======== Completed Installion of Pre Reqs for Role SMSPXE ========
<01-02-2012 20:47:35> Installing the SMSPXE
<01-02-2012 20:47:35> Machine is running Windows 2003 SP1 or later. (NTVersion=0X601, ServicePack=1)
<01-02-2012 20:47:35> WDS Service is installed.
<01-02-2012 20:47:35> No versions of SMSPXE are installed.  Installing new SMSPXE.
<01-02-2012 20:47:35> Enabling MSI logging.  pxe.msi will log to F:\Program Files (x86)\Microsoft Configuration Manager\logs\pxeMSI.log
<01-02-2012 20:47:35> Installing F:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\pxe.msi CCMINSTALLDIR="F:\Program Files (x86)\SMS_CCM" PXEENABLELOGGING=TRUE PXELOGLEVEL=1 PXELOGMAXSIZE=1000000 PXELOGMAXHISTORY=1
<01-02-2012 20:47:44> pxe.msi exited with return code: 0
<01-02-2012 20:47:44> Installation was successful.

 

 

Found quite some solutions in this forum and social.technet, but none of them have solved much for me so thats why I ended up making a post here.

 

 

 

 

NOTE: I'm still new at the SCCM, so don't expect me to understand too advanced responses.

 

/Taz

[Eswar Koneti]

can you check if WDS service is runniing or not it not,you may have to fix that first.Also check if WDS service is configured with just remote installation folder.

[TazBaz]

When I try to start the WDS Service I get the Error code 87 and I someone had this as a solution:

 

"Solution:

 

Change the below regitry key

 

HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\IsCritical from 1 to 0"

 

 

At last I managed to start up the WDS Services, but the Message ID 6319 is still there complaining that I have to start WDS Services.

 

 

Also check if WDS service is configured with just remote installation folder.

 

Sorry, but I didn't quite understand what you mean there?

I do have a folder called RemoteInstalltion.

[silverhand]

Hi guys,

 

So before we try to install PXE Service Point, does WDS has to be able to start or run?

 

Cheers,

[Rocket Man]

ConfigMgr should do all for you, by just enabling PXE on the DP...it will install and configure WDS for you so you should not have to do any configuration..

 

 

This is not bible(however it has worked a treat for me):

If it is a remote DP across a bad link what I would suggest you to do is enable the WDS role through server manager, but do not configure it...restart the server and then enable the PXE through SCCM on the DP..

 

The remote Install folder should get populated with extra folder directories paying particular attention to the SMSBoot directory and the inner directories both x86 and x64 (they should get populated with extra files)

 

Rocket Man

 

Rocket Man