Configuring Permissions to RDP to Server

Microsoft Dynamics GPThis is only something I need to do occasionally so am posting this as a reminder.

Most of the demo VMs I create are on my local Client Hyper-V, but occasionally I make one available to a prospect or client and need to give them a user other than the administrator account.

Creating the user account itself is easy, but the bit I usually fail to remember how to do, is to give the user the rights to sign in remotely.

When this right has not been granted, an error message like the below will be displayed:

To sign in remotely, you need the right to sign in through Remote Desktop Services. By default, members of the Administrators group have this right. If the group you

To sign in remotely, you need the right to sign in through Remote Desktop Services. By default, members of the Administrators group have this right. If the group you're in doesn't have this right, or if the right has been removed from the Administrators group, you need to be granted this right manually.

Continue reading “Configuring Permissions to RDP to Server”

Hyper-V Error Creating Virtual Machines

Hyper-VA while ago I was having problems with Hyper-V whenever I tried to start a VM after my laptop had been to sleep or after it was first started up.

That problem went away recently after I upgraded to Windows 10 by rebuilding the laptop. However, it seems the problem has migrated to whenever I try to create a new virtual machine:

The server encountered an error while creatng

New Virtual Machine Wizard

The server encountered an error while creating {server name}.

The operation failed.

An unexpected error occurred: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

The operation failed.

The Hyper-V Virtual Machine Management server encountered an under unexpected error: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569).

This is a lot less disruptive than the originally problem as I started VMs a lot more often than I create them. And fortunately, the fix is the same as last time, so the batch file I created can still be used.

Run the batch file and the VM can be created; and even better is that I can keep the New Virtual Machine Wizard open with all of the settings configured when I run the batch file. So if I forget to run the batch file before starting to create the VM, I don’t lose any work.

Batch Command To Restart Hyper-V

Hyper-VI got a new laptop at work recently (i7 16GB RAM 1080P) and have finally been able to pretty much transition away from VMWare to Hyper-V (which I use at home for my test system); I only have a final couple of VMs to recreate or migrate. It has not all been smooth sailing however, as I have found that if the laptop goes to sleep or is switched off the VMs cannot be started again.

I think this is something to do the AD group policy rather than an inherent problem as my Surface Pro 3 works fine.

The solution is to restart the Hyper-V Virtual Machine Management service, but going into Services every time for this was soon going to get annoying, so instead I created a batch file I can run from a keyboard shortcut containing the following two lines:

net stop vmms
net start vmms

These commands stop and then start the service allowing me to use the VMs.

Physical Memory Error In VMware Workstation

Microsoft Dynamics GPWhen I joined Perfect Image they had, unfortunately, standardised on VMware Workstation for virtualisation and I have been stuck using it ever since (we have recently been transitioning to Hyper-V which I intend to start using exclusively once I can get all the VMs either converted or recreated).

I was away for a demo the other week and the night before I tried to launch the demo VM to do some final preparation when I got the following error:

GP Demo - VMware Workstation: Not enough physical memory is available to power on this virtual machine with its configured settings.

GP Demo - VMware Workstation>/p>

Not enough physical memory is available to power on this virtual machine with its configured settings.

This error message was a baffling one as I had run the VM a couple of days previously with no problems and had made no changes to the laptop in the intervening period.

The fix was a rather odd, yet simple one: launching VMware Workstation using Run as Administrator allowed the application to launch and the VM work without further problem.

Since doing this I have been able to launch the VM at any time under my usual security context.

Error Starting Virtual Machine On Client Hyper-V

Hyper-VI make a lot of use of virtual machines for both testing and demonstrating Microsoft Dynamics GP. As a company, when I joined, Perfect Image tended to use VMware (I’ll reserve comment, which I realise tells it’s own story), but more recently have started making more use of Microsoft Hyper-V, which is what I also use at home for testing and writing my blog and books.

After installing Hyper-V on my work laptop I created a virtual machine and clicked start. Unfortunately, I received the below error messages:

Hyper-V Manager

I did some digging around and found that although Hyper-V was installed, the hypervisor wasn’t running. Fortunately, the laptop I have does support Hyper-V and I only had to do one thing which was to enable the hypervisor by opening an elevated command prompt and type the following command:

bcdedit /set hypervisorlaunchtype auto

Once I had run the command I was able to start the virtual machine without further problem; at least with Hyper-V.

What I found was that with the hypervisor running, I wasn’t able to start a VMware virtual machine. So a second command can be used to disable the hypervisor for those times when I need to use a VMware virtual machine:

bcdedit /set hypervisorlaunchtype off

Hopefully, I’ll be able to complete the transition away from VMWare very soon and stop toggling from one to the other.

Remote Desktop Connection – An Authentication Error Has Occurred

this is an off topic post which I’m posting mainly as a memory prompt for myself. I was working with a set of virtual machines the other day on my test server and received the following error when I tried logging in:

Remote Desktop Connection - An authentication error has occurred. The Local Security Authority cannot be contacted. Remote computer: azc-gp2013-wc-8Remote Desktop Connection
An authentication error has occurred.
The Local Security Authority cannot be contacted
Remote computer: azc-gp2013-wc-8

I logged onto the Hyper-V server and launched the VM from Hyper-V Manager and was able to log in without issue. I did some fiddling around and realised that my Domain Controller wasn’t accepting connection requests.

One quick reboot later and I was able to log into the VM without error.

SysPrep Virtual Machine After Replication

I think I mentioned the other week that I had built a new Hyper-V server to use a as a test bed. I did run into an issue when I created the second virtual machine and tried to install SQL Server into it when it was complaining about S IDs.

I did a quick look around and realised that the problem was because I had created a virtual machine with Windows installed and made a backup of this VM which I had been copying to create subsequent machines.

The first VM I configured properly became my Domain Controller and had worked fine.

The second machine, and every subsequent ones needed to be tweaked using the System Preparation Tool before it is used.

To run the System Preparation Tool (sysprep), open the Run window and type sysprep;

Run

Continue reading “SysPrep Virtual Machine After Replication”