SCCMTroubleshootingFlowchart

1、SCCM_OSD 常見Q&A1SCCM安裝問題21.1SCCM安裝過程21.2SCCM打開的時候，一直顯示“Connecting to SQL Server”31.3SCCM打開的時候，顯示“snap-in ”41.4SCCM 在Windows 2008安裝的時候報(bào)Unknown錯誤51.5SCCM 無法Uninstall82SCCM OSD使用問題82.1System Partition Not set82.2Failed to find driver XXX92.3IBM DP重裝后Task Sequence不能Advertise的問題102.4Windows 2003 Passw

2、ord問題112.5Clean Uninstall OS的過程112.6Reinstall IBM DP需要做的事情：122.7Failed to connect to "WIN-ZBCR84XE77M.W2K8X64.SCCM.COMSMSPKGC$2K800005" (86)：132.8SMT_AMT_Proxy_Component Error132.9用F8不能進(jìn)入client端Debug模式132.10PXE Component相關(guān)142.11Proxy DHCP142.12RAID Error152.13Several RAID Adpaters in a sys

3、tem152.148i卡在Zeus上應(yīng)該插到一個特定的PCI槽上152.15A fatal error occurred while trying to Sysprep the machine（Capture OS Image）152.16Failed to load "OSDTargetSystemRoot=C:windowssystem32configsoftware" (0x80070003).162.17用以Capture Image機(jī)器的用戶名和密碼163SCCM Software Update使用163.1SCCM Software Update的配置步驟164

4、Windows 系統(tǒng)使用165Vmware ESXi191 SCCM安裝問題1.1 SCCM安裝過程Windows 2003:1. 如SCCM站點(diǎn)服務(wù)器操作系統(tǒng)版本為Windows Server 2003 SP1，則需要安裝：MMC 3.0與.Net Framework 3.0 、KB932303、MS06-030 （ 補(bǔ)?。┤鏢CCM站點(diǎn)服務(wù)器操作系統(tǒng)版本為Windows Server 2003 SP2，則只需要安裝 .Net Framework 3.0與KB932303（ 補(bǔ)?。?. 安裝系統(tǒng)服務(wù) Internet 信息服務(wù) (IIS) 6.0 (Windows Component->

5、;Application Server->IIS)3. 安裝后臺智能傳送服務(wù) (BITS) 2.0 (Windows Component->Application Server->IIS ->BITS)，默認(rèn)不選中4. 安裝WebDAV Publishing(Windows Component->Application Server->Web Wide Web Service ->WebDAV Publishing), 默認(rèn)不選中5. 安裝WDS (Windows Component->Windows Deployment Service)6.

6、安裝 WSUS 3.0以上的版本7. 升級MMC到3.0版本，檢查MMC版本(命令行mmc，在彈出窗戶中看help)，確保MMC為3.0版本以上8. 安裝Active Directory，Server Manager > add roles（,期間選擇安裝DNS，千萬不要單獨(dú)安裝DNS，否則會在AD注冊到DNS的時候有問題）9. 配置主DNS后綴（右鍵點(diǎn)擊My Computer，選擇Computer Name頁面，點(diǎn)擊Change，選擇More，鍵入Primary DNS suffix）10. 將動態(tài)IP地址換成靜態(tài)IP地址11. 使用DCPROMO將AD升為該網(wǎng)絡(luò)內(nèi)的Domain co

7、ntroller，（選擇Domain Controller for a new domain->domain in a new forest,鍵入要創(chuàng)建的Domain名稱，一路next下去），然后注冊到DNS服務(wù)器中。12. 登陸lab 的DNS，IP：，為此臺server添加新的域，確保其他機(jī)子能ping通它的完整計(jì)算機(jī)名包括域名。13. SQL Server2005安裝（以域身份登陸，全選所有component，Default instance，Use the build-in System account, Windows Authentication Mode,其他默認(rèn)），記得重

8、啟系統(tǒng)，否則安裝SP1的時候會有一些安裝不上去，而且會有Exception。14. 打SQL Server SP1(請注意將SQL所有相關(guān)服務(wù)，以及WMI的服務(wù)關(guān)閉，否則無法安裝上去，顯示W(wǎng)arning)15. 打 SQL Server SP2(請注意將SQL所有相關(guān)服務(wù)，以及WMI的服務(wù)關(guān)閉，否則無法安裝上去，顯示W(wǎng)arning)，成功安裝之后，默認(rèn)會調(diào)入”SQL Server 2005 User Provision Tool for Vista”,選中所有用戶名及用戶組，點(diǎn)擊OK（如果有錯誤出現(xiàn)，則忽略？）PS: Configuration Manager 2007 只支持 SQL Ser

9、ver Windows 身份驗(yàn)證且SQL2005SP2以上數(shù)據(jù)庫，但在新版本中提供了對了命名實(shí)例的支持.16. 安裝SCCMl 架構(gòu)擴(kuò)展：運(yùn)行SCCM安裝源文件下SMSSETUPBINI386EXTADSCH.EXE （對于站點(diǎn)服務(wù)器安裝，不要求進(jìn)行 Configuration Manager Active Directory 架構(gòu)擴(kuò)展，但是建議您這樣做，以便完全支持使用 Configuration Manager 的所有功能）. Verify that the schema extension was successful by reviewing the extadsch.log loca

10、ted in the root of the system drive.l 開始安裝SCCM Server，先進(jìn)行Check,如果確認(rèn)Check出來的問題已經(jīng)解決，直接安裝，一路Next即可。SCCMSetupSP2ConfigMgr07SP2Eval_RTM_ENUsplash.htaWindows 2008:1. 安裝.Net Framework 3.0: Server Manager > add roles (Application Server, and “web server iis” should be added)2. 安裝IIS: Server Manager >

11、add roles (Web Server IIS) IIS6 及其它一些組件一并安裝3. 安裝WDS: Server Manager > add roles (Windows Deployment Service) 4. 安裝BITS: Server Manager > add feature5. 安裝和配置WebDAV (1.5)6. 安裝 WSUS 3.0, cancel掉配置WSUS7. 安裝Active Directory：Server Manager > add roles (Active Directory Domain Service)8. 將動態(tài)IP地址換成

12、靜態(tài)IP地址9. 使用DCPROMO將AD升為該網(wǎng)絡(luò)內(nèi)的Domain controller，并注冊到DNS服務(wù)器中。10. 登陸lab 的DNS，IP：，為此臺server添加新的域，確保其他機(jī)子能ping通它的完整計(jì)算機(jī)名包括域名。11. SQL Server2005安裝（以域身份登陸，全選所有component，Default instance，Use the build-in System account, Windows Authentication Mode,其他默認(rèn)），記得重啟系統(tǒng)，否則安裝SP3的時候會有一些安裝不上去，而且會有Exception。如果在安裝前出現(xiàn)警告信息說IIS

13、存在問題，可以在Server Manager -> Roles ->Add Roles ->IIS 中將IIS6 及其它一些組件一并安裝(for 2k8r2 sp1, we need install sql 2008 sp1)12. 安裝SQL Server SP3 (請注意將SQL所有相關(guān)服務(wù)，以及WMI的服務(wù)關(guān)閉，否則無法安裝上去，顯示W(wǎng)arning) 默認(rèn)會調(diào)入“SQL Server 2005 User Provision Tool for Vista”，選中所有用戶名及用戶組，點(diǎn)擊OK（如果有錯誤出現(xiàn)，則忽略？）PS: Configuration Manager 20

14、07 只支持 SQL Server Windows 身份驗(yàn)證且SQL2005SP2以上數(shù)據(jù)庫，但在新版本中提供了對了命名實(shí)例的支持.13. 安裝SCCM Server：l 架構(gòu)擴(kuò)展：運(yùn)行SCCM安裝源文件下SCCMSetupSP2ConfigMgr07SP2Eval_RTM_ENUSMSSETUPBINI386EXTADSCH.EXE （對于站點(diǎn)服務(wù)器安裝，不要求進(jìn)行 Configuration Manager Active Directory 架構(gòu)擴(kuò)展，但是建議您這樣做，以便完全支持使用 Configuration Manager 的所有功能）。Verify that the schema

15、extension was successful by reviewing the extadsch.log located in the root of the system drive.l 開始安裝SCCM Server，先進(jìn)行Check,如果確認(rèn)Check出來的問題已經(jīng)解決，直接安裝，一路Next即可。SCCMSetupSP2ConfigMgr07SP2Eval_RTM_ENUsplash.htaWindows 2008 R2 SP1:1. Open windows powershell, set its execution property as runnable(set-exe un

16、restricted -> Y), copy preinstall.ps1 to a local folder such as C:Tools. Run it.2. Check if .net 3.5 sp1 and .net 4.0 have been installed, mannully install them if not.3. Lon in DNS server , add a new forest with the name of our new win2k8 machine, and also, create a new A host record in this for

17、est, make sure that we can get a reply when pinging our new machine.4. SQL Server2008 installation:（logon as a domin user, select all the components ，Default instance，Use the build-in System account, Windows Authentication Mode, make sure the integration service and reporting service use dominadmini

18、strator as the account）。5. Install SQL Server 2008 SP1 -> kb977443 -> kb2497673 6. 安裝SCCM Server：l 架構(gòu)擴(kuò)展：運(yùn)行SCCM安裝源文件下SCCMSetupSP2ConfigMgr07SP2Eval_RTM_ENUSMSSETUPBINI386EXTADSCH.EXE （對于站點(diǎn)服務(wù)器安裝，不要求進(jìn)行 Configuration Manager Active Directory 架構(gòu)擴(kuò)展，但是建議您這樣做，以便完全支持使用 Configuration Manager 的所有功能）。Veri

19、fy that the schema extension was successful by reviewing the extadsch.log located in the root of the system drive.l SCCM Server installation: recommend to check the “use typical installation options for a single server installation” box. Use the downloaded updates you copied from the source server,

20、and then sign the site code and site name, in next step, choose the option “primary site will be installed as a standalone site”, choose default settings for all the other items, untill finishing the whole installation.1.2 SCCM無法installl Cannot connect SQL。把SQL打頭的服務(wù)開啟l The Microsoft Remote Different

21、ial Compression (RDC) library must be registered for Configuration Manager site server installation.To add Remote Differential Compression to site servers and branch distribution pointsIn Server Manager, on the Features node, start the Add Features Wizard.On the Select Features page, select Remote D

22、ifferential Compression, and then click Next.Complete the rest of the wizard by clicking install then close.Now run the prerequisite checker again and the RDC error should be gone1.3 SCCM打開的時候，一直顯示“Connecting to SQL Server”1. 檢查Service：Start->All Programs->Services, 確保如下SQL服務(wù)已經(jīng)正常啟動：Ø SQL

23、ServerØ SQL Server Active Directory Helper (主要是幫助，可以Stopped)Ø SQL Server AgentØ SQL Server Analysis ServicesØ SQL Server BrowserØ SQL Server FullText SearchØ SQL Server Integration ServicesØ SQL Server Reporting ServicesØ SQL Server Vss Writer而且需要確保WMI服務(wù)正常啟動&#

24、216; Windows Management Instrumentation Driver Extensions2. 如果其中有任何一項(xiàng)服務(wù)沒有啟動，尤其是SQL ServerSQL Server AgentSQL Server Integration ServicesSQL Server Reporting Services，需要檢查系統(tǒng)日志，并修復(fù)：Start>All Programs->Administrative Tools->Computer Management點(diǎn)擊Event Viewer，雙擊Application，查看相關(guān)Log，并依據(jù)此進(jìn)行修復(fù)。常見問題：

25、SQL Server 評估期超期。解決辦法：修改系統(tǒng)時間，例如修改為去年的時間。SQL Server Reporting Service不能正常啟動，顯示：Error 1069：The Service did not start due to a logon failure方法：1. Click Start, point to Settings, and then click Control Panel.2. Double-click Administrative Tools, and then double-click Services.3. Use one of the following

26、 steps based on your instance type:o For a default instance of SQL Server, double-click MSSQLServer, and then click the Log On tab.o For a named instance of SQL Server, double-click MSSQL$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server

27、 instance.o For a default instance of SQL Server Agent, double-click SQLAgent, and then click the Log On tab.o For a named instance of SQL Server Agent, double-click SQLAgent$YourInstanceName, and then click the Log On tab. Replace YourInstanceName with the actual name of the SQL Server instance.4.

28、Type the correct password in the Password and Confirm password textbox, and then click OK.SQL Server（MSSQLServer）不能正常啟動，顯示：Error 17051錯誤太多，重裝SQL Server1.4 SCCM打開的時候，顯示“snap-in ”原因：Memory可能過小解決辦法：1） 擴(kuò)大Memory，尤其是Windows 2008系統(tǒng)，對于Memory的需求很大（SCCM：3G左右）；2） 重啟系統(tǒng)，重啟SCCM1.5 SCCM 在Windows 2008安裝的時候報(bào)Unknown錯

29、誤問題解決：配置WebDAV配置步驟如下：2） 點(diǎn)擊【開始】>【程序】【管理工具】【IIS管理】3） 點(diǎn)擊Default Web site（或者SMSWeb）4） 雙擊WedDAV Authoring Rules, 并Enable WebDAV5） Create the Authoring Rule, Click Add Authoring Rule6） Allow "All users" read access to "All content"7） Configure these settings:Anonymous property queri

30、es = True. Allow Custom Properties = False. Allow property queries with infinite depth = True. 8） 然后卸載SCCM，重裝SCCM,問題解決。1.6 SCCM 無法Uninstalll SCCM卸載的時候一直顯示“Remove ConfigMgr Services”無法繼續(xù)?！窘鉀Q方法】【開始】【程序】【管理工具】【服務(wù)】將所有以SMS開頭的服務(wù)關(guān)閉。l SCCM修改密碼之后，卸載SCCM，卸載的時候顯示“Setup can not deinstall the database，contact yo

31、ur SQL administrator”【解決方法】【開始】【程序】【管理工具】【服務(wù)】右鍵點(diǎn)擊所有以SQL開頭的服務(wù)，修改Logon頁面里面的用戶名密碼，并確保SQL Server出于connect狀態(tài)（SQL Server兩個主要服務(wù)出于Started的狀況）2 SCCM OSD使用問題2.1 注意事項(xiàng)1） Deploy 2003 OS 時，需要選擇Raid 卡driver在Apply Driver Package那一步。需要設(shè)置Password在 “Apply Windows Setting”這一步。2） Apply OS Image這步， 不要選sysprep3） Update OS

32、 Image DP時，在site status里面要查看確保DP已經(jīng)更新好。4） 存放log文件和wim文件的文件夾必須share出來，并且給Administrators（域名用戶名）所有的控制權(quán)限5） 以非管理員賬號登錄試圖安裝：首先以域管理員賬號登錄時，在管理工具->Active Directory Users and Computers對話框的Users里面創(chuàng)建一個用戶，該用戶自動為domainUsers組。接著在計(jì)算機(jī)右鍵屬性對話框中，允許用戶遠(yuǎn)程登錄，并add剛添加的用戶，此時，用戶應(yīng)該自動加入了Remote Desktop Users組，可以在管理工具->Active

33、Directory Users and Computers的Builtin里面查看Remote Desktop Users的屬性，看是否包含了該成員。然后運(yùn)行g(shù)pedit.msc，定位到計(jì)算機(jī)配置->Windows設(shè)置->安全設(shè)置->本地策略->用戶權(quán)限分配，在右側(cè)面板里雙擊“通過終端服務(wù)允許登錄”，添加Remote Desktop Users，并確定。（如果后面還是不能登錄，可以在這里直接加入添加的用戶，再試）這樣，我們就能用遠(yuǎn)程桌面連接域控制器了，注意，一定要是遠(yuǎn)程桌面！而不能是直接連（例如用VMWare Client的console！）2.2 System Par

34、tition Not set【問題描述】1） 部署OS之后，Client端顯示圖片如下：2） 通過F8，返回Log如下：System partition not set（其中一個Error）（請用Trace32.exe打開）3） 檢查RAID配置，發(fā)現(xiàn)RAID沒有設(shè)置成功。重啟機(jī)器，發(fā)現(xiàn)RAID卡的BIOS被禁用。4） 啟動RAID卡的BIOS，該問題解決。【解決辦法】啟動RAID卡的BIOS2.3 Failed to find driver XXX【問題描述】1） 部署OS之后，Client端顯示圖片如下2） 通過F8，返回Log如下：Failed to load driver XXX（其中

35、一個Error）【解決辦法】1） 重啟Client，POST過程中查看RAID卡信息2） 點(diǎn)擊Computer ManagementOperation System DeploymentDrivers3） 點(diǎn)擊相關(guān)Driver具體文件，點(diǎn)擊Applicability，可以得到該Driver的適用Hardware4） 選擇相應(yīng)的driver5） 點(diǎn)擊Task Sequence并選擇Apply Driver PackageCheck the checkbox “Select the mass storage driver within the package that needs to be in

36、stalled before setup on Pre-Vista Operation systems”選擇相應(yīng)driver6） 點(diǎn)擊Apply2.4 IBM DP重裝后Task Sequence不能Advertise的問題【問題描述】IBM DP重裝之后，重裝前創(chuàng)建的Task Sequence，右鍵點(diǎn)擊彈出的菜單中沒有Advertise選項(xiàng)。【問題解決】1） 右鍵點(diǎn)擊Task Sequence，點(diǎn)擊Properties，點(diǎn)擊Advanced頁面2） Uncheck the checkbox “Use a boot image”，點(diǎn)擊Apply3） 然后重新選中上述checkbox，并選擇相應(yīng)

37、的Boot Image，點(diǎn)擊Apply2.5 Windows 2003 Password問題【問題描述】使用IBM DP部署OS Windows 2003，默認(rèn)情況下生成一個隨機(jī)的Password，需要對Password進(jìn)行修改，否則無法進(jìn)入安裝好的系統(tǒng)【問題解決】1） 編輯Task Sequence，Deploy Operation System->Apply Windows Settings, 并選中raido box “Enable the account and specify the local administrator password”2） 鍵入Password，并確認(rèn)P

38、assword3） 重裝系統(tǒng)之后，設(shè)置的Password無效，但是會保留以前的Password2.6 Clean Uninstall OS的過程1） Uninstall IBM DP2） 挨個刪除Computer ManagementOperation System DeploymentDrivers 里面的Driver3） 確保如下Package都已經(jīng)被刪除：4） 搜索IBM文件夾，并刪除2.7 Reinstall IBM DP需要做的事情：1） Operation System Deployment->Boot Images-> IBM Deployment-> IBM

39、Deployment Boot Image(X86) 右鍵點(diǎn)擊Manage Distribution Points，一路Next下去注意選擇機(jī)器名SMSPXEIMAGES$右鍵點(diǎn)擊Upgrade Distribution Points，一路Next下去2） Operation System Deployment->Boot Images -> Boot Image(X86)/Boot Image(X64) 右鍵點(diǎn)擊Manage Distribution Points，一路Next下去注意選擇機(jī)器名SMSPXEIMAGES$右鍵點(diǎn)擊Upgrade Distribution Point

40、s，一路Next下去3） Operation System Deployment->Boot Images-> Driver Packages ->IBM Server Drivers (X86)/IBM Server Drivers (X64) 右鍵點(diǎn)擊Manage Distribution Points，一路Next下去注意選擇機(jī)器名SMSPKGC$右鍵點(diǎn)擊Upgrade Distribution Points，一般非?？?，會很快完成。4） Software Distribution->Packages -> IBM Server Deployment->

41、;IBM Custom Reboot Script 1.1/IBM ServerGuide Toolkit Integration 1.1 右鍵點(diǎn)擊Manage Distribution Points，一路Next下去注意選擇機(jī)器名SMSPKGC$右鍵點(diǎn)擊Upgrade Distribution Points，一般非?？?，會很快完成。5） 重新關(guān)聯(lián)Task Sequence和Boot Image(請參考2.3)2.8 Failed to connect to "WIN-ZBCR84XE77M.W2K8X64.SCCM.COMSMSPKGC$2K800005" (86)：【問

42、題描述】Reinstall IBM DP之后，按照2.6重新更新所有的DP，重新Advertise之前可用的TS，Client無法正常進(jìn)入Task執(zhí)行，反復(fù)重啟2.9 SMT_AMT_Proxy_Component Error【問題描述】“The AMT Proxy Manager failed 10 times while replicating file C:Program FilesMicrosoft Configuration Managerinboxesamtproxymgr.boxmtn.box9DC95818-2807-4D7C-B717-706FAB036739.MTN to

43、out of band service point. The file has been moved to the BAD file inbox.”【問題解決】Google上搜來的This type of messages will not block you any other scenarios. Actually it's trying to initiate OOB related maintenance tasks. If you really want to eliminate the error messages, you can disable the 2 oob ma

44、intenance tasks on admin console. (Site SettingsSite MaintenanceTasksReset AMT Computer Passwords & Evaluate Provisioned AMT computer Certificate)2.10 用F8不能進(jìn)入client端Debug模式IBM Boot Image右鍵點(diǎn)擊Property，選擇WinPE頁面選中Enable Command Support（test only）重新更新DP2.11 PXE Component相關(guān)重新創(chuàng)建PXE Role之后，需要重新更新所有DP，尤

45、其是Boot Image的DP，需要重新Manage2.12 Proxy DHCP【問題描述】系統(tǒng)從PXE啟動失敗，顯示Proxy DHCP【問題解決】檢查DHCP Server是否正常運(yùn)行，網(wǎng)絡(luò)連接是否正常，DHCP服務(wù)是否正常啟動。2.13 RAID ErrorPress C to load configuration Utility.2.14 Several RAID Adpaters in a system進(jìn)入到RAID卡里面去，把不用的RAID卡禁用掉。（POST之后，會顯示RAID Firmware信息，可以進(jìn)入RAID Controller的Utility進(jìn)行操作）。2.15 8

46、i卡在Zeus上應(yīng)該插到一個特定的PCI槽上Hermes也是否則會有Kernel Panic的錯誤2.16 A fatal error occurred while trying to Sysprep the machine（Capture OS Image）【問題描述】在Windows 2k8 64bit中運(yùn)行sysprep超過3次會有該Error報(bào)出來。The Setuperr.log file may contain lines that resemble the following: Error 0x0f0082 SYSPRP LaunchDll: Failure occurred w

47、hile executing 'C:WindowsSystem32slc.dll, SLReArmWindows', returned error code -1073425657Error 0x0f0070 SYSPRP RunExternalDlls: An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = -1073425657Error 0x0f00a8 SYSPRP WinMain: Hit failure while processing sy

48、sprep generalize providers; hr = 0xc004d307Note The Setuperr.log file is located in the WindowsSystem32SysprepPanther folder.【解決辦法】重裝Win2k8 系統(tǒng)2.17 Failed to load "OSDTargetSystemRoot=C:windowssystem32configsoftware" (0x80070003).【問題描述】使用SCCM Capture Image，Client端成功PXE啟動，在執(zhí)行Capture Image過程中

49、報(bào)錯【解決辦法】OSDTargetSystemRoot variable needs to be all capital. C:WINDOWS2.18 用以Capture Image機(jī)器的用戶名和密碼請注意：用來capture Image機(jī)器的用戶名和密碼必須要有？否則deploy之后無法進(jìn)入capture的系統(tǒng)2.19 "PXE-E53.no boot filename received" while booting through PXE to Deploy the OS image.1) Make sure that WDS (Windows Deploym

50、ent Service) has been installed and that it was installed before the PXE Service Point role was added.2) Do not try and configure WDS as it should not be necessary. Do not try and change any configurations in WDS as this also should not be necessary. When installing the PXE Service Point role, the i

51、nstall will automatically properly configure WDS. In some cases, some changes may be necessary and are outlined below under the section titled FURTHER TROUBLESHOOTING. However, these actions should not be taken until first trying the TROUBLESHOOTING section.3) Do not try and manually start the WDS s

52、ervice as this should not be necessary. When installing the PXE Service Point role, the install will automatically start the WDS service after properly configuring WDS. The WDS service will not start until the PXE Service Point role has been successfully installed.4) After both WDS and the PXE Servi

53、ce Point have been successfully installed and the WDS service has successfully started, when opening the WDS console, it is normal for WDS to show a yellow exclamation mark and for it to say "Windows Deployment Server not yet configured".5) Make sure that BOTH the x86 and x64 Boot Images a

54、re copied up to the SMSPXEIMAGES$ Distribution Point. Even if an x86 OS is being deployed to an x64 capable PC and even though it will eventually boot from an x86 Boot Image, the x64 Boot Image is still necessary as WDS needs to extract some files from that x64 Boot Image in order for the x64 capabl

55、e PC to be properly PXE booted from.6) Make sure that no PXE related DHCP options are set on the DHCP server. If WDS was being used in conjunction with another product before SCCM 2007 was installed (such as RIS), make sure that you have removed any DHCP Options from the DHCP server that the previou

56、s product may have required. Usually these DHCP Options include060 PXE Client066 Boot Server Host Nameor066 TFTP server name067 Bootfile NameNOTE: According to KB259670 (PXE clients computers do not start when you configure the Dynamic Host Configuration Protocol server to use options 60, 66, 67 - s

57、etting up DHCP scope options to redirect PXE clients is NOT supported by Microsoft. The recommended solution is to use router IP helper tables.7) In the rare cases where the DHCP server is on the same server as the SCCM server where the PXE Service Point role is being installed, the 060 PXE Client D

58、HCP Option will be necessry and will need to be added to the DHCP Server DHCP Options. The PXE Service Point installer will automatically detect this, prompt for confirmation in the setup wizard, and then set the DHCP options on the DHCP server automatically. No manual configuration or additions should ever be necessary to the DHCP option