![]() However, the previous app appears to have exited with a clean success code. Google tells me that 1618 means that another instance of msiexec is already running/another install is in progress. We traced back through the logs, and found that, in the AppEnforce.log, it was always failing on a specific app, giving the 0x80070652 error and informing us that the app was exiting with code 1618. For the record, nothing has changed on the SCCM servers, the OSD Task Sequence, or any of the software which it is deploying. However, over the last 2 days, around 50% of machines have begun failing to complete the OSD Task Sequence. ![]() Our deployment department images/re-images around 130 machines in any given day.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |