Back in 2012 I wrote an article about dynamically setting a computer name during a Task Sequence. Here is my updated and improved script. I’m currently setting up a deployment solution running SCCM with MDT 2013…
You can deploy the SCCM client several ways, the most common being through SCCM, manual install via the ccmsetup.exe. This article describes how to install and uninstall the client manually.
Lately we have gotten some inquiries asking us to share some “must have” SCCM collections, here are some of our commonly used queries.
An update for the System Center Endpoint Protection 2012 Client was released today, and the installation fails on our customers servers.
An acticle about what’s new in Configuration Manager 2012 R2, what to consider before an upgrade and how to proceed with the actual upgrade.
Remember, uninstalling Service Packs or R2 is not supported, so make sure you don’t rush through it and you’ve completed the recommended actions on the checklist!
Lately I’ve been struggling with deploying Windows 7 via SCCM 2012 to a workstation running a RevoDrive as primary storage. Right now 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.