Upgrade to Exchange 2013 CU6


  • Reboot servers to clear any updates that have applied.
  • Prepare Schema and Active Directory.
  • Place server in Maintenance Mode.
  • Run the Exchange Setup.
  • Take server out of maintenance mode.

Active Directory Preparation:

From an elevated prompt you can run the following commands:

  • Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
  • Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

Start Maintenance Mode:

(**You need to open up the Exchange Management Shell as Administrator or point 3 will give you a permission error**)

Open up an elevated Exchange Management Shell and run the 4 commands, let each one complete before doing the next one:

  • Set-MailboxServer <Server Name> -DatabaseCopyActivationDisabledAndMoveNow $True
  • Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Draining –Requester Maintenance
  • Suspend-ClusterNode –Name <Server Name>
  • Set-MailboxServer –Identity <Server Name>–DatabaseCopyAutoActivationPolicy Blocked

Start Exchange 2013 CU6 Upgrade:

Open up the Exchange CU6 file you downloaded and extracted and double click the Setup file.


  • Click Next.


  • Checking for Updates. Wait for it to finish.



  • Once it has checked for updates then click Next.




  • Exchange setup busy copying files.


  • Copy progress screen.



  • Exchange Setup busy initializing.




  • Once it has finished initializing you can now start the upgrade. Click Next.


  • Accept the license agreement and then click Next.



  • Readiness Checks. wait for it to complete.



  • Now that its complete click the Install button. Below are the different steps:















Setup24 Setup25


Stop Maintenance Mode:

We need to run 4 commands again to Stop Maintenance Mode:

(**Remember you need to run these commands as an administrator from an elevated Exchange Management Shell)

  • Set-MailboxServer –Identity <Server Name> –DatabaseCopyAutoActivationPolicy Unrestricted
  • Resume-ClusterNode –Name <Server Name>
  • Set-ServerComponentState –Identity <Server Name> –Component HubTransport –State Active –Requester Maintenance
  • Set-MailboxServer –Identity <Server Name> –DatabaseCopyActivationDisabledAndMoveNow $False

Now after that run the following command to check the DAG status:

  • Get-Mailboxdatabasecopystatus *

Hope it helps.


Install SNMP Windows Feature and Configure SNMP in System Center Operations Manager 2012 (SCOM)


  • Install Windows Features.
  • Configure SNMP Services.
  • Configure SCOM.

Install Windows Features

Open up server manager.


  • Once the Server Manager has initialized click on “Add roles and features”


  • Leave Role-based or feature-based installation as default and click Next.


  • Leave the default and then click Next.


  • Click Next on the roles section.


  • Scroll down on the features section until you find SNMP. Press the arrow on the left to expand it. Click both checkboxes.


  • Once you have clicked the checkboxes in the previous screen then this window will come up. Click the “Add Features” button.


  • Now that both are selected the Next button enables, click Next to continue.


  • Click the Install button.


  • Installation starting.


  • Feature installation busy. You can click the Close button and monitor the install from Server Manager.


  • Once the installation has completed click the close button.

Configure SNMP Services

Open up Services (you can click start -> Run -> Services.msc)


  • Disable the SNMP Trap Service.
  • Make sure the SNMP Service is started and set to Automatic.


  • Right Click on SNMP Service and select properties.


  • Click on the Security Tab.
  • Click on the “Add” button.


  • Select the Community Rights.
  • Type in the Community Name.
  • Click the Add button.


  • The details will now show under the “Accepted Community Names” Section.
  • Click OK.

Configure SCOM.

Open up the SCOM console.


  • Step 1 -> Click on the Authoring Tab.
  • Step 2 -> once the menus have refreshed click on the Rules line.


  • Step 1 -> Right Click Rules.
  • Step 2 -> Click on “Create a new rule”


  • The “Create Rule Wizard” screen will come up as shown above.


  • Expand Collection Rules -> Event Based.
  • Click on SNMP Trap (Event).
  • We are going to create a new management pack for rules. Click the New button as shown above.


  • Step 1 -> Enter in the Name.
  • Step 2 -> Click Next.


  • If you want to add in a knowledge Article click the “Edit” button.
  • Click on Create.
  • Click Next on the following screen.


  • Now we are going to create a new Rule. Step 1 -> Give the rule a name.
  • Step 2 -> Click on the Select button.


  • Step 1 -> In the box type in “Node” and then click on “View all Targets”. Press Enter.
  • Click on “Node and then Step 2 -> Click the OK button.


  • Once you have selected Node in the previous screen it will now show under the “Rule Target”
  • Click the Next button.


  • We cannot leave this screen blank so enter in
  • Click on the create button.


  • Make sure you are on the Authoring Tab, have selected Rules.
  • In the Look For: button type in Node.
  • Scroll down till you find the type: Node and the name of the rule we just created.


  • Right click on the name (Step 1)
  • Click on Properties. (Step 2)


  • Step 1 -> Click the Configuration Tab.
  • Step 2 -> Click on the Edit button.


  • Double click the object identifier we created earlier and delete the information.
  • Click OK.

Discover SNMP Devices


  • Step 1 -> Click the Administration tab.
  • Step 2 -> Click on Discovery Rules.


  • Step 1 -> Right click Discovery Rules.
  • Step 2 -> Click on the Discovery Wizard option.


  • Step 1 -> Click on Network Devices.
  • Step 2 -> Click the Next button.


  • Step 1 -> Enter in a name.
  • Step 2 -> Select your management server.
  • Step 3 -> Click on the “Create Resource Pool” button.


  • Step 1a -> Enter in the Name for the New Resource Pool.
  • Optional – > give a description.
  • Step 2b -> Click Next.


  • Click the “Add” Button.


  • Step 1 -> Click the Search button.
  • Step 2 -> Click the name of your management server.
  • Step 3 -> Click the “Add” button.
  • After you have completed step 3 your management server will show under the “Selected Items” section.
  • Click OK.


  • After adding in the info it will show in the box (as shown above). Click Next.


  • Confirm the settings. Click the Create Button.


  • Once it’s complete click the “Close” button.


  • Now that we have created a new resource pool it will list under the “Available Pools” section.
  • Click Next.


  • We going to use “Recursive Directory” click the radio button.
  • Click the next button.


  • On Default Accounts page we need to create an account. Step 1 -> Click on the “Create Account” button.


  • Step 1 -> Type in a display name.
  • Step 2 -> Click Next.


  • Step 1 -> Enter in the community string.
  • Step 2 -> Click the “Create” button.


  • The account we just created will be selected.
  • Click Next.


  • On this screen click the “Add” button.


  • Enter in the name or IP address. Make your other selections.
  • Click OK.


  • The information created in the previous screen will now show under “Devices”.
  • Click Next.


  • Leave the default selected.
  • Click Next.


  • If you want to exclude any IP’s then click the “Add” button, else Click Next.


  • Make your selection.
  • Click the Next button.


  • On the summary screen confirm your settings.
  • Click the Create button.


  • When the following Warning comes up, make your selection. I click Yes.


  • Progress screen.


  • Once it finishes we can run the discovery wizard. Leave the checkbox selected and then click the close button.


  • Once you have clicked close the page above shows the progress circle.


  • As seen above we now see a status of Pending.
  • If you click on Network Devices Pending Management you will see any errors.

Hope it helps.

Setup Exchange 2013 Journaling

Brief Description:

Journaling can help your organization respond to legal, regulatory, and organizational compliance requirements by recording inbound and outbound email communications. When planning for messaging retention and compliance, it’s important to understand journaling, how it fits in your organization’s compliance policies, and how Microsoft Exchange Server 2013 helps you secure journaled messages.


  • Exchange Administrator with full access.
  • To enable journal rules, an Enterprise CAL must be purchased.
  • Port 25 needs to be open.


  • Create Journal Contact.
  • Create SMTP Connector.
  • Enable Journaling.
  • Enable Journaling Rule.

Create a Journal Contact:


  • Open up the Exchange Admin Center.
  • Type in the user that will be configuring jounaling.
  • Click Sign in.


  • Step 1 -> Click Recipients.
  • Step 2 -> Click Contacts.
  • Step 3 -> Click the + button. After that click “Mail Contact”.


  • Step 1 -> Enter a First Name for the Journaling contact.
  • Step 2 -> Enter a Last Name.
  • Step 3 -> Enter in the Alias Name.
  • Step 4 -> Enter the external email address as provided by your ISP.
  • Optionally you can add this to an organizational unit. Do so by click the Browse button and then making a selection.
  • Step 5 -> Click the Save button.


  • Once saved the new contact will show.

Create SMTP Send Connector:


  • Step 1 -> Click on mail flow.
  • Step 2 -> Click Send Connectors.
  • Step 3 -> Click the + button.


  • Step 1 -> Type in the connector name. E.G. Journal Connector.
  • Step 2 -> Click on Custom.
  • Step 3 -> Click Next.
  • On the next page add in a smart host. Make sure your authentication is set to none.
  • Click on Save.
  • Click on Next.


  • Click on the + button.
  • Once the next window comes up select the server.
  • Once completed the server will show.
  • Click the Finish button.

By default, the maximum send message size is set to 10 MB. You can change the maximum send message size to 100 MB as an example.

To change this open up the Exchange Management Shell and type in the command below:

  • Set-SendConnector “<JournalConnectorName>” -MaxMessageSize “100 MB”

Once done you can verify the change has complete by running this command:

  • Get-SendConnector “<JournalConnectorName>” |fl MaxMessageSize

Enable Journaling:


  • Step 1 -> Click on Servers.
  • Step 2 -> Click on Databases
  • Step 3 -> Double Click on the mailbox database that requires journaling activation.
    • Select Maintenance.
    • Click Browse next to the journal recipient field.
    • Select the Journaling Contact you created earlier.
    • Click Ok.
    • Click Save.
  • Perform the above steps if you have additional mailbox databases you need to activate this on.

Enable Journaling Rule:


  • Step 1 -> Click on Compliance Management.
  • Step 2 -> Click Journal Rules.
  • Step 3 -> Click the + button.


  • Step 1 -> Enter a name for the journal rule.
  • Step 2 -> Click the drop down and select “Apply to all messages”
  • Step 3 -> Here you have 3 options, All Messages, Internal Messages Only, External Messages Only. Select one of them.
  • Step 4 -> Enter in the email address that will receive the journal reports.
  • Step 5 -> Click Save.


  • As shown above the journal rule is enabled.

Hope it helps.

Import Management Pack in System Center Operations Manager (SCOM)

Brief Description:

Management packs typically contain monitoring settings for applications and services. After a management pack is imported into an Operations Manager management group, Operations Manager immediately begins monitoring objects based on default configurations and thresholds that are set by the management pack.

Steps for importing the management pack:


  • Open up System Center Operations Manager.
  • Wait for the system to initialize and connect to the DB.


  • Once initialized you will be shown this screen.
  • Click on Administration on the bottom left hand side.


  • Step 1 -> Right click on Administration.
  • Step 2 -> click on “Import Management Packs”


  • On this screen make the following selections:
    • Step 1 -> Click on the Add button.
    • Step 2 -> Click on “Add from catalog”


  • The following window will show. Don’t click anything, wait for the catalog page to show.


  • There are a couple of steps to complete here.
    • Step 1 -> Type in what you want to find, I used office.
    • Step 2 -> We searching for all management packs but if you click the drop down you can select updates.
    • Step 3 -> Click the search button.
    • Step 4 -> Once the search is complete it will show a range of items. Select the one you want, you will notice the status is showing as “Not Installed”
    • Step 5 -> Click the Add button, once you do that it adds the item you just selected to the bottom.
    • Click OK.


  • Click the install button.


  • Management Pack downloading.


  • Management Pack importing.


  • The management pack has been imported successfully.
  • Click the close button.


  • Click on Management packs and on the right hand side you will see the Management Pack we just imported.

Hope it helps.

Create a new protection group in DPM 2012 R2

Brief Description:

A protection group is a collection of data sources that share the same protection configuration. Data sources within a protection group are referred to as protection group members.

Steps to create a new protection group:



  • Double click the DPM icon to launch DPM.


  • The console will open up and show the protection groups currently running.
  • To add a new protection group click the new button.


  • We going to protect a server. Click Next.


  • Step 1 -> Expand the server you want to backup.
  • Step 2 -> Click the checkbox for the folder you want to backup. Once that is done it will show on the right hand side of the screen.
  • Click Next.


  • Step 1 -> Give your protection group a name.
  • Step 2 -> Select your option.
  • Step 3 -> Optional, you can enable online protection.
  • Click Next.


  • Step 1 -> Select your retention range.
  • Step 2 -> Select the Synchronization.
  • Step 3 -> Click on the Modify button.


  • Select the days of the week you want the backups to run, the default time is set, you can click the remove button and add in your times.
  • Click OK and it will return you to the previous screen. Click Next.


  • I have a storage pool setup so it allocates the space, however if you want to modify this then click the modify button and select your storage. Don’t forget to format the drive within DPM.
  • Click Next.


  • Select your option above. Click Next.


  • Here you can select where you want to run a consistency chick if a replica becomes inconsistent and then you can also schedule it. Once you have made your selection click Next.


  • Review the summary and then click “Create Group”.
  • Once it completes it will give you a success message. 
  • In the DPM you will now have the new protection

hope it helps.

Deploy an Application with System Center Configuration Manager R2

A System Center 2012 Configuration Manager application contains the files and information that are required to deploy software to a device. An application contains one or more deployment types that comprise the installation files and information that are required to install software. A deployment type also contains rules that specify when and how the software is deployed.

This document shows how to deploy an MSI application to users.


  • Create the application.
  • Create deployment Type.
  • Distribute Content.
  • Deploy Application.

Create the Application:

Open up SCCM.


  • Step 1 -> Click on Software Library.
  • Step 2 -> Click on Application Management.
  • Step 3 -> Click on Applications.


  • Right Click on Applications and then click on “Create Application”


  • When the screen above shows click the second radio button to manually specify the application information and then click Next.


  • Fill in the following information:
    • Name
    • Publisher
    • Owners
    • Support contacts.
  • You can select Administrative Categories.
  • Once done click Next.


  • Fill in your Keywords, you can change the Icon by clicking the Browse Button. Once finished click Next.


  • You can configure “Deployment Types” now or later, we will do this later, click Next.


  • Confirm the settings, click Next.


  • Progress status.


  • The wizard has completed. Click the Close button.

 Create Deployment Type:


  • Step 1 -> Right click on the new application we just created.
  • Step 2 -> Click on “Create Deployment Type”


  • Once the Wizard has started, click on the second radio button to manually specify the info and click Next.


  • Step 1 -> Type in the Name of the application.
  • Step 2 -> Click on the Select button to choose your language.
  • Click Next.


  • Step 1 -> Click on the browse button to location the MSI file. After this SCCM will fill in the parameters. Alternatively you can specify them.
  • If you want to provide uninstall options then click the Browse button next to “Uninstall Program”
  • Step 2 -> Click on the checkbox to “Run installation and uninstall program as 32-bit process on 64-bit clients”
  • Click Next.


  • On the above screen click on the “Add Clause Button”


  • Step 1 -> Click the dropdown and choose your selection, in this exercise I went with “Windows Installer”.
  • Step 2 -> Click on the browse button and select the MSI file. Once done click OK.


  • As shown above the Clause has been added. Click Next.


  • Step 1 -> Select the Installation Behavior.
  • Step 2 -> Select the Logon requirement.
  • Step 3 -> Select the program visibility
  • You can also change the maximum allowed run time.
  • Click Next.


  • If you have any specific installation requirements then click the “Add” button.
  • Click Next.


  • If you have any dependencies then click the “Add” button.
  • Click Next.


  • Review the information and then click Next.


  • Progress screen.


  • Once the deployment wizard finishes then click close.

Distribute Content:


  • Step 1 -> Right click the application.
  • Step 2 -> Click on “Distribute Content”


  • When the Wizard starts click the Next button.


  • Click Next.


  • Step 1 -> Click on the Add button.
  • Step 2 -> Click on Distribution Point.


  • Step 1 -> Select your server.
  • Step 2 -> Click on OK.


  • Once you have clicked “Add” and selected your Distribution point it will show above.
  • Click Next.


  • Review the information. Click Next


  • Progress.


  • Distribute content complete. Click the close button.

Deploy an Application:


  • Step 1 -> Right click the application.
  • Step 2 -> Click on deploy.


  • Step 1 -> Click on the browse button (collections) and select the target audience.
  • Step 2 -> Leave this as default or deselect it to distribute content.
  • Click Next.


  • Verify the distribution points and then click Next.


  • Step 1 -> Select the Action (Install or Uninstall). We going to install the application.
  • Step 2 -> Select the purpose (Available or required).
  • Click Next.


  • You can set a schedule or leave the default and click Next.


  • Specify the user experience settings. Click Next.


  • Here you can specify alert options. Click Next.


  • Confirm the settings, click Next.


  • Progress screen.


  • Once success completed you can click the close button.

Hope it helps.

Install & Configure Hyper-V and create a Virtual Machine.

Brief Description of Hyper-V:

Hyper-V enables you to create a virtualized server computing environment. You can use a virtualized computing environment to improve the efficiency of your computing resources by utilizing more of your hardware resources. This is possible because you use Hyper-V to create and manage virtual machines and their resources. Each virtual machine is a virtualized computer system that operates in an isolated execution environment. This allows you to run multiple operating systems simultaneously on one physical computer.


  • Install Roles.
  • Configure Hyper-V
  • Create a Virtual Machine.

Installing the Roles:

Open up Server Manager.Hyperv1

  • Once the server has initialized all its roles then click on Manage as shown above and then click on “Add Roles and Features”


  • Read through the information (if you knew to this), to continue click Next.


  • Select “Role-Based or feature-based installation” and click Next.


  • Leave the defaults and then click Next.


  • Click on the checkbox next to Hyper-V.


  • After you have selected the role Hyper-V this window will come up. Click on add Features.
  • Click Next.


  • On the Feature screen click Next.


  • You can read the note regarding the install and then click Next.


  • Make your selection and then click Next.


  • If you want to allow live migrations then click the checkbox above, otherwise accept the defaults and then click Next.


  • Specify the default location for your virtual harddisks by clicking the Browse button or accept the default locations and then click Next.


  • Click the checkbox to “Restart” the server automatically if required.


  • After you made the selection in the previous section this box will come up. Click Yes.
  • Click Install.


  • Installation started, you can close this window and then view the install from Server Manager.


  • Installation complete.
  • Restart your server.

Configuring Hyper-V:


  • You can open this shortcut either by using Server Manager or going to Control Panel -> Administrative Tools -> Hyper-V Manager.


  • This is the Hyper-V window that will open.
  • Click on Hyper-V Settings on the right hand side, the screen below will come up.


  • Here you can change all your settings. Once done click on Apply then OK.


  • Below Hyper-V settings you have Virtual Switch Manager, Click on it and you will see the screen above.
  • Here you can create your virtual switch. When done click on Apply then OK.

Create a Virtual Machine:


  • Click on New -> Virtual Machine.


  • Enter in the name of the new virtual machine, if you want to change the storage location of the VM select the checkbox and then click on browse.
  • Click Next.


  • Set the memory for the virtual machine and then click Next.


  • You can select the Virtual Switch you setup earlier or you can leave the VM “Not Connected”.
  • Click Next.


  • Here you can create a new Virtual Disk. Adjust the size and change the location to suite you otherwise select the defaults and then click Next.


  • You can install an operating system later or make the selection above, click the browse button to select a valid ISO file. If you want to install from the Hosts physical drive then choose “Physical CD\DVD drive”


  • The summary screen will show, click Finish to create the virtual machine.

Hope it helps.

Install Windows Server 2012


This document lists the steps to install Windows Server 2012.

Attach the media (if its a virtual machine) or insert the DVD into the DVD drive and then boot the Virtual/Physical Machine.

A screen will show loading. When it completes you will get the screen below.


  • Select your language, time and Keyboard method.
  • Click Next.


  • Click on the “Install Now” button to start the installation.


  • Enter in your product key and then click Next.


  • Make your select if you want a GUI or Core installation and then click Next.


  • Click on the checkbox to accept the license terms and then click Next.


  • We are going to do an Custom Installation as this is a new install on a system with no OS.


  • Select the partition you want to install on or create your custom partitions and then click Next.


  • Progress screen. Sit back and wait for the install to complete.


  • Once the setup has completed and after several reboots you will get to this screen. Enter in the local Administrator password and confirm it. Once done click Finish.


  • Once done you will get the login screen. Press any key on the keyboard for the screen to show display the screen below.


  • Type in the password you just created to login to the system.

Deploy Agents with System Center Operations Manager R2 (SCOM)


  • Open up System Center Operations Manager.
  • Wait for the system to initialize and connect to the DB.


  • Once initialized you will be shown this screen.


  • Step 1 -> Click on Administration.
  • Once the menus refresh then Step 2 -> Right click on Administration.
  • Step 3 -> Click on “Discovery Wizard”.


  • On the Discovery Type section click on Windows Computers.
  • Click Next.


  • Click on “Advanced Discovery”, if you have multiple management servers then select one from the drop down or leave the defaults and click Next.


  • Click on Browse for, or type-in computer names.
  • I typed in the machine in this example. You can also click browse to select a machine.
  • You can type in multiple computer names one below the other. Don’t forget to use the FQDN of the machine.
  • Click Next.


  • If you have an Action Account that has access to deploy the Agent then leave the default selected or enter in other credentials by click the radio button “Other user account”
  • Click on the Discover button.


  • The progress screen.


  • Once the machine has been discovered it will show in the box above (computer name removed), click on the check box to select the machine and then click Next.


  • The summary screen will show, leave it as is and click Finish.


  • A task Window will show with the status. You can leave it open or close it and then in Administrator go and click Pending Management to see if the installation failed.

Hope it helps.

Deploy Windows Updates with System Center Configuration Manager 2012 R2 (SCCM)

System Center Configuration Manager (SCCM) 2012 R2 adds a feature that enables software updates to be automatically approved and deployed to selected machines in your organization.

Icon Descriptions and Explanations:


The icon with the green arrow represents a normal software update.


Normal software updates have been synchronized and are available for software deployment.

Operational Concerns:

There are no operational concerns.



The icon with the black X represents an expired software update. You can also identify expired software updates by viewing the Expired column for the software update when it displays in the Configuration Manager console.


Expired software updates were previously deployable to client computers, but once a software update is expired, new deployments can no longer be created for the software updates. Expired software updates contained in active deployments continue to be available to clients.

Operational Concerns:

Replace expired software updates when possible. When software updates become expired, Configuration Manager does not remove the software updates contained within active software update deployments. Configuration Manager continues to assess software update compliance on expired software updates in deployments, but they are considered “not required” for reporting purposes.



The icon with the yellow star represents a superseded software update. You can also identify superseded software updates by viewing the Superseded column for the software update when it displays in the Configuration Manager console.


Superseded software updates have been replaced with newer versions of the software update. Typically, a software update that supersedes another software update does one or more of the following:

  • Enhances, improves, or adds to the fix provided by one or more previously released software updates.
  • Improves the efficiency of its software update file package, which clients install if the software update is approved for installation. For example, the superseded software update might contain files that are no longer relevant to the fix or to the operating systems now supported by the new software update, so those files are not included in the superseding software update’s file package.
  • Updates newer versions of a product, or in other words, is no longer applicable to older versions or configurations of a product. Software updates can also supersede other software updates if modifications have been made to expand language support. For example, a later revision of a product update for Microsoft Office might remove support for an older operating system, but add additional support for new languages in the initial software update release.

On the Supersedence Rules tab in the Software Update Point Component properties, you can specify how to manage superseded software updates. For more information, see theSupersedence Rules section in the Planning for Software Updates in Configuration Manager topic.

Operational Concerns:

When possible, deploy the superseding software update to client computers instead of the superseded software update. You can display a list of the software updates that supersede the software update on the Supersedence Information tab in the software update properties.



The icon with the red X represents an invalid software update.


Invalid software updates are in an active deployment, but for some reason the content (software update files) is not available. The following are scenarios in which this state can occur:

  • You successfully deploy the software update, but the software update file is removed from the deployment package and is no longer available.
  • You create a software update deployment at a site and the deployment object is successfully replicated to a child site, but the deployment package has not successfully replicated to the child site.

Operational Concerns:

When the content is missing for a software update, clients are unable to install the software update until the content becomes available on a distribution point. You can redistribute the content to distribution points by using the Redistribute action. When content is missing for a software update in a deployment created at a parent site, the software update must be replicated or redistributed to the child site. For more information about content redistribution, see the Redistribute Content on Distribution Points section in the Operations and Maintenance for Content Management in Configuration Manager topic.

Steps to download and deploy Windows updates.


  • Open SCCM and then Click on Software Library -> All software updates.


  • Select the updates you want to download and deploy. You can select multiple items by holding down the shift key or individual ones using the ctrl key.


  • You can leave the Deployment Name as is or give it your own description.
  • Click on the browse button to select the collection you want to target these updates to. Once done click the Next button.


  • Select the Type of Deployment, if you want to use Wake-on-LAN then select the checkbox.
  • Choose your detail level and then click Next.


  • Here you can configure the schedule for updates. Once you have made your selections click Next.


  • This window all you to specify deadline behaviour.
  • To suppress restarts on servers make sure the checkbox under “Device Restart Behavior” is checked.
  • Click Next.


  • Make your selection here regarding alerts and then click Next.


  • Specify your download settings and then click Next.


  • Click on the Browse button to select your deployment package and then click Next.


  • If you download updates from the internet then leave the default setting above, otherwise chose to download updates to a share.
  • Click Next.


  • Select your language and then click Next.


  • Confirm the settings, you can review the details of all updates you selected.
  • Click Next to start downloading the updates.


  • Updates download starting.


  • Updates downloads in progress.


  • Once all the updates have finished downloading it will show you the screen above. If there were any failures or errors it will also list it here for you to review.


  • It takes a few minutes for the database to update but once you refresh the screen it will show the updates have been deployed.

Hope it helps.