Altaro have put out a blog on 12 of the common Hyper-V deployment mistakes that people make. I think I have done a few of these before!
- Mis-Provisioning Resources in Hyper-V
- Improper Balance of CPU and Memory
- Improper Balance of Networked Storage and Network Connectivity
- Improper Balance of SSD and Spinning Disks
- Improper Balance of Networking Resources
- Improper Focus of Resources
- Creating Too Many Networks and/or Virtual Adapters
- Creating Too Many Virtual Switches
- Optimizing Page Files
- Not Leveraging Dynamic Memory
- Leaving Default VM Configurations
- Not Troubleshooting the Right Thing
- Overloading the Management Operating System
- Leaving the Management OS in Workgroup Mode When there is a Perfectly Good AD Domain Available
- Not Testing
- Avoiding PowerShell
- Not Figuring Out Licensing in Advance
Read the entire article here – http://www.altaro.com/hyper-v/common-hyper-v-deployment-mistakes/
Yes, that is not a typo. Microsoft is offering unlimited storage on OneDrive for Office 365 subscribers.
This news was released via their blog here – https://blog.onedrive.com/office-365-onedrive-unlimited-storage/
“Today, storage limits just became a thing of the past with Office 365. Moving forward, all Office 365 customers will get unlimited OneDrive storage at no additional cost. We’ve started rolling this out today to Office 365 Home, Personal, and University customers. “
What about OneDrive for Business? That will be coming in 2015! – http://office.microsoft.com/en-us/products/office-365-roadmap-FX104343353.aspx
“We are announcing the removal of current limits on external users for all SharePoint Online plans. Specifically, the changes will be as follows. The external users limit for Office 365 Small Business and Small Business Premium will change from 500 to Unlimited. The external users limit for Office 365 Midsize Business and Office 365 Enterprise plans (including E1 – E4, A2-A4, G1-G4, and SharePoint Online Plan 1 and Plan 2) will change from 10,000 to Unlimited.“
Microsoft has just released version 3 of their Virtual Machine Converter (MVMC). This is a standalone tool that will covert virtual machines, hosts and physical machines to Hyper-V.
The new features of MVMC 3.0 include:
- Converts virtual disks that are attached to a VMware virtual machine to virtual hard disks (VHDs) that can be uploaded to Microsoft Azure.
- Provides native Windows PowerShell capability that enables scripting and integration into IT automation workflows.
- Note The command-line interface (CLI) in MVMC 1.0 has been replaced by Windows PowerShell in MVMC 2.0.
- Supports conversion and provisioning of Linux-based guest operating systems from VMware hosts to Hyper-V hosts.
- Supports conversion of offline virtual machines.
- Supports the new virtual hard disk format (VHDX) when converting and provisioning in Hyper-V in Windows Server® 2012 R2 and Windows Server 2012.
- Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.1, and VMware vSphere 4.1 hosts Hyper-V virtual machines.
- Supports Windows Server® 2012 R2, Windows Server® 2012, and Windows® 8 as guest operating systems that you can select for conversion.
- Converts and deploys virtual machines from VMware hosts to Hyper-V hosts on any of the following operating systems:
-Windows Server® 2012 R2
-Windows Server® 2012
-Windows Server 2008 R2 SP1
- Converts VMware virtual machines, virtual disks, and configurations for memory, virtual processor, and other virtual computing resources from the source to Hyper-V.
- Adds virtual network interface cards (NICs) to the converted virtual machine on Hyper-V.
- Supports conversion of virtual machines from VMware vSphere 5.5, VMware vSphere 5.0, and VMware vSphere 4.1 hosts to Hyper-V.
- Has a wizard-driven GUI, which simplifies performing virtual machine conversions.
- Uninstalls VMware Tools before online conversion (online only) to provide a clean way to migrate VMware-based virtual machines to Hyper-V.
- Important MVMC takes a snapshot of the virtual machine that you are converting before you uninstall VMware Tools, and then shuts down the source machine to preserve state during conversion. The virtual machine is restored to its previous state after the source disks that are attached to the virtual machine are successfully copied to the machine where the conversion process is run. At that point, the source machine in VMware can be turned on, if required.
- Important MVMC does not uninstall VMware Tools in an offline conversion. Instead, it disables VMware services, drivers, and programs only for Windows Server guest operating systems. For file conversions with Linux guest operating systems, VMware Tools are not disabled or uninstalled. We highly recommend that you manually uninstall VMware Tools when you convert an offline virtual machine.
- Supports Windows Server and Linux guest operating system conversion. For more details, see the section “Supported Configurations for Virtual Machine Conversion” in this guide.
- Includes Windows PowerShell capability for offline conversions of VMware-based virtual hard disks (VMDK) to a Hyper-V–based virtual hard disk file format (.vhd file).
You can download the tool here – http://www.microsoft.com/en-us/download/details.aspx?id=42497
The video is well worth watching.
The bottom line is that if you have a third party flashlight app, you should remove it immediately … especially if you have an Android based phone (Samsung etc).
Here is the full report – http://www.snoopwall.com/threat-reports-10-01-2014/
Microsoft Azure have announced the general availability of Azure Site Recovery services. The announcement by Abhishek Hemrajani is as follows.
“I am excited to announce the GA of the Disaster Recovery to Azure using Azure Site Recovery. In addition to enabling replication to and recovery in Microsoft Azure, ASR enables automated protection of VMs, remote health monitoring, no-impact recovery plan testing, and single click orchestrated recovery – all backed by an enterprise-grade SLA.
The DR to Azure functionality in ASR builds on top of System Center Virtual Machine Manager, Windows Server Hyper-V Replica, and Microsoft Azure to ensure that our customers can leverage existing IT investments while still helping them optimize precious CAPEX and OPEX spent in building and managing secondary datacenter sites.
The GA release also brings significant additions to the already expansive list of ASR’s DR to Azure features:
- NEW ASR Recovery Plans and Azure Automation integrate to offer robust and simplified one-click orchestration of your DR plans
- NEW Track Initial Replication Progress as virtual machine data gets replicated to a customer-owned and managed geo-redundant Azure Storage account. This new feature is also available when configuring DR between on-premises private clouds across enterprise sites
- NEW Simplified Setup and Registration streamlines the DR setup by removing the complexity of generating certificates and integrity keys needed to register your on-premises System Center Virtual Machine Manager server with your Site Recovery vault”
The following scenarios are supported.
Costing can be found here – http://azure.microsoft.com/en-us/pricing/details/site-recovery/
You can read more from the blog post here – http://azure.microsoft.com/blog/2014/10/02/disaster-recovery-to-azure-using-azure-site-recovery-is-now-ga/
If you want to have a play with the various new preview releases of Windows, here are the links to resources and information on where to download these previews.
If you have a MSDN or Microsoft Azure subscription, you can get them directly via the respective site portals.
Otherwise, here are the public links.
Here are a couple of useful resources for working with Subnets.
I came across a useful site that helps you build up an SPD record using a form that asks various questions.
Here is a list of where you can find important log files for Windows Server 2012 Essentials and Windows Server 2012 R2 Essentials.
In Windows Server Essentials 2012 and 2012 R2, the location of the log files is under %programdata%\Microsoft\Windows Server\Logs.
Service Integration Log Files:
|Windows Azure Backup
Backup Log Files:
|Server Backup Configuration wizard
|Server Backup restore wizard
|Client Backup Feature server side log
|Client backup database cleanup
|Client backup database checker
Storage and Devices Log Files:
|User/Device management feature
|Storage related feature
Azure Backup Log Files:
|Location: C:\Program Files\Windows Azure Backup Agent\Temp
|Azure Backup Logs
|Failed Azure Backup Logs
Other Helpful Log Files:
|Health evaluation schedule task
|Macintosh Clients Status update
|Server DNS status
|Customer Experience Improvement
Program and Service Quality Measurement Log Files:
|CA Role installation
|Media pack installation (2012 R2)
|Media Service (Specially with RWA)
|O365 (Assign/Un-assign Accounts)
The client-side log files are located in the folder %programdata%\Microsoft\Windows Server\logs. They are as:
|Client package installation Failures
|Client backup restore mount driver
|Client operation for File history Sync
|Main log for client launch pad
|Password synchronization feature in AAD
|Add-in feature on client
|Health evaluation schedule task
|Client Backup scheduled task
|Connector uninstall cleanup task
|Update health definition file from server to client task
|RDP feature for RWA
||RunTask-RDP Group Configuration.log
|Client VPN connectivity issues
||RunTask-VPN Routes Repair.log
|Client network status update
|Client deployment API call (Client deployment fails)
|Health alert feature
Reference – http://blogs.technet.com/b/sbs/archive/2014/09/30/windows-server-essentials-log-files.aspx
Oh, and by the way, check your NAS devices to ensure that they are safe. Disconnect direct Internet access right now, until the devices are patched.
QNAP says that they are vulnerable to this, and urge users to take immediate action. http://www.qnap.com/useng/index.php?lang=en-us&sn=885&c=3036&sc=&n=22457
Apparently, Synology units are not generally affected (interesting…), but nevertheless, they are also coming out with a patch (also interesting…) https://www.synology.com/en-global/support/security/bash_shellshock