SCCM 2012 R2 – Deploying Microsoft Office 2013 Professional Plus

In this post I will give detailed instructions on how to deploy Microsoft Office 2013 Professional Plus

While I have done this with SCCM 2012 R2 in this guide the process is identical for SCCM 2012, 2012 SP1 and Microsoft Office 2010 Professional Plus

  1. Navigate to the location of the install media and open a CMD windowSCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 01
  2. Type “setup.exe /admin” and press EnterSCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 02
  3. When the product selection screen appears, select the product you wish to install (there will usually only be one)SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 03
  4. Navigate to “Install location and organization name”
  5. Type in your organization name (This step is not required)SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 05
  6. Navigate to “Licensing and User Interface”
  7. At my location I have a KMS server running which services all my clients for me. If you do not have this you can enter you MAK key here
  8. Click “I accept the terms in the License Agreement”
  9. Change “Display level” to “None”
  10. Ensure “Complete notice” remains unchecked and check “Suppress modal” and “No cancel”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 06
  11. Navigate to “Modify user settings”
  12. In the left of the two panes, navigate to “Microsoft Office 2013\Privacy\Trust Center”
  13. In the right pane double click on “Disable Opt-in Wizard on first run”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 07
  14. Select “Enabled” and click “OK”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 08
  15. Confirm that the status is now set to enabledSCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 09
  16. Navigate to “Set feature installation states”
  17. In the right pane, click on “Microsoft Office” at the top of the tree and select “Run all from My Computer” from the drop-down menuSCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 10
  18. One this is done save the MSP file. I have chosen to create a folder in the source media folder and call it “AdminFiles” and then the file name as Full.MSP, so that i can create individual installs for Excel, Word, etc. you can set any name, but it is much easier later if you don’t include spaces in the nameSCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 11
  19. Within the SCCM console, navigate to “Software Library”, “Application Management”.
  20. Right click on “Applications” or a folder that you have created under this and click “Create Application”.SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 12
  21. Select “Manually specify the application information” then click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 13
  22. Fill the the appropriate fields with the information you wish to provide, then click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 14
  23. Fill the the appropriate fields with the information you wish to provide. If you wish to have a custom icon for the Application Catalog choose it here, then click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 15
  24. When you reach the “Deployment Types” field, click “Add”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 16
  25. Within the wizard that opens up, select “Manually specify the deployment type information”. Then click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 17
  26. In the “Name” field, type “Microsoft Office 2013 Professional Plus 32-Bit” as this is a 32-Bit deploymentSCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 18
  27. Enter the content location of the source media (extracted folder obviously)
  28. In the “Installation program” field, type “Setup.exe /AdminFile AdminFiles\Full.MSP” (Or whatever you called your MSP file)
  29. In the “Uninstall program” field, type “Setup.exe /Uninstall PROPLUS”
  30. Tick “Run installation and uninstall program as 32-bit process on 64-bit clients” and click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 19
  31. Click “Add Clause”
  32. Change “Setting Type” to “Windows Installer”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 20
  33. In the “Product code” field, click “Browse”
  34. Navigate to the source media, then proplus.ww. Select “proplusww.msi” and click “Open”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 21
  35. Select “This MSI product code must exit on the target system and the following condition must be met to indicate the presence of  this application”. Then click “OK”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 22
  36. Review information and click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 23
  37. Change “Installation behavior” to “Install for system”
  38. Change “Logon requirements” to “Whether or not a user is logged on”
  39. Change “Installation program visibility” to “Hidden”
  40. Change “Estimated installation time (minutes)” to “20”, then click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 24
  41. If you would like to set requirements for the installation, such as minimum system requirements or primary device you can do so here, otherwise click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 25
  42. If you would like to set a dependency for this installation such as .Net you can do so here, otherwise click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 26
  43. Review all details here then click “Next”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 27
  44. Click “Close”SCCM 2012 R2 - Deploying Microsoft Office 2013 Professional Plus - 28
  45. Once you have completed all the above steps you can then deploy this package to your collections and test installation (preferable to a small test group such as yourself first)

SCOM 2012 R2 – Monitor a Windows Service

In this post I will give detailed instructions on how to monitor a Windows service through SCOM 2012 R2.

For this example I will be creating a monitor to monitor a service called ‘LP360 License Server’ which only occurs on a single server

  1. Within the SCOM console, Navigate to the ‘Authoring’ tab, expand ‘Management Pack Objects’ and select ‘Monitors’SCOM - Authoring Monitors
  2. Right click on ‘Monitors’, expand ‘Create a Monitor’ and select ‘Unit Monitor…’SCOM - Authoring Monitors - Create Unit Monitor
  3. Expand ‘Windows Services’ and select ‘Basic Service Monitor’SCOM - Create Unit Monitor - Monitor Type
  4. From the drop-down menu, select the management pack that you wish to place this monitor into. For custom monitors I create a management pack which i have called ‘Service Monitoring’. Then click ‘Next’
  5. Give your monitor a name that is unique and specific to what you are monitoring, I called mine ‘LP360 License Server’SCOM - Create Unit Monitor - General
  6. Select a monitor target. if this service is specific to an operating system such as Server 2008 R2, then search for and select ‘Windows Server 2008 R2 Computer’ of the Discovery management pack. Otherwise select ‘Windows Computer’ to cover all Windows server and clients. Then click ‘Next’
  7. Select a ‘Parent monitor’ from the drop-down box. for custom monitors I create an Aggregate Rollup Monitor which is called ‘Custom Services’. If you have not got a custom one, select ‘Availability’, it can always be changed later
  8. Because this service is only on one server, I do not want the monitor enabled by default. Untick ‘Montor is enabled’, then click ‘Next’
  9. If you are confident of the service name then type it in the box. I strongly suggest clicking on the ‘…’ buttonSCOM - Create Unit Monitor - Service Details
  10. Click ‘…’, type the server name and click ‘OK’SCOM - Create Unit Monitor - Select Windows Service - Select Computer
  11. Locate the service you wish to monitor and click ‘OK’. When you use this method there can be no doubt as to the service nameSCOM - Create Unit Monitor - Select Windows Service
  12. Click ‘Next’
  13. The default health states are fine for monitoring services, so unless you have specific requirements for something different, click ‘Next’SCOM - Create Unit Monitor - Configure Health
  14. I turn on alerts for all service monitors, select ‘Generate alerts for this monitorSCOM - Create Unit Monitor - Configure Alerts
  15. Change the ‘Alert description’ to something that makes sense for you, mine is ‘The ‘LP360 Server’ Service has stopped.”
  16. Click ‘Create’
  17. Search ‘Monitors’ for your monitor, locate it under ‘Windows Computer’. Right click, expand ‘Overrides’, then ‘Override the Monitor’. Select ‘For a specific object of class: Windows Computer’SCOM - Create Unit Monitor - Search - Override
  18. Search for the server that is running the service, select the server and click ‘OK’SCOM - Create Unit Monitor - Override - Select Object
  19. Tick the ‘Override’ box the corresponds to the ‘Enabled’ parameter, then change the ‘Override Value’ to ‘True’. Click ‘OK’SCOM - Create Unit Monitor - Override - Enable
  20. Navigate to the ‘Monitoring’ tab, then select ‘Windows Computers’SCOM - Search for server - Right Click - Open
  21. Search for the server you just created the override for. Right click on the server, expand ‘Open’, select ‘Health Explorer’ for your server
  22. Navigate to where you placed the monitor, in my case it was ‘Custom Services’. Depending on your setup, you may have to clear the filter, it will be a yellow bar at the top of the left paneSCOM - Health Explorer - LP360
  23. Click on State Change Events to confirm when the monitor became active. It could take up to an hour for the monitor to become active. This is dependent on the amount of clients you are monitoring and the performance of your SCOM infrastructure

SCSM 2012 R2 – Authoring Tools prerequisites check fails

Symptoms

When attempting to install the “Service Manager 2012 R2 Authoring Tools”, the prerequisites check fails on the “Microsoft Visual Studio Shell 2008 Check”Server Manager 2012 R2 Authoring Tools Prerequisites check fails

Troubleshooting

Verify that you have installed Visual Studio Shell 2008 from the Microsoft site

http://go.microsoft.com/fwlink/?LinkId=310149

Resolution

  1. Open the folder where the installation contents are locatedServer Manager 2012 R2 Authoring Tools location
  2. Browse to <InstallMedia>\Setup\enServer Manager 2012 R2 Authoring Tools Prerequisites XML file location
  3. Open Authoring_PrerequisiteInputFile.xmlServer Manager 2012 R2 Authoring Tools Prerequisites XML file contents
  4. Find the line <Check Order=”3″>Server Manager 2012 R2 Authoring Tools Prerequisites XML file contents1
  5. Remove this line from the XML document
  6. Find the next instance of </Check>Server Manager 2012 R2 Authoring Tools Prerequisites XML file contents2
  7. Remove this line from the XML document (The contents between these two points could also be removed, but this method makes it easier to undo the changes)
  8. Save the XML, overwriting the existing file
  9. Run Setup.exe again to verify that the process has worked, it should no longer check for Visual Studio 2008 ShellServer Manager 2012 R2 Authoring Tools Prerequisites check passed

SCOM 2012 SP1 – Agent Not Monitored

Symptoms

After installing/attaching agents the state is displayed as “Not monitored”

Image

Note: The agent will likely appear this way after first installing/attaching. wait 24 hours for it to auto-configure and only assume failure if it is still showing the same status after this

Resolution

  1. Connect to server that is displayed as “Not monitored”
  2. Open the run box and type “Services.msc”Run - services.msc
  3. Locate service named “System Center Management”Services - System Center Management
  4. Right click and stop serviceServices - Right click menu
  5. Browse to C:\Program Files\System Center Operations Manager\Agent
  6. Change folder name to “Health Service State Old”SCOM - Health Service State folder
  7. Start service and make sure that a new folder is createdSCOM - Health Service State folder new
  8. Wait 5 minutes and refresh SCOM console to ensure that agent is now monitoredSCOM - Agent monitored

DPM 2012 SP1 – Suspect Tape

Symptoms

  • Tapes will be listed as “Suspect”
  • DPM will not be able to write to these tapes

Troubleshooting

One of the first indication that this was not a legitimate error was that i was seeing this on 7 brand new tapes

Another giveaway was that they were labeled this way after a Fast Inventory, which means that they have never entered the drive to be read or written on

DPM Tape Suspect

Resolution 1

Change the label on the tape.

For me, everything in the 50 range was being marked as suspect. e.g. 450-459, 550-559.

This is not a very good fix but will allow the tapes to be written on should you be hesitant to try anything else

Resolution 2

Open the DPM Shell and enter the following

osql -E -S localhost\MSDPM2012 -d DPMDB -Q “UPDATE tbl_MM_ArchiveMedia SET IsSuspect = 0”

This command will modify the SQL table and change all tapes to non-suspect

DPM Mark all tapes as not suspect

WARNING: if you have any tapes that are legitimately suspect this will also change them so use with caution

Resolution 3

This method will allow you to individually mark tapes as not suspect, but can be quite time consuming

Open Microsoft SQL Server Management Studio

Navigate to Server Instance > Databases > DPMDB > Tables

SQL DPM Tables

Right click on dbo.tbl_MM_ArchiveMedia and click “Edit Top 200 Rows”. should you have more than 200 tapes you can easily expand the amount of rows in the right pane under “Top Specification”, change it to No

SQL Right Click Table

To Identify which tape is which, run a query on the database (DPMDB) and match MediaID to the edit tab

select [BarcodeValue], [MediaID]
FROM [DPMDB].[dbo].[tbl_MM_Media]

Once the correct row is identified change the column marked “IsSuspect” to 0

Note: i am working on a PowerShell script that will make this process easier, but time has been tight and this will be a good starting point for most people

DPM 2012 SP1 – Attempting to cancel

Symptoms

  • Job displays “Attempting to cancel for an extended period of time”

Troubleshooting

The jobs that i experienced this issue with refused to budge, even after a full system restart. However, Time Elapsed continues counting up on some of them

DPM Attempting to cancel

Resolution

  1. Ensure that there are no other jobs currently running
  2. Open SQL Management Studio and connect to your DPM SQL instance
  3. Right click on the instance and click “New Query”
  4. Copy and paste the following query into the Window——————————————————————————-
    USE DPMDBBEGIN TRANUPDATE tbl_PRM_LogicalREplica

    SET Validity = 1

    WHERE OwnerTaskIdLock IS NOT NULL AND

    Validity <> 5 AND

    Validity <> 6

    UPDATE tbl_PRM_LogicalREplica

    SET OwnerTaskIdLock = null,

    Status=8

    if (select COUNT(name) from tbl_AM_Agent where Name like ‘DPM RA v2%’) > 0

    begin

    exec sp_executesql N’UPDATE tbl_RM_ShadowCopy

    SET ArchivetaskId = NULL,

    RecoveryJobId = NULL’

    end

    UPDATE tbl_ARM_Datasource

    SET Status = 0,

    OwnerLockId = NULL

    DELETE tbl_RM_DatasourceServerlock

    DELETE tbl_RM_ShadowCopyLocks

    UPDATE tbl_TE_TaskTrail

    SET ExecutionState = 3,

    LastStateName = ‘Failure’,

    StoppedDateTime = GetUtcDate()

    WHERE ExecutionState NOT IN (2,3)

    UPDATE tbl_JM_JobTrail

    SET JobState= ‘Failed’,

    EndDateTime = GetUtcDate()

    WHERE jobstate= ‘Execute’ OR jobstate= ‘Retire’

    UPDATE tbl_MM_Global_Media

    SET ReservationLevel = 0,

    ReservationOwnerMMId = null

    UPDATE tbl_MM_Global_Drive

    SET ReservationLevel = 0,

    ReservationOwnerMMId = null

    UPDATE tbl_MM_Global_IEPortResource

    SET ReservationLevel = 0,

    ReservationOwnerMMId = null

    COMMIT TRAN
    ——————————————————————————-

  5. Execute Query
  6. Open DPM console
  7. Find all volumes that were affected (they will most likely say “Recovery Point Creation Failed”)
  8. Right click on volume and select “Create Recovery Point”
  9. Select “Create a recovery point by using express full backup”

DPM 2012 SP1 – Replica is inconsistent

Symptoms

  • Protection group member displays “Replica is Inconsistent”

Troubleshooting

There is a large number of reasons you could be seeing this error, the two main areas to focus on are making sure that the backup feature is installed and the event viewer logs on the target server

Event Viewer Backups

Resolution 1

  1. Right click on the member and click “Perform consistency check…”

DPM Replica is Inconsistent

Resolution 2 (Server 2012 and 2008 R2)

  1. Connect to target server
  2. Open PowerShell window
  3. Type “import-module servermanager”PowerShell import-module servermanager
  4. Type “get-windowsfeature”. this will display a list of the Windows Services and Features that are currently installed
  5. Locate the Windows Server Backup line and ensure that it is ticked, if not continue with this resolutionPowerShell Windows Server Backup
  6. (Server 2012) Type “add-windowsfeature windows-server-backup”
  7. (Server 2008 R2) Type “add-windowsfeature backup”
  8. Right click on the member in the DPM console and click “Perform consistency check…”

Resolution 3 (Server 2008)

  1. Open Server Manager
  2. Click Add Features
  3. Locate Windows Server Backup Features and expand
  4. Select Windows Server Backup and click next, then finish the wizardServer 2008 Install Windows Server Backup
  5. Right click on the member in the DPM console and click “Perform consistency check…”

Resolution 4 (Server 2003)

  1. Install the Server 2003 VSS update http://support.microsoft.com/kb/940349
  2. Right click on the member in the DPM console and click “Perform consistency check…”

Resolution 4

  1. Verify that the volume that you are attempting to backup has enough HDD space, general rule is to have the volume (when OS volume) at 50% capacity but this can vary depending on your individual requirements

Resolution 5

  1.  Open CMD as administrator
  2. Type “wbadmin -destination <dest>” where <dest> is the location that you wish to backup everything to, e.g. D:\Backup (WARNING: this will use up a large amount of space)
  3. Right click on the member in the DPM console and click “Perform consistency check…”

DPM 2012 SP1 – Manually copy large volume to secondary DPM server

At our site our file server is quite large and is required to be backed up offsite via DPM replication

As the volume is around 4TB and we have a 10mb/s link this would have taken a large amount of time

The solution is to copy the volume to removable media and then relocate it to the secondary DPM server

Instructions

  1. Configure the protection on the secondary site as you would normally but select “manual” when asked if you want to start the synchronization now
  2. On the primary DPM server locate the volume you wish to have replicated and at the bottom of the screen click “Replica Path”. you cant expand the window but if you double click on the end of the column (instead of clicking and dragging) you can expand the column to its full size

DPM Replica Path

  1. Open the command prompt and type “mountvol” and locate the replica path, then mark and copy the line above it

mountvol marked

  1. Type “mountvol” followed by an unused drive letter and the paste the previous contents (e.g. mountvol T:\ \\?\Volume{4bae1ccb-e2eb-11e2-93ee-00155d032025}\)

mountvol paste

  1. Open your newly mounted volume and see if you are able to access all folders, if need to change the owner, I suggest to the local administrator
  2. Copy contents of mounted volume to your removable media
  3. Relocate removable media to secondary site
  4. Repeat steps 1-5 on secondary DPM server
  5. Paste contents of removable media into mounted volume
  6. Run a consistency check on the server

Dell TL2000 Status – Media Attention

This week i decided to tackle and issue with our tape library that has been there for several months now and Dell was unable to give me any feedback as to what might be causing it

Image

Up until this point i was very reluctant to touch anything as the library is not completely reliable (despite this being our second unit)

So after a fair amount of poking around the web gui i was able to work out what was showing this annoying warning

In our library i have two cleaning tapes, but had the number of active slots set to 23.

After changing this number the number to 21 the error went away and the library status is now green

Image

I did notice that this caused DPM to be unable to see the cleaning tapes and thus you cant initiate a drive clean from within the DPM console. This is an inconvenience but not a large issue because i have left the “Auto Clean Enabled” box ticked which should keep the drive clean

DPM 2012 SP1 – Unable to configure protection for SQL database

Symptoms

  • When protection of an SQL server in DPM is configured, DPM shows critical error “Unable to configure protection”

DPM Unable to configure protection

Resolution

  1. Open SQL Management Studio on database server
  2. Navigate to Security > Logins
  3. Right click on NT AUTHORITY\SYSTEM and click properties
  4. Under Server Roles, check the sysadmin box and click ok
  5. In DPM, right click on each critical job and select run Configure protection job again