Lately I’ve been struggling with deploying Windows via SCCM 2012 to a workstation running a RevoDrive as primary storage. The MDT scripts do not seem to think that the card is bootable…
I set up a small script which adds the username supplied during OSD to the local administrative group instead, which you could run from a TS.
This way only the Primary User gets elevated privileges over their own PC.
I ran into this issue when switching between our production and test environment. If you’re receiving the 0x87D00607 error you are most likely connected to a network/site which does not have a Configuration Manager Boundary or Boundary Group.
If you’re having trouble deploying the SCCM client and you’re getting Error 53 you should verify that the Client Installation account is local administrator and that Remote administration is turned on.
After setting up a new domain and deploying SCCM 2012 I came to realize how much work it actually is to set up new applications.
I have made a script which creates AD groups and Collections.
Understanding how the Configuration Manager client works is a crucial part of troubleshooting.
Here you will find information about how to retrieve policies from the SCCM server.
You might see content mismatch warnings in System Center 2012 Configuration Manager when content validation runs and determines that there is a discrepancy between the expected list of packages in WMI on the distribution point and the packages in the content library.
In System Center 2012 Configuration Manager, Microsoft added the capability to automatically remove software
update content from distribution points when that content is related to expired updates.
Our Distribution Point crashed and gave us Hash Mismatch on pretty much all my Applications, Programs and Updates. After this was resolved we started having issues with PXE…
I’ve been troubleshooting an issue with application/client installations for a while now. Some applications have been getting hash mismatch when downloading…