WLSE to WCS upgrade path

Hi,
Could anybody tell me if they are aware of an upgrade path from WLSE to WCS using existing WLSE hardware? Can anybody point out the main benefits/features moving to WCS from WLSE?
Many thanks
SJ

Hi Scott,
Just the 1130-19 or 1133 are supported;
The new Cisco WCS SKU family, WCS-WLSE-UPG-K9, is now available for CiscoWorks WLSE customers that wish to migrate from CiscoWorks WLSE (Models 1130-19 or 1133) to Cisco WCS. These new SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
All CiscoWorks WLSE conversion SKUs ship with two special conversion CDs. These CDs check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
This SKU family supports only ***CiscoWorks WLSE hardware models 1130-19 and 1133. To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. ***Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Note: CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Model 1105) are not supported with CiscoWorks WLSE conversion SKUs. Do not install the CiscoWorks WLSE CDs on the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and it will not work.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Autonomous access points are not supported by a converted CiscoWorks WLSE.
Customers migrating their CiscoWorks WLSE to Cisco WCS do not need to buy a copy of RedHat Linux ES v. 4.0 software. A copy of RedHat Linux ES v. 4.0 software is included with the CiscoWorks WLSE migration CDs. (RedHat Linux AS v. 4.0 is not supported by a converted CiscoWorks WLSE.)
From this good doc;
http://www.cisco.com/en/US/products/sw/cscowork/ps3915/prod_bulletin0900aecd804b4635.html
Hope this helps!
Rob

Similar Messages

Installing WCS - upgrade path

Hello, I have WCS with location version 3.0.101.0 on CD, and want to know the best path to take regarding installing and upgrading to work with my controllers. I have two WiSMs with versions 3.2.78.4 and 4.0.179.11 with about 350 access points. I know I need to upgrade the controller verisons to be the same. Should I upgrade to WCS 4.0.87.0? Do I need to upgrade in steps, or go for the latest version right off. I want to upgrade WCS before adding any controllers.
Thanks

We upgraded our WLCs to 4.0.179.8 prior to installing the WCS (installed from scratch 4.0.81.0) and had good success.
The release notes for 4.x discussed a problem if you update the WLC to 4.x while the LWAPs are connected. I remember something about the APs being unable to download the new firmware successfully which sounds like you could end up with a real mess on your hands if the APs lock up in that state.
From page 6 of the installation notes: 6 "Connecting 1100 and 1300 Series Access Points: You must install software release 4.0.179.8 on the controller before connecting 1100 and 1300 series access points to the controller."
Here is the link to the installation notes:
http://www.cisco.com/cgi-bin/Software/Tablebuild/doftp.pl?ftpfile=cisco/crypto/3DES/wireless/aironet/WLAN/4400/WLC-4.0.179.11-ReleaseNotes.pdf&app=Tablebuild&status=showC2A
In terms of AP licensing, we ran into an issue where there were no AP licenses for the WCS. However, since this was a new install of WCS 4.0, and you are performing an upgrade, your experience might be better than ours was. If you run into AP licensing issues with WCS 4.0, you may want to reference the following forum thread:
(forum user, ethiel, ended up with better information than TAC on this particular problem):
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddc79a8
Finally, you may want to double check the firmware rev levels of your existing access points. Hopefully, this will not apply to you, but since you said you are running 3.x on one of your WiSMs...
Message Type : Field Notice
Title: Cisco Field Notice: FN - 62474 - LWAPP 1231 Fails to Upgrade to 4.0.155.0 with 4402 Image
URL:
http://www.cisco.com/en/US/customer/products/hw/wireless/ps430/products_field_notice09186a00806e3ac7.shtml
Posted: July 14, 2006
Summary: When a 1200, 1130 or 1240-series Access Point, with an LWAPP image installed that is prior to 12.3(11)JX, attempts to connect to a Wireless LAN Controller running 4.0.155.0 software, the Access Point may be unable to complete downloading its updated
software.
Hope this helps
- John

WLSE - WCS upgrade license question

Hello,
We need to upgrade our WLSE to WCS but our sales people bought the wrong license (WCS-Standard-K9) Is it possible to upgrade the WLSE to WCS with this license and just get the conversion CDs needed from you ?

Hi Gudmundur,
This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
[email protected]
Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Please see Appendix C for information about receiving support for existing SMARTnetÂ® (hardware support) contracts for CiscoWorks WLSE.
Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
Base or Location
Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
PAK Certificate, Instructions and CD
Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
Hope this helps!
Hi Gudmundur,
This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
[email protected]
Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
Please see Appendix C for information about receiving support for existing SMARTnetÂ® (hardware support) contracts for CiscoWorks WLSE.
Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
Base or Location
Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
PAK Certificate, Instructions and CD
Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
Hope this helps!

Ordering the wlse to WCS converion CD with 100 LAPS support

I am getting the below message when i tried to order the convertion product WCS-WLSE-APB-100 Option WLSE To WCS 100 AP. License And CD. N/A $4,796-
1. You are only eligible for a WCS-WLSE SKU if you have the WLSE 1130-19 and 1133 platforms. These SKUs can only be installed and run on the WLSE 1130-19 and 1133 Platforms.
Why can't i order the above said product enen though that is found in cisco Global price list.
It is very urgent issue to be resolved to order the product
Please looking for your suggestions.
swamy

Hi Bobby:
Yes, in order to run WCS versions beyond 4.2, you'll need a Red Hat upgrade on a converted WLSE. Because the conversion process brought Red Hat provided by Cisco, the converted WLSE is indeed an appliance (it's just not called that) and Cisco does indeed provide the Red Hat upgrade. You can open a service request with TAC and they'll post the ISO image of the Red Hat upgrade CD for you, or give me your Cisco.com ID and I'll post it for you without an SR.
As for your proposed upgrade path, if this was *my* WCS installation to address, I'd go:
4.1.83.0 to 4.2.128.0 then run Data Cleanup
4.2.128.0 to 6.0.181.0
6.0.181.0 to 7.0.164.0
Long and short, avoiding some bugs and letting 4.2 executables clean a 4.2 database before exiting the train, then bypassing 5.* altogether.
Sincerely,
Rollin Kibbe
Network Management Systems Team

WCS upgrade to Prime 1.2

I'm currently running WCS 7.0.230 ready for upgrade to Prime 1.2. Reading Cisco docs, the path is to upgrade from WCS to NCS 1.1.1.24 firstly, then to Prime 1.2
so far...
export.bat all > wcs-export.zip
also performed a backup via the GUI backup tool
have a NCS 1.1.1.24 - 30 day eval license (docs say eval is enough before upgrading to Prime 1.2 which you have purchased)
A couple of things are not clear to me,
http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/quickstart/guide/cpi_qsg.html#wp56675
currently WCS runs
7.0.230
Feature - plus
AP limit 150
Type permanent
Does this mean I need to uninstall WCS to install NCS cleanly or is there an upgrade path without uninstalling WCS manually? In the download section you can only download for Small/medium/Large. I intend to download medium, but again there are no specifics I can find in relation to my WCS license i.e. - AP limit = NCS medium or do I look at my new Prime License 500 Device upgrade LIC
I'm looking for better documentation WCS > Prime.

I manged to upgrade to NCS 1.1.1.24 without any problems and successfully migrate the WCS backup file into NCS.
The next issue I have is upgrading from NCS 1.1.1.24 to Prime 1.2.
Performed NCS backup successfully
admin# show repository defaultRepo
backup-20130422-0950.tar.gpg
PI-upgrade-bundle-1.2.1.12.tar.gz
Upgrade not successful (i'm still running NCS eval license, should I be importing Prime PAK licenses after upgrade to Prime?)
admin# application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz defaultRep o
Save the current ADE-OS running configuration? (yes/no) [yes] ?
Generating configuration...
Saved the ADE-OS running configuration to startup successfully
Initiating Application Upgrade...
Stage 1 of 7: Transferring file ...
-- complete.
Stage 2 of 7: Unpacking file ...
-- complete.
% One or more required RPM's not found in the bundle
admin# show ver
Cisco Application Deployment Engine OS Release: 2.0
ADE-OS Build Version: 2.0.1.038
ADE-OS System Architecture: x86_64
Copyright (c) 2005-2010 by Cisco Systems, Inc.
All rights reserved.
Hostname: SV195968
Version information of installed applications
Cisco Prime Network Control System
Version : 1.1.1.24

Ciscoworks 3.2.1 Upgrade Path

We have Ciscoworks 3.2.1 (Windows Server). We also currently have Cisco Prime Infrastructure 1.2 (appliance) for wireless management.
I'm getting a bit confused trying to determine the appropriate upgrade path for the LMS server. I'm wondering if I should be upgrading the existing server to Prime Infrastructure 1.2 which will run on the windows server or migrate the wired management to the Prime Infrastructure 1.2 appliance? I like the idea of one management portal for both wired and wireless networks. Does Cisco take a module based approach to the licensing of the Prime Infrastructure products? In other words, do I need to simply buy the "LMS module" for use on the existing appliance? The Windows Server has dated hardware so I would also need to confirm that it supports the upgrade if that is the recommended path.
I'd like to hear what others have done that have made the switch to Prime Infrastructure from LMS.

LMS and Cisco PI are intended to merge in coming period, but in Cisco PI it almost run a parallel to LMS and is not the complete replacement of LMS.
Every new release comes out with more LMS featured baked inside Cisco PI. Hence I recommend you to keep your LMS for LAN Management tasks.
Cisco PI is an complete and evolved upgrade to WCS/NCS. You can upgrade the following Cisco Prime Network Control System products to Cisco Prime Infrastructure 1.2:
•Cisco Prime Network Control System 1.0.0 (NCS 1.0 MR2, 1.0.2.29)
•Cisco Prime Network Control System 1.1.0 (NCS 1.1 FCS, 1.1.0.58)
•Cisco Prime Network Control System 1.1.1 (NCS 1.1 K MR1, 1.1.1.24)
On Server side, I think CPI can't be installed on LMS Windows server as it has to have a virtulized environment. You should keep and treat both separately. However, if you have got the LMS 4.2 license with CPI , you should upgrade your LMS to version 4.2 and get CPI to manage wireless infrastructure.
-Thanks

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

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.

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me kn

I am trying to upgrade EPM 8.9(8.49.23) to EPM 9.1 (8.53.08). During dataconversion step the AE process finished succssfully in few seconds. When i see the log it says "There are no conversions to run for upgrade path PF89 (18028,10003)". Please let me know why it didnt do any conversion. Am i missing something?

yes, that app engine didnt inserted any rows. So now when i tried to drill down i found that there was no data in the "new demo" database on table UPG_DATACONV. That is the reason for all this.
When i applied required for upgrade patch in demo it said couple of patch already exists so those update i skipped. Now when i check upd877654 has a step which imports the data in this table. my change assistant told that the update is already available in my demo so i skipped. Now i am not sure what to do.
I tried reimporting the data and running the analyzer again. But worried that there can be any issues due to this.

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

Upgrade Path from 5.1.4

We are currently running version 5.1.4 and are looking to upgrade. What is the recommended upgrade path or version we should be planning to go to? Our pipeline isn't very complicated since I've read some articles about there not being a direct migration to version 3.0. We currently develop using the RAD toolkit and .NET if that is a factor when upgrading.
Also if someone could clarify which packages I'm looking at migrating to as before I installed Endeca IAP and Dev Studio and I was up and running. I don't see those packages in the newer versions of the software and I'm not 100% on what the packages were renamed to after the transition to Oracle.

It sounds like you are upgrading an Endeca Commerce / Guided Search implementation. This forum is for Oracle Endeca Information Discovery (EID) products. You will get better answers over on the other forum, https://forums.oracle.com/community/developer/english/endeca_experience_management/technical_questions .

Merom / Conroe upgrade path for Intel iMac?

Has anything been released about a processor upgrade path (if possible) to take the Early 2006 IiMacs from the Yonah CPU family to Merom or Conroe?
I'm still steamed to be stuck with a 32-bit CPU (even though it is a good one, funny how that fact is still judiciously left out of all promotional materials) and wondered if I will be left high and dry in 2-3 months when the 64-bit Core 2 Duo chips ship.
It would be nice if there were an upgrade path to bring the early adopter faithful into the 64-bit realm. Anyone heard a mighty rumblin' ?

People have successfully removed the CPU and replaced it. And, the new chips are supposed to be compatible with any Yonah based system.
So, while there is no official upgrade path, it should not be a problem installing a new CPU in the machine later.
Obviously, the heat of the new chips will be a consideration. They may be hotter, they may not be.
And, it will obviously void your warranty.
But, it should be possible.

Upgrade path

we are upgrading from ACS 2.6 to 4.1
should we order the upgrade software (CSACS-4.1-WINUP-K9) or should we order the regular package (CSACS-4.1-WIN-K9)since 2.6 is so out of date?

Hi Martin,
I agree with Scott (no surprise!) One of my co-workers just went down the upgrade path (albeit from a more recent version) and it was very messy. I'm pretty sure he finally just ditched the whole plan and started fresh.
Hope this helps!
Rob

Usually there is a upgrade path for current users of the software at a reduced price. I dont see anything like that for Lightroom 6. Will I have to pay full price just to upgrade to the new LR6 standalone version???

Usually there is a upgrade path for current users of the software at a reduced price. I dont see anything like that for Lightroom 6. Will I have to pay full price just to upgrade to the new LR6 standalone version???

The standalone upgrade is 79 US Dollars.
Go to Products, select Lightroom 6, click on Buy, select Upgrade instead of Full

WLSE to WCS upgrade path

Similar Messages

Maybe you are looking for