topcal

This script (link below) installs or uninstalls the SCCM Client 2007 or 2012. I've used PSAppDeployToolkit and other scripts from different sources to accomplish the task. The installation happens in an OFFLINE mode. CCMSETUP will not download the supporting files from the server but utilize the content in the FILES folder of the tool-kit. <ALL THINGS LOCAL> IMPORTANT: Copy the content of the CLIENT folder on the SCCM Server <\\SCCMServer\SMS_SiteCode\Client> and paste it into the FILES folder. Run with elevated permissions. IF running from a share; the computers 'SYSTEM' account should have read access to the FILES folder. The best way to do this is to give everyone read access to the package share. Download from Microsoft's Technet Website. After the SCCM client install, the script will wait for 60 seconds and then trigger a Machine Policy & Evaluation Cycle and a Hardware Inventory cycle. Logging is done to: C:\Windows\Logs\Software Copy the content of the CLIENT folder on the SCCM Server <\\SCCMServer\SMS_SiteCode\Client> and paste it into the FILESfolder. Install SCCM Client: Options: SMSCACHESIZE SMSMP SMSSITECODE FSP SMSSLP DNSSUFFIX The below command will SILENTLY installs the SCCM Client (Offline) .\Deploy-Application.EXE -DeploymentType Install -DeployMode silent -SMSCACHESIZE 10260 -SMSMP "FQDN-of-Management-Point" -SMSSITECODE "Your-Site-Code" -FSP "FQDN-of-Fall-back-Status-Point" The below command will INTERACTIVELY installs the SCCM Client (Offline) .\Deploy-Application.EXE -DeploymentType Install -DeployMode Interactive -SMSCACHESIZE 10260 -SMSMP "FQDN-of-Management-Point" -SMSSITECODE "Your-Site-Code" -FSP "FQDN-of-Fall-back-Status-Point" Uninstall SCCM Client: The below command will SILENTLY Uninstall the SCCM client. .\Deploy-Application.EXE -DeploymentType UnInstall -DeployMode Silent The below command will INTERACTIVELY Uninstall the SCCM client .\Deploy-Application.EXE -DeploymentType UnInstall -DeployMode Interactive

Just for the people who are still looking for a solution. Launch the HTA using the following command on a 64 bit machine. ccmexec.exe (SMS service) runs as a 32 bit process on a 64 bit machine. In-order to invoke the 64 bit process of mshta.exe, we've got to call it using the following method in SCCM. if not, windows redirects automagically to the 32 bit version of mshta.exe. %WINDIR%\sysnative\mshta.exe <path-to-the-HTA> and if you are using SCCM 2012 with WinPE 5, use the power of dot net vs HTA (which I still like): An example dotNET application on Microsoft Technet <Click to open technet article> Topaz Paul: nz.linkedin.com/pub/topaz-paul/19/275/328/

This application would allow you to present a front-end to an active end-user who is executing the SCCM 2012 task sequence. Click here to download from Microsoft's technet website.

Microsoft Deployment Tool kit is great and works wonders after its initial setup. But again, its too complicated to get basic sequences done. I recommend using it for interactive sequences. But for the scenario outlined in this post, a standard SCCM 2012 task sequence will suffice. Use the following front-end to set the initial variables and then perform the normal SCCM 2012 task sequence steps (no dramas). This works for me all the time for small sequences. http://gallery.technet.microsoft.com/SCCM-2012-OSD-Task-9c3f2be7