[THIN] Re: MF 1.8 to MFXP migration strategy
- From: "Mike Semon" <msemon@xxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Thu, 19 Feb 2004 19:31:06 -0600
Rob,
For our environment we had too many servers (100+) to upgrade for the
mixed-mode
route. Concerns were raised about interoperability and the length of
time to upgrade the MF 1.8 farms. We opted to use Nfuse to provide support
for our legacy and new server farms. This allows us more time to complete
the upgrades, collapse domains,..etc. However, what is right for our
environment
may not be right for yours. The wonderful thing about IT is there is often
more
than one right answer. Let us know how your upgrade works.
-Mike
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Rob Slayden
Sent: Thursday, February 19, 2004 4:25 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MF 1.8 to MFXP migration strategy
I proposed that but it was rejected due to costs so it is not really an
option. The way I understand it, you can add the pub apps to the MFXP
servers once they are up but you must manage each server products' pub apps
in its native tool (MF 1.8 with PAM, MFXP with CMC). I don't plan on making
any pub app changes during the migration and I intend to complete the
migration ASAP and get into native mode. Do you recall any other issues?
Have you completed a migration from 1.8 to XP successfully?
Thanks,
rob
-----Original Message-----
From: Mike Semon [mailto:msemon@xxxxxxx]
Sent: Thursday, February 19, 2004 1:00 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: MF 1.8 to MFXP migration strategy
As I recall there are some gotcha's in going the mixed-mode route. I think
there was an issue about using published applications between farms and
licensing.
Seems to
me you could not change this until your servers were upgraded to XP.
Building the XP
farm separate is the way to go if you can.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Rob Slayden
Sent: Thursday, February 19, 2004 2:46 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] MF 1.8 to MFXP migration strategy
I'm planning to migrate a 27-server MF 1.8 farm to MFXP. Going to do the
mixed-mode migration by replacing the master browser with an MFXP ZDC in
interoperability mode, then rebuild all NT 4/MF 1.8 servers to W2K3/MFXP
FR3. Should be no problems competing the migration within 6 weeks and going
to native mode. I've been reading all I can on this including Brian Madden's
Adv. Technical Design Guide (Da' bomb!) and Citrix WPs and it appears that
part of the key to this is to use the same farm name as the MF 1.8 farm.
Well, it is not actually in "Farm" mode but NT domains scope. Also
complicating matters potentially is the existence of a new MFXP farm (5
servers) with which I want to communicate.
These are the steps I believe I need to complete to accomplish my end goal
of a single farm with two zones.
In the existing MF 1.8 farm, "Create a Server Farm" in PAM and name it the
same as the existing MFXP farm.
Replace the MF 1.8 Master Browser with an MFXP ZDC in interoperability mode
(same IP), as a second zone. This ZDC and the other ZDC should communicate
now and all 4000 terminals pointing to the Master Browser IP should work.
Upgrade the 27 servers from NT 4/MF 1.8 to W2K3/MFXP, in a phased approach
obviously, but as quickly as possible.
When the migration is complete, re-configure the ZDC for native mode to
eliminate all the unnecessary "interoperability" traffic.
That said, here are some questions that come to mind:
What are the ramifications of the MF 1.8 "Create server farm" with the same
name as the existing MFXP farm?
Will there be any issues adding the ZDC to the MF 1.8 farm with the name of
an existing MFXP farm? I presume I will be able to simply make it another
zone.
Will the data store (in the MFXP farm) have any issues when the ZDC is
brought online in the MF 1.8 farm?
Any issues using the same DS for the two zones even though the servers in
the second zone are MF 1.8?
I do intend to test as much of this in the lab as possible before I swing
the wrecking ball through my production MF 1.8 farm <g> but I thought maybe
some of the experts might be able to point out some glaring holes in this
strategy.
Thanks in advance!
Rob
24 Hour Fitness, Inc.
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting vc-iMapper
--> - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting vc-iMapper
--> - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or set Digest or Vacation mode use
the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting
--> vc-iMapper - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
********************************************************
This weeks sponsor Vizioncore, Inc.
--> vc-iMonitor - Performance Monitoring, Control & Reporting
--> vc-iControl - Desktop & Start Menu Management & Reporting
--> vc-iMapper - Drive, Printer & COM Management & Reporting
http://vizioncore.com/products.html
**********************************************************
Useful Thin Client Computing Links are available at:
http://thethin.net/links.cfm
***********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
