When you are creating a plan for deploying software updates to machines using System Center Configuration Manager, you most likely are creating at least two different deployments: one for pilot and one for production.
If you wanted to completely automate this process prior to ConfigMgr 1511, you were required to create one Automatic Deployment Rule for Pilot and one for Production.
Starting with ConfigMgr 1511, it is possible to create several deployments for one Automatic Deployment Rule, which means you can minimize the amount of Automatic Deployment Rules.
Here is a step by step guide for adding a new deployment to your existing Automatic Deployment Rule. I am assuming that we are adding a deployment to your previous ADR used for Pilot machines.
- Select the Automatic Deployment Rule for which you want to create a new deployment:
2. Right-click and press Add Deployment.
3. Browse for the collection where you want to create the new deployment:
4. Run through the next steps as you would previously when creating a new Automatic Deployment Rule.
5. Done! Now you have two deployments for one Automatic Deployment Rule. In this case, I have one for Pilot and one for Production, where the Production deployment is set with a deadline one week after the Pilot.
- Bulk import from CSV
- Removes objects discovered by System Discovery before importing the device, to fix issues with duplicate objects
- Verifies if the machine name and/or MAC address already exists
- Possibility to change MAC addresses
- Logging provided in a CMTrace format
- Automatically populates MAC address from the ConfigMgr database
- Provides the user a dropdown list of collections within a specific folder in ConfigMgr
- Various validation checks
- ConfigMgr 2012 R2 SP1 or later
- Powershell v3
- Permissions required by account running the tool:
- Import new devices
- Delete devices
- Add device to collection
- Example of role with minimum permissions:
The ConfigMgr Import Tool v1.0 is available on the TechNet Gallery.
Running the Tool
- Open a new Powershell window with a user that has sufficient permissions in ConfigMgr.
- Browse to the folder containing the tool and run it with the command line:.\ConfigMgr-Import-Tool-v1.0.ps1 -<Parameters>
.\ConfigMgr-Import-Tool-v1.0.ps1 -Container OSD -SiteCode P01 -SiteServer p01.danielclasson.local -LogPath \\p01\logs$
- Container = Folder in ConfigMgr containing OSD collections.
- SiteCode = ConfigMgr Site Code
- SiteServer = FQDN of ConfigMgr Site Server
- LogPath = UNC path to log files. REQUIRED if logs are to be written.
- CSVPath = UNC path to initial CSV path directory. OPTIONAL.
Manually import devices
If you wish to import a single computer or a few computers, use Manually import devices.
However, if you wish to import many computers, refer to the next section on how to Bulk Import Devices.
- Simply enter the Device Name in the text box on the right hand side.
- If the device exists, press Validate to populate the MAC address field.
- If the device does not exist, enter the MAC address in the MAC address field.
- If the device exists, but you want to change the MAC address in the database, change the MAC address in the field.
Add to import list
- If the validation is successful, Add to selection will be enabled. Press the button to add the device to the list.
- Continue with these steps until you have the desired devices in the list.
- If you want to remove a computer from being imported, select, the computer in the list and press the button Remove from selection.
When the correct devices are in the import list, press Import Devices.
Bulk Import Devices
The best way to import many computers at a time is by bulk importing them using a CSV file.
Create a file name with a *.csv extension with two rows named ComputerName and MAC like the below example:
Import devices from CSV
- Once the CSV file is ready, select Bulk Import Devices.
- Select the OS Deployment Collection from the dropdown list.
- Press Browse and select the CSV file.
- Verify that the correct devices are in the import list. If not, modify the CSV and import it again.
- When ready, press Import Devices.
I hope that the tool will prove useful to you and please send me suggestions for further improvements 🙂
If you want to fully remove an installation of Office, the best way is to use a VBScript called Offscrub, which is provided by Microsoft. This script has been widely used for removing Office 2007, 2010 and 2013.
This script is also available for Office 2016 and Office 365, but it is slightly hidden.
Follow the below instructions:
- To retrieve it, go to this link: https://support.office.com/en-us/article/Uninstall-Office-2013-Office-2016-or-Office-365-from-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8?ui=en-US&rs=en-US&ad=US
- Go to Option 2 – Completely uninstall Office with the easy fix tool and download the easy fix tool which is a file called O15CTRRemove.diagcab.CAB
- Go to the download location and open the CAB file using 7-Zip or similar.
- Extract OffScrub_O16msi.vbs
- Done! Now you can run the script either manually on a computer or most likely as part of another script deployed through ConfigMgr 🙂