June 26th, 2014
During TechEd NA 2014 , Microsoft announced bunch of new features that are supported by windows Azure , some of these new features are (VM Security Extensions, ExpressRoute GA, Reserved IPs, Internal Load Balancing, Multi Site-to-Site VPNs, Storage Import/Export GA, New SMB File Service, API Management, Hybrid Connection Service, Redis Cache, Remote Apps).
one of my favorite feature is VM Security Extensions.
VM Security Extensions: These extensions offer a richer security protection to the VMs hosted in Azure using industry security products. Currently there are new three extensions for Microsoft Antimalware , Symantec Endpoint Protection and TrendMicro’s Deep Security Agent.
To enable any one the above extensions, login to Azure Management Portal and check the extension when you create new a new Virtual Machine:
but wait you can enable these extensions from Power shell , the following cmdlets are available
April 27th, 2014
I have been waiting for months to write this blog about how to protect AlwaysOn with DPM , the reason for the delay that DPM 2012 R2 before RU2 wasn’t supporting AlwaysOn with Cluster.
for Enterprises looking for true disaster Recovery and avoid single point of failure, AlwaysOn can be setup using SQL Cluster Instance with a stand alone SQL server Instance.meaning the primary replica is hosted on a SQL Cluster instance and Secondary replica is hosted on SQL Instance Standalone. the reason for that is to avoid the single point of failure such as the SAN
As I mentioned earlier , before DPM rollup Update 2 for System center , DPM didn’t support Protecting AlwaysOn with Cluster Setup.
First step: Install DPM Client to your WFC nodes , make sure to patch your DPM server with the latest RU2
Second Step: Create a Protection Group to protect databases on Clustered AlwaysOn .
April 19th, 2014
When you install DPM 2010, right after the prerequisites verification you receive an error “Verify that Windows Management Instrumentation (WMI) Service is running. if…
in order to fix this issue, you need to reinstall WMI , this is how to do it
From an elevated Command Prompt
1. Disable and stop the WMI service.
sc config winmgmt start= disabled
net stop winmgmt
2. Rename the Repository folder under C:\Windows\System32\wbem to Repository.old
3. Run the following commands.
Winmgmt /salvagerepository %windir%\System32\wbem
4. Re-enable the WMI service and then reboot the server to see how it goes.
sc config winmgmt start= auto
April 17th, 2014
Don’t be surprise , DPM 2012 R2 doesn’t support Windows server 2003 , the rollup update is coming shortly and it will fix the issue.
I know if Shreesh said that it will happen
April 17th, 2014
This question came from Momo my DBA Friend, I have SCOM 2012 installed , what kind if maintenance Plan I need to run, Momo meant DBCC check, Index rebuild etc..
my answer nothing , you don’t need to run any maintain on SCOM DBs and the reasons are the following :
1- there is a rule name “Optimize Indexes” that execute a daily database maintenance it calls a Store Proc name “p_OptimizeIndexes” , by default the rule runs once a day at 2:30 AM , you can change the time (Configuration Tab,View DS ),
the index optimization Store Proc has the following
April 17th, 2014
There is always something new , in the System Center area, there is a new SQL Server Analysis Services released early January 2014
it supports the following :
1- SCOM 2012 and later
2- Virtualized SSAS instances
3- Clustered SSAS instances
Download the MP
From Microsoft web site :
System Center Management Pack for SQL Server 2008 Analysis Services
System Center Management Pack for SQL Server 2012 Analysis Services
1- SSAS Instance monitoring
2- SSAS Database monitoring
3- SSAS Partition monitoring
Health Rolls Up :
a well detailed article please visit Oleg’s Blog