my personal blog about systemcenter

Updating ATA to version 1.7

Categories: Active Directory, ATA, Security
Comments Off on Updating ATA to version 1.7

Microsoft is keeping the fast pace with update to the star of their “classic” AD security solution

image

So we saw version 1.7 drop yesterday

New Major Features are

· Role based access control.

· Windows Server core support.

· Reconnaissance using Directory Services Enumeration detection.

· Pass-the-Ticket detections enhancements.

Unusual Protocol Implementation detection enhancements

Link : https://support.microsoft.com/en-us/kb/3185481

Personally we are looking fwd to RBAC its a major improvement for the majority of our customers and highly requested

image

Starting the install , we are upgrading fra 1.6.1 , we have a few enviroments on 1.4 and there is NO direct upgrade to 1.7

image

At upgrade we can either upgrade the whole database or do a partial migration , we opted for partial as having ATA offline for a longer duration wasnt a option , the database is placed on SSD so its unlikely it will take a day but we will test that in another enviroment

image

Sucess

image

New UX for updating agent and improved progress indicator

And we now have a few new security groups

image

image

image

This now means we can give auditors access to the enviroment without handing them the keys to the kingdom Smile

ATA 1.6 Update 1 , Auto Update gateways

Categories: Uncategorized
Comments Off on ATA 1.6 Update 1 , Auto Update gateways

image

https://www.microsoft.com/en-us/download/details.aspx?id=52046

Microsoft have released the first update to version 1.6 a short while ago

image

This is the first update that can use the new auto update of gateways

image

We didnt have autoupdate enabled so all gateways want a update

image

Enable and Save Smile

image

and a few seconds later the gateway agents starts to update , and 5 minutes later here all agents are updated

Very Very Smooth Smile

Deploying Data Protection Manager in a dedicated domain

Categories: Active Directory, Data Protection Manager, Disaster Recovery, DPM, Hyper-V
Comments Off on Deploying Data Protection Manager in a dedicated domain

Data Protection and the ability recover data is key to keeping your job and your company alive.

The demo setup thats is going to be used in this post are

  • PROTECTDC01 Domain Controller in the PROTECT Forest
  • PROTECTDC02 Domain Controller in the PROTECT Forest
  • PROTECTDDPM01 Data Protection Manager Server in the PROTECT Forest
  • FABRICDC01 Domain Controller in the FABRIC Forest
  • FABRICDC02 Domain Controller in the FABRIC Forest
  • FABRICHV01-04 Hyper-V HyperConverged Instal
  • FABRICHVC01 Hyper-V Cluster with member FABRICHV01-04
  • WORKLOAD01-05 Virtual Workload in the FABRIC Hyper-V Cluster

As this is a test enviroment everything are stuck on one box.

For the real world deployment the FABRIC and PROTECT domain must be seperated , the whole point in this post will be if you for some reason get compromised in your FABRIC domain , you will still have access to the PROTECT domain and maintain the ability to recover your data.

This also means that in a larger enviroment you can easier seperate the roles so one team wont have access to both source and target of backup data

We do in the example log in interative on the fabric domain , so if the host is compromised before agent install the protect domain is going down the same path , so there is still some work to be done but beats having everything in one domain.

image

On the PROTECT domain setup DNS forwarders to the FABRIC domain

image

And in Reverse to get name resolution up and running up between the two forests

image

Setting up the trust

image

Setting up the trust

image

for this test forest-wide is used , tighter security can be used with selective authentication

image

On the 4 Hyper-V Hosts we add the DPM account from the protect domain


image

We then add the DPM agent to all Hyper-V hosts and run the

SetDPMServer –dpmservername protectdpm01.protect.azurestack.coffee  , this connects the Hyper-V host to the remote DPM server

image

On the data protection manager , we use Attach Agents

image

And we add the 4 Hyper-V hosts manually

image

And we now have all 4 servers

image

use credentials in the fabric domain or the dpm account to attach the agent


image

Sucess

image

Create a protection group browse to the VM’s and add them

And we can now backup from a dedicated domain from the Fabric domain



ATA 1.6 Unable to bind to the underlying transport , unable to access console

Categories: ATA, Microsoft Advanced Threat Analytics
Comments Off on ATA 1.6 Unable to bind to the underlying transport , unable to access console

On a recent Advanced Threat Analytics 1.6 install we got

Event 15005 HTTPEVENT

Unable to bind to the underlying transport for xxx.xxx.xxx.xxx:5985. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine.  The data field contains the error number.

After reboot and was then unable to access the webconsole of the ATA Center Install

Workaround for now set World Wide Web Publishing to delayed automatic start

Storage Replica Windows Server 2016 TP5 Server to Server Replication

Categories: Datacenter, License, Storage, Storage Replica, Windows Server 2016
Comments Off on Storage Replica Windows Server 2016 TP5 Server to Server Replication

Microsoft added Storage Replica in Windows Server 2016 , and this post will cover the smallest deployment that is server to server replication

https://technet.microsoft.com/en-us/library/mt126183.aspx

image

First off is the licensing part , Storage Replica require Windows Datacenter edition

But if this is to protect a small branch office with a bunch of VM the host is most likely licensend with datacente either way

PS C:\Users\administrator.COFFEE> $Servers = ‘SR01′,’SR02’
PS C:\Users\administrator.COFFEE>
PS C:\Users\administrator.COFFEE> $Servers | ForEach { Install-WindowsFeature –ComputerName $_ –Name Storage-Replica,FS-
FileServer –IncludeManagementTools -restart }

Success Restart Needed Exit Code      Feature Result
——- ————– ———      ————–
True    Yes            SuccessRest… {File and iSCSI Services, File Server, Rem…
WARNING: You must restart this server to finish the installation process.
True    Yes            SuccessRest… {File and iSCSI Services, File Server, Rem…
WARNING: You must restart this server to finish the installation process.

Adding the WindowsFeature required to use storage replica Smile

image

Then we need to ensure we have the drives adding a data and a log drive to use with replication

After drives have been created we can then run the Test-SRTopology powershell that checks all the bits to see if everyone is configured correctly

Test-SRTopology -SourceComputerName SR01 -SourceVolumeName E: -SourceLogVolumeName F: -DestinationComputerName SR02 -DestinationVolumeName E: -DestinationLogVolumeName F: -DurationInMinutes 30 -ResultPath c:\temp

image

image

This will stress the networking but lays the foundation of how this will perform in production after being enabled

So let it sit for the default 30 mins Smile

image

20 Test Run , 1 warning

image

and lack of ICMP in firewall rule ended up with a warning for latency test not completed

Time to enable replication

New-SRPartnership -SourceComputerName SR01 -SourceRGName rg01 -SourceVolumeName e: -SourceLogVolumeName f: -DestinationComputerName SR02 -DestinationRGName rg02 -DestinationVolumeName e: -DestinationLogVolumeName f:

image

On my little test setup with 2 cores we can push 6gb/s with resonable cpu usage (not with RDMA adapters)

After initial sync is done we are now in sync

E: is available for use on server SR01 , F: is the log drive where the default 8gb is reserved

And we can reverse replication from SR02 to SR01 instead

Set-SRPartnership -NewSourceComputerName SR02 -SourceRGName rg02 -DestinationComputerName SR01 -DestinationRGName rg0

image

And we are now mounted on SR with with the active E: