Archives

KMS activation problems

I part-time manage a branch office IT infrastructure. (More formally, I am developer who has unofficially assumed the IT role.) There are other sites within the company running a common domain. Originally we were not connected  via site-to-site VPN
to other sites, so we created our own separate domain. After a number of years things have changed and we are now connected and are moving our IT infrastructure to the common domain. This has been progressing for a few months, generally fairly smoothly.

We also have two Hyper-V hosts, one running Windows Server 2008 R2 Datacenter. I set it up a number of years back and until now have not had any problems. Recently I noticed one of our VMs that I had moved from the old domain to the new domain a few weeks
back had failed to register its IP in the DNS. Checking the event log indicated KMS failures. I naively tried to re-activate it: slmgr /ipk 74YFP-3QFB3-KQT8W-PMXWJ-7M648. The screen turned black and indicated that Windows is not genuine.

I have checked several of the other VMs, but there does not seem to be any significant issues so far. Please note that the VM host is still in the original domain. Googling around I found this,
I found this indicating to check the SRV record for _vlmcs._tcp. The domain had changed, so this was pointing to the old domain. (Still available if necessary.) I updated it in the new domain DNS. I have also verified that the VM host server is available over
port 1688 via telnet.

I then ran the above slmgr /ipk again. It indicates that the key was successfully applied, but Windows still indicates that the environment is not genuine. I’d appreciate some help in resolving this.

Here is the output for slmgr /dlv on the Hyper-V VM host.

(Please let me know if this contains any keys that I should not post here and I will gladly edit it.)

—————————

Windows Script Host
—————————
Software licensing service version: 6.1.7601.17514

Name: Windows Server(R), ServerDatacenter edition

Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_C channel

Activation ID: 8fe15d04-fc66-40e6-bf34-942481e06fd8

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 55041-00168-305-513198-03-1033-7601.0000-2252011

Installation ID: 017750272912111325448091054514636704605876070861877344

Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342

Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343

Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345

Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344

Partial Product Key: K8W74

License Status: Licensed

Remaining Windows rearm count: 3

Trusted time: 4/25/2019 2:55:52 PM

Key Management Service is enabled on this machine

    Current count: 1

    Listening on Port: 1688

    DNS publishing enabled

    KMS priority: Normal

Key Management Service cumulative requests received from clients

    Total requests received: 2

    Failed requests received: 0

    Requests with License Status Unlicensed: 0

    Requests with License Status Licensed: 0

    Requests with License Status Initial grace period: 0

    Requests with License Status License expired or Hardware out of tolerance: 0

    Requests with License Status Non-genuine grace period: 0

    Requests with License Status Notification: 2

—————————
OK   
—————————

And here is the same output for the problematic VM client.

====================

—————————
Windows Script Host
—————————
Software licensing service version: 6.1.7601.17514

Name: Windows Server(R), ServerDatacenter edition

Description: Windows Operating System - Windows Server(R), VOLUME_KMSCLIENT channel

Activation ID: 7482e61b-c589-4b7f-8ecc-46d455ac3b87

Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f

Extended PID: 00496-00168-001-000128-03-1041-7601.0000-1152019

Installation ID: 007722422601855746498885195842058945462581432133218512

Partial Product Key: 7M648

License Status: Notification

Notification Reason: 0xC004F056.

Remaining Windows rearm count: 3

Trusted time: 2019/04/25 14:58:42

Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

—————————
OK   
—————————

Read full post . . . .

Expanding a fixed VHDX file – Is data preserved?

I want to expand a fixed .VHDX.  It’s currently 2 TB and I want to make it 3 TB.  I would edit the VHDX with the Edit Wizard in the Settings for the VHDX.  Will the data remain safe?  Could anyone approximate how long it will take?

Read full post . . . .

HyperV VirtualSwitch – Adaptername

HyperV server 2016 Core

I changed the names of the networkcards  (4x onboard)

When i checked it with 

Get-NetAdapter ill see everything correct

Name: Port1
InterfaceDescription:AD-Server

Now i like to create a virtualswitch in HyperV manager 
Ill choose an ExternalSwitch , and theni have to choose the network adaptor
There ill see :
Intel Gigabit Network Controller
Intel Gigabit Network Controller #1
Intel Gigabit Network Controller #2

and not the names ill see on the server with powershell
In the windows admin center - devicemanagement - networkcard , ill see also the correct names, 
there is no place to find that "intel" name on the server… 

what do i have to change to see the correct names in the virtualswitch creator?

Henri

Read full post . . . .

Hyper-V on Windows 10 (1903) – how to set default configuration version?

Hyper-V on Windows 10 (1903) - how to set default configuration version?

I have upgraded my Windows 10 from 1809 to 1903.

I have several VMs running under Hyper-V with configuration version 9.0.

Using the command Get-VMHostSupportedVersion I receive the following output: 

Name                                                      Version IsDefault
—-                                                      ——- ———
Microsoft Windows 8.1/Server 2012 R2                      5.0     False
Microsoft Windows 10 1507/Server 2016 Technical Preview 3 6.2     False
Microsoft Windows 10 1511/Server 2016 Technical Preview 4 7.0     False
Microsoft Windows Server 2016 Technical Preview 5         7.1     False
Microsoft Windows 10 Anniversary Update/Server 2016       8.0     False
Microsoft Windows 10 Creators Update                      8.1     False
Microsoft Windows 10 Fall Creators Update/Server 1709     8.2     False
Microsoft Windows 10 April 2018 Update/Server 1803        8.3     False
Microsoft Windows 10 October 2018 Update/Server 2019      9.0     True
Microsoft Windows 10 April 2019 Update/Server 1903        9.1     False

So there is a new 9.1 configuration available, but it’s not set as default. How can I change to 9.1 as default?

I am also unable to upgrade my existing VMs from 9.0 to 9.1, using Update-VMVersion .

Windows tells me that I am already on the maximum supported version for my VM, so why is there a 9.1 config if it is not available for an upgrade?

Please help!

Read full post . . . .

Difference between deployed rd license server and rd license server in deployment properties?

In a very simple windows 2012 r2 RDS server there are two setting which seem almost the same. If someone could explain the difference that would be helpful.

Both are accessible from the RDS Overview panel.

#1 is found in the Deployment Overview panel where there is a RD Licensing icon. If one adds a RD License Server via that icon, the server will appear in the adjacent Deployment Servers list.

#2 is exposed via Tasks list when you choose Edit Deployment Properties. The four deployment properties that are exposed there include an entry for RD Licensing, which allows you to again specify the FQDN for a RD License Server and to choose between licensing
per device or per user.

Read full post . . . .

having trouble trying to connect a vm server and a vm win10 for learning purposes.

Hello

novice here,so bare with me as I’m not fluent yet in all the technical therms and aspects.

i recently started learning for a mcsa certificate,

in class we use vmware; i make a windows10vm and a server2012 VM,

i assign the server an ip from the range i see in the subnet address(VMware-virtual network editor)

i set up ADDS,DHCP,DNS on the server and in "edit/virtual network editor"",i put both the sever and the win10  on a VMnet-nat and use local DHCP to distribute ip addresses.(i think it was nat,maybe local host?)

i try to do the same with hyper-v but having issues,i guess i didn’t fully understand how those switches work.

i added an internal switch and put both the machines on it, but when using ipconfig, i see i get different range of ips for both the server and win10 and i wasn’t able to have the server distribute an ip to the win10vm nor connect to its local domain with
it.

i get these kind of ips:169.254…  saw it was apipa - not sure what that means.

I’d appreciate the help.

Read full post . . . .

New KB articles published for the week ending 20th April,2019

VMware Horizon Remote Desktop connection with NLA is not supported in Horizon View Date Published: 16-Apr-19 VMware NSX for vSphere Can’t assign new user role in NSX Manager Date Published: 18-Apr-19 NSX Controller Certificate flagged on Security/Audit Scan flagged as bad certificate Date Published: 15-Apr-19 Mellanox Onyx, NSX Hardware VXLAN Gateway, version 3.7.1200, NSX 6.4.4

The post New KB articles published for the week ending 20th April,2019 appeared first on VMware Support Insider.

Continue reading..

Hyper-c role is not installed on the destination host.

Hi,

I am trying to use the following command but it failed with error message:

Measure-Command { New-VHD -Path E:TestVHD-50GB.vhdx -Size 50GB -Fixed}

Error message:

PS C:UsersAdministrator> Measure-Command { New-VHD -Path C:ClusterStorageVolume11.vhdx  -Size 50GB -Fixed}
New-VHD : The Hyper-V role is not installed on the destination host. Add the Hyper-V role on that host and then run this cmdlet again.
At line:1 char:19
+ Measure-Command { New-VHD -Path C:ClusterStorageVolume11.vhdx  -Size 50GB -Fi …
+                   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [New-VHD], VirtualizationOperationFailedException
    + FullyQualifiedErrorId : Microsoft.Vhd.PowerShell.NewVhdCommand

Thanks 

Read full post . . . .

New KB articles published for the week ending 13th April,2019

Read full post . . . or http://feedproxy.google.com/~r/VmwareKnowledgebaseBlog/~3/m_m7uw5Qeto/new-kb-articles-published-for-the-week-ending-13th-april2019.html

Virtual Disk Development Kit Best practice for Linux proxy VM configuration in HotAdd transport Date Published : 10-Apr-19 VMware ESXi ESXi host may crash with a PSOD - Spin count exceeded - possible deadlock with PCPU Date Published: 11-Apr-19 VVOLs are inaccessible after moving to another vCenter Server or refreshing CA certificate Date Published: 9-Apr-19

The post New KB articles published for the week ending 13th April,2019 appeared first on VMware Support Insider.

Microsoft Admin Center and Hyper-V Server 2012 R2

Hello,

Microsoft Admin Center states it supports Hyper-V Server 2012 R2 and I must upgrade to Powershell 5.0+.

Hyper-V Server 2012 R2 ships w/ 4.0 and fails to upgrade to 5.0 or above.

It state the OS is not supported.

Any ideas? I can’t find anything about this searching online for the past 2 hours…

Thank you!

Read full post . . . .

Go Que Newsroom

Categories