| Omar 的个人资料Omar's Blog on Systems M...照片日志列表 |  工具  帮助 |
|
10月9日 SCCM 2007 R2 RTM available for evaluation and upgradeMicrosoft has released a 180 day evaluation version of SCCM 2007 R2 that can be upgraded to the full product at the end of the evaluation period. For more details check http://technet.microsoft.com/nl-nl/configmgr/cc761485(en-us).aspx Hotfix for SCCM Task Sequence delay: KB 955955Microsoft has released a hotfix (kb 955955) for customers who experience 'a delay' when using a task sequence to deploy 'more than 50 packages'. The hotfix sets the default 90 second pause between tasks to null.
The hotfix is intended for environments that are upgraded to Service Pack 1 or have hotfix 949225 installed. This hotfix was created to do introduce the 90 second delay due to the fact that SCCM 2007 RTM sometimes did not process all advertised tasks.
Some questions and answers are to be found in the discussion http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3877200&SiteID=17 10月2日 WDS service fails to start after reboot SCCM SP1In multiple SCCM environments (being SCCM 2007 RTM environments that are upgraded to SP 1 on W2K3) there might be an issue with the WDS service that does not start up after the server being rebooted. On the technet forum for SCCM there are serveral reactions of people(http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3619346&SiteID=17) who have noticed the same problem in their environments. When opening services.msc and a manual start of the WDSSERVER service, the SCCM PXE related functionality is back online.
From the mentioned article, there is a workaround if you use a server 2008 platform, because you can set the WDSServer service to a 'delayed start', but when you use server 2003 this option is not available.
A few interesting observations: It seems the WDS service under the PXE Service Point still tries to start the legacy BINL service and the WDS Image server (binlsvc.dll and WdsImgSrv.dll), probably as a result of installing WDS without configuration (otherwise the PSP will not work). Both providers are set to non critical, so WDS can continue starting up.
It all goes wrong when SMSPXE provider errors during initialization, which is set as critical component to the WDS service. As a result the WDS service shuts down.
|
|
|
