jott19

New-VM with vhdx drives from Exported App server

I want to deploy the same VM build (App server with IIS, LOB app, database) repeatedly to multiple customer H-V hosts with each VM having a different BiosIDs so the OS (Server 2019) can be licensed/activated.

Proposed solution:

Export a "gold" build, create a New-VM with the same settings, then attach vhdx drives from the Export.

As far as I know, this is the only way to get a different BiosID (sysprep wreaks havoc with the build).

The LOB app in question licenses independently from the BiosID, but other utilities on the server may not.  Aside from that caveat, are there any pitfalls in cloning a VM like this?

Read full post . . . .

How to relocate VM config files in Server 2016?

I’m trying to consolidate a number of vhdx files with their corresponding VM config files into a folder named after the VM (regardless of the vhdx or config file names).

Will I need to Export/Import the VM in order to accomplish this task?

Our "standard" directory structure scheme has been violated a number of times now and we need to reduce the potential for confusion/mistakes.

Can these new binary files in 2016 be moved? Can their parent directories be renamed?

I can obtain info about the VM like this:

((Compare-VM -Copy -Path 'H:VM.vmcx' -GenerateNewID).VM) | Select *

But I’m not sure how this helps me correlate the .vmcx or .vmrs files with the .vhdx or assist in the task at hand.

Read full post . . . .

How to relocate VM config files in Server 2016?

I’m trying to consolidate a number of vhdx files with their corresponding VM config files into a folder named after the VM (regardless of the vhdx or config file names).

Will I need to Export/Import the VM in order to accomplish this task?

Our "standard" directory structure scheme has been violated a number of times now and we need to reduce the potential for confusion/mistakes.

Can these new binary files in 2016 be moved? Can their parent directories be renamed?

I can obtain info about the VM like this:

((Compare-VM -Copy -Path 'H:VM.vmcx' -GenerateNewID).VM) | Select *

But I’m not sure how this helps me correlate the .vmcx or .vmrs files with the .vhdx or assist in the task at hand.

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 53 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/wp-db.php on line 1995