| Omar's profileOmar's Blog on Systems M...PhotosBlogLists |  Tools  Help |
|
Omar's Blog on Systems ManagementShare knowledge, Avoid Potholes - Together December 09 Search and you will find: ICP 1 & 2 for SCCM 2007 SP1.... :-(I was wondering why it took so long this time before the International Client Packs (ICP) for SCCM 2007 SP1 (also R2) to come out. So today I mailed Wally Mead if he knew? Well, Wally mailed back to me that these were already available since the end of september 2008 and added a link to the page on download.microsoft.com .
I replied that I was happy he 'd sent me the link, but the page could not be found through the regular ConfigMan homepage > downloads page. There was only a link to the 'old' RTM ICP's and it would probably be very convenient to get the SP1 ICP's on that page too. Wally replied that he already made that request but somehow it is still not done.
For the ones that are still searching: here's the link to the SP1 ICP's
October 09 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 October 02 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.
July 08 Task sequence media and storage best practiseWhen you create your Task Sequence Media (e.g. when you want to deploy your images offline) and all goes well, you'll probably wonder why I'm getting excited about a little thing as the location SCCM uses to store the packages temporarily during compilation.
It's the temp folder under your user profile (%USERPROFILE%\Local Settings\Temp). In a test environment that brought me into trouble because my system drive had not enough disk space (you get a 0x80070070 error that states that SCCM failed to stage {PackageCode} in your CreateTSMedia.log). So depending how much stuff you need to pile into your image, the temp folder can easily grow to the size of the content of your average desktop / laptop system drive.
From a network perspective, it's interesting to understand what happens when you are working from a administrative desktop with your SCCM console. If you start to build your offline task media all necessary files and packages will be copied over the network into your %USERPROFILE%\Local Settings\Temp. Then if you selected a remote share on the network to store your images on, all that data (as one or more ISO files) will travel a second time over the network. And what happens if you decide to burn the ISO on your local DVD burner? I guess you get the point
 ...So what could you do as a best practise? You could consider the following:
|
|
||||
|
|
