Tech Encounters

Manage Windows Server 2008 SP2 and R2 from Windows Server 2012 Server Manager By KeithMayer 2 Oct 2012 12:10 PM Server Manager in Windows Server 2012 has been redesigned as a new cool multi-server management console, making it as easy to manage multiple servers remotely as you can from a local server's console - whether those servers are physical, virtual or hosted in the cloud!  Not familiar with the new Server Manager yet?  Check out this post over at My Thoughts On IT, the blog of my fellow IT Evangelist Brian Lewis and an all-around great guy! :-) Well, it seems it's a little known fact that Server Manager in Windows Server 2012 can manage not only Windows Server 2012 and Hyper-V Server 2012 servers, but also servers running Windows Server 2008 SP2 and Windows Server 2008 R2 SP1 as well!  However, it's a bit of a trick to get it all working ... If you don't follow these steps on these older servers, you'll likely end up with the following status message in ...

Source  Aug. 6, 2012John Savill | Windows IT Pro Hyper-V Replica works by replicating write operations that are stored in transaction log files every five minutes to the replica server.  An expand or compact action on a virtual hard disk (VHD) isn't a write operation and therefore doesn't replicate and will break the replication of the VHD.  The only solution is to stop replication, then restart replication.  In most organizations, compacting and expanding WHDs isn't a common operation, especially if dynamic VHDs are used; however, it's important to understand that if using Hyper-V Replica for a VM, any compact or expand operations will break the replication. Below are some steps to "ease the pain": If Recovery History is off , which means when setting up Hyper-V Replica you did not enable the option to keep additional point in time replica snapshots, do the following: 1.On the same VHD on recovery, do same operation to get the identical geome...

Access to drivers on Windows Update was blocked by policy EventID:122 errors appearing on Windows Server 2012 Hyper-V host.  “Device Setup Manager” service. There is a scheduled task that runs each night in “Microsoft | Windows | Device Setup” called “Metadata Refresh”.  When that task runs it causes the “Device Setup Manager” service to start, and that’s what is causing the messages.  If you look in the Event Viewer under “Application and Services Logs | Microsoft | Windows | DeviceSetupManager | Admin” and filter on Event ID 122 then you can see the entries. The “policy” that is causing the block is actually the Device Installation Settings.  SOLUTION Use the search in the Control Panel window and look for “device installation” When that window opens, you will see the settings that define the “policy” If you change the setting to “Always install the best driver software from Windows Update.” then the Even...

Hyper-V is not in a state to accept replication on the replica server for virtual machine   Message appears at the end of the replication Wizard. A replica for this virtual machine had previously existed on the Replica server. Cause The previous successful or unsuccessful replicated virtual machine may be still exist at the replica server.   Solution Remove the old virtual machine at the  replica server and enable replication again.  Yes this pushes a fresh replication to the replica server. Additional notes Under the details of the error message on the source server a Virtual machine ID is listed, and using this ID to find the replication files from the previous replication on the Replica server (under \Virtual Hard Disks\Hyper-V Replica\Virtual hard disks\<ID>\ and under \Virtual Hard Disks\Hyper-V Replica\Virtual Machines\<ID>. These files may be locked while a previous replica exists on the Replica server

Virtual Machine failed to start worker process: Incorrect function. (0x80070001) Configuration Hyper-v Server 2012 with 4 VMs. One VM running the others would not start. Error message popup when starting VM. Further in the event logs "The authorization store could not be initialized from storage location". Cause An earlier test restore had replaced the key entry with a now redundant location. Solution Edit registry key as below [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization] Problem Key shows an invalid location: "StoreLocation"="msxml://D:\\Restore Test\\Host Component\\C_\\ProgramData\\Microsoft\\Windows\\Hyper-V\\InitialStore.xml" Change key to correct location: "StoreLocation"="msxml://C:\\ProgramData\\Microsoft\\Windows\\Hyper-V\\InitialStore.xml" Then restart Virtual Machine Service from Hyper-V console

Zoom the private cloud computing platform from New Zealand expands storage and CPU capacity to meet growing demand. www.itco.co.nz/zoom.html