SCOM 2012 – Reset Reporting Services

1. Uninstall the SCOM reporting component.

2. Copy the following two files from installation media \SupportTools\AMD64 to SQL reporting server.

• ResetSRS.exe

3. Open an elevated command prompt and locate to the path where the two files above stored.

4. run ResetSRS.exe <reporting instance name> and use the account which has permission to reset the SQL reporting instance.

for example:

ResetSRS.exe MSSQLSERVER (default instance)

or

ResetSRS.exe Instancename (named instance)

5. After the reset, please logon to the reportserver URL for SCOM instance.

• http://localhost/reportserver (default instance)

• http://localhost/reportserver_instancename (named instance)

6. If you see a blank page without error, then you can reinstall SCOM reporting.

7. After the installation, please access the reportserver URL again which won’t return any errors.

WSUS Installation Fails with No Specified Error and ‘Tools’ Folder is Missing

Symptoms
===========

·         When installing WSUS through the Add Roles and Features Wizard (ARW), the Post-Installation task fails and the generated log folder (*.tmp) is empty, AND

·         The Tools folder is missing after WSUS was installed. Note: By default, the Tools folder is installed to the following location: %SystemDrive%\Program Files\Update Services\Tools

This behavior has been seen when:

·         Uninstalling WSUS

·         Manually deleting WSUS folder: %SystemDrive%\Program Files\Update Services

·         Manually deleting WSUS registry keys: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services

·         Re-installing WSUS

Root Cause
===========

When uninstalling WSUS Role via ARW the “API and PowerShell cmdlets” feature is not uninstalled by default (unless explicitly selected by the user). Deleting the remaining WSUS folders and registry keys leaves the server in a bad state and the re-installation fails because it is expecting this feature to be already installed.

Workaround
============

Uninstall all the WSUS roles and features and re-install WSUS.

Workaround 1: To uninstall WSUS roles and features using Windows PowerShell

1.    In PowerShell, review features installed by calling: Get-WindowsFeature UpdateServices*

2.    To remove features, call: Uninstall-WindowsFeature <featureName>

Workaround 2: To uninstall WSUS roles and features using the Server Manager Console

In Server Manager, launch Remove Roles and Features Wizard (RRW), unselect items to be uninstalled, and complete the Wizard:

1.    In Server Roles tab unselect ‘Windows Server Update Services’ option

2.    In Features tab unselect ‘Remote Server Administration Tools -> Role Administration Tools -> Windows Server Update Services Tools’ option

Request Count data is missing from APM reports after upgrade to Operations Manager 2012 R2

After you upgrade from SCOM 2012 SP1 to SCOM 2012 R2, request counts are no longer available in Application Performance Monitoring (APM) reports. This occurs because the APM performance counter names for ".Net Apps" were changed to just "Apps" in the Operations Manager database, however there were no corresponding name updates in the Operations Manager Data Warehouse.

Please see the following:

Request Count data is missing from APM reports after upgrade to Operations Manager 2012 R2

http://support.microsoft.com/kb/2984838

Sender ID Framework SPF Record Wizard - Microsoft

Configure DNS Sender ID

Use the Sender ID Framework SPF Record Wizard to verify or configure a sender policy framework (SPF) record for your DNS domain. The SPF record is used by the Sender ID Framework to identify an e-mail sender and to help increase the detection of deceptive e-mail.

For more information about the Sender ID Framework, see the Microsoft Web site

To configure an SPF record for your domain

1. Browse to the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=114211). This starts the Sender ID Framework SPF Record Wizard.
2. Follow the steps of the wizard to create a new SPF record for your domain.
   If you have already configured an SPF record, you can use the wizard to verify the configuration.

After you configure an SPF record, you will need to add the text file to your domain's DNS zone file configuration. You may need to contact your Internet service provider for assistance with this task. 

Hyper-v,Linux Integration Services issue

Edit the file /etc/initramfs-tools/modules
and add the line allow us to load the rest of the required modules:
hv_vmbus
hv_storvsc
hv_blkvsc
hv_netvsc
hv_utils

Save the file and run the command:
$ Sudo update-initramfs-u

Put this in /etc/network/interfaces your new synthetic network interface seth0.
If you have used an outdated network interface Legacy, it would be called eth0.
For a static address:
Auto seth0
iface seth0 inet static
address xxxx
netmask xxxx
Gateway xxxx
To get the address for DHCP:
Auto seth0
iface seth0 inet dhcp
I tested both methods of network addressing, they work.
Reboot and see now in the process of such reports that the device associated with vmbus found.

Hyper-V Virtual Machine cannot be displayed or showed as “saved-critical” in Hyper-V Manager.

Problem
========
Hyper-V Virtual Machine cannot be displayed or showed as “saved-critical” in Hyper-V Manager.

Solution
========
1. Delete the DC virtual machine manually as it cannot be shutdown/start from hyper-v manager;
2. Create two virtual machine with original VHD disk for DC and Exchange VM;
3. Boot up the DC and Exchange VM, configure the network adapter with correct IP settings.
4. Verify the exchange service and we can receive/send email normally.