Windows 10: DHCP Failover Issue - Automation

Hi eveyrone,I'm deploying a script to automate creating new DHCP scopes in a DHCP Failover Cluster. The idea is apply the below commands: DHCPScopeCommand=f"Add-DhcpServerv4Scope -Name '{entry[5]}' -StartRange {entry[2]} -EndRange {entry[3]} -SubnetMask {entry[1]} -LeaseDuration 1.00:00:00" DHCPOptionsCommand=f"Set-DhcpServerv4OptionValue -ComputerName '{dictServerIPs[SERVERIP]}' -ScopeId '{entry[0]}' -DnsServer {PRIMARYDNS},{SECONDARYDNS} -DnsDomain 'user.ngahr.int' -Router {entry[4]}"which work fine, however I'm facing some issues with the following one: DHCPFailoverCommand =

:)

 

Issues with report server setup during Install of MBAM using a SQL failover cluster

I'm trying to setup MBAM 2.5SP1 on Server 2016 using a SQL 2016 on a Failover Cluster (but not using AO).

The initial database configuration went smooth, but setting up the next step (Reports) is causing an issue because it cannot find the instance of the report server.

"Unable to find an instance of the Reporting Services.

That said, I realize that the report server is not supported with the failover cluster, but is there a way to point the Report feature to another SQL server or a server that has the reporting services (ie: one of the Failover cluster nodes) instead of auto-detecting
the SQL failover cluster name/IP?

I'm trying to avoid having a SQL server just for MBAM if I can avoid it (for cost and manageability reasons).

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.

 

Windows 10 RSAT - Failover Cluster Manager

I installed the remote server admin tools yesterday to my Win10 enterprise which made me very happy at first. DNS, DHCP, ADUC all worked great. Then I opened failover cluster manager. Problems began.

We have dozens of MS clusters running 2003 and up, mostly 2008R2 or 2012R2. When I try and manage them I get

Connection Not Supported

Cluster XXXXXXX not supported

The cluster to which you are attempting to connect is not a version of the cluster supported by this version of Failover Cluster Manager

This is happening with all the clusters I need to manage. Is this a bug or "working as designed"?