I am currently building and configuring Secondary sites via a task sequence, but running into issues when trying to deploy the required hotfix KB977384 for R3 using this method. The hotfix seems to timeout trying to stop services, one of them being "winmgmt". One of its dependecies is the SMS Task Seqeunce agent, which I think is what the problem is. Has anyone any advice on how to install this HF successfully through a task sequence? Cheers

Have not tried it. But maybe you can add a step before which stops or kills the processes.Follow me through my blog and Twitter!

its better to wait for sometime as per the KB article. Sanka Perera

That simply cannot be done. See http://technet.microsoft.com/en-us/library/bb633063.aspx: "Task sequences cannot be used to upgrade client computers".

Thanks for your responses thus far, but I think there is some confusion here I am merely trying to install the pre-req hotfix for the R3 installation, not upgrade the client. To upgrade the client I am using the PATCH property which can be set in the client properties where the SMSSLP and SMSMP settings are specified within the TS. Cheers

It doesn't matter if upgrading the client itself or installing that hotfix. You already mentioned the root cause in your first posting. Winmgmt cannot be stopped because of the running task sequence agent.

Thanks Torsten, but your statement is incorrect that WinMgmt cannot be stopped. See the snippet from the logfile. [13:30:41] Add Service Winmgmt MSI (s) (2C!D8) [13:30:41:184]: PROPERTY CHANGE: Adding ResetServiceList property. Its value is 'SMS_SITE_COMPONENT_MANAGER SMS_EXECUTIVE SMS_SITE_VSS_WRITER ccmexec iphlpsvc Winmgmt '. [13:30:41] Reset Service List: SMS_SITE_COMPONENT_MANAGER SMS_EXECUTIVE SMS_SITE_VSS_WRITER ccmexec iphlpsvc Winmgmt [13:30:41] Exit SmsPatchPrepareAffectedServiceList [13:30:41] Stop Service SMS_SITE_COMPONENT_MANAGER [13:30:42] SMS_SITE_COMPONENT_MANAGER status is stopped [13:30:42] Stop Service SMS_EXECUTIVE [13:30:47] SMS_EXECUTIVE status is stopped [13:30:47] Stop Service SMS_SITE_VSS_WRITER [13:30:48] SMS_SITE_VSS_WRITER status is stopped [13:30:48] Stop Service ccmexec [13:30:49] ccmexec status is stopped [13:30:49] Stop Service iphlpsvc [13:30:49] iphlpsvc status is stopped [13:30:49] Stop Service Winmgmt [13:30:49] Winmgmt status is stopped [13:30:49] Exit SmsPatchStopService MSI (s) (2C:6C) [13:30:49:731]: Doing action: InstallValidate Action ended 13:30:49: SmsPatchStopService. Return value 1. Action start 13:30:49: InstallValidate. MSI (s) (2C:6C) [13:30:49:731]: PROPERTY CHANGE: Deleting MsiRestartManagerSessionKey property. Its current value is 'ea195ffa4af9884486f95c4820eeffc7'. MSI (s) (2C:6C) [13:30:49:731]: Feature: CMPATCH; Installed: Absent; Request: Local; Action: Local MSI (s) (2C:6C) [13:30:49:731]: Component: __00000409_climsgs_dll_E2C9B6C6_67A1_4076_BF61_93EAE0DF740A65; Installed: Null; Request: Local; Action: Null MSI (s) (2C:6C) [13:30:49:731]: Component: __tsspropertieslist_xml_1B82AA13_DC4D_44DF_92EF_42AACBC6E6B665; Installed: Null; Request: Local; Action: Null MSI (s) (2C:6C) [13:30:49:731]: Component: __smsprov_dll_1CDA26F7_4CE0_4A27_89DE_D0C78D94615565; Installed: Null; Request: Local; Action: Local MSI (s) (2C:6C) [13:30:49:731]: Component: __sitecomp_exe_1E39E4BC_D34D_4D39_8549_D47564AF2B0165; Installed: Null; Request: Local; Action: Local MSI (s) (2C:6C) [13:30:49:731]: Component: __sccm2007ac_sp2_kb977384_x86_en_A1B53A66_47FC_40A1_970D_34E8F696829565; Installed: Null; Request: Local; Action: Null MSI (s) (2C:6C) [13:30:49:731]: Component: __rolesetup_exe_DABD1F77_0128_4A04_BC1E_3E9507E34B7065; Installed: Null; Request: Local; Action: Local The process does indeed work in virtual environments, but not physical machines. I am currently experimenting with bigger wait times between the Secondary Site to install and firing off the hotfix as I think on physical machines processes are slower to complete than on virtual machines. Will post back what the results are.

I found the issue. The hotfix has a timeout of 5 minutes when trying to stop services before installation, and if services take longer than that to stop, error 1603 occurs.

Thanks Torsten, but your statement is incorrect that WinMgmt cannot be stopped. See the snippet from the logfile. That was originally your statement: "The hotfix seems to timeout trying to stop services, one of them being "winmgmt"." Glad you solved it.

Hi all, Somebody found a solution about this issue ? Thanks

I ran into the same problem...is there a solution for it ? Can the timeout of 5 minuted be extended ?

Apologies for the late reply... Within the msi file, there is a custom action to stop the WMI service. As task sequences rely on this service, the TS will break when it is stopped. The fix is to create a *.mst and disable the stopping of this service, and apply this to the original msi. In all my testing this works fine with no ill affect and have deployed this approach to thousands of machines already

Hi...is it possible to share the MST ? Or tell where the custom action is located so I can recreate it myself ? Thanks PS. I did some testing today myself and found out that deploying KB977384 and R3 works fine if done by a Advertisement. So that is another working solution......

Hi...is it possible to share the MST ? Or tell where the custom action is located so I can recreate it myself ? I see the following custom actions within the MSI...which one to disable by the MST ? CustomAction Action SmsAddARPEntries 1 SmsProdPatchActionI SmsAddARPEntries SmsConnectDBFail 19 [SmsConnectDatabaseFail] SmsDeleteARPEntries 1 SmsProdPatchActionI SmsDeleteARPEntries SmsDeployAC 66 SmsDeployAC SmsExecuteSqlScripts 1 SmsProdPatchActionI SmsExecuteSqlScripts SmsIncorrectLang 19 [SmsIncorrectLang] SmsIncorrectProviderVersion 19 [SmsIncorrectVersion] SmsIncorrectRemoteAdminUIVersion 19 [SmsIncorrectVersion] SmsIncorrectSiteServerVersion 19 [SmsIncorrectVersion] SmsNotInstalled 19 [SmsNotInstalled] SmsNotRunningInElevated 19 [SmsNotRunningInElevated] SmsPatchCreateSmsconfig 1 SmsProdPatchActionI SmsPatchCreateSmsconfig SmsPatchDeleteOldHotfixARPReg 1 SmsProdPatchActionI SmsPatchDeleteOldHotfixARPReg SmsPatchDeleteSmsconfig 1 SmsProdPatchActionI SmsPatchDeleteSmsconfig SmsPatchDisableNonVersionComp 1 SmsProdPatchActionI SmsPatchDisableNonVersionComp SmsPatchRollbackFiles 1 SmsProdPatchActionI SmsPatchRollbackFiles SmsPatchStartService 1 SmsProdPatchActionI SmsPatchStartService SmsPatchStartServiceInit 1 SmsProdPatchActionI SmsPatchStartServiceInit SmsPatchStartServiceRollback 3329 SmsProdPatchActionD SmsPatchStartServiceRollback SmsPatchStopService 1 SmsProdPatchActionI SmsPatchStopService SmsPatchTestFailAfterInstallFiles 3073 SmsProdPatchActionD SmsPatchTestFailAfterInstallFiles SmsPatchTestFailAfterInstallFilesInit 1 SmsProdPatchActionI SmsPatchTestFailAfterInstallFilesInit SmsPimarySiteNotApplicable 19 [SmsIncorrectRole] SmsReadSetupRegValues 1 SmsProdPatchActionI SmsReadSetupRegValues SmsRegisterAdminUI 1 SmsProdPatchActionI SmsRegisterAdminUI SmsRemoteAdminUINotApplicable 19 [SmsIncorrectRole] SmsRemoteProviderNotApplicable 19 [SmsIncorrectRole] SmsResetSiteRoles 1 SmsProdPatchActionI SmsResetSiteRoles SmsRunSQLScriptFail 19 [SmsRunSQLScriptFail] SmsSecondarySIteNotApplicable 19 [SmsIncorrectRole] SmsSetRegWow6432Node 51 RegWow6432Node Wow6432Node\ SmsTestConnectSqlServer 1 SmsProdPatchActionI SmsTestConnectSqlServer PS. I did some testing today myself and found out that deploying KB977384 and R3 works fine if done by a Advertisement. So that is another working solution......

Any idea which custom action to change ?

I no longer have access to the (*.mst) as it has been left at a customer's site. However, the custom action to look for is the step where the WMI services get stopped. I will see if I can dig up the exact action to comment out via some documentation later. Another link to look at is this: http://henkhoogendoorn.blogspot.com/2011/01/task-sequence-fails-after-r3-client.html Cheers

Thanks I am really interested in that information. I can't find it myself when searching in the MSI file. At this moment I update en install R3 using a advertisement, but using the TS I prefer.

That simply cannot be done. See http://technet.microsoft.com/en-us/library/bb633063.aspx: "Task sequences cannot be used to upgrade client computers". Using an advertisement - not a tasksequence - would be the supported way.Torsten Meringer | http://www.mssccmfaq.de

Torsten, As I have noted before, it CAN be done, but may not be supported as you point out. I know this method works because I have implemented it myself and built MANY SCCM secondary sites with R3 installed via a task sequence I am currently getting access to the Custom action and will update this site as soon as I can Cheers