Server 2012 “Automatic Maintenance” Killed our SAN

We have had performance issues for a few weeks at night, all our Hyper-V Servers where performing like CRAP every night around 3 AM and for about 45 minutes.

After a long night of investigation with my colleague, we found out that Windows 2012 is running a maintenance job around 03:00 each day.

The Automatic Maintenance window in the Action Center
The Automatic Maintenance window in the Action Center

When we stopped it all began to run as normal. This caused overloading of the SAN SP and gave high disk queue on all servers attached to the SAN.

But, after we disabled the Scheduled Task “Regular Maintenance“, it got enabled Again after some hours.

To avoy this disable “Maintenance Configurator“, but this can´t be done from GUI

To disable Maintenance Configurator run this command on a server with PsExec Link :

psexec \\SERVERNAME -s schtasks /change /tn "\Microsoft\Windows\TaskScheduler\Maintenance Configurator" /DISABLE
Maintenance is now disabled.
Maintenance is now disabled.
VN:F [1.9.22_1171]
Rating: 5.9/6 (7 votes cast)

Monitor Citrix Licenses In Use With Powershell

# Setup Variables
$Total = 0
$InUse = 0
$StrHost = "Localhost" 

# Get Citrix licensing Info
$licensePool = gwmi -class "Citrix_GT_License_Pool" -Namespace "Root\CitrixLicensing" -comp $StrHost

$LicensePool | ForEach-Object{ If ($_.PLD -eq "MPS_ADV_CCU"){
    $Total = $Total + $_.Count
    $InUse = $InUse + $_.InUseCount
    }
}

$PercentUsed = [Math]::Round($inuse/$total*100,0)
$Free = [Math]::Round($Total-$Inuse)

echo "Total: ",$Total
echo "In Use: ",$InUse
echo "Free: ",$Free
echo "Percent Used: ", $PercentUsed
VN:F [1.9.22_1171]
Rating: 6.0/6 (3 votes cast)

SYSVOL share is not replicating between RODCs and Writable Controllers

Event id 2843 in Directory Service is logged

“The Knowledge Consistency Checker was unable to locate a replication connection for the read-only local directory service.  A replication connection with the following option must exist in the forest for correct FRS system behavior.

 

Additional Data

Option:

64

User Action

Restore the original replication connection for the local directory service instance on a writable directory service instance. “

 

1. On a writable DC, please run adsiedit.msc after logon as Enterprise administrator.
2. then in adsiedit.msc, please establish a new connection:

1). For Connection Point, please “Select a well known Naming context”: Configuration
2). for Computer, please input the Name of the writable DC.
3). then click OK to connect.
4). once connect, please expand:

CN=Configuration,DC=DC Name,DC=Domain Name,DC=com,
\CN=Sites
\CN=Site Name
\CN=Servers
\CN=RODC Name

\CN=NTDS Settings
5). then in the right pane, right click and open the properties of “CN=Name of Full DC”.
6). in the properties dialog, please set Filter to check on:

Mandatory
Optional

Constructed
Backlinks
System-Only

7). then in the list, find Options
8). edit it and set the data to: 0x41
9). Save and apply
10). switch to Security tab, click Advanced, click Add, click “object types”, select computers, click OK, input the RODC name, click Check Name, click OK.

In the Permission for RODC Name dialog box, click Properties tab, locate Read fromServer, Write fromServer, Read schedule, Write schedule and give RODC permission to this four permissions. Click OK to save.
11). monitor to check whether the new gpo can be replicated to RODC.

VN:F [1.9.22_1171]
Rating: 6.0/6 (4 votes cast)

WSUS 3.0 SP2 Hotfix to provide updates to Windows 8 and Windows Server 2012

This update lets servers that are running Windows Server Update Services (WSUS) 3.0 SP2 provide updates to computers that are running Windows 8 or Windows Server 2012

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

VN:F [1.9.22_1171]
Rating: 0.0/6 (0 votes cast)

Unable to create the CAU clustered role because a Network Name resource could not be created

Recently i got this error when trying to enable Cluster Aware Updating in Server 2012, i got this error:

“Unable to create the CAU clustered role because a Network Name resource could not be created. This can occur if a computer account (virtual computer object) for the role could not be created in the domain. Check the event log for more information. If the cluster name account does not have permissions to create the object, you can pre-stage a computer account in Active Directory. Then, use the Add-CauClusterRole Windows PowerShell cmdlet with the VirtualComputerObjectName parameter to create the CAU clustered role. For more information about pre-staging computer accounts, see http://go.microsoft.com/fwlink/p/?LinkId=237624.”

Unable to create the CAU clustered role because a Network Name resource could not be created
Unable to create the CAU clustered role because a Network Name resource could not be created

to fix this open Active Directory Users and Computers, go to view and select Advanced Features. Navigate to the OU where your Cluster object will be created and right-click on the OU and choose properties., go to the Security tab. Add your Hyper-V cluster computer object, then choose Advanced. From there select your Hyper-V cluster object and choose Edit. Navigate down to “Create Computer objects” and choose check the check box.

Click Apply and Ok, then try enabling CAU again!

Note: By default the new CAU object will be created where the cluster object is.

VN:F [1.9.22_1171]
Rating: 6.0/6 (9 votes cast)