Netware Physical to Virtual migration

I have one Netware server left. It is hosting a few services that I
haven't been able to replace yet. Need to move it off of older
hardware. Plan to move it to a VMware virtual server. I figure I
have two options:
1. Install a new NW6.5 server into the tree and manually move the
services over.
2. Use the server migration utility to transfer the server.
The server identity isn't critical...the services could run on any
Netware server. So I'm leaning towards option 1. But just thought I
would see if anyone had any thoughts on the subject.
Thanks,
Ken

On Thu, 30 Jan 2014 15:12:22 GMT, Massimo Rosen
<[email protected]> wrote:
>On 30.01.2014 14:44, KeN Etter wrote:
>> I have one Netware server left. It is hosting a few services that I
>> haven't been able to replace yet. Need to move it off of older
>> hardware. Plan to move it to a VMware virtual server. I figure I
>> have two options:
>>
>> 1. Install a new NW6.5 server into the tree and manually move the
>> services over.
>> 2. Use the server migration utility to transfer the server.
>
>3. Use an imaging product like e.g Portlocks Stprage Manager to
>basically copy the server over "as is".
>
>> The server identity isn't critical...the services could run on any
>> Netware server. So I'm leaning towards option 1. But just thought I
>> would see if anyone had any thoughts on the subject.
>
>Option three is most likely the fastest and most reliable, but comes at
>a cost. Options 1 and 2 really totalyl depend on your individual
>situation, for instance if the current server object in Edirectory is of
>*any* importance anywhere. If it isn't, option 2 wouldnt have much of an
>advantage over 1.
>
>CU,
Thanks. I think I'll still go with option 1.
Ken

Similar Messages

Physical to Virtual Migration Approach for Exchange CCR 2007 on Windows 2003 Ent Edition

Hi Team,
I am running Two exchange 2007 CCR in my environment on Physical node on windows 2003 ENT edition. MY Hardware is end of life and we are planning to migrate/Converting them into virtual environmnet running Vsphere 5.1.
can any one let me know the best approach to virtualize exchange CCR .
Exchange CCR details are :-
Windows 2003 Ent edition.
Excahnge 2007.
Quorum is configuraed on shared folder.
Exchange Primary replicating Data on Exchange Secondry ..Both Primary and Secondry are having Raid 10 Local Disks.

Hi Ravi,
you can take a couple of approaches here. First off, I want to make sure you are not wanting to do a P2V conversion, that is taking the OS image that is running on the physical host and, using VMware Converter, create a virtual machine from it. You could do it that way but, depending on how much mail data is there it could take a long time and it's not the preferred approach for Exchange.
I'm going to make a couple of assumptions here:
I'm assuming upgrading to Exchange 2010 is out of the question (if it is not just do that and move mailboxes )
I'm assuming that there is plenty of storage in the vSphere environment to satisfy the requirements of Exchange. Obviously you would have to provide enough storage for all mail data x 2 if you want to continue with CCR.
Your message says "local disks", so I'm guessing the RAID 10 you mention is not available for use for these virtual machines and that you will provide some type of shared storage.
So, if you have enough compute within a vSphere cluster and enough storage (capacity and IO) to satisfy CCR I see two options:
Leapfrog approach
1. Shutdown passive
2. Evict passive from CCR cluster
3. Create new VM, Clustering services, Exchange/add as passive to the cluster (you could run setup in recovery mode /m:recoverserver, but I don't see why you would want to in a cluster)
4. Seed databases
5. Failover
6. Repeat for other physical
New Cluster
1. Create two new VMs
2. Create new CCR Cluster
3. Install Exchange active/passive
4. Move mailboxes
5. Decomm physicals
Obviously these are very high level but the approaches are straight forward. If this is your only set of Exchange servers in the environment you will have to account for any public folders/system folders, etc. Take some time and check out compute usage in the current environment so you are sure you have plenty of compute in the vSphere environment, especially if you are moving into a shared environment.
-alex

Physica to virtual migration of 4 TB disk Machine from VMware to hyper-v

Hi Team ,
I have virtual machine running on VMware with disk size of 4 TB.. 2/2 TB VMdk combined into 4 TB. since earlier VMware has 2 TB vmdk limitation. i am moving my environment from VMware 4.x to windows 2012.
i have done few p2V successfully but in this case disk are not visible on SCVMM console. Please let me know if i have any other option to migrate 4 TB machine.
Thanks in advance.
Ravi
Ravi

Hi Ravi,
"then both 2 TB disk merged and presented as 4 TB partition to windows OS."
I assume that it is spanned volume .
After "merge" , the 4TB disk become a data disk to provide file share in the windows OS .
At this situation , my suggestion is Migrating your file server to a new VM.
As for file server migration , please refer to following link:
https://blogs.technet.com/b/josebda/archive/2009/06/30/microsoft-file-server-migration-toolkit-1-2-available-as-a-free-download.aspx
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Conversion from physical to virtual server

Our server technology group wants to convert our physical
server that contains the RoboEngine to a virtual server (using ESX
VMware). We are using RoboHelp 5 to publish WebHelp to the
RoboEngine. Has anyone else converted from a physical to a virtual
server? If so, could you tell me about any problems you
encountered?
Thanks,
Liz

Hello Nelson,
There are quite lot of things in TMG which are dependent on Hardware.
If you want to migrate from physical to virtual server, you can follow the steps here which are recommended/supported way of doing it.
Though this article is for ISA to TMG migration, still you can follow the same steps for Physcial to Virtual migration.
http://technet.microsoft.com/en-us/library/dd440994.aspx
Please let us know, how it goes!

Sap Server movement from physical to virtual(p2v)

Hi all,
We currently have two older versions of R/3 running 4.6c and 4.7ee, both IDES versions.
These versions have been out of support for some time.
We have these instances running for reference purposes. We have new versions of R/3 ECC 5.0, 6.0
also running in our company. All these versions of R/3 are IDES.
Our Windows administrators are of the opinion that servers on which the instances 4.6c and 4.7ee are running are very old,
and spares are hard to find. So they want to move these instances from a physical environment to a virtual environment.
I have read through the Note: 1409608.
It says,
SAP does not support SAP systems that are installed on Windows 32-bit
in a virtualized environment. If you plan to migrate your SAP system that is running
on native hardware on Windows 32-bit to a virtualized environment
on Windows 64-bit, it might be necessary to upgrade the SAP system to a higher release.
For these configurations, SAP recommends to migrate the SAP system to Windows x64 first
and then upgrade the SAP system.
Now, I don't think is it quite possible to upgrade 4.6c and 4.7ee to 64 bit.
License keys on windows are based on SID, Hostname, MAC address of the network card.
If we make sure that the MAC address is the same and
that its at the same place as before(sequence of multiple network cards is the same),
we can still Use the old license.
Our Windows guys say its very hard to retain the MAC address, they can try it.
So with these old versions of R/3, how can we keep them running, if they have to be moved from Physical to virtual,
as license keys and installation software is hard to get.
Regards,
Vishnu.

Hi Markus,
Thanks for your reply. Would open an OSS call.
I have looked at the note mentioned by you, and since our OS is windows, I thought the below statement
holds good in my case. From the note I have also deduced that for Windows, licenses are based only on the Hardware Key.
Am I wrong in assuming this?
Only Windows uses a hardware key that does NOT depend on the hardware.
A new installation of Windows definitely causes the hardware key to change.
I have also looked at note 793649, which says Hardware key changes only when,
1. Formatting the machine and reinstalling Windows.
2. When changing the computer name.
3. When changing the domain (it will not change back when returning to the previous domain).
Regards,
Vishnu.

SCCM 2012 hierarchy from Physical to Virtual

I have an existing standalone SCCM 2012 hierarchy on a physical server with ~ 50K clients reporting with additional servers hosting various site system roles. Now the requirement is to migrate this hierarchy on a virtual environment. Client doesn't want
to do P2V migration and wanted to have the migration done on new infra.
In current hierarchy we have client health compliance at ~90% and we have to maintain the same post migration additionally there are lot of collections, packages and deployments those needs to be successfully migrated.
Please suggest a feasible and most efficient solution for this

Client doesn't want to do P2V migration
Assuming that you have done your homework and are OK that Virtual is the way to go, the easiest way to migrate from Physical to Virtual is to carry out a P2V migration. I don't quite understand this.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

How to Install Physical and Virtual Host

I am getting licensing issues after I installed Essentials 2012R2 on a physical machine and then used the same license to virtualize it. It's saying my physical machine needs to hold all the FSMO roles in which my virtual machine is hosting those roles.
I read that Microsoft allows you to use the Essentials license for the physical and virtual server. Is that correct?
Is there a specific service I need to remove on the physical machine in order for these errors to stop? I still have the Windows Server Essentials Experience service installed. Is that what needs to be removed?
Thanks,
Doug

Hi Doug,
There is an article that provide details of licensing for Windows Server 2012 R2 Essentials. Please refer to and check if can help us to understand licensing for Windows Server 2012 R2 Essentials better.
Understanding Licensing for Windows Server 2012 R2 Essentials and the Windows
Server Essentials Experience role
Please also refer to following article and check if can help you.
Customize Deployment - Windows Server Essentials
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Physical to virtual ends with errors, other methods export but launch with windows repair 2008 r2

New to hyperV here, plan to implement it in a few months. So I am practicing with it now.
I am trying to convert a working 2008 r2 physical to virtual using Microsoft virtual machine converter. in the settings I was point it to my hyperv- server and I was getting errors, this was due to permissions. No matter what I did I can't get it to
work, not sure whats wrong. SO I installed hyper V under my win8.1 pro machine shared the folders and the export started.
Upon the end of the export where it goes into "Fixing disk' I get an instant error no matter how may times I do this or how which server I try to export I get an error here.
It still created files and when I then copy those over to my test hyper V the win2008 R2 export goes into repair mode, I'm sure it's a driver issue but I would have expected that MS would have stripped the drivers our before export.
I then tried Acronis backup server and was able to export to MS virtual machine but this export also goes into windows repair more.
In the past I've used acronis and restored a physical server , this would also go into repair mode unless I use the "intelligent restore" which strips the drivers.
I don't want to tinker with the live server to get this to work since It's still in production, but I would like to get this to work , would any one have a tip, what can I do to provide more information on the root of the problem?
nambi

Hi Sir,
>>I am trying to convert a working 2008 r2 physical to virtual using
Microsoft virtual machine converter.
Generally, I would suggest you to use
Disk2Vhd to convert a physical computer to Virtual Machine (virtual hard disk) then create a VM and attach that VHD .
Please refer to this
article .
Any further information please feel free to let us know .
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

SCCM report query that displays count of cpus per host and if host is physical or virtual

Hello,
I have this query that displays the count of CPUs per host. How can I add a column to show if the host a physical or virtual?
SELECT
DISTINCT(CPU.SystemName0) AS [System Name],
CPU.Manufacturer0 AS Manufacturer,
CPU.Name0 AS Name,
COUNT(CPU.ResourceID) AS [Number of CPUs],
CPU.NumberOfCores0 AS [Number of Cores per CPU],
CPU.NumberOfLogicalProcessors0 AS [Logical CPU Count]
FROM [dbo].[v_GS_PROCESSOR] CPU
GROUP BY
CPU.SystemName0,
CPU.Manufacturer0,
CPU.Name0,
CPU.NumberOfCores0,
CPU.NumberOfLogicalProcessors0

I see that you have posted this exact question in another forum for CM12, however this is an CM07 forum.
Are you CM07 or CM12?
If you are CM12, use my answer here.
http://www.systemcentercentral.com/forums-archive/topic/sccm-report-query-for-cpu-cores/
If you are CM07, this is NOT a simple how exactly do you detect that a computer is a VM? You can guess by looking at the manufacturer name but it is only a guess.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Best Practice for Operations Masters physical vs. virtual.

I understand that the schema master and the domain naming master should be co-located. As well as the RID master PDC emulator should be co-located. But I
cannot find any "best practices" documents for mixed server environments.
When you have both physical and virtual environments. Are there any “best practices” documents on mixing the two sets of roles between the two environments?

Hello,
see here about, especially "Load and criticality may dictate that some roles be deployed on physical hardware":
http://support.microsoft.com/kb/888794
Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Physical to Virtual Cluster using SAS - is it possible?

We're prepping to dramatically increase our IT infrastructure here, and I need a little advice. We're changing our practice management software from something running on a relatively lightweight database to MS SQL Server. With that we're planning a big upgrade
in computing and storage, plus we'd like to add failover clustering to help guarantee a certain level of service.
The current plan calls for 3 physical servers running WS2012R2 connected directly to a SAS array on an IBM DS3524. Physical server A will host the primary SQL Server database, plus a few light-usage VMs for testing and dev stuff. Physical server B will host
images and files, no SQL Server, plus a bunch of RDP VMs. Physical server C will host a nightly copy of the primary database used for heavy reports, plus another couple of VMs for various network functions.
Ideally we would like to cluster the physical server A to a VM on physical server B. I'm unsure, though, if that can be done using the direct attach SAS drives. We do not want to set up an iSCSI SAN.
Two questions, then:
Is this type of failover setup even possible? If so, how would we set up a shared storage between a physical server and a VM on a second physical server using direct attached SAS?
If this isn't possible, would we be better off virtualizing the primary database and clustering the two VMs (best practices from our software vendor recommend virtualizing everything *except* the primary DB server), or setting up a physical failover from Server
A to Server C? In the event of a failure, server C would then find itself hosting 2 databases, though we could restrict reporting during a failure to lighten load.
Thanks -
Mike

We're prepping to dramatically increase our IT infrastructure here, and I need a little advice. We're changing our practice management software from something running on a relatively lightweight database to MS SQL Server. With that we're planning a big upgrade
in computing and storage, plus we'd like to add failover clustering to help guarantee a certain level of service.
The current plan calls for 3 physical servers running WS2012R2 connected directly to a SAS array on an IBM DS3524. Physical server A will host the primary SQL Server database, plus a few light-usage VMs for testing and dev stuff. Physical server B will host
images and files, no SQL Server, plus a bunch of RDP VMs. Physical server C will host a nightly copy of the primary database used for heavy reports, plus another couple of VMs for various network functions.
Ideally we would like to cluster the physical server A to a VM on physical server B. I'm unsure, though, if that can be done using the direct attach SAS drives. We do not want to set up an iSCSI SAN.
Two questions, then:
Is this type of failover setup even possible? If so, how would we set up a shared storage between a physical server and a VM on a second physical server using direct attached SAS?
If this isn't possible, would we be better off virtualizing the primary database and clustering the two VMs (best practices from our software vendor recommend virtualizing everything *except* the primary DB server), or setting up a physical failover from Server
A to Server C? In the event of a failure, server C would then find itself hosting 2 databases, though we could restrict reporting during a failure to lighten load.
Thanks -
Mike
Discussed with more details on SpiceWorks here:
SpiceWorks Discussion
http://community.spiceworks.com/topic/462437-failover-cluster-2012r2-physical-to-virtual-sas
Making long story short: use shared VHDX. Quote:
You need to have 100% virtualized workload and then you can use shared VHDX placed on CSV placed on top of your clustered storage (SAS + Clustered Storage Spaces). That would do the trick. See:
Shared
VHDX
http://blogs.technet.com/b/storageserver/archive/2013/11/25/shared-vhdx-files-my-favorite-new-featur...
Shared VHDX in Failover Cluster
http://technet.microsoft.com/en-us/library/dn265980.aspx
Clustered Storage Spaces
http://technet.microsoft.com/en-us/library/jj822937.aspx
Another option you've mentioned is to run clustered MSFT target on top of a SAS-back ended cluster. But that's both slow and ugly. Another option would be using clustered out-of-box iSCSI stack but that's not free and makes less sense as you have IBM SAS already.
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Will UE-V work across Physical and virtual desktops

We are currently evaluating few product, and are looking for a product that can work across our VMWare VDI infrastructure as well as physical hardware to provide transparent and seamless UEM. Profile management is a key for us, the goal is to achieve as
identical as possible experience between out Windows 7 and 8 machines.

UE-V is designed to synchronize data between any desired environments. This includes physical systems, virtual desktops, RemoteApp applications, and App-V applications.
See the Comparing UE-V to other Microsoft products section here.
The ability to synchronize common settings between Windows 7 and Windows 8 was
added in UE-V Beta 2.
Brandon
MDOP on the Springboard Series on TechNet

Physical Server Clustered Migration to Virtual Machine

Dear All,
We got an request from SQL server running on physical server migrate to virtual machine.
Please advice me the procedure and checklist for this migration request.
Thanks.

Hi mailatdinesh,
If you want to run SQL Server in a virtual machine (VM), here are some of the essential tips for virtualizing SQL Server.
1. To support bare metal virtualization platforms, you need to make sure that the host uses a 64-bit x64 processor; In addition, for a resource-intensive workload like SQL Server, it's vital that the host processor supports Second Level Address Translation.
2. SQL Server can automatically take advantage of multiple CPUs if they're present. If you're migrating from a physical SQL Server implementation to a virtualized SQL Server implementation, you can use the number of CPUs in the physical implementation as
a guide for the number of virtual CPUs that you'll configure in the SQL Server VM.
3. In order for SQL Server to take advantage of dynamic memory, I recommend you to use the Enterprise edition of SQL Server 2008 or later or using the Datacenter edition of SQL Server 2008 R2 or SQL Server 2008.
For more information , see:
http://sqlmag.com/sql-server/sql-server-virtualization-tips
When you migrate one instance from one server to another, as other post, you can use backup and restore, the sp_detach_db and sp_attach_db stored procedures, or
the Import and Export Data Wizard to copy objects and data between SQL Server databases, you also need to transfer logins and passwords between instances of SQL Server, move jobs, alerts and operators. For more information, you can refer to the following
article,
http://support.microsoft.com/kb/314546
There is also similar issue about moving SQL Server to VM, you can refer to the following post.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/43085f0f-4526-4994-be95-530aecb5dd7c/moving-sql-server-to-vm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Blue Screen Error during starting Windows Server 2008 R2 (VM on Hyper-v WinSvr2012) Using a Physical to Virtual (P2V) VHDX.

Hi There,
I'm trying to migrate one of my physical Windows Server 2008 R2 to Virtual Environment (Hyper-V on WinSvr2012).
(The original physical machine had multiple partitions on the windows HDD and 2 other boot able OSs where installed on 2 of those partitions ...) So anyhow, After heaps of trouble shooting and fixing the boot records, it finally started booting the
Windows but when it got to loading C:\windows\System32\Drivers\Classpnp.sys
and it crashed, a blue screen poped up saying "A Problem has been detected and windows has shut down to prevent damage to your computer ... ) and then system got rebooted automatically.
I have tried chkdsk, also tried copying a new classpnp.sys to replace the old one but no hope. I don't think is not a damage file issue. Not sure, but it is probably related to changing the HDD devices or SCSI/IDE controllers?
Any idea?

1. You have placed your problem in wrong forum. Address your problem to Server forum instead.
2. I do not think it is liable configuration. I have not heard about migration of multiboot HDD. Try to split it. Pay attention to better preparation. I would expect separate target VM.
Regards
Milos

Block alignment for NetWare 6.5 Virtual Machines

I have an enviornment with multiple virtualized Netware VM's running on vSphere. Some were converted using VMware's P2V software other's were migrated using the SCMT.
My question relates to block alignment at the NSS layer. I have the block alignment handled up to this point:
SAN Luns: 64kb
VMFS Partitions: 64kb
VMDK files: If created using the vSphere client 64kb. If P2V ???
NSS partitions within VMDK: ???
What is the default block size for the NSS partitions in Netware? I there a way to check?
If they are not at 64KB, Is there a tool available to re-align them to 64kb?
Thanks for the help!

The default and only available block size for NSS is 4k. No alignment should be necessary as 4 divides evenly into 64.

Netware Physical to Virtual migration

Similar Messages

Maybe you are looking for