Skip to content

Orphaned Source Files

Featured Replies

All sorts of fun questions from me today. I noticed that my sources folder, where I downloaded my Windows Updates to, is now empty. The log file looks like it considered them "orphaned" and removed the files from the source folder. Now the deployment package is reporting as failed since it can't locate any of its source files. Does this deletion occur after it creates all of the packages for the DPs? I don't seem to remember this happening in SCCM 2007.

Thanks,
Brenden

  • Author

I believe I found out why the source files were deleted. I had two packages pointed to the same source location. Typically SCCM doesn't allow this to occur, but one source entry used the FQDN while the other used shorthand. I'm guessing each package saw the other package's files, decided they didn't belong, and deleted them. Hope this helps someone.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.