Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Adminoob

  • Rank

Profile Information

  • Gender
  • Location
    Michigan, USA
  1. I have an SCCM 2012 R2 distribution point that was accidentally reinstalled (the DP role removed, then re-added - no content was deleted) the packages and content library are all still on the DP, is there any way to get the reinstalled DP to recognize and associate with the now old content? it seems like it should just be a matter of recreating the content mapping, but I have no Idea how to do that. Please help!
  2. I tried this method, first test was a bust, had to remove the variable and just use C:, second test was a bust because the image finished and I noticed that the CCM client was missing most of the actions, and the notification was disabled, and the patch didn't apply...time to dig through logs.
  3. Thank you for the excellent info, do you also have a guide updated to for SCCM 2012 R2 + Server 2012 + SQL 2012? WSUS is now a role rather than a separate install for Server 2012 so there are a few differences regarding prerequisites and install processes.
  4. In SCCM 2007 I could apply client patches during the config manager client install task of an OSD like thus: PATCH="%_SMSTSMDataPath%\OSD\AH2000A6\hotfix\KB2994331\Client\x64\Configmgr2012ac-r2-kb2994331-x64.msp" Can it be done the same way in 2012? the hotfixes no longer reside in the client install folder, so the .msp's would have to be copied there manually and the client package updated. I've found at least one post where this was being done, but I cannot find any official MS KB saying this is supported or not: http://www.deploymentresearch.com/Research/tabid/62/EntryId/189/Installing-
  5. when I create a package and then distribute it to a DP it first copies a temp file to the root of D:\SMS_DP$, Then it transfers those files to D:\SCCMContentLib, and creates the necessary files within the 3 subfolders, finally, and this only happens if the box is checked to copy to the package to a share, a folder with the extracted files is copied to D:\SMSPKGD$\(PACKAGE_ID). It also creates a .tar file in smssig. When I distribute an application pretty much the same thing happens minus the extracted file in SMSPKGD since applications cannot be run from the DP, which I find annoying and o
  6. Hello, When I distribute content to a DP, I get this error repeatedly in my distmgr.log: SetObjectSecurity failed; 0x80070002 then a ton of these after: Failed to decrypt cert PFX data I'm running with HTTPS, and the packages always seem to copy ok, anyone know what this error indicates?
  7. Hello! Ok, no one, not even Microsoft engineers can seem to provide a clear and definitive answer on this topic, everyone's understanding of the .PCK file with relation to SCCM 2012 is clear as mud. I understand what .PCK files are...in the SCCM 2007 world, and how they work, all that jazz, what I don't understand is how/when/why they would be used by SCCM 2012...it seems that sccm 2012 would only need these .pck files during a reassignment of a shared DP in a migration scenario...even that surmise is sketchy since I've watched very closely the DP content conversion process and at no time
  8. I had the same problem and found this thread, only to realize that my issue was caused by our DHCP server running out of IP's! Sometimes it is the simple things that elude us.
  9. Thank you. Should I upgrade my SCCM 2007 to R3 prior to using the migration connector? Or does that not matter? T
  10. Hello, If my current SCCM 2007 R2 is installed on a 32bit Windows Server 2003, and I plan on migrating to SCCM 2012 on Server 2008 R2 x64, will there be any problems with the migration process going from a 32bit to 64bit environment? The reason I ask is that I read in a forum post somewhere that an admin in a similar situation did the following steps: performed a full backup of SCCM 2007 running on W2K3 32bit, reinstalled SCCM 2007 on a different server running W2K8 x64 and restored from that backup he made essentially creating a mirrored install but on a x64 OS instead, they then installed
  11. Thanks Jorgen (a bit late, sorry!) I did manage to simply add an unattend.xml to the B&C TS, and this worked fine, but I found out the hard way that you MUST remove that file prior to running the capture process, otherwise it just continues to boot into audit mode (the sysprep process should remove that file, but it doesn't , not sure why that is.) T
  12. Hello, I have a build and capture TS that works great for creating my thin-image, however, I would like to somehow interrupt the build and capture at some point and force it to boot into audit mode so I can install some apps that cannot be repackaged or otherwise scripted. Can this be done? Thanks!
  13. That link is dead, or is down at the moment. I have uploaded a zipped copy of the file here: http://www.filedropper.com/wsname
  14. Sorry for the dumb question: Do those existing workstations have the CCM client installed already? And how did you figure out that you must disable those specific services in order to get the patch to install?
  15. Hi there, I'm in the same boat, did you ever resolve this issue? I tried following Microsoft's method here: http://support.microsoft.com/kb/977384 but on my test deployment machine, both the ConfigMgr client and the hotfix failed to install, the error on the deployment machine referenced a problem copying the hotfix to a temp location. I'm going to attach a portion of my client.msi.txt file from the destination pc that failed. Also, here is the exact commands I'm using in my TS (it is the Microsoft suggested commands, plus the standard setting for cache) PATCH="%_SMSTSMDataPath%\OSD\CEC0030\
  • Create New...