Upgrade path question...

I've been using golive 6 and in about a month I'm planning to upgrade...I'm seeing upgrades to golive 9 (which i read here has its problems), CS2 which I'm assuming I can update golive 6 to, and then the alternative that the Adobe site offers/suggests, switch to Dreamweaver...
I haven't followed all the changes and rumor...maybe you can help me here...is golive a dead end now? Is Adobe going to eventually just abandon it for DW?...
Also, I'll be updating my other adobe software to CS3 for photoshop, illustrator, and indesign...so nice integration between Golive CS2 or DW would be a goal...
Please don't shoot me if this isn't the place to ask, it just seems you guys know everything when I come with a question about me being lost and confused in golive...
oh, I did watch the little video presentation about DW on the Adobe site...i didn't feel totally lost looking at the examples there...I do wonder if DW will just be so new that'll i'll be totally lost for while...I've read of some complaints from golive users in the past...
I mean, can you tell me if DW has any 'major' shortcoming?...I'm not familiar with it...just know about golive 5 and 6 which wasn't too complicated and allowed me to do a website 'almost' pain free...
thanks for any advice/experience/tips you can pass along...I mean I could spend near $200 for the CS2 update or for $400 just buy DW...just don't want to waste money on an update if it doesn't make sense/cents...
thanks...
M

ok, so i just found this in the golive to dw transition forum...i think this starts to explain what i need to know...
http://www.adobeforums.com/webx/.3bc63381/3

Similar Messages

WLC code upgrade path questions

We running WCS 6.0.132(lastest) and our controllers are on 4.2.130, we now want to upgrade to keep up with the times, but don't want to change over to capwap yet.
Question1:What's the latest LWAPP release code??
Question2:Whats the differences between 4.2.207 (cisco's support page says this is the latest release) but there's even releases with much higher versions ie 6.0 how does this work it's very confusing to workout an upgrade path
Cheers

Hi Tyrone,
I'm not an expert on Versioning but here are some basic details in response
to your query
4.2.207 is the latest release on the 4.2 Train and is probably an excellent choice
if you are avoiding CAPWAP for the time being. You will see in the link below that
there are multiple "simultaneous" Trains for the WLC (and most Cisco products). People
were not huge fans of the early 5.x Trains (quite buggy) and CAPWAP was introduced
in 5.2 and forward so this is why 4.2.207 seems like a good fit for you
In controller software release 5.2 or later, Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points protocol (CAPWAP) in order to communicate between the controller and other lightweight access points on the network. Controller software releases prior to 5.2 use the Lightweight Access Point Protocol (LWAPP) for these communications.
CAPWAP, which is based on LWAPP, is a standard, interoperable protocol that enables a controller to manage a collection of wireless access points. CAPWAP is being implemented in controller software release 5.2 for these reasons:
      To provide an upgrade path from Cisco products that use LWAPP to next-generation Cisco products that use CAPWAP
      To manage RFID readers and similar devices
      To enable controllers to interoperate with third-party access points in the future
LWAPP-enabled access points can discover and join a CAPWAP controller, and conversion to a CAPWAP controller is seamless. For example, the controller discovery process and the firmware downloading process when you use CAPWAP are the same as when you use LWAPP. The one exception is for Layer 2 deployments, which are not supported by CAPWAP.
You can deploy CAPWAP controllers and LWAPP controllers on the same network. The CAPWAP-enabled software allows access points to join either a controller that runs CAPWAP or LWAPP. The only exception is the Cisco Aironet 1140 Series Access Point, which supports only CAPWAP and therefore joins only controllers that run CAPWAP. For example, an 1130 series access point can join a controller that runs either CAPWAP or LWAPP whereas an 1140 series access point can join only a controller that runs CAPWAP.
http://www.cisco.com/en/US/products/ps6366/products_qanda_item09186a008064a991.shtml
4.2.207 was released 24/Jul/2009 which does make it the second newest version available in any train.
http://www.cisco.com/en/US/products/ps6366/prod_release_notes_list.html
Cheers!
Rob

Windows 8.1, Update 1 upgrade path

Hi, if there is anyone of any influence who might read this, please, please, for you own sakes make an upgrade path directly from Windows 8.0 --> Windows 8.1, Update 1
I cannot upgrade from W8.0 --> 8.1.
I cannot upgrade due the the following error. But I believe it is a silly error and can be overcome as some have managed:
https://answers.yahoo.com/question/index?qid=20131018074442AAswJqp
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_install/windows-81-install-unable-to-create-ramdisk/887b5adc-86ce-4c37-9c58-72eca5f712d4?page=8&tm=1396807793681
I even had a MS 3rd line Andswer Desk (ref:1233447567.) guy who was remote controlling my machine trying clean boot give up after saying that if my
MB manufacturer wont support drivers past Vista then there is nothing they "should" do... But Vista is EoS but not extended support as XP is, that ends 2017:
http://windows.microsoft.com/en-gb/windows/lifecycle
This is an issue I'm having with my personal PC but I also work in IT infrastructure and I think this needs to be sorted. This is going to become a BIG issue for many other people who have Vista/XP-grade systems with the requirements for 8.1.1 who will try
to upgrade.
Please can someone help?
System: Q6600, MB: XFX Nvidia Nforce 680i LT, 8GB RAM

Hi,
Windows 8.1 do have have higher requirements for hardware, If your computer hardeware device was too old, you may encounter some problem during install or using Windows 8.1.
Roger Lu
TechNet Community Support

Nexus 7010 upgrade path

We currently have two Nexus 7010 with 5.0(2a) as system images.
We would need to know the correct upgrade path to 6.1(1). On the release notes it reads the path is from 4.2(8), 5.0(5) or 5.1(6) to 5.2(5) then to 6.1(1).
Also if ISSU is possible or, because we may need to upgrade EPLD, if there is no upgrade path to do a non-disruptive upgrade.

You probably need to dig a little deeper to get a definitive answer (sup1 or 2, type of cards, etc..) but here is a diagram in the release notes for 6.1 found here:
http://www.cisco.com/en/US/docs/switches/datacenter/sw/6_x/nx-os/release/notes/61_nx-os_release_note.html
If this posts answers your question or is helpful, please consider rating it and/or marking as answered.

10.2.0.4 on OEL x86-64 Upgrade Path Issues

I am performing a new installation of Oracle Enterprise Manager Grid Control (OEM GC). I want to want to run Oracle Enterprise Manager 10.2.04 on Linux x86-64 - OEL 4 update 5. My installation for OMS and Repository will be on one server. I will install the database separate from the OEM GC installation.
My upgrade path is a full install of Oracle Enterprise Manager 10.2.0.3 followed by patch to 10.2.0.4. I desire to have my databases at 11g so I would have to upgrade 10gR2 database to 11g database as well. My questions are as follows:
1) Linux x86-64 is not supported on 10.2.0.3 according to certify page. Why is OEL 4 update 4,5 not on Certification page for OEM GC?
2) What installation instruction set should I follow for 10.2.0.3 GC on Linux x86-64? Linux x86-64 documentation following RHEL install?
2) Oracle 11g Repository is also not supported on 10.2.0.3. Is it possible (is it supported?) for me to install Oracle Database 11.1.0.6 EE as repository for OEM GC 10.2.0.3 then only patch OEM GC to 10.2.0.4?
Thank you.

There is no direct full installer to 10.2.0.3 Database. Do I need to do the following:
1) Install OEL 4 Update 5 x86_64
2) Meet prerequisites for Oracle Db 10.2.0.1 (x86_64 - only full installer is 10.2.0.1)
3) Patch Db to 10.2.0.2 or 10.2.0.3 (is there a reason for 10.2.0.3)
4) Install OEM GC 10.2.0.3
a) requires 10.1.0.4, 10.1.0.5, 10.2.0.2 or 10.2.0.3 database
b) use ignore system requirements parameter since OEL 4 Update 5 (x86_64) is not supported
5) I am not sure if any patches are required to OS, DB or OEM at this level
6) Patch OEM GC 10.2.0.3 to 10.2.0.4
7) I am not sure if any patches are required to OS, DB or OEM at this level
8) Follow note: 467677.1 replacing OEM GC 10.2.0.1 with my version 10.2.0.3 and upgrade db to 11g
done
Does this look correct? Is there a more efficient way?

IDSM-2 upgrade process questions.

Hello,
I started a new job and have been tasked with looking into what we can do with the IDSM-2 module we have in our 6509. The company has not been using the module so it hasn't been updating in a few years. I do not have a current license so I know I cannot install new signature updates, but what I would like to do is upgrade the software to version 7.0(5a)E4. Once I have it upgraded I would like to configure it in our environment and then see about getting a signature license.
I have a few questions regarding the upgrade process, and could use some assistance.
First the IDSM is currently running version 5.1(3)S256.0. From what I have read I don't believe I can go directly to 7.0(5a)E4 so my Planned Upgrade Path is: 5.1(3)S256.0 -> 5.1(8)E3 -> 7.0(5a)E4.
Am I able to upgrade this way or is there another recommended way that I should do this upgrade?
The files I have for this are below, will they be enough or am I missing any?
Do I apply them in the order listed?
Can I apply all of these files from the IDM GUI?
IPS-K9-5.1-8-E3.pkg
IPS-engine-E3-req-5.1-8.pkg <--- Is this included in the above file?
IPS-K9-r-1.1-a-5.1-8-E3.pkg
IPS-K9-7.0-5a-E4.pkg
IPS-K9-r-1.1-a-7.0-5a-E4.pkg
I plan on backing up my configuration first just in case, but should this process have any affect on the configuration?
I also saw that the upgrade will convert the configuration, so should I back it up a second time between the 5.1(8)E3 and 7.0(5a)E4 step?
Will there be any effect on network traffic or downtime during this process?
Is there any thing else I need to be aware of or that I'm missing?
Thanks in advance,
Will

Hi Will. Since you indicated that this sensor has not been in-use, it would be quickest/easiest to simply re-image it directly to the desired version (7.0(5a)E4). Additional benefits of doing this are that the sensor's filesystem will be created clean, OS/binaries cleanly installed, no potential config conversion issues, etc.
Step-by-step instructions for doing this can be found here.
And, the System Recovery Image file you will need ('IPS-IDSM2-K9-sys-1.1-a-7.0-5a-E4.bin.gz') can be downloaded here.
Will there be any effect on network traffic or downtime during this process?
That depends on whether the sensor is configured in Promiscuous Mode or Inline [VLAN Pair] Mode. You can determine this from the Catalyst config. If the sensor is installed in Inline [VLAN Pair] Mode, then certainly the re-image (and even just upgrade) could be traffic-impacting (if there is no alternative/backup path for traffic to take), as in both scenarios, the sensor is rebooted and not available for ~10 minutes (during which time, it would not be forwarding traffic (if it were installed Inline)). Additionally, since re-imaging results in a clean/default config, if the sensor were configured Inline, that portion of the config would have to be re-input post-reimage so that the sensor would know to forward traffic accordingly again. Details about the modes can be found here.

Is there an upgrade path from Logic Pro 9 to Logic Pro X?

I convinced a friend to purchase Logic Pro 9, not knowing version X was about to be released 3 weeks later. Even though upgrade path always crosses my mind prior to a software purchase, I was not worried - this was Apple. Now it's looking like there's not a built-in upgrade path at all (as there IS with just about every other software company I have bought from). Is this for real? This friend has version 9, and I have version X. So this friend learned everything there is to know about version 9, then I bought version X not even knowing we were out of synch on versions. We were hoping to work on songwriting together, but paying $200 again is out of the question. I notice that the file save under version X has extension .logicx, so is it even possible to exchange files?

my friend with Logic Pro 9 can send files to me but they cannot accept files created with Logic Pro X.
Which is exactly what i said earlier....
You can open Logic Pro 9 projects in LPX but not the other way around.
Apple wouldn't even give me a refund on Logic Pro X (purchased just 3 days ago), which is useless to me now.
There are no refunds from the App Store... That is what you agreed to when you purchased a license for LPX.
Your choice is simply for your friend to update to Logic Pro X or use the audio stem process I outlined earlier (Not something i would recommend doing for any period of time)... or spend even more money on purchasing two copies of a different DAW... and taking the time to learn them and spending time converting over what your friend has already created... and hope your friend hasn't been using the internal plugins found only in Logic Pro... otherwise you have even more work to do...
The reality is, the sensible solution is simply to upgrade LP9 to LPX for $200... (and think of it as the upgrade price even though you can buy the full version for the same amount but that really doesn't matter does it?) Less outlay, less time lost and less hassle, but as always the choice is yours...
I have never, EVER, encountered a software company that treated customers that way.
Then you haven't been in the computer business that long......
Seriously though, you haven't been treated that badly...
You bought LPX at a price that is basically a steal.... and your friend bought LP9 at the same 'deal' of a price.. compared to what Logic Pro used to cost ($1000)
You can 'upgrade' from LP9 to LPX for $200 which is much cheaper than it used to cost to upgrade from , say LP8 to LP9... and the same price as it cost to upgrade to LP9 via the App Storeprior to the release of LPX
The alternatives at this stage would cost you much more money......time.. and hassle..
The only things that truly frustrating is the timing of your friend's purchase of LP9... For that he has my sympathies but it happens... Some people who bought Logic Pro 9 within a month of Logic Pro X being released were given refunds on the LP9 purchase if they bought LPX... Your friend just left it way too late.... Apple has since stopped such refunds.... and you didn't do the research you should have done before you jumped in and bought LPX... Unfortunate but sadly true.
Again, you and your friend have my sympathies for whatever they are worth... but at least the obvious solution is still cheap compared to what the alternatives could cost you now and in the past!

Upgrade path for Cisco EIM/WIM v4.2(5)

Hi all,
I need some help in understanding what is required to deploy Cisco EIM/WIM v4.2(5) for Cisco UCCE.
a) media kit received contained v4.2(1), 3rd party tools, v4.2(4a) SR & v4.2(5a) MR
b) based on the docs, v4.2(1) needs to be installed first followed by v4.2(4a) SR and then v4.2(5a) MR
Some concerns/questions i have is
a) Since v4.2(1) only supports SQL 2000 and v4.2(5) only supports SQL 2005, does that mean i'll require to purchase both SQL 2000 & SQL 2005? Can I install v.4.2(1) directly on SQL 2005?
b) Since v4.2(1) only supports BEA WebLogic, is there a way to change it to JBoss when upgrading to v4.2(5)? If so, any idea how that can be done? If not mistaken this is possible when upgrading to v4.3(1).
c) Is there a way to directly install v4.2(5) without going to the mentioned upgrade path
Thanks!
-JT-

HI
The license is assigned to a MAC address so if you have other NICs available it may cause issues. As the system maybe comparing the wrong NIC. I dont believe you can "Reload" the license. I am all most certain you are hitting a bug with the license file. There are a number around :-(. Below is the most common:
http://www.cisco.com/en/US/partner/products/ps7233/products_tech_note09186a0080a8c0bc.shtml
I know your symptoms do not match "Exactly" but I had the same issue as you and just upgraded to 4.2(5) and then applied ES1. That fixed all my problems. I have attached ES1 for you. If you are still not to sure then i would probably open a TAC case but they are probably going to tell you to upgrade to 4.2.4 or 4.2.5 first.
If you decide to upgrade to 4.2.5 please also take note of the following:
http://www.cisco.com/en/US/partner/products/ps7233/products_tech_note09186a0080a72faf.shtml
You need to make sure that the collation in SQL is set to SQL_Latin1_General_CP1_CI_AI. The above guide exsplains how to check this and change it if it is incorrect.
Thanks,
Matt
(Edit)
The patch is to large to upload but you can download it from here for 4.2.5:
http://www.cisco.com/cgi-bin/tablebuild.pl/ba8630bc8d6cd87a3b23513eb7700b54
OR if you dont fancy going all the way to 4.2.5 you can download the patch for 4.2.4 here:
http://www.cisco.com/cgi-bin/tablebuild.pl/70fc7a9f5f1315519a00b2b3c0dc48d8
Message was edited by: matthewpage

Upgrade path for TREX / Internet Sales

Can anyone point me in the direction of SAP info regarding upgrades to TREX and Internet Sales?
We're on very old unsupported versions of these and I'm looking for info on both latest versions and whether there are upgrade paths from our current version. Happy to dig out the detail myself if someone can point me in the right direction.

OK, answered my own question now I've discovered the newer product is called e-commerce 5.
David

A.W. 6.0.4 Upgrade path to X

I bought a copy of A.W. 6.0.4, my iBook is completely X. I can not install the 6.0.4 and the updater will not recognize the install CD as being in the "correct" area.
Any ideas on how to make a upgrade path so I can get A.W. 6.0.4 to 6.2.9.
I do have a OS 8.6 computer but if I install 6.0.4 to upgrade I will be installing another copy of Apple works. I am stuck
Thanks
Sue

Hello Susan,
Classic installs under OS X as if it were another program. Basically, classic mode runs just like any other program in OS X. It doesn't require you to remove OS X first.
So, it shouldn't be much of an inconvenience. I think it only takes a couple of minutes to run the installer (it's been a while since I installed it).
I can understand if you didn't want Classic on the machine, but it doesn't require anything fancy (no removal or changes to OS X) to install it.
Basically, if you install Classic under OS X, it just looks and behaves like any other OS X application.
To run classic, you just launch it, and then run any of the OS 9 applications you want. OS X then decides whether it is a classic mode program or OS X program and handles it accordingly. For all intents and purposes, it is pretty seamless.
Some people have classic mode configured to launch with the booting of OS X. Then, you can run OS 9 and OS X programs side by side, and not have to even think about classic mode. In that arrangement, you wouldn't even think about whether it was an OS 9 or OS X application.
But, personally, I prefer to just launch classic when needed. Otherwise, I just leave it closed.
I'm not sure if you are familiar with classic mode on OS X or not, but it isn't the same as dual booting, or having 2 separate operating systems installed. You don't choose between them when you boot, you just run classic on top of OS X.
Apple has actually made it so that many of the newer machines can only use classic mode on top of OS X. The newer machines cannot even boot OS 9 as a stand-alone operating system.
I can understand if you don't want to install the classic mode for OS X, but it would probably be more convenient to do that than to purchase a new copy of AppleWorks.
Best of luck to you whatever you decide. Let me know if you have other questions I might be able to answer for you.

Exchange Upgrade Path

Hey all...
We are using Exchange Server 2010, Version 14.02.0347.000. I did not install the server but I want to go to the latest SP and RU.
I am not sure what I need to install first. Can anyone point me to an upgrade path to the latest updates?
TIA!
David

AD changes?
SP3 for Exchange 2010 will upgrade the schema. Rather than repeat documentation already available, I'll just post this link:
http://exchangeserverpro.com/installing-exchange-server-2010-service-pack-3/
(Paul Cunningham's site - Exchange MVP).
If you prefer, you can update the schema and Active Directory separately before the SP3 install itself. This can better isolate the problem if one occurs (tell at what point it happened).
You just target the install files and use these commands:
setup /PrepareSchema or simply setup /ps
and then
setup /PrepareAD or simply setup /p
You will probably want to make full backups of Active Directory beforehand, just in case.
A health check of Active Directory would be a good idea since it sounds like you are working in a new environment and may not know what hidden problems might affect operations.
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ed6644f3-d197-420d-bb72-85bcdd1a5da5/how-to-test-active-directory-health?forum=winserverDS
+++++++++++++
EDIT:
I would pay close attention to the comments in the link above (Paul Cunningham article). In particular:
- 3rd party apps (AV, backup software). Are your's compatible with SP3?
- Customizations, to OWA in particular.
SP3 is essentially a new "full" installation of Exchange, so it may overwrite certain customizations.
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Upgrade path from Unity / Exchange to Unity Connection 7.1

Has anyone found (perhaps doesn't exist) an upgrade path from Unity / Exchange 4.1 to Unity Connection 7.1?

It will likely require a new server, but I just performed this migration. You also have to be on Unity 4.0(5) or higher in order to perform the migration. You use the COBRAS Export tool for Unity to grab the majority of system data and the COBRAS Import tool for Connection to migrate data over. Read up on COBRAS here:
http://www.ciscounitytools.com/Applications/General/COBRAS/COBRAS.html
If you have other questions, let me know.
Hailey
Please rate helpful posts!

What are all the possible upgrade paths from Tiger to Snow Leopard?

What is are all the ways to upgrade from Tiger to Snow Leopard?
Can I buy the 29.00 Snow Leopard upgrade? Or is my only path forward to do the Snow Leopard box set for Tiger? I know my model isn't support but this is a question about the upgrade path from Tiger to Snow Leopard.
Thanks in advance.
Todd

I have a Power PC dual 2 gig G5 running OS X 10.4.10. I know at some point that Leopard will not support the power PC platform, but I also know I probably will have one more upgrade path before my computer is no longer supported. I have not upgraded because My machine runs perfect. But I also know that a lot of my software will not run when I upgrade. Pro Tools, Maya,Mocha, various plug ins for Pro Tools. What path should I take to my final upgrade to the latest OS?
Thanks in advance

Upgrade from SCCM 2012 SP1 CU4 to R2 Fails - Unsupported Upgrade Path

Hi everybody,
I'm currently upgrading our SCCM infrastructure to SCCM 2012 R2 after have finished with the upgrade from SCCM 2012 RTM to SP1 CU4, thus far everything works fine, but when I try to update any
of the site servers, whether CAS or Primary, I'm getting the following error message in the Prerequisites Check:
I've gone through the system requirements and prerequisites over and over again and I can assure you that every possible update, supported OS, feature set, SQL Server, check list, etc,
etc, have been followed as per the official documentation available, however I'm stuck in this point, and surely enough I haven't been able to find out a similar case.Additionally I'm adding
the ConfigMgrPrereq log (the relevant portion of it) in case someone could kindly take a look at it.
<04-25-2014 02:06:46> ******* Start Prerequisite checking. *******
<04-25-2014 02:06:47> ********************************************
<04-25-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade,
minimum supported installed build version is [7804].
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Unsupported upgrade path;    Error;
Configuration Manager has detected that one or more sites in the hierarchy are installed with a version of Configuration Manager that is not supported for upgrade.
<04-25-2014 02:07:00> INFO: This rule only apply to primary site, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Active Replica MP;    Passed
<04-25-2014 02:07:00> INFO: This rule only applies to primary or secondary site in hierarchy, skip checking.
<04-25-2014 02:07:00> INFPROSCCMCMS.usersad.everis.int;
Parent site replication status;    Passed
<04-25-2014 02:07:00> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:00> ===== INFO: Prerequisite Type & Server: SQL:INFPROSCCMCDB.usersad.everis.int
=====
<04-25-2014 02:07:00> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:00> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;
SQL Server sysadmin rights;    Passed
<04-25-2014 02:07:00> INFPROSCCMCDB.usersad.everis.int;    SQL Server sysadmin rights
for reference site;    Passed
<04-25-2014 02:07:00> INFO: CheckLocalSys is Admin of <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Site server computer account administrative rights;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server security mode;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: OS version:601, ServicePack:1.
<04-25-2014 02:07:09> INFO: Target computer is a Windows server.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Unsupported site server operating system version for Setup;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Domain membership;    Passed
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Pending system restart;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: Return code:0, Major:10, Minor:50, BuildNum:4000
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server version;    Passed
<04-25-2014 02:07:09> INFO: Get Sql edition:Enterprise Edition.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Edition;    Passed
<04-25-2014 02:07:09> INFO: Checking Tcp is enabled to Static port, SQL Server:INFPROSCCMCDB.usersad.everis.int,
Instance:.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
SQL Server Tcp Port;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is limited.
<04-25-2014 02:07:09> INFO: SQL Server memory is limited.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Configuration for SQL Server memory usage;    Passed
<04-25-2014 02:07:09> INFO: Checking if SQL Server memory is configured to reserve minimum memory.
<04-25-2014 02:07:09> INFO: Installing the central administration site or primary site, requires SQL
Server to reserve a minimum of 8 gigabytes (GB) of memory.
<04-25-2014 02:07:09> WARN: SQL Server minimum memory is 8000 MB.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;    SQL Server process memory allocation;
Warning;    Configuration Manager requires SQL Server to reserve a minimum of 8 gigabytes (GB) of memory for the central administration site and primary site and a minimum of 4 gigabytes (GB) for the secondary site. This memory is reserved by
using the Minimum server memory setting under Server Memory Options and is configured by using SQL Server Management Studio. For more information about how to set a fixed amount of memory, see
http://go.microsoft.com/fwlink/p/?LinkId=233759.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Case-insensitive collation on SQL Server;    Passed
<04-25-2014 02:07:09> INFO: Check Machine FQDN: <INFPROSCCMCDB.usersad.everis.int>.
<04-25-2014 02:07:09> INFO: getaddrinfo returned success.
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Validate FQDN of SQL Server Computer;    Passed
<04-25-2014 02:07:09> INFO:CheckSupportedFQDNFormat <INFPROSCCMCDB.usersad.everis.int>
<04-25-2014 02:07:09> INFO: NetBIOS <INFPROSCCMCDB>
<04-25-2014 02:07:09> INFPROSCCMCDB.usersad.everis.int;
Primary FQDN;    Passed
<04-25-2014 02:07:09> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:09> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:09> ===== INFO: Prerequisite Type & Server: SDK:INFPROSCCMCMS.usersad.everis.int
=====
<04-25-2014 02:07:09> <<<RuleCategory: Access Permissions>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking access permissions...>>>
<04-25-2014 02:07:09> INFO: The rule 'Administrative rights on site system' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> <<<RuleCategory: System Requirements>>>
<04-25-2014 02:07:09> <<<CategoryDesc: Checking system requirements for ConfigMgr...>>>
<04-25-2014 02:07:09> INFO: The rule 'Unsupported site server operating system version for Setup' has
been run on server 'INFPROSCCMCMS.usersad.everis.int', skipped.
<04-25-2014 02:07:09> INFO: The rule 'Domain membership' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:09> INFO: Windows Cluster not found on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Failover Cluster;    Passed
<04-25-2014 02:07:10> INFO: The rule 'Pending system restart' has been run on server 'INFPROSCCMCMS.usersad.everis.int',
skipped.
<04-25-2014 02:07:10> <<<RuleCategory: Dependent Components>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking dependent components for ConfigMgr...>>>
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
Windows Deployment Tools installed;    Passed
<04-25-2014 02:07:10> INFO: CheckAdkWinPeInstalled on INFPROSCCMCMS.usersad.everis.int.
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;    Windows Preinstallation Environment
installed;    Passed
<04-25-2014 02:07:10> INFPROSCCMCMS.usersad.everis.int;
SMS Provider machine has same domain as site server;    Passed
<04-25-2014 02:07:10> <<<RuleCategory: Site Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking if the target ConfigMgr site is ready to upgrade...>>>
<04-25-2014 02:07:10> <<<RuleCategory: Database Upgrade Requirements>>>
<04-25-2014 02:07:10> <<<CategoryDesc: Checking the target ConfigMgr database is ready to upgrade...>>>
<04-25-2014 02:07:10> ***************************************************
<04-25-2014 02:07:10> ******* Prerequisite checking is completed. *******
<04-25-2014 02:07:10> ******************************************<04-25-2014 02:07:10> INFO: Updating
Prerequisite checking result into the registry
<04-25-2014 02:07:10> INFO: Connecting to INFPROSCCMCMS.usersad.everis.int registry
<04-25-2014 02:07:10> INFO: Setting registry values
If you wonder whether it might be related to this error:
-2014 02:07:00> INFO: Detected current installed build version [7711] for sitecode [BRA]. For Upgrade, minimum supported installed build version is [7804].
I confirm that this one site is a secondary one that's attached to a primary site and this log is from the CAS server, I managed to tall it and delete it from that site, but still appears listed
on the CAS management console, any idea how to force the removal of a secondary site that's attached to a primary from the CAS site when it has been removed already from said primary?
I've already tried the
Preinst /DELSITE XXX command but it only works when the site to remove it's attached to the local site and certainly not from a CAS
Finally, the version, build number and everything is correct, no idea what could be the problem, does anybody know a way to bypass this or force the re-evaluation of this rules, I've got
the impression that it's being cached somehow.
Any help would be highly appreciated,
Thank you.
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Hello again everybody,
I've finally managed to fix this up, in the end I had to delete those entries manually from the database as Garry suggested. After this was done the upgrade has gone through as expected with no further ado and has finalized already, now moving on to the
primary sites.
If anybody out there is facing the same issue, what I did was to delete those "stubborn" records executing the following statements over the CAS database:
DELETE
FROMServerDataWHERESiteCode='XXX'
DELETE
FROMSC_SiteDefinitionWHERESiteCode='XXX'
And this is pretty much about it. I'd recommend to take a proper backup first though as best practice.
Thank you all anyways for your answers and comments,
Marcelo Estrada MCP-MCTS-MCITP-MCSA-MCSE

Error Message: "This upgrade path is not supported"

Scenario
During the process of upgrade to Windows 10 Technical Preview, we may encounter the error “This upgrade path is not supported. Please close Setup and re-launch from the root of the media or go back and pick a different installation
choice.” in the Compatibility report.
Analysis
Step 1: Perform the scenario 1: the upgrade installation fails.
Reproduce this error following the steps below:
Download the Windows 10 Technical Preview ISO installation file.
Extract the ISO installation file to C:\New folder, and now the location of the installation file is
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\.
Click setup.exe from the installation file, and then click
Install now.
Setup is starting, and then get two options Upgrade and
Custom which is the classic setup wizard which we can see during booting from DVD.
Click Upgrade to run upgrade installation, however, the error occurs.
It seems that it is impossible to perform upgrade installation to Windows 10 Technical Preview, although it is fine to click
Custom to perform clean installation which cannot keep the personal setting and applications.
However, what we want is upgrade installation, not clean installation.
Step 2: Perform the scenario 2: the upgrade installation works fine.
If extract the ISO installation to C:\New in the above step2, click the
setup.exe from the installation file C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\, the upgrade installation would work fine, which is as shown the following two figures:
Step 3: Check the setupact.log
file which contains information about setup actions during the installation of the two scenarios.
Scenario 1: Check the setupact.log file of the scenario 1. The detailed information is shown as below:
2014-10-14 19:03:40, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:03:42, Info UI Will launch ConX setup experience
2014-10-14 19:03:42, Info UI Launching ConX setup experience
2014-10-14 19:03:42, Info UI Launching C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
2014-10-14 19:03:44, Info UI Unknown command line for ConX setup experience. Launching legacy setup experience.
2014-10-14 19:03:44, Info UI Determining if we are in WDS/Unattend mode
2014-10-14 19:03:44, Info UI No need to hide autorun
2014-10-14 19:03:44, Info [0x0a000a] UI Autorun:Autorun core successfully initialized!!!
2014-10-14 19:03:44, Info [0x0a000b] UI Autorun:Autorun UI successfully initialized!!!
2014-10-14 19:03:44, Info UI AppWindow has layout style 0
2014-10-14 19:03:45, Info UI NavWindow has layout style 0
2014-10-14 19:03:45, Info [0x0a011c] UI WizardDialogPost::SetActive
2014-10-14 19:04:57, Info [0x0a018e] UI Passing command line parameter ("C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.
Scenario 2: Check the setupact.log file of the scenario 2. The detailed information is shown as below:
2014-10-14 19:08:04, Info UI Determining whether we should run ConX or legacy setup
2014-10-14 19:08:05, Info UI Will launch ConX setup experience
2014-10-14 19:08:05, Info UI Launching ConX setup experience
2014-10-14 19:08:05, Info UI Launching C:\New\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe
According to the two logs, we can get the following points:
In scenario 1, it would invoke the SetupPrep.exe in the source folder directly to perform an installation preparation. However, it failed to recognize the path
C:\New folder\9841.0.140912-1613.FBL_RELEASE_CLIENTENTERPRISE_VOL_X64FRE_EN-US\Sources\SetupPrep.exe. Then it would launch legacy setup.
In the scenario 2, Windows setup would be redirected to the ConX setup to perform upgrade installation automatically.
So, what is the difference of the scenario 1 and 2 to bring the different results of upgrade installation?
Workaround
Based on lots of testing, we find that if there is no space in the extracting location of the ISO installation
file, the upgrade installation would work fine.
What’s more, we can get the meaning of the two setup models in the setupact.log:
Legacy setup: it is same with setup from DVD boot.
ConX setup: it would check the compatibility and language UI for upgrade preparation, then perform migration and upgrade directly.
Additional Resource
From the release of Windows 10 Technical Preview, many users have installed and tested Windows 10 Technical Preview, we still hope more and more users would download and install Windows 10 Technical Preview for test, and provide
us your feedback.
Download Windows Technical Preview
http://windows.microsoft.com/en-us/windows/preview-iso
Download Windows Technical Preview for Enterprise
http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hello,
I would guess that existence of a space in the folder name is what the issue is. Try removing the space from the folder name and see if works. New_Folder for example
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

Upgrade path question...

Similar Messages

Maybe you are looking for