• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 405
  • Last Modified:

Print Cluster in Windows 2003 running on VMWARE

Hello Everyone,
I am currently working on a project where i need to move our current Standalone print server running on Windows 2003 Server running on VMWARE environment as a virtual machine to Cluster enviormnet. Can someone please guide me how can i move our current standalone print server running on Windows 2003 on Vmware as virtual machine to Vmware virtual machine in a cluster enviornment.

Your help is much appreciated.
0
novice1980
Asked:
novice1980
  • 7
  • 6
  • 2
1 Solution
 
mnasr333Commented:
If you mean *.vmx file to ESX file refet to this link

http://www.thoughtpolice.co.uk/vmware/howto/import-vmx-files-into-esx-server.html

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
0
 
novice1980Author Commented:
Thanks mnasr333 for your reply. I didnt mean this. What i mean is we are currently running our Print server on Windows 2003 running on one of ours ESX host. Now i have been asked to migrate and build a plan to move from this standalone print server to a clustered print server.

I need to know what my steps will be and how can i go about it.
Remind you the enviormnet will again be running on Vmware.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Do you mean Building a Microsoft Cluster? with two Virtual Machines?
0
 
novice1980Author Commented:
Thanks hanccocka for your reply and sharing such a great document. Yes i mean Building a Microsoft Cluster with two Virtual Machines and some how migrate my current stanalone print server running on Virtual machine on windows 2003 platform.

The downtime needs to be less for users and i couldnt find the way by which i can just add one more virtual machine on different ESX host and create a cluster and with current standalone print server running on domain environment as one node and add another node with new virtual machine


Can you please guide me through what will be the best way with less downtime for users
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
It would be easier to create new Virtual Machines Node 1 and Node 2, and add MSCD, the Printer Cluster, MIgrate the Printer settings and drivers using Printer Migratior 3.1 (http://www.microsoft.com/download/en/details.aspx?id=25311), and then over night, change the IP Address to the new Cluster, avoiding downtime.

But you would also need to create LUNs on your shared storage, and follow Cluster Virtual Machines Across Physical Hosts on Pages 21 of the

Setup for Failover Clustering and Microsoft Cluster Service
http://www.vmware.com/pdf/vsphere4/r41/vsp_41_mscs.pdf
0
 
mnasr333Commented:
Maybe you will need a complicated idea . Just make the name of your current server and its IP to be the virutal network name and IP in cluster and hence users will connect to same IP and name regardless which real machine running it . So you will
1) Prepare your second machine
1) first change IP and name of current first server
2) Add both servers to microsoft cluster with virtual name and IP of old print server



0
 
novice1980Author Commented:
Thanks hanccoka for your reply and guiding me through.

The problem which i am facing at the moment is that we have lets say clients they are using a print server with the unc path \\printserver and all the printers are shared to this print server. As an example \\printserver\PR1.

After creating Node 1 and Node 2 on virtual machine on different ESX hosts by following the documentation you have shared in your previous post and adding MSCD and the printer cluster. The name which i will be assiginig to this printer cluster will be different is that correct as an example it can be \\printerserver2 am i correct or am i wrong about it. If i assign a different name to my cluster then my clients will have issues in conneting to the print server they used to do it before. Which will be a great downtime for us.

Secondly the steps which i understand are:

Step 1: Create new Vitural machine Node 1 and Node 2 by following your document
Step 2: Add MSCD, the printer cluster by creating Resource group and all that, but what will be the name for this cluster
Step 3: Migrate Printer settings and drivers through Print Migrator 3.1 (Means backup from current printer server name \\printserver and restore it to the cluster server \\printserver or \\printserver2
Step 4: Change the ip address of cluster to be the old ip address of \\prinserver

Am i correct about these steps

Before all this LUNS need to be created on shared SAN and follow Cluster Virtual Machines Across Physical Hosts on Pages 21 of the Setup for Failover Clustering and Microsoft Cluster Service.

Thanks for your help again.



 

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Your biggest issue is going to be getting the SAN LUNs configured.

But your steps are fine.

You can add or change the cluster name later, when you switch over out of hours.
0
 
novice1980Author Commented:
You are right my biggest issue will going to be in configuring SAN LUNS as i am very new to this technology. May be i will post another on Storage area and request for help from such great persons out there like you who always try there best to help people like us.

The steps which i understand now is:

Step 1: Create new Vitural machine Node 1 and Node 2 by following your document
Step 2: Add MSCD, the printer cluster by creating Resource group and all that and name can be \\printserver2
Step 3: Migrate Printer settings and drivers through Print Migrator 3.1 (Means backup from current printer server name \\printserver and restore it to the cluster server \\printserver2
Step 4: During downtime change the name of the cluster from \\printserver2 assigned on previous steps to \\printserver and the ip address of the cluster to be the same like 10.0.1.5 as we have at the momemt for \\printserver 10.1.0.5

So what do you recommend the downtime will be, and how we can go about avoiding it.

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, that's correct, of course, you could use a different IP address, because you clients probably access printing by DNS or WINS name.

So the IP address could be different, it's up to you.
0
 
novice1980Author Commented:
Dear hanccocka i just found one of link that shows how to rename the cluster will this work under my case you reckon

http://technet.microsoft.com/en-us/library/cc757533(WS.10).aspx
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, thats one method.
0
 
novice1980Author Commented:
Thanks for your help
0
 
novice1980Author Commented:
Thanks hanccocka for all your help and support
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 7
  • 6
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now