Search the Community

I am dealing with a really weird issue. We have two environments one is SCCM 2007, and we just stood up the SCCM 2012 R2 environment to transfer over. I am trying to transition the clients over subnet by subnet using the client push install. SOme installs go without issue. But a good number of installs fail with a 1603 error. I know that the 1603 error is a generic error, so I was able to go through the Client.msi.log to find this error. "[10:25:19] ERROR: ITaskService::Connect failed with error 0x8007045a". This error is not in a successful deployment, and unfortunately no where in the googleverse either. I have attached the CCMSetup and Client.msi log, and would appreciate any help. My next step would be a call to MS. Happy Holidays and thanks, Ed Pertinent Log sections: [10:25:19] Automatic Delayed Start configuration is enabled for CCMEXEC MSI (s) (64:40) [10:25:19:418]: Executing op: CustomActionSchedule(Action=CcmRegisterWinTaskRollback,ActionType=3329,Source=BinaryData,Target=CcmRegisterWinTaskRollback,) MSI (s) (64:40) [10:25:19:433]: Executing op: ActionStart(Name=CcmRegisterWinTask,Description=Registers tasks with Windows Task Scheduler.,) MSI (s) (64:40) [10:25:19:433]: Executing op: CustomActionSchedule(Action=CcmRegisterWinTask,ActionType=3073,Source=BinaryData,Target=CcmRegisterWinTask,) MSI (s) (64:40) [10:25:19:433]: Creating MSIHANDLE (25398) of type 790536 for thread 3392 MSI (s) (64:B8) [10:25:19:433]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIFF7F.tmp, Entrypoint: CcmRegisterWinTask MSI (s) (64!5C) [10:25:19:496]: Creating MSIHANDLE (25399) of type 790531 for thread 1884 MSI (s) (64!5C) [10:25:19:496]: Closing MSIHANDLE (25399) of type 790531 for thread 1884 [10:25:19] ERROR: ITaskService::Connect failed with error 0x8007045a MSI (s) (64:B8) [10:25:19:496]: Closing MSIHANDLE (25398) of type 790536 for thread 3392 CustomAction CcmRegisterWinTask returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (64:40) [10:25:19:542]: User policy value 'DisableRollback' is 0 MSI (s) (64:40) [10:25:19:542]: Machine policy value 'DisableRollback' is 0 Action ended 10:25:19: InstallFinalize. Return value 3. ccmsetup.log ccmsetup-20131224-102250.log client.msi.log

Hey all, After reading through all of the setup articles to get SCCM 2007 setup, I'm now trying to do a push install of the client to a PC, and nothing seems to be happening. SCCM lists the client as "N/A" for approved, and I made sure that the client install credentials are admin-level, and are enabled as local machine admin. The DNS A record is correct, and from what I can tell everything else is setup too. I'm not getting any errors or feed back. Any thoughts? -Guy Update: So obviously I'm blind, as I didn't think to look at the error logs... Severity Type Site code Date / Time System Component Message ID Description Warning Milestone ABC 10/25/2011 10:34:43 AM 2008R2 SMS_CLIENT_CONFIG_MANAGER 3014 SMS Client Configuration Manager cannot connect to the machine "UsersPC". The operating system reported error 5: Access is denied. Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. Possible cause: A remote client installation account was not specified in the SMS Admin console, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active remote client installation accounts are specified in the SMS Admin console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines. There was an error like this for every client, so this has cleared now that I updated the client install credentials, but I'm getting a slightly different error now: Severity Type Site code Date / Time System Component Message ID Description Warning Milestone ABC 10/25/2011 10:55:10 AM 2008R2 SMS_CLIENT_CONFIG_MANAGER 3014 SMS Client Configuration Manager cannot connect to the machine "OPTI2". The operating system reported error 1068: The dependency service or group failed to start. Possible cause: The client is not accessible. Solution: Verify that the client is connected to the network and that the SMS Service account or (if specified) the SMS Client Remote Installation account has the required privileges, as specified in the SMS documentation. Possible cause: A remote client installation account was not specified in the SMS Admin console, the account is not valid, is disabled, or has an expired password. Solution: Ensure one or more valid and active remote client installation accounts are specified in the SMS Admin console, that the account names and passwords are correct, and that the account has the required administrator rights on the target machines.