Tag: deployment
-
Ensure the Operating System applys to C: drive not D: drive
This problem will increase more and more as everyone starts to use wim’s instead of the OS media in SCCM. There are a few workarounds for this problem however the best method is to force the new OS the reevaluate Drive Letters with 3 easy steps after applying the OS Create a Run Command Line step…
-
Creating Collections to deploy ConfigMgr client updates (the easy way)
Get the Servicing Exstension from Microsoft NOW as it does all the work!!! http://blogs.technet.com/b/configmgrteam/archive/2014/12/09/now-available-microsoft-system-center-2012-configuration-manager-servicing-extension.aspx Once you have this, in the Admin node, there’s a site servicing section -> client targeting. You click ‘Create Query’ and it makes a nice query for your collections. Then you go about creating your collection. click next. Select Add Rule -> Query Rule…
-
Format failed (0x80070057) during task sequence.
Update: If this is happening to you I recommend importing the boot wim again creating a new one and only adding the network drivers (in the surface pro 3 case) and test using that boot wim with a copy of your task sequence. Then add existing sata/network drivers you need for other…
-
How To: Create Automatic Deployment Rules for Patch Tuesday Software Updates
Automatic deployment of updates is one of the best features of SCCM. Automation in general is awesome. The best way to use Automatic deployment rules (ADR) is to have them run on Patch Tuesday which is the second Tuesday of the month when Microsoft releases their updates generally before 11:00 PST/PDT (I am Australian based so…
-
KB: Temporary partition to stage boot wim on UEFI booted devices fails.
When not using the latest version of bootable media and the system is not partitioned SCCM is meant to create a temporary partition to stage the correct boot wim. What actually happens is it just creates 1 big NTFS partition. What actually happens is it just creates 1 big NTFS partition. Then it checks the…
-
Create a compliance baseline to remove a folder
In this example we are killing the Silverlight start menu folder enabling us to use the Windows Updates while keeping the start menu clean. Create the Configuration Item 1. In the console click Create Configuration Item 2. Name your configuration item, click ‘This configuration item contains application settings’ and click Next 3. Select ‘Always assume application…
-
Optimize the ‘build and capture’ time and size (SCCM Build)
Inspired by Johan’s post http://www.deploymentresearch.com/Research/tabid/62/EntryId/174/Building-reference-images-like-a-boss.aspx I am probably one of the few that uses SCCM to capture base images. I use it because I create a thick image and it keeps the history of packages that it has installed meaning that newly imaged machines will know that they have already installed software x when…
-
KB: PXE boots using the wrong wim file.
If you happen to change the source name of a boot wim the pxe point may boot using the old file. To fix rename <Drive Letter>RemoteInstallSMSImages<WIMPkgID>oldbootname.wim to oldbootname.wim.old Next PXE boot it will then use the new boot.wim file.
-
Application Catalog logs
There are 2 operational logs for the App Catalog server side. <Drive Letter>SMS_CCMCMApplicationCatalogLogsServicePortalWebSite.log <Drive Letter>SMS_CCMCMApplicationCatalogSvcLogsServicePortalWebService.log Troubleshooting If the App catalog has an error message “Cannot Connect to the Application Server” this is referring the to the ServicePortalWebService.log. So far I have only seen the error: error: WriteHeadersCallback(WebExceptionStatus errorStatus, ConnectStream stream, Boolean async) in the…
-
Versioning and naming your base SOE .wim during OSD
If you replace the base wim (via build and capture) frequently it can be good to set versions and date the wim file that you import. It makes it easy to revert back if a change didn’t go so well. Below are the steps in my build and capture to do versioning and work around…