Questions[windows-server-2012-r2](server)

I have a Windows Server 2012 R2 running SharePoint 2013 which I am trying to migrate from Hyper-V to KVM (qemu). I have converted the vhdx file to qcow2 format and copied it across to the KVM server (RHEL 7.3)

The Hyper-V VM was configured as Generation 2 and I have create a new VM in KVM with a UEFI firmware (OVMF).

When I boot up the machine goes in to Automatic Repair mode but will not boot. I can open the Cmd Prompt and to do so I need to authenticate with the local Administrator password.

I have run the following:

1. Type BOOTREC /FIXMBR, and then press ENTER.
2. Type BOOTREC /FIXBOOT, and then press ENTER.
3. Type Drive:\boot\Bootsect.exe /NT60 All, and then press ENTER.

However the VM is unable to boot always enters Repair mode.

Any suggestions on what I might need to check or any 3rd party utilities I might be able to use or buy to help me easily get past this ?

If I login to command prompt I can run Diskpart / sel disk 0 / list vol to see :

Volume 0    D          CDROM          0 B   No Media
Volume 1    C NTFS     Partition    126GB   Healthy
Volume 2    E Recovery Partition    300MB   Healthy   Hidden
Volume 3               Partition     99MB   Healthy   Hidden

VM on KVM was configured as:

*Emulator:/usr/libexec/qemu-kvm *Firmware:UEFI x86_64: */usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd *CPUs 8 *Memory 8192MB *IDE DISK- Disk Bus IDE *Storage format qcow2

What I have done so far:

1. Opened Hyper-V and Exported the VM to a new directory on Windows
2. Use Hyper-V Inspect Disk to merge the difference avhdx and vhdx disks into one vhdx
3. Used StarWind v2v Converter to create a qcow2 file
4. Copied the qcows file to KVM machine
5. Create new VM of same spec:

6. When starting the new machine I see this:

I have a Windows Server 2012 R2 Domain.

Yesterday, a computer’s (running Windows 10 Pro) network drive stopped working.

After further investigation (gpresult /h) it appears ALL group policy objects are failing with the reason Inaccessible, Empty, or Disabled.

I have confirmed that all the GPOs still exist and are enabled on both (redundant and local) domain controllers. Furthermore, there are 20 other machines on the same domain and LAN with absolutely no problems.

However, there is one other computer that I tested which presented with the same problem! Does that mean the problem is with the servers?

gpresult /r reports that one client is getting GPOs from local DC1, and the other from DC2. So it is not a problem related to a specific DC.

gpupdate /force fixed nothing (though it claimed that policies were applied).

I tried deleting the registry entries for local policies (following this guide https://superuser.com/questions/379908/how-to-clear-or-remove-domain-applied-group-policy-settings-after-leaving-the-do) and rebooting - same problem.

I found this support page from Microsoft (https://support.microsoft.com/en-us/kb/2976965), but it claims it only applies to Windows 7 or earlier clients.

All my machines (both server and client) are running 64-bit versions and are fully updated. I have rebooted all of them just to be sure.

How can I view, who is currently connected to a server (Windows 2012) with a remote desktop client? I am myself connected to this server via RDP.

This question offers a solution to get IP addresses with established connections. I would be interested in a list of users or their sessions and when these sessions were active the last time.

I'm trying to RDP into one of my servers, which as Network Level Authentication Enabled as well as NTLMv2 being forced. This worked fine until the server had to reboot for updates. Now, I cannot RDP into my server anymore. I get this error trying to connect via RDP:

An authentication error has occurred - The function requested is not supported

This translates to: An authentication error has occurred. The function requested is not supported

I tried several things I found by googling, for example adding extra SecurityPackages values to the registry as described here: http://funeasytech.com/rdp-connection-error-of-the-requested-security-package-does-not-exist/ but that didn't work. Neither did changing the Group Policy on the client solve my issue, as described here: https://stackoverflow.com/questions/17371311/the-function-requested-is-not-supported-exception-when-using-smtpclient-in-azu

The problem is that I don't have physical access to this box, only via RDP. The server is running Windows Server 2012 R2 Standard, the client is running Windows 10 Pro.

How can I regain access to my server?

1:

I installed a fresh Windows Server 2012 R2 Standard with GUI instance on a VMware VM. The first time I logged in as Administrator, I noticed an Internet Explorer window automatically opened to http://go.microsoft.com/fwlink/p/?LinkId=255141 and redirected to http://www.msn.com/?ocid=wispr. This seems to be the default Internet Explorer Start Page.

This has continued - every time I log in as Administrator or any other user, this page opens.

Later I installed Firefox, and now Firefox opens to this same page on login (which is the default Internet Explorer Start Page, not the Firefox homepage!).

I've checked the Programs Menu Startup folders for Administrator and all users, and used Sysinternals Autoruns to look for something, all to no avail. There doesn't seem to be anything that should be launching IE on logon.

This was a default install of Windows Server with GUI on a network with very limited (whitelisted) outbound Internet access. In fact, msn.com isn't on the whitelist so I never see the page, only the message from my firewall that it's blocked.

I cloned this VM to a couple of other VMs and they exhibit the same behaviour.

The only hits I can find for this sort of problem involve spyware on desktop machines or shortcuts in the Startup folder. It's a mystery to me.

I've even gone through the registry and removed all four references to LinkId=255141:

• HKLM\Software\Microsoft\Internet Explorer\Main: Start Page and Default_Page_URL (changed both to about:blank)
• HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\Main: Start Page and Default_Page_URL (changed both to about:blank)