Hi everyone, i'm new in this forum and i got a strange issue in my clients upgrade.I just migrate from SMS2003 to SCCM 2007 Sp1 (side by side upgrade). The migration was ok, all of my clients are assigned to my new site.In most cases (not always) when i try to push a client install on a computer this install never finish (i did right click on client and click "install client").I'm using this parameters: SMSSITECODE=002 SMSSLP=SEVERNAME FSP=SEVERNAMEI tried with manual install with batch file: ccmsetup.exe /noservice /MP:LUMGT023 SMSSITECODE=002 SMSSLP=SEVERNAME FSP=SEVERNAME but i get the same issue.Here is the logs:Last rows of ccmsetup.logMSI: Action 16:28:12: CcmUnregisterPerfCounters. Unregistering performance counters ccmsetup 15/10/2009 16:28:12 3892 (0x0F34)MSI: Action 16:28:12: CcmTypelibRollback. ccmsetup 15/10/2009 16:28:12 3892 (0x0F34)MSI: Action 16:28:12: RemoveRegistryValues. Removing system registry values ccmsetup 15/10/2009 16:28:12 3892 (0x0F34)MSI: Action 16:28:13: SmsDeinstallDesktopClientRollback. Deinstalling the SMS Legacy Client or SMS 2.0 Client ccmsetup 15/10/2009 16:28:13 3892 (0x0F34)MSI: Action 16:28:13: SmsMigrateSwDistExecutionHistory. Migrating Software Distribution History ccmsetup 15/10/2009 16:28:13 3892 (0x0F34)MSI: Action 16:28:13: SmsDeinstallDesktopClient. Deinstalling the SMS Legacy Client or SMS 2.0 Client ccmsetup 15/10/2009 16:28:13 3892 (0x0F34)MSI: Action 16:28:14: CreateFolders. Creating folders ccmsetup 15/10/2009 16:28:14 3892 (0x0F34)MSI: Action 16:28:15: CcmDetectFilesInUseRollback. ccmsetup 15/10/2009 16:28:15 3892 (0x0F34)MSI: Action 16:28:15: CcmDetectFilesInUse. ccmsetup 15/10/2009 16:28:15 3892 (0x0F34)MSI: Action 16:28:16: CcmDetectFilesInUseCommit. ccmsetup 15/10/2009 16:28:16 3892 (0x0F34)MSI: Action 16:28:16: InstallFiles. Copying new files ccmsetup 15/10/2009 16:28:16 3892 (0x0F34)MSI: Action 16:28:31: RegisterExtensionInfo. Registering extension servers ccmsetup 15/10/2009 16:28:31 3892 (0x0F34)MSI: Action 16:28:31: WriteRegistryValues. Writing system registry values ccmsetup 15/10/2009 16:28:31 3892 (0x0F34)MSI: Action 16:28:38: WriteIniValues. Writing INI files values ccmsetup 15/10/2009 16:28:38 3892 (0x0F34)MSI: Action 16:28:38: RegisterTypeLibraries. Registering type libraries ccmsetup 15/10/2009 16:28:38 3892 (0x0F34)MSI: Action 16:28:40: SelfRegModules. Registering modules ccmsetup 15/10/2009 16:28:40 3892 (0x0F34)------------Last rows of client.msi.logMSI (s) (28:20) [16:28:40:715]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.MSI (s) (28:20) [16:28:40:730]: ProcessTypeLibraryCore returns: 0. (0 means OK)MSI (s) (28:20) [16:28:40:730]: Executing op: TypeLibraryRegister(,,FilePath=C:\WINDOWS\system32\CCM\dcmsdk.dll,LibID={62591F60-6F08-4498-8B89-C43ED9AB43CF},,,Language=0,,BinaryType=0,IgnoreRegistrationFailure=0,)MSI (s) (28:20) [16:28:40:746]: QueryPathOfRegTypeLib returned -2147319779 in local context. Path is ''MSI (s) (28:20) [16:28:40:746]: CMsiServices::ProcessTypeLibrary runs in local context, not impersonated.MSI (s) (28:20) [16:28:40:761]: ProcessTypeLibraryCore returns: 0. (0 means OK)MSI (s) (28:20) [16:28:40:761]: Executing op: ActionStart(Name=SelfRegModules,Description=Registering modules,Template=File: [1], Folder: [2])MSI (s) (28:20) [16:28:40:761]: Executing op: ProgressTotal(Total=28,Type=1,ByteEquivalent=1300000)MSI (s) (28:20) [16:28:40:761]: Executing op: SetTargetFolder(Folder=C:\WINDOWS\system32\CCM\)MSI (s) (28:20) [16:28:40:761]: Executing op: RegSelfReg(File=StatusAgentProxy.dll,FileID=StatusAgentProxy_dll.A6940213_CD40_4753_8BA2_E803376DECC3)MSI (s) (28:20) [16:28:41:168]: Executing op: RegSelfReg(File=Sched_ps.dll,FileID=Sched_ps_dll.A6940213_CD40_4753_8BA2_E803376DECC3)-----------No errors messages in both logs, only a kind of freeze in the middle of msi installation...Installation freeze at this step, on client computers ccmsetup.exe + 3 msiexec.exe are still runningAt the beginning somes computers was upgraded successfully. The same problem also appears when i uninstall SMS2003 client first.Thanks for your help

Can you email me the entire ccmsetup.log? john marcum at gmail dot com without spaces or anything.John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Hi John,I just sent the logs to you.Thanks for your help.

I am having the same problem. I would be interested to see what the solution is. Thanks.

I'm not alone :)Do you try to upgrade sms2003 sp1 clients to SCCM 2003 sp1 clients? I think the workaround is to first uninstall the old client and then push the install of SCCM client, in this case the installation will works properly.

No need to uninstall the SMS 2003 client. ConfigMgr's ccmsetup.exe does that automatically for you. Just have a look at ccmsetup.log. It should tell you what part took a long time.

Thanks Torsten, i know that but the problem is that the ccmsetup show nothing special, no error, the log just hang at "MSI: Action 16:28:40: SelfRegModules. Registering modulesccmsetup15/10/2009 16:28:403892 (0x0F34)" and i don't know why.

It is not supported to upgrade directly from SMS 2003 SP1 to SCCM SP1 therefore it's very possible that the client upgrade may not work. Just try manually running ccmclean on a client then push the SCCM client to it and see if that works. Another option would be to upgrade the SMS 2003 clients to SMS 2003 SP3 clients then try the upgrade to SCCM clients.Here are the supproted upgrade paths for SCCM SP1http://technet.microsoft.com/en-us/library/cc161823.aspxJohn Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum

Thanks John, it is what i'm thinking, i will find another solution.Thanks

Hi everyone again, i reopen my answer.After some others tests i got the same problem on computers with sms2003 sp2 and sp3 clients (upgraded from SP1)and on computers without sms.If i understand the microsoft upgrade strategy (http://technet.microsoft.com/en-us/library/cc161823.aspx) i should have done this in order:- upgrade SMS2003 sp1 to sp3- install SCCM without service pack (side by side upgrade)- Migrate SMS2003sp3 clients to SCCM clients- Upgrade to SCCM SP1 (because i don't used SCCM SP1 complete release)- Migrate clients to SCCM SP1In my case i upgraded directly to SCCM SP1 (side by side upgrade) but all my clients are still in SMS2003 SP1 client version. I tried to update all of them since 2 weeks but in most cases it doesn't works. Only a couple of them was upgraded successfully.Also after use ccmclean on clients the install failed in most cases too, exactly like the direct update without ccmclean.Please help.Thanks

I have issue like you (with setup freeze at dll registration), and still can't find the solution,workaround ismanual DLL register at client or many,MANY reboots:http://social.technet.microsoft.com/Forums/en/configmgrsetup/thread/e51ad4ea-5de4-40df-b44f-01728d5000a8and some more1)Have you any antivirus or HIP system on your client? They may not work propertly.2) Check how your DNS and WINS works. =-)In my case i install NEW SP1 clients at NEW workstations!And one more thing, maybe that can help you if you use McAfee solutions:http://community.mcafee.com/thread/5015

Hi Aero,Thanks for your interresting reply, it will be helpful.Yes we have HIPS 7.0.0 implemented on our 2000 XP clients, i will try to prevent HIPS to interact with msi installation.For the moment my workaround is to kill the msi who register the dlls and after that the installation continue normally.I'll keep you informed about HIPS.Thanks

I confirm that the problemcomes from McAfee HIPS (IPS part). In my case the IPS part of HIPS firewall was configured as monitoring (not blocking) on all of my clients and the problem comesonly with patch 1, 2 or 3 of HIPS 7 (I think so). No Problem with the latest patch (5 or 8 for example.)We tried to disable the IPS part of HIPS on some computers and the SCCM client installation was successfull, the DLLs was registered without problem.Next step is to upgrade all clients with patch 8 of HIPS and test SCCM client installation again.Hope it will help.Teschmi

hi; Plese have a look at client.msi.log. I noted on one of my clients logs that some files have been marked for deletion after reboot. It was also frozen at the same step. Once machine rebooted sccm client installation resumed and then was successfull Thank you all

Just FYI...our clients all have Patch 8 installed and this is STILL an issue. We used to have our SCCM client install via a startup script but McAfee HIPS will still stop the client install at the SelfRegModules. Registering modules location. I wish we could figure out why and how to prevent this.

Hi Jlumadue, You have to create an exception rule in your McAfee EPO server to exclude all msiexec operation from HIPS IPS monitoring. By this way HIPS will not affect any operation executed by msiexec.exe. I don't remember exactly how to do that in EPO console but i could ask my EPO administrator if you can't find the place to add your exception rule. Teschmi