Does Task Sequence Hotfix KB955955 just reintroduce a previous issue for processing task sequences?
Hi,
There has been a recent hotfix "KB 955955 - A task sequence that contains many packages may take longer to run after you install System Center Configuration Manager 2007 Service Pack 1 or hotfix 949225"
"This problem occurs because of a behavior change introduced in hotfix 949225.
This change adds 90 second delay to make sure that all task sequences are executed on the System Center Configuration Manager client-side when many task sequences are assigned to a client at the same time. However, it causes a side effect that a task sequence takes longer to run if it contains many packages."This delay however was introduced as part of "KB949225 - System Center Configuration Manager 2007 does not process all advertised task sequences" (which is also in SP1) to esnure all task sequences are processed.
If this delay is removed so the multiple-package side effect is no longer experienced.
Arent we therefore just re-introducing the same problem of not processing all advertised task sequences that the original KB949225 originally introduced this dealy in order to help deal with ?
There is unfortunately very little information in this latest KB article.
Regards
Lee
Answers
The ConfigMgr is never updated automatically to any version. R2 just adds additional functionality (no new client components) so installing R2 does not help out.
But maybe this helps in your scenario: http://blogs.technet.com/smsandmom/archive/2008/09/24/configmgr-2007-how-to-automatically-apply-a-client-hotfix-as-part-of-a-client-push-or-client-installation.aspx
All Replies
This KB955955 seems to be causing more trouble than it's worth. I had 2 test ConfigMgr sites, both running SP1 and R2. Each is in a different test domain. On one test server I was having the issue with the 90 second lag between application isntalls during my TS execution. We installed KB955955 on both servers. Not only did the KB955955 not fix the problem on the site having the 90 second delay, but the other site that did not have the problem now does have the 90 second delay since installation of the patch.
We tried uninstalling the patch on one site. It seems that the uninstall does not roll back Policyagentendpoint.dll to the prior version. It stays at 4.0.6221.1110. Next I'm going to attempt a manual rollback to the prior version.
A side affect to this seems to be that on the one site where I have the PXE Service point enabled, installation of this patch broke PXE. The component was still there and appeared to be functional but the processing of collection membership was broken. I tried with unknown computers and with computers I had manually imported into the site and PSP could not recognize any TS assignments for any PC's. I had to uninstall and re-install the PSP role in order to get PXE working again.
One thought I had in regards to the KB955955 issues is that perhaps the Sccm2007ac-sp1-kb955955-x86.msp patch to the ConfigMgr client has to be applied during the task sequence in order to resolve the 90 second delays. I ensured the msp was included in the client\i386\hotfix\KB955955 folder on the server. This did not fix the problem. I even added an additional step to my TS to forcefully install the MSP. This doesn't give a good return code when installed during the TS. Moved it around to a couple different places but still got the 90 second delay. MS - more info is needed on this patch. If the rollback of the dll does not get me back to where I was before the patch I'm going to have to open a support ticket, which I dread doing as I have now less than a month before my big production rollout upgrading SMS 2003 to ConfigMgr.
I can confirm after only the most basic of testing that a newly deployed client does not automatically upgrade to version 4.0.6221.1110. Clients deployed in task sequences are still .1000. I'm going to try forcing it in the task sequence as well.
My other question - I'm not 100% convinced that the installer for the hotfix (on the server) actually performed a site reset - I clicked yes - got not errors - but also no indication it was actually happening. What might be the ramifications of not performing a sit reset? Should I go ahead and perform one manually (and I assume only check the top of the three options - the one about resetting default permissions, not the ones about modifying database or provider locations)?
Thanks,
Andrew
I did also confirm that the client version doesn't automatically get upgraded during a task sequence build just by including the .msp in the client code. After the build I manually ran the msp and could see the client version get upgraded.
Since the KB did not fix the 90 second delay problem on the server, but rather, made it start, we uninstalled the KB from the server. To get the policy agent dll to roll back to the previous version we had to do a site reset. Even doing this did not get us back to square 1 and we still have the 90 second delay. I am not planning on loading this KB when I implement in my production environment next month.
You're seeing this in R2 as well, right? So we can't just install R2 and get the problem taken care of that way, can we?
Andrew
that's correct, we're running SP1 with R2.
Well, what's the definition of insanity?
Same results when I try to force the .msp during the task sequence. I would suspect that the task sequence DOES NOT like javing the client restarted in the middle of things. Might there be any way to quash the client restart? Although I suppose there's probably stuff being done before and after, and it's not just a restart to freshen whatever version of the client is loaded in to memory.
Andrew
The ConfigMgr is never updated automatically to any version. R2 just adds additional functionality (no new client components) so installing R2 does not help out.
But maybe this helps in your scenario: http://blogs.technet.com/smsandmom/archive/2008/09/24/configmgr-2007-how-to-automatically-apply-a-client-hotfix-as-part-of-a-client-push-or-client-installation.aspx
good info. I'll give it a shot. thanks.- I can confirm that structuring the client code to include the hotfix as noted in the above referenced article does indeed fix the problem. This allows the ConfigMgr client installation during a task sequence build to install the msp and be at the updated version. With this, the 90 second delay goes away. Many thanks for that article reference.
Agreed - my task sequence smokes now. I'm not seeing any side effects either - somewhere on this forum is someone who reports that the addition of this hotfix backs out the fix that the 90 second delay is supposed to provide...or something along those lines.
Andrew
I have everything consolidated into 1 task sequence so I don't think that issue would be applicable to my environment anyway.
- I marked Torsten post as the answer to help people that have the same problem to find the solution faster, and to avoid other answerers from reading through posts that are already answered.
- The link in the answer is not accessible. Does anyone have the steps to get this work?
- It looks like that link above is dead...the post appears to have been deleted. I found another copy of the post on Rod Trent's blog and created a condensed version of it at the end of my blog post on this issue.
Rod's post:
http://myitforum.com/cs2/blogs/rtrent/archive/2008/09/25/good-info-how-to-automatically-apply-a-client-hotfix-as-part-of-a-client-push-or-client-installation.aspx
My post:
http://verbalprocessor.com/2009/03/31/kb955955-error/
Jarvis Davis
~ The Verbal Processor We are using the international client pack on our sccm2007 Sp1 server. I tried the senario from the above link but the TS still fails.
I put in a part of the client.msi.log. it give the following error back: Transforming table Error. Could this be a problem with the different language?
If you need more info let me know
I appreciate your help
Dirk
Property(S): RecacheTransforms = C:\WINDOWS\system32\ccmsetup\{E8357347-7382-42F6-B18B-14528BBD3654}\client.mst
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): CCMHTTPPORT = 80
Property(S): CCMHTTPSPORT = 443
Property(S): CCMHTTPSSTATE = 0
Property(S): CCMFIRSTCERT = 0
Property(S): SMSPUBLICROOTKEY = 0602000000A40000525341310004000001000100470084AC08331D245780FEF1ECFA165463F48FE16E28B8BAEFDB14341BEA8F62088B80D3774A254E47CE241B2C206E7E6BD16EE031B6E731572053AB030D69ABE4FF7CDE89B5EB6B8EE1E437E37D7543D3A1A7B035E1BEE45C0D2CD7649A236C3F91615D6119FB8138C0B0D21DA15D8AD895311382E22AF3ABEF27B9AF36E9C8
Property(S): CURRENTDIRECTORY = C:\WINDOWS\system32
Property(S): CLIENTUILEVEL = 3
Property(S): CLIENTPROCESSID = 516
Property(S): SOURCEDIR = C:\WINDOWS\system32\ccmsetup\{E8357347-7382-42F6-B18B-14528BBD3654}\
Property(S): SourcedirProduct = {0CB63ED9-8B6C-4312-B214-8AE8896DCC25}
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 3.01
Property(S): VersionNT = 501
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 3
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\WINDOWS\TEMP\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\WINDOWS\system32\config\systemprofile\Application Data\
Property(S): FavoritesFolder = C:\WINDOWS\system32\config\systemprofile\Favorieten\
Property(S): NetHoodFolder = C:\WINDOWS\system32\config\systemprofile\NetHood\
Property(S): PersonalFolder = C:\WINDOWS\system32\config\systemprofile\Mijn documenten\
Property(S): PrintHoodFolder = C:\WINDOWS\system32\config\systemprofile\Netwerkprinteromgeving\
Property(S): RecentFolder = C:\WINDOWS\system32\config\systemprofile\Onlangs geopend\
Property(S): SendToFolder = C:\WINDOWS\system32\config\systemprofile\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Sjablonen\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All Users\Application Data\
Property(S): LocalAppDataFolder = C:\WINDOWS\system32\config\systemprofile\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\WINDOWS\system32\config\systemprofile\Mijn documenten\Mijn afbeeldingen\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Menu Start\Programma's\Systeembeheer\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Menu Start\Programma's\Opstarten\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Menu Start\Programma's\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Menu Start\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Bureaublad\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 6
Property(S): PhysicalMemory = 2013
Property(S): VirtualMemory = 3768
Property(S): AdminUser = 1
Property(S): LogonUser = SYSTEM
Property(S): UserSID = S-1-5-18
Property(S): UserLanguageID = 1043
Property(S): ComputerName = IT22274
Property(S): SystemLanguageID = 1043
Property(S): ScreenX = 800
Property(S): ScreenY = 600
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 14:52:02
Property(S): Date = 6-4-2009
Property(S): MsiWin32AssemblySupport = 5.1.2600.5512
Property(S): RedirectedDllSupport = 2
Property(S): Privileged = 1
Property(S): USERNAME = Basisinfrastructuur
Property(S): COMPANYNAME = Gemeente Nijmegen
Property(S): DATABASE = C:\WINDOWS\Installer\c383.msi
Property(S): OriginalDatabase = C:\WINDOWS\system32\ccmsetup\{E8357347-7382-42F6-B18B-14528BBD3654}\client.msi
Property(S): UILevel = 2
Property(S): ACTION = INSTALL
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 303617592
Property(S): PrimaryVolumeSpaceRequired = 235831
Property(S): PrimaryVolumeSpaceRemaining = 303381761
Property(S): INSTALLLEVEL = 1
Property(S): SmsSoftwareDistributionCacheSize.8AE6A59B_5597_4D75_9BFD_7F566BF56500 = 5120
Property(S): CcmAdministratorsGroupName = Administrators
Property(S): CcmUsersGroupName = Gebruikers
Property(S): CcmCreatorOwnerAccountName = MAKER EIGENAAR
Property(S): PrimaryVolumePath = C:
Property(S): CCMALWAYSINF = 0
Property(S): ProductToBeRegistered = 1
MSI (s) (F4:BC) [14:52:02:243]: Note: 1: 1707
MSI (s) (F4:BC) [14:52:02:243]: Transforming table Error.MSI (s) (F4:BC) [14:52:02:243]: Transforming table Error.
MSI (s) (F4:BC) [14:52:02:243]: Product: Configuration Manager Client -- De installatie is voltooid.
MSI (s) (F4:BC) [14:52:02:259]: Attempting to delete file C:\WINDOWS\Installer\c384.mst
MSI (s) (F4:BC) [14:52:02:259]: Unable to delete the file. LastError = 32
MSI (s) (F4:BC) [14:52:02:259]: Cleaning up uninstalled install packages, if any exist
MSI (s) (F4:BC) [14:52:02:259]: Post-install cleanup: removing installer file 'C:\WINDOWS\Installer\c384.mst'
MSI (s) (F4:BC) [14:52:02:259]: MainEngineThread is returning 0
MSI (s) (F4:60) [14:52:02:368]: Destroying RemoteAPI object.
MSI (s) (F4:B8) [14:52:02:368]: Custom Action Manager thread ending.
=== Logboekfunctie beëindigd: 6-4-2009 14:52:02 ===
MSI (c) (04:C0) [14:52:02:368]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (04:C0) [14:52:02:368]: MainEngineThread is returning 0
=== Verbose logging stopped: 6-4-2009 14:52:02 ===- Try installing it manually on an existing client and see if you get an error message that will tell you more ...
- thanks for your reply.
I need SCCM2007-SP1-KB955955-X86-ICP2.exe. This works on an existing client, but I can't get the patch installed on my server:
while installing patch: error Failed to install cat files
client are dutch SCCM2007 server is eng
any ideas - can I just rename 955955.cat file?
I fixed my problem,
I was posible to install the SCCM2007-SP1-KB955955-X86-ICP2.exe on sccm2007 server. (rename cat file from previous install)
Then i used the above senario, works like crazy...- Hi,
A quick warning about this method. We had a support case with MSFT where the usage of the ClientPatch folder was identified as being the culprit.
We got this formal answer: "They (Developement Team) consider the use of the clientpatch folder to be unsupported as it was never fully tested."
Cheers,
Serge
