Thursday, November 20, 2008
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Member Login
StandardLiveID


Register
Forgot Password ?



Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Subject: HOTFIX - SCCM SP1 Task Sequence Bug
Prev Next
You are not authorized to post a reply.

AuthorMessages
ianfraserUser is Offline

Posts:6

Send Message
09/09/2008 11:53 AM  

Hi Guys

After badgering Microsoft about this problem, they have produced a hotfix for SCCM SP1. It fixes the issue we have had where we are seeing a 90 second delay between task sequence steps, which is dragging out our build process.

http://support.microsoft.com/kb/955955/en-us

Good luck!

Ian

 

Eric GirouxUser is Offline

Posts:22

Send Message
09/22/2008 6:31 PM  
I think it may have been rushed a bit.  I loaded this hotfix on my test server after loading R2.  Prior to the loading the hotfix I was not having the 90 second delay issue.  After loading the fix the problem started to occur.  I tried uninstalling the hotfix and the problem did not go away.  How do I get back to a working state?
ianfraserUser is Offline

Posts:6

Send Message
09/25/2008 7:57 AM  
I would not suggest installing the fix on R2 as it is designed as a fix for SP1, or the previous SP0 hotfix. And if you didn't have the issue in the first place, what were you tring to prove by installing it?

I would suggest having a look through the article http://support.microsoft.com/kb/955955/en-us and you could restore the files from another SCCM server. Or re-apply R2.

Out of interest have you experienced the problem with SP1?

Cheers

Ian

Eric GirouxUser is Offline

Posts:22

Send Message
10/28/2008 3:53 PM  

Well, to answer your question, another member of my team added the KB to our development server kind of for the sake of trying to be as up to date as possible.  So, we added the update to our production server as well, for consistency sake. 

I was able to get everything working.  The problem was that the MS article does not tell you how to integrate this patch into new installs of the ConfigMgr client.  There's lots of info on patching existing ConfigMgr clients who do not have the msp install.  My problem was getting the client installed, up to the patched version, as part of a new ConfigMgr client install during task sequence (XP OS) rollout.  What the article didn't allude to is that you have to create the "clientpatch" folder under your \\siteserver\sms_sitecode\client folder and include the msp in this folder.  This is in addition to the client\i386\hotfix\KB955955 directory structure that gets created automatically.  Once I added the clientpatch folder everything started working fine. 

You are not authorized to post a reply.
Forums > Related Technologies > System Center Configuration Manager 2007 > HOTFIX - SCCM SP1 Task Sequence Bug



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.



Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt