SCCM advanced client install failing jh

We have a problem installing the SCCM agent on two Windows 2003 servers, both with IIS.

We normally deploy via Windows Update but as this was failing we also tried installing by manually running ccmsetup - both as and not as a service. All report the same errors. I've included what I think are the relevant errors below as a code snippet.

Things I have checked:

1) The Administrator account had been renamed so I put it back to Administrator
2) The IIS accounts do match the machine name

Note that we were provided these machines as VM images in a batch of five. They were dis-joined from their original domain and joined to ours. Three of the five are fine but the two mentioned are reporting the error below.
Extract from ccmsetup.log:


<![LOG[MSI: Action 13:44:50: RegisterUser. Registering user]LOG]!><time="13:44:50.771+000" date="03-18-2011" component="ccmsetup" context="" type="0" thread="3996" file="msiutil.cpp:374">
<![LOG[MSI: Action 13:44:50: CcmFixupServiceConfigInit. ]LOG]!><time="13:44:50.771+000" date="03-18-2011" component="ccmsetup" context="" type="0" thread="3996" file="msiutil.cpp:374">
<![LOG[MSI: Action 13:44:50: CcmSetObjectSecurityInit. Applying security permissions]LOG]!><time="13:44:50.849+000" date="03-18-2011" component="ccmsetup" context="" type="0" thread="3996" file="msiutil.cpp:374">
<![LOG[MSI: Setup failed due to unexpected circumstances
The error code is 80070534]LOG]!><time="13:44:51.005+000" date="03-18-2011" component="ccmsetup" context="" type="3" thread="3996" file="msiutil.cpp:360">
<![LOG[Installation failed with error code 1603]LOG]!><time="13:44:51.317+000" date="03-18-2011" component="ccmsetup" context="" type="3" thread="3996" file="msiutil.cpp:889">
<![LOG[Next retry in 120 minute(s)...]LOG]!><time="13:44:51.489+000" date="03-18-2011" component="ccmsetup" context="" type="0" thread="3996" file="ccmsetup.cpp:8348">


Extract from client.msi.log:


MSI (s) (78!44) [14:19:33:242]: Creating MSIHANDLE (9855) of type 790531 for thread 2116
MSI (s) (78!44) [14:19:33:242]: Creating MSIHANDLE (9856) of type 790531 for thread 2116
Action start 14:19:33: CcmSetObjectSecurityInit.
MSI (s) (78!44) [14:19:33:242]: Closing MSIHANDLE (9856) of type 790531 for thread 2116
[14:19:33] @@ERR:25001
MSI (s) (78!44) [14:19:33:242]: Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
The error code is 80070534


Event log entry:


Event Type:	Error
Event Source:	MsiInstaller
Event Category:	None
Event ID:	10005
Date:		18/03/2011
Time:		14:19:33
User:		NT AUTHORITY\SYSTEM
Computer:	SERVER1
Description:
Product: Configuration Manager Client -- Error 25001. Setup failed due to unexpected circumstances
The error code is 80070534

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 32 36 30 39 45 44 46   {2609EDF
0008: 31 2d 33 34 43 34 2d 34   1-34C4-4
0010: 42 30 33 2d 42 36 33 34   B03-B634
0018: 2d 35 35 46 33 42 33 42   -55F3B3B
0020: 43 34 39 33 31 7d         C4931}

Open in new window

LVL 1
tlcsupportAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

merowingerCommented:
0
tlcsupportAuthor Commented:
I don't think it's that. I've seen that article already and our IIS accounts do match the machine name - i.e the system was sysprep'd properly if it was imaged. We're also not seeing any DCOM errors in our event log.
0
merowingerCommented:
i would check name resolution and retry a sysprep
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tlcsupportAuthor Commented:
I think we'll be logging this with Microsoft in the coming days so will see what they suggest. Syspreping the machine is a bit drastic and not practical for the users of the servers affected.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server Apps

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.