Since Ignite 2017 Security & Compliance offering is now part of Azure Service Center service. Because of that some of the controls of that offering are moved to ASC but still the integration is not complete at least to me. With this blog post I will focus on two of the ASC settings that you should set up when you start with ASC – Changing to another Log Analytics workspace and Security Events level (filtering). Continue reading “Tips and Tricks of Setting up Azure Security Center”
The last issue I’ve stumbled upon with System Center is with VMM component.
- You have SCVMM 2012 SP1 UR2 installed
- You have Windows Server 2012 Hyper-V for hosts
- You use SMB 3.0 share for storing virtual machines
- Some or all of your virtual machines does not use FQDN path to their vhd/x files
- You’ve added your File Server in VMM by FQDN or NetBIOS Name
- You receive the following error: Error (13924) The highly available virtual machine (VMNAME) is not supported by VMM because the virtual machine uses non-clustered storage.
- Some or all of your virtual machines show as Unsupported Cluster Configuration
I’ve managed to resolve this issue by executing the following steps:
1. Make sure you’ve added your file server in VMM by FQDN. If it is not added by FQDN you have to add it.
2. Create new share. You can create it on the same server. Give the share appropriate permissions.
3. Locate the new share in VMM. Add it as storage location to your hosts/clusters.
4. After is added make sure it show green in the properties of the hosts/clusters.
5. Storage migrate all your virtual machines from the old share to new share. For the machines with status Unsupported Cluster Configuration you can change the status to Running by live migrating them trough the Failover Cluster console.
6. After storage migration of each virtual machine refresh it and make sure in the properties of the machine in Status tab all is green.
7. After successful migration of all virtual machines you can remove the old share from the hosts/clusters and delete it from the File Server.
I’ve also may had problems with the permissions on the old share but it is easier to create new share than fixing permissions on existing share with running virtual machines.
The information is provided ‘AS IS’ with no warranties and confers no rights. Keep in mind that your case may be similar and this solution may not work for you.
Software I’ve used:
- Windows Server 2012 with latest updates
- SCVMM 2012 SP1 UR2
- File Server with SMB share
In order to start building Cloud you have to have resources. Such resources are storage, network and compute power (servers). Let’s say you have those but the servers are nothing without operating system. The operating system connects these resources together. To get the OS on a server you have to install and configure it. But if you start to install and configure OS on every server manually it will be resource intensive and could lead to inconsistency in the configuration of your servers. Of course there is solution for this problem and it is called automatic deployment. Microsoft offers such solution and it is free – Microsoft Deployment Toolkit. MDT offers full automation in deploying Windows but it can be integrated with System Center Configuration Manager to increase its powers in automatic OS deployment.
In the video below offered by Microsoft you will see Session 1 from Deployment day on Tech Days 2012 conference in Belgium. Presenter is Rhonda Layfield which is Sr. Deployment Architect. Video is Level 200 according to me and will show you the basics around MDT and what is new in 2012 version. Click on the link below and watch.