Month: July 2019

Situation: The client is running Windows 2016 Hyper-v and moves the VM to different drive. Now, they can’t start the VM.

Troubleshooting: 1. They should not us copy and past to move the VM. They should use export.

2. Hyper-V virtual machine may not start, and you receive a “‘General access denied error’ (0x80070005)” error message Every Hyper-V virtual machines has a unique Virtual Machine ID (SID). If the Virtual Machine SID is missing from the security permissions on the .vhd or .avhd file, the virtual machine does not start, and you receive the “‘General access denied error’ (0x80070005)” error message that is mentioned in the “Symptoms” section. Please refer to this article:

Google Custom Search Hyper–V virtual machine may not start, and you receive a “’General …support.microsoft.comhttps://support.microsoft.com/…/hyper–v–virtual-machine-may-not-start-and- you-receive-a-general-access

3. There are two ways to fix the problem. The easy (but completely insecure) fix is to give Everyone full control of the virtual hard disk file. The “correct” fix it to give read and write access to the virtual machine’s SID.

You can find the virtual machine’s SID by using the Get-VM cmdlet in PowerShell. For a VM named New Virtual Machine the command would be:

Get-VM 'New Virtual Machine' | Select-Object VMID

4. Update the Permissions

The solution is to give the SID Full control of the VHD using the command line.

Tip: Rather than type (or mistype) the SID by hand, cut and paste it from the event log message or from the XML file name in the Virtual Machines folder.

The command:

icacls <Path of .vhd file> /grant "NT VIRTUAL MACHINE\<Virtual Machine SID>":F

Note that there is no space before the :F. For example:

icacls "D:\Virtual Machines\VM01\Virtual Hard Disks\DRIVE01.VHD" /grant "NT VIRTUAL MACHINE\6B78D45F5-71DF-4725-B4B2-E651800BE80EF":F

Once that permission has been added, you should be able to start the virtual machine.

5. Updating the NTFS level permissions: 1.  On the destination server, Right-click on the shared folder and select Properties. 
2.  Select the Security tab. 
3.  Click Edit button and click the Add button in the permissions dialog box. 
4.  Click Oject Types and select Computers if not already done and click OK
5.  In the dialog “Enter the object names to select” provide the name of Hyper-V host machine and click Check Names
6.  With the Hyper-V host machine name select, click Allow by “Full control” and click OK

Updating the share level permissions:1.  On the destination server, Right-click on the shared folder and select Properties. 
2.  Select the Sharing tab. 
3.  Click Advanced Sharing…
4.  On the Advanced Sharing dialog, click Permissions  and then Add. 5. Click Oject Types and select Computers if not already done and click OK
6.  In the dialog “Enter the object names to select” provide the name of Hyper-V host machine and click Check Names
7.  With the Hyper-V host machine name select, click Allow by “Full control” and click OK

Situation: one of outside client cant login remote Desktop server with this error: Your credentials did not work. Your system administrator doesn’t allow the use of saved the credentials to log on to the remote Computer.

Troubleshooting: 1. Use other computer with the same username doesn’t have this problem.

2. We fixes it by do this:

“The reason why it wasn’t working was because Windows automatically stored the certificate in a “non-trusted” root store. Once it was moved RDP connected without prompting for credentials”

Other suggestions: 1. Change the group policy setting.

2. Security settings.

3. If the client is located the same LAN, change the network profile from public to private.

4. Make sure the company firewall allow remote session.

5. Edit Windows Security Policy.

6. Delete the credentials:

Go to Control Panel -> Credential Manager. You will see three sections:

1. Windows Credentials
2. Certificate-Based Credentials
3. Generic Credentials

Remove the credentials from Windows Credentials and add it to Generic Credentials.

Situation: When the user prints a excel sheet, it misses some characters. It works frint from other computer prints to the same printer.

Troubleshooting: 1. Upgrade the printer driver.

2. Restart the printer and computer.

Situation: The client has Hyper-V server running Windows 2016. They can’t login server remotely or from the console. But all VMs run fine and they can access those VMs without any problems.

Troubleshooting: We use another server’s Computer Management and Service to connect to the Host server, every thing is fine except the Event ID: 51
Description:
An error was detected on device \Device\Harddisk1\DR23 during a paging operation.

We find they has external USB connect to the server. Unplugging the external USB and restart the host, everything works.

Situation: The client setup a FTP site in their Windows 2012 R2. When they try to access the FTP site, and enter their credentials, they can’t access the FTP with timeout message.

Troubleshooting: 1. If we turn Windows Firewall off, it works.

2. The Windows Firewall already has FTP inbound and outbound configured.

3. We fix the problem by adding port 20 in windows firewall.

Situation: The client setup a FTP site on their Windows 2012 R2 server. They can’t access FTP with this message: Make sure you have permission to access that folder. The hadle is invalid.

Details
200 Type set to A
227 Entering Passive Mode (10,0,1,17,149,179)

Troubleshooting: This could be the FTP Firewall Support issue. Go to IIS Manger>Server name, double click on FTP Firewall Support.

Change the Data channel Port Range to 0-0 and remove the External IP addresses of Firewall in it is used for internal only.

Situation: The client setup a FTP site on their Windows 2012 R2 server. They can’t access FTP using Internet Explorer, Microsoft Edge, and FileZilla and WinSCP. However, they can access FTP using Chrome browser. This is the error message: An error occurred opening that folder on the FTP Server. Make sure you have permission to access that folder. The hadle is invalid.

Troubleshooting: This could be the FTP Firewall Support issue. Go to IIS Manger>Server name, double click on FTP Firewall Support.

Change the Data channel Port Range to 0-0 and remove the External IP addresses of Firewall in it is used for internal only.

Situation: The user use Plantronics Bluetooth earphone connecting to his Android phone. Sometimes it works, but other it doesn’t work.

Troubleshooting: We find whenever he plug Plantronics Bluetooth into a computer, then the Bluetooth doesn’t work on the phone. Resolution is unplug the Bluetooth USB from the computer.

Here are some cases we have been working on FTP connection problem.

1. The certificate expired.

2. Make sure you connect to correct FTP site. In this case, the client open the port 21 on Default website. Disable the default website or remove the port 21 from the default website fixes the problem.

3. In other case, The client assign port 21 to ftps site. Refer to above screenshot.

4. Make sure you configure correct authentication and authorization. Also make sure you enter correct username and password. In one of case, the client needs to enter domainname/user to access the FTP site.

Situation: When running Installutil to install a program as windows service, the client receives this message:

An exception occurred during the Install phase.
System.ComponentModel.Win32Exception: The account name is invalid or does not exist, or the password is invalid for the account name specified

Troubleshooting: You need to use correct login format, for example domain name\admin and correct password.